looking for help on basic (sim-)setup

More
9 years 8 months ago #88666 by Reinhard
Hello,

I want to work with hal and therefor I'm looking for a simple way to process gcode-files without bothering with limit- or home-switches, homing and whatever might popup errors before gcode-processing.
I created axis- and joint-definitions with pretty big positive and negative limits - to not touch them.

Additionally I used NO_FORCE_HOMING=1 and HOME_IGNORE_LIMITS=yes
... but linuxcnc stil pops up errors like "need to home axis before switching to mdi" and the like.

How can I setup a fake-linuxcnc that just processes gcode-files through motion and trajectory planner, so that I can use the motion-pins in hal?

Please Log in to join the conversation.

More
9 years 8 months ago #88670 by Todd Zuercher
In you ini for the axis in question you need to follow the settings here.
linuxcnc.org/docs/html/config/ini-homing.html#_immediate_homing

Where did you place the NO_FORCE_HOMING=1 in your ini file? It would need to be under the [TRAJ] section.

Please Log in to join the conversation.

More
9 years 8 months ago #88673 by Reinhard
yes, NO_FORCE_HOMING is in TRAJ section.

following the recommendations from link did not change anything.
Stil get the errors
Code:
all joints must be homed before going into teleop mode all joints must be homed before going into coordinated mode

Please Log in to join the conversation.

More
9 years 8 months ago #88689 by Todd Zuercher
What version of Linuxcnc are you trying to use?

Please Log in to join the conversation.

More
9 years 8 months ago #88716 by Reinhard
master build as uspace only (no rt-kernel).

To understand hal I don't care about jitter of servo-thread ...

Please Log in to join the conversation.

More
9 years 8 months ago #88717 by Todd Zuercher
Would you mind posting the ini file you are trying to use.

I believe in Master the homing info in the link I posted needs to be set in the [JOINT_N] section(s) rather than the [AXIS_N] as in the previous versions of Linuxcnc, and it looks like the docs have not been updated to reflect those changes yet.

Please Log in to join the conversation.

More
9 years 8 months ago #88718 by Reinhard
No, I don't mind :)

I started with a copy of sim.axis/gantry_mm and for so, the tags where already placed at joints.
After your hint, I just copied the tags to the axis sections too, without removing them from the joints.

axis-UI has different sliders for feed-override and fast-move-override.
I found one feed-override input on motion only. So how should I wire the signals for correct usage?

Please Log in to join the conversation.

More
9 years 8 months ago #88720 by Reinhard
Ok, I changed to gmoccapy and the homing macro seems to work.

The cursor behaviour is a little bit confusing, but after all, it works. :)
Thank you.

Please Log in to join the conversation.

Time to create page: 0.094 seconds
Powered by Kunena Forum