Boneill3
commented
3 years ago Is it always in decimal?
On Sat, Aug 28, 2021 at 1:03 PM Ryan Medick @.***> wrote:
Describe the bug The star tracker is showing up as 0x30 in the display, even though canopen-monitor has its dcf in it's cache.
To Reproduce Steps to reproduce the behavior:
- Start the star tracker on MDC.
Expected behavior It should printing Star Tracker not 0x30
Environment (please complete the following information): MDC
Additional context If i had to guess the canopen-monitor is assuming that the NodeId under [DeviceComissioning] is in hex, when it really is a decimal.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/oresat/CANopen-monitor/issues/74, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABCAYVBMKAHJVDQCZEBJBPLT7E6IHANCNFSM5C7N7XKA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
ryanpdx
Describe the bug The star tracker is showing up as 0x30 in the display, even though canopen-monitor has its dcf in it's cache.
To Reproduce Steps to reproduce the behavior:
Expected behavior It should printing
Star Trackernot0x30Environment (please complete the following information): MDC
Additional context If i had to guess the canopen-monitor is assuming that the
NodeIdunder[DeviceComissioning]is in hex, when it really is a decimal.