RepRapFirmware 3.0
-
@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? -
which board and which probe?
@caveman said in RepRapFirmware 3.0:
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? -
duet meastro and original probe
-
Maestro was discussed mid may if you scroll up, not familar with what probe is original for anycubic, but hopefully the pin definition earlier in this thread will help.
-
@dc42 So what does have to change if z probe is connected to endstop before?
-
@caveman said in RepRapFirmware 3.0:
@dc42 So what does have to change if z probe is connected to endstop before?
Use the C parameter ni the m558 command to specify that endstop pin. See https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M558.
-
Ok, I've updated to 3.0 to run my weird cnc contraption. I'm a bit stuck on how to set it up. I have two Y motors and endstops, z, x and e (which is actually a tangential cutter but rotates based on E moves). I have Y hooked up to the Z driver and mapped as M584 Y0 Z1 X2 E3. Does this make sense given I have two endstops and motors on that axis? Should I be defining the second y motor as its own axis to use an second endstop? What should my M574 look like?
As always, appreciate any help!
-
@clearlynotstef said in RepRapFirmware 3.0:
I have Y hooked up to the Z driver and mapped as M584 Y0 Z1 X2 E3.
Seems off me? "Z driver" should be driver number 2, so you should probably have Y2 in there. Are you connecting both motors to the same driver output? If not you need something like Y2:1 or Y2 U1 (if the two Y motors are connected to the Y and Z drivers which ar drivers 1 and 2 respectively) ... or so i think at least.
If you clarify that bit I'm sure someone can help you with the M574
-
@bearer that's what I guess I'm trying to figure out. I currently have both Y motors hooked up to driver 0 (typically used for Z) so I can drive them off of the same driver without merging cables. This means I can't drive one without driving the other, which I guess means the best case scenario with two end stops is smashing one side into the endstop until the other catches up and hits the other endstop. Given I have an extra driver still, maybe I should drive each y motor off its own driver with it's own endstop, but still define both drivers as being the y axis? Not sure how to define the motors and end stops in either scenario on 3.0!
-
@clearlynotstef said in RepRapFirmware 3.0:
I currently have both Y motors hooked up to driver 0 (typically used for Z)
Which board are you using?
-
@bearer duet 2 Wi-Fi
-
@clearlynotstef said in RepRapFirmware 3.0:
@bearer duet 2 Wi-Fi
Then maybe you should wait for someone else to tell you that driver 0 is not the one labeled for Z as you seem to ignore me telling you that ... because you're not going to have much success until you do.