I disassembled one last night and the confirmed what you said. I took a look on Aliexpress and it appears that 200mm and 300mm stepper motors (ie. T8 lead screws attached) are fairly inexpensive, so no need to remove screw from the motor. Just need to confirm the model with the correct motor height (40mm ) and pitch.
Cheers!
FYI I am using this motor to build a portable macro photography rig.

I disassembled one last night and the confirmed what you said. I took a look on Aliexpress and it appears that 200mm and 300mm stepper motors (ie. T8 lead screws attached) are fairly inexpensive, so no need to remove screw from the motor. Just need to confirm the model with the correct motor height (40mm ) and pitch.
Cheers!
FYI I am using this motor to build a portable macro photography rig.

Thanks for the reply. Actually that has not been my experience with stepper motors. As long as you know the pitch (mm/rev) and the step count (steps/mm) I have found them to be pretty accurate.
I will be able to deal with the this by mapping the values to correct, but I was hoping this would at least be consistent otherwise each has to be manually calibrated.
I really like this little stepper motor, especially for the price. It also looks like it could be easily modified to extend the length by replacing the 1515 aluminum extrusions and the screw rod.

Hi, there is no documentation on the feed speed command. (ID???:F????\r\n).
Does anybody know what the default value is and what speed it represents?
On a side note , I have determined that there seems to be a discrepancy between the mm values entered using the Move (:X) command and the actual distance travelled on my unit. If I enter ID123:X40.0\r\n the motor travels to 50 mm (for example).That is 50mm from the position it returns to when you send Find Zero. Have others found this to be the case?
Is this consistent for each 6060-PUSH unit?
Thanks in advance!

@felmue Thanks for you fast reply Felix!
I will.

I just bought some 4-Relay Units (i2C) and I found that there are two operating modes; synchronous and asynchronous. The documentation does not describe the difference between these modes except to say, don't use asynchronous!

from documentation - UIFlow functions
"Set LED and relay mode
Synchronize
LED and relay ON/OFF are synchronized.
Asynchronous
LED and relay ON/OFF are asynchronous."

1. Can anybody shed light on what they are referring to? Does this mean that in asynchronous mode you can select the LED and Relay separately?? Or does it refer to the settings of the individual relay values?

from documentation - RELAY control Reg 0x11
"Note:The relay can only be controlled in synchronous mode, if the relay is controlled in asynchronous mode, it will not work."
2. If we are not supposed to use the asynchronous mode the why the heck do they let you select it???

Thanks in advance!

So I tried help("modules") to get the list of all modules. Turns out there is a reference to "_uasyncio" but the object looks like it is only a shell of a module. It has references to a Task class and TaskQueue class but no functions. An attempt to use _uasyncio confirms this. Sigh.

@ajb2k3 Thanks for your assistance. I do know how to use the dir and help functions, but I have looked in m5stack and machine and cannot locate them (even drilling down modules are in m5stack and machine.)

@ajb2k3 thank you. how does one access descriptions of the contents of the firmware that are accessible through micropython? I have tried importing (i.e. import uasyncio fails)

V1.9.8
Sorry for the delay in responding . Running on Core

Version v1.9.8 Core

The following code will cause a syntax error when run

x = "#"
print(x)

I guess the interpreter thinks the # string is the start of a comment.

Why did I need this? I am trying to send the GRBL command "$#" to the GRBL stepmotor module. (which is one of the commands it accepts).

Workaround

x=b'\x23'.decode()
grbl.g_code('$'+x)