Migrating to from 2.05.1 to 3.0 need help
-
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
yes I did. I have not compared all the files if previous owner had some custom code in them though.
Want me to zip em all down for comparison?Then they are migrated and should work. But if you like you can do that.
-
@DIY-O-Sphere everything is so big and new when it comes to reprap cause there is a lack of guides compared to marlin, that is explaining everything. But if you acctualy sit down and thing about it’s not that hard. I was over whelmed trying to configure 3.0 cause I was trying to figure everything out at ones. But as soon as I focused on just one section at a time I could get it configured in like 30 minutes.
When you overcome that reprap is so superior compared to marlin. Especially when tuning the printer. The ability to fine tune the printer is so much easier. No need to compile software all the time. Having a connected yes printer to without octoprint is a big bonus to. Fiddling with this has made to consider going to reprap for my prusa to.
-
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
But as soon as I focused on just one section at a time I could get it configured in like 30 minutes.
That's the right track...
-
@DIY-O-Sphere said in Migrating to from 2.05.1 to 3.0 need help:
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
yes I did. I have not compared all the files if previous owner had some custom code in them though.
Want me to zip em all down for comparison?Then they are migrated and should work. But if you like you can do that.
I just did a check on beg.g and deployprobe.g and they are not even remotely close toe achother. Can i just keep the other files or i need to look for code that wont work i 3.0? Basically all files are different compared to the generated files.
Also the bl touch is har to see the backside of but it said v2.1 so guess i have a v2 right?
-
@Alucardi
Use the new files. The only thing is to adapt bed.g depending on you requirements for mesh compansation. But that can be done later on....
For the BLTouch add the "^" as mentioned, than you are ready for a test...
Have you already updated the DWC to 2.0.7? -
@DIY-O-Sphere that is updated. But why are so many files different? Like my homing files are also different. I don’t want the printer to behave differently.
If all goes to shit can I downgrade? -
@Alucardi
You will manage to adapt them... -
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
Like my homing files are also different.
If you have set the bed limits correct in the config tool the new ones will work...
-
@DIY-O-Sphere I understand they will work but will all be the same? Cause when it comes to homing I have a lot more code in my old files. I need the printer so can’t sit for days trying to get it back as it was if I can’t downgrade back on firmware.
-
@Alucardi
It will not take days....But If you feel better you can upload the files...
And yes a downgrad is also possible.
But please pay attention to https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware -
You've asked twice if you can downgrade... the solid answer is YES.
The very best way is to be sure you have a backup of your entire /sys directory. All of it. (Also the macro directory, just in case).
To backout, the high-level idea is:
- Restore the /sys directory.
- Follow documentation to load firmware (depending on board, load main board, WiFi, etc)
- Follow documentation to load correct (your past) Duet Web Control
That's it. By restoring /sys, you should have both the binary that will get loaded into the actual board, and all your config and bed and so forth, all your "dot g" files.
You will be right back where you started.
-
Actually, the VERY best way is to copy the SD card before you start the upgrade.....
-
@Danal that I have done.
-
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
@Danal that I have done.
Good! Then backout is even more certain. If needed, insert that card, and issue commands to load firmware onto boards. That's it.
-
@Danal said in Migrating to from 2.05.1 to 3.0 need help:
If needed, insert that card, and issue commands to load firmware onto boards. That's it.
Sorry Danal, but for the downgrade you also need an additional bin witch is not pressent on the old card.
That was the reason why I have pointed to the guide..@Alucardi
Anyway.
Believing in yourself (or in us), we will get the update done....Edit:
@Danal
Downgrade might get a challege if someone has overlooked that....
Out of the guide:
Also copy file iap4e.bin (for Duet WiFi/Ethernet) or iap4s.bin (for Duet Maestro) into /sys -
@DIY-O-Sphere il see if I can get it done tonight or tomorrow.
-
@Alucardi
Just one last info. In case you have overlooked that....
If you would like to upgrade directly from RRF2 to a higher version than 3.01-RC3, you must upgrade to the 3.0 release first. -
@DIY-O-Sphere just going to 3.0. Not gonna bother with rc releases atm. I just want to have the printer up to speed with 3.0.
-
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
@DIY-O-Sphere just going to 3.0. Not gonna bother with rc releases atm. I just want to have the printer up to speed with 3.0.
IMHO, that's a mistake. You might as well stick with 2.x, if you are not going to 3.0 RC4 or RC5. There really has been that much change since 3.0.
-
@Danal I want to be able to update if there is a upgrade that I want. Going to 3.0 saves me the trouble next time I want an upgrade.