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
The Novatel_OEM615 device seems to have some layover code from Sample, specifically around HK and config commands, where they seem to be set up similarly/the same to sample, but without some necessary distinctions set up (command codes don't seem referenced, split off in a different CommandDevice method from the CommandDeviceCustom method that has the rest of the real commands (log, unlog, unlog-all). The necessity of device HK and config should be reevaluated, and the methods should be cleaned up, consolidated, and fixed as necessary.
Running with cFS, it seems that the Device Count works, Device Counter sticks at 0, and Device Error Count rapidly increases from 0 to near 256 (max count? Not sure) before resetting to 0. This behavior all seems improper.
The text was updated successfully, but these errors were encountered:
The Novatel_OEM615 device seems to have some layover code from Sample, specifically around HK and config commands, where they seem to be set up similarly/the same to sample, but without some necessary distinctions set up (command codes don't seem referenced, split off in a different CommandDevice method from the CommandDeviceCustom method that has the rest of the real commands (log, unlog, unlog-all). The necessity of device HK and config should be reevaluated, and the methods should be cleaned up, consolidated, and fixed as necessary.
Running with cFS, it seems that the Device Count works, Device Counter sticks at 0, and Device Error Count rapidly increases from 0 to near 256 (max count? Not sure) before resetting to 0. This behavior all seems improper.
The text was updated successfully, but these errors were encountered: