Building Automation Knowledge Base

Issue Encountered the following error when running the SNMP service: Start service: SnmpService [1272] SnmpService SnmpReceive: unable to create socketjava.net.BindException: Address already in use: Cannot bind Environment I/A Series R2 SNMP driver Windows Server 2008 Cause The SNMP ports are being used by another application / process. In this particular case, the SNMP Service (which is available in Windows Server 2008) has been enabled. Resolution The I/A Series R2 default ports for SNMP are 161 (receive SNMP requests) and 162 (receive SNMP trap messages). Check if the SNMP Service in Windows Server 2008 is enabled. If it is enabled and not in use: Disable it by stopping the service and setting it to 'Manual' so that it does not start whenever the computer reboot and starts. Uninstall it using Windows 'Add or Remove Programs'   Alternatively, you can change the SNMP ports in I/A Series R2. To do this,  in your station, go to the SnmpService properties, 'General' > 'Config' tab.

Issue How to automatically disable access for Personnel who's expiry date has passed? Environment Continuum Access Control Cause Want to automatically disable Personnel who's cards have gone beyond the expiry date. Resolution The below code sample can be used as a basis to provide this feature. It is a fallthru Workstation Program that can be triggered from one of the time related SystemVariables such as Hour or Minute. It uses the OpenList function to go through all Personnel in a specific folder and compare their expiry dates to the current Date and then disables them if required.   ========================================== 'Fall thru program that will search through the Personnel class for ' an expiration date that is less than today’s date. Object oAPerson Numeric nResult Line 1   nResult = OpenList("Personnel", oAPerson, Root\CardHolders) 'specify CH path Line 2   If nResult = Success then     While GetObject(oAPerson) = Success       'The next line will fail when the Expiration Date attribute is greater than 12/31/2037 (12/31/2099, by default)       If (Date > oAPerson ExpirationDate) then         Set oAPerson State = Disabled       Else         Set oAPerson State = Enabled       Endif     Print oAPerson Name, " is ", oAPerson State 'prints to message window for testing     Endwhile   Endif ==========================================

Issue Can Pelco's Control Point Software run on the same PC as I/NET Seven Software? Product Line Pelco, TAC INET Environment All Windows OS I/NET Seven Software Pelco Control Point Software Cause The two software packages are not compatible with each other. Resolution Pelco's client software cannot be installed on the same PC that is running TAC I/NET Seven. See TCON 301 - Chapter 6.

Issue An object’s override and set pop-up boxes do not fully open in Niagara G3. You have to grab and pull the corner of the pop-up to open it completely. Niagara version 3.5.x is installed on a Windows 7 PC. Environment Niagara G3 Version 3.5.x and older Cause Versions of WorkBench prior to 3.6.31 have not been officially certified with Windows 7. Resolution The issue is more of a nuisance, but does not affect functionality in any way. There are a couple of options you can try to try and correct the issue. The first option is to try to reduce the font size in Windows 7. - Click on the Start button and open the Control Panel - Open the Fonts folder and select Change font size. - Select smaller fro the font size and click apply The other option is to change the screen resolution slightly. Note: Since Niagara versions prior to 3.6.31 have not been certified for the Windows 7 operating environment, the above my not correct the issue.  

Issue LinePrinterRecipient 'Load Printer List' does not bring up a list of the available printers Environment I/A Series G3 Enterprise Network Server (ENS) or Enterprise Network Controller (ENC). Cause At this stage the reason that this occurs is unknown but the following resolution is the current workaround. Resolution Since you are not able to find the printer using the 'Load Printer List' button, you should just type in the name of the printer in the LinePrinter Recipient's properties 'Printer' field. To make sure you get the name correct, go to Windows Control Panel and go to 'Printers and Faxes'. Find the line printer and right-click on it to the properties. Copy the name of the printer. Go to Workbench and paste the name of the printer in the LinePrinter Recipient as per described above.  

Issue Is it possible to get Host ID locked licenses for Vista IV? Environment TAC Vista IV (Versions 3.30 to 4.50, using the Privilege Licensing system) Cause Since virtualization and other non USB/LPT dongle friendly applications are getting more common, a Host ID locked version of Vista IV is requested.  Resolution Vista IV was withdrawn in the end of 2011. The support is very limited, and Host ID locked licenses are not available. Suggest upgrading site to Vista version 5 where host ID locked licenses are available. Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue When reloading an ACX5720 the controller goes offline permanently and has to be power cycled to restore communications. Environment ACX5720 Reload Cause Controller is not able to establish communications following a soft reset. Resolution Reflash the controller to eliminate the reload recovery issue.

Issue The MN-S3, MN-S4, and MN-S5 sensors allow for local setpoint adjustment.  This ability is provided by configuring the sensors in WorkPlace Tech with a MNL or a MNB controller.  When a custom setpoint is entered via the sensor, is there a scenario when it could be replaced by the default setpoint? Environment MN-S sensors MNL controllers MNB controllers Cause End user described a situation where main power was lost in the building and all custom setpoints were replaced by the default setpoints. Resolution The only scenario when custom setpoints are lost is if the associated controller's database is re-installed and the MN-Sx sensor is disconnected at the time of the download.  Once the download is completed, and the MN-Sx is re-connected, the default values are used by the controller.  The custom setpoints have to be re-entered at the sensor. A power loss to the controller does not remove the custom setpoints.

Issue Can read temperatures but system does not control outputs. On the Site Stat Controller Interface the SS light is not flashing. Environment OnSite Cause Field wiring error. Resolution In this case someone had rewired the temperature sensor with the x1 and x2 terminations reversed. Once x1 and x2 were wired correctly normal operation resumed.

