Building Automation Knowledge Base

Issue Which auxiliary switch is used on with the MV15B actuator? Environment MV15B S2-MV15B 8800469000 Cause Some applications requires an aux switch to the actuator. Resolution The S2-MV15B, part no 8800469000, is the correct auxiliary switch for this application. 

Issue Which valve actuator is the correct choice for V222?  Environment V222 7212254000 7212258000 7212262000 7212266000 7212270000 Forta M22 M50 Cause Suitable actuators for V222 Resolution For V222 DN65 to DN100, the Forta series is the recommended actuator. For V222 DN125 and DN150, M22 or M50 should be used. The Forta series actuator will not fit these valves.

Issue If the WorkPlace Tech Tool application file has been modified when you attempt to monitor a controller containing that application, blank or incorrect monitor tag values will be displayed. Environment WorkPlace Tech Tool software versions 5.0 through 5.8.2 or 5.8.6 MNL or MNB controller loaded with an application downloaded from WPT Visio 2003, Visio 2007 or Visio 2010 Cause There are two causes: First, the WPT software, release 5.8.3, 5.8.4 or 5.8.5 will modify the application when it is opened making it appear to be different than the previously downloaded application Second, failure to observe the following three constraints, regarding the application .vsd file will make the application file appear different than the application previously downloaded: The application file (.vsd) must not have been modified and/or re-saved in any version of the WorkPlace Tech Software since the application was downloaded. The application file (.vsd) must not have been modified directly in Visio and re-saved. The application file (.vsd) must have been last saved, compiled and downloaded using any version of the WorkPlace Tech Tool software, 5.0 through 5.8.2 or 5.8.6, running in Visio 2003, 2007 or 2010.   Resolution An application downloaded to an MNL (or with the compatible WPT version, MNB) controller can be monitored provided that the application .vsd file has not been modified or re-saved after download and that the current version of the WorkPlace Tech Tool software, versions 5.0 through 5.8.2 or 5.8.6 (not versions 5.8.3, 5.8.4 or 5.8.5)  is being is being used with a compatible version of Visio (2003, 2007 or 2010). NOTE: For MNB controllers this applies only to WPT versions 5.7.0 through 5.8.2 and 5.8.6 as the earlier versions are not compatible with MNB application development.

Issue A LON -USB adapter is configured as LON2 on a Windows laptop.  Several efforts were made to modify its address to LON1 but to no avail.  Running a Niagara R2 station on a laptop, with the LonWorks Service, defaults to using LON1 for the interface.  Can LON2 be used instead? Environment Niagara R2 Cause Unable to modify the adaptor's LON address Resolution In the Admin Tool, modify the drivers.properties file located on the Installation tab. Change the line "lon.deviceName=LON1" to "lon.deviceName=LONx"      where x = new port number. Restart the station.  

Issue Can't find AREAPURGE part number in parts list or iPortal. Environment Continuum Add-on Software from COE Cause The AREAPURGE is an Add-On application made, and supported, by the Security Center of Excellence (COE). It has also had the part number "AE-PURGE".   Resolution Unfortunately, COE has informed us that this product is discontinued and is no longer available for sale.

Issue The IO Module does not report input signals and all physical outputs are turned off. The IO module status LED blinks at a rate of one blink per second. Product Line EcoStruxure Building Operation Environment I/O Module Cause The IO module has been placed into Low Power Mode. Resolution  I/O Module Low Power Mode In order to save energy, an I/O module can be placed in low power. When an I/O module is in low power, the following conditions apply: The I/O module does not report input signals and all physical outputs are turned off. The Module status reports low power. The I/O module's LED pattern indicates low power (the slowest green LED blink pattern, approximately once every 3 seconds). When you set an I/O module to low power, the software turns off all outputs. When you want to recover an I/O module from low power, there are several points to consider: Make sure all I/O module Output values are set to a safe level before a return to normal power conditions. This prevents "power surge" conditions. After normal power resumes, the Output values set are reached immediately after any timing delay occurs. Setting and Recovering an I/O Module from Low Power Place an I/O module in low power mode in order to save energy and then recover that module later.   To set and recover an I/O module from low power In WorkStation, in the System Tree pane, expand the IO Bus. Click the I/O module that you want to put in Low power mode. Click File and then Properties. Under Configuration Settings, in the Low power box, select True. Click OK to change the value and close the Properties tab. If the physical I/O module, shown in the System Hardware folder, matches the logical I/O module defined in the I/O Bus, the I/O module goes into Low power. After the physical module enters low power, the Module status attribute in the Status Information area displays Low power.  To set and recover an I/O module from low power In the System Tree pane, expand the IO Bus to recover from low power mode. Click the I/O module to recover. Click File and then Properties. Under Configuration Settings, in the Low power box, select False. Click OK to change the value and close the Properties pane. If the physical I/O module, shown in the System Hardware folder, matches the logical I/O module defined in the I/O Bus folder, the I/O module exits from low power. After the module resumes operation from low power, the Module status returns to the status it had before it went into Low power. NOTE: If unable to change the Low Power property: Export the contents of the I/O module Deleted it from the AS Re-add it to the AS Import the XML back into the module

