RepRapFirmware 3.0
-
You are right, it's not adding the trigger height to the dive height. I will fix this in the next build. Thanks for reporting it.
-
At least I'm not going mad. Thanks
-
@jay_s_uk, please try the new binary at https://www.dropbox.com/s/zfv4p7dr2ycmjzd/Duet2CombinedFirmware.bin?dl=0.
-
@dc42 thats spot on
-
-
I also now tried out RRF3 and first very obvious observation: Fan PWM inversion does not work. I do have
; Fans M950 F0 P"fan0" Q10 ; Fan 0 has a low PWM frequency of only 10Hz M950 F1 P"!fan1" Q25000 ; Fan 1 has a high PWM frequency of 25kHz and is inverted M950 F2 P"!fan2" Q25000 ; Fan 2 has a high PWM frequency of 25kHz and is inverted [...] M106 P0 S0 H-1 C"Part Cooling Fan" ; Set fan 0 value. Thermostatic control is turned off M106 P1 S1 L0.7 H1 T45:220 C"Hotend Fan" ; Set fan 1 value. Thermostatic control is turned on M106 P2 S0 H-1 C"Hardware Fan" ; Set fan 2 value. Thermostatic control is turned off
where the first fan is a regular 3-wire fan but the other two are 4-wire PWM controlled fans and both spin at 100% speed after startup (I know fan 1 is thermostatic but the hotend is at room temp). Unless I make fan 1 non-thermostatic I have no way of stopping it (I stopped fan 2 by issuing
M106 P2 S1
).EDIT: Second observation:
I have two independent Z steppers. Also each stepper has a separate endstop switch. Homing Z works fine with both steppers running until their appropriate switch is triggered. After that I un-hide W axis (right of the two Z steppers) and apply a correction since the switches are not perfectly aligned. So far this works. What does not work isM119
for W axis. It will always show that the endstop is not triggered even though at the same time it shows triggered for Z.M584 X0 Y1 Z2:3 W3 E4 ; Assign one driver X, Y and E and two to Z [...] M574 Z1 S1 P"zstop+e0stop" ; Set active high endstop at low end on Z with two separate endstops M574 W1 S1 P"e0stop" ; Set active high endstop at low end on W
Since I never use W axis outside of
homez.g
and don't even have ahomew.g
for me this is purely cosmetical - but their are probably other users that depend on this working correctly. -
@wilriker said in RepRapFirmware 3.0:
I also now tried out RRF3 and first very obvious observation: Fan PWM inversion does not work. I do have
; Fans
M950 F0 P"fan0" Q10 ; Fan 0 has a low PWM frequency of only 10Hz
M950 F1 P"!fan1" Q25000 ; Fan 1 has a high PWM frequency of 25kHz and is inverted
M950 F2 P"!fan2" Q25000 ; Fan 2 has a high PWM frequency of 25kHz and is inverted
[...]
M106 P0 S0 H-1 C"Part Cooling Fan" ; Set fan 0 value. Thermostatic control is turned off
M106 P1 S1 L0.7 H1 T45:220 C"Hotend Fan" ; Set fan 1 value. Thermostatic control is turned on
M106 P2 S0 H-1 C"Hardware Fan" ; Set fan 2 value. Thermostatic control is turned offThe pin name parameter in the M950 command (and most other commands that don't take axis parameters) is C not P.
What does not work is M119 for W axis. It will always show that the endstop is not triggered even though at the same time it shows triggered for Z.
You can't currently assign the same endstop input to more than one axis. So the M574 command to assign e0stop to W is failing. If you run that command from the console you will get an error message.
-
@dc42 said in RepRapFirmware 3.0:
The pin name parameter in the M950 command (and most other commands that don't take axis parameters) is C not P.
In that case the example code for
M106
in the RRF3 wiki is wrong (I checkedM950
has it right).You can't currently assign the same endstop input to more than one axis. So the M574 command to assign e0stop to W is failing. If you run that command from the console you will get an error message.
As I said no real problem for me but thanks for clarifying.
-
I have corrected the example.
-
@dc42 Thanks. Just wanted to do it myself only to find it's been done already.
-
Found another discrepancy in the wiki. In the description for
M950 C
it says to enable pull-up resistor^
has to be trailing. In Pin Name Format section below it says the^
should appear in front of the pin name.Again not relevant for me but others might stumble across that one.
-
@wilriker said in RepRapFirmware 3.0:
Found another discrepancy in the wiki. In the description for
M950 C
it says to enable pull-up resistor^
has to be trailing. In Pin Name Format section below it says the^
should appear in front of the pin name.Again not relevant for me but others might stumble across that one.
Thanks, I've corrected that.
-
I am testing the newly added function M581.
How would you ignore output, in Reprap 2.03 this was done with S-1, but there is no S parameter available.
Thanks -
@t9 said in RepRapFirmware 3.0:
I am testing the newly added function M581.
How would you ignore output, in Reprap 2.03 this was done with S-1, but there is no S parameter available.
ThanksUse
M280M581 Tn P"nil" to select no input ports. -
Thanks, I found that M581 Tn P"nil" works. Im not sure if that's what you meant, rather than M280
-
Latest RRF3 builds are now at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.
-
Hi,
I´m just playing around with the new version.
One thing I stmbled across is M558
How do I set up a second probe?I tried:
M558 K1 P5 C"!e0stop" H5 F120 T300
M585 Z100 F600 P1 S0but I get the error:
"M558 invalid z probe index"I can change K1 and P1 to 0 and it works, so there might be a problem with additional probes?
thanks
Moosi -
@moosi said in RepRapFirmware 3.0:
Hi,
I´m just playing around with the new version.
One thing I stmbled across is M558
How do I set up a second probe?I tried:
M558 K1 P5 C"!e0stop" H5 F120 T300
M585 Z100 F600 P1 S0but I get the error:
"M558 invalid z probe index"I can change K1 and P1 to 0 and it works, so there might be a problem with additional probes?
You are right, it wasn't working. Try the new binary that I've just put at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.
-
Thanks, that was fast
It is working now. Not exactly as expected, but I think it is my fault and I need to dive deeper into the configs. -
How to setup probe on anycubic linear plus? In 2.xx probe worked fine. In 3.xx Probe is not even registered when connected.
Am I missing something?