You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugSomething isn't workingbug-minLikely inconsequential that shouldn't affect any aspect of mission, even nominal ones.smallOnly several lines of code and quick to test.WDCode changes to the WatchDog
For some reason the thermistor data in the WD's DetailedStatus packets are wrong (always 1), specifically BattRT (the battery thermistor). No idea why. Data comes through just fine in the heartbeats. Could suggest a broader formatting issue with DetailedStatus but bit-boundaries in the packet have been thoroughly tested and all the other fields have change when and how they are expected to in all other testing.
Low priority because we already have this data coming down in heartbeats.
NOTE from #196 :
Plugged a 5k resistor (i.e. 25C or 298K) into RT port. Heating status changed to NOT_HEATING (suggesting that the WD sees a new ADC value) butTbatt in DetailedStatus stayed at 1, suggesting a data packing issue. BattTemp in Heartbeat and in Hercules telem incorrectly reported charging thermistor instead of main battery thermistor, so it's possible this is just a detailed status data packing issue.
Thoroughly re-test all DetailedStatus downlink fields before merging if any changes were made to how it's packed.
The text was updated successfully, but these errors were encountered:
zCoCo
added
bug
Something isn't working
small
Only several lines of code and quick to test.
WD
Code changes to the WatchDog
bug-min
Likely inconsequential that shouldn't affect any aspect of mission, even nominal ones.
labels
Mar 1, 2023
bugSomething isn't workingbug-minLikely inconsequential that shouldn't affect any aspect of mission, even nominal ones.smallOnly several lines of code and quick to test.WDCode changes to the WatchDog
For some reason the thermistor data in the WD's
DetailedStatus
packets are wrong (always 1), specificallyBattRT
(the battery thermistor). No idea why. Data comes through just fine in the heartbeats. Could suggest a broader formatting issue withDetailedStatus
but bit-boundaries in the packet have been thoroughly tested and all the other fields have change when and how they are expected to in all other testing.Low priority because we already have this data coming down in heartbeats.
NOTE from #196 :
Plugged a 5k resistor (i.e. 25C or 298K) into RT port. Heating status changed to
NOT_HEATING
(suggesting that the WD sees a new ADC value) butTbatt
inDetailedStatus
stayed at1
, suggesting a data packing issue.BattTemp
inHeartbeat
and inHercules
telem incorrectly reported charging thermistor instead of main battery thermistor, so it's possible this is just a detailed status data packing issue.See #206 . Might be related...
The text was updated successfully, but these errors were encountered: