APRS beacon testers needed

[F1RMB]

Could you post an excerpt of the nmea file (empty file ?, no NMEA sentence ?)

[VK3KYY]

Could you post an excerpt of the nmea file (empty file ?, no NMEA sentence ?)

Good point

[SA0BUX]

Attached the NMEA file from yesterday in zip format.

I have the same JS error in Edge and Chrome too and I tested on several computers.

This is a minor issue, APRS reports works and I could load the file from the RT3S in GPS Visualizer.

Capture.JPG (129.63 KiB) Viewed 1111 times

[F1RMB]

The file is 6Mb, but corrupted (2548 usable lines, rest is full of 0xef 0xbf 0xbd).

[SA0BUX]

The file is 6Mb, but corrupted (2548 usable lines, rest is full of 0xef 0xbf 0xbd).

Ok, I noticed that now when I loaded it in notepad++ , deleted the bad part and the map worked.

I tried another NMEA load via CPS and it's corrupted either from radio flash or in CPS function.
Maybe the file wasn't closed properly in the radio, best approach is to powercycle radio before download ?

I tried not to power off radio so much to avoid GPS cold starts.

[LY4SA]

Can not get DMR APRS working as beacon. In-Call APRS works well.
Tried Auto, Smart setting without positive results. Just In-Call APRS working.
Any specific settings should be for hotspot or BM selfcare ?
Thanks for answer
Alex LY4SA

[F1RMB]

Wrong topic.
This one is about analog (FM) APRS.

Cheers.
---
Daniel

[LY4SA]

Thanks for explanation.
Sorry for misunderstood.
Alex LY4SA

[VK3KYY]

I'm not sure why the file could be so big, the CPS only downloads 2Mb from the radio.

The reason the file is not getting loaded is becasue the last NMEA line is incomplete.

I'll double check whether the power off code is saving the data correctly. Its odd that the last line of data was interrupted in the middle as the way the GPS functionality works is that it does not process a line until the entire line has been received and its CRC has been checked.

I will need to add some debugging into the CPS to save the raw data from the radio to try to understand why this has happened

[VK3KYY]

I've changed the attachment settings to allow .txt files within the developer discussions section. Size limit is 256k which should be enough for most small logs as this would allow around 1 hour of logging

Viewing the attached file, it looks typical of the JumpStar GPS fitted to the RT3S, with much more position error than the distance reported by the NMEA data from the GPS module