Firmware 2.02 Release candidate 3 now available

incogizmo

Tested with Duet Maestro and LCD, no stutter or slowdowns on high detail areas like previously. A decent torture test seems to have been Slic3r Gyroid infill. Awesome work!

dc42

@incogizmo said in Firmware 2.02 Release candidate 3 now available:

Tested with Duet Maestro and LCD, no stutter or slowdowns on high detail areas like previously. A decent torture test seems to have been Slic3r Gyroid infill. Awesome work!

Thanks for confirming that it is fixed.

fma

@dc42 said in Firmware 2.02 Release candidate 3 now available:

The object model will underpin three features planned for forthcoming firmware revisions: conditions and loops in GCode, more flexible/more readable menu description files for the 12864 display on the Duet Maestro, and user-configurable fields in Duet Web Control. Currently it is only used in two places:

The M408 P1 S"filter" command uses it to return values from the object model. It's not fully working because of a bug in the filter parser, however M408 P1 with no filter returns the complete object model. DWC will use a similar mechanism to retrieve values for user-specified fields.

In a G- or M-code command, in place of a numeric parameter it should be possible to use an expression such as [gcodes.speedFactor]. But this isn't useful yet because so few variables are included in the object model, also it's not working because of the same bug in the filter parser.

The next step is to design the object model. Some of the existing module boundaries (gcodes, platform, move etc.) are not right for the object model, so some redesign/refactoring will be needed.

Amazing! The future looks good

kuhnikuehnast

Interesting thing I found about G30:

If you use:

G30 X20 Y20

to probe the bed at a specific point, you always have to calculate the offset of the probe, because the coordinates of the nozzle are used.

Whereas if you use 2:

G30 P0 X20 Y20 H0 Z-99999

the offset of the probe is already calculated and the real probe coordinates are used but not the "actually" coordinates of the nozzle

The H- parameter is still not taken into account when probing. Therefore, I performed a little test:

M561                                                    ; delete any bed transformation
G1 X45.457 Y8.602 Z10 F15000				; go to probing point on floating bed
G30 X45.457 Y8.602 H0 S-1   				; define this point as Z=0

M561                                                    ; delete any bed transformation
G1 X45.457 Y8.602 Z10 F15000				; go to probing point on floating bed
G30 X45.457 Y8.602 H5 S-1   				; define this point as Z=0

M561                                                    ; delete any bed transformation
G30 P0 X20 Y20 H0 Z-99999 S-1			        ; probe point P0

M561                                                    ; delete any bed transformation
G30 P0 X20 Y20 H3 Z-99999 S-1			        ; probe point P0

M561                                                    ; delete any bed transformation
G30 P1 X20 Y20 H3 Z-99999 S-1			        ; probe point P1

This ended up in the results:

20:20:45G32 bed probe heights:, mean nan, deviation from mean nan
20:20:42G32 bed probe heights: 0.004, mean 0.004, deviation from mean 0.000
20:20:39G32 bed probe heights: 0.007, mean 0.007, deviation from mean nan
20:20:36Stopped at height 1.399 mm
20:20:31M98 P"0:/macros/Test H-Factor"
Stopped at height 1.399 mm

So as the H-factor differs every probe, the results are all the same...

greetings kuhni

Adrian52

@dc42 updated to 2.02rc3 and dwc 1.22.4-b1. Prints fine, but at the end of a print, the 'job status' does not seem to finish properly. Previously the 'print another' option would appear, but now I just get greyed out 'pause job' button. Using a Kossel delta. Can select and print another job from the g-code files tab.

Adrian52

@adrian52 previous version dwc seems to work fine with rc3

pro3d

@phaedrux
Did you test M600 yet?

Does it have pause and park feature or does this have to be macros on the side?

/Roy

stewwy

Had a problem with the 1.22.4 web interface:

Uploading a file the first time using the upload&print button was fine.
However if I upload it again with the same filename, having made some slicer settings, and having paused and canceled the original it usually failed the re-upload.

Just retrying with 1.22.3 and it works fine

Phaedrux

@pro3d it will run pause.g by default or filament-swap.g if present. So you have to customize the macro to your needs.

k3lag

@dc42 updated to 2.02rc3 and dwc 1.22.4-b1. Since upgrading whenever I scroll down in DWC it automatically scrolls back up a couple seconds later. Very irritating. I'm using Safari 12.0. This hasn't been a problem with any previous version. It seems to print fine however.

dc42

@k3lag said in Firmware 2.02 Release candidate 3 now available:

@dc42 updated to 2.02rc3 and dwc 1.22.4-b1. Since upgrading whenever I scroll down in DWC it automatically scrolls back up a couple seconds later. Very irritating. I'm using Safari 12.0. This hasn't been a problem with any previous version. It seems to print fine however.

Which version of DWC were you using previously?

Dougal1957

@k3lag I can't reproduce this in Safari 12.0 it appears just fine to me tho I normally use Chrome.

