New firmware 2.01 beta 2 available

Phaedrux

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.

keyz182

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 ===

gtj0

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

gideon

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

@gideon I found the error by not reading properly,
I have put the DWC back to version 1.21R4 and now it works again

dc42

@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.

dc42

@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.03

This is a bug in DWC 1.21.2beta2 used with CoreXY machines. Please revert to DWC 1.21.

gideon

@dc42 I found the error by not reading properly,
I have put the DWC back to version 1.21R4 and now it works again

JohnOCFII

@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.

sjason1377

this firmware doesn't let probe work. P9 code does nothing

dc42

Closing this thread because nobody should be using the 2.01RC firmware now that 2.01 is released.