Building Automation Knowledge Base

Issue In order to troubleshoot random network issues, it is sometimes necessary to set up Wireshark to capture network traffic for an extended period of time. As Wireshark runs it decodes packets and its data structures grow. This causes performance issues and eventually, Wireshark may simply run out of virtual memory and stop capturing or crash. Product Line Andover Continuum, EcoStruxure Building Operation Environment Wireshark Cause Need to capture network traffic using Wireshark for an extended period of time. Resolution Open Wireshark and follow these instructions: From toolbar, select Capture -> Options On the Input tab, select input adapter. If necessary set capture filter. On the Output tab, perform the following: Browse capture file location and provide a filename. A timestamp will be added to the filename as a suffix. Ensure output format = pcapng Check Create a new file automatically Check After 1 and change seconds to hours Check when time is multiple of 1 and change seconds to hour Check use a ring buffer with X files. (Recommended settings are 96 hours (4 days) or 168 hours (1 week) so can retrieve files after long weekend or 1 week, respectively).  On the Options tab, perform the following Check last selection and change to 744 hours. (Recommended to capture for 31 days without stopping).  When an event happens, gather a capture with the timestamp before and after the event. One can ZIP the .pcapng files to save space when transferring.   NOTE: More recent versions of Wireshark ( 2.4.1.21317 ) make it very easy to set up a ring buffer from the Output tab of the Capture options. For older versions of Wireshark 1.x use the steps below When capturing data, Wireshark actually uses a capture utility called DumpCap to do the actual data capture. DumpCap does not decode packets as they come in and thus has a smaller memory footprint which remains constant. The only remaining concern is the size of the capture file or files which can be specified when starting the ring buffer to keep them from growing too big. DumpCap is found at the location where the Wireshark program resides which can be seen if you go to Help\About Whireshark\Folders Determine the index to the Ethernet adapter you need to capture on. In this example, the traffic seen by the Broadcom NetXtreme Gigabit Ethernet adapter will be captured. Index 1 is specified when starting DumpCap. Execute DumpCap with the following options dumpcap -i 1 -b files:3 -b filesize:10 -w C:]temp\abe.pcapng -i 1 specifies tp capture on the network adapter with an index of 1 -b file: 3 specifies to use a 4 file ring buffer. -b filesize:10 specifies to limit the file size to 10 KB (*** for a real life capture this number would be much bigger like say 100/200 MB) -w c:\temp\abe.pcapng specifies location and prefix for the three files In the screenshot below we can see the files in the ring buffer being used, once a file reaches the specified limit, the capture continues at the next file, files are names using the specified prefix as well as a date-time stamp that is updated each time utility dumps captured data in the file. Care should be taken to stop the capture as soon as possible once the issue under investigation takes place and before the ring buffer wraps around and overwrites the data.

Issue Continuum crashes with RPC error "The RPC server is unavailable" shortly after launching. RPC Server Error Product Line Andover Continuum Environment Cyberstation Cause Possible causes: Virtual memory, make sure virtual memory is set to recommended value. (see virtual memory requirement in Cyberstation installation document) Remote Procedure Call (RPC) locator service not started (Should be configured for automatic start) A resource needed by Continuum is not available. For example if an EventNotification is configured to page on alarm and there is no modem installed in the workstation then if an alarm is active on start up Continuum will encounter RPC error. Resolution Set workstation virtual memory to recommended value. Configure Remote Procedure Call (RPC) for automatic start. Make sure resource needed is available or reconfigure as needed.

