New firmware 1.20 Release Candidate 2 - please try it!

dc42

@AS-3D:

The Dark Theme on the new Webcontol is a little bit wrong.

Screenshot:
https://gyazo.com/5d01aed4163234081552f63a99b2f76c

Try updating DWC to 1.20RC3.

AS-3D Druck

@dc42:

@AS-3D:

The Dark Theme on the new Webcontol is a little bit wrong.

Screenshot:
https://gyazo.com/5d01aed4163234081552f63a99b2f76c

Try updating DWC to 1.20RC3.

There is no DWC 1.20RC3 here: https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge
or here: https://github.com/chrishamm/DuetWebControl

//Edite
THX now i found it (Duet Wifi): https://github.com/dc42/RepRapFirmware/blob/dev/Release/Duet-WiFi/Edge/DuetWebControl-1.20-RC3.zip

dc42

I've just released 1.20RC3. This has only minor changes from 1.20RC2.

The following have been reported in this thread:

1. "Starting with Beta11, with the M584 changes, with the U axis hidden if I run G29 the printer starts probing, but after the first row the U drive, which is my second Z motor starts moving up rather than down."

I thought I had asked for more detail about this issue, but it looks like I didn't. Has anyone else seens a similar issue? Hiding the U axis should make no difference to the behaviour of the Z axis, but it will prevent explicit U moves being made.

2. Various WiFi disconnection issues. Please note the instructions to install DuetWiFiServer-1.20b10 twice. You can use older DuetWiFiServer versions with RRF 1.20RC3 if necessary, but if you do then the M587 command to list configured wifi networks may not work. I expect to have DuetWiFiServer 1.20beta11 available early next week.

3. A report that pause/resume caused the print to resume too high. I have tested this on 2 printers and I can't reproduce it.

4. Various DWC issues, which I believed are resolved in DWC 1.20-RC3.

AS-3D Druck

I got a Problem to open a Directory on G-Code Files:

[[language]]
A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:

Version: 1.20-RC3
Message: Uncaught TypeError: Cannot read property 'match' of undefined
URL: http://d-bot.local/js/dwc.js
Line: 2015:27
Error object: {}

Only this Directory makes Problemes everything else works.

deckingman

@dc42:

….................
4. Various DWC issues, which I believed are resolved in DWC 1.20-RC3.

Some have been resolved but the extruder position issue that I reported above is still outstanding.

Gone2Far

@dc42:

@Gone2Far:

Admittedly I do not stress the Duet much, but FWIW, RC2 is working well for me.

Thanks for the feedback! Which Duet do you have?

Duet WiFi, with smart effector and 7" panel due.

dc42

@AS-3D:

I got a Problem to open a Directory on G-Code Files:

[[language]]
A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:

Version: 1.20-RC3
Message: Uncaught TypeError: Cannot read property 'match' of undefined
URL: http://d-bot.local/js/dwc.js
Line: 2015:27
Error object: {}

Only this Directory makes Problemes everything else works.

Is there anything unusual about that directory, for example its name?

Dougal1957

@dc42:

I've just released 1.20RC3. This has only minor changes from 1.20RC3.

The following have been reported in this thread:

1. "Starting with Beta11, with the M584 changes, with the U axis hidden if I run G29 the printer starts probing, but after the first row the U drive, which is my second Z motor starts moving up rather than down."

I thought I had asked for more detail about this issue, but it looks like I didn't. Has anyone else seens a similar issue? Hiding the U axis should make no difference to the behaviour of the Z axis, but it will prevent explicit U moves being made.

2. Various WiFi disconnection issues. Please note the instructions to install DuetWiFiServer-1.20b10 twice. You can use older DuetWiFiServer versions with RRF 1.20RC3 if necessary, but if you do then the M587 command to list configured wifi networks may not work. I expect to have DuetWiFiServer 1.20beta11 available early next week.

3. A report that pause/resume caused the print to resume too high. I have tested this on 2 printers and I can't reproduce it.

4. Various DWC issues, which I believed are resolved in DWC 1.20-RC3.

David

A Couple of Typos first in this post first line V1.20RC3 has minor changes to 1.20RC3

And in the changeling latest release titled as 1.20RC2

Doug

T-Printer

I still have at lot of Communication Error (before with 1.18, ther was no problems with the WiFi)
DuetWiFiServer ver. 1.20B10 Install twice as DC42 say
Web Interface ver. 1.20-RC3
Duet FirmWare ver. 1.20RC3
My Wifi ruter is a ASUS RT-AC87U, and is firmware is up to date. good signal -55
It just go on and off. On the Paneldue is say Wifi Reported Error Lost Connection Auto Reconnect, and Auto Reconnect Succeeded about every 1 - 2 min
On the webinterface most of the time, I have Communication Error, then I can reconect, but after Max 1min I am off aging..
Anny solution to this?
Kent

AS-3D Druck

@dc42:

@AS-3D:
I got a Problem to open a Directory on G-Code Files:
[[language]]
A JavaScript error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this error message:

Version: 1.20-RC3
Message: Uncaught TypeError: Cannot read property 'match' of undefined
URL: http://d-bot.local/js/dwc.js
Line: 2015:27
Error object: {}
Only this Directory makes Problemes everything else works.
Is there anything unusual about that directory, for example its name?

Got it, i used letters like äüß and he converted that to strange Symbols.
After renaming everything works again.

dc42

@Dougal1957:

A Couple of Typos first in this post first line V1.20RC3 has minor changes to 1.20RC3

And in the changeling latest release titled as 1.20RC2

Doug

Thanks, I've corrected those.

dc42

@T-Printer:

