New Duet WiFi firmware 1.19beta1
-
I've released this at https://github.com/dc42/RepRapFirmware/tree/dev/Release/Duet-WiFi/Edge. It will mostly be of interest to Duet WiFi users who have been trying version 1.19alpha, and others who have been unable to get reliable connections to their networks because of exceptions causing the wifi module to restart, or who need to use more than one access point.
Important:
-
If you are not already running firmware 1.19alpha, see the upgrade instructions at https://duet3d.com/wiki/DuetWiFiFirmware_1.19_alpha before trying to install this version.
-
If you are already running 1.19alpha then you need to do a simultaneous upgrade of DuetWiFiFirmware and DuetWiFiServer, but your access point details should be remembered. You can upgrade DWC separately, it doesn't have to be done at the same time.
See https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md for the full change list since 1.18.1. My thanks to chrihamm for his hard work on many of the networking improvements in this release.
-
-
Will give this ago tonight and report back. Did you see my 122 dump from alpha3 crash?
-
Again it failed in approx the same spot as last time. I can't figure out exactly at what line tho
Edit: when comparing more closely this time it went 2-3 layers higher so then I think we can rule out error in the gcode file.
gcode used:
http://lokalhost.org/3d/audi_can.gcodeWill try another one now. Never had this happend before tho so suspect that it's related to the upgrade but I'll try another gcode just to be on the safe side ^^
In the web interface I got "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: Syntax Error: Unexepected token p in JSON at position 0".
M122 is showing:
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (6 max)
=== Platform ===
Static ram used: 20356
Dynamic ram used: 95740
Recycled dynamic ram: 2688
Stack ram used: 1296 current, 3592 maximum
Never used ram: 8696
Last reset 01:06:13 ago, cause: reset button or watchdog
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 16776 bytes (slot 4)
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 31.1, current 34.0, max 40.5
Supply voltage: min 24.2, current 24.2, max 24.6, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-05-21 20:36:27
Slowest main loop (seconds): 0.013394; fastest: 0.000000
=== 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
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-beta1
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 39320
WiFi IP address 10.0.1.14
WiFi signal strength -74db
HTTP sessions: 2 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)Edit2: forgot to add version info.
Firmware Version: 1.19beta1 (2017-05-21)
WiFi Server Version: 1.19-beta1
Web Interface Version: 1.16 -
I tried upgrading to this new beta. Would not connect via wifi for me. Rolled it back to 1.18.1 and now my Duetwifi connects. Duetwifiserver 1.06 and web interface 1.15a.
This is the same setup that on different days, it won't connect at all, but most of the time it will connect and once connected, it stays connected.
-
-
Did a second print now of a smaller gcode and that was all good except for some issues on first layer that I've never seen before. I didn't watch the first layer go down so not sure about what happend but it almost looks like the nozle stopped at some spots just heating not extruding so there was some dents in the first layer. This is looking at the side that faces towards the glass (first layer).
Printing on glass + gluestick.
-
Yes. I did. I did it with the 1.19. alpha2 and it would connect and then immediately give the ajax error so rolled back to 1.18.1. Then you released the beta 1 and followed the same instructions and the wifi would not connect.
-
Upgrade to beta1 went well. M552 does not show IP address. How do I connect to DWC? I also upgraded to 1.16
UPDATE Ran Pronterface and connected. M122 showed the IP address. It would be nice to be able to see it with M552 like before
-
I updated the firmware (on my experimental machine) as instructed and added a WiFi network, but when I run [c]M552 S1[/c], nothing happens. I get [c]Wifi module is idle[/c] back after a while, but that's it. I tried with two different WiFi networks, but neither work.
-
Did you check that the network password was entered correctly, and surround it in quotes?
-
With 1.19beta1 my U axis stopped working.
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Wed May 17 2017 18:05:05 GMT+0200 (Romance Daylight Time); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P5 ; Set firmware compatibility to look like Repetier; Drives
M569 P0 S1 ; Drive 0 goes forwards X
M569 P1 S1 ; Drive 1 goes forwards Y
M569 P2 S1 ; Drive 2 goes forwards Z
M569 P3 S1 ; Drive 3 goes forwards X2
M569 P4 S1 ; Drive 4 goes forwards ********UNUSED
M569 P5 S0 ; Drive 5 goes backwards E1
M569 P6 S1 ; Drive 6 goes forwards E2M584 X0 Y1 Z2 E5:6 U3; Create U axis for second X carriage before we try to configure it
M208 X-28 Y0 Z0 U0 S1 ; Set axis minima
M208 X250 Y300 Z420 U337 S0 ; Set axis maximaM350 X16 Y16 Z16 U16 E16:16 I0 ; Configure microstepping without interpolation
M92 X80 Y80 U80 Z1600 E2000:2000 ; Set steps per mm
M566 X1000 Y1000 U1000 Z12 E120:120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 U6000 Z500 E1200:400 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 U1000 Z250 E1000:1000 ; Set accelerations (mm/s^2)
M906 X1200 Y1200 U1200 Z1200 E800:800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Endstops
M574 X1 Y1 Z1 U1 E0 S0 ; Define active low and unused microswitches
;M558 P6 X0 Y0 U0 Z0 H1 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
; G31 P600 X20 Y-8 Z-5 ; Set Z probe trigger value, offset and trigger height
;M557 X15:235 Y15:285 S20 ; Define mesh grid; Heaters
M143 S260 ; Set maximum heater temperature to 260C
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M305 P2 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 2; Tools
M563 P0 D0 H1
M563 P1 D1 H2 X3 ; tool 0 uses extruder drive 0 and heater 1 and maps X to U
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R00 S00 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 X3 ; tool 1 uses extruder drive 1 and heater 2 And maps X to U
G10 P1 X0 Y3 Z0 ; Set tool 1 axis offsets
G10 P1 R00 S00; Set initial tool 1 active and standby temperatures to 0C; Network
M550 PAwesomemaker 3 Wifi ; Set machine name
M552 S1 ; Enable network
;M587 SAtlas Connect P"Atlas Connect" ; Configure access point. You can delete this line once connected
;M586 P0 S1 ; Enable HTTP - Not implemented
M586 P1 S1 ; R21 T1; Enable FTP
;M586 P2 S0 ; Disable Telnet; Fans
M106 P0 S0 I0 F200 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F200 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S0 I0 F200 H2 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Custom settings
M575 P1 B57600 S1 ;Setup PanelDue
;Override fan controls for hotend cooling fans
;M106 P0 S0 I0 F100 H1 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
;M106 P1 S0 I0 F100 H2 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on; Miscellaneous
;T0 ; Select first tool
; BLTouch
M307 H3 A-1 C-1 D-1 ; BLTouch - on heater 3 pin
M558 P5 X0 Y0 Z1 H3 F200 T5000 ; Homing Z axis, P5 for BLTouch
G31 X-22.00 Y7.0 Z1.5 P50 ; Set the probe height - reduced P25 down to P5 - no difference;M307 H3 A-1 C-1 D-1
;M558 P3 X0 Y0 Z5 H3 F200 T5000
;G31 P50 X-14 Y40 Z2 -
Maybe I should be more specific - the U axis never moves. Not using the panel and not using the web interface. It is never powered.
-
So. I tried the update to the beta again. It did connect this time and gave me an ajax error a few seconds later. This is what it said.
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: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
And here is the output from M122.
M122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (7 max)
=== Platform ===
Static ram used: 20356
Dynamic ram used: 95748
Recycled dynamic ram: 2680
Stack ram used: 3680 current, 4504 maximum
Never used ram: 7784
Last reset 00:05:03 ago, cause: power up
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 32812 bytes (slot 0)
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 17.9, current 23.5, max 26.8
Supply voltage: min 12.1, current 12.2, max 12.4, 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-22 17:39:21
Slowest main loop (seconds): 0.013398; fastest: 0.000036
=== 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: 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 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
WiFi firmware version 1.19-beta1
WiFi MAC address a0:20:a6:16:ea:67
WiFi Vcc 3.06, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 40344
WiFi IP address 192.168.1.10
WiFi signal strength -38db
HTTP sessions: 1 of 8
Socket states: 0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)Plus when I hooked up to it via usb, only the extruder would and heaters would operate. It would not home any of the axis'.
I have rolled it back to 1.18.1 again and the wifi won't connect but it operates normally via usb. -
Did you check that the network password was entered correctly, and surround it in quotes?
Yes, several times.
-
Did you miss my comment, With 1.19beta1 my U axis stopped working. - two posts up.
-
Yes I did miss that. I'm hoping to do another release today so I will look into that.
-
Is there anyway to see all the lines of M122 on a 7" Panel Due? My IP address changes and without being able to see it with M552, I have to hook up to pronterface with usb just to find it.
-
I second that, I need the full output from M552 on the Panel Due so I don't have connect via USB.
Thanks!
-
No need to hook up USB, just either check your router or use an app like Fing on your phone.
Or set your router up to assign a static IP by MAC address.
-
I am at work and have no access to my router or network scan. Nslookup does not want to report the ip for the printer. It would be immensely helpful to be able to view the ip address of the printer on the Panel Due 4.3. As of now I have not been able to do that at all. M552 S1 does not report the ip on the Panel Due. Is there another M command that shows the ip of the printer?
