I think most devices should work just fine at high altitudes. I'm surprised that Teltonika is not working. Is there some logs to check the root cause?
hello anton,
thank you for your replay.
in attached the logs as requested:
the test operation for yesterday was between 11h:30 and 11h:45 ( morocco times)
My teltonika IMEI Number is 868373079646479
but I was did some research and discovered that the GSM network (voice + 4G/5G) of any telephony operator does not propagate upwards (it propagates like a pyramid whose head is the top of the pylon).
this means that at high altitudes there is no connection so the GPS tracker is no longer connected!
There are same gps trackers that use satellite sim cards which can work at hight altitude but they are expensive !!
Well, I hope we can find a solution for my case, because I really need it, thank you once again for your help
2025-08-31 11:29:30 INFO: [Tbd36b662] id: 352672102707635, time: 2025-08-31 11:29:30, lat: 33.59080, lon: -7.52510, course: 352.0
2025-08-31 11:29:30 INFO: [Tbd36b662: gt06 > 105.74.5.214] 7878052218e6fd630d0a
2025-08-31 11:29:31 INFO: [Tc9385b08] disconnected
2025-08-31 11:29:31 INFO: Event id: 868373079646479, time: 2025-08-31 11:29:31, type: deviceOffline, notifications: 0
2025-08-31 11:29:33 INFO: [T10af4ec8: gt06 < 105.67.130.23] 7878222219081f0b1d1fce03963f4e00d1f2d1001cf2025c0200a200c26901000001fe04a70d0a
2025-08-31 11:29:33 INFO: [T10af4ec8] id: 352672102708096, time: 2025-08-31 11:29:33, lat: 33.43236, lon: -7.64399, course: 242.0
2025-08-31 11:29:33 INFO: [T10af4ec8: gt06 > 105.67.130.23] 7878052201fe23230d0a
2025-08-31 11:29:35 INFO: [Tfa1f33c4: tk103 < 105.74.65.78] (028044236238BR00250831A3332.6751N00731.8640W000.0112933249.3701000000L00000000)
2025-08-31 11:29:35 INFO: [Tfa1f33c4] id: 028044236238, time: 2025-08-31 11:29:35, lat: 33.54459, lon: -7.53107, course: 249.4
2025-08-31 11:29:38 INFO: [Tae386870: tk103 < 105.74.12.190] (028043579448BZ00,{604,2,212,3404}\n{604,2,212,23404}\n{604,2,212,21811}\n,00000000)
2025-08-31 11:29:38 INFO: [Tae386870] id: 028043579448, time: 2025-08-31 11:29:38, lat: 32.22871, lon: -7.94894, course: 286.0
2025-08-31 11:29:38 INFO: [T6019aa3b: tk103 < 105.74.66.141] (028044042578BR00250831A3228.1136N00515.6018W040.8112934321.3300000001L00000000)
2025-08-31 11:29:38 INFO: [T6019aa3b] id: 028044042578, time: 2025-08-31 11:29:38, lat: 32.46856, lon: -5.26003, speed: 22.0, course: 321.3
2025-08-31 11:29:39 INFO: [Tfe6f869d] connected
2025-08-31 11:29:39 INFO: [Tfe6f869d: gt06 < 102.52.111.169] 78780d0108988888812349980002d3260d0a
2025-08-31 11:29:39 INFO: [Tfe6f869d: gt06 > 102.52.111.169] 787805010002eb470d0a
2025-08-31 11:29:40 INFO: [Tbd36b662: gt06 < 105.74.5.214] 7878222219081f0b1d26c9039a994a00ceaedc001d60025c02009000b05200000018e712ec0d0a
2025-08-31 11:29:40 INFO: [Tbd36b662] id: 352672102707635, time: 2025-08-31 11:29:40, lat: 33.59080, lon: -7.52510, course: 352.0
2025-08-31 11:29:40 INFO: [Tbd36b662: gt06 > 105.74.5.214] 7878052218e7ecea0d0a
2025-08-31 11:29:40 INFO: [Tae386870: tk103 < 105.74.12.190] (028043579448BZ00,{604,2,212,3404}\n{604,2,212,23404}\n{604,2,212,21811}\n,00000000)
2025-08-31 11:29:40 INFO: [Tae386870] id: 028043579448, time: 2025-08-31 11:29:40, lat: 32.22871, lon: -7.94894, course: 286.0
2025-08-31 11:29:40 INFO: [Tfe6f869d: gt06 < 102.52.111.169] 7979058a0002ce0d0d0a
2025-08-31 11:29:43 INFO: [Tfa1f33c4: tk103 < 105.74.65.78] (028044236238BP00355228044236238HSO199)
2025-08-31 11:29:43 INFO: [Tfa1f33c4: tk103 > 105.74.65.78] (028044236238AP01HSO)
2025-08-31 11:29:43 INFO: [T10af4ec8: gt06 < 105.67.130.23] 7878222219081f0b1d29ce03963f4e00d1f2d1001cf2025c0200a200c26901000001ff7ca90d0a
2025-08-31 11:29:43 INFO: [T10af4ec8] id: 352672102708096, time: 2025-08-31 11:29:43, lat: 33.43236, lon: -7.64399, course: 242.0
2025-08-31 11:29:43 INFO: [T10af4ec8: gt06 > 105.67.130.23] 7878052201ff32aa0d0a
2025-08-31 11:29:50 INFO: [Tbd36b662: gt06 < 105.74.5.214] 7878222219081f0b1d30c8039a995300ceaeee001d60025c02009000b05200000018e837bd0d0a
2025-08-31 11:29:50 INFO: [Tbd36b662] id: 352672102707635, time: 2025-08-31 11:29:50, lat: 33.59080, lon: -7.52511, course: 352.0
2025-08-31 11:29:50 INFO: [Tbd36b662: gt06 > 105.74.5.214] 7878052218e8141d0d0a
2025-08-31 11:29:50 INFO: [Tfa1f33c4: tk103 < 105.74.65.78] (028044236238BR00250831A3332.6751N00731.8639W000.0112948249.3701000000L00000000)
2025-08-31 11:29:50 INFO: [Tfa1f33c4] id: 028044236238, time: 2025-08-31 11:29:50, lat: 33.54459, lon: -7.53107, course: 249.4
2025-08-31 11:29:50 INFO: [Tc093e70e: tk103 < 105.74.2.198] (027046453668BP00355227046453668HSO1ac)
2025-08-31 11:29:50 INFO: [Tc093e70e: tk103 > 105.74.2.198] (027046453668AP01HSO)
2025-08-31 11:29:51 INFO: [Tae386870: tk103 < 105.74.12.190] (028043579448BP00355228043579448HSO19f)
2025-08-31 11:29:51 INFO: [Tae386870: tk103 > 105.74.12.190] (028043579448AP01HSO)
2025-08-31 11:29:51 INFO: [Tae386870: tk103 < 105.74.12.190] (028043579448BP01 DYEGOO-HY,CCID:8921202200185486207F)
2025-08-31 11:29:52 INFO: [Tfe6f869d: gt06 < 102.52.111.169] 7878222206010f0b1d32c9037738ac00ddcf93451cad025c0102870043db000000000332f30d0a
2025-08-31 11:29:52 INFO: [Tfe6f869d] id: 898888881234998, time: 2025-08-31 11:29:52, lat: 32.30274, lon: -8.07589, speed: 37.3, course: 173.0
...
2025-08-31 11:32:36 INFO: [Tfa1f33c4] id: 028044236238, time: 2025-08-31 11:32:36, lat: 33.54458, lon: -7.53105, course: 249.4
2025-08-31 11:32:36 WARN: [T26cfcf37] error - Connection reset - SocketException (...)
2025-08-31 11:32:36 INFO: [T26cfcf37] disconnected
2025-08-31 11:32:36 INFO: Event id: 028043579646, time: 2025-08-31 11:32:36, type: deviceOffline, notifications: 0
2025-08-31 11:32:37 INFO: [T7bfb959a: tk103 < 105.137.125.163] (028043585700BR00250831A3345.9148N00615.0253W000.0113235114.2901000000L00000000)
2025-08-31 11:32:37 INFO: [T7bfb959a] id: 028043585700, time: 2025-08-31 11:32:37, lat: 33.76525, lon: -6.25042, course: 114.3
2025-08-31 11:32:40 INFO: [Tbd36b662: gt06 < 105.74.5.214] 7878222219081f0b2026ca039a992f00ceae97001d60025c02009000b05200000018f974f00d0a
2025-08-31 11:32:40 INFO: [Tbd36b662] id: 352672102707635, time: 2025-08-31 11:32:40, lat: 33.59078, lon: -7.52506, course: 352.0
2025-08-31 11:32:40 INFO: [Tbd36b662: gt06 > 105.74.5.214] 7878052218f915150d0a
2025-08-31 11:32:41 INFO: [T340df74f: tk103 < 105.74.129.39] (028043579448BP00355228043579448HSO19e)
2025-08-31 11:32:41 INFO: [T340df74f: tk103 > 105.74.129.39] (028043579448AP01HSO)
2025-08-31 11:32:42 INFO: [T340df74f: tk103 < 105.74.129.39] (028043579448BP01 DYEGOO-HY,CCID:8921202200185486207F)
2025-08-31 11:32:43 INFO: [T10af4ec8: gt06 < 105.67.130.23] 7878222219081f0b2029ce03963f4a00d1f2cb001cf2025c0200a200c2690100000211a9e20d0a
2025-08-31 11:32:43 INFO: [T10af4ec8] id: 352672102708096, time: 2025-08-31 11:32:43, lat: 33.43236, lon: -7.64399, course: 242.0
2025-08-31 11:32:43 INFO: [T10af4ec8: gt06 > 105.67.130.23] 78780522021116b20d0a
2025-08-31 11:32:44 INFO: [Tfa1f33c4: tk103 < 105.74.65.78] (028044236238BP00355228044236238HSO199)
2025-08-31 11:32:44 INFO: [Tfa1f33c4: tk103 > 105.74.65.78] (028044236238AP01HSO)
2025-08-31 11:32:48 INFO: [T2045f97a] connected
2025-08-31 11:32:49 INFO: [T2045f97a: tk103 < 105.74.66.206] (028043579646BP05355228043579646060115A3332.7074N00732.0334W035.8113245255.5200000001L00000000)
2025-08-31 11:32:49 INFO: Event id: 028043579646, time: 2025-08-31 11:32:49, type: deviceOnline, notifications: 0
2025-08-31 11:32:49 INFO: [T2045f97a] id: 028043579646, time: 2025-08-31 11:32:49, lat: 33.54512, lon: -7.53389, speed: 19.3, course: 255.5
2025-08-31 11:32:49 INFO: [T2045f97a: tk103 > 105.74.66.206] (028043579646AP05)
2025-08-31 11:32:49 INFO: [T44876fad] connected
2025-08-31 11:32:49 INFO: [T44876fad: gt06 < 102.52.87.68] 78780d0108988888812349980002d3260d0a
2025-08-31 11:32:49 INFO: [T44876fad: gt06 > 102.52.87.68] 787805010002eb470d0a
I was talking about your device logs.
this is what I found for the test period (11h:30 and 11h:45)
31/08/2025 11:20:24 INFO: [Tc9385b08] id: 868373079646479, time: 2025-08-31 11:20:24, lat: 33.51477, lon: -7.64548, speed: 4.9, course: 190.0
31/08/2025 11:20:29 INFO: [Tc9385b08] id: 868373079646479, time: 2025-08-31 11:20:29, lat: 33.51466, lon: -7.64547, speed: 3.2, course: 238.0
31/08/2025 11:24:29 INFO: [Tc9385b08] id: 868373079646479, time: 2025-08-31 11:24:29, lat: 33.51467, lon: -7.64549, course: 238.0
31/08/2025 11:29:31 INFO: Event id: 868373079646479, time: 2025-08-31 11:29:31, type: deviceOffline, notifications: 0
31/08/2025 12:26:12 INFO: Event id: 868373079646479, time: 2025-08-31 12:26:12, type: deviceOnline, notifications: 0
31/08/2025 12:26:12 INFO: Event id: 868373079646479, time: 2025-08-31 12:26:12, type: deviceStopped, notifications: 0
31/08/2025 12:26:12 INFO: [T4fdf0892] id: 868373079646479, time: 2025-08-31 12:26:12, lat: 33.51467, lon: -7.64549, course: 238.0
31/08/2025 12:26:12 INFO: [T4fdf0892] id: 868373079646479, time: 2025-08-31 12:26:12, lat: 33.51467, lon: -7.64549, course: 238.0
31/08/2025 12:27:27 INFO: [T4fdf0892] id: 868373079646479, time: 2025-08-31 12:27:27, lat: 33.51465, lon: -7.64549, course: 105.0
31/08/2025 12:32:28 INFO: Event id: 868373079646479, time: 2025-08-31 12:32:28, type: deviceOffline, notifications: 0
31/08/2025 12:40:13 INFO: Event id: 868373079646479, time: 2025-08-31 12:40:13, type: deviceOnline, notifications: 0
That's still server logs.
Where can i find device log ?
Help please
I don't know that. That's why I said if it's possible. You should check with your vendor if you don't know.
Hello,
We're looking for a type of GPS tracker that can provide decent results even at very high altitudes. From 200m to 4km!!
We tried it with the FMC940, but over 150 meters, no real-time data is sent.
Could you please let us know if other parameters need to be adjusted on this teltonika GPS tracker, or if we should definitely change it and test with other modules.
I did a test this morning, when the altitude of the drone is a little low (20 to 50 meters), the data transmission time is perfect (2 to 10 seconds ). but as long as the drone is raised in the sky, no data arrives even after 3 or 4 minutes of waiting
Thank you so much for your support.