You can configure the FAC3613 or CGM09090 controller to identify itself to an N2 supervisor as an AHU device type. If you configure the FAC3613 or CGM09090 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 FAC3613 or CGM09090 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 SNE or SNC type N2 supervisor, perform these changes offline using the SCT.
For replacements that use the AHU Device Type, the following point mapping restrictions must be observed.
- The range of allowable Point Addresses for each mapped Network Point Type is restricted.
- CCT N2 Point Mapping tool does not enforce these restrictions; an application could be configured with CCT that results in points that cannot be mapped into an N2 supervisor.
- Many of the allowed ADF, ADI, and BD Point Addresses are Read Only, meaning no commanding is allowed.