Building Automation Knowledge Base

Issue TAC Xenta 300, How many I/O modules   Environment Vista Xenta Cause Trying to connect more then 2 I/O modules to a TAC Xenta 300.   Resolution Please look at TAC Xenta 300 Specification Sheet Always check the The Exchange Download Center for a more current release.

Issue Have a save file from a two station 7793 MCI controller that does not retain any door parameters, time schedules or personnel schedules when viewed through offline.  The parameters are seen and present in the online controller. Environment I/NET Seven 2.xx up to I/NET Seven 2.41A Dual Station Controller 7793 Cause The door parameter upload stops when a personnel schedule 31 is entered on any door on the second station of the 7793.   Resolution If you are using I/NET 2.41 or below: A work around is to delete the Personnel Schedules on any door which is using Schedule #31 on the second station address of the 7793. A patch is available only for I/NET revision 2.31, please contact Product Support for verification of this problem so this patch can be provided.  Reference this article number. Rectification of this issue will be in revision 2.41A and above.

Issue Part of a TGML graphic is missing when viewed. Environment TGML editor 1.1.X - Xenta Server; Webstation; Workstation Cause The resolution of the TGML document is less than the resolution of the object created in the editor. Resolution Set the TGML document resolution to a resolution higher enough to show all objects.

Issue Want to install both Continuum LAN key and webClient Server Key (WEBC-PRO) to enable both Cyberstation and webClient functionality on the same computer. Environment Continuum Cyberstation webClient Server Cause Want to merge two functions of Continuum onto the same machine to save the cost of one computer. Resolution No, you can only install one Continuum Security Key on any PC. In a LAN environment you will need to have the Continuum Cyberstations and webClient Server on separate computers. To have both the functionality of a Cyberstation and a webClient Server on a LAN system will require two PCs.  

Issue Xenta 104-A will control heating outputs but not cooling outputs. Environment Xenta 104-A Cause U1 is setup as a discharge temperature sensor if the outside air is bound into the controller. Resolution If the outside air is bound in as a SNVT connection and Bit 4 on nciAppOptions is set to on. When this occurs, U1 terminal 7 and 8 on the 104 become a Supply temperature sensor. If no 1.8k resistor is installed across these terminal the Supply temperature will read less than 0 causing the controller to think no cooling is needed as the supply temperature is so low. Install a 1.8k temperature across terminal 7 and 8 and this will allow normal control of the Xenta 104-A controller.

Issue Using PE functions designed to take multiple arguments (Minimum, Maximum, Average) with just one argument causes undesired behavior. Environment CyberStation i2 devices b3 devices Cause Functions expecting more than one argument require that more than one argument is passed. Resolution Make sure to always pass at least two arguments to PE functions that are designed to take multiple arguments such as Minimum, Maximum, Average etc For example: OAT = Minimum(MyNetwork\MyCX\Myi2Device) The line above may cause undesired controller behavior Replace the line above with the following line OAT = MyNetwork\MyCX\Myi2Device

Issue Short Form Editor will not work on the local Sigma client. Environment Sigma 4.05 SEB Short Form Editor Shortform SFE Cause Using the Short Form Editor causes the local Sigma client to crash, when accessing it from the Sigma index or graphics. This issue causes a button identified as "SigPntSF" to appear on the bottom of the screen. It is not possible to close down the Sigma Client, and the user must use "ctrl+alt+del" to stop the Sigma Client. Resolution This issue is caused by a corrupted user file. There are two ways to resolve this issue. Restoring backup files. Shutdown the Sigma client and server. Copy the backup "User" folder and "GenCNF.rec" file to the Sigma\Data folder. Restart the Sigma server and client. Test the operation of the short form editor. Reinstalling Sigma. Shutdown the Sigma client and server. Copy the Sigma\Data folder to a secure location. Uninstall Sigma. Delete the Sigma folder. Restart the PC and re-install Sigma Rename the new Sigma\Data folder and call it 4.05 SEB Data copy. Copy your site Data folder back to the Sigma folder. Copy the "User" folder and "GenCNF.rec" file from the 4.05 SEB Data copy folder, to the Sigma\Data folder. Restart the Sigma server and client. Test the operation of the short form editor. Please note that GenCNF.rec holds a lot of the Sigma configuration, and this will have been lost, so will need to be reconfigured.

