New firmware 1.19alpha
-
Yes.
-
Great thanks David.
-
I've updated:
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19alpha1 (2017-05-04)
WiFi Server Version: 1.19-alpha1
Web Interface Version: 1.15cI'm still seeing dramatically increased AJAX errors and "can't connect to Firmware" errors with this version (Just like I was with the release of 1.18 and 1.15 web) even though ping seems to be stable. Literally, I'm getting a seconds to a couple of minutes of web connection before the connection drops.
Is this just me?
Also, I may have missed this but the machine name is no longer usable as http://duetwifi.local. Is there a way to get that back?
-
What AJAX error reason does it report: timeout, or something else?
The machine name that you specify in the M550 command should be used as the basis for the ".local" network name, but I forgot to test it. I'll test it today.
-
I'm not getting any domain resolution on MonkeyBot.local (my M550 name) but before the upgrade to 1.19 alpha, I had forgotten to change the name for the wifi connection and it was stuck on duetwifi.local. That, of course, no longer works either.
I'm seeing both AJAX timeouts and "Could not establish a connection to the Duet firmware! Please check your settings and try again."
I've always had periodic AJAX errors (not surprising as I live in a condo with 27 units) but after upgrading from 1.18 beta (3?) to 1.18.1 and DWC 1.15b (and then a), it's been on a whole diferent level.
I'm also seeing periodic reboots while sitting idle (I hear the fans tick on for a fraction of a second while the machine sits idle). It might do it once or a few times. As far as I can tell, I have a solid 24V power signal and I've even tried powering my panel by external power using the micro USB port.
So, it is entirely possible that there is something going on here beyond the firmware. I've ordered a Duet Ethernet which will solve the wireless connection problems and, if no one else is having these issues it could be me, not you.
That brings up a more complex question for myself as this is my third wifi board. I've got a good Meanwell power supply. My wiring has been thoroughly checked and re-checked. Yet I had one catastrophic board failure and the replacement had a habit of rebooting two or three times during startup. Now this board has exhibited some weird power issues (recall the black flashing screen?) and now occasional reboots that may or may not have something to do with this firmware release.
I don't want to derail into possible hardware problems but I'll be happy to try anything you've got that could be software remedial for this issue. There is still a possibility that the reboots are a software crash, right?
-
Weirdly enough, it has been behaving itself all afternoon.
One notable behavior (when it was behaving poorly) was that I was usually getting the DWC pages served to me but connection to the firmware was often not working. Since the DWC shouldn't work if I don't have connection to the system, it seems to be something a little different than the normal AJAX problem.
-
Next time you get an unexpected reboot, run M122. Look at the last reset reason, and if it is Software then report the software reset parameters.
There are no known software issues in DuetWiFiFirmware that cause resets in the current version, but if you have hit a new one then I need the software reset data to help diagnose it.
Your browser may choose to fetch the DWC pages from its cache, but not of course the live updates of temperatures etc.
-
jeez this seams extremely difficult to install lol.
-
Hi David,
So I ran in some same instability problems too,
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19alpha1 (2017-05-04)
WiFi Server Version: 1.19-alpha1
Web Interface Version: 1.15cUpdate was succesfull to 1.19alpha1. Before, I was running 1.18.x (but not 1.18.1) and never had connectivity or stability problems
First, after restarting the webinterface I lost connection a lot. I got AJAX-timeouts and no connection to the firmware in the webinterface. So I tried to investigate:
I restarted the Duet Wifi without webinterface but withPronterface connected and waited 10 minutes ( and got the Webserver: rejecting message with: not found, in Pronterface in that time). Connected at 10 minutes later to the webinterface and it connected, so it somehow reestablished itself (and was still connected to Pronterface). Then heated the bed up and waited 10 minutes. Still connected to the webinterface and Pronterface. After that heated the hotend and waited 10 minutes. Still connected to the webinterface and Pronterface. Homed, let the motors idle. Precisely when the current from the motors was cut off (idle-timeout) Pronterface and the webinterface threw an error, see below for Pronterface M122. Pronterface says it's software-related. Maybe this helps
[c]
Connecting…
Printer is now online.M503
SENDING:M503
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Jan 03 2017 22:45:03 GMT+0100 (West-Europa (standaardtijd))
; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
;M665 L333.000 R174.708 H289.7 B115.0 X0.457 Y0.079 Z0.000
M665 L333.000 R174.587 H289.7 B115.0 X0.456 Y-0.026 Z0.000
;M666 X0.90 Y-0.18 Z-0.71
M666 X0.84 Y-0.21 Z-0.63
M557 R115 S20
M574 X2 Y2 Z2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z0 H3 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 Z1.896 ; Set Z probe trigger value, offset and trigger height
; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
;M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
;M92 X100 Y100 Z100 E450 ; Set steps per mm
;M350 X256 Y256 Z256 E256:256 ; Configure microstepping with interpolation
M92 X100 Y100 Z100 E417.5 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E12000 ; Set maximum speeds (mm/min)
M201 X3000 Y3000 Z3000 E2000 ; Set accelerations (mm/s^2)
M906 X2000 Y2000 Z2000 E1400 I30 ; Set motor currents (mA) and motor idle factor in per cent (Nu ingesteld op 85 procent van stepper motors 2.5a (towers) en 1.7a (extruder))
M84 S30 ; Set idle timeout
; Heaters
M143 S290 ; Set maximum heater temperature to 290C
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4725 C7.06e-8 R4700 ; Set thermistor + ADC parameters for heater 1
;M305 P1 T100000 B4719 C7.08e-8 R4700 ; Set thermistor + ADC parameters for heater 1
;M307 H1 A366.3 C379.3 D3.5 B0
;M307 H1 A360.8 C256.1 D6.0 S1.00 B0
M307 H1 A455.2 C264.6 D7.0 B0
; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
; Network
M550 PKosselXLDuet ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
; Fans
;M106 P0 S0
M106 P0 S0 I0 F200 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P1 S1 I0 F500 H0:1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
; Custom settings are not configured
M501
Webserver: rejecting message with: not found
Webserver: rejecting message with: not found
M122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (12 max)
=== Platform ===
Static ram used: 28556
Dynamic ram used: 79644
Recycled dynamic ram: 2392
Stack ram used: 3680 current, 4668 maximum
Never used ram: 15812
Last reset 00:30:58 ago, cause: power up
Last software reset code 0x4031, HFSR 0x40000000, CFSR 0x00008200, ICSR 0x0440f803, BFAR 0x46320110, SP 0x2001fe74
Stack: 0041a339 0041dafe 21000000 00000000 2000a484 00000e91 200057ec 00000001 00000000 20003544 20003544 00000000 2000a484 cd215182 00000000 00000000 00000000 00000000
Spinning module during software reset: Network, available RAM 16256 bytes (slot 1)
Error status: 0
[ERROR] Error status: 0Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 33.8, current 36.4, max 40.5
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-05-07 19:50:57
Slowest main loop (seconds): 0.009766; fastest: 0.000032
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -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 ready with "M122" 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
Code queue is empty.
Network state is running
WiFi module is connected to access point
SPI underruns 11551056, overruns 11553397
WiFi firmware version 1.19-alpha1
WiFi MAC address 5c:cf:7f:2c:24:ba
WiFi Vcc 3.12, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 6472
WiFi IP address 192.168.1.73
WiFi signal strength -60db
HTTP sessions: 1 of 8
FTP state 0
Telnet state 0M503
SENDING:M503
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Jan 03 2017 22:45:03 GMT+0100 (West-Europa (standaardtijd))
; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
;M665 L333.000 R174.708 H289.7 B115.0 X0.457 Y0.079 Z0.000
M665 L333.000 R174.587 H289.7 B115.0 X0.456 Y-0.026 Z0.000
;M666 X0.90 Y-0.18 Z-0.71
M666 X0.84 Y-0.21 Z-0.63
M557 R115 S20
M574 X2 Y2 Z2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z0 H3 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 Z1.896 ; Set Z probe trigger value, offset and trigger height
; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
;M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
;M92 X100 Y100 Z100 E450 ; Set steps per mm
;M350 X256 Y256 Z256 E256:256 ; Configure microstepping with interpolation
M92 X100 Y100 Z100 E417.5 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E12000 ; Set maximum speeds (mm/min)
M201 X3000 Y3000 Z3000 E2000 ; Set accelerations (mm/s^2)
M906 X2000 Y2000 Z2000 E1400 I30 ; Set motor currents (mA) and motor idle factor in per cent (Nu ingesteld op 85 procent van stepper motors 2.5a (towers) en 1.7a (extruder))
M84 S30 ; Set idle timeout
; Heaters
M143 S290 ; Set maximum heater temperature to 290C
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4725 C7.06e-8 R4700 ; Set thermistor + ADC parameters for heater 1
;M305 P1 T100000 B4719 C7.08e-8 R4700 ; Set thermistor + ADC parameters for heater 1
;M307 H1 A366.3 C379.3 D3.5 B0
;M307 H1 A360.8 C256.1 D6.0 S1.00 B0
M307 H1 A455.2 C264.6 D7.0 B0
; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
; Network
M550 PKosselXLDuet ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
; Fans
;M106 P0 S0
M106 P0 S0 I0 F200 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P1 S1 I0 F500 H0:1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
; Custom settings are not configured
M501
[ERROR] Can't write to printer (disconnected?) (SerialException): Write timeout
[ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] Het apparaat herkent de opdracht niet.)
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] Het apparaat herkent de opdracht niet.)
M503
SENDING:M503
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] Het apparaat herkent de opdracht niet.)
[ERROR] Disconnecting after 4 failed writes.
Disconnected.
Connecting…
Printer is now online.
M122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (4 max)
=== Platform ===
Static ram used: 28556
Dynamic ram used: 79644
Recycled dynamic ram: 2392
Stack ram used: 3680 current, 4504 maximum
Never used ram: 15976
Last reset 00:03:28 ago, cause: software
Last software reset code 0x0031, HFSR 0x40000000, CFSR 0x00008200, ICSR 0x0440f803, BFAR 0xb1bac26b, SP 0x2001fe44
Stack: 0041980f 004343d4 21000000 400c0000 00000001 00000000 0041992b 004198de 81000000 2000a484 00000001 00000000 00000000 00000000 00000000 00000003 2000c018 00000001
Spinning module during software reset: Network, available RAM 15492 bytes (slot 2)
Error status: 0
[ERROR] Error status: 0Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 36.0, current 37.9, max 41.9
Supply voltage: min 12.0, current 12.0, max 12.2, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.003934; fastest: 0.000032
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -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 ready with "M122" 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
Code queue is empty.
Network state is running
WiFi module is connected to access point
SPI underruns 1220324, overruns 1220323
WiFi firmware version 1.19-alpha1
WiFi MAC address 5c:cf:7f:2c:24:ba
WiFi Vcc 3.12, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 6536
WiFi IP address 192.168.1.73
WiFi signal strength -67db
HTTP sessions: 0 of 8
FTP state 0
Telnet state 0
[ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] Het apparaat herkent de opdracht niet.)
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] Het apparaat herkent de opdracht niet.)
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] Het apparaat herkent de opdracht niet.)
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] Het apparaat herkent de opdracht niet.)
[ERROR] Disconnecting after 4 failed writes.
Disconnected.
[/c] -
And now I tested it without Pronterface / usb connected, cold restarted Duet. Just homed and moved down a bit, waited for the steppermotor-timeout in idle: precisely when the motors are cut off, I get " Communication Error
An AJAX error has been reported, so the current session has been terminated.
Please check if your printer is still on and try to connect again.
Error reason: timeout", in the webinterface.
-
Next time you get an unexpected reboot, run M122. Look at the last reset reason, and if it is Software then report the software reset parameters.
There are no known software issues in DuetWiFiFirmware that cause resets in the current version, but if you have hit a new one then I need the software reset data to help diagnose it.
Your browser may choose to fetch the DWC pages from its cache, but not of course the live updates of temperatures etc.
I'll check M122 if it happens again.
I thought of the cache so I loaded it from Safari (which I never use) instead and got the web page with no connection to the firmware. Also, at no time in my history of using this platform have I ever had a case where the web page would serve while not be connecting to the firmware unless I was already connected and it dropped the connection. Meaning that on a first navigate, it always either connected or didn't load anything.
I'll update if I find anything else.
-
FYI, I replaced my board with a Duet Ethernet and I have reliable connection now. I'm on 1.18.1 and 1.15a on the Duet Ethernet, though.
-
I was having problems with connection to duet wifi with version 1.19 alpha 2 and 3. i couldnt connect no matter what i tried….Then i saw DC 42 remark about shutting down the wifi module. M552 S-1 (dont forget the minus sign) I did this and sent M552 S1 to start it up again...has been working flawless. Its a miracle when you follow directions...LOL
-
I had the same problems… disconnects and reboots of the machine after few moments.
Back to 1.18.1 now and everything works like a charm.If you want me to debug/try more David, let me know.
-
DC42, now that the baby is here and we've moved houses, I can do a little testing.
What do you need tested to confirm CoreXY Kinematics, or I should say, How do you want CoreXY kinematics to be tested?
I have a C-Bot with a 7" Panel Due and a BLTouch probe, All are currently working properly now with 1.18.1 firmware, and with a little effort I maybe will be able to get it on video. When I am able I will gladly help with testing.
-
-
I'm also having some problems with disconnects and reboots. Upgraded just 2hr ago so didn't test it much yet but I allready had a problem with the interface just loading like I can't click any buttons and staying there until I hard-reboot it with power down. Testing first print with it now and it seems fine but hope the problems with locking/stopping doesn't come to often. Seems to print fine
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19alpha3 (2017-05-09) <–- this was marked alpha2 on github
WiFi Server Version: 1.19-alpha1
Web Interface Version: 1.15c -
update: tried to access the web interface 70% into the print and the printer just stopped mid print. When web interface finally opened it showed that no axes where homed and the temperatures where going downwards.
Hope these issues is easy to solve so I don't have to downgrade to 1.18 again. Please let me know if there is any logs or dumps I can provide you with.
11:32:06 PMM122
=== Diagnostics ===
Used output buffers: 3 of 32 (6 max)
=== Platform ===
Static ram used: 28556
Dynamic ram used: 79708
Recycled dynamic ram: 2328
Stack ram used: 1296 current, 3592 maximum
Never used ram: 16888
Last reset 00:13:47 ago, cause: software
Last software reset code 0x4031, HFSR 0x40000000, CFSR 0x00008200, ICSR 0x0440f803, BFAR 0x3a687467, SP 0x2001fe5c
Stack: 0041ae99 0041e5b2 81000000 544af202 001556f4 00000000 001af165 b126e0ae 04fcf669 00433812 a1000000 000007ff 0042ff27 0042ff28 21000000 00000000 00000000 00000000
Spinning module during software reset: Network, available RAM 11788 bytes (slot 3)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 35.0, current 37.4, max 41.7
Supply voltage: min 24.1, current 24.2, max 24.6, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-05-20 23:32:05
Slowest main loop (seconds): 0.007935; fastest: 0.000033
=== Move ===
MaxReps: 1, StepErrors: 0, MaxWait: 671ms, Underruns: 0, 0
Scheduled moves: 4, completed moves: 4
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 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
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19-alpha1
WiFi MAC address 5c:cf:7f:2b:ec:d5
WiFi Vcc 3.09, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 8352
WiFi IP address 10.0.1.14
WiFi signal strength -72db
HTTP sessions: 1 of 8
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) -
I have just released version 1.19beta1 for the Duet WiFi. See the new thread on that version for details. Please can those of you who have been trying 1.19alpha upgrade to that version. You need to do a simultaneous upgrade of DuetWiFiFirmware and DuetWiFiServer again, but you should not need to re-enter your access point data because it will not be erased by the firmware upgrade.
