[John BenacParticipant]

OK. I just wanted to make sure that I wasn’t going to mess up the calibration on accident. The WRITE_TO_FACTORY register is not even published, so I don’t think that anyone will do that.

[John BenacParticipant]

ok. Not that I ever would, but I could mess up the calibration if I changed the advanced settings with the CHR Serial Interface, right?

And If I did ever do that, would RESET_TO_FACTORY fix the calibration back to the factory calibration, or would that be broken forever?

• This reply was modified 5 months ago by  John Benac.

[John BenacParticipant]

OK, so in the example of 0x736E70CC78F2FE008BC0D7000044596B0CBB07, according to the information in the datasheet, I would interpret this as meaning:

“736E70” is SNP,
“CC” is information about the packet, being translated from hex to binary as 11001100 and meaning (1XXXXXXX) has data, (X1XXXXXX) is a batch, (XX0011XX) batch length is three, (XXXXXX0X) it is not hidden, and (XXXXXXX0) the command has not failed.
“78” is the one and only time that a registry is named in this package
“F2FE” is roll,
“008B” is pitch, completing the information in registry 78. We know that 79 is the next registry to come, because it is the next registry of a total of three starting with 78.
“C0D7” is yaw from 79,
“0000” are the unused bits identified for registry 79. this ends registry 79 and we now start registry 7A.
“44596B0C” is the time.
“BB07” is the checksum.

[John BenacParticipant]

How can I get all the registers in the log generated by the CH Robotics configuration utility?

[Author]

Posts