Issue Duplicate Infinet ids can result if previously configured i1/i2 device is connected to field bus after power up. Environment All i1 and i2 devices. Cause Duplicate Infinet ids can result if previously configured i1/i2 device is connected to field bug after power up. Resolution When an Infinet device with an assigned Infinet id comes up before it joins the Infinet token passing it performs a self test routine that detects whether its id is already in use, in which case the device rolls its own id back to factory default (zero) and stays off the bus until commissioned. In order to make sure the duplicate id detection works, the device MUST be connected to the Infinet BEFORE it is powered up.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121, which does not have a D1 input. Product Line TAC Vista Environment Xenta 121 STR-150 Cause The correct terminal for the mode input from the STR-121 is labeled differently on the Xenta 121 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 121 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 6   The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 121. When the Xenta 121 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained inIs it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue Get a hard copy of all points in a controllers / system Get a hard copy of I/NET controllers' databases (SAV files) Environment I/NET Seven Cause Require a hard copy to view all points and database and / or extensions Resolution There is a feature under Network Functions which allows you to print (screen or default printer) any or all controllers save in your Network Configuration. This lets you get a printout of exactly what points and point extensions you have added to the controllers on your system. Select Edit >Host Computer >Network Functions from the main menu. The system displays the screen shown Choose the link of the controller(s) you wish to print from the drop-down list. The system now displays the controllers on the link you selected. Above the list are six push-buttons. Select the Print push-button. Choose the controllers you wish to mark for printing by either clicking on individual controllers in the list or by selecting All Yes. Controllers that are marked for printing will show a “Y” in the Print column of the list. Each click on a controller in the list will toggle the Print function between “–” and “Y”.  Select the Setup push-button at the bottom of the window. The window shown below appears. If you want the database report to print to the screen activate the Print to screen checkbox. Select the database items that you want to print by clicking on the Select checkbox. To select multiple links follow Steps 2 through 6 for each link and controller, selecting Close from the Database Print window to return to Network Functions, until you have selected each controller. Note: The TAC I/NET Seven system lets you select more than one link at a time but this results in a very lengthy printing session. If you do not want to tie up the printer for an extended period of time select only one link at a time. If N/A appears in the print column this means that the station exists for this controller, but no save file exists in the save file directory.   When you have selected the appropriate parameters, select Print to start the printing. When you have selected the appropriate parameters, select Close to return to the Network Functions window. Since database prints may be very long, make sure no manual control commands from the PC are needed during the time required for printing.   Select Close to return to the Network Functions window. This information is also available in TCON299 I/NET Seven Operators Guide - Chapter 2 Setup and Network Configuration

Issue Installation and configuration for SE8600 heat pump application Product Line EcoStruxure Building Expert Environment  SE8600 Cause Installation and configuration errors for heat pump application Resolution SE8600 terminal identification In typical HP application, you shall connect to following terminals below: Y2 = Compressor 2 | Y1 = Compressor 1 | G = Fan | RC = 24 Vac positive | C = Common << 24Vac common >> W1 = Auxiliary Heating stage | W2 = O/B = First stage heating | UI22 = Supply temperature sensor | UI23 = Outdoor temperature sensor Depend on specification document, the application may require addition controls and connections. Application shall be set to: HP for heat pump From winter to summer season, high BP is the outdoor temperature value ABOVE which the system transfer from auxiliary heat <> and maintain heating setpoint with the heat pump << default 32°C >>. Temperature shall be set per system geographical localization. From summer to winter season, low BP is the outdoor temperature value BELOW which the system transfer from heat pump <> and maintain heating setpoint with the auxiliary heat << default -24.5°C >>. Temperature shall be set per system geographical localization. * Outdoor temperature sensor shall be installed   Heat pump reversing valve operation O: energize valve in cooling operation << default position >> B: energize valve in heating operation Heat pump system

Issue The Drayton Theta YBL1 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBL1 Cause The Drayton Theta YBL1 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL1 Valve Body the following is required:- S-E SatchwellMB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL1 Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL1 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here.   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL1 Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here. Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   N.B. ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL1 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here.   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL1 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E until 1.532  Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, until 1.532. Cause Common IP (Internet Protocol) ports echo (7), daytime (13) and time (37) are open. Having any of these IP ports open may be a cause of concern for customers that are sensitive to network security issues; these customers include defense installations, financial institutions, and government buildings. Resolution The services using the echo, daytime, and time protocols have been disabled which prevents IP ports 7, 13, and 37 from being open. These services and protocols have no purpose during the normal operation of the MNB-1000. Disabling the echo protocol and closing of port (7) has the side effect that the MNB-1000 cannot be “pinged”. Using the command line program Ping will not detect an MNB-1000 that has firmware v1.50E installed. Use WPCT instead of Ping to verify communications with the MNB-1000. Click here to see the Release Notes for firmware Revision 1.50E. Update; In firmware 1.532, the ping function was re-initiated as the default.  Please see the TPA-IA-19-0004.00 Firmware 1.532 Release Notes.  It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue When opening I/NET and getting an Initialization failure error and unable to log on to start the program. Product Line TAC INET Environment I/NET Revision 2.40 and higher on Windows 7 PCs. Cause There was a security update that disabled the Named Pipes and TCP/IP that is required for SQL to run. Resolution Start , All Programs select Microsoft SQL 2005 or 2008 Expand Configuration Tools and select SQL Server Configuration Manager Select SQL Native Client Configuration and expand it then click on Client Protocols Verify that TCP/IP and Named Pipes are enabled Click on SQL Server 2005 Network Configuration and click on Protocols for MSSQLSERVER Verify that Named Pipes and TCP/IP are enabled Open up Services and verify that SQL Agent, SQL Server and SQL Browser are all running and set to automatic. Start the I/O Configuration and verify that the connection is made to the correct database Restart I/NET again and it should allow you to start the program now. For Remote Client with I/O Configuration: Repeat the above on SQL Server PC Ensure that port 50069, 1433 and 1434 are open between the PCs

