loumaag said:Was there ever a scanner that took hex input? I can't think of one.
Where are you getting your hex TG information, if you are getting it from here on the site, that won't work anyway. Those hex numbers are only there to match Motorola radio TG input. IMHO we ought to take them off the site as they cause more confusion than anything.
I was talking about scanners, not software. And my comment still holds. The Hex number we present on the site is the hex value shifted right once. (Doing away with the lest-significate nibble.)Voyager said:Uhhh... Win96 takes HEX TGs. It's also convenient for those used to hex TGs.loumaag said:Was there ever a scanner that took hex input? I can't think of one. ...
loumaag said:I was talking about scanners, not software. And my comment still holds. The Hex number we present on the site is the hex value shifted right once. (Doing away with the lest-significate nibble.)Voyager said:Uhhh... Win96 takes HEX TGs. It's also convenient for those used to hex TGs.loumaag said:Was there ever a scanner that took hex input? I can't think of one. ...
Yes, hence my opinion that it is a piece of data not needed on the site. The site does presnet Project-25 systems with the correct Hex value (equal to the decimal) and the Motorola Type II systems are presented missing the final nibble. This is where the confusion comes in, new scanner users attempt to use that hex value (as it is presented) to program TG's for Type II systems when in fact it cannot be entered in the scanner directly and if using software must be adjusted to add the nibble back. Just to complete the description, Hex is not presented for LTR and EDACS systems.Voyager said:That works for 3600 systems since the last nibble is 0 anyway. It would not work on 9600 systems.