Duet Web Control 2.1.1 released

jay_s_uk

Its dependant on RRF3.01+ as it uses the object model

DocTrucker

@jay_s_uk cheers, that's what I expected but I wasn't sure if it used the object model it available, or exclusively. From what you say it is the latter.

GrodanB

@PaulHew said in Duet Web Control 2.1.1 released:

@chrishamm
Found this this morning.

'Turn Everything Off' does not do anything.

FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-01-03b3

Also strange is that with a dual set-up the loaded filament is moved from T1 to T0 and cannot be unloaded.
(To be clear, T1 has a filament loaded, I do a pause, then immediately a cancel and suddenly T0 is loaded with T1 filament and that cannot be loaded to T1 again and T0 does not what to unload it. Temp settings is still on as espected on T1 (old temp) and t0 also as before...)

I had to delete the file "filaments.csv" and do a "EMERGENCY STOP" to get T0 to relese the T1 filament...

I think this happen when I cancel a print...

Which I do a lot since I try to get my filament to stick.
Would be nice to be able to cancel directly and not need to pause and then cancel...

This time I do not see the "filament.csv" so I pray to god that a power on of cycle get my printer back...

I did... the file was not shown until I made a power on/off cycle.

That would be nice if it did.
I also do not understand why the file "filament.csv" kept after a power cycle? At least a forced unload feature would be useful...

GrodanB

For some reason I cannot change the wording mistake I did above (someServer.com identified post as spam)

So a power OFF/ON did work...

smoki3

Is M122 working for someone?

chrishamm

Thanks, I've already fixed the crash that occurs when a heater fault occurs and I'll fix the filament assignment next. Both fixes will be available when RRF 3.01 is released. Likewise the "Turn off all" button has been fixed and a new DWC version will be released among the next DSF version.

SIam

@smoki3

M122 is working here

6.4.2020, 20:32:50 	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC6 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-95BNL-MGPSJ-6J9FD-3SJ6N-K1W3Y
Used output buffers: 4 of 24 (22 max)
=== RTOS ===
Static ram: 28052
Dynamic ram: 94208 of which 24 recycled
Exception stack ram used: 576
Never used ram: 8212
Tasks: NETWORK(ready,116) HEAT(blocked,1244) DUEX(suspended,136) MAIN(running,1608) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 11:14:43 ago, cause: software
Last software reset at 2020-04-06 09:18, reason: User, spinning module GCodes, available RAM 8532 bytes (slot 3)
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: 133.8ms, max retries 0
MCU temperature: min 21.7, current 39.7, max 41.7
Supply voltage: min 24.0, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/981
Driver 1: standstill, SG min/max 0/1023
Driver 2: standstill, SG min/max 0/1023
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max 0/1023
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 0/1023
Date/time: 2020-04-06 20:32:48
Cache data hit count 4294967295
Slowest loop: 312.35ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 107, MaxWait: 5922743ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 789.12ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(2) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 2c:3a:e8:0b:06:33
WiFi Vcc 3.44, reset reason Unknown
WiFi flash size 4194304, free heap 15424
WiFi IP address 192.168.188.36
WiFi signal strength -49dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 4 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok

GrodanB

@chrishamm said in Duet Web Control 2.1.1 released:

Great, by the way, great work. Much appreciated.

Do you require me to upgrade to RRF 3.01? Do not see the benefit to me until new functions are added at the moment I understand that soon it will be at the same function level as latest 2.x.

Again thanks.

DocTrucker

@GrodanB said in Duet Web Control 2.1.1 released:

Do you require me to upgrade to RRF 3.01?

@jay_s_uk said in Duet Web Control 2.1.1 released:

Its dependant on RRF3.01+ as it uses the object model

smoki3

@SIam said in Duet Web Control 2.1.1 released:

@smoki3

M122 is working here

6.4.2020, 20:32:50 	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC6 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-95BNL-MGPSJ-6J9FD-3SJ6N-K1W3Y
Used output buffers: 4 of 24 (22 max)
=== RTOS ===
Static ram: 28052
Dynamic ram: 94208 of which 24 recycled
Exception stack ram used: 576
Never used ram: 8212
Tasks: NETWORK(ready,116) HEAT(blocked,1244) DUEX(suspended,136) MAIN(running,1608) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 11:14:43 ago, cause: software
Last software reset at 2020-04-06 09:18, reason: User, spinning module GCodes, available RAM 8532 bytes (slot 3)
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: 133.8ms, max retries 0
MCU temperature: min 21.7, current 39.7, max 41.7
Supply voltage: min 24.0, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/981
Driver 1: standstill, SG min/max 0/1023
Driver 2: standstill, SG min/max 0/1023
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max 0/1023
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 0/1023
Date/time: 2020-04-06 20:32:48
Cache data hit count 4294967295
Slowest loop: 312.35ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 107, MaxWait: 5922743ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 789.12ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(2) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 2c:3a:e8:0b:06:33
WiFi Vcc 3.44, reset reason Unknown
WiFi flash size 4194304, free heap 15424
WiFi IP address 192.168.188.36
WiFi signal strength -49dBm, reconnections 0, sleep mode modem
Socket states: 4 0 0 4 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok

I just get this without an output. Are you on Duet 2 Wifi?

Bildschirmfoto 2020-04-07 um 09.37.23.png

jay_s_uk

@smoki3

i get full M122 output on a duet 3 + pi and a duet 2 ethernet

wilriker

@jay_s_uk @DocTrucker @GrodanB DWC 2.1.1 is supposed to work with RRF versions pre-ObjectModel. Unfortunately, currently there is a bug in the code that prevents it to get into legacy-mode.

SIam

@smoki3
Yes i use duet wifi

jay_s_uk

@wilriker good to know!

chrishamm

@wilriker I am not aware of this bug, in fact I successfully tested DWC 2.1 with RRF2 just a few days ago.

wilriker

@chrishamm @jay_s_uk It seems that this bug is only for very specific uncommon configurations. So it should already work with everything <3.01-something

c310

How to enable fans on GUI ?!

chrishamm

@c310 Job Status => Fans => Change Visibility

GrodanB

@wilriker said in Duet Web Control 2.1.1 released:

@jay_s_uk @DocTrucker @GrodanB DWC 2.1.1 is supposed to work with RRF versions pre-ObjectModel. Unfortunately, currently there is a bug in the code that prevents it to get into legacy-mode.

OK... so next release might contain the fix so that it is 2.x compatible?

Plan to go to 3.x but not convinced that it is as good as 2.x yet... Seems to have some bug left to remove until I feel it is worth the work... (2.x works fine for me and I only upgrade for any new features so far...)

But being able to use new DWC is a good reason for upgrade if that is necessary...

c310

@chrishamm it does not show up at all. however, if i switch to DWC1 fan is there and works...

888577df-9bc9-4b72-8db6-386786ade95e-изображение.png