Communication Error, Firmware 1.9
-
I have the same error
[[language]] 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
it happens even on idle. pressing connect on web interface connects back, but this does not reconnect after Emergency Stop button pressed. power off required.
i think it is either WiFi frimware or web server.
i increased timeouts and retry in web interface , but it did not help.please advise
-
Are you running 1.19 firmware? If so, please run M122 when you are connected and report the WiFi statistics, in particular the RSSI.
-
Mine drops all of the time now after 1.19 , any solution for this
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (18 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DAM-9K9K2-NGNSN-6J9D8-3SJ6S-14U3M
Static ram used: 21176
Dynamic ram used: 96128
Recycled dynamic ram: 1480
Stack ram used: 1304 current, 5836 maximum
Never used ram: 6452
Last reset 00:48:07 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 3224 bytes (slot 1)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 19.5ms
MCU temperature: min 50.1, current 50.5, max 55.1
Supply voltage: min 24.4, current 24.5, max 24.9, 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: 2017-08-25 20:39:30
Slowest main loop (seconds): 0.068481; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 7, completed moves: 7
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.3
=== 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 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 state is running
WiFi module is connected to access point
WiFi firmware version 1.19
WiFi MAC address 5c:cf:7f:f8:1f:6b
WiFi Vcc 3.05, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 37752
WiFi IP address 10.0.0.50
WiFi signal strength -76dBm
HTTP sessions: 1 of 8
Socket states: 0 2 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) -
Your WiFi signal strength is only -76dBm, which is to low to give a reliable connection. Changing the WiFi channel on your router may help.
-
here is my M122 too. signal is -76
however nothing changed in setup but firmware. with previous version connection NEVER failed…is there any way to tweak WiFi module?
perhaps watchdog that will do M552-S0 and M552-S1 after signal lost
?[c]
M122
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (9 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DAM-9K9K2-NGNS0-7JKDL-3SD6Q-KR37K
Static ram used: 21176
Dynamic ram used: 96064
Recycled dynamic ram: 1544
Stack ram used: 4008 current, 9300 maximum
Never used ram: 2988
Last reset 00:15:50 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 3224 bytes (slot 2)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
[ERROR] Error status: 0Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 24.9ms
MCU temperature: min 36.8, current 43.1, max 43.6
Supply voltage: min 11.8, current 12.0, max 12.1, 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: 2017-08-27 08:37:51
Slowest main loop (seconds): 0.078613; fastest: 0.000061
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, 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
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.2
=== 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 doing "M190 S110 " 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
autopause 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
WiFi MAC address 5c:cf:7f:a4:0d:77
WiFi Vcc 3.04, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39720
WiFi IP address 192.168.11.233
WiFi signal strength -76dBm
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)[/c]
-
The WiFi module is already supposed to reconnect if it loses the signal, because we are calling the SDK function that enables that. But that code is closed source and I am not sure that it it working, so it is on my list to test soon.
-
here is another dropout: web intertface lost connection, but i was connected via USB…
network is running, but IP is lost.is it possible to use manual IP instead of DHCP?
[c]
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19
WiFi MAC address 5c:cf:7f:a4:0d:77
WiFi Vcc 3.04, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39488
WiFi IP address 0.0.0.0
WiFi signal strength -78dBm
HTTP sessions: 1 of 8
Socket states: 0 0 0 0 0 0 0 0
[/c]Update: M552 P192.168.xx.xx does not update IP address … (even after this command M122 gives IP of 0.0.0.0)
-
1. Please try the 1.19+4 version, see separate thread.
2. For the Duet WiFi, if you want to set the IP address you do that in the M587 command.
-
installed 1.19+4 it does reconnect… but
what is a way to solder external WiFi antenna to the board?which pin or where cable should go?
p.s. i have a delta printer and board is under heatbed (that is aluminium). at the moment i do not want to change printer setup...
probably removing heatbed will increase signal strength, but antenna is much convenient -
If you search the web for ESP8266 and external antenna, you will find a few write-ups from people who have done that.
I too have a delta printer with the Duet under the bed, but I have the wifi antenna poking out through a slot at the side. See https://www.thingiverse.com/thing:965396.