You can configure the CVM or FEC family controller to identify itself to an N2 supervisor as a VAV device type. If you configure the controller this way, you do not need to reconfigure the N2 supervisor in this regard.
If the CVM or FEC family controller's 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).
- To change the NCM database on an NCM type N2 supervisor, you must delete the old hardware and define new hardware. If you use the DDL compile method (@NC+) with the DELETE keyword, this simplifies the NCM database change. You may not need to recompile the GPL and JC Basic process.
- For an SNE or SNC type N2 supervisor, perform these changes offline using the SCT.
To make the CCT controller replacement operation as similar as possible to the old VAV1xx 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