"Could not establish a connection to the Duet firmware!…"
-
Hi guys
I've been at it for a while now, initially I've tried updating the firmware in November or so, "Could not establish a connection to the Duet firmware! Please check your settings and try again" error… was very busy with work, gave up, just left it standing collecting dust. Xmas came, than holidays overseas, got back, started a new job so little time to play with it the updates.
I'm trying 2nd day now, following instructions on official website, found a better flowing guide online ( https://betrue3d.dk/duet-wifieth-recover-from-erase-basic-setup/ ), followed that, still same result.
Digging around forums I've found an older post by DC42 quoting a user with "WiFi module started Error: Failed to initialise WiFi module, code -10" Then it reverted to this error "Received opcode 0000013e length 0 data" constantly" and his answer For anyone else getting this error, it means that the version numbers of DuetWiFiFirmware and DuetWiFiServer are out of step. You can comment out the M552 S1 command in config.g to prevent the wifi module starting up. Then run M115 to check the version number of DuetWiFiFirmware. If that shows 1.19 then copy DuetWiFiServer-1.19.bin into /sys and rename it DuetWiFiServer.bin. Then you can run M997 S1 to install it.
Now, I'm either missing something or doing something wrong, got the latest release published (1.21) using DWC 1.20, following everything step by step, files flashed correctly, wifi initiates correctly, connects to my network without fail every time, upon loading DWC all I get is "Could not establish a connection to the Duet firmware! Please check your settings and try again"…
What am I missing here??
Thank you
-
Hmm, changed things again after having a walk to vent off hehe, used different SD card, flashed things in order, briefly had a glimmer of hope! It connected… but within seconds died again with:
A communication error was reported, so the current session has been terminated. Please check your board and try to connect again
Starting to really get on my nerves…
M122 dump:
SENDING:M122
=== Diagnostics ===
Used output buffers: 1 of 32 (1 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.21RC1 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F6-3SJ6N-1LZRY
Static ram used: 15448
Dynamic ram used: 99784
Recycled dynamic ram: 3552
Stack ram used: 3568 current, 4496 maximum
Never used ram: 7792
Last reset 00:01:08 ago, cause: power up
Last software reset details not available
Error status: 1
[ERROR] Error status: 1Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 43.1, current 45.8, max 46.2
Supply voltage: min 23.7, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.099134; fastest: 0.000043
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 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 heaters = 0 -1 -1 -1, chamberHeaters = -1 -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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21RC1
WiFi MAC address 60:01:94:34:3b:6a
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 17448
WiFi IP address 192.168.1.22
WiFi signal strength -63dBm, reconnections 0, sleep mode modem
HTTP sessions: 0 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) -
In the brief moment that connection is established I've checked the Settings tab in web interface, this is telling:
Firmware Name: n/a
Firmware Version: n/a
Web Interface Version: 1.20 -
The WiFi signal strength of -68dBm is low, which may explain why the connection is marginal. See https://duet3d.com/wiki/WiFi_disconnections_and_AJAX_timeout_errors.
-
Hmm, I'll try moving it.
The printer has been in same location from the start, never lost a connection due to network issue before my firmware update woes.. I'll post an update
-
Nope, same story there.
"A communication error was reported, so the current session has been terminated. Please check your board and try to connect again."
Moved it closer and closer, signal isn't the issue here.
-
Hmm, tried same process again, erased everything, started from scratch with new release of 1.21, connection lasts about 2 seconds, followed by:
"A communication error was reported, so the current session has been terminated. Please check your board and try to connect again."
While it lasts, I can check tabs, so getting:
Firmware Name: RepRapFirmware for Duet WiFi and Duet Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 1.21RC2 (2018-02-15 build 2)
WiFi Server Version: 1.21RC2
Web Interface Version: 1.20 -
Can you get ready to send M122 from the GCode Console, then connect and immediately send that command?
-
After a lot of testing and moving things around, I have to say that you're right after all, it must be the signal. While signal dB values change, and I can maintain the connection for quite some time - even seemed fixed at some point - while uploading new config via web interface I've noticed something very telling.
In the batch of text files being uploaded, some would pass some would fail - retry - different batch would pass and different fail, and so on…
Got it going now but resigned myself to running it via usb.
Thank you for your time mate, you can close this thread
