Advanced Search

Typically the Realtek MAC requires the DKMS driver for usable latency.

Not sure which thread is the best on this but searching the forum for "DKMS"
will find a thread that shows the Realtek DKMS driver installation details.

You are not guaranteed to see any change in the Z signal
as its a short pulse and quite hard to catch at the 1 KHz servo thread.
(especially with higher resolution scales)

This is why the actual index event is captured in hardware.

The index (Z) signal is only provided as a hal signal for debugging
or using it as a GP input. It's normally not of any other use.

If index enable goes false on an index event, the index was detected.
 

If you have a Mesa setup, you could add a 7I73 that will support up to 4
MPG encoders (plus buttons/keypad/etc) and unlike the Arduino, it's
real-time.

Hi Dylan,

Have a look through the docs, they should point you in the right direction.

remora-docs.readthedocs.io/en/latest/index.html

You will need to flash the original firmware back onto the board as the Remora firmware will be loaded off the SD card with the original bootloader.

I'm working at designing a small CNC machine for milling lock set mortises and would like to incorporate automatic tool length detection.  I was wondering if a proximity switch could be used to accurately detect the tool tip.  The tool would be spinning slowly in the spindle and lower into the prox's detection field from above the switch.  The tool size, shape and material makeup should stay the same from one tool change to the next, so I shouldn't need to worry about a variety of different tools being detected differently by the sensor. 

Thoughts and opinions?  Think this could work consistently? Or would it be better to simply use a conductive pad with a lead connected to the tool or conventional normally closed switch.

yes, I checked all that with 4 encoders but I never saw any change in the Z signal. I think my .hal is compliant. Could there be a connection subtlety on the 7i96s card?

excellent! glad you got it sorted! now you should be future proofed too for 2.10 when it is officially released as stable!

I figured it out, I had to modify the math a bit (along with adding the stglue and RANDOM_TOOLCHANGER = 0 changes) but now it works perfectly. Not sure if it is something inherent to the Mazak index style ATC or if I had something wrong from the start when I used the sample configs as a reference to write the config for my machine. I just pushed the changes to my github attached above. I'll be sure to keep it public when I clean everything up and merge it to my main repo.

Thanks for the help!

you can also ask on the probe basic facebook group chat, just join here, the group chat would allow realtime communication and video sharing to better help understand whats going on:

www.facebook.com/share/g/1E9TtGtPQv/

I have only ever actually received 2 notification emails from the forum since I started this thread (the last one was on March 19, 2025). Maybe the problem is g-mail? But I've mostly given up. Yes the check box to be notified at the bottom of my replay is checked, and no it hasn't worked for this thread or any of the dozens of others I'm subscribed to.

sounds like some math is going wrong somewhere. or a direction is wrong in one of your macros. without knowing more about the amchine its directions etc its hard to determine just looking over your code.

one thing i did notice is you didn't have

[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool_inch.tbl
RANDOM_TOOLCHANGER = 0 <<<<<<

Sorry, I've been busy and hadn't checked the forum for a couple of weeks.

Are you using servos or closed loop steppers? if servos, how are they commanded? Are you using encoder feedback to Linuxcnc? What kind of tuning needs done to them yet? Is this a new machine or a retrofit of an older one? Are you sure all of the mechanics are in good order (no backlash, low compliance)

Have you decided exactly how you want to configure the machine and it's kinematics? is the Z and W heads completely independent on their own X axis so the configuration will be XYZ and UYW? Or will the configuration be more of an XYZ and XYW with merely u controlling the distance between the Z and W axis. (t is possible to have X1 and X2 be fully independant joints but still configure them such that the normally move together with the X command, but U commands control the distance.

I can try to help you as much as I can over the forum here.

I applied the stdglue change, no change. From what I can tell, the controller/Carousel module is losing count of the current pocket, mostly when running store tool in carousel. Is the logic built into the stglude to reflect the current pocket from probe basic back to the controller? Or is that something that the end user has to do when configuring it to their machine?

It looks like some people use a M68 E Q command to update motion.analog-out-00 => conv-float-s32.0.in and change the s32 count.

I just wasn't sure if the logic was already there inside of probe basic to do this and I didn't have something configured correctly, or if it is logic that has to be added.