Advanced Search

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.

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.

I'm in the process of upgrading my DIY router mill to include dual Y axis steppers. The current configuration uses a single Y stepper to move a rather long axis (~ 44 in) on which the X axis rides to provide X/Y motion for cutting.  However, on long, fast moves I sometime notice slight cogging.

I have an extra stepper and Microstepper that matches the current Y Stepper-Microstepper combination that I would like to incorporate to minimize cogging.

The machine uses a MESA 7i76u 5 axis control board. My question is, will the MESA 7i76u provide sufficient direction and step current to drive two Microstepper drives so that both get their signals at the exact same time? Or, do I need to configure separate sections of my HAL and configuration files to drive each driver separately and if so, how would I go about the configuration?

I did find an old post on the subject of two steppers for an axis, but it was for a rather old version of LCNC.  I guessing that 2.9.4 may have a more straight forward approach to configure dual axis drives.

Kind regards,

Thanks for your reply tommylight. Sorry if this sounds stupid but I selected each axis (X, Y, Z) and click the +/- buttons to move it in that direction, but it still doesn't seem like Home All works. It only seems to home the y axis (so j = 1).

Im still getting errors for j = 0 and j = 2

Simulated switches so you have to move all axis to be able to home again.

I think I might of taken a pic of mine but no originally it was rbobey1989

I'm having trouble understanding why my "axis" simulation is getting "Cannot home while shared home switch is closed". This happens once I click "Home All" twice. I'm wondering if I have something setup incorrectly.

My end goal is to be able to do this via python. I have attached my current python code (which I don't think is the issue) and I get the same issue.

Thanks

dachte eher so:)

youtube.com/shorts/6ZKBH5xW8OQ

www.amazon.de/dp/B0FNRH8QSN

Optional:
www.amazon.de/TECNOIOT-Two-Way-Transfer-...081J5R35N/ref=sr_1_6