Advanced Search

currently the "+" key in combination with a keyboard jog key will run at max speed, the "-" key in combination with a keyboard jog key will run at 10% of the jog speed slider adjusted speed. so you do have access currently to speed overrides with the keyboard in probe basic.

I ran a linuxcnc 2.9.2 instance with axis in a virtualbox. I look at linuxcnc status.

One call to G10 L1 P1 X10 and G43 works fine. g5x_offset don't move, tool_offset is changing to X10.
The same test with qtaxis needs two call to G10 and G43 in order it works.

I managed to do my offset change on the fly with a numbered variable and two calls to G10, so it's not a problem anymore for me, but I think there's a bug to look at here.

I already watched that!
No LinuxCNC is not built on python, but it does use Python for remap and VCP and lately for every new GUI, it is C/C++ and TCL mostly, as far as i know.

forum.linuxcnc.org/show-your-stuff/38547...plasma-build?start=0

linuxcnc.org/docs/html/plasma/plasma-cnc-primer.html

forum.linuxcnc.org/plasma-laser/35349-cn...lding-info-and-guide

What drives are you using?

In this case you should ask Dmitry as I don't know his sources from he built his debs.

Not sure if it would overwrite his drivers if you install the official LinuxCNC package but it could be worth a try.

It is installed from Dmitry's NYX53, which is mainly bringing the NYX stuff up to par with 2.9.4. This is the link: yurtaev.com/nyx32.html

Yes, you will find most answer in the doc. I suggest you to install the complete linuxcnc distrib (it can be done in a virtualbox to use it as a sandbox) to focus on your interface test. Here you can load a simulation example and then modify yourself the different files (some of them are duplicated in your home directory).

I have created a new configuration for axis and the option to move faster by pressing shift plus the movement keys works, and in Probe Basic I can confirm that it worked before the update.

If I can help you test something, let me know.

Yes that is correct. Keep in mind that the unit in TRAJ is in machine units per second (linuxcnc.org/docs/html/config/ini-config.html#sub:ini:sec:traj)
and in Gmoccapy it is machine units per minute.

I think you blow the current sensing resistor. There is no current limiting resistor in today's stepper drivers.
In normal operation, it's impossible, the board will measure the current, and open the transistor when it reach the maximum.
Either the current sensing is dead, either the power stage is damaged, and can't stop the current (a damaged mosfet is always closed). It's more probably the power stage.

Hi,
it seems that your glade file is corrupted somehow. If I look at the glade file in 2.9.4: github.com/LinuxCNC/linuxcnc/blob/v2.9.4...ccapy/gmoccapy.glade - I can't find those duplicates.

How did you install LinuxCNC 2.9.4? Directly from the ISO image or updated from 2.9.3 or earlier?
 

Enjoy your holiday.

zz912 wrote:

I would like to return to my original question. How is it possible to reference files in source codes? Does anyone know? Or at least have some guidance?

forum.linuxcnc.org/gmoccapy/55011-lcnc-2...-g43?start=10#320387

Let me have a look when I am back from holiday...

zz912 wrote:

 
Could be possible read notifies from release_notes.txt?
github.com/LinuxCNC/linuxcnc/blob/master...py/release_notes.txt

Possible, but it would be a very long list if someone is updating e.g. from 2.8.0 to 2.9.4.
Therefore I only want to add infos that one really need to pay attention at.