this is the discrepancy I see in the returned data. below I have mapped (based on documented data types) of returned values. there is a gap in the middle of the returned values that contains undefined bytes of data... any insight would be helpful. thanks
header 3E 21 68 FFFFFF89 profile 0 notch freq1 0 notch width1 0 notch freq2 0 notch width2 0 notch freq3 0 notch width3 0 lpf freqs 0 0 0 0 0 0 filter en 0 0 0 enc offset 0 0 0 0 0 0 enc fld offset 0 0 0 0 0 0 enc man set tim 0 0 0 mot heat fac 0 0 0 mot cool fac 0 0 0 reserved 0 0 0 mot mag lnk 0 0 0 mot gearing 0 0 0 0 0 0 enc limit min 0 0 0 enc limit max 0 0 0 ---------------------------------------------- not sure what these bytes are but they are throwing my data off????? 0 1 0 1 0 1 0 0 0 0 0 0
notch gain1? 64 64 64 notch gain2? 64 64 64 notch gain3? 64 64 64 ---------------------------------------------- beeper vol FFFFFFFF enc gear ratio 0 0 0 0 0 0 enc typ F F F enc cfg 0 0 0 outer p 19 19 19 outer I 19 19 19 mag axis top 1 mag axis right FFFFFFFD mag trust 32 mag declination C reserved2 0 0 0 0 0 checksum????? FFFFFF85
I have not been using Serial Api for long time, but will again soon. However this sounds like it could be a bug, anyway something that Aleksey hopefully takes a look at.