Opps... How bad did I screw up my Duet2?
-
I just accidently uploaded a fresh default config from the RepRap Configurator for my Duet3 to my Duet2.
I still have RepRap v2.x on my Duet2....I realized I made this mistake right away (before rebooting it), and downloaded the config.g.bak file.
Found an old back up of my Duet2 from March and uploaded that. Put the config.g.bak file back on the Duet2 as the main config and rebooted the Duet2.Did I just save the printer after a big mistake? Or did I still do something bad to the Duet2?
I know some of my home config files are probably bad now as I do make tweaks fairly often....Sort of afraid to use it at the moment.... Anything I should check/confirm before I try to use the printer again?
Thanks! -
You should be fine. The config.g file is just g-code that runs on boot, so a wrong config file will just generate errors and not work correctly.
Its not possible to break anything that way.
-
@theruttmeister
I was worried there was other config files/firmware changes that may not be compatible and could do something bad after a reboot.... That's why I was in a hurry to put everything back as much as I could.
Sucks as I am in the middle of printing parts for a new printer right now for the Duet3 and now may have major troubleshooting to do to after work today/this weekend now. I couldn't tell you all the small changes/tweaks I have made over the last 6 months... -
Without knowing the differences between your printers... it could move in the wrong direction and things like that. But its not going to suddenly melt or anything.
The great thing about RRF2/3 is that its all gcode, so your config.g file is the config, theres no memory, no eprom stuff. And if you load a bad config.g, it will just not work. The bad commands get ignored the same way bad commands in a print file get ignored. The board is totally re-configured every time it boots.
Heck, if you were a crazy person who could figure out the mechanicals, you could have a printer that started as a coreXY, but then turned into a rotary delta part way though the print.
Isolate, substitute, verify.
-
config.g.bak is a copy of your config from before the last time you edited it and saved it. So you could have deleted the accidentally uploaded config.g and then renamed config.g.bak to config.g and your old config would have been returned.
This wouldn't help if you've also replaced the homing files when you uploaded. Those would need to be restored from a different backup or recreated.
It wouldn't hurt anything to upload the wrong config for the most part. Thermistors and heaters and endstops wouldn't work because the configuration is very different between rrf2 and rrf3.
-
@Phaedrux
From what I could tell, everything was replaced expect for the config.g.bak file.
I restored a full backup I took in March, and know I have tweaked the home files a bit since then...
So far printing OK, but know some things have changed but not impacting me enough to be a noticeable issue right now.
Thanks for the feedback. -
@theruttmeister said in Opps... How bad did I screw up my Duet2?:
. it could move in the wrong direction and things like that. But its not going to suddenly melt or anything.
The great thing about RRF2/3 is that its all gcode, so your config.g file is the config, theres no memory, no eprom stuff. And if you load a bad config.g, it will just not work. The bad commands get ignored the same way bad commands in a print file get ignored. The board is totally re-configured every time it boots.
Heck, if you were a crazy person who could figure out the mechanicals, you could have a printer that started as a coreXY, but then turned into a rotary delta part way though the print.I am building an IDEX printer with the Duet3, and my Duet2 is a CoreXY.
I feel like you are offering to build something cool, just be cause you can...
-
@BlueDust said
I feel like you are offering to build something cool, just be cause you can...
Well, if I could make a living just designing weird and wonderful 3d printers, that would be fun.
I'm stuck just designing fairly straight forward ones instead
