search

ncssar / radiolog

SAR radio log program
Other
13 stars 3 forks source link

add NXDN support (Icom) #629

Open caver456 opened 1 year ago

caver456 commented 1 year ago

see #628 which only refers to NEXEDGE, which is Kenwood's implementation of NXDN.

dBitech commented 1 year ago

ICOM uses the same STX (0x02) ans ETX (0x03) as Kenwood. the rest of their structure is a bit different.

so for example a position report looks like:

NTF,IDAS,RXMSG,IND,200,150,-,-128,GPS,”$GPRMC,170642,A,3545,000,N,13536.000,E,18.5,275.5,190109,14.5,E,A*11“

This is a GPS position report From Unit ID:150 to Individual ID:200 data type of GPS, with a RSSI of -128dBm

caver456 commented 1 year ago

After some of the other current issues are buttoned up, I'll work on getting a beta release that handles icom. Can you also send a just-CID icom string? Both BOT and EOT ideally. In FS, the BOT string is different from the EOT.

Just to keep terminology clear: BOT = beginning of transmission (in Kenwood terms) = the entire packet that gets sent when PTT is pressed; EOT = end of transmission = the entire packet that gets sent when PTT is released. Sounds like STX = the string at the start of the packet, and ETX is the string at the end of the packet; so BOT has a STX and a ETX, and EOT has a STX and a ETX - does that sound right?

On Mon, Feb 13, 2023 at 11:54 AM DarcyB @.***> wrote:

ICOM uses the same STX (0x02) ans ETX (0x03) as Kenwood. the rest of their structure is a bit different.

so for example a position report looks like:

NTF,IDAS,RXMSG,IND,200,150,-,-128,GPS,”$GPRMC,170642,A,3545,000,N,13536.000,E,18.5,275.5,190109,14.5,E,A*11“

This is a GPS position report From Unit ID:150 to Individual ID:200 data type of GPS, with a RSSI of -128dBm

— Reply to this email directly, view it on GitHub https://github.com/ncssar/radiolog/issues/629#issuecomment-1428566085, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEPCEZTGACFCDT7SWEIBDCDWXKGORANCNFSM6AAAAAAUXHO2ZU . You are receiving this because you authored the thread.Message ID: @.***>

dBitech commented 1 year ago

I will endeavor to capture a BOT and an EOT, though in digital mode, I'm not sure there is a notion of a BOT vs an EOT.

Yes, correct the STX and ETX are the beginning of string and end of string identifiers for the serial packet.

caver456 commented 1 year ago

In testing with nexedge, I do get CID and GPS at BOT, then CID again at EOT. One character is different in the BOT CID vs the EOT CID. But they don't seem to use the terms BOT and EOT when talking about nexedge/nxdn - only when talking about fleetsync.

On Tue, Feb 14, 2023, 10:38 AM DarcyB @.***> wrote:

I will endeavor to capture a BOT and an EOT, though in digital mode, I'm not sure there is a notion of a BOT vs an EOT.

Yes, correct the STX and ETX are the beginning of string and end of string identifiers for the serial packet.

— Reply to this email directly, view it on GitHub https://github.com/ncssar/radiolog/issues/629#issuecomment-1430204384, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEPCEZUTLV6XWGUIR3WL2DLWXPGKFANCNFSM6AAAAAAUXHO2ZU . You are receiving this because you authored the thread.Message ID: @.***>