I loaded both files for version 1.05. When I tried to move the M4 the fan came on but no movement. I powered down and did the Retract extend Tension dance. Still not moving. I did notice the BL belt was loose both times, but the M4 reported it was within spec.
I then loaded the V1.04 firmware only. Did the RET dance, all belts tightened, and I could move the M4 as per usual.
Maslow-serial (23).log (3.6 KB)
1 Like
Further info:
I have reloaded the latest firmware and no problems moving unless
If I do the release tension, then do the retract, extend, Tension without powering the M4 off, the Arrow keys, home key etc don’t actually move the M4, although the x & y numbers move as expected. Same thing with the earlier v1.04.1
Can someone confirm this please
3 Likes
Hmmm interesting! That sounds like a bug in how the state machine is handling something. For some reason it’s not telling the machine that it can move even though it is in the right state. I will look into it. Thank you for the clear description of how to replicate it
Same here - thanks ian_ab for describing it succinctly, I see the same behavior on my M4, though by now so many issues around the movements, calibration and location that lost track of whether this actually happens all the time. Feels like it might be an issue related to position tracking; After succesful calibration, I tried to run an actual simple g-code pattern, but after moving about 50cm towards the first cutting position, the tool reported ‘Position error on Top Right axis exceeded 15mm while running’, repeated several times, finally triggering an E-stop. @bar fyi.
1 Like
If you go back to 1.04 does the issue go away?
Hi Bar, I have reloaded both files for V1.04 and I no longer see the problem. I did have it when I loaded V1.04.1 (I only updated the firmware with that after uploading V1.05). Also when I tried with V1.05, I noticed the BL belt was slack after tensioning. This also does not appear to happen on V1.04. In summary how I tested:
Loaded V1.04 files
Powered off the M4
Powered on the M4 & connected via Microsoft Edge
Did the RET dance.
Moved the M4 via arrow buttons & Home button
Released Tension
Did the RET dance without powering M4 off
was able to move the M4 using arrow and home buttons
I wasn’t able to replicate this issue, but in digging into the code I did find a better way to do some things which will hopefully fix the behavior that you were seeing in the next release.
If you have a chance to give these a try and let me know if you are still seeing the same behavior I would love the feedback!
index.html.gz (117.6 KB)
firmware.bin (1.9 MB)
Sent you a message with some anomalies, did a config again from power on and got a more believable Fitness measure, will see if the problem reemerges.
1 Like
Haven’t checked to see if same happens but have found another related problem. If I try to reset the Zero axis from the Setup menu Set Z-Stop the fan starts and nothing else happens, Z-Stop is not set. On returning to the main menu and selecting an arrow or home key the following popup is displayed and the arrow keys, home etc do nothing.
It is still possible to run a job successfully.
I have great admiration for you juggling all these problems while still getting all the other things you have to do.
1 Like
Only tells the machine that you think you have bottomed out the Z-Axis.
You need to first move the machine all of the way down (if you have a bit in your router you’ll have to remove it first) and then once it can’t go any further click the Set Z-Stop button.
Note that this is not Z-Home, which you would normally set at the surface level of the material you are cutting.
I understand the difference between Z-Stop and Z-Home.
I was trying to set the Zero-Stop, I had raised the Z axis too high and it had messed up its Absolute Zero position. I did not have a bit in while trying this. The point is it wouldn’t set the Zero position but just started the fan and did not return any indication. Then when I used the arrow keys the fan went off and that message came up. Could not Jog the machine, but I could run a script.
I can partly confirm this. The z-stop is being set, but the fan is also staying on.
I’ll figure out what is going on!
Edit: In case anyone is curious you can confirm that the z-stop has been set by checking the value of Zm here:
The fan not turning off after setting the z-home position will be fixed in today’s firmware update. Thank you for pointing out the issue!