Advanced Search

Probably by remaping M3 would be the best way, but no idea if M3 can be remaped.
I am sure it can be done in hal but that is quite a journey.
Using M6 or M7 is much easier, see mist/coolant use, requires adding an output for it in wizard, be it StepConf or PncConf.

Seems to be a kernel issue, to many PC's having the same issue, i though this was already fixed by using new kernels.

Maybe these modified files help:
forum.linuxcnc.org/21-axis/53099-manual-...-9-2?start=10#304309

'/sim/axis/remap/manual-toolchange-with-tool-length-switch' runs for me on a 2.9 build from February:
 

I just had some time to look into this again and a closer inspection of the 'lib/python/gladevcp' folder revealed that I had modified versions of 'hal_python.xml' and 'hal_widgets.py' files that seem to fix this error.

 

If you want it to startup in G54 then change this line in your ini:

RS274NGC_STARTUP_CODE = G64 P0.05

to

RS274NGC_STARTUP_CODE = G54 G64 P0.05


You may also want to set other things here
RS274NGC_STARTUP_CODE = G17 G21 G40 G49 G54 G64 P0.05 G80 G90 G94 G97 G98

Actually just found it in the docs var 5220

Hi Andy ; can you send me your mail adress or facebook or insatgram ..

That would be embarrassing, but an easy fix, and the sequence of events would match that.

I actually assumed that linuxcnc defaults to that on startup.

My mini mill at home appears to. Is that specifically set in linuxcnc?

Will have to wait till tomorrow to give it a try


Will do a clean startup and see what appears in the modal window

What was the result? Were you able to start the machine?

Hello Andypugh,
I had same error.
If I deleted "n_rows" and "n_colums", it can run, but layout is not as beautiful as design.
Can you update ?.
Thank you.

2. Run a tool orientation algo for a & b axis. I think using A & B is simplest. This then solves smoothing for A & B axis toolpath.

This would only work for a machine with XYZAB kinematics so the algorithm needs to be adjusted depending on the type of machine kinematics used in the particular config as solving for AB angles will not work for XYZAC (C axis instead of a B axis) or XYZBC (C axis instead of a A axis) machines.  

Tonight i went to the production machine with a hard-drive for testing hal-core.
After figuring out how to setup hal parport and run posix realtime etc for a few hours,
i managed to run the machine on hal-core.

I'm still a bit confused seeing that tool motion still decelerates to a full stop after each segment. I guess feed rate blending over consecutive feed moves is a separate problem to solve but given the importance of constant tool velocity in CNC trajectory planning I'm wondering if you have a solution in mind for this yet. 

I think a look at your hal and in files will need looking at. And a drawing of your actual wiring.

Try the parallel port tester as mentioned at the beginning of this thread.
Try it without the breakout board connected, if everything is fine try again with the breakout board connected.
BTW what voltage are you powering the breakout board with ?

N40 G54

Are you sure you are also zeroing the Z offset in G54?