I just noticed this morning that it sometimes imports incorrect talkgroups for DMR systems. After importing a few channels local to me I wondered why I wasn't receiving any traffic... turns out the talkgroups are all wrong.
I was importing the following:
Lambton County, Ontario (ON) Scanner Frequencies and Radio Frequency Reference
Lambton County - Sarnia
- Sarnia Fire TAC 1 thru 4
- Sarnia Transit
- Sarnia CareAvan
- Sarnia works
In the EZ-Scan import wizard the talkgroups show the proper values but after importing I'm seeing this:
If you look at 13578490 in hex it's 00EA A83A, while 43066 is A38A so it seems any bytes over FFFF are being thrown away. I've also submitted this to the bug report email address that Wendy provided. So if you are importing DMR users with large talkgroups, double check what is actually being imported!
I was importing the following:
Lambton County, Ontario (ON) Scanner Frequencies and Radio Frequency Reference
Lambton County - Sarnia
- Sarnia Fire TAC 1 thru 4
- Sarnia Transit
- Sarnia CareAvan
- Sarnia works
In the EZ-Scan import wizard the talkgroups show the proper values but after importing I'm seeing this:
Code:
Talkgroup Correct TG Imported TG
SFRS TAC 1 15378490 43066
SFRS TAC 2 15378491 43067
SFRS TAC 3 15378492 43068
SFRS TAC 4 15378494 43070
Transit 51234 51234 (ok!)
CareAvan 51235 51235 (ok!)
Works 2912041 28457
If you look at 13578490 in hex it's 00EA A83A, while 43066 is A38A so it seems any bytes over FFFF are being thrown away. I've also submitted this to the bug report email address that Wendy provided. So if you are importing DMR users with large talkgroups, double check what is actually being imported!