One issue I see with IDAS Type C TGID's. I think it's more of a BCDx36HP issue because the TGID's in the RRDB are in the correct format.. There are only 3 IDAS Type C systems in the RRDB(compared to 40 Type D) so don't know if it's a big issue. sid=7930, 9218, 9635. The Type C TGID's are in a decimal format.
The scanner TGID Format parameter has only 2 choices. NXDN and IDAS. When the TGID Format is set to IDAS, it expects the TGID to be in a LTR like(or Type D) format. I would think the scanner should have three choices NEXEDGE, IDAS Type C, & IDAS Type D.
I don't know how to handle Type C systems in ProScan Import. Do I set the TGID Format to NEXEDGE (I'm leaning towards this but it will be confusing to the user) or do I set the TGID Format to IDAS which will format the Type C decimal TGID's to a LTR like format.
The scanner TGID Format parameter has only 2 choices. NXDN and IDAS. When the TGID Format is set to IDAS, it expects the TGID to be in a LTR like(or Type D) format. I would think the scanner should have three choices NEXEDGE, IDAS Type C, & IDAS Type D.
I don't know how to handle Type C systems in ProScan Import. Do I set the TGID Format to NEXEDGE (I'm leaning towards this but it will be confusing to the user) or do I set the TGID Format to IDAS which will format the Type C decimal TGID's to a LTR like format.
Last edited:
