Unable to link an I/A Series R2 UNC to a McQuay Microtech III DAC or SCC to clear alarms via nviClearAlarms.
I/A Series R2, UNC-410, UNC-520
The nviClearAlarms is used to clear faults, problems, warnings, etc. from a McQuay Microtech III controller. The variable used by McQuay is a UNVT (user network variable type) and requires a combination of objects to connect and control.
This Lessons Learned specifically details the interface to the newest Microtech III shadow objects as shown below. The same general solution can be applied to other McQuay devices as needed.
McQuay Microtech III Applied Air Unit Controller DAC - MtIIIAhuDac01B (80:00:25:56:0A:03:04:B2)
McQuay Microtech III Applied Air Unit Controller SCC - MtIIIAhuScc01B (80:00:25:55:00:03:04:B2)
Note: Update the lonMicrotechIII jar file to version 535b or higher. An issue with UNVT definitions prevented the DynamicMux object from properly interfacing to the nviClearAlarms on the MtIIIAhuScc01B shadow object. The lonMicrotechIII-2.302.535b.zip file can be downloaded from The Exchange Download Center
- Add a DynamicMux object from the tridiumx lonworks jar (conversion folder) to the workspace. Connect the DynamicMux object to the nviClearAlarms input.
- Add a Program object to the workspace. Edit the Program object and add the program text from the appropriate text file. Compile the Program object and link to the DynamicMux.
- Add a Multistate Output object and configure the Visual stateText to the desired values shown below. Link the Multistate Output object to the Program object.
0 = None
1 = ClearAllFaults
2 = ClearAllProblems
3 = ClearAllWarnings
4 = ClearAllAlarms
default = Error