CubePilot ID_Cube programming

Mission Planner
1

I experienced a problem with my setups on the Cube Orange+ and the Cube ID-CAN using Mission Planner. I contacted the reseller and was told it was more of a software issue than a hardware problem, There is some truth, since I used Mission Planner to program the Cube.

The problem I encountered was the setup locked the wrong information in the Persistance.parm file after just enabling the DID_ENABLE. Some how it apparently loaded the the sample info from the Drone ID tab into the DID_UAS_ID perimeters in the Persistance.parm file, which I’m told I cannot change it.
What I thought was confusing is how did it set the information in the Persistance.parm file, since it did not set the DID_OPTIONS? So, since the Persistance.parm file is write protected, there is no changing the information, and I have to live with it.

2

@HDPilot the way to erase those persistent parameter would be to disable DID completely and do flash bootloader. Try this see if this works.

3

Thank you.
I did try that first, but it did not remove the file.
I was able to download the file which still had the test ID.

4

@HDPilot yeah, the persistent parameters are meant to be difficult to remove by mistake. you will need to build ardupilot firmware with define HAL_ENABLE_SAVE_PERSISTENT_PARAMS 0 in hwdef. And then do the flash bootloader.