cannot connect to duet 2 Wi-Fi or board

Blunt2007

@droftarts I was wondering if you ended up getting the photos that you requested if you're able to view them

Phaedrux

What are you getting in YAT when you try to connect?

droftarts

@Blunt2007 Yes, they got forwarded on to me, but they are the same as you posted.

In the picture of YAT from your post, it says this at the bottom:

Did you do this:

Connect to Duet
YAT
Select "Terminal" menu, then "Open/Start" to connect to your Duet. Or click the green tick in the tool bar.

Did the message in the bottom bar change, and if so, what to?

Ian

Blunt2007

@droftarts in yat. Terminal menu to open Stark tab is not activated in other words is it's in gray because at the very top it says closed waiting for reconnect. I even tried closing that one and opening a new one and it comes up the same way this board is defective is it possible I can get a email from duet 3D stating that this board is defective so I can return it and get another one. Printed solution does not stand behind the product they sell they're requiring me to contact you guys and get a letter saying that board needs to be replaced before they'll do anything it's almost Christmas time and I'll be lucky if I get another board by then this board is not doing what it's supposed to do it is a defective board

droftarts

@Blunt2007 This is how the warranty process works. Once we've done troubleshooting, and worked out where the problem is, and if it is not fixable, we'll issue a warranty. We don't send a letter, just an online form for you to fill in, and you reference this thread so we can see the problem with the board when it is returned, and see the troubleshooting steps that have been taken.

It is usually quicker for you, the user, to bear with us and try and fix the problem. Because replacing the board takes time. A hardware fault is pretty rare; the boards go through extensive testing in the factory.

I'm still not convinced the problem is with the Duet. I've never known for the Duet to report correctly in the Device Manager, and yet not be able to connect. The problem is usually with Windows, that you don't have the privileges to access the board, or Windows is running YAT in protected mode. Replacing the board may just put you back at square one, unable to connect. I have asked my colleagues to look at this problem. The only current suggestion is to erase the board and reflash the firmware, but I'm concerned that if we do that, and you can't connect to the board, then you can't even get it working any other way, and it will have to be replaced.

In an earlier post, you said:

I cannot access the board so I cannot upload g code to it

