As described previously, you can configure the FX-PCG controller to identify itself to an N2 supervisor as a UNT device type. If you configure the FX-PCG this way, you do not need to reconfigure the N2 supervisor in this regard.
Also, if you configure the MASD application to automatically generate the N2 mapping table, then you do not need to reconfigure the N2 supervisor in this regard. However, if the FX-PCG N2 point mapping does not exactly match its N2 supervisor's point mapping, then you need to reconfigure the N2 supervisor so that it does. 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 FX Supervisory Controller type N2 supervisor, perform these changes offline using FX Workbench. Refer to the FX Workbench User's Guide (LIT-12011149).
For replacements that switch to VND Device Type, point mapping is unrestricted. To make the FX-PCG replacement operation as similar as possible to the old UNT device:
- 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.