CubeCell GPS (HTCC-AB02S) Air530 not getting signal?

Hi, I got a few of your AB02S GPS modules, and am trying to use them, but it seems the Air530 is not getting a signal?

The basic behavior in the configAir530 example seems to work (see edit at bottom of post), gives results like:

15:06:50.305 -> $GNGGA,000018.029,3041.4346,N,10410.4026,E,0,0,,181.9,M,-31.9,M,,*7F

15:06:50.342 -> $GPGSA,A,1,,,,,,,,,,,,,,,*1E

15:06:50.380 -> $BDGSA,A,1,,,,,,,,,,,,,,,*0F

15:06:50.380 -> $GPGSV,1,1,00*79

15:06:50.413 -> $BDGSV,1,1,00*68

15:06:50.485 -> $GNRMC,000018.029,V,3041.4346,N,10410.4026,E,0.000,0.00,060180,,,N*52

15:06:50.523 -> $GNVTG,0.00,T,,M,0.000,N,0.000,K,N*2C

The other example programs, oledDisplayGPSInfo and printGPSInfo are also giving nonsense data, such as the time being June 1, 2080 at 0:00:00, and my coordinates and altitude as 0.00. Here’s an example of the output from printGPSInfo:

14:30:10.845 -> Date/Time: 2080/06/01 00:00:20.02
14:30:10.845 -> LAT: 0.000000, LON: 0.000000, ALT: 0.00
14:30:10.845 -> SATS: 0, HDOP: 0.00, AGE: 4294967295, COURSE: 0.00, SPEED: 0.00

Is this a known issue? How can I fix this to get useful information out of the GPS module?

I’m using the latest version (1.0.0) of the CubeCell Development Framework.
Thanks!

Edit: upon further research, I realize the fields that did have information in the ConfigAir530 example were just providing the (incorrect, presumably) time. How good is the built-in GPS antenna, and how long does it take to acquire a signal? If I want to use an external antenna, does the included one work, or is that just for LoRa? Also which connector is for GPS and which is for LoRa, they don’t seem to be labeled or described in the documentation?

thanks again.

Summary

This text will be hidden

Hi,
Please test the GPS in an open environment.The connector nearby the OLED is for LoRa, the other one is for GPS. An active external GPS antenna may accelerate GPS fix.

1 Like