New experimental firmware 1.20beta2
-
I'm getting wifi connection issues after upgrading to the latest version. When using DuetWiFiServer 1.20beta2 the printer becomes unreachable via wifi in around 1 minute after starting it. M122 says wifi sleep mode: modem
When using DuetWiFiServer 1.20alpha1 it seems to work fine; M122 says wifi sleep mode: unknown -
After updating my CoreXY can't home. At first it reported X-62Y-123 (or similar), at the second try it reported X0Y-0.4 and now it reports X-0.0Y-100.3 after trying to home X and Y. It also reports
Error: Homing failed
These are in my config.g
M574 X1 Y1 Z0 S0 M208 X-11 Y-0.75 Z0 S1 M208 X200 Y200 Z240 S0 Could this be because of the stall detection feature? I have not configured it, so I was thinking that it will not be used…?
-
The "Homing failed" message has nothing to do with the stall detection feature. What it means is that it ran a homing file in response to the homing command you gave it, but the same axes were flagged as not homed after running the file as before.
Were you trying to home all, or specific axes? Which axes show up in DWC as homed, before and after sending the command? Have you created any additional axes using M584?
-
Now I am able to use Z and B for my Z lead screws – homes correctly -- just did a quick test -- swapped U back to my 2nd Y gantry. Now B is use appropriately. So far outside of one freeze up where it looks like it got confused how long moves take after I was move Z up and down after machine was homed -- it's been working.
PS -- any use case instructions for M585 .. the docs are not clear how to apply it. -
Were you trying to home all, or specific axes? Which axes show up in DWC as homed, before and after sending the command? Have you created any additional axes using M584?
First I did home all, then I quickly hit the emergency stop button, because it tried to move waaay out of the printer frame, as it was reporting Y-169 and my Z-homing point is at X100Y100. Then I tried homing X and Y seperately. Directly they were marked as 'not homed' (all buttons orange). I only have X Y Z (and E).
-
Were you trying to home all, or specific axes? Which axes show up in DWC as homed, before and after sending the command? Have you created any additional axes using M584?
First I did home all, then I quickly hit the emergency stop button, because it tried to move waaay out of the printer frame, as it was reporting Y-169 and my Z-homing point is at X100Y100. Then I tried homing X and Y seperately. Directly they were marked as 'not homed' (all buttons orange). I only have X Y Z (and E).
At which point(s) did you get the "Homing failed" message?
The buttons will be marked as "not homed" when you ask to home those axes. They should change to "homed" status as each one is completed.
-
At which point(s) did you get the "Homing failed" message?
The buttons will be marked as "not homed" when you ask to home those axes. They should change to "homed" status as each one is completed.The message appeared directly after the homing procedure, the buttons did not change.
Here is my homex.g
; Lift Z relative to current position G91 G1 Z5 F12000 G90 ; Move quickly to X axis endstop and stop there (first pass) G1 X-205 F1800 S1 ; Go back a few mm G91 G1 X5 F12000 G90 ; Move slowly to X axis endstop once more (second pass) G1 X-205 F360 S1 ; Lower Z again G91 G1 Z-5 F12000 G90 homey.g is the same, just with X. I think I didn't change anything after generating it with the configurator. I certainly did not change anything here after the update.
-
After updating my CoreXY can't home. At first it reported X-62Y-123 (or similar), at the second try it reported X0Y-0.4 and now it reports X-0.0Y-100.3 after trying to home X and Y. It also reports
Error: Homing failed
These are in my config.g
M574 X1 Y1 Z0 S0 M208 X-11 Y-0.75 Z0 S1 M208 X200 Y200 Z240 S0 Could this be because of the stall detection feature? I have not configured it, so I was thinking that it will not be used…?
I have the same homing issue on coreXY. After some digging around, I think that the issue creeps in the code where the endstops are checked.
In DDA.cpp around line 1270 the function is returned and part just below it which sets the homed axes is never invoked on a platform that shares drives:if (endStopsToCheck == 0 || kin.QueryTerminateHomingMove(drive)) { MoveAborted(); // no more endstops to check, or this axis uses shared motors, so stop the entire move return; } I may be smoking something, but that is the only location that I could find where the AxesHomed bits are set. After removing the return, the axes homed like before (barring everything else that might now be broken
) -
You are right, it's a bug. I shouldn't have added the 'return' at line 1274. I'll release a new beta tomorrow. In the meantime, CoreXY users should revert to version 1.20beta1.
-
Is anyone seeing any weird behavior with controlling heaters?
on fresh power up both the hot end and the bed heaters are set to "off." When I click them in DWC I can cycle through to active, but then it goes into "changing tool" mode and I can't do anything until it hits target temp…?
-
That's normal behaviour if you have tool change files that wait for your tools to reach temperature.
-
That's normal behaviour if you have tool change files that wait for your tools to reach temperature.
Ah, I found it! I think these must have been created by the RRF configurator. I recently used it to redo all of my config files fresh in an attempt to solve my wifi issues. Thanks David.
-
I think I figured out an issue. It has something to do with how the Duet powers up and initializes. If it powers and hits some race condition or if I try to home it before it finishes some part of the startup routine – which is not clear when it does, it doesn't home correctly, if I wait a couple of minutes after power up. It appears to work properly.
Is there a way to add something to end config.g to print a message to the console -- Ready or something like that? -
Additional, i'm not able to print Files with Spaces or Brackets in the Filename anymore.
They upload just fine, but they are not able to print cause they will not be found. The Filename is not the same anymore.
Uploaded a File Test Cube (0.4).gcode
Trying to print:
[[language]] M32 Test Cube (0.4).gcode Error: M32: GCode file "Test Cube .gcode" not found As you can see, eveything after ( will be cutted. Even if the Space after Cube is visible, no Special-Character can be used.
-
The open-bracket character starts a comment in standard CNC gcode, so filenames with brackets in them should never have been allowed - just like filenames with semicolons in them. In the 1.20release I intend to allow filenames in commands such as M32 to have double quotation marks around them, which will provide a way round this.
-
I've just released 1.20beta3 which fixes a number of bugs in 1.20beta2. See the whats_new file for details.
-
The open-bracket character starts a comment in standard CNC gcode, so filenames with brackets in them should never have been allowed - just like filenames with semicolons in them. In the 1.20release I intend to allow filenames in commands such as M32 to have double quotation marks around them, which will provide a way round this.
Ah, was not aware of this. Sorry if i've overseen this.
Will test beta3 now
Cheers
MoS-tekknix -
Btw the standard I am referring to is http://ws680.nist.gov/publication/get_pdf.cfm?pub_id=823374 and section 3.3.4 describes comments. We have increasing interest in using Duets to control CNC machines, so I am striving for a greater compatibility with CNC gcode, without having to use a separate build of the firmware.
-
Confirmed the Error is gone for config-override.g
Thanks, waiting for Final of it
But, i hope that we see always an ongoing release of Firmware(s) -
Mhh, tried to do a simulation via WebIf and it stucks at 0.5%, also it is not possible to cancel the print. Need to press Emergency-Stop