@jay_s_uk Ok thanks so much for taking the time to look at it, really appreciate it.

Thanks
David

@dc42 said in Duet mini keeps restarting if the toolboard is missing:

@Aurimas thanks for confirming. The problem occurred when a filament monitor was configured on a missing expansion board.

as long as it is not me it is all good 🙂
thanks again

@droftarts said in Brand New Duet 3 Mini 5+ - Wifi Issues and Bogus IP:

@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.

WiFi firmware 1.27 is the latest release version; you are on 1.26. Update with the ‘DuetWifiServer.bin’ file from the ‘Duet2and3Firmware-3.4.6.zip’ file in the RRF 3.4.6 release here: https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.6

1.26 worked fine afterall and if I'm not wrong this was what came out of the 3.4.6 zip but I'll double check!

Anyways thanks for all the help and suggestions @droftarts @fcwilt

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

@mesacrash https://configtool.reprapfirmware.org/Start

@KenW no, that's unconnected

Cool. Thank you. Now I understand.

@Phaedrux, I can confirm using it (1.26.1 RRF and DWC 2.07) on my Duet 0.6

@oozeBot You are quite correct. I did look up the gcode dictionary but was too busy looking at the number to notice the letter had changed.

Many thanks!!!!

@Phaedrux Brilliant - that sorted it. I used the wifi server from 3.4.6.

Thanks again.

@dc42

Thank you very much, that was the problem, I declared the set drive mapping before and everything was solved.

fda35897-ecd8-4253-8c34-6b75a34411ab-imagen.png

What procedure are you using to flash the Duet?

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2

This one should get you back up and running. If still not, see this guide.

https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

@johndonges 3.4.6 is a bug fix of 3.4.5, so there's nothing that would cause any problems like that. Check the SD card hasn't been popped out when you were plugging in the USB lead.

Ian

@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.

Ian

@Massimiliano1991 said in Sensorless homing without z probe:

what i've not found is the height offset between the nozzle and the probe, does it exist or is like a bit of trial and error?

It's the previous section in the link I already posted: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing#calibrate-the-z-probe-trigger-height

Ian

@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.

@axiom look at Phaedrux post https://forum.duet3d.com/topic/15030/can-t-access-wifi/32

You can create a file with the SSID and password in it and run that to provision the new board.

@Phaedrux thanks! That helped a lot 😉

@droftarts

Again, very helpful. Thank You

@droftarts

Thanks. Based on what I read that is what I thought should appear... However.. this is what I have.

DWC.jpg

firmware.jpg

Accelerometer.jpg

As noted, when I did install Input Shaping plugin as an external plugin and activated it it does work.

Any suggestions?

Thanks

@Rein3003 best to just sudo apt update && sudo apt upgrade -y