New Duet WiFi firmware 1.19beta1
-
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?
-
M552 with no params reports the IP address
-
M552 with no params reports the name of the access point I am connected to on the Panel Due display, but does not report the ip unfortunately.
-
ah it does on the DWC stby and I'll just check it on mine
-
M552 on my PanelDUE does give me the IP Address
it reports the configured IP address (This is ignored of course) and the Actual IP address -
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.This has the same software reset code as I have
-
I didn't think you could set a static IP in the config with a duetwifi. David had told me that awhile back. Has that changed?
-
Static IP should be set it in your wireless router using the Duet Wifi's MAC address.
-
In 1.19 you can set up a static IP address in the connection parameters you give in the M587 command. See https://duet3d.com/wiki/G-code#M587:_Add_WiFi_host_network_to_remembered_list.2C_or_list_remembered_networks.
-
Is there a beta for the Ethernet board? I am on 1.19alpha and I am unable to get mesh leveling to work. It will probe the bed and even save the height map file. It is non compensating for my bed at all during the print and M122 says "Bed compensation in use: none". This is right after running G29 or G29 S1
-
I'm not sure I want to upgrade to 1.19. The web-server works OK for me.
Can I just upgrade DWC to 1.16?
-
I think DWC 1.16 should work with firmware 1.18 but I haven't tested it.
There will be a new 1.19beta1 tomorrow or possibly later today. However, the changes in 1.19 are mostly to do with WiFi improvements and supporting new kinematics, do Duet Ethernet and users of older Duets are probably better off staying with 1.18.1 for now.
