NOTE: Before making any of the changes below, please read the related
AX sections in this document to understand current limitations. Currently, there is no known utility to “convert” the existing
application database (appdb) of an
R2 Web Supervisor into a format that can be “merged” into the existing
AXSupervisors collection of histories and alarm database.
- If mastering
R2 Schedule objects from the
AX Supervisor (or another
AX controller), and they are currently “slaved” to another
R2 Schedule, you need to first unlink those slaved
R2 Schedules (remove externalSubscription at “slaveIn” input). For more information on engineering for the “
AX side,” see “
AX Supervisor engineering” on page 2-7.
- Depending on how log archiving is to continue for any
R2 JACE station, you may wish to change the setup of the station’s LogService, with the following Config tab properties:
- archiveMode — from “archive_remote” to “archive_local”.
- archiveAddress — uncheck Supervisor entry
- Depending on alarm/alert management is to continue for any
R2 station, you may wish to change the setup of the station’s NotificationService, with the following Config tab properties:
- alarmArchiveAddress — uncheck Supervisor entry
- archiveMode — from “archiveRemote” to “archive_local” (if the JACE-403/JACE-545, “archive_local_no_SQL”).