Advanced Search

I have finally started to work with LinuxCNC
Tried using the Mach import feature in LinuxCNC but it didn't work very well for me, but I was fortunate enough to have both systems' monitors on the same shelf side by side which resulted in a nearly working LinuxCNC system.

The LinuxCNC system is able to run the home-all routine, but I find that the Z axis goes in the wrong direction, so after home-all I need to enter a positive value (G0 Z10) to get the tool to move towards the workpiece.
This is wrong in my mind, as it should be a negative value like: G0 Z10. 

I find that the X and Y axes work as I thought, it is only Z I have problems with.
What do you think is the error?

 

Many thanks! this sounds way easier than I tought.

A 'queuebuster' is a command that tells the interpreter to stop parsing Gcode until actual code execution has caught up (ie the command queue is empty). After such an event the new ini.* values are reloaded and Gcode parsing restarts.

The queue buster (eg reading an analog input) needs to be right after the change
in the ini values (eg done in the 'M123'). I usually put a queue buster in front as well:

Aciera wrote:

The underlying problem may be that GUIs handle this differently (ie have not been updated to the new [SPINDLE_n] section) but I'm not sure.

Please raise an issue so it does not get lost.
 

I have raised an issue here: github.com/LinuxCNC/linuxcnc/issues/3171

I vaguely remembered there being a discussion about this and I just found it. This may explain some of the issues:
github.com/LinuxCNC/linuxcnc/issues/2335

Thanks that already helped a lot.
linking and unlinking Hal I can mange in a bash script.
I would switch reference and limit switch for toolchenge and Bach afterwards.
What I don't understand is the queuebuster command.
What I understand ist the the limits are part of the milltask an I can alter the values with halcmd without altering the infile.
Where and how do I need the queuebuster?

Thanks

Patrick

JT wrote:

Many of the later GUI's introduced a ton of extra ini settings, the authors of those GUI's should update the docs if they moved from display to spindle. I really don't understand why they didn't use the existing ini entries...

JT
 

There does seem to be a bit of inconsistency, duplication and ambiguity in the ini files used and/or generated by either GUIs or configuration tools - is there available guidance on how to use the in file (or is that something I could try to contribute?).

I am planning to create a separate [MANUALMATIC] section where its ini options take priority over values set elsewhere - perhaps the GUIs should each use their own section and keep [DISPLAY] for purely generic/official display options?

The moving of (say) spindle options to a spindle section makes sense initially but should it also include purely UI options like INCREMENT? I don't really have a view on that, but it depends on what the ini sections are supposed to define. eg. TRAJ has options that apply to both the machine and the UI (eg MAX_LINEAR_VELOCITY) but others that it could be argued only apply to the UI (eg DEFAULT_LINEAR_VELOCITY).

I'm not really qualified to have an opinion on any of the above, hence the question, but would be happy to try to document the views of those who are qualified!

 

Softlimit values are accessible in the ini.* hal pins after startup has completed.
If changed during gcode execution (eg by using a custom mcode) they need a queuebuster command to be updated internally.
Limit switches can be disconnected/reconnected in hal.

1. Open the 'show halconfiguration' tool and check if the 'cia402_homecomp' component and its pins have been created.

2. Start linuxcnc from a terminal, select your config and check for errors:

Tutorial 15



JT

tommylight wrote:

Would this be better in the "LinuxCNC documents" section?
 

This is a very sensible suggestion - not sure why I didn't but probably because my question evolved as I wrote it!

Many of the later GUI's introduced a ton of extra ini settings, the authors of those GUI's should update the docs if they moved from display to spindle. I really don't understand why they didn't use the existing ini entries...

JT

What resistor value would you use between positive of the isolated power supply and the positive input of the THCAD ?

Get the Mesa 7i85, without the S.
And THCAD5 or 10 and 2 of 1MOhm/2W resistors, it is most probably a HF/HV pilot start plasma, and 300 is not recomended for those, although i am sure it works, i have several of those in daily use.
For power supplies, 5V and 24V, both at 5A should do just fine, MeanWell or Delta preferably.

Hello,

okay thank you.
One other question about the G-Code. Where can I read about the supported G-Code for Linux CNC and what kind of postprozessor I have to use or setup.
I need some bore cycles and helix in all 3 axis...

Have a nice day
Martin