TTgo : Gps cannot being connected : Impossible to get the right baud rate

[tonton-h4]

Good morning,

We are trying to build a Eu you are naming example 3. The connection Raspberry - TTGo doesn't hold more than few seconds.

Here is the Stratux Log:

2023/08/18 15:22:24 Logfile truncated
2023/08/18 15:22:29 handleRestartRequest called
2023/08/18 15:22:29 signal caught: terminated - shutting down.
2023/08/18 15:22:30 Entered ES shutdown() ...
2023/08/18 15:22:30 ES shutdown(): calling e.wg.Wait() ...
2023/08/18 15:22:30 ES read(): shutdown msg received, calling cmd.Process.Kill() ...
2023/08/18 15:22:30 kill successful...
2023/08/18 15:22:30 ES shutdown() complete ...
2023/08/18 15:22:30 Entered OGN shutdown() ...
2023/08/18 15:22:30 signal shutdown(): calling f.wg.Wait() ...
2023/08/18 15:22:31 signal shutdown() complete ...
2023/08/18 15:22:32 - stratux-pre-start.sh - Running Stratux Updater Script.
2023/08/18 15:22:32 - stratux-pre-start.sh - Exited without updating anything...
2023/08/18 15:22:32 read in settings.
2023/08/18 15:22:32 Stratux v1.6r1-eu029 (94438ef) starting.
2023/08/18 15:22:32 Developer mode set
2023/08/18 15:22:32 Added critical system error: System uptime 338 seconds. Daemon was restarted.

2023/08/18 15:22:32 Entered uatReader() ...
2023/08/18 15:22:32 client connected: 192.168.10.37:4000 ().
2023/08/18 15:22:32 client connected: 192.168.10.37:2000 ().
2023/08/18 15:22:32 client connected: 192.168.10.37:49002 ().
2023/08/18 15:22:33 ===== OGN Device Serial: stx:868:20 PPM 20 =====
2023/08/18 15:22:33 Entered OGN read() ...
2023/08/18 15:22:33 Delaying ogn-rx start until we have a valid GPS time
2023/08/18 15:22:33 ===== ES Device Serial: stx:1090:-13 PPM -13 =====
2023/08/18 15:22:33 Entered ES read() ...
2023/08/18 15:22:33 Executed /opt/stratux//bin/dump1090 --fix --gain 37.2 --net-stratux-port 30006 --net --device-index 1 --ppm -13 successfully...
2023/08/18 15:22:52 serial port/baudrate detection err: Failed to detect GPS serial baud rate
2023/08/18 15:23:02 stats [started: 30 seconds ago]
2023/08/18 15:23:02 - Disk bytes used = 1.3 GB (4.0 %), Disk bytes free = 30 GB (96.0 %)
2023/08/18 15:23:02 - CPUTemp=40.78 [40.78 - 41.86] deg C, MemStats.Alloc=1.9 MB, MemStats.Sys=12 MB, totalNetworkMessagesSent=43
2023/08/18 15:23:02 - UAT/min 0/0 [maxSS=0.00%], ES/min 0/0, Total traffic targets tracked=0
2023/08/18 15:23:02 - Network data messages sent: 38 total. Network data bytes sent: 677 total.
2023/08/18 15:23:02 - Last GPS fix: 30 seconds ago, GPS solution type: 0 using 0 satellites (0/0 seen/tracked), NACp: 0, est accuracy 999999.00 m
2023/08/18 15:23:02 - GPS vertical velocity: 0.00 ft/sec; GPS vertical accuracy: 999999 m
2023/08/18 15:23:02 - Mode-S Distance factors (<5000, <10000, >10000): 2500.000000, 2800.000000, 3000.000000
2023/08/18 15:23:10 serial port/baudrate detection err: Failed to detect GPS serial baud rate
2023/08/18 15:23:27 serial port/baudrate detection err: Failed to detect GPS serial baud rate
2023/08/18 15:23:32 stats [started: 1 minute ago]
2023/08/18 15:23:32 - Disk bytes used = 1.3 GB (4.0 %), Disk bytes free = 30 GB (96.0 %)
2023/08/18 15:23:32 - CPUTemp=41.32 [40.78 - 41.86] deg C, MemStats.Alloc=2.7 MB, MemStats.Sys=13 MB, totalNetworkMessagesSent=90
2023/08/18 15:23:32 - UAT/min 0/0 [maxSS=0.00%], ES/min 0/0, Total traffic targets tracked=0
2023/08/18 15:23:32 - Network data messages sent: 79 total. Network data bytes sent: 1254 total.
2023/08/18 15:23:32 - Last GPS fix: 1 minute ago, GPS solution type: 0 using 0 satellites (0/0 seen/tracked), NACp: 0, est accuracy 999999.00 m
2023/08/18 15:23:32 - GPS vertical velocity: 0.00 ft/sec; GPS vertical accuracy: 999999 m
2023/08/18 15:23:32 - Mode-S Distance factors (<5000, <10000, >10000): 2500.000000, 2800.000000, 3000.000000
2023/08/18 15:23:45 serial port/baudrate detection err: Failed to detect GPS serial baud rate
2023/08/18 15:24:02 stats [started: 1 minute ago]
2023/08/18 15:24:02 - Disk bytes used = 1.3 GB (4.0 %), Disk bytes free = 30 GB (96.0 %)
2023/08/18 15:24:02 - CPUTemp=41.32 [40.78 - 41.86] deg C, MemStats.Alloc=2.5 MB, MemStats.Sys=13 MB, totalNetworkMessagesSent=135
2023/08/18 15:24:02 - UAT/min 0/0 [maxSS=0.00%], ES/min 1/1, Total traffic targets tracked=0
2023/08/18 15:24:02 - Network data messages sent: 117 total. Network data bytes sent: 1796 total.
2023/08/18 15:24:02 - Last GPS fix: 1 minute ago, GPS solution type: 0 using 0 satellites (0/0 seen/tracked), NACp: 0, est accuracy 999999.00 m
2023/08/18 15:24:02 - GPS vertical velocity: 0.00 ft/sec; GPS vertical accuracy: 999999 m
2023/08/18 15:24:02 - Mode-S Distance factors (<5000, <10000, >10000): 2500.000000, 2800.000000, 3000.000000
2023/08/18 15:24:03 serial port/baudrate detection err: Failed to detect GPS serial baud rate

