|
East Central, Nebraska | so we used to have problems that occurred exactly like your stating when the nmea strings on the output side were cranked way up. like 115k+ with lots of strings turned on at a fast rate. when that was the situation it would act exactly like you explain. in non computer lingo basically the high message rate would overwhelm the beacon and confuse it to a point it couldn't do anything else. as a test i would try ensuring that the output is turned off and use the gps on the android device (for locatoin) if possible and see if you get different results.
edit, just to confirm your not trying to use a hotspot to feed the tablet are you, the tablet does have its own data plan correct?
Edited by caseihfarmer 3/21/2024 22:00
| |
|
Beacon NTrip bluetooth connection update
