New firmware 1.20 Release Candidate 2 - please try it!
-
@strips, please follow the instructions at https://www.duet3d.com/forum/thread.php?pid=32944#p32944.
-
David, that is what I did.
Connected to DuetWifi by USB (octoprint in bigbox). The M111 S1 P14 really does not give my anything after it failed. I need to try again and enable before it fails to see if I get anything before.
-
Funny… not changing anything today everything works
So I have to call this one off for the moment
-
Please try the new 1.20RC4 and DWS 1.20RC1 that I have just released.
-
The Machine Properties tab is not reporting the motor currents in RC4 or RC3. Not sure about earlier versions. Could be a DWC thing too I suppose?
-
…
1. Use M140 H0:2:3:4 to configure multiple bed heaters, instead of M140 P0 H0, M140 P1 H3 etc.
...
Thoughts?That sounds very good to me.
-
Hi I still a lot of problems to Connect, to my DuetWifi board, is just go on and off.
I Have install the new 1.20RC4 and DWS 1.20RC1, but NO, the only drifrence from RC3 I can see, is it now only reconnect once, the it say WiFi reported error: Timed out while trying to connect to ….This is from Pronterface, and running a M111 S1 P14
Connecting...
Printer is now online.
WiFi reported error: Lost connection, auto reconnectingM111 S1 P14
SENDING:M111 S1 P14
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13)
WiFi reported error: Timed out while trying to connect to Nordbygaard
WiFi: sleep enable,type: 2
WiFi: sl
WiFi: scandone
WiFi: usl
WiFi: state: 5 -> 0 (0)
WiFi: rm 0
WiFi: pm close 7
WiFi: del if0
WiFi: usl
WiFi: mode : nullAny ide, what this can be?
-
Don't understand why you installed a release candidate rather than the full release one https://www.duet3d.com/forum/thread.php?id=3817
-
Just to try is, because the full release do the same on and off. Now I an´m back to the full release.
From Pronterface:
SENDING:M111 S1 P14
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13)
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 6
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 7
WiFi: dhcp client start…
WiFi: pm open,type:2 0
WiFi reported error: Timed out while trying to connect to Nordbygaard
WiFi: sleep enable,type: 2
WiFi: sl
WiFi: scandone
WiFi: usl
WiFi: state: 5 -> 0 (0)
WiFi: rm 0
WiFi: pm close 7
WiFi: del if0
WiFi: usl
WiFi: mode : nullTo connect aging, I have to power off / on.
-
On RC4 now and so far so good! Running through levelling and calibration routines because of a rebuild.
-
Maybe a bit late to claim an issue with RC4 now that it is officially released.
I have some G1 or G0 moves in the end code of the slicer to park the effector at X0 Y0 Z160.
These moves get misinterpreted by DWC and it always shows layer count 799. Thereby the estimated print duration based on
layer time x #layers is totally wrong too.
I tried G0 and G1 moves, both with same result.
If DWC would check for moves which include an extrusion, it would detect the last relevant layer.Sorry, if that has been posted earlier, I'm not a regular visitor here…
-
That's a well-known issue. The solution is put a comment starting with ;E or ; E at the end of the G0 or G1 command line that does that movement.
