Advanced Search

To not answer your question....
If the backlog of counts is causing a problem, you can enable:

joint.N.jog-vel-mode IN BIT

When FALSE (the default), the jogwheel operates in position mode. The joint will move exactly jog-scale units for each count, regardless of how long that might take. When TRUE, the wheel operates in velocity mode - motion stops when the wheel stops, even if that means the commanded motion is not completed.


If you can find where in the motion code the "backlog" exists then you could connect it to one of the supplied "debug" parameters:
github.com/LinuxCNC/linuxcnc/blob/master...motion/motion.c#L556

These are already set up in the code, you just need to assign values to (for example) emcmot_hal_data->debug_float_0 to see that number in the HAL.
(and recompile LinuxCNC)

I think you can probably use a 7i37-TA, but it will need to be wired differently.
But a repair might well be possible.

You mean, that you didn`t tune your Servos at all?
In my world a Servo need to be tuned connected to the machine and the load it has to work with to work properly and performant.

Aciera wrote:

Why a user entry for a float value would be passed through all of that, I have no idea.

That part I can explain. Axis allows you to enter any valid G-code expression (apparently including parameters) in the numeric entry box. 

I have used it for simple things like 1234.5 / 2 but it also allows functions like SIN / COS / PI (?) and from looking at the code I think you can probably use the numeric parameters in the .vars file. 

So, in this case the error seems to be caused by not finding the PARAMETER_FILE. 

OP: does that entry appear in your INI? And does the referenced file exist? (and who does it belong to?)
linuxcnc.org/docs/stable/html/config/ini...sub:ini:sec:rs274ngc

 

HAHA
Thank you!
I spent so much time on this, I had forgotten to hook that up. Still strange that the LEDs worked after connecting 4 switches. Anyhow. I can finish this now.

Nevermind, I have changed the JTAG programmer to USB Blaster and everything went fine.

My board responds to pings, but seems to drop 50% of the packets, is this normal?

I generally keep signal & power separate (I include the wires for the stepper coils power).

Even then unknown I don't expect things to get better with the next administrations.

You can thank the UK gumbernment and my own pseudo socialist gumbernment. It's embarrassing to be an Aussie at the moment and we have 3 more years of the fools.

Unserstood, thank you

Hi Everyone,

I am in the process of wiring up my first CNC machine and just spent the day finishing up the wiring from my closed-loop stepper motors to the drive, and was wondering if I had made a big blunder. Since the encoder needs 6 wires for EB-, EB+, EA-, EA+, VCC and GND and the stepper power needs 4 more for A+, A-, B+ and B-, I used a single 10-core shielded cable from the drive to the stepper. Is this ok, or will it cause problems, and should I have used a 4-core and a 6-core cables instead? I don't have much of an electrical background, so I am really unsure about this. Thanks for your help

Gautham

Hi Everyone

I am in the process of wiring up my first CNC 5-axis machine and I wanted to know if I can use this Rotary Encoder  to home the A-axis and if so how would I wire it up. From the research I have done, my understanding is that it can be done but it involves some editing of VHD files that I didn't really understand since I am new to LinuxCNC. Thanks for the help

Gautham

Thinking about this a little more, where is the documentation link to writing custom conversation macros? Basic ones,I can learn on or test.

I have a few conversation mill events in python, but just can't figure out how to try and load them. Looks like I need a gfx screen and then links to the macros. Which then produces some gcode?

Any help or videos would be awesome. I want to add a nice pocket and frame event.

AG

richcolvin wrote:

What did you do to fix it?
 

I updated to GTK+ v3.x, and asked ChatGPT to help me update my lzpanel.ui file to the latest version. It was amazingly helpful in this regard, although I think there were a couple hiccups along the way.

If it ain't broke, don't fix it.