New firmware 2.01 beta 2 available
-
@wilriker said in New firmware 2.01 beta 2 available:
@dc42 said in New firmware 2.01 beta 2 available:
Before you added the comment, did you have a newline at the end of the M29, or not?
I did not. Is that an implicit requirement?
EDIT: Empty newline at the end also works.
Thanks for confirming that. The firmware appends a newline to the end of the last command if there isn't one, but I guess it's doing it a little too late in the case of having to recognise M29. I'll fix it in the next beta or RC if the fix isn't complicated.
-
@incogizmo said in New firmware 2.01 beta 2 available:
@dc42 said in New firmware 2.01 beta 2 available:
- On the Duet 2 Maestro, the 2 optional add-on drivers are now assumed to be TMC2224 with UART interface
Amazing! I will have some time on the weekend to properly test this! Along with the 7th Driver pin reversal. I will report back as soon as I can.
@dc42 got to testing it all sooner than expected. Can confirm microstepping is now applying on both addon drivers and driver 6 (7th driver) is also working as expected.
Are there any commands or anything else I can do to help you confirm all is working as expected?
-
@incogizmo said in New firmware 2.01 beta 2 available:
@incogizmo said in New firmware 2.01 beta 2 available:
@dc42 said in New firmware 2.01 beta 2 available:
- On the Duet 2 Maestro, the 2 optional add-on drivers are now assumed to be TMC2224 with UART interface
Amazing! I will have some time on the weekend to properly test this! Along with the 7th Driver pin reversal. I will report back as soon as I can.
@dc42 got to testing it all sooner than expected. Can confirm microstepping is now applying on both addon drivers and driver 6 (7th driver) is also working as expected.
Are there any commands or anything else I can do to help you confirm all is working as expected?
Thanks for confirming this. I can't think of any other tests needed on the expansion board at present.
-
I just had a print stop on me. I think it happened when I tried to connect to the DWC from my iphone to check on the print. I had just looked at the camera and things we're going smoothly. I loaded the DWC and it wouldn't finish loading on the iphone. I went to check the printer and it was stopped sitting above the print. Heaters off and cooling down.
M122
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01beta2(RTOS) running on Duet WiFi 1.02 or later Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3SN6N-T2ZBY Used output buffers: 3 of 20 (10 max) === RTOS === Static ram: 28484 Dynamic ram: 96160 of which 0 recycled Exception stack ram used: 328 Never used ram: 6100 Tasks: NETWORK(ready,328) HEAT(blocked,1192) MAIN(running,3616) Owned mutexes: === Platform === Last reset 00:16:07 ago, cause: software Last software reset at 2018-07-20 22:02, reason: Stuck in spin loop, spinning module PrintMonitor, available RAM 5724 bytes (slot 1) Software reset code 0x4049 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x2001ffd0 Task 0x4e49414d Stack: 00000008 0044509b 00008096 ffffffed 00000000 00f00000 e000ef34 c0000000 20006c94 00445195 00444f0c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 36.6, current 38.8, max 40.1 Supply voltage: min 23.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0 Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 2018-07-20 22:19:11 Slowest loop: 9.67ms; fastest: 0.08ms === Move === Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 0, completed moves: 0 Bed compensation in use: mesh Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Stack records: 2 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 71.55ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.21 WiFi MAC address 5c:cf:7f:ef:4a:74 WiFi Vcc 3.31, reset reason Turned on by main processor WiFi flash size 4194304, free heap 14808 WiFi IP address 10.10.0.63 WiFi signal strength -36dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 === Expansion ===In the console of the PanelDue I also see an error from 3 hours earlier saying Wifi reported error: incomplete write. But nothing else. I'm not sure what that would have been from.
-
I'm running an earlier version of post 2.0 beta firmware (will confirm on Monday) on a Duet Ethernet/Deux5/CoreXY with three steppers for the z-axis.
I run a bed level compensation that probes three points in the bed.g file and adjusts the screws to level the bed.
I've a limit switch on max y (homing works fine) but found that if the coordinate in the bed.g is beyond that limit switch the system will drive the axis into the switch and then some while the stepper misses steps.
Running 3 P3Steel with Duet 2. Duet 3 on the shelf looking for a suitable machine. One first generation Duet in a Logo/Turtle style robot!
-
@phaedrux said in New firmware 2.01 beta 2 available:
I just had a print stop on me. I think it happened when I tried to connect to the DWC from my iphone to check on the print. I had just looked at the camera and things we're going smoothly. I loaded the DWC and it wouldn't finish loading on the iphone. I went to check the printer and it was stopped sitting above the print. Heaters off and cooling down.
Thanks for your report. Unfortunately the stack trace doesn't provide any useful data in this case. I will change it in the next beta.
-
@doctrucker said in New firmware 2.01 beta 2 available:
I'm running an earlier version of post 2.0 beta firmware (will confirm on Monday) on a Duet Ethernet/Deux5/CoreXY with three steppers for the z-axis.
I run a bed level compensation that probes three points in the bed.g file and adjusts the screws to level the bed.
I've a limit switch on max y (homing works fine) but found that if the coordinate in the bed.g is beyond that limit switch the system will drive the axis into the switch and then some while the stepper misses steps.
The coordinates of points in bed.g files are not checked against the axis limits. This is because on delta printers it is sometimes useful to probe beyond the normal bed limits.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Probing beyond a limit switch? That behaviour should be an exception rather than norm? If this is still the case would it be more sensible to have a hard limit and print limit for the axis maximum and minimum?
-
Is it now normal for the DWC manual controls to ignore the configured the M208 maxima? I'm not using max endstops on my cartesian and now it's able to crash past the set maxima when jogging the axis around. The previously installed 2.0 release build did not allow this with the same config.
-
I'm also still finding that my first layer heights are off unless I clear the heightmap and reload it after homing Z.
G29 S2 ; Disable bed compensation. G29 S2 ; Disable compensation again. G28 Z ; Home Z G29 S1 ; Load heightmap.csv and enable compensation. -
I'm getting really unreliable Wifi connection on this build, DWC is disconnecting a lot. Sometimes it will be fine for an hour or so, other times it'll be constant disconnects for a few minutes at a time.
Not sure if it's useful or not, but here's M122 straight after reconnecting.
23:37:36M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01beta2(RTOS) running on Duet WiFi 1.02 or later Board ID: 08D6M-91AST-L2MS0-6JKDD-3SJ6K-9PD5L Used output buffers: 1 of 20 (14 max) === RTOS === Static ram: 28484 Dynamic ram: 96524 of which 0 recycled Exception stack ram used: 508 Never used ram: 5556 Tasks: NETWORK(ready,328) HEAT(blocked,1248) MAIN(running,3584) Owned mutexes: === Platform === Last reset 03:07:26 ago, cause: power up Last software reset at 2018-07-21 18:21, reason: User, spinning module GCodes, available RAM 5556 bytes (slot 1) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 43.8, current 44.1, max 44.7 Supply voltage: min 24.0, current 24.1, max 24.6, under voltage events: 0, over voltage events: 0 Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 2018-07-21 23:37:35 Slowest loop: 10.02ms; fastest: 0.08ms === Move === Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 248, completed moves: 248 Bed compensation in use: mesh Bed probe heights: -0.864 -0.912 0.269 0.131 0.069 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.0 === GCodes === Segments left: 0 Stack records: 3 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 170.46ms; fastest: 0.08ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.21 WiFi MAC address 5c:cf:7f:37:89:d5 WiFi Vcc 3.33, reset reason Turned on by main processor WiFi flash size 4194304, free heap 16864 WiFi IP address 192.168.0.183 WiFi signal strength -44dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: ok === Expansion === -
Another hang in the middle of a print...
The Duet is taking a few seconds to respond to commands and the Duex I2C error rate is increasing.M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01beta2(RTOS) running on Duet Ethernet 1.02 or later + DueX5 Board ID: 08DGM-95BNL-MGPSJ-6JTD8-3SS6K-11XHZ Used output buffers: 1 of 20 (14 max) === RTOS === Static ram: 28484 Dynamic ram: 95760 of which 0 recycled Exception stack ram used: 484 Never used ram: 6344 Tasks: NETWORK(ready,400) HEAT(blocked,1248) MAIN(running,3128) Owned mutexes: === Platform === Last reset 01:52:46 ago, cause: reset button or watchdog Last software reset at 2018-07-21 16:32, reason: User, spinning module GCodes, available RAM 6504 bytes (slot 2) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 35.7, current 35.9, max 36.3 Supply voltage: min 24.4, current 24.5, max 24.5, under voltage events: 1, over voltage events: 0 Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: standstill, SG min/max not available Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Expansion motor(s) stall indication: yes Date/time: 2018-07-21 18:25:42 Slowest loop: 185.59ms; fastest: 102.56ms === Move === Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 109591, completed moves: 109592 Bed compensation in use: none Bed probe heights: 0.005 -4.491 -1.857 0.000 0.000 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 === GCodes === Segments left: 0 Stack records: 3 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is ready with "M105" in state(s) 0 aux is ready with "M408 S0 R26" in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 167.65ms; fastest: 0.03ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 Interface state: 5 === Expansion === DueX I2C errors 33903 -
Hello, I updated the firmware today.
I had version 1.21, but now he has been updated to 2.01beta2 (RTOS) (2018-07-14b5).
at version 1.21 everything did it well but now I have 1 problem the homen of the x and y axis goes well, but if I do on the x axis +100 then he moves digionally this was not the other version
how can I solve this ?
it is about corexy, the problem in the firmware should be downgraded or I am doing something wrong
thank you in advance
is about the duet 2 v1.03 -
@gideon I found the error by not reading properly,
I have put the DWC back to version 1.21R4 and now it works again -
@helluscorus said in New firmware 2.01 beta 2 available:
Is it now normal for the DWC manual controls to ignore the configured the M208 maxima? I'm not using max endstops on my cartesian and now it's able to crash past the set maxima when jogging the axis around. The previously installed 2.0 release build did not allow this with the same config.
I already asked chrishamm to revert this behaviour.
-
@gideon said in New firmware 2.01 beta 2 available:
Hello, I updated the firmware today.
I had version 1.21, but now he has been updated to 2.01beta2 (RTOS) (2018-07-14b5).
at version 1.21 everything did it well but now I have 1 problem the homen of the x and y axis goes well, but if I do on the x axis +100 then he moves digionally this was not the other version
how can I solve this ?
it is about corexy, the problem in the firmware should be downgraded or I am doing something wrong
thank you in advance
is about the duet 2 v1.03This is a bug in DWC 1.21.2beta2 used with CoreXY machines. Please revert to DWC 1.21.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 I found the error by not reading properly,
I have put the DWC back to version 1.21R4 and now it works again -
@phaedrux said in New firmware 2.01 beta 2 available:
I'm also still finding that my first layer heights are off unless I clear the heightmap and reload it after homing Z.
G29 S2 ; Disable bed compensation. G29 S2 ; Disable compensation again. G28 Z ; Home Z G29 S1 ; Load heightmap.csv and enable compensation.Interesting. I noticed that I was getting a smushed first layer on parts of my delta bed with beta2. I wonder if this is related, or if my issue is just something physical. I'll have to try this to see if I see different behavior.
-
this firmware doesn't let probe work. P9 code does nothing
-
Closing this thread because nobody should be using the 2.01RC firmware now that 2.01 is released.
