Migrating to from 2.05.1 to 3.0 need help
-
So i bought a coreXY that was not printing so well so i have taken care of all the mechanical and got it printing real good.
Thing is i suck at software so i thought i could use the json file and use that as a guide for migrating over to 3.0. But it was for an old printer. But now i am realizing that that would not have helped me much since i could take all values from the regular config file anyways. Its when setting up heater and z brobe im lost. I have no clue what so ever what i should pick there. Like whats the difference between "beadheat" and "beadheat inverted" or one of the 30+ options for the sensor. Or when it comes to the Z-probe, no clue what to pick there either. I know the Bl touch is connected to 2 placed on the board but when looking on a diagram of the board its connected to z-probe port and expansion 2/6 for something. I cant use that and relate to the configurator.
No where can i find info about it either, so atm i am SOL. So hopefully no feature i will ever need will be added. Cause i am no software engineer
I might have spoken to soon. It all refers to the ports they are connected to and i think i figured it out. All but the modulation pin for the probe. Also have some issues with the fans. Not sure which one is which. I have one connected to fan 0 with 2 wires but on fan 1 its just 1 wire.
-
-
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
All but the modulation pin for the probe.
You don't need a modulation pin for BLTouch. Set it as 'unassigned'. You only need to set the 'Input Pin' and 'PWM Control Channel (BLTouch only)'.
Ian
-
I think i got most of the problems i had figured out but want to make sure before i load on the software and config. Would anyone be able to help me look over the 2 configs to see if i missed something in the new one? I know acceleration and stuff are not correct but those i can fix later. Are there more files needed that needed?
config OLD.g config.g to be compared?
-
@Alucardi
Witch version of BLTouch?
-
-
@Alucardi
Config should be O.K.
Have you also migrated the other files? Especially the homing-files?
-
@DIY-O-Sphere i have not. Do i need to change anything specific in them or can I just use the old files?
-
@DIY-O-Sphere I am unsure of the version. How can check that? I just know where it was connected.
-
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
i have not. Do i need to change anything specific in them or can I just use the old files?
Have you used the config tool for generating the files?
-
@DIY-O-Sphere 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?
-
@Alucardi said in Migrating to from 2.05.1 to 3.0 need help:
I am unsure of the version.
You can check the lable. For the "Smart" like in the picture your setup should be o.k. For the older ones you have to change it as I mentioned.
-
@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.
