Adding a GPS to V2.2

[pacrunner]

I have added a GPS to my CubeSatSim via j12 on the main board.
I can see both GPS and Payload data in BPSK mode using FoxTelem, but when I change to APRS mode I get no data other than the battery current and voltage in both Direwolf and WebSDR.
If i use CubeSatSim/config -p in BPSK, I get the data. But if I enter the same command in APRS mode I get
cat: /dev/serial0: Device or resource busy twice.

I have not changed any software on the Pico.

Has anyone else had this issue.

[alanbjohnston]

Hi,

I’m not sure why that would happen.

Could you share the log outputs when in BPSK and APRS modes using:

CubeSatSim/log

Alan

[pacrunner]

The CubeSatSim has been working great upto the point I connected the GPS.

Before I started it up today, I took the wires off the GPS unit to see if it was that causing the issue.
Still the same.
I reconnected the GPS at 16:53, poor signal inside so no data.
I switched to BPSK at 17:02.

I have included 2 files:
Log complete.txt is from initial start.
Log.txt is after I cleared the logs this afternoon.

The lack of GPS data is it takes an eternity to find the sats in my shack.

Tim
log Complete.txt
log.txt

[alanbjohnston]

I think I see the problem.

If you connected your GPS module to your Main PCB, the GPS is connected to the Raspberry Pi Pico, and you do not want to turn on gpsd on the Raspberry Pi. You don't need to do anything on the Raspberry Pi or Pico for GPS to work - it will just start working after your GPS module gets a location lock. The best way to get a location lock is to put the GPS module where it has a clear view of the sky. It should get a lock within 10 minutes. Indoors, even near a window will take a long time and possibly not ever get a lock.

Turning on gpsd on the Raspberry Pi is only for when you want to connect a GPS module to a CubeSatSim Lite board. Since the Lite board doesn't have a Pico, the Raspberry Pi Zero must talk to the GPS module using the one serial port it has. Once gpsd is turned on the Raspberry Pi, the serial port is no longer available to talk to the Pico. This is why your BME and MPU sensor data goes away - there is no way the Raspberry Pi can read the data. You see these lines in the logs:

      Aug 30 16:36:08 get_payload_status not run since gps_status is ON
      Aug 30 16:36:08 cubesatsim cubesatsim[283]: pi_sensors status: 0
      Aug 30 16:36:08 cubesatsim cubesatsim[283]: Checking Pi gps
      Aug 30 16:36:14 cubesatsim cubesatsim[283]: gps read: 1 0.000000 0.000000 0.0
      Aug 30 16:36:14 cubesatsim cubesatsim[283]: No Pi gps available

So, turn off gpsd on the Raspberry Pi and you should get both GPS and BME and MPU data. If you don't see GPS data after your GPS module has a lock (usually, there is an LED on the module that blinks when it has a location lock), try connecting a micro USB cable between the Pico and your computer, and run the Arduino IDE Serial Monitor - you should see some GPS logs there.

Alan