Duet 2 wifi not connecting to Paneldue 7i

3dpnut

@Phaedrux thanks for the reply.
M115: FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-05-19b2
ok
M122:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S4-6J9F6-3SD6J-1U1GL
Used output buffers: 1 of 24 (2 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93916 of which 44 recycled
Exception stack ram used: 308
Never used ram: 8824
Tasks: NETWORK(ready,1892) HEAT(blocked,1224) MAIN(running,1824) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:01:24 ago, cause: power up
Last software reset details not available
Error status: 0
MCU temperature: min -72.1, current -67.6, max -65.6
Supply voltage: min 16.3, current 16.3, max 16.7, under voltage events: 0, over voltage events: 0, power good: yes
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
Cache data hit count 140654521
Slowest loop: 5.06ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.1ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is ready with "m122" in state(s) 0
Aux is assembling a command in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.25ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

WiFi -
Network state is starting2
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok

3dpnut

I put the M552 S"Network" P"Password" in, and it says "ok", but doesn't give me the IP address...

Phaedrux

Send M552 by itself. It should respond with an IP address

If not, send M552 S1.

@3dpnut said in Duet 2 wifi not connecting to Paneldue 7i:

MCU temperature: min -72.1, current -67.6, max -65.6
Supply voltage: min 16.3, current 16.3, max 16.7, under voltage events: 0, over voltage events: 0, power good: yes

Seems like an off temperature for the MCU and odd voltage?

3dpnut

The MCU temp should read close to room temp, which is 69 deg F, any ideas why this reading? Also, I'm feeding in 24v (which I've checked and is correct), so no idea why it's reading 16v.

Phaedrux

Did M552 work?

droftarts

@3dpnut said in Duet 2 wifi not connecting to Paneldue 7i:

Also, I'm feeding in 24v (which I've checked and is correct), so no idea why it's reading 16v.

VIN is measured by feeding it through a voltage divider into an ADC input. So either the ADC in the microcontroller is faulty, or the ADC reference voltage (ADCVREF) is much higher than the intended 3.3V. You can measure ADCVREF, it's pin 41 on the expansion connector.

Is this a new board? Do you still get the same readings with the PanelDue disconnected?

Ian

dc42

The VIN reading reads low if you connect the PanelDue to the wrong connector. When using the ribbon cable it must be connected to CONN_SD, not CONN_LCD.

3dpnut

@Phaedrux This is what I'm getting:

M552
WiFi module is being started
ok
M552 s1
Turn off the current WiFi mode before selecting a new one
ok
M552 S0
ok
M552 S1
Turn off the current WiFi mode before selecting a new one
ok
M552 S0
ok
M552
WiFi module is being started
ok
M552 S1
Turn off the current WiFi mode before selecting a new one
ok

3dpnut

@dc42 Thank you! I made the change and now it's speaking to the Paneldue. Still no luck with the wifi tho

dc42

@3dpnut said in Duet 2 wifi not connecting to Paneldue 7i:

@dc42 Thank you! I made the change and now it's speaking to the Paneldue. Still no luck with the wifi tho

Please send M997 S1 from either USB or PanelDue to re-install the WiFi firmware. The message "WiFi module is being started" persisting usually means that the WiFi firmware is not running.

3dpnut

@dc42 I'm trying to load the results of M997 S1 and the subsequent M552's, but it blocking me as spam by Askimet.com

3dpnut

@dc42 I'll try again:

This is what I get after successfully running M997 S1:

95% complete
Upload successful
ok
M552 s1
ok
WiFi module started
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
M552 s0
ok
WiFi reported error: no known networks found
WiFi module is idle
M552 S1
ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle

Phaedrux

Ok, the no networks found means that you now need to give it a SSID and password for your wifi network using the M587 command.

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M587_Add_WiFi_host_network_to_remembered_list_or_list_remembered_networks

You should now be able to complete the getting connected guide

https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7#s9

3dpnut

Thanks all!! Everything is now working with the exception of a Z homing issue, which I think I can (hopefully :)) figure out. Have a great weekend!

3dpnut

I turned the machine on today, and it seems like I turned back the clock 2 weeks. The same thing is happening, not connecting to Wifi. I've run through the same cycles which fixed it last time, no luck. I ran M997 S1, and it re-installed the firmware fine. Then ran M552 S0, OK. Then M552 S1, OK. Then M587 S"xx" P"xx", and it says OK, then times out and says wifi module is idle. My computer is connected to the same network and is connected no problem. I double-checked the password and it's correct.

What am I doing wrong?

Phaedrux

If you send M587 by itself does it list back your network details?

3dpnut

Sends back:

6Dh 35h 38h 37h

Phaedrux

Are those SSIDs?

3dpnut

@Phaedrux I don't know what they are. I changed my terminal type from binary to text, and it's connected now. Previously I had to change it the other way for it to work...not sure what the correct setting is for that.

Phaedrux

I'm not sure what you're talking about, but it sounds like it's working now?