Issue Customer is adding newer MNB-1000 controllers to an existing network. Will there be any communications issues caused by having different firmware versions? Environment MNB-1000 controllers on BACnet-IP or BACnet-Ethernet See Resolution section for specific firmware versions. Cause Adding new controllers to existing BACnet network. Resolution MNB-1000 controllers using firmware releases 1.502 through 1.511 are fully compatible at the BACnet-IP or BACnet-Ethernet communications level.  (NOTE: Future firmware releases should also be compatible but this document will be updated if necessary.) Firmware revisions to the MNB-1000 controller did not change the BACnet-IP or BACnet-Ethernet protocol as the underlying protocol is defined by the BACnet standards. Since these versions are all in compliance with the relevant BACnet standards, they will intercommunicate properly. Some intermediate firmware revisions may have implemented improvements in the use of the communications protocols to improve communications reliability or to reduce communications overhead. 

Issue I/A Series G3 ASD driver exhibits excessive device initialization and recovery times upon a restart of the station or a power cycle of the ASD devices. Environment I/A Series G3, ASD Cause Driver not synchronizing baud rates to efficiently recover the devices on the bus. Resolution The tacAsd 3.6.47.4 module resolves this issue by improving the mechanism that synchronizes the baud rates between the station and the ASD devices. Download the file tacAsd-3.6.47.4 from The Exchange Download Center.

Issue Clicking on the help button does not bring up any help information. Product Line TAC INET Environment Any version of Windows after Windows XP I/NET Seven Cause There is a file that has to be manually installed for the I/NET Seven Help to work. Resolution Go to Microsoft's website KB917607: Error opening Help in Windows-based programs: "Feature not included" or "Help not supported" Download and install the appropriate file from the list of operating systems in the article's resolution. Restart the PC Start I/NET and click on the Online Help button. It should now bring up the necessary information for that particular section.

Issue Unable to see all Individuals in a Tenant. Environment All versions of Software and I/NET Seven. Cause Wanting a print out of all the Individuals in a System. Resolution To display all the individuals in a system, there is no medium in I/NET itself to do this. However there is a report in Seven Reports that will allow this to be accomplished. The following steps shows how this should be done. Open Up I/Net Seven Data and expand it. Select the Reports Folder and expand it. Select the TenantIndividual_xi.rpt and run that. Enter the parameters and click on the OK button. Print the results accordingly.

Issue More BACnet objects are being added to a UNC-520. Is there a way in Niagara R2 to run a report that lists the BACnet objects’ instance numbers used in an UNC-520? Environment Niagara R2 all versions, UNC-520, UNC-410 Cause NA Resolution Niagara does not offer a report which lists the Instance numbers already assigned in an UNC. About the only way to determine BACnet instance numbers in the UNC is to do a search of the station’s XML file using "instanceNumber" as the search criteria.

