GPS Timestamp incorrect when enabled?

[Tezla_LLC]

Hello…
When I enable my gps on WM1302 and push data to the network server I notice the timestamps of the received packets are dated incorrectly as 1999…Can someone point me to what is wrong?

[Marcos_Rojas_Mardone]

Probably more context about your deployment could be useful in this case
Providing links directly to the devices that you are using, for example.

I’m guessing it’s this device

Even more concerning that the fact that the year is 1999 is the fact that the date and hour is static in all Uplink

Checking on the WM1302 I notice that I can’t find any GPS functionality
I’m guessing, the WM1303 it’s only a gateway that has to be driven by some host, I will assume that you are using a rasperry pi, or something like that, in that case, the GPS module should be added.

My guess is that you don’t actually have a GPS module, or that is not being used correctly

[Tezla_LLC]

Hello Marcos.
Some context:
WM1302 stacked onto an RPi5. I have a LoRaWAN and a GPS antenna connected to the WM1302. I am using TTYAMA0 in the global_conf.json file for the GPS.

Prior I did not have this line in the file and Chirpstack did not know my location. I then added the line and Chirpstack found my location (that was the only change), So I am sure GPS is working.

Could it be the 1PPS pulse ?

Thanks