New Configurations not Being Saved in RoboRun+ and Unable to Load Configuration

I have 4 MDC 2230s we have been using for our robot for half a year now and they are suddenly not taking new configurations nor are they able to load their current configuration. I connect to them through the RoboRun Utility and go to the configuration tab. I make any necessary configuration changes, like power adjust and activating some analog and digital-in pins. I then click save to controller and it says saved successfully... However when I then plug in the next Roboteq and click Load From controller it shows the exact same configuration as the last one. If I make a change and go back to the last one I had plugged in it will still just show whatever I last had on RoboRun. It seems like nothing is getting saved/read from the controllers and I am not sure why.

Could someone help me with this issue it is a very critical issue since we have a competition in a couple weeks.

Do you write to flash memory from a script very often?

It couldn't have been more than 100 times I have loaded a new configuration onto these Roboteqs. They also have all been used a different amount so I don't think all the flash chips would suddenly fry.

Hmm, yes this is puzzling. I didn't realize that you were referring to all 4 controllers. Most likely you have something going on with your computer driver. Is it possible to test on another computer?

So I figured out what the issue was. I thought that naming pins would be Controller specific however it is client side specific. So when I was looking at the configuration I was very confused on why the pins were named the same as the last one. What I learned: pin names are stored in Roborun+ and not on the controller

Ah, I see. Yes, the pin naming is simply a label for convenience while you are using the software utility.