Firmware update woes. Duet3
-
And CONGRATULATIONS and WOO HOO!!
By the way, you should never have to bossa or change feeds or anything again. From this point forward, it really is the two 'apt' commands.
-
@Danal said in Firmware update woes. Duet3:
If you run with the card in the Duet, you will need the ether plugged into the duet, and the enable command.
Yep thats exactly what I have setup. Card in the Duet, Duet hooked to ethernet, M552 S1 as the first line in config.g. Does not reconnect after restart. I think I might be leading us down an "XY problem here".
The whole reason for all of this is that M401 and any probe related macros dont work when I am connected through the pi. If I run the macros with M98, they work fine. If i run the commands that are in deployprobe.g, it works like a champ. IF on the other hand, I am in stand alone mode, then the M401 and G30 codes all work correctly. They just dont through the pi. Now thats not a big deal, if I can run in standalone mode, but as of now I cant, because it defaults to disabling the ethernet, and adding it to config.g doesnt seem to do anything.
Guys, I really am sorry this is such a pain, and I cant thank you enough for all the help.
-
WAIT I think I understand what you are trying so desperately to get through my thick head. Just enable ethernet through SSH like you would with any other pi. Standby as I try to be less mentally compromised and give that a go.
-
@Demi said in Firmware update woes. Duet3:
@Danal said in Firmware update woes. Duet3:
If you run with the card in the Duet, you will need the ether plugged into the duet, and the enable command.
Yep thats exactly what I have setup. Card in the Duet, Duet hooked to ethernet, M552 S1 as the first line in config.g. Does not reconnect after restart. I think I might be leading us down an "XY problem here".
The whole reason for all of this is that M401 and any probe related macros dont work when I am connected through the pi. If I run the macros with M98, they work fine. If i run the commands that are in deployprobe.g, it works like a champ. IF on the other hand, I am in stand alone mode, then the M401 and G30 codes all work correctly. They just dont through the pi. Now thats not a big deal, if I can run in standalone mode, but as of now I cant, because it defaults to disabling the ethernet, and adding it to config.g doesnt seem to do anything.
Guys, I really am sorry this is such a pain, and I cant thank you enough for all the help.
I think you will find that all cleaned up on this release. I run all that stuff on a D3+Pi toolchanger that is passing 10,000 toolchanges at the moment (I track for wear) each of which has to do what you are describing several times.
With one caveat: Check your macros after you switch back to the Pi... even though it is the same physical SD, stand-alone and Pi have separate places they store /sys, /macros, /gcode, etc, etc.
-
Good lord. Okay so just to try to get up and running in stand alone, I am flashing a new SD with the Duetpi-lite.zip from:
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_DuetPiPutting it right in the board and seeing if I can run stand alone with ethernet.
-
@Demi said in Firmware update woes. Duet3:
Good lord. Okay so just to try to get up and running in stand alone, I am flashing a new SD with the Duetpi-lite.zip from:
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_DuetPi
Putting it right in the board and seeing if I can run stand alone with ethernet.That image is still primarily for using the Duet3 with the Pi. To use wihtout the Pi you can use the same card but have to make sure to put config and duetwebcontrol files on the first FAT32 partition* (or simpler reformat the card so there is but one fat32 partition and put the files on there)
*) when the pi is running this is /boot
-
HOLY HELL! It works! I think I now know what I was doing wrong. With a fresh card, it connected straight away. As soon as I loaded my old config it wouldnt connect.....because I have the brain rot, and the old config wasnt for stand alone. YEESH. Everything works now. You guys are absolutely amazing, thank you so so much.
-
@Demi said in Firmware update woes. Duet3:
the old config wasnt for stand alone
there isn't much difference afaik.
heck if you add M552 S1 and put config.g in /boot/sys/config.g and symlink it to /opt/dsf/sd/sys/config.g it should (could?) work in both the pi and the Duet3 with no furhter changes but maybe not poke the bear if its working
(and you'd need to put all the other files and dwc into /boot/www etc) -
May I kindly ask, in the end do we have a instructions how to do it for dummies?
I kinda got to update mine duet 3 and reading this post is scary -
@monster said in Firmware update woes. Duet3:
May I kindly ask, in the end do we have a instructions how to do it for dummies?
I kinda got to update mine duet 3 and reading this post is scaryDuet 3 or Duet 3 + Raspberry Pi? (Also probably better to make a new thread to keep it easier to follow the information later)
-
There are a lot of horror stories when things get out of sync. These will go away as the procedure matures and people get more used to the procedure.
But... no fear!
The real procedure is:
sudo apt update sudo apt upgrade
With the one and only caveat that if you have multiple boards, you will need to M997 B1, B2, etc.
Other than that caveat, those two commands are really it. They will take care of everything for you.
Perhaps it is fair to say, that ONE TIME, you need to etch an SD image onto a card, and ONE TIME you need to choose whether to be on the 'stable' feed or the 'unstable' feed.
But, again, beyond those one time installation activities, it REALLY IS, those two commands.
-
@bearer said in Firmware update woes. Duet3:
Duet 3 or Duet 3 + Raspberry Pi? (Also probably better to make a new thread to keep it easier to follow the information later)
Duet 3 + Raspberry Pi it is! Shall it go to new thread then?
P.S. When I was beginning with it - I tried to flash SD card following some instructions. But I couldn't succeed with that card. Fortunately with card that came with Duet 3 it went better. Though I'm not sure is this information even relevant, you see this needs "for dummies" level instructions
-
@monster said in Firmware update woes. Duet3:
Duet 3 + Raspberry Pi it is! Shall it go to new thread then?
I suppose OP's issue is sorted but still adds noise for those who were following that thread. It also means you don't get a notification unless tagged or watching the topic. In general new problem = new topic is better.
But @Danal covered the Duet3 + Pi. Unless you already have a problem, or need to upgrade to the unstable (rightly named so) version,
sudo apt update && sudo apt upgrade
or on two lines, does the job reliably.