Invalid output when using ERB protocol

I have tried connecting a Reach module to a Pixhawk but was unable to get a GPS fix. I then connected the Reach module directly to a PC in order to examine the output. I can see that if use NMEA as output I get a valid position, but if I switch to ERB, I get lat/lng values very close to 0 and no satellites in view. I suppose this could explain why I can’t get a GPS fix when connecting it to the Pixhawk. Am I missing some configuration in Mission Planner or on the Reach module?

/Jesper

An example of the messages I receive as HEX:
455201070086420700000100D8A4
4552021C0086420700BB31DD05C331E721962201009622010000000000000000002972
455203090086420700770701010E6900
4552040C00864207000000000000000000DF48
4552051C00864207003800000004000000B2FFFFFF38000000C3FE8200000000005673
45520605008642070000DA0E
455201070087420700000100D9AB
4552021C00874207009D31DD056132E7214A2901004A2901000000000000000000218F
455203090087420700770701010E6A09
4552040C00874207000000000000000000E054
4552051C0087420700F3FFFFFFFCFFFFFF0A0000000D000000ACDA59FF00000000CFF6
45520605008742070000DB13
455201070088420700000100DAB2
4552021C00884207009B31DD05E031E721B33D0100B33D0100000000000000000098D8
455203090088420700770701010E6B12
4552040C00884207000000000000000000E160
4552051C00884207002F00000001000000B1FFFFFF2F000000D36A870000000000C3AD
45520605008842070000DC18

Hi!

What ReachView version do you have? We fixed a couple of bugs in v0.4.9.

I updated to 0.4.7 around two weeks ago, I hadn’t noticed that a new version had been released. I will perform another update and see if that fixes the issue. Thanks!

/Jesper

That fixed our problem! :slight_smile:

1 Like

Good to know!