Advanced Search

Consider setting the HOME_SEQUENCE value for joint 4 and 5 to 2 so it can be homed with the Y axis.

Are you sure HOME_IGNORE_LIMITS = YES is a good idea?

Seems a bit potentially risky.

Anyway, linuxcnc.langdonstaab.ca/media/kunena/at..._auto_probe_tool.ngc seems to have stuff like `#<_ini[CHANGE_POSITION]Y>`

But as far as I can see, no such variable with that name is in the INI file.

Is there another INI file?

Otherwise, where the is LinuxCNC retrieving these values from?

In the NGC file it shows an error message and returns LinuxCNC is not in the correct measurement mode, why not just call G21 at the top of the file to ensure the correct mode is enabled always?

Why show a prompt when a simple G21 would (likely) suffice?

On the Fujitsu also make sure that if it has the AMT feature
(common in corporate desktops), that it is disabled.

Also disable EEE and any PCIE power saving  in grub.

When you get to about the stepper motor section of pncconf check out "tandem" axis... like this:

 

Also, depending on your machine you may or may not need to invert the direction of one of the motors. There's a few ways to do that but this is one way:

 

attached are my config files. I have been trying for over a week to get the remap to work, I don't know what am I doing wrong. thank you!

I don't really know but have a look here:
github.com/LinuxCNC/linuxcnc/blob/bd96ca...tion/control.c#L2023

Thanks for your feedback. I'm not so worried about the first issue above as much as the second issue that I describe above.

The second problem has persisted for a long time and many have tried their luck at resolving it. I continue to see problems being discussed
that may be probable causes for this subroutine. 

Honestly, I think that the documentation around what I have described is perhaps incorrect or simply doesn't provide enough information
for the operator to make the subroutine work as expected. A good example of this is line number 31, the instructions indicate the following:

  31;  4 - Workpiece Measure: Use the button under the Probe Screens for "Probe Z height
  32 ;        of material:" this will set and display on the Probe Settings screen the
  33 ;        "Block Ht" = #<_hal[qtversaprobe.blockheight]> value in ABS coordinates.

What is missing is is there should be a "Jog to a coordinate" in order to measure the work piece height which will determine the "Block Ht" .

I am curious if there are any other steps involved that are not documented?

You should not need to "Clear all tool offsets (set Z to 0.0)"

Isn't that what G53 is for?

Please post .hal and ini files.

So sorry that meant around 22mm

Included with LinuxCNC, go to "sample configurations">sim>axis>remap>ract-toolchange>racktoolchange
It will copy the sample config to your config directory, so you can have a look at what it uses, and copy/paste the relevant stuff to your working machine config for testing on the actual machine.
Do make a backup or two before editing your machine files.

I do recall getting the same thing sometimes, but i never really bothered with why it happens, it is a sim and i use it only to check the gcode sometimes, not for anything important.
If you want to test on a real machine but with no machine attached, use the parallel port configs, so will work even with no parallel port, but it is a real machine so nothing is simulated. You will have to use immediate homing for it though.

Thanks everyone for the support.
Yes, I know, so where can I change the value in the source code?

Perhaps someone typed " " instead of "", or perhaps it's an intentional design to ensure an empty filename is impossible.

Hmm...

What does "probe height" mean.

Same as: linuxcnc.langdonstaab.ca/42-deutsch/57850-rack-atc

Could you provide us with some more info regarding the machine and what you hope to acheive?

The ideal way would be to have 2 sets of step/dir signals and 2 Y home switches so
any gantry racking can be corrected every time the machine is homed.

Whether one step/dir output can drive 2 motor drive inputs depends on the current
requirements of those inputs, but in general I would suggest the separate drive/separate
home switch system.