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
This was first noticed in PR #39 when the GPS altitude was being reported as -18 and 11574.799805 on different test builds. spkm and spkn were also reporting values greater than, or near, 1000 which means the GPS module must have been moving at that speed in km/hr.
One probable cause may be the power configuration. Right now the testing node is powered by the programmer as opposed to battery power. It has two ultrasonic sensors, a decagon, a DO sensor and (just recently) an autosampler attached.
The text was updated successfully, but these errors were encountered:
This was first noticed in PR #39 when the GPS altitude was being reported as
-18
and11574.799805
on different test builds. spkm and spkn were also reporting values greater than, or near, 1000 which means the GPS module must have been moving at that speed in km/hr.One probable cause may be the power configuration. Right now the testing node is powered by the programmer as opposed to battery power. It has two ultrasonic sensors, a decagon, a DO sensor and (just recently) an autosampler attached.
The text was updated successfully, but these errors were encountered: