troymail
Silent Key
Traveled to various areas today on a big road trip/loop. Learned a couple of things with my G4...
1. Use caution when entering WACN, SYSID and particularly RFSS and site values. I was getting "out of range" messages on multiple occasions and systems over the past few days and it turns out that I was entering RFSS and site information in decimal when the input screen was expecting HEX. I really ought to know better....
2. I learned for the second time now that you cannot trust the information on RRDB that most people do not use. A year (or more) ago, I learned that there's alot of system/site location (lat/lon/range) data that is bad and/or not what you'd expect. Today I found a case here the RFSS/site information for a system was incorrect on RRDB and once again, the G4 just kept reporting "out of range" (it was not - the G4 just didn't find a RFSS/site value pair on the active frequencies/control channel that matched what was programmed).
For Unication: it might be better to provide a different message (other than "out of range") if a CC in the programming is detected and active but the system characteristics (SYSID, WACN, RFSS, site) do not match what the radio extracts. It would have helped me solve both of the above problems much more quickly.
1. Use caution when entering WACN, SYSID and particularly RFSS and site values. I was getting "out of range" messages on multiple occasions and systems over the past few days and it turns out that I was entering RFSS and site information in decimal when the input screen was expecting HEX. I really ought to know better....
2. I learned for the second time now that you cannot trust the information on RRDB that most people do not use. A year (or more) ago, I learned that there's alot of system/site location (lat/lon/range) data that is bad and/or not what you'd expect. Today I found a case here the RFSS/site information for a system was incorrect on RRDB and once again, the G4 just kept reporting "out of range" (it was not - the G4 just didn't find a RFSS/site value pair on the active frequencies/control channel that matched what was programmed).
For Unication: it might be better to provide a different message (other than "out of range") if a CC in the programming is detected and active but the system characteristics (SYSID, WACN, RFSS, site) do not match what the radio extracts. It would have helped me solve both of the above problems much more quickly.