M2 on Cube Pilot Orange

Reach Module / M+ / M2 Hardware integration
1

Hello ,

I got a RS2 & M2 combo and am trying to install it on a cube pilot Orange.

From the post (i wish it was on the docs also) it seems i only need to connect RX > TX and TX >RX on the UART GPS of the FC . Which is what ive done, connected just those 2 cables and then a 5V.

i can connect from reachView3 see satellites etc but i don’t see it working on mission planner, i have a gpsstatus2 = 0 and gpshdop = 655.35

From the posts i saw the type should me NMEA but i have tested also what the docs write as ERB

Any ideas what am doing wrong ?

Thank you for your time,
Best!

3

Hi @firebblade,

We have the guide describing integration with Ardupilot. It also contains info about sending corrections via Mission Planner, you probably don’t need that, but it still can be useful.

I’d check the baud rate first. The Mission Planner SERIAL4_BAUD parameter should match the baud rate value you set in ReachView 3.

5

Hello @svetlana.nikolenko ,

Thank you for your reply !

I have been through the docs and through the previous posts with similar issue .

I have tried setting same Braud rates (19200, 38400 57600) in the 3 different places :

  • mission planner serial4_baud
  • in the receiver reachView3>Correction Input>serial
  • in the receiver reachView3>settings>position streaming 1

Then i tried with changing in mission planner and in reach the ERB to NMEA and then tried the above BAUD rates in the appropriate settings , still i get a GPS Status2 == 0

i see i get a solution from the app but i see nothing in mission planner. i even removed the first gps but then i just get a safety error for not having any gps

Best!

7

I just noticed you didn’t mention GND here. Did you connect it? It’s required too.

8

Hello @svetlana.nikolenko ,

You are right i was not connecting the ground cable !

I did connect it and did tests with current settings :

  • mission planner serial4_baud >>>> 57
  • mission planner gps_type2 >>>> ERB
  • in the receiver reachView3>Correction Input>serial >>>> 57
  • in the receiver reachView3>settings>position streaming 1 >>>> 57 on ERB
  • mission planner serial4_type >>>> 5
  • mission planner serial4_baud >>>> 57
  • mission planner gps_type2 >>>> NMEA
  • in the receiver reachView3>Correction Input>serial >>>> 57
  • in the receiver reachView3>settings>position streaming 1 >>>> 57 on NMEA
  • mission planner serial4_type >>>> 5
  • mission planner serial4_baud >>>> 57
  • mission planner gps_type2 >>>> NMEA
  • in the receiver reachView3>Correction Input>serial >>>> 57
  • in the receiver reachView3>settings>position streaming 1 >>>> 57 on NMEA
  • mission planner serial4_type >>>> 20
  • mission planner serial4_baud >>>> 38
  • mission planner gps_type2 >>>> NMEA
  • in the receiver reachView3>Correction Input>serial >>>> 38
  • in the receiver reachView3>settings>position streaming 1 >>>> 38 on NMEA
  • mission planner serial4_type >>>> 20
  • mission planner serial4_baud >>>> 38
  • mission planner gps_type2 >>>> NMEA
  • in the receiver reachView3>Correction Input>serial >>>> 38
  • in the receiver reachView3>settings>position streaming 1 >>>> 38 on NMEA
  • mission planner serial4_type >>>> 5
  • mission planner serial4_baud >>>> 38
  • mission planner gps_type2 >>>> ERB
  • in the receiver reachView3>Correction Input>serial >>>> 38
  • in the receiver reachView3>settings>position streaming 1 >>>> 38 on ERB
  • mission planner serial4_type >>>> 5

i also checked my cables with a multimeter and it looks the connections are fine .

Please advice what other setting could be causing an issue ?

I should be able to see gpsstatus2 and hdop2 in mission planner right ?

Thank you,
Best!

9

Hello @svetlana.nikolenko ,

i found this which fixed my issue :

serial3 needs to -1 so serial4 an pick up the gps2.

Thank you for your help,
Best!

10

Wow, it was unobvious. Thanks for sharing this! It’s very useful to know these features of 3rd-party devices.

2 Likes
12

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.