LarrySC said:
The answer should be NO. You have a conflict of Fleet Maps if both are type one and a conflict if one is type one and the other type two.
A workaround for this type of conflict is to program them all as Type-II. Every Type-I ID has a corresponding 12-bit value that is stored in the scanner - same with Type-II IDs. It's these 12-bit values that are actually tested when the PRO-95 looks through the ID list. The only remaining conflict (potentially) is if two systems happen to use the same 12-bit ID.
For example, imagine these four (hypothetical) systems:
A: Type-I, Fleet map E1P7. ID 002-07 is stored internally as 383 (0x17F).
B: Type-I, Fleet map E1P5. ID 100-12 is stored internally as 927 (0x39F).
C: Type-II. ID 6144 is stored internally as 384 (0x180).
D: Type-II. ID 14832 is stored internally as 927 (0x39F).
To enter A and B as Type-II, you'd multiply the decimal values (383 and 927) by 16, getting 6128 and 14832. One way to get these "Type-II values", already multiplied by 16, is to use Win95: set a bank to MOT and set the fleet map for the Type-I system. Enter the Type-I IDs. Set the Fleet Map back to all Type-II. The IDs will be converted to their Type-II equivalents. Copy/paste the IDs from this "scratchpad bank" over to the "real bank" (where the real bank is already set to MOT Type-II).
The only remaining talk group conflict is between B and D. The Type-II equivalent of B's 100-12 is the same as D's 14832. You only get to enter one of these in a single bank (technically, you can enter both, but the scanner will only display the first one it sees in the list, possibly subject to open vs. closed mode, TGID lockouts, sub-bank on/off, etc.).
-Don