Disregard tape base & Rover ,I don’t know which is which now if autopilot determines.
I think you need to flip-flop the blue and yellow wires on one side of each GH connector.
In other words, the wire colors should be in identical order on every termination.
Your tape labels are correct based on the last parameters I saw. GPS1 is the moving base (the one with protocol 17).
Thanks Yuri, I need to have Steve Johnson check his wiring diagram again. I had mine wired exactly. In his defense if it is correct the pin out he has for the cube and the rtk2b boards cannot be correct. because it is wired TX TX and RX RX. as you suggested. Regardless I now have GPS with 3D dgps and GPS 2 with RTK FIX without NTRIP! THANKS I will post pics when back together and have a few suggestion’s that I have not seen in any other post.
Part of the problem is that ArduSimple chooses to use a non-standard labeling convention, which confuses EVERYONE.
On the good side, the products are high quality, and the GH connector does follow the Pixhawk standard, so if you didn’t pin the connector yourself and just used one off the shelf, it would be plug-and-play.
Also, the RTK Fixed status on the second GPS does not mean that you are getting increased overall accuracy. That is a byproduct of the moving baseline configuration and the mechanism by which heading (yaw) is determined. It’s a very good sign, though, and a good indicator that your system is functioning properly thus far.
If you want high accuracy, you still need to use an external correction source such as NTRIP or a fixed base installation.
I think you are right Yuri. The wiring convention is not reversed when you are using the GH connector. I remember it is reversed when we are using the solder tabs to move the UART2 signals between the boards to transmit the correction signal from on GPS1 to GPS2. Sorry for the confusion @Rustey! I am glad to fix the wiring diagram to prevent others from being confused also.
I tried to delete the original diagram but I am having difficulty doing that task. I may need help to eliminate the diagram that has an error on it.
I have been out there on a tractor all day moving dirt and tomorrow I will be out there all day loading timber so it will get hauled off. I will be away from the computer again all day
1 Like
Thanks, so much Steve ,I thought I was getting old! That make sense to me now. No problem. I have read wiring Diagrams for 40 + years and that did not add up.
Right ,I will be looking to get my Base station going now with a c00zedf9p configured by the autopilot? thank you Yuri.
Well, here I am stuck again . (EK3 awaiting gps config data) message never went away. I disregarded message and finished my retrofit to mower. Took it out for test drive. I thought because I was under roof that it would go away. Still there.
myparamfile.param_6.param (15.6 KB)
In that picture it indicates that neither GPS card is working they way you would expect. They should be indicating RTK Fixed. Its puzzling that even GPS2 does not indicate RTK. It looks like the GPS units are not working even though they have power and are plugged in. Do you have the antennas connected and correction signal from some source? I did a compare on the parameters and the only thing I can find off normal is your GPS_AUTO_SWITCH should be set to 0 to make it use GPS1 as the primary GPS.
No I’m not connected to ntrip yet or base station yet! I thought this should work somewhat without correction’s. I have ,when first turned on I have rtk fix then it goes to dgps on both. I think Yuri said that was closer to correct than rtk fix? until you have ntrip or base station corrections? Thanks Steve.
Yes it should work. Both are reporting DGPS fix type, so they are recognized. But neither are receiving corrections, and neither have acknowledged auto configuration
GPS2 should indicate RTK Fixed if moving baseline is set up correctly. It’s possible either the position offsets are incorrect or GPS_DRV_OPTIONS,1 is configured but not wired for direct UART2 comms.
More puzzling is why they are not auto configuring. Reset them to default in u-Center before further troubleshooting.
1 Like
What version of Ardupilot are you using?
The screenshot above showed v4.5.7 up in the title block.
1 Like