Issue Cannot upgrade CyberStation key. Environment CyberStation Cause Received key activation code from Repair Dept. to add an option to CyberStation. After entering the activation code into the KeyWriter application, getting the error "Invalid Key Activation Code: Please try again..."    Resolution There is a KeyWriter application for the Continuum Reports Add-On Software and a different one for activation codes from the Repair Dept..  Use ...\Program Files\Continuum\CyberKeyWriter2.exe for the codes from the Repair Dept.

Issue Can't display values from a Modbus IP device where it is using a data type of swapped Longint (32 bit). Environment Continuum Modbus IP XDriver (2nd Generation) v2.00012 and below CX9680 ACX5720, ACX5740 bCX1-9640, bCX1-4040 PM9C Power Meter Cause Modbus IP Xdriver did not support the swapped Longint (32 bit) data type. Resolution Support for this data type was added to the Modbus IP XDriver (2nd Generation) in v2.00018 which is available on The Exchange Download Center at the link below: E01_0210_215 Modbus TCP driver.zip

Issue Is TAC Vista creating a new IP connection every time it communicates with a Xenta server?   Environment TAC Vista 5.1.7 and earlier versions Cause When TAC Vista communicates with a Xenta server https is always used and a new connection is used every time Vista likes to communicate with the Xenta server. When Vista is communicating with a Xenta 911 http is used and one connection which is connected as long as possible is used even if it is silence long period of times. Resolution When TAC Vista communicates with a Xenta server https is always used and a new connection is used every time Vista likes to communicate with the Xenta server.  

Issue Connecting Modbus RS-485 to a CX9200 Comm4 will not operate correctly. Environment Modbus RTU XDriver Serial port XDriver Cause Different ports support different electrical standards. Resolution Comm1 and Comm2 of a CX9200 has RS-485 ports and can be used directly with the Modbus RTU XDriver. As a first generation controller it requires the 1st Generation driver. Second Generation X Drivers are only for the second generation controllers (bCX1, NC2 &ACX) The comm ports also have RS-232 ports that can be used and using an external RS-232 to RS-485 converter they can support an RS-485 network. On Comm 4 it has 2 ports they are RS-232 and RS-422 which is sometimes referred to as "4 wire RS-485". But this is not the regular 2 wire RS-485. The difference between regular RS-485 and RS-422 (4 Wire RS-485) is half and full duplex. The RS-422 with + and - connected is not a true RS-485 2 wire as the transmitted data will also be received by the transmitting controller (feedback). Regular RS-485 will turn off its receiver when it is transmitting.

Issue Is LDAP (Lightweight Directory Access Protocol) supported in Vista? LDAP is an application protocol for accessing and maintaining distributed directory information services over an network. Environment TAC Vista 5.1.X Cause Customer has a requirement for distributed directory access on their network. Resolution LDAP is not currently supported in Vista.

Issue Controllers Comm port has previously been used for Infinet and it is now required to change its operation to Modbus or another X Driver. Environment All CX controllers that support X Drivers CX9200, CX9400, CX9900, CX9940, bCX1, NC2 Cause When connected to a controller whose comm port is in infinet mode the mode can not be changed. Resolution Delete any Infinet controllers under that comm port in the database Go to offline editing, change the mode from Infinet to Autoset or Printer, apply the change. Go online. Reload the controller. You can now select X Driver mode and select the required X Driver file.  

Issue Unable to communicate as lights are solid red on the front panel. Environment All versions of I/Net Software. Cause The lights indicate that there is no communication to the device which can be caused by the failure of the power supply. This has been a known issue as those devices are not manufactured anymore and needs to be replaced. Resolution Replace the Legacy NPR 2000 with the Xenta 527-NPR.

Issue Xenta Server Error: Ethernet autonegotiation error (Error#: 59) Environment Xenta Server System Error log Xenta 527 Cause The Ethernet negotiation error comes from bad connection with the Ethernet switch. The negotiation is the low level negotiation between the PHY (physical layer) interface on the Xenta and the PHY on the switch. It negotiates speed (10/100 Mbps ) and duplex. This error can indicate a bad cable or other problems with the switch. Resolution Replace any patch cables Replace connectors on any suspected bad cables Use a different port on the ethernet switch. *Note that the Xenta Server Ethernet port is only capable of 10 Mbps. Speed negotiation is unnecessary if the port on the switch can be manually configured.

Issue Third party BACnet discovered successfully but CyberStation returns a "Segmentation not supported" error when an attempt is made to send the devices objects to the database. Environment CyberStation Third party BACnet device (in the case at hand the device was a  Liebert Mini-Mate) Cause Device incorrectly report its NPDU (Network Protocol Data Unit) as zero. Ask vendor to correct its BACnet implementation so as to have the device correctly report its NPDU capability. Resolution Ask vendor to correct its BACnet implementation so as to have the device correctly report its NPDU capability.

Issue Will the first generation Modbus RTU xdriver work on the CX9200? Environment CX9200 X-Driver Modbus RTU Cause Difficulty getting the Modbus x-driver working on a CX9200. Resolution The CX9200 works just fine with the 1 st generation Modbus RTU xdriver. 

Issue Sites have Continuum add-on reports and bacnet and try to use them for bacnet devices Environment Continuum Continuum add-on reports Bacnet Cause Continuum add-on reports do not support bacnet objects Resolution The latest version 20.0e of Continuum add-on reports now supports access to BACnet objects. Download Continuum add-on reports For further information on this or you would like to discuss it's development, please contact COE.Support@Buildings.Schneider-Electric.com . Other options for reporting are to use Continuum internal reports or a third party report writer (Excel, Access or Crystal Reports) to develop the reports needed.