New firmware 1.21RC3 available
-
Okay, well that's simple enough. That was though just a minor issue, its the fact that RC3 doesn't seem to work on corexy that was the main event for me.
Please provide more details of why RC3 didn't work for you, along with any relevant GCode files.
Hi David sorry scroll up a bit I provided a report and an M122. Corexy and attempting to print a SlicerPE file, so same issue others have had, downgrading just FW fixed it. Deltas working perfectly on rc3.
I use SlicerPE and no problems on my CoreXY.
-
I've tried it out, both S3D and Slic3r PE files work on my delta (it gives the "Error: Attempt to seek on a non-open file." popup at the end of the print though), while neither would print on the CoreXY. The printer executes the G28 command and stops with the error message. The same result repeats regardless of the object in question, I'll try to attach a sample G-code here.
; generated by Slic3r Prusa Edition 1.39.1-beta1-prusa3d-win64 on 2018-03-06 at 18:25:08 ; ; external perimeters extrusion width = 0.45mm ; perimeters extrusion width = 0.45mm ; infill extrusion width = 0.45mm ; solid infill extrusion width = 0.45mm ; top infill extrusion width = 0.40mm ; first layer extrusion width = 0.45mm M107 M106 P1 S0.1 I0 F500 H-1; M140 S110; G28 X Y G1 X150 Y100 M190 S110; G30 X150 Y100 G1 X150 Y100 Z25 M104 S267 T0; M109 S267 T0; M106 P1 S0.2 I0 F500 H-1; ; Filament gcode ;M290 S0.05 G21 ; set units to millimeters G90 ; use absolute coordinates M83 ; use relative distances for extrusion G1 Z0.300 F10500.000 G1 E-1.20000 F2280.00000 G1 X125.225 Y99.725 F10500.000 G1 E1.20000 F2280.00000 G1 F600 G1 X174.775 Y99.725 E2.38319 G1 X174.775 Y100.275 E0.02645 G1 X125.225 Y100.275 E2.38319 G1 X125.225 Y99.785 E0.02357 G1 X125.625 Y99.726 F10500.000 G1 X125.418 Y100.000 F10500.000 G1 F600 G1 X174.582 Y100.000 E1.00800 G1 E-1.20000 F2280.00000 ; Filament-specific end gcode ;END gcode for filament M104 S0 ; turn off extruder M140 S0 ; turn off bed M107; Turn off fans G91 G1 Z50 ; lift z G90 ;G28 Z; home all axes M84 ; disable motors M106 P1 S0.5 I0 F500 H-1; dim lights -
I don't know if this was fixed in RC3 or not, but I just noticed the following issue in RC2:
When setting up a z-probe with P5 (It's a BLtouch) A3 (probe each location up to 3 times) and B1 (turn off bed heater while probing), the heater gets turned off for the FIRST of multi-tap probes, but not subsequent multi-tap probes.
So, assuming a M558 of:
M558 P5 X0 Y0 Z1 H5 F100 T4000 A3 B1
and a bed.g containing the following:
G30 P0 X1.1 Y-69.2 Z-99999
G30 P1 X-50 Y65.5 Z-99999
G30 P2 X49 Y65.5 Z-99999 S3(and the manual levelling assistant configured.)
In each of the above probes, the heater is turned off for the FIRST test in each location, but the heater is turned back on (and stays on) for the SECOND probe. (My probes are apparently within 0.03 of each other, as I don't see a third probe in any location.)
Thanks for posting this - I wasnt sure how to use the Bed heat on/off within M558. Also I wasnt aware that multitap was in the RC2 version. Im on RC3 and needed to change the P parameter of Probe MODE to 9 [ P9 ] for RC3 as per the notes. I will test out RC3 with the bed on/off settings and report if RC3 is working as inted for this feature
-
Thanks for posting this - I wasnt sure how to use the Bed heat on/off within M558. Also I wasnt aware that multitap was in the RC2 version. Im on RC3 and needed to change the P parameter of Probe MODE to 9 [ P9 ] for RC3 as per the notes. I will test out RC3 with the bed on/off settings and report if RC3 is working as inted for this feature
Sorry to quote myself - but … I just tried this and I dont see any changes in the DWC interface indicating to me the heated bed is getting shut off between probes ... What are you using to monitor that activity ...
-
I don't know if this was fixed in RC3 or not, but I just noticed the following issue in RC2:
When setting up a z-probe with P5 (It's a BLtouch) A3 (probe each location up to 3 times) and B1 (turn off bed heater while probing), the heater gets turned off for the FIRST of multi-tap probes, but not subsequent multi-tap probes.
So, assuming a M558 of:
M558 P5 X0 Y0 Z1 H5 F100 T4000 A3 B1
and a bed.g containing the following:
G30 P0 X1.1 Y-69.2 Z-99999
G30 P1 X-50 Y65.5 Z-99999
G30 P2 X49 Y65.5 Z-99999 S3(and the manual levelling assistant configured.)
In each of the above probes, the heater is turned off for the FIRST test in each location, but the heater is turned back on (and stays on) for the SECOND probe. (My probes are apparently within 0.03 of each other, as I don't see a third probe in any location.)
I believe that was fixed in RC3 along with the other multi-touch issues, but please check.
-
Me again, tried 1.21rc3 and found CoreXZ isnt moving along its "planes" anymore its as though ive left it in cartesian mode.
only change was updating from v1.20 to 1.21rc3 and changed my z movements with S2 parameter.Gav
-
You won't see any indications in DWC because it is a temporary suspension of heating. However, all the heater LEDs on the Duet will go off; and any heater LEDs on the hot end (e.g. Smart Effector) or bed heater will go off too.
-
Me again, tried 1.21rc3 and found CoreXZ isnt moving along its "planes" anymore its as though ive left it in cartesian mode.
only change was updating from v1.20 to 1.21rc3 and changed my z movements with S2 parameter.Gav
OK, I see the problem. S2 invokes direct motor movement; but on a CoreXZ printer, you need to move both the X and Z motors to move Z. Here are two possible workarounds:
1. As you don't have a Z endstop switch, make sure you say so in config.g (Z0 in the M574 command), then you can use S1 instead of S2 in that G1 Z command;
2. Instead of G1 S2 Znn use G1 S2 Xnn Znn to get the correct Z movement (one of them may need to be negative, I can't remember).
I have been considering introducing a new mode S4 for G1 commands. This would mean:
1. Movement is allowed regardless of whether axes have been homed (like S1, S2 and S3);
2. Axis mapping is not performed (like S1, S2 and S3);
3. Coordinates are always interpreted in Cartesian space;
4. On Delta and SCARA printers, X and Y movements using S4 are not allowed;
5. Coordinates are always interpreted as relative (not sure about this one, because absolute S4 movements might possibly be useful on CoreXYU and CoreXYUV machines). -
1. As you don't have a Z endstop switch, make sure you say so in config.g (Z0 in the M574 command), then you can use S1 instead of S2 in that G1 Z command;
so this has kind of worked, but having a bltouch probe thats defined as M574 Z2 right? whats the correct way to define a z probe but no endstop?
-
As long as you are using G30 to do Z homing in homez.g and homeall.g (not G1 S1 Znnn moves), M574 Z0 will work just fine. That says you have a Z probe and no endstop.
-
ended up using method 2, working as expected now
apart from the z not homed before z as in other thread, im almost there 
thanks again
-
I don't know if this was fixed in RC3 or not, but I just noticed the following issue in RC2:
…
In each of the above probes, the heater is turned off for the FIRST test in each location, but the heater is turned back on (and stays on) for the SECOND probe. (My probes are apparently within 0.03 of each other, as I don't see a third probe in any location.)I believe that was fixed in RC3 along with the other multi-touch issues, but please check.
I need to compile a new PanelDue firmware that sends S2 along with G1 movement commands before I can use RC3. (…and I haven't even begun the process of setting up a build environment for paneldue.) Hopefully, someone else will be able to verify on RC3 sooner.
-
Maybe there should be some kind of gcode command to enable safe movement protection
I'd think it could have a few parameters
S0 - disabled, no movement locks
S1 - enabled, no movement until homed
S2 - All moves have S1 enabled until homed
S3 - Z axis prevented from moving down until homedor something
-
I don't know if this was fixed in RC3 or not…
When setting up a z-probe with P5 (It's a BLtouch) A3 (probe each location up to 3 times) and B1 (turn off bed heater while probing), the heater gets turned off for the FIRST of multi-tap probes, but not subsequent multi-tap probes.
I believe that was fixed in RC3 along with the other multi-touch issues, but please check.
I can confirm that this IS fixed in RC3 for G30 probes (multi-tap or otherwise.) However, if the probe is used as an endstop (G1 S1), the heater is not turned off. (I'm still using my BLTouch as a "P5" instead of a "P9" if that matters.)
Given the following two gcode lines, the FIRST one does not turn off the heater. The second one DOES turn the heater off.
[[language]] G1 S1 Z-155 F6000 ; heater isn't turned off G30 ; heater IS turned off -
In regards to the new S2 requirement for unhomed G1 moves on non-Delta printers:
I was making code changes in PanelDue to force the S2 parameter to always be sent when I decided to read the duet gcode wiki and see what side effects it might have. There I found out that "G1 S2" has a completely different meaning on delta printers when compared to non-delta printers. Here's my understanding (and if I'm wrong, please correct me):
A normal "G1" on a cartesian printer moves the axis specified. So "G1 X" moves the X stepper motor, etc. Passing a "S" parameter (S1, S2, etc) doesn't change that.
On a delta, however, a normal "G1" actually often ends up moving THREE different stepper motors in order to make a straight horizontal or vertical move. So, it's actually more of a "virtual" move in that the duet board has to figure out which steppers have to move (and in which direction) to move the print head a given distance on a single line. (Making it really confusing, each stepper motor is labeled X, Y, or Z - but those labels have nothing to do with straight lines in the printed space.)
On those deltas, however, passing a "S" parameter completely changes the meaning of the G1 command. If S1, S2, or S3 is passed to G1 on a delta, the G1 command doesn't mean to move the print head a given distance on a given line, but instead means to move a specific stepper motor (remember that each motor has a X/Y/Z label?) a given distance. So, while "G1 X10" on a delta might move the print head 10mm to the right, "G1 S2 X10" will actually cause the print head to move in 3 dimensions (slightly down and either left or right depending on which stepper motor is labeled "X".)
Why does all this matter?
Because now I'm more opposed to this change as it's currently implemented in RC3. It means that the same VALID command on two different printers will have completely different end results. I realize that this situation already exists with "G1 S1", but at least in that case they both mean "detect endstop" and hopefully they're only used for that. In the case of "G1 S2", which is now valid for both printer types, one printer will "move in cartesian space" and the other will "move in… delta space?" (not sure what the proper term would be.)
If there's really some good reason to not allow un-homed moves (and please share it with those of us testing the changes), then at least add a new non-delta S parameter for moving when not homed on cartesian (and corexy) printers where X is always X, Y is always Y, and Z is always Z. Perhaps "S4." On delta's, the parameter would be completely ignored and treated as if no S parameter was passed.
One other reason: It makes it easier for me to add a parameter to the paneldue's "jog" buttons without wondering what kind of problems I'd introduce on a delta machine.
-
1. Thanks for confirming the the heater is turned off correctly when doing bed probes in RC3.
2. G1 S1 Z moves should only be done if you are using an endstop switch for homing Z. To home using a Z probe, use G30.
3. Please explain why you consider it such a problem that you can no longer use the Move buttons in DWC/PanelDue before the corresponding axes have been homed. This has always been the case for Delta and SCARA printers, is the default for some other firmwares already, and is the only sensible default for a CNC machine.
-
Please can those of you running 1.21RC4 on a Duet WiFi try upgrading DuetWiFiServer to 1.21RC4. I need feedback on this version asap because a deadline is approaching.
-
DC42:
Again, in case of failure or emergency there is no way to quickly move an axis after a reset.
I was stuck twice now since the new RC3 with a hot nozzle in either my bed or a printed part.
Immediate reaction is to hit the reset button to stop all further movements.
Now all axis are unhomed, the nozzle is melting away my part and bed surface - AND I CAN'T MOVE AWAY!What would you recommend in such a way?
Please provide an override, aka "Allow unhomed moves" M-code, and provide a button/checkbox on DWC + PanelDue to allow unhomed moves!
-
Please can those of you running 1.21RC4 on a Duet WiFi try upgrading DuetWiFiServer to 1.21RC4. I need feedback on this version asap because a deadline is approaching.
I've updated the wifi server in my home printer from my office and it never came back, so I'm assuming the issue with my AP is still there. I can restart it (it's connected to a wifi plug) but I won't so I can check the error message in the PanelDue, but I assume is the usual "incorrect password" message.
Regards
-
What would you recommend in such a way?
Please provide an override, aka "Allow unhomed moves" M-code, and provide a button/checkbox on DWC + PanelDue to allow unhomed moves!
I haven't upgraded yet but I agree it's a bit of a pain. I can also see why some people might want to have that feature though. Ideally having the ability to enable or disable the "no moving until homed" feature, say in config.g would be good. Otherwise, I guess all we can do is create a macro to move Z using S2. Something like G91, G1 Z10 S2 Fnnn, G90 and call it say "Emergency Z move" or some such.