I still have at lot of Communication Error (before with 1.18, ther was no problems with the WiFi)
DuetWiFiServer ver. 1.20B10 Install twice as DC42 say
Web Interface ver. 1.20-RC3
Duet FirmWare ver. 1.20RC3
My Wifi ruter is a ASUS RT-AC87U, and is firmware is up to date. good signal -55
It just go on and off. On the Paneldue is say Wifi Reported Error Lost Connection Auto Reconnect, and Auto Reconnect Succeeded about every 1 - 2 min
On the webinterface most of the time, I have Communication Error, then I can reconect, but after Max 1min I am off aging..
Anny solution to this?
Kent

Please can you and anyone else experiencing WiFi disconnection issues do this. Connect a PC via USB and send M111 S1 P14 to enable the WiFi debugging feature. You will get a few WiFi debug messages during startup and initial connection to your router, but there should be no more after that. If the disconnect occurs again, look at the console on the PC to see whether any more debug messages have been received, and report what you find.

vp

When i type M915 in the g-code console in the web interface
only the 1st 3 drivers are listed, see below. I have 9 drivers. Is that the way it should be ?

M915
Driver 0: stall threshold -10, filter on, steps/sec 200, coolstep 0, action: none
Driver 1: stall threshold -10, filter on, steps/sec 200, coolstep 0, action: none
Driver 2: stall threshold -10, filter on, steps/sec 200, coolstep 0, action: none
Driver 3:

T-Printer

HI DC42
This from my WiFi debug.

Connecting…
Printer is now online.

M111 S1 P14
SENDING:M111 S1 P14
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13)
WiFi: bcn_timout,ap_probe_send_start
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: pm open,type:2 0
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi: pm open,type:2 0
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: pm open,type:2 0
WiFi: bcn_timout,ap_probe_send_start
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi: pm open,type:2 0
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi: pm open,type:2 0
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi: pm open,type:2 0
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: bcn_timout,ap_probe_send_start
WiFi: pm open,type:2 0
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: pm open,type:2 0
WiFi: bcn_timout,ap_probe_send_start

dc42

@vp:

When i type M915 in the g-code console in the web interface
only the 1st 3 drivers are listed, see below. I have 9 drivers. Is that the way it should be ?

M915
Driver 0: stall threshold -10, filter on, steps/sec 200, coolstep 0, action: none
Driver 1: stall threshold -10, filter on, steps/sec 200, coolstep 0, action: none
Driver 2: stall threshold -10, filter on, steps/sec 200, coolstep 0, action: none
Driver 3:

There is a limit on the response length for normal replies. You can use M915 D0, M915 D1 etc. to get status for individual drives.

dc42

@T-Printer:

HI DC42
This from my WiFi debug.

Connecting…
Printer is now online.

M111 S1 P14
SENDING:M111 S1 P14
Debugging enabled for modules: WiFi(14)
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13)
WiFi: bcn_timout,ap_probe_send_start
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi status to disassoc
WiFi: state: 5 -> 0 (1)
WiFi: rm 0
WiFi: pm close 7
WiFi: scandone
WiFi: state: 0 -> 2 (b0)
WiFi: state: 2 -> 3 (0)
WiFi: state: 3 -> 5 (10)
WiFi: add 0
WiFi: aid 9
WiFi: cnt
WiFi:
WiFi: connected with Nordbygaard, channel 1
WiFi: dhcp client start...
WiFi reported error: Auto reconnect succeeded
WiFi: ip:192.168.1.162,mask:255.255.255.0,gw:192.168.1.1
WiFi: pm open,type:2 0
WiFi: bcn_timout,ap_probe_send_start
WiFi reported error: Lost connection, auto reconnecting
WiFi: ap_probe_send over, rest wifi
...

Thanks. Apart from an unusual number of disconnections, i don't see anything wrong in those messages. Can you try changing your WiFi router to a different channel? There were some reports a while ago that channel 1 didn't work very well.

deckingman

I just ran simulation mode on a 2MB file that will use 473,819.3mm of filament. It was sliced with a 0,9mm nozzle, 0.7mm layer height at 20mm/sec print speed. The simulation reckons it'll be printed in 1 minute and 1 second. (I wish).

Firmware Name: RepRapFirmware for Duet Ethernet
Firmware Electronics: Duet Ethernet 1.0 + DueX5
Firmware Version: 1.20RC2 (2017-12-13)
Web Interface Version: 1.20-RC3

Edit. Ignore all that - it was me being stupid (no change there then)

T-Printer

Hi Dc42
I have try most of the channel on the WiFi router, but still the same, Some time after 1 hour, but then to go into a loop on / off. We dont have Any problems with other WiFi equipment on the 2.4G

Kent

Iirai

@dc42:

@Iirai:

When I try to connect to DWC I get this error:
Could not establish a connection to the Duet firmware! Please check your settings and try again.

I'm able to ping the DuetWiFi, wifi signal is -59, it's on a static Ip and I confirmed that the mac address is correct . Am I missing something obvious?

1. Did you install DuetWiFiServer.bin twice as suggested in the upgrade notes?

2. If you send M552 S1 from USB or PanelDue then it will report success/failure of the attempt to connect to your router.

M552 S1 from USB and PanelDue says connection the router. As far as I can tell everything sees each other and I can get on to DWC but it will not connect.

DuetWiFiServer ver. 1.20B10 Installed twice(+)
Web Interface ver. 1.20-RC3
Duet FirmWare ver. 1.20RC3
DuetWifi HardWare ver. 1.0

StevenL

my Z height is now messed up. Yes I ran the macro to do a mesh level. even AFTER that, any print starts at a negative Z.
I try to raise the Z, but it gets delayed and then over compensated by me because of the delay.