Issue Analog Pulse Command Object Environment I/A Series R2 Cause A standard I/A Series Analog Output object will send a value periodically or when there is a change of value. However, the lighting control system requires a pulse command type.  Resolution There is a 'Fp1Shot' object in the programlib library which can functions as an Analog Pulse Command. This object is located in tridiumx > programlib > util.  If you go to the properties of the 'Fp1Shot' object, you can set the minimum and maximum values that allowed to be set. You can also set the delay time which determines how long the value should hold before being released.  If you go to the properties of the 'Fp1Shot' object, you can set the minimum and maximum value allowed to be set. You can also set the delay time which determines how long the value should hold before being released. 

Issue How fast are the IO Modules polled by the Netcontroller? Environment NCII, Netcontroller CX9900 IO Modules UI-8-10, DI-8, DI-6-AC, MI-6, DM-20, AO-4-8, DO-4-R, DO-6-TR. Cause Information on the update speed of the I/O Modules is required. Resolution It is a polling network with the NCII as the master polling the slave IO Modules: Utilizes a polling protocol in which information is retrieved from I/O modules NetController polls each I/O module by Module ID number Modules are polled at a 50ms rate If Less than 4 modules, the polling rate is 200ms

Issue After selecting a photo and trying to save it in the Image Enhancement screen, the above error pops up.  Environment CyberStation 1.94 Cause Not certain - but possible Windows user profile corruption. Resolution Uncheck the resize box under the capture options. Logged into Windows as another user and the issue was not seen. The Windows user with the problem was deleted (this was not on a domain) and recreated.

Issue All Controllers have recently gone offline to one Cyberstation and get an error trying to access the Windows Firewall Environment Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause The Windows firewall has become corrupted either by a bad sector on the hard drive or by a virus/malware Resolution Check the Windows event viewer application and system logs to see if there are errors that happen when accessing the Windows Firewall. For example, if there are bad hard drive sectors, run a chkdsk. Take the appropriate action to correct the issue. Run Antivirus and ensure the PC is clean Run Anti Malware software (Ex. MalwareBytes, Spybot, etc.) and ensure the PC is clean Repair the Windows Firewall http://support.microsoft.com/kb/920074 A couple of other options would be to go to a Windows Restore point prior to the issue or Format the Hard Drive, reinstall Windows and Cyberstation.

Issue What properties of a signal is exposed in SmartStruxure via TAC Vista SmartStruxure Interface? Environment TAC Vista SmartStruxure Interface SmartStruxure Cause What properties of a signal from TAC Vista can be seen in SmartStruxure? Resolution Value (read/write) Unit (read only) Description (read only)

Issue How does TAC Vista SmartStruxure Interface affect the field bus traffic under TAC Vista? Environment TAC Vista SmartStruxure interface SmartStruxure TAC Vista Cause Does the TAC Vista SmartStruxure Interface ask for all values that are hosted and how often? Resolution TAC Vista SmartStruxure Interface creates subscriptions to the TAC Vista server and only asks for values that are being used. When you set up the EcoStruxure web service interface, you also set up how often the values get polled in the "value poll interval."