Doug

zerspaner_gerd

@k3lag said in Firmware 2.02 Release candidate 3 now available:

@dc42 updated to 2.02rc3 and dwc 1.22.4-b1. Since upgrading whenever I scroll down in DWC it automatically scrolls back up a couple seconds later. Very irritating. I'm using Safari 12.0. This hasn't been a problem with any previous version. It seems to print fine however.

I have that too (with Chrome).
It depends on the screen size, I noticed.

Here are two pictures see scroll bar
0_1540130916549_Scrollen 100%.jpg
jump back (100%)

0_1540131019863_Scrollen 110%.jpg
scrolling works (110%)

But I already had it with the previous version DWC 1.22.1

k3lag

I was using 1.22 and never noticed a problem. I reverted back to 1.22.3 and it behaved the same as the .4b1. However, I figured out that it is related to 'scaling' the web page. If I use the buttons in my browser to either shrink or enlarge the page the problem occurs. It does not occur if it's not being scaled. It appears others have seen the same thing in other browsers. I don't have this problem with any other web pages that I've noticed.

BlueDust

@adrian52 I also see that the Print Again is missing, and it is super annoying. I keep testing the same parts after making small adjustments, pause, cancel, print again etc... And this got annoying the first time I printed after updating the firmware and web interface.

Phaedrux

I've seen an error message on the PanelDue console that hasn't shown up in the Gcode console.

Wifi reported error: incomplete write wifi reported error: incomplete write It shows up twice like that.

It happened once while trying to download a gcode file from the DWC. The download failed in the browser as well.

Then it happened again uploading a Gcode file. But the gcode file seems to have uploaded correctly.

When I saw the error message I checked the DWC console which was up and running but nothing was there.

I then ran a M122 to see the diagnostics and the DWC reloaded and the printer paused for a second mid print and then carried on. When the DWC reloaded I ran M122 again. This time it worked. But doesn't seem to show anything amiss. Nothing was logged to the PanelDue console.

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC3(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6JKF0-3SN6N-T2ZBY
Used output buffers: 1 of 20 (20 max)
=== RTOS ===
Static ram: 28532
Dynamic ram: 98720 of which 12 recycled
Exception stack ram used: 512
Never used ram: 3296
Tasks: NETWORK(ready,328) HEAT(blocked,1184) MAIN(running,3484)
Owned mutexes:
=== Platform ===
Last reset 02:13:18 ago, cause: power up
Last software reset at 2018-10-15 13:21, reason: User, spinning module GCodes, available RAM 3480 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 4
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 44.5, current 44.9, max 45.3
Supply voltage: min 23.8, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max 0/1007
Driver 1: ok, SG min/max 0/254
Driver 2: standstill, SG min/max 0/222
Driver 3: ok, SG min/max 0/240
Driver 4: standstill, SG min/max not available
Date/time: 2018-10-21 16:43:25
Cache data hit count 4294967295
Slowest loop: 4.63ms; fastest: 0.07ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 150, MinFreeDm: 150, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 191830, completed moves: 191800
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 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
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 doing "G1 X186.602 Y122.915 E0.08193" 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: 182.79ms; 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:ef:4a:74
WiFi Vcc 3.31, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 13216
WiFi IP address 10.10.0.63
WiFi signal strength -40dBm, reconnections 0, sleep mode modem
Socket states: 0 2 0 0 0 0 0 0
=== Expansion ===

Synapsis

I have been using it without any real problem but a funny one.
While I was connected I had to turn my router off. When the router was back online the duet reconnected but the web interface would not connect again, even after a refresh of the page. I closed the browser and reopened it, but nothing it would not connect to the duet.
I had to turn the duet off then on and all was back to normal.

timcurtis67

If you have a panel due try sending an M552 S1to restart the Wifi.

See https://duet3d.dozuki.com/Wiki/GCode#Section_M552_Set_IP_address_enable_disable_network_interface

chrishamm

@adrian52 Thanks for the note, I'll fix this shortly.

@k3lag I'm afraid I cannot reproduce this. I tried it on Firefox (Win+Linux), Edge and Safari (OS X) but it never scrolls up for me. Can you check if the toggling the option "Always show info area and menu" on the Settings makes a difference?

Edit: There you go - v1.22.4 is now official: https://github.com/chrishamm/DuetWebControl/releases/tag/1.22.4

k3lag

@k3lag I'm afraid I cannot reproduce this. I tried it on Firefox (Win+Linux), Edge and Safari (OS X) but it never scrolls up for me. Can you check if the toggling the option "Always show info area and menu" on the Settings makes a difference?

Edit: There you go - v1.22.4 is now official: https://github.com/chrishamm/DuetWebControl/releases/tag/1.22.4

I can't duplicate now either. It was consistent for a few days now suddenly it seems fine. I'll let you know if the problem returns and I'll pay attention to any change in circumstances that may cause it.