I flashed once again and still the same problem.

Where should I check first or maybe is there any menu to change the baud rate?

Should it be set to 115200 Bauds?

Thanks a lt,

Dan.

[b3nn0]

Didn't even specify which firmware you are using, so only a generic answer. Also, Screenshot of status page would be helpful.
Stratux tries 115200, 38400, 9600. If it receives NMEA data with any of those, it works. Otherwise you will get the error you posted.

[tonton-h4]

Good evening,

Thanks of your answer.
We did :
sudo /opt/stratux/ogn/install-ogntracker-firmware-pi.sh

The TTGo is the following one :

The version# written on the label is T-Bean V1.1

This is why I used install-ogntracker-firmware-pi.sh

Best regards,

Dan.

[b3nn0]

That looks fine to me. The problem is not the baud rate. Screenshot of Status page please?

[tonton-h4]

Thanks for your answer.

Here are what I got:

It started slowly getting the satellites.

Then, I dowloaded this Log when the screen and then we got 0 satellites

stratux.txt

Maybe I need to re-flash the whole set?

Thank you,

Dan.

[VirusPilot]

From the distance I would say that all is fine with your setup - your bad GPS reception may have two reasons: the default GPS antenna is quite small and I assume that you are inside a building so maybe you try outside first.

[b3nn0]

Yes, in the beginning everything looks good, but for some reason the T-Beam stops communicating. That's not related to the GPS signal quality - it just stops.
Maybe try a different USB cable, different USB port, make sure that your Stratux has a good power source and the red LED on the PI is constantly on. If it isn't, try a different power supply and/or power cable.

If all this doesn't help, it is either a bug in OGN-tracker, or a defective T-Beam. The fact that I can not reproduce it with my T-Beam 1.1 would make me thing that it is the latter.

Also make sure you saw the notice in the Wiki regarding newer AXP chips and verify:
https://github.com/b3nn0/stratux/wiki/TTGO-T-Beam-Firmware-for-Stratux#important-notice-2023-08

[tonton-h4]

Viruspilot and Adrian,

Thank you, both of you.

When I am testing outside, I use a power pack.

Since I had some doubts concerning the 2 Usb/Micro Usb cable, I bought new cables yesterday evening. Today, I am far away of the house, I will resume testing starting tomorrow. I have been delivered today with a new TTGo. I'll keep you posted.
Have a pleasant week-end,

Dan.

[VirusPilot]

Cool picture, we should use this for our repository ...

[tonton-h4]

If you want, go ahead, feel free to do it.

Daniel

[tonton-h4]

Good morning,

The green led is on. The red led blinks.

Should it be difgfgerent?

Its a raspberry 3B+.

Thanks,

Dan.

[tonton-h4]

Good evening,

The new cables Usb/Micro Usb are giving an astonishing good results.

The stratux was turned on 8 hours ago, and is still running.

This shows how tricky and difficult it can be to understand what can be wrong.

Thank you Adrian, thank you Viruspilot for your help.

Now, I go further with the AHRS and Pressure.

Dan.