Issue PIMS are going offline intermittently, so that the doors won't unlock Environment Continuum Windows XP Windows 7 Windows Server 2003  Windows Server 2008 Cause If doors 1-8 are addressed on one PIM and also 1-8 (even though they are different doors) are addressed on another PIM they will conflict with each other Resolution The PIM configuration specifies that Doors 1-16 are addressed on one PIM and 17-32 be addressed on another PIM

Issue Does the Modbus XDriver interface with the ATV212 speed drive? Environment Continuum Modbus XDriver Cause Unable to get Modbus RTU communications working with the ATV212 drive. Resolution Unfortunately, this does not work. The Modbus XDriver's cannot reference the large number address range that the ATV212 uses (above 64,000).   A workaround for this would be to use the BACnet MSTP interface available on the ATV212 to establish communications.

Issue On two occasions all of the scheduled periods disappear from the schedule. Environment AS Schedules Exception Schedules Cause Weekly scheduled times were entered as exception schedules. Resolution Recurring periodic scheduled event which occur week after week should be programmed as weekly schedules.  Exception schedules are used to override weekly scheduled events.

Issue After changing the engineering and electric scale with the spreadsheet the implicit logs stopped working Environment StruxureWare version 1.3 Cause It is not possible to recreate this problem in version 1.3 SP1. Resolution Upgrade to version 1.3 SP1 will solve the problem.

Issue In Vista 5.1.8 the line break character of the internal trend log file format was changed from the previous CR+LF to LF.  This can break some third party reporting and editing tools. Environment Vista 5.1.8 Cause In Vista 5.1.8 the line break character of the internal trend log file format was changed from the CR+LFof previous versions to LF Resolution Apply Hotfix 38 to Vista 5.1.8.  This restores the trendlog file format used in previous versions.

Issue Characteristics may be necessary for some applications. Environment SLO320 006920640 SLR320 006920630 Cause Output characteristics not defined in documentation Resolution SLO320 / SLR320 has 2 light ranges selectable by jumper: 400 Lux and 20 Kilo Lux. Depending on output this means:  400 Lux              - 0-10V -           0 V = 0 Lux, 5 V = 200 Lux, 10 V = 400 Lux                           - 4…20mA-       4mA=0 Lux,12mA=200 Lux, 20mA=400 Lux  20 Kilo Lux         - 0-10V -           0 V  =0 klx, 5 V   =10  klx,  10 V   =20 klx                           - 4…20mA        4mA=0 klx, 12mA=10  klx,  20mA =20 klx

Issue Unable to Bind to an I/NET Point Command Error Alarm after Binding to an I/NET Value Product Line EcoStruxure Building Operation, TAC INET Environment StruxureWare Workstation Cause As of version 1.4, I/NET input points can not be bound to SmartStruxure outputs. A Command Error Alarm will occur when attempting to bind to an I/NET controller that does not have the current bin file Resolution If needed create an additional I/NET output point and use that to control the I/Net input point via a Calculation Point Extension. In I/NET, connect to the controller. Select Edit > Controller > Configuration If the Build Date is older than April of 2012, you will need to upgrade the controller. In StruxureWare, when setting up the bind to the I/NET point, be sure to edit the I/NET point objects bindings, if that is what is being controlled. Bind the desired StruxureWare value to Control Value (DO) or Value (AO) property of the point for I/NET.

Issue Pinpoint will not open on one workstation. or some parts of a graphic will not work. Deleting the Pinpoint.ini file form the C:\Windows folder fixes the problem for a time, but the problem recurs later. Environment Pinpoint Pinpoint.ini Display Driver Cause When original Dell display monitor that came with the PC had failed, the customer installed an older Hewlett Packard display without installing the appropriate display driver.  The contents of the Pinpoint.ini is not written not by Continuum, but by the Microsoft Foundation Class API.  The ini file contains information on screen resolution, the number of tool bars, and the position and placement of each tool bar. Looking at the Pinpoint.ini file it can be seen that the API attempted to write the information for Pinpoint Design Mode toolbar 1 twice.  The second tool bar property section contained an identical BarID number but none of the other information such as X position, Y Position, Docking state, etc.  It appears that Pinpoint was starting without sufficient information to place the tool bar and would crash.  The API also wrote that their were 11 tool bars when this miswrite meant that there were actually 12 tool bar specifications written.  Resolution Install the proper display monitor driver. Pinpoint crashes will no longer occur.