Firmware 2.04RC1 available

zerspaner_gerd

I still have problems that the Duet is not available at regular intervals, neither via the PanelDue nor DWC!

PanelDue will display the same messages each time before the connection aborts or shows no response.

M122 result (after emergency stop):

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J9D2-3S46T-K2T3X
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93996 of which 0 recycled
Exception stack ram used: 312
Never used ram: 11084
Tasks: NETWORK(ready,660) HEAT(blocked,1196) MAIN(running,3748) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:01:30 ago, cause: software
Last software reset at 2019-06-22 19:29, reason: User, spinning module GCodes, available RAM 10916 bytes (slot 0)
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 38.6, current 39.4, max 39.7
Supply voltage: min 24.5, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
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: 2019-06-22 19:31:07
Cache data hit count 349732351
Slowest loop: 4.31ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== 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: 15.60ms; fastest: 0.00ms
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.23
WiFi MAC address 60:01:94:73:5e:04
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24352
WiFi IP address 192.168.188.40
WiFi signal strength -65dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

I think there is a problem with the WiFi "Auto reconnect"!

https://forum.duet3d.com/topic/10892/firmware-2-03-duet-2-and-1-24-duet-06-085-released/8

themelle

@dc42 Thank you for this build!
As far as I can tell, initialization, basic movement, and homing as well as heating seems to work on my delta.
Had a WiFi disconnect (DWC (2.0RC7) was not reachable, ping reported "host is down") for some minutes. Came back online without having to reboot though.

What really puzzles me is that M122 in DWC did not produce any output, even tried different P parameters to no avail. It this a known issue? Is this an issue with DWC or with RRF? Would have loved to gather some error report after the WiFi outage ...
Whatever caused this to happen - it's cured and working after a reboot ...

Best regards
Andreas

zerspaner_gerd

One small question:
Is there a possibility in the current firmware to deactivate and reactivate the heaters without losing the temperature values?
Actually, just as it works for the bed heating (M144 S1 == activate, M140 S-273.15 == disable), since the temperature is maintained?
I read somewhere that it was not the expected behavior. It is apparently not resolved yet?
White a more accurate?

blt3dp

Running a Duet Ethernet v1.02
I prevsiously had 2.02 stable and it was working perfectly. I skipped 2.03 as there were issues found with Delta autocalibration. I recently upgraded to 2.04RC1, after the firmware update I restarted the printer and it came up and appeared to be functioning correctly except the Delta autocalibration. IT probed to my normal 0.005 deviation, but the nozzle was too high, I had to baby step down to get a good first layer. This behavior did not occur with 2.02

I let the print finish, cool down and then shut the printer off. When I went to turn it on, I could connect to DWC, but could not gain control of the machine. I troubleshot this for an hour, clearing my browser cache, rebooting, rebooting the router, switching ethernet cables and nothing resolved it. That behavior also did not occur with 2.02.

Troubleshot further and it appears I was getting the connection to DWC, but it would not connect to the firmware. I ended up putting 2.02 firmware on the SD card by plugging it into my computer, then connecting to Duet via USB and downgrading the firmware. Since then it's been fine.

dc42

Do you have a DueX expansion board in your system?

blt3dp

I don't have an expansion board, just the plain Duet Ethernet board.

dc42

Which version of DWC do you use? If you were using an old one, that might explain the connection issues.

blt3dp

I'm running 1.22.6

garyd9

At this point, can this version of the firmware considered stable?

T3P3Tony

@garyd9 2.03

dc42

2.04RC1 is stable, however there are a couple of 2.03 bug reports that I want to investigate before I do the 2.04 release. Unfortunately there is a tight deadline to meet for the Duet 3 firmware development, so it may be a while before I get back to 2.04.

garyd9

@dc42 said in Firmware 2.04RC1 available:

2.04RC1 is stable, however there are a couple of 2.03 bug reports that I want to investigate before I do the 2.04 release. Unfortunately there is a tight deadline to meet for the Duet 3 firmware development, so it may be a while before I get back to 2.04.

Oh, I completely understand about deadlines and RRF/Duet3. (In fact, I'd be on the duet3 first-run list if I wasn't extremely tight on money these days.)

I really just needed to confirm that this RC is (at the moment) the best stable choice for a delta printer.

Thank you
Gary

boldnuts

@garyd9 I have been using this 2.04RC1 version on my delta since it came out with no issue's at all, go for it!.

jay_s_uk

Same here. I use it on both my deltas

garyd9

Thanks - it seems to be working fine for me (so far*.)

* Typically, if I say something is working, it breaks immediately afterwards. Hopefully, by qualifying the statement with "so far", things will stay working.

blt3dp

I had definite problems with it, I’m totally willing to re-upgrade. If DWC stops being able to connect to the firmware again, can I still run M122 in a terminal connected via usb?

Those with Deltas that haven’t any problems with it, what DWC are you running?

jay_s_uk

DWC 2.0.0-RC7

boldnuts

@jay_s_uk said in Firmware 2.04RC1 available:

DWC 2.0.0-RC7

DWC 2.0.0-RC7

blt3dp

@jay_s_uk said in Firmware 2.04RC1 available:

DWC 2.0.0-RC7

@boldnuts said in Firmware 2.04RC1 available:

DWC 2.0.0-RC7

I just re-updated to 2.04RC1 and this time I updated to DWC 2.0.0-RC7, seems like I'm not having the issue with the higher than normal first layer this time. Wierd, autocalibration calibrated to the deviation I expected, but it seems to be normal now.

Seems fine like last time but we'll see after I power it off and back on in a couple of days.