Cool!
Can anyone advise on what happens if I try to take a 396XT file for a trunked system having multiple sites (such as for statewide systems) and try to program that file in a 396T which doesn't do multiple sites? Does it simply capture the first site it sees and programs the associated control channels into the 396T (pretty much overlooking the remaining)?
If you're trying to take a FreeSCAN file, for a model that supports "multi-site", such as the 396XT, then use that to load one of the earlier models that
don't support multi-site, such as the 396T, FreeSCAN will make the conversion for you. If a system is entered, for the 396XT as an example, as "multi-site", FreeSCAN will break that into individual systems, for each "site", duplicating the talkgroups & groups in each one as they are set in the original "multi" file. As an example, this small multiple site
system in my area is entered in my master file as a one system, with all four sites. It loads that way in the 396XTs or the 996T. However, if I instead use the same file to program it into my 396T, I end up with four systems, one for each site, each system with the same full complement of groups and talkgroup ID's.
This change os made as the file downloads to the scanner that does not support multiple sites. The original source file is not changed. FreeSCAN won't convert a 396Tfile, with multiple systems, into a multi-site file, for the 396XT. But you can accomplish this by using the cut and paste commands to move the sites from independent systems into just one, multi-site, system. That is exactly what I did to create a file for the 396XT originally. For that same system linked above, I took the individual systems from my 396T file, and rolled them into one, which I then used for the 396XT.