As described previously, the FAC controllers do not support identifying themselves to an N2 supervisor as a SyS91 device type. As a result, you must reconfigure the N2 supervisor so that the FAC controller is mapped as a VND device. Also, if the FAC3613 N2 point mapping does not exactly match its N2 supervisor point mapping, then you need to reconfigure the N2 supervisor so that it does match the supervisor point mapping. The procedure for performing these changes depends on the type of N2 supervisor.
- For an N30 type N2 supervisor, perform these changes offline using the Project Builder tool. Refer to the Project Builder User's Guide (LIT-693205).
- For an NAE type N2 supervisor, perform these changes offline using the System Configuration Tool (SCT). Refer to N2 Integration with the NAE Technical Bulletin (LIT-1201683).
- For an NCM type N2 supervisor, changing the NCM database requires you to delete the old hardware and define the new hardware. The incremental DDL compile method (@NC+) using the DELETE keyword simplifies the NCM database change. GPL and JC Basic processes may not need to be recompiled. Refer to the DDL Programmer's Manual (LIT-630010).
- For an SNE or SNC type N2 supervisor, perform these changes offline using the SCT.
To make the FAC3613 replacement operation as similar as possible to the old DX-9100 controllers:
- Select a Supervisor Object Type that matches the replaced controller point.
- For multi-state objects, select an appropriate States Text table.
- Use the Supervisor Object Definition to restrict commands.