GPS not connecting
-
I have a starling 2 with the default GPS. When I write "px4-listener sensor_gps" I receive: "never published". When I looked at the startup log I see that it is searching and not connecting to any gps, constantly printing the following lines:
GPS UART baudrate set to 115200
Dec 12 10:19:56 m0054 voxl-px4[22983]: INFO [muorb] SLPI: GPS UART baudrate set to 9600
Dec 12 10:19:56 m0054 voxl-px4[22983]: INFO [muorb] SLPI: GPS UART baudrate set to 38400
Dec 12 10:19:56 m0054 voxl-px4[22983]: INFO [muorb] SLPI: GPS UART baudrate set to 57600when I run the gps status command I see in the log:
Dec 12 10:36:46 m0054 voxl-px4[1942]: INFO [muorb] SLPI: Main GPS
Dec 12 10:36:46 m0054 voxl-px4[1942]: INFO [muorb] SLPI: protocol: UBX
Dec 12 10:36:46 m0054 voxl-px4[1942]: INFO [muorb] SLPI: status: NOT OK, port: 6, baudrate: 0
Dec 12 10:36:46 m0054 voxl-px4[1942]: INFO [muorb] SLPI: sat info: disabled
Dec 12 10:36:46 m0054 voxl-px4[1942]: INFO [muorb] SLPI: rate reading: 0 B/s
Dec 12 10:36:46 m0054 voxl-px4[1942]: INFO [muorb] SLPI: Ok executing command: gps status
Thanks! -
Hi @john-0,
You are trying the right commands, so this could be a hardware issue. Can you please inspect the cables that go into the GPS unit and J19 connector on VOXL2?
Do you have any other GPS unit you could plug into J19 for a quick test instead of the one installed on your vehicle?
Also, which VOXL2 SDK are you using?
Alex
-
Hi @Alex-Kushleyev, (I am from the same team as John's)
Our VOXL2 SDK is "voxl-suite 1.3.1".
We did try to connect the cable that goes into the sensor to another "taoglas CGGBP 18.4.A.02" and recieved GPS messages.
Our Starling2 came out of the box like that, should we change the sensor's configuration or is it a hardware malfunction?Thank you!
-
@Meytal-Lempel On your device what does
/etc/modalai/voxl-px4.conflook like? -
Hi @tom , here is my /etc/modalai/voxl-px4.conf:
#!/bin/bash # # voxl-px4 Configuration File # # GPS: # Tell PX4 which GPS to use. If there is no GPS unit use NONE. Otherwise # choose AUTODETECT and the startup script will attempt to automatically # configure the GPS, magnetometer, and status LED # Options include: [NONE, AUTODETECT] # # RC: # Tell PX4 which RC transmitter to use. # Use EXTERNAL when getting RC control from external Mavlink messages (e.g Via QGC) # Options include: [SPEKTRUM, CRSF_MAV, CRSF_RAW, M0065_SBUS, EXTERNAL, FAKE_RC_INPUT] # # ESC: # Tell PX4 which type of ESC to use. # Options include: [VOXL_ESC, VOXL2_IO_PWM_ESC] # # POWER_MANAGER: # Tell PX4 which power manager to use. # Use NONE for ModalAI Mini-ESC since the ESC driver handles PM. # Use EXTERNAL when not using the ModalAI APM power manager to power the board # This also just disables the voxlpm driver, same as the NONE option # Options include: [VOXLPM, EXTERNAL, NONE] # # DISTANCE_SENSOR: # Tell PX4 which distance sensor peripheral to use. # Note: The sensor will be started on the RC port so it is only # really possible to use it when using external RC. # Options include: [NONE, LIGHTWARE_SF000] # # OSD: # Tell PX4 whether to enable OSD (on-screen display). # Options include: [ENABLE, DISABLE] # # DAEMON_MODE: # Tell PX4 whether to enable daemon mode. # Options include: [ENABLE, DISABLE] # # SENSOR_CAL: # Tell PX4 where to source sensor calibration information. # Options include: [ACTUAL, FAKE] # # ARTIFACT_MODE: # Do not allow artifacts to be saved to disk. Will not start the logging # module, will delete any current log files, and will delete the data manager file. # Options include: [ENABLE, DISABLE] # # EXTRA_STEPS: # Optional field that allows a user to define custom commands to be run by PX4 on boot. # Must be a valid bash array as seen below # Example: EXTRA_STEPS=( "qshell gps start" "qshell commander mode manual" ) # # GPS=AUTODETECT RC=GHST ESC=VOXL_ESC POWER_MANAGER=VOXLPM DISTANCE_SENSOR=NONE OSD=DISABLE DAEMON_MODE=ENABLE SENSOR_CAL=ACTUAL ARTIFACT_MODE=DISABLE EXTRA_STEPS=()
