pAcommsHandler will not read IN_*_HEX* variables properly

Bug #792025 reported by toby schneider
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Goby
Fix Released
Medium
toby schneider
1.0
Fix Released
Medium
toby schneider

Bug Description

If incoming hex MOOS variables (e.g. IN_LAMSS_STATUS_HEX_32B) are manually published (using a MOOS Poke utility like uPokeDB) or from another community via wireless (pMOOSBridge), pAcommsHandler will fail to decode them. This is due to the bug where ModemTransmission::ParseFromString() (which expects a protobuf byte-serialized string) is being called instead of parse_for_moos() (which expects a Google Protobuf TextFormat string.

Related branches

toby schneider (tes)
no longer affects: goby/2.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.