Issue Time schedules are not switching off according to the workstation time. Time schedules are delayed. Product Line TAC Vista Environment TAC Vista, Xenta Servers and Controllers (280/300/400) Cause The Time in the TAC Xenta 911 and TAC Xenta controller is not the same as in TAC Vista Server. Resolution To check the time in the TAC Xenta controller follow these steps : Browse to the TAC Xenta controller Right Click on the controller and select Properties Select the Information Tab. This will display the time in the TAC Xenta controller To check the time zone of the TAC Xenta controller select the time settings Tab. Once the TAC Xenta controllers have been set in the right time zone TAC Vista server will sync them to the correct time. By default this occurs every 10 minutes The final step is to ensure the time and time zone of TAC Vista server is correct. To do that locate your TAC Vista Server object and right click then select properties.  Select the Information Tab to show the server time. This time is governed by the PC time so to adjust the PC time through Windows.

Issue Suprema Fingerprint Reader Integration Product Line EcoStruxure Security Expert Environment Security Expert Suprema Fingerprint Reader Cause Security Expert integrates with Suprema BioEntry, BioEntry Plus, and FaceStation devices. Enrolment is both quick and easy with users scanning their fingerprint or face at an enrolment reader. The Suprema reader uses the scanned data to create a credential template, including a card number, which it sends to the Security Expert Server. Security Expert then sends this template to any other Suprema readers that are attached to the system so that only one enrolment is required. Resolution The following information is available on integrating Suprema Fingerprint Readers with Security Expert A list of qualified Suprema devices and configuration details can be found in the Suprema Biometric Integration in Security Expert Application Note. There are some available help topics in the online help. In the Security Expert  Client go to ABOUT | HELP and search for "Biometric Readers" and "Suprema". Each Suprema reader requires a wiegand port on a controller / expander, a license (SX-BIO-SP) and an IP address. The amount of Suprema readers allowed is only limited by these numbers. 

Issue Personnel distribution shows error 5310 Product Line Andover Continuum Environment Cyberstation Cause Error 5310 (0x14BE hex) indicates a duplicate card number. Resolution Take a LAN capture of the distribution using Using WireShark to analyse communications on an Ethernet network and send it to PSS for analysis, a PSS engineer will decode the packet to extract the card number and card type that is being rejected as duplicate. Armed with the card number and type find the offending record in the DB and eliminate the duplication.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, Security Expert, TAC INET Environment Existing intelligent Building Management System Open Mind High Availability Solutions (Deprecated by manufacturer) everRun MX ztC Edge Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing the system's reliability. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility are site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measures to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components are the leading cause of failure, followed by a lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity. Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with EcoStruxure Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide For ztC Edge solution guide please look at the following link; ztC Edge guide   

