Firmware 2.02 Release candidate 3 now available

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.

k3lag

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

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

It just started doing it again and I noticed what's going on but I don't know why. My printers name on the network is "bigbox.local". If the URL in address bar is "bigbox.local" it does not exhibit the problem. Somehow the URL is changing to "bigbox.local." (notice the "." at the end) and when it is that way it scrolls back to the top after scrolling down. I'm not sure where the extra "." is coming from. If I manually put the "." on the end when it's working correctly the behavior will start as well. For some reason the extra "." is getting added to the end of URL on its own somehow.

BlueDust

Z Baby Stepping doesn't seem to work any more.
I just updated DWC to 1.22.4 to see if that would fix it, and it did not.

Current version
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet Ethernet 1.02 or later
Firmware Version: 2.02RC3(RTOS) (2018-10-17b2)
Web Interface Version: 1.22.4

Is anyone else having this problem?

garyd9

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

Z Baby Stepping doesn't seem to work any more.

It seems to be working for me from both the 1.22.4 DWC (that was just put out today) and from the PanelDue 1.22 released a couple days ago. (It's annoying from the Paneldue due to the "response" popups, but it seems to work.)

What symptoms are you seeing that suggest it's not working?

claustro

M557 now supports a P parameter to set the number of X and Y points, as an alternative to using the S parameter to set the spacing

So I can write M557 X30:260 Y15:245 P9
Instead M557 X30:260 Y15:245 S57.5
and the firrmware automatically calculate probe point spacing right?
i

dc42

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

M557 now supports a P parameter to set the number of X and Y points, as an alternative to using the S parameter to set the spacing

So I can write M557 X30:260 Y15:245 P9
Instead M557 X30:260 Y15:245 S57.5
and the firrmware automatically calculate probe point spacing right?
i

Yes, that's correct.

fma

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

Could it be related to this bug? https://www.thingiverse.com/thing:2448907

On previous versions of Chromium, I was able to set the 'enable-scroll-anchoring' to true, and it fixed the problem. But in recent versions, this flag does not exists anymore, and the bug came back (on Thingiverse, I didn't try Duet latest firmware).

BlueDust

@garyd9
I press the neagtive or positive buttons and the nozzle doesn't get any closer or further from the bed. I use this all thr time adjust the squish during the first layer.
I didn't reboot my printer a second time after installing the 3rd beta of the firmware. I will do that when I get home and see if that fixes it.

garyd9

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

@garyd9
I press the neagtive or positive buttons and the nozzle doesn't get any closer or further from the bed. I use this all thr time adjust the squish during the first layer.
I didn't reboot my printer a second time after installing the 3rd beta of the firmware. I will do that when I get home and see if that fixes it.

How big are your baby steps configured for? Does DWC claim that the baby steps are taking place? (It shows the current babystep.) On mine, I never actually measured the nozzle distance to ensure that the babysteps were happening, but I know that I'm about 0.04mm too high on my manual level, and if I don't babystep, everything curls up.

SupraGuy

I hadn't thought much about this, but I'm seeing something similar.

Baby steps are configured as 0.05mm, but I'm not seeing any effect on the machine. It changes the compensation factor on the DWC, (I had it showing up to a full 3mm of compensation at one point) but it didn't move the Z axis motors at all, so far as I could see.

My last few prints, I just stopped using it, because I thought that it might be something in my Z speed/acceleration settings not letting it get started for such a small move.

This started when I upgraded to 2.02RC2, still happening with RC3, however I also changed my Z lead screws when I upgraded to 2.02RC2 from 5mm/0.8mm lead to 8mm/8mm lead (4000 steps/mm to 400 steps/mm.) I had assumed that it had to do with the change in lead screws. I don't have those values from my config.g in front of me at the moment.