Use this discussion for hardware issues, or start a new discussion (Add a Discussion)
start with enable debug messages from the ardupilot ublox driver https://github.com/diydrones/ardupilot/blob/master/libraries/AP_GPS... .
Thanks Thomas. Before connecting, I verified (or at least I thought I verified) that the GPS compass serial outputs were already at 3.3V. I couldn't find a schematic of my unit, but assumed it has a regulator in there to step the 5 volts down to 3.3. Maybe I better go back and check those voltages...
Also, I have a sneaking suspicion that the GPS compass is finicky about its power supply. That has been a key difference in how I've been testing at home. When I switch over to the APM, the GPS compass is powered off of the USB port on the APM, but on the BBB it gets its power off the 5V power supply from the wall. However, I just switched the BBB over to battery power, and the GPS still isn't working. Power supply is at 5.2 volts, which should be good enough for the GPS.
Great suggestion. So I understand I want to set: #define UBLOX_DEBUGGING 1
Dumb question... it looks like the debugging code is sending the output via a "hal.console->printf". Where does that send the text? To the command line? I have the code autostarting at BBB boot-up, so will probably need to kill it and restart.
Also, my compass is giving me headaches now. EKF is complaining "Error Compass Variance" and "Bad AHRS", and heading is drifting all over the place. It was working! Still works when I plug in the APM, so something about this darned BBB setup is not liking my GPS or compass. Maybe I need to try a different GPS/compass.
Nevermind about the compass problem! I had forgotten to reconnect the I2C port, so it was grabbing the compass measurement from the MPU9250. I haven't calibrated that yet.
That GPS, on the other hand, is still a problem...
Great to hear that Larry!
It somehow sounds like my Neo7 GPS that does not want to play with one of my BBBmini's.
I will try to see if it is a similar thing again now :)