Issue Getting modbus devices to communicate to Continuum may require some trial and error. Product Line Andover Continuum Environment Continuum Modbus RTU, ModbusRTU Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Manufacturers of modbus devices may have an offset for their register values and addressing these values requires trial an error. Resolution This article was created as a starting point. There are a lot of tools and methods to get values from modbus devices communicating. This resolution discusses some important concepts as well methods for trying to bring values in. The Modbus RTU protocol is a Master/Slave style of protocol. The Andover Controls CX will be the master on the Modbus RTU network. There can be only one (1) master at a time on the Network. The Slave number is always set in the third party device. This could be either a hardware setting such as dip switches or a software setting. Modbus-IDA (also known as Modbus.org) has set the limit that the slave address can be between 1 and 247. Address 0 is allocated as a broadcast message. The Andover Controls x-driver can support addresses in the range of 0-255. The third party manufacturer should be able to tell you what the expected function codes are for the points that you are interested in. Modbus.org has defined the function codes in a very loose manner and leaves it up to individual interpretation. Andover controls supports the following standard function codes: 1-8 15,16. Since when you request information from a Modbus RTU device you receive the exact value that is in the register Andover Controls has provided some special function codes that will help to convert some of the common engineering values into usable values. The listing in the x-driver documentation shows the special function code, what is expected from the third party and the equivalent function code that is truly sent to the device. For instance if a point is a Intel float and resides in the 40,000 range then function code 245 would be used in the Andover Controls x-driver. This will still send out a function code 3 in the Modbus message but the x-driver will take the value sent in from the third party device and convert it into a usable float. Most confusion occurs when talking about the data registers, (also known as addresses or channels). Modbus.org has the following statements about the addresses in the protocol document. All data addresses in Modbus messages are referenced to zero. The first occurrence of a data item is addressed as item number zero. For example: The coil known as ‘coil 1’ in a programmable controller is addressed as coil 0000 in the data address field of a Modbus message. Coil 127 decimal is addressed as coil 007E hex (126 decimal). Holding register 40001 is addressed as register 0000 in the data address field of the message. The function code field already specifies a ‘holding register’ operation. Therefore the ‘4XXXX’ reference is implicit. Holding register 40108 is addressed as register 006B hex (107 decimal). Register number also known as address. When setting the start channel number parameter on the x-driver tab the x-driver is expecting the exact decimal address that you are looking to obtain. For instance: if a device shows a listing for the first point to occur at 40,001 then the start channel number is typically 0. This can be confusing since some manufacturers have decided to have 40,001 as being 1 and not zero while others manufacturer have decided that 40,001 is 0. There are two ways of determining how the manufacturer has started the numbering system for the device if it is not documented: Method 1 is a trial and error method. Where you set the value to minus 1 of the register address, the actual register address and plus 1 of the register address and see which one you a response from. Method 2 uses a third party software to poll all the points to see what addresses are populated. There are many shareware Modbus RTU software packages on the Web. One such program is called ModScan32 by Win-Tech. www.win-tech.com Number of channels. The least amount of channels that will be requested is 1 so number of channels should always be 1 or greater. If the data is stored in multiple channels then you will need to set the number of channels equal to the number of registers. If you are not using a special function code you will need to set up a separate numeric with a manual log with the number of entries equal to the number of channels. When you poll for the value of the channels the data will then be stored in the manual log of this second numeric. The first element of the log will be the first channel that is requested. For instance if a value is stored in registers 40,000 through 40,003 then the start channel number will be set to 0 and the number of channels would be 4. Another numeric with a manual log of 4 would be created and linked in the x-driver numeric by placing the name of the new numeric in the annex point parameter. Once the x-driver point is polled the returning information will be stored in the annex point. The manual log of the annex point will contain the data for the 40,000 register in location 1. The data for each subsequent register location will be in the next manual log location. I.E. annexpoint[4] will contain the data for register 40,003 The Modbus RTU x-driver is a poll on demand x-driver. What this means to the user is that either a Plain English (PE) program, graphic or editing the x-driver numeric will cause a poll to occur. It is best to mirror the x-driver point and use PE to poll the x-driver points. A simple program would loop through and perform a simple line of mirroredpoint = x-driverpoint. This will avoid multiple polls to the same point tying up more CX resources then necessary. Then you can use the mirrored point in programs and graphics. If you try to get values from a slave device that is offline (not responding) the x-driver will poll each point three times before it moves on to the next point. This will cause the CX scan time to rise to seconds instead of tenths of a second. It is helpful to have a single x-driver point in the third party slave device that will return a known value, (Product ID or serial number for example). This can be used to avoid running the scan time of the CX up if the slave device can not communicate. Inside of the polling program try to poll for the value of this point. If the value does not come back then skip the polling for the rest of the points for this slave device. This point can also be used as an alarm for the offline device as well. For example: 1: If ProductID1 = 15 then Mirroredpoint1 = x-driverpoint1 Goto 2 else Goto 2 endif 2: If ProductID2 = 15 then Mirroredpoint2 = x-driverpoint2 Goto 1 else Goto 1 endif Some data may come back as a value when you need only a bit of information. In this case you will need to use the Bitand operator in PE to extract the exact bit that you are looking for. As seen below the PE code will take an alarm point from a Liebert AC unit and break out the individual bits of information. AC9_Alarm1 = x_ac9alarm1 'setting the mirrored point AC9_CommFail = AC9_Alarm1 bitand 1 'extracting bit 1 AC9_LocalOff = AC9_Alarm1 bitand 2 'extracting bit 2 AC9_RemoteOff = AC9_Alarm1 bitand 4 'extracting bit 3 AC9_HiHeadPrs1 = AC9_Alarm1 bitand 8 'extracting bit 4 AC9_HiHeadPrs2 = AC9_Alarm1 bitand 16 'extracting bit 5 AC9_LossAirFlow = AC9_Alarm1 bitand 32 'extracting bit 6 AC9_StbyGlycolOn = AC9_Alarm1 bitand 64 'extracting bit 7 AC9_LiquidDet = AC9_Alarm1 bitand 128 'extracting bit 8 AC9_ChangeFltr = AC9_Alarm1 bitand 256 'extracting bit 9 AC9_HighTemp = AC9_Alarm1 bitand 512 'extracting bit 10 AC9_LowTemp = AC9_Alarm1 bitand 1024 'extracting bit 11

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue Xenta OP menu items: Status, Sub menu, Week chart, Holiday chart, Alarm, Access Code, Edit Access Code, Date and Time, Daylight Saving have defined Access Levels: Low Level Medium Level High Level Accessing the medium or high-level menu items requires a password. What is the default password and how can they be changed? What if the passwords have been lost? Product Line TAC Vista Environment Menta Xenta Controllers Xenta OP Cause Accessing the medium or high-level menu items requires a password. Resolution The default password for accessing medium level menu items is: 1111 The default password for accessing high-level menu items is: 2222 These can be changed via the Xenta OP only provided the "Edit Access Code" menu item is present in the OP Tree. Downloading the controller may reset the access level passwords back to the default.

Issue Getting error "Communications failure due to routing device not available" when reloading BACnet Controller Product Line Andover Continuum Environment CyberStation 1.74 above b3 controllers BACnet bCX1 Cause Anti-virus applications can prevent the BACnet objects from saving into the Continuum Database (BACnet objects may also not appear on the BACnet side).   When you reload the BACnet controller which contains these objects, they are 'inaccessible' and the error is generated in the distribution property window Resolution Close Continuum CyberStation Disable all the Anti-Virus applications then restart Continuum CyberStation From the BACnet Device side, Right click the Controller you want to reload then select SendToDatabase, all the BACnet objects will appear under the controller. Reload the controller again.

Issue Can't communicate with more than 1 device on LG Gateway at the same time. Updated with solution on 12/15/2017 Product Line EcoStruxure Building Operation Environment LG Gateway Model:PQNFB17C1 Firmware version: 1.11.4 Cause The gateway can only provide one source address when there are multiple device IDs. The wireshark capture confirmed that no unique source ID provided by the gateway with different device IDs. Resolution Update the firmware version to 5.08.1h Configure the "BACnet Type Setting" to "B Type".

Issue Where can I find an End User Guide for G3 that’s not written for developers? Environment G3, WorkBench (all versions) Cause N/A Resolution Each G3 release zip file includes a document folder.  The PDF file titled docNaxBag.pdf (Niagara AX-3.x Browser Access Guide) is an end users guide and can be found in this folder.

Issue Reader Expander loses communications to the SP-C, how are Users authenticated when they attempt to access Doors controlled from this Reader Module? Which Users will still have access through Doors when the Reader Expander is offline to the (SP-C) Controller? Product Line EcoStruxure Security Expert Environment Security Expert SP-C SP-RDM2 Cause The SP-RDM2 Security Expert - Door Expansion Module - Installation Guide lists three options for how the SP-RDM2 should behave when it is offline from its SP-C controller.  The resolution below describes what each of these modes means. Resolution There are three options for how to handle access when the Reader Expander is in offline mode (not communicating with the Controller).  1. No Users Under Expanders | Reader Expander | General tab > Configuration section > Offline Operation, the “No Users” option removes access for any cards badged at these Readers. no one will have access while the Reader Expander is offline to the Controller. 2. Any Card Under Expanders | Reader Expander | General tab > Configuration section > Offline Operation, the “Any Card” option allows for any card at all to be granted access when the Reader Expander is offline to the Controller. This is the least secure option as anyone with a valid technology card, which is correctly formatted to either the Primary or Secondary formats defined for the Reader Expander, will be granted access. There is no validation of the card's Facility Code or Card Number. At present there is no option available for providing valid access on reading a card's Facility Code only. 3. First 10 Users plus Cache Under Expanders | Reader Expander | General tab > Configuration section > Offline Operation, the “First 10 Users plus Cache” option allows for the below Users to be granted access when the Reader Expander is offline to the Controller. The first 35 Users in that Controllers Database. The last 150 Users that have badged with valid access. Note: This options text description is an old reference and will be updated in a new software version to reflect that this supports the first 35 Users.