I posted this earlier and some guy kevin? closed it saying it was not an RR issue. Am I supposed to post ONLY RR issues? I don't think he read it. I never said it was a RR issue. I found the problem tho' An experienced guy ex 'TV Engr" Jim in Maryland found the setting I was looking for - in EZ scan general Tab. I am partially blind and have trouble finding things like that sometimes.
This was my question--> How is that an RR problem? Should I only post RR problems?
I have saved some working trunked systems from South Carolina to "Archive". These talkgroups ALL worked I used them for many months. The TGID was in HEX. So now I am starting clean with a new trunking system here in Western MI. But EZ scan WILL not allow me to enter any hex TGIDs in the new archive I created. They must be Decimal or it Errors as OUT OF RANGE. If I load the other archive and add a new talk group line it Allows me to create a TGID in HEX... Also I noticed that when I loaded a CSV file I created - one that that had Hex in it, the system truncates as soon as it sees a Hex character like ABCDEF. So a talk group ID of 123C in the CSV file would truncate as 123. Or one that begins as A123 would be thrown out altogether since it begins with a character in the Hexadecimnal range 'A'.
I added 34 Michigan police talk groups using their DECIMAL values but I hear nothing. So if what is allowed or understood is determined by the radio (A PRO-668 with whistler firmware) then I suppose mine is looking for HEX. And given that HEX is what worked down in SC it must be looking for HEX. BUT as I said I cannot put Hex in this new list.
==========================
So the issue now is poor voice decoding ..It sounds like a high BER. Gotta place the radio in a sweet spot here in downtown Gtand Haven
Anyone have any ideas?
This was my question--> How is that an RR problem? Should I only post RR problems?
I have saved some working trunked systems from South Carolina to "Archive". These talkgroups ALL worked I used them for many months. The TGID was in HEX. So now I am starting clean with a new trunking system here in Western MI. But EZ scan WILL not allow me to enter any hex TGIDs in the new archive I created. They must be Decimal or it Errors as OUT OF RANGE. If I load the other archive and add a new talk group line it Allows me to create a TGID in HEX... Also I noticed that when I loaded a CSV file I created - one that that had Hex in it, the system truncates as soon as it sees a Hex character like ABCDEF. So a talk group ID of 123C in the CSV file would truncate as 123. Or one that begins as A123 would be thrown out altogether since it begins with a character in the Hexadecimnal range 'A'.
I added 34 Michigan police talk groups using their DECIMAL values but I hear nothing. So if what is allowed or understood is determined by the radio (A PRO-668 with whistler firmware) then I suppose mine is looking for HEX. And given that HEX is what worked down in SC it must be looking for HEX. BUT as I said I cannot put Hex in this new list.
==========================
So the issue now is poor voice decoding ..It sounds like a high BER. Gotta place the radio in a sweet spot here in downtown Gtand Haven
Anyone have any ideas?
