Building Automation Knowledge Base

Issue How does the Xenta 121 indicate that a fan feedback failure condition has occurred? Environment Xenta 121-HP Xenta 121-FC Cause The fan failure signal could be used to trigger another sequence of events, to annunciate an alarm in the Workstation, or to send an email to the on-call mechanic. Resolution The output SNVT, nvoSystemStatus bit 15, represents a fan failure condition.

Issue In Vista 5.1, TGML graphics bindings can be bound using a multi-bind .[OBJECT] bindings. Dragging and dropping a single object can then automatically bind all other defined signals, for example. But there is a limitation of two network levels. Environment Vista 5.1 Workstation TGML Graphics Bindings window Cause Controllers with standard naming (especially application specific controllers with pre-defined naming) can be bound to graphics more quickly and efficiently with the use of multi-binding. There are limitations to what can be multi-bound simultaneously. Resolution Multi-binds can bind all defined signals for up to two levels of their database structure. For example: RoomTemperature.[OBJECT] can be used to bind: RoomTemperature.PV and RoomTemperature.OVR You can travel up one more level, though to get even more signals at once: SUMMARY.[OBJECT] can be used to bind: SUMMARY.RoomTemperature.PV and SUMMARY.RoomTemperature.OVR and SUMMARY.RoomSetpoint.PV You cannot travel up any more levels, so you could not do: LonworksNetwork.[OBJECT] in order to bind all signals in a network at once.  

Issue Attempts to login are unsuccessful and device reports that logins are blocked. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Xenta Server tracks attempts to log in by recording the IP address and Username of the login attempt. After 5 login attempts it will block any attempts to login to with that username and IP address for 10 minutes. Resolution Use a different user account on the Xenta Server to login and perform the necessary work or wait 10 minutes for the lockout to expire. If the lockout is continuing after 10 minutes then ensure that if the Xenta Server is in a Vista database that it is not running and trying to communicate to the Xenta Server with an incorrect username and password. Any changes to the root user password must also be changed in the Vista database to avoid perpetual blocking of login attempts on that computer and IP address.

Issue Getting an “out of memory error” when converting a station’s database from Release 2.301.330 to Release 2.301.529. Environment Niagara R2, UNC-520-1, UNC-410-1 Cause The sns file was used to convert database from 330 to 529  Resolution The XML copy of a station’s database should be used when bringing older version of R2 databases forward.  Convert the XML file to DB locally. Any errors will be discovered during the conversion.  Fix any error that may appear.  The database can now be downloaded to the UNC

Issue What is the procedure for upreving from 1.31 with MS Access to 1.93? Environment CyberStation Cause No supported upgrade path when upgrading Continuum system that uses MS Access database to SQL database. Resolution Since there is no direct upgrade path the only option is to export everything to dump files from the old MS Access Continuum system then import into a new SQL ContinuumDB in new version of the CyberStation. Graphics files from the old system are not compatible with new version of the Pinpoint Continuum application and will have to be discarded, although it may be possible to re-use bitmap files.

Issue  Windows 7 Enterprise is not listed in the compatibility matrix for Continuum versions 1.93, 1.94, 1.94SP1 and 2.0x Environment Windows 7 Enterprise Continuum versions 1.93, 1.94, 1.94SP1 and 2.0x Cause  Windows 7 Enterprise is not listed in the compatibility matrix as a supported OS for Continuum versions 1.93, 1.94, 1.94SP1 and 2.0x  Resolution  All versions of Windows 7 require product activation.  Windows 7 Enterprise can only be activated with a Volume License MAK or KMS  Key if it is not activated against a local KMS server. Enterprise requires a  VL KMS/MAK out of the box or activation against a local KMS server. It can  be rearmed up to 3 times.  Windows 7 Ultimate edition activates conventionally via the internet to  Microsoft activation servers.  Unless you are in a business enterprise environment, then Windows 7  Ultimate should be your choice. The Windows 7 Enterprise features and code are the same as Windows 7 Ultimate. Windows 7 Enterprise is supported.  Code is the same as Windows 7 Ultimate.  Windows 7 Enterprise is supported.