Issue I/A Series R2 - Unable to delete users using the browser and Web User Admin screen. Users can be successfully deleted through WorkPlace Pro JDE, but not through the web browser.  This occurs in R2 versions 514 and 522. Environment I/A Series R2, Enterprise Server Cause NA Resolution The issue is resolved in R2 versions 527 and higher.  The excerpt from the R2 527/529 release notes state (Fixed - 10.1:6473 User cannot be deleted from browser when using Sun's Java Plugin). The solution is to upgrade the server to 527 or higher.

Issue How many Echelon PCLTA & NIC709-USB's can use for one single PC Environment TAC Vista 5.x.x Echelon PCLTA NIC709-USB Cause Requirement to know, If we can run more than one PCLTA & NIC709-USB's on a single PC. Resolution There is no limitation on Echelon PCLTA & NIC709-USB's to use in single PC. As long as the PC has a slot for LTA & USB to insert then can be used.

Issue What processor and memory does Xenta 300, 400 and 700 have? Environment Xenta 300, 400 and 700 Cause   Xenta 700, Xenta 913, Xenta 511: CPU: 50 MHz  32 bit ARM Samsung S3C4510B  +  3120 Neuron   Xenta401:   CPU: 12.3 MHz  32 bit   Hitachi H8  + 3120 Neuron   Xenta300: CPU: 10.0 MHz  32 bit   Hitachi H8 + 3120 Neuron   Xenta100: CPU: 10 MHz Cypress  3150   I/O modules: Xenta410 CPU: 10 MHz Cypress 3120   I/O modules: Xenta420A,450A,470,490 CPU: 10 MHz Cypress 3150     Resolution   Xenta 700, Xenta 913, Xenta 511: CPU: 50 MHz  32 bit ARM Samsung S3C4510B  +  3120 Neuron   Xenta401:   CPU: 12.3 MHz  32 bit   Hitachi H8  + 3120 Neuron   Xenta300: CPU: 10.0 MHz  32 bit   Hitachi H8 + 3120 Neuron   Xenta100: CPU: 10 MHz Cypress  3150   I/O modules: Xenta410 CPU: 10 MHz Cypress 3120   I/O modules: Xenta420A,450A,470,490 CPU: 10 MHz Cypress 3150

Issue System error log are reporting Wm_TimeObject errors when trying to create or modify a time schedule in a Xenta server. Wm_TimeObject: Http_Get Error   (Error#:41992) Wm_TimeObject: Http_Post Error   (Error#:41993) Wm_TimeObject: Update File Error   (Error#:41994)   Environment Xenta Server Xenta 511, 527, 711, 731 Time Schedules Cause Attempting to view or create a time schedule object page in the web browser when the time schedule resides in an offline Xenta controller.   Resolution  The Xenta controller must be online to create or modify a time schedule.  

Issue Field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Environment MNB-1000 with firmware 1.50E and earlier only. Cause Field office needs to access the Web Service page so that they can  perform an Ethernet network packet capture for communications troubleshooting purposes. Resolution The Web Service page has been removed from the MNB-1000 Plant Controller firmware effective with release version 1.510.  The user-name is user The password is mnb1000

Issue Request to exit motion sensor seems to be causing nuisance alarms. Environment CyberStation, ACX family, AC1 family, REX motion sensor  Cause Even though the exit request variable is "On" in the door object, if the door opens and closes more than once, a forced entry alarm is created. This causes issues when the REX motion never turns off and multiple users exit the door. Resolution In Continuum controller firmware once the door is closed and locked a change of state of the REX input is required to keep the alarm shunted. To simulate this, trigger the REX motion detector and then open the door while it is unlocked. The door relocks 1 second after opening. If the door REX signal goes OFF and then ON again, the door unlocks. If, while the door is unlocked, the REX signal goes OFF and ON and OFF and ON the door can be opened and closed with no forced entry OR it can remain open and no door ajar will occur. The same is true if you do not check 'unlock on exit request' - it's just harder to test because you cannot watch the REX signal as easy as the unlock output. The key to avoiding the nuisance forced entry alarms is to let the REX motion sensor cycle quickly - have it turn on and then off after 1/2 to 1 second. The forced entry alarm will be shunted until the door relocks. Then if there is still motion at the sensor the REX will come on again and the controller will continue to shunt the alarm.

Issue Need to be able to change any schedule inside a bCX1-CR from another BacNet/IP workstation like Citec SCADA. Environment BACnet bCX1-CR Citec SCADA Cause It is a project requirement to change schedules in a bCX-CR1 from a third party BACnet workstation. Is this possible? Resolution The answer to your question is not a simple yes/no. Please see page 8 of Product Implementation Conformance Statement bCX1-CR It describes the "writable" properties of the schedule objects in the bCX1-CR v4.5. Make sure that the BACnet workstation (B-OWS) that you wish to use to edit schedules in the bCX1-CR v4.5 supports (in its PICS) the properties that your customer needs to be able to edit. For example, from the linked PICS, it appears the Next_Transition_Time is not writable in the bCX1-CR v4.5. If this is a property that your customer requires the Citec SCADA to edit in the bCX1-CR v4.5 then there may be a problem. Since we do not provide support for Citec SCADA we cannot say whether or not it will work. You will need to talk to Citec or make a judgment based on their PICS.  

Issue The STR-200 and STR-202 are the recommended replacement for TSS100WJ and S/STAT. Environment STR-200 STR-202 Xenta 102-AX 7728 MR-VAV TSS100WJ S/STAT Cause Obsolete parts Resolution STR200 replaces the TTS100WJ (Temperature Sensor Only, PN) STR202 replaces the S/STAT (Bypass button and Offset wheel) STR200-202 can be used with the 7728, MRs, and Xenta 102-AX controllers. STR200 . . . . . . . . . . . . . . . . . . . . . . . . 004603000 STR200-W (White) . . . . . . . . . . . . . . . . 004603010 STR202 . . . . . . . . . . . . . . . . . . . . . . . . 004603200 Full Datasheet containing additional information is located here.