You can. You can eject the SD card from it, and put it in your PC, assuming you have an SD card reader. Then you can edit the files on the SD card, and put it back in the Duet. If you set up the runonce.g file like I said, and edit config.g as it says in the 'Getting connected' guide (see this part https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#h-7-ensure-future-connectivity), that should connect to your WiFi (not wife).

If you want to try erasing the board and reflashing the firmware, follow the instructions here: https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2
Use the 'Duet2CombinedFirmware.bin' firmware file from the 3.4.6 release.

Ian

Blunt2007

@droftarts
Okay I tried closing it and then clicking open and start and it goes back to the same thing closed waiting for connect okay what do you recommend for me to do

Blunt2007

@droftarts I do have an SD card reader The files that are on the SD card says they want to open with unimaker cure what program do you recommend so I can read the SD card and write g code in it since I cannot connect to the motherboard by a USB and I cannot connect by Wi-Fi what do you recommend I do.

droftarts

@Blunt2007 try setting up the WiFi using runonce.g, before going the erase firmware route.

Use Windows Notepad. The files have .g endings for gcode, but they are just text documents. Just make sure the files you create are 'runonce.g' not 'runonce.g.txt', and that they are plain text files.

Ian

Blunt2007

@droftarts okay I'm going to use notepad I'll get back to you in a little while probably tomorrow

Blunt2007

@droftarts awesome I got the board to connect to Wi-Fi by using the code you gave me thank you very much for your help much appreciative I got one more question I'm getting notification that it keeps on losing Wi-Fi and has to reconnect to it if I increase bandwidth will that help to keep connected to the board once again I thank you so much I was wrong this board is working now and it connects to Yat. I am getting a green light now and it connects to Wi-Fi

Blunt2007

@droftarts a crud I disconnected from the Wi-Fi unplug the board and then plugged it back in and now it will not connect to Wi-Fi and it will not show a green light in yat. It worked last night but this morning when I connected it it will not connect to the Wi-Fi

Blunt2007

@droftarts when I go into the browser to click on the link that was left there from last night it's coming up with a 404 page not found and in device manager it is showing up on com4 same as last night

droftarts

@Blunt2007
For YAT:

Try starting Windows in Safe Mode, which should stop any other application from taking over the COM port. See https://support.microsoft.com/en-us/windows/find-safe-mode-and-other-startup-settings-in-windows-10-7551aac3-21b5-c646-06ee-31e0e6a5e4dc
Is the USB cable pushed fully in to the Duet? It may not be making a good connections. Be careful when inserting the cable though, as it is possible to rip the USB port off the Duet, especially if you don't push the cable straight into the port.
If you think the USB port is damaged, take close up picture of the back of the port, where the soldered connections are, and post it here so we can see.
Is the Duet powered only by USB? It can cause problems if you connect the mains power and USB at the same time, and the mains power is poorly earthed. See https://docs.duet3d.com/en/User_manual/Overview/USB_ground_loops

For WiFi:

If the green light next to the WiFi module is on solidly, it has connected to WiFi.
Did you use an IP address, or duettest.local to connect to it?
Does your Duet 2 WiFi have an external aerial, and have you connected it?
For general WiFi troubleshooting, see https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshooting
If you can connect via YAT, send M122 for a system report. The last section shows WiFi details. Copy and paste that into your reply.

Ian

Phaedrux

@Blunt2007 said in cannot connect to duet 2 Wi-Fi or board:

@droftarts a crud I disconnected from the Wi-Fi unplug the board and then plugged it back in and now it will not connect to Wi-Fi and it will not show a green light in yat. It worked last night but this morning when I connected it it will not connect to the Wi-Fi

Your config.g file will require M552 S1 in it to reconnect to the wifi at startup.

Blunt2007

@Phaedrux I am still at the point of trying to get connected to the board USB is only power going to the board. I pulled the SD card out and put it in my computer and reload it "runonce.g"onto the SD card under config g and it booted up and I was able to connect to Wi-Fi again. I shut it down letting it sit overnight and then I'm going to plug it in again to see if it reestablishes Wi-Fi again I will give you an update tomorrow if it works or or if it doesn't work. If it doesn't work I will reboot the computer in safe mode and try it then

Phaedrux

@Blunt2007 said in cannot connect to duet 2 Wi-Fi or board:

see if it reestablishes Wi-Fi again

It won't automatically connect to wifi unless M552 S1 is present in config.g

droftarts

@Blunt2007 as @Phaedrux said, on the SD card, in the /sys folder, config.g should have M552 S1 in it. If it does, and the WiFi still does not start when the Duet is powered up, copy the config.g file off the SD card on your computer, and post it here.

Because the runonce.g file worked, and you could connect to DWC, I don’t think the problem is with the SD card or SD card socket, but possibly a corrupt config.g is causing problems.

Another thing to try is to remove the SD card, then power the Duet, and try connecting via YAT.

Lastly, if you do connect, either by YAT or WiFi, send M122 and post the result here. In DWC (the WiFi interface) click on ‘Console’ and enter M122 there. See https://docs.duet3d.com/en/User_manual/Reference/Duet_Web_Control_Manual#console for a guide.

Ian

Blunt2007

@droftarts okay here we go again. I connected the board using USB it connected to Wi-Fi .I unplugged the USB .hooked up my power supply turned on power supply it connected to Wi-Fi and I was able to select different options then it lost signal and would not reconnect I tried shutting off power supply and returned it on and Will not connect Wi-Fi under power supply unplugged power supply .plugged USB back in with power supply off it comes up in device manager and now will not connect Wi-Fi

Blunt2007

@droftarts hear the post M122.
12/15/2023, 6:03:46 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JTD4-3SN6K-9U4LK
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75072 of which 24 recycled
Never used RAM 15444, free system stack 184 words
Tasks: NETWORK(ready,12.4%,244) HEAT(delaying,0.0%,346) Move(notifyWait,0.1%,364) MAIN(running,84.7%,443) IDLE(ready,2.7%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:34 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,570
Step timer max interval 0
MCU temperature: min 38.5, current 41.4, max 41.7
Supply voltage: min 24.2, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2023-12-15 18:03:46
Cache data hit count 1246170868
Slowest loop: 2.04ms; fastest: 0.17ms
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 9.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 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 idle 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
LCD 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: 15.96ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address c8:c9:a3:40:90:59
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 25560
WiFi IP address 192.168.1.21
WiFi signal strength -19dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
12/15/2023, 6:03:32 PM Connected to 192.168.1.21

Blunt2007

@droftarts to get the board working again I had to reload "runonce.g"