Fallback procedure #1 worked.... no idea why the normal procedure did not work

@DocTrucker said in "sudo apt dist-upgrade" Doesn't update main board?:

@jay_s_uk that got it, thanks.

Can someone update the documentation to add a note relating to this to step 6?

https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup

@droftarts Not a bad idea?

@FrodeBNilsen MIR is documented in the github link I posted in my reply: https://github.com/Apsu/Mir

See this video for a run on my prototype (would need proper re-engineering to work, time I dont seem to find): https://streamable.com/vczvhu

My config from back then is at https://github.com/oliof/printerconfigs/tree/main/minimir

Regarding larger PEI sheets: I got nothing on this, I am more into small printers.

@OwenD great - thank you

@dc42

Hi,

Recently I have tried to change this feeder motor from DC to Stepper motor. However i facing quite a challenge to operate the feeder motor in conrdination with the X,Y,Z axes.

So i am planning to revert back to the previous DC motor setup.

The PWM frequency of the OUTPUT Pins was not enough to vary the feedrate. I am not sure this could be a problem of the DC motor or something else. However this time i am planning to purchase a good specificaiton DC motor.

Request your feedback on the integration of this DC (specification link: https://www.igus.pt/product/MOT-EC-42-C-H-A?artnr=MOT-EC-42-C-H-A) to connect with OUT_1 and OUT_2

However other motor that are compatible and recommended can also be used

Requesting your insights on this issue plz....

@chrishamm
Thanks, works now!
...though it looked like and displayed Version 3.4.1 after the first start up 😄

@droftarts
thanks, i started a new topic as suggested
https://forum.duet3d.com/topic/34439/bed-heating-problem

@KenW

You brilliant bastards, you've done it again. This was it. Expansion board was slightly behind the mainboard. Thanks for all the great suggestions gang.

For future generations:

M115 to check mainboard firmware version.
M997 to update firmware on mainboard
M115 B1 to check firmware version on expansion board at CAN address 1.
M997 B1 to update the expansion board.

Thank you both! It turned out to be the change in the M593, input shaping. The discord helped me figure that one out. I didn't realize the old algorithm was not in the new firmware. I have an accelerometer coming so I can really tune it now. thank you both for the great hardware/software.

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