Advanced Search

Was this an one time fault or did it happen again with this g-code file? Or also with other files?

The easiest way to get the last line is to monitor the pin gmoccapy.program.current-line with halscope.

I bet you will get a nice pcb when you are done, keep up the good work.

Which version have you installed?
I guess you are talking about the slider that controls the jog velocity? This slider gets its max value from [TRAJ] MAX_LINEAR_VELOCITY , see  linuxcnc.org/docs/html/gui/gmoccapy.html#gmoccapy:traj-section
 

Thanks Chris,

Yes, that is what I meant. I am using 2.9.4 and the HD version of QTDragon.

No hurry at all. I've got my m6remap working really well. It allows using a mix of fixed and variable length tools where the variable length ones get automatically measured during the manual tool change. I'm just adding the finishing touches. I use this in conjunction with Basic Probe.

Thanks again.
John

I took a look and was able to add shift modifer which will make shift key use the max velocity ini setting as the override speed. I tested here and it works in all levels of safety, I need a few independent tests done before i push to the develop branch.

Hello
I have gmoccapy installed the problem is that the feed bar in manual mode has inflated values compared to those defined in the ini file. I don't know if this is supposed to be the case or do I need to change something in my configuration?

Here is a video of the system: 

tommy, idk, isn't linuxCNC built on python?

Those lines won't work in the remap (if that is what you meant) you would need to connect those to a HAL pin in qtdragon, then read the pins n the remap. I'm at work right now but will see if I can make a sample file for qtdragon tonight. You use master and regular or HD dragon?