RepRapFirmware 3.01-beta2 released
-
It's at https://github.com/dc42/RepRapFirmware/releases/tag/3.01-beta2. The change summary is at https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md.
-
Seems to be working fine with a stand-alone Duet3.
-
Loaded on a SBC + Duet3 6HC + 2 x 3HC. Haven't printed yet, but a few quick tests looked fine.
-
Tried RF 3.01-beta2 with the same problems
homeall.g -> OK (also X without errors?)
homex.g -> error
homey.g -> OK
homez.g -> OK
Only homex.g fails, he drives on it once, takes off and stops, the slower approach is missing. If you press again, the following error occurs:
G28 X
Error: G0 / G1: insufficient axes homedI've shared my macros here before
https://forum.duet3d.com/topic/13630/reprapfirmware-3-0-is-released/119?_=1580039563223greetings
-
Where can I look up which number corresponds to which status?
echo state.status
outputs only one numberThank you for many new opportunities
-
@zerspaner_gerd said in RepRapFirmware 3.01-beta2 released:
Where can I look up which number corresponds to which status?
echo state.status
outputs only one numberThank you for many new opportunities
There's a bug, try the internal build at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 instead.
-
Having trouble getting my delta to home correctly after update to 3.0. I have also tried 3.01-beta2. I have performed a successful upgrade on my cartesian machine.
My delta keeps adding the prehomed Z height value to the new homed height. It is almost exactly double the actual machine height. This triggers an "Error: G0/G1: target position not reachable from current position".
This machine has a smart effector and a duet wifi. At first i thought it might be because of the config override. After playing around with this a few times I think I get it to work and then it reverts back the next time I home it.
I removed M501 from the config.g file and pasted the override settings into the main config. Interestingly enough if I send an M502 the machine will work for a homing cycle.
Anyone seen this before?
-
From your config.g:
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstopEndstops on a delta are at the high end, so you need X2 not X1. Same for Y and Z.
-
Thank you dc42. I feel so stupid now...