Issue After running LANMON 3 on an I/NET C-LAN, it may return some error codes. The list below will help determine what they mean and the best way to address them. Environment I/NET Controller LAN LANMON output text file Cause Controller LAN errors captured by the LANMON program. Resolution One of the most useful new features of LANMon 3.0 is the detection and labeling of several types of communications errors. The label associated with the detection of a communications error is stored in the disk file just in front of the communications packet to which the error label applies. The error labels are presented in ASCII text along side the hexadecimal data. This text should allow most I/NET technicians to perform some level of useful investigation into controller LAN communications problems and reduce the necessity for sending LANMon files in to Technical Service for analysis. The following paragraphs lists the error descriptions associated with the type of errors detected by LANMon. The Bold text represents the label you will see on the screen or in the capture file when LANMon detects that type of error. ERR: Retry This error indicates that LANMon has detected a retransmission of the same command. This is the most common error type and can be used to find which controllers are having problems receiving from others. You should reference the destination and source addresses listed in the retry packet and accumulate/record this information. If there is a prevalence of specific nodes (destination or source) showing up in the retry packets, this would serve as a significant pointer to examine for network problems in that physical area (possibly in the cabling, environmental disturbances, power, grounding, and controller hardware and/or application software) ERR: LAN reconfiguration This error indicates that LANMon detected the occurrence of a LAN reconfiguration. This is a normal expectation when a controller/node is added or removed from the network as a result of LAN cable disconnect or power. When intentional changes are not in-work on the network configuration, a LAN reconfiguration is typically the result of several sequential errors (typically retry’s) which prompts the sending controller/node to initiate a LAN reconfiguration on the basis that it appears a node has been lost and everyone needs to have a new picture of the network layout. ERR: SDLC CRC Error This error indicates that the LANMon Tap received an RS485 packet with incorrect CRC indicating the packet is corrupted in some way. This error results from data distortion on the cabling or from intermittent disruptions such as from EMI, noise or grounding fault. With this error, the primary address you are interested in is the source address. If you are seeing a number of CRC errors from the same node address, or a collection of node addresses, you may want to look for cabling or loading problems in that area, or the length of cable getting to the area. You should make note of where LANMon is positioned when seeing this error. The error could be expected to get worse as to get further away from the reporting node address. For this reason, it is often recommended that you perform LANMon captures and analysis from at least two points on the network and those points should be the two most distant ends of the network. ERR: LAN master conflict with ## This error indicates LANMon has detected a NULL command output from a controller/node other than the currently recorded LAN master. The ## number will show the address of the node currently understood to be the LAN master. The packet following this error message will contain the address of the contending LAN master. This master conflict error is frequently the result of multiple simultaneous LAN reconfigurations. There should only be one LAN master and it is the function of that one LAN master to output the NULL command each time the token makes one pass around to all the network addresses and arrives back at the LAN master.   The following error descriptions will be encountered far less frequently and are not typically used for LAN diagnosis. ERR: Bad address LANMon detected a destination or source address greater than 3F16 (6310) ERR: Bad NULL LANMon detected that NULL was sent out without the same destination and source address, or without the broadcast header. ERR: Bad reconfigure LANMon detected that reconfigure command “01” was sent out without the same destination and source address, or without the FF broadcast header. ERR: Bad token LANMon observed what appeared to be a token command but had byte count greater than 3, or had destination and source addresses the same. ERR: Frame overrun LANMon received >160 bytes on the Async port from the LANMon Tap which exceeds design limits/expectations. ERR: Frame underrun Async frame from LANMon Tap to PC was considered too short to contain any SDLC (CLAN) data. ERR: Lost frame synch The LANMon program running in the PC got out of synch with the data stream from the LANMon Tap. This should be an unusual error. If it is repeatedly encountered, You can try running the LANMon utility on a faster PC, or you can try running it with Monitor mode OFF. B E1 m N O ERR: Bad frame CRC The LANMon program detected a CRC error in the Async frame of data from the LANMon Tap. With the standard short (6 ft.) RS232 cable between the PC and Tap, this should be a very infrequent error. ERR: Unknown error code This is a catch-all error indication intended to present any error codes returned from the SDLC controller in the Tap that are not currently defined. You should not see this error message. ERR: Frame too short The Async frame of data from the Tap to the PC is considered too short to contain a valid SDLC packet.

Issue Replaced HID Prox Pro on ACX781 and still not working. Environment Continuum 1.8X ACX781 Windows XP Cause The ACX 781's cannot provide adequate power for the HID readers. Resolution Power the readers with an external power supply.

Issue Can the Niagara R2 MailService (SMTP) port number be changed to something other than its default port number of 25?     Environment Niagara R2 CoreRuntime 2.301.429.v1 and later Cause Local IT may require SMTP messages be sent on some port other than the typical port 25. Resolution MailService can now use non-default port for SMTP. Previously, only SMTP port 25 was supported for the MailService. Starting in coreRuntime 2.301.429.v1 and later, you can specify an alternative port for SMTP. The port is assigned in Config property of the MailService.  - Under the Service container, open MailService Properties then click the Config tab.  - In the smtpHost property, enter the IP address of the SMTP server using format: or . Example: ourMailSrv:40 or 10.10.9.4:40  Note: A station restart is required after entering (changing) the SMTP host. If the port number is omitted, MailService use default port 25.

Issue When a SHR100-T is setup with a 0-10 volt humidity sensor the temperature reading fluctuates Environment Xenta controllers I/NET Controllers SHR100-T Temperature Humidity Sensor Cause Interference from the 24Volt AC power supply in the same cable causes this temperature fluctuation. Resolution  The two tested fixes that stabilize the temperature reading are. Set the humidity as a 4-20mA signal, this will stabilize the temperature reading. Run the 24Volt AC power supply in a separate cable. This is the better option if this is noted before installation is started.

Issue The following error message occurs when starting OGC editor on a remote PC using remote desktop: "Local TAC Vista Server not started. Cannot reserve graphic object". Environment Vista 5.X Remote Desktop Windows XP Windows 2003 server Windows 2008 Server Windows 7 Cause There are two ways of connecting with remote desktop - connect to the console session or create a new session. The console session is what you see when you log in locally on the server. If you create your own session that is not the same as what’s shown on the server’s own monitor. If you start a programme in a new session this will not be seen in the console session. Each new session receives a new session ID. Resolution Connect to the remote desktop using console admin mode. Click on Start\Run and then type mstsc.exe /admin Log on to the remote desktop with a user that has administrator rights on the remote PC. Confirm that you are connected to the console session. Start OGC graphics editor. Open the task manager - Right-click on the task bar and select Task Manager. Select the tab Processes. Ensure the column Session Id is shown. If not go to  View\Select Columns and select Session ID Locate the process TADRAW.exe process and ensure that the session ID = 0 (in other words the console session) Please note that Schneider Electric does not officially support this method of running programs.

Issue Is TAC Vista webstation 5.1.X supported on Windows 7? Environment Windows 7 Webstation 5.1.X Cause Webstation works with Windows 7, but the reason why it's not officially supported is that the number of concurrent connections is limited to 10 (the same as in XP). Resolution Webstation is not supported on Windows 7. If/when an issue arises our advice will be to upgrade to a server (2003, 2008) as unexpected behaviour may be resolved simply by doing this.

Issue ACX57xx supported communication channels  Environment CyberStation ACX5740 ACX5720 Cause Not known cause Resolution The ACX5740 and ACX5720 are ethernet devices only and can not be placed on the Infinet field bus.

Issue If "Use server assigned subnet/node address" is unchecked and manual addressing is used what addressing guidelines should be followed. Environment Vista Server/Workstation Vista Classic Network Cause The node addressing of a network can be performed in different ways. All nodes need an individual Subnet/Node address, in other words, a logical address. The Subnet address can be any number between 1 and 255. Server assigned subnet/node addressing typically uses Subnet 255. To facilitate future router connections it is recommended that you start with Subnet no. 10. Normally the I/O modules or STR 350/351s have the same Subnet address as their TAC Xenta 280/300/401. Resolution The addressing of a TAC Xenta Node should follow some simple rules. Each TAC Xenta device requires three consecutive node addresses; the first for the device itself, the other two are always reserved for the handling of one or two operator panels. Example: Device 1 - Node address 10(and 11 and 12 for any OP) For each TAC Xenta 301/302 device a maximum of two I/O modules or STR 350/351s may be added (for TAC Xenta 401 ten I/O modules/STRs; for TAC Xenta 280 two STRs), each requiring its own address. The address will typically follow the two OP addresses. Example: I/O Module 1 - Node address 13. I/O Module 2 - Node address 14 and so on. The maximum number of Node addresses on one subnet is 127 (125 for the TAC Xenta 280/300/401). If the number of nodes exceeds 125 on a Subnet, or if logical grouping is required for other reasons, a new subnet number is used.

Issue What LonWorks data is accessible from a Xenta Server and what can the data be used for? Environment Xenta 500 Xenta 700 Xenta 900 XBuilder Cause There are different types of data accessible on a LonWorks network. TAC network variables / Public Signals - TAC proprietary communication for signals from Xenta programmable controllers SNVT - network variables available for bindings SCPT/UCPT - Configuration properties for LonWorks devices. UNVT - User defined SNVT. Data accessible from a Xenta Server can be used in Xbuilder in multiple ways: Polling - value polled for use in graphics page, values page, alarm, trending, and scheduling. Connection object - poll and send process to pass value from one device to another (could cross protocols). SNVT binding - binding from a SNVT created on the Xenta Server. Resolution Use the following table to identify which signals types are supported and how they can be used. Data type  Polling Connection Object  Binding  Public Signals  Yes 1  Yes 1  No  SNVT  Yes  Yes  Yes 2  SCPT/UCPT  No  No  No  UNVT  No  No  No 1 Xenta Server must be commissioned to have the TAC group address in its address table. Create group bindings in TAC System Plug-in for LNS networks Commission LonWorks network for Xenta Servers in Classic networks Commission and download Xenta Server acting as LonWorks unit in a LonWorks group in Classic network. 2 SNVTs must be created by Xbuilder on the Xenta Server device. These SVNTs are then bound using a network management tool such as LonMaker or NL-220.

Issue When an Alarm point goes into Alarm, it needs to come up on the forefront. Environment All versions of I/Net using graphics. Cause When creating Alarms and the point goes in Alarm but does not come to the forefront and stays on the graphic page. Resolution For the page to come up front when the point goes into Alarm, the following steps needs to be followed: Select System, Edit Graphic Page. Open the page that the point is on. Select the point and Right Click to display the properties. Select the Automatic Page Display check box. Close the editor and then save the changes. NOTES: In order for the auto pop up feature to function, you will need to have the point masked for messaging. Also set AMT Configuration and Host Masking with the corresponding check boxes.

Issue What is the maximum number of site codes that can be loaded into a Continuum system? Environment AC-1 and AC-1 Plus modules Cause Network design limitations Resolution There is no limit to the number of site codes that can be loaded in a Continuum system.  However, each door can contain a maximum of four (4) site codes.  In the case of an AC-1 module, if it loses communication with its associated Netcontroller, it will only allow access from the first two fields.

Issue How to open a graphic panel using a PE program. Environment Cyberstation Pinpoint Graphic Cause What PE code is used to open a Pinpoint graphic? Resolution Use the Show command. See Cyberstation on-line help. Type Show in search box. See sample PE code in help file.

Issue Webclient fails to send alarm events (using Outlook). This happens every few days. The Windows event viewer on the IIS (Webclient) server has a few errors happening at the same time. Errors include Continuum losing connection to the database and going into 'no database mode'. Then it restores the connection after few minutes. At almost the same time an error occurs related to 'accdataservices.exe'. Also, an error occurs indicating that Outlook has failed to communicate with the exchange server. Environment Webclient v1.74, v1.81, v1.82, v1.90 MS Outlook MS Exchange Cause Continuum will randomly stop sending emails for alarms that are configured to send emails. Manually sending of emails from Outlook still works but CyberStation will not send out the message. There are no Outlook errors posted in the Windows Event Viewer and there are no Cyberstation error messages related to email. Resolution There are hotfixes, for some of the above versions, to fix this issue.  Contact Product Support Services if you need these hotfixes. Note: Versions 1.91 and higher have the updated code. 

Issue Swiping valid card immediately following a valid access at the door resets the door's strike time. Environment CyberStation ACX5740 ACX5720 CX9680 CX9900 ACX781 Cause PE programming needed to override built in behavior Resolution Continuum access controllers unlock a door for DoorStrikeTime seconds on valid access and then wait for the DoorSwitch (door contact) to report the door has been opened. Between the door unlock and the detection of door open, the controller will not process a new card swipe, but will buffer up to ONE card swipe transaction for processing at a later time. The buffered card swipe will be processed either when the door strike time expires or once the door is detected open.  When the controller detects the door open, it resets the door strike time to ONE second and immediately processes a buffered card swipe or a newly detected card swipe. If the card swipe is valid, the controller then overrides the one second strike time with the DoorStrikeTime value. The behavior explained above, allows for scenarios where many card holders file through a door in a quick manner, such as the start/end of a shift. This allows the system to process valid card swipes in a very fast way without requiring that each card holder waits for the door to re-lock after the person in front goes through. In some door configurations such as a turnstile, the above creates undesired issues with the operation of the turnstile and must be overridden so that no valid access can be processed until the system has relocked the door, after allowing a card holder through. This can be accomplished with a PE program that disables credential access at the door when the door switch reports the door open, and re-enables credential access when the door switch reports the door has closed. Sample PE code: If MainEntrance DoorSwitch = Opened then MainEntrance  DisRdrKpAccess = on else DisRdrKpAccess = off In cases where no door switch is assigned the door stays unlocked for DoorStrikeTime seconds and if a valid credential access is processed during this time the door strike will be reset to DoorStrikeTime seconds. In certain scenarios this behavior is undesirable and can be overridden using a PE program so that no valid access is allowed until the door relocks after a previous valid access transaction   SamplePEprogram   Line EnableAccess   Door1 DisRdrKpAccess = False   If Door1 ValidAccess then Goto DisableAccess   Line DisableAccess   Door1 DisRdrKpAccess = True   If TS > Door1 DoorStrikeTime then Goto EnableAccess