@marcossf I am sorry but I cannot reproduce this problem on my Duet 3 Mini 5+ WiFi. Please make sure you have DuetWiFiSocketServer version 1.27 installed. If that is the case and the issue persists, open a new thread about this problem.
The firmware binary files go in the /firmware folder. However, so long as you haven’t deleted the firmware from the 6HC, you don’t need them. The Duet runs the same firmware for standalone and SBC, so you shouldn’t need to update the firmware to get it working. Indeed, if you have a Mac, DON’T erase the firmware; flashing firmware on 6HC using bossac on Mac is currently not working. Though you can use an RPi to do it.
@ozgunkilicafsar if you’re using a Mac to connect to your Duet via USB, are you using SerialTools app to connect? SerialTools can be a bit flaky sending commands. I notice there wasn’t an ‘ok’ response to the M558 S"*" command; if a command goes through correctly, you should always get an ‘ok’. I use Coolterm on Mac now, with the options for ‘line mode’ and ‘local echo’ turned on, which is more reliable. It isn’t available through the App Store though.
Thanks @droftarts this is actually what saved me! It was SerialTools that was the main issue. Thank you so much! And it turns out my old board's wifi is also working just fine! It was again thanks to this that solved the mystery! So happy!
In this command
M587 S”mynetworkssid" P”mypassword”
Yeah this just happened during copy and paste, I confirm that I used straight quotation marks at all times.
you have used curly quotes, not straight quotes. All commands must be sent with straight quotes. Again, there was no ‘ok’ returned.
I suspect that the stored WiFi SSID is the one used for testing at the factory. Delete it with M588 S"*" then put in your SSID and password with M587.
I guess it was so when I transferred to Coolterm M588 was also received fine so this is also figured and I deleted all the old SSIDs stored.
Final takeaway was that both Coolterm (MAC) as well as YAT (Windows) worked best for me in this process of debugging wifi issues. I personally do not recommend SerialTools anymore with the amount of struggle it caused with wifi setup.
@droftarts Hi Ian, I found the error, it was between the ears (my ears). I should have read more carefully. I hadn't paid attention to the fact that the first thing I had to do was upload a file using Bossa. After that everything worked fine. It was the file "Duet2CombinedFirmware.bin"
I'm sorry for having to employ you for nothing, but you still helped me, otherwise I wouldn't have read the documentation again.
Thank You and Greetings Harald
@Milke If you are on 3.1.1, the instructions say to update to 3.3, then a later version. Realistically, you don't need to; you can go from 3.1.1 direct to 3.4.6 (the current release version).
Download the 'Duet2and3Firmware-3.4.6.zip' from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.6
Upload it to the Duet. As you are on 3.1.1, this will put all the firmware files in the /sys folder
Let the Duet update the firmware
Occasionally, updating the WiFi firmware fails, and you can't connect to the Duet. Connect using YAT via USB, and send M997 S1 P"0:/sys/DuetWiFiServer.bin" to update the WiFi firmware.
Connect to the Duet via DWC. Check that the firmware and DWC are on version 3.4.6.
Upload 'Duet2and3Firmware-3.4.6.zip' again. This will create the ‘0:/firmware/’ directory, and put all the firmware files in it. You can delete the firmware files from the /sys folder.
@o_lampe RRF already supported torque mode for Hangprinter version 4, which uses O-drives. It may be that in future it will be possible to use Duet3D closed loop drivers instead of O-Drives in a Hangprinter.