Building Automation Knowledge Base

Issue I need to know hardware specifications for the BACnet controllers and cannot find it in any documents.  Environment The specifications given below are accurate as of 6/30/2011 but are subject to change without notice. Cause Not applicable Resolution The memory specifications below are also available in the MicroNet BACnet Wiring, Networking, and Best Practices Guide.  If a formal document for the CPU and I/O specifications is required contact your Regional Salesman or Product Marketing. MNB-V1 and MNB-V2 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution  MNB-70 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution MNB-300 Processor: Atmel ATMEGA256-16AJ (8-bit) operating at 16 MHZ Memory: Flash 256KB, SRAM 8KB, EEPROM 4KB, FRAM 8KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution  MNB-1000 Main Control Processor: Freescale Coldfire MCF5485 (32-bit) operating at 200 MHZ Memory: Flash 16MB, SDRAM 64MB, EEPROM 1KB, Boot Flash 2MB Motherboard (Local I/O Processor) Processor: Atmel ATMEGA128 series 8-bit microcontroller running at 16 MHZ Memory: Processor Flash 128KB, SRAM 4KB, EEPROM 4KB.  Motherboard SRAM 256KB, EEPROM 128KB A/D and D/A resolution: UI inputs have a 12 bit resolution and UO outputs have an 8 bit resolution

Issue Communicating to I/NET on a direct connect requires a cable that has to be connected from the PC to the controller. Product Line TAC INET Environment All versions of I/NET using Direct Connect to controllers. Cause Connecting to a controller from a PC if there are no Net Plus Routers for connectivity over the Ethernet. If a 7798C controller is being used then another programming cable needs to be used for the virtual HHC on that PC. Resolution To resolve this a cable part number CBL-072 connected to the PC and controller. To obtain the various part numbers for the cables, connecting to the iPortal and searching on %CBL% should bring up the required information. Maximum supported cable length is 25 feet (7.62 meters). ***See the comment below on the CBL-072*** Part number for the direct connect is CBL-072 The pin-out for this cable is shown below: Part number for the 7798C is CBL-082 The pin-out for this cable is shown below: Note: CBL072 is for direct connect between the computer and controller. CBL-082 is for programming with Virtual HHC. **********************************************************************  ***The CBL-072 looks to be no longer available From Schneider Electric (9/2017) *** You have two choices on the CBL-072: 1)            Build a new CBL-072 using the Pin-out above. 2)            Convert a CBL-082 into a CBL-072 (see steps below) To convert a CBL-082 into a CBL-072, cut the “Gray” wire connected to pin 5 on the D-Sub 9 connector at the PC end. Then remark the cable label to avoid future confusion on its use. ***********************************************************************

Issue Floor Plans and Camera Views that show up in the Security Expert thick client do not work in the Web Client. Instead of floor and camera images, “Floor plan not supported” and “Camera view not supported” are displayed. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause Floor Plans and Camera Views are not displayed through the Web Client interface and will only work with the Security Expert Client. The Security Expert Web Client is not intended to support the full suite of options available through the thick client. Resolution Use the Security Expert Client as this will support Floor Plans and Camera Views.

Issue Reference of I/NET Guide Product Line TAC INET Environment I/NET Seven Cause Combination of various TCON documents showing most common used functions for easy reference.  Note that this document is not maintained.  Please refer to documentation available on Exchange Resolution Download the INET Pocket Reference Guide PDF

Issue Tooltip feature for TGML Graphics was hotfixed in Vista 5.0.3 (Hotfix 20) and was disabled later versions of TAC Vista based on customers requirement. Refer to TPA-MALI-08-0007.01 for more details Product Line TAC Vista Environment TAC Vista 5.0.3 and later versions. Cause By default, the tooltip feature in TGML Graphics was removed. Resolution To enable the Tooltip option in TGML graphics following these steps: The Tooltip snippet is available under Snippets > Basic Functions > Tooltip. If the editor does not have this snippet, download the attached Tooltip.zip snippet. Close all the TGML windows and Install the tooltip snippet Open the TGML editor and you can find the tooltip snippet under My Snippets Drag and drop the tooltip snippet on to the graphic objects window to see the tooltip feature. After drag and drop the tooltip snippet on to the graphic, the Metadata – TooltipContainer will be added to the object properties. Tooltip will now be available for this graphics Object. Repeat steps 4 and 5 for each other graphics Object.

Issue Using a repeater to extend ACC LON bus. Environment CX9900 CX9940 CX9680 IOU Modules Cause Infilink repeater is designed for the Infinet field bus. Resolution The Infilink repeaters CAN NOT be used to extend ACC LON.

Issue How to change the firmware version in a controller. Product Line Andover Continuum Environment All flash-upgradeable controllers: CX9900, CX9940, ACX5720, ACX5740, all i2, b3, and bCX controllers.  Cause Controller firmware needs to be changed. Resolution Locate the firmware version that you need for each controller you want to change. The Continuum firmware files can be downloaded from the Schneider Electric Ecobuilding Exchange. The downloaded files are often a zip file which includes the release notes in PDF format and the flash file (UPD file). Note: You may need to upgrade or downgrade firmware (see also Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum?) Make sure you check the document Andover Continuum Software and Firmware Compatibility Matrix for the appropriate firmware version for your system.   Copy the file to a disk drive accessible to your CyberStation workstation. Edit the controller object in ContinuumExplorer and click on the "Update OS" button. Browse to the file location in step 2 and click "Open". A progress box "Updating Controller OS..." will appear. During this time the controller is reset and not functional.  Once complete, and if successful, you will get  a dialog box indicating that the upload was successful and the controller will return On-Line momentarily. Click OK. Click the refresh button in the controller editor. Once the controller is on-line the version field should indicate the new version. At this point some controllers may need a reload, others will be reloaded from flash memory. This depends on the controller type. For example, the CX9900 has no flash memory and therefore will need to be reloaded. This procedure also applies to upgrading controller options such as adding Xdriver support. In this case a UPD file will be provided by the Repair Dept. In the case of added Xdriver support, after doing the Update OS procedure the version will not change. Look at the controller Options tab after it comes back online following the upgrade. The information here, such as a non-zero entry in the numbers next to the appropriate Xdriver Commport will be changed. The above procedure was based on an IP level controller such as the CX, bCX and ACX II. Infinet and MSTP controllers are done in a similar manner. IOU models are also upgraded similarly via the "Update IOU" button in the IOUModule editor. However, the files are .IOU files instead of .UPD files and the versions are in the fourth pair of characters in the Program ID field.  

Issue When using an Echelon U10/U20 USB or other Lon network adaptor for communication with a laptop and standalone WorkPlace Tech, not WorkPlace Tech Editor, you must change the default configuration settings.  The default Lon Network Domain ID length (1 byte), Domain ID (18 decimal) and Subnet (254) in the AS-P conflicts with the defaults used by WorkPlace Tech. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech (Lon Network communication settings) Building Operation Automation Server Premium Building Operation Enterprise Server Cause Lon Network configuration Resolution Look at the LonWorks Network "Advanced" tab in the AS-P to determine the addressing information. Open the WorkPlace Tech WorkStation Communication Settings and select LonWorks.  Open the Change Address window Select the "Manual Setup" radio Button Modify to match the AS-P Lon Works Network configuration.  If a different Domain ID or subnet has been assigned in the AS-P, it will need to be assigned the same in WorkPlace Tech You can now browse the LonNetwork from the laptop.  If the MNL devices are assigned applications from the AS-P, do not modify the programs from the WorkPlace Tech Tool  

Issue Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Controllers: ENC-410-1 ENC-410-1-N ENC-520-2 ENC-520-2-N Cause There maybe a need to access the ENC via its serial port if the IP address of the ENC is unknown or for troubleshooting purposes when the ENC's Ethernet port is not functioning. Resolution Hardware required for connection to ENC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors. RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430). A functioning COM port on your computer. A 2-pin jumper for connection to the ENC's 'Mode' connector. Refer to the Installations Instructions for ENC-410 (pages 10 & 11) or ENC-520 (pages 10 & 11) for details on the cable and adapter.  Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC also refers to these pin outs. Connection to ENC's serial system shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the ENC’s RS-232 port and the RS-232 COM port you are using on your computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to ENC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port you are using on your computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 57600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Click OK. On the ENC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 7 of the ENC-410 or ENC-520 Installation Instructions for position of the Mode connector. With your HyperTerminal session active and configured to log to a file, remove power from the ENC, let it cycle down, then reapply power.  The easiest way to power cycle the ENC is to unplug the 6-pin power plug from the circuit board, wait 15 seconds and plug it back in.  After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... Do not press any key, wait for the login prompt. If you did press a key to stop auto-boot, select option 1. At the login prompt, enter the platform user name, and at the password prompt, the platform password. The default user name is 'tac' and password is 'niagara'. The system shell menu should now appear. You should able to see the IP address of the ENC now. When finished using the serial system shell, do the following: Remove the 2-pin jumper from the Mode connector of the ENC. From the system shell menu, select the Reboot option. Type 'y' at the 'Are you sure you want to reboot [y/n]' prompt, and press Enter. Shutdown-related text appears in the HyperTerminal window, and then the connection is dropped. Press the Disconnect button on the HyperTerminal tool bar. Exit from the HyperTerminal application, selecting to Save if you wish to reuse this HyperTerminal setup for future connection to an ENC. If you are troubleshooting the ENC, send the HyperTerminal start up messages to Product Support for analysis.

Issue Continuum analyzer reports errors in the IE Table Check. Environment Cyberstation Cause Errors need to be cleaned up using the Continuum analyzer. Resolution Clean up the errors using the Continuum analyzer then run the tests again to verify errors where corrected. If everything appears to work correctly then there is no need to reload the IE table to the controllers, otherwise: Send the IE table to CX level controllers. To send only the IE table select the 'Do not reload attached objects' in the 'Send To Controller Options' dialog window.

Issue The MNL-800 controller will not communicate with the WorkPlace Tech tool nor will it communicate with LON network management software tools such as LonMaker or the I/A Series (Niagara) R2/G3 LON Device Manager software. Symptom - Controller LEDs (top to bottom) Green Power and Transmit Data (Green) – on solid (normal power condition) Receive Data (Yellow) – may be flashing if data present on the bus Service (Red) – flashing a repeated abnormal pattern (long flash / short flash) Heartbeat (Green) – alternates on and off at a half second rate (normal) Environment MNL-800 on existing or new LON network WorkPlace Tech Tool software or LON Network Management software Cause An analysis of field returns has identified a condition where the MNL-800 fails to communicate and appears to be resetting continuously. The controller has entered a condition where the Neuron’s image has been deemed corrupted due to an application checksum error or signature inconsistency. When this occurs, the Neuron is unable to complete the startup sequence resulting in the MNL-800 continuously resetting. Resolution Follow the procedure documented in TPA-RKFD-09-0005.00 to reconfigure the communications processor in the MNL-800 controller. In the unlikely event that this procedure does not correct the communications issue, please contact Product Support Services for additional assistance.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. The SSN is invalid for this installation. Product Line EcoStruxure Security Expert Environment Security Expert Cause Wrong SSN being used. The SSN being used is different to what was used when Security Expert was initially installed. Resolution Uninstall Security Expert and re-install using the correct SSN. Backup the SecurityExpert and SecurityExpertEvents databases and copy the resulting backup files somewhere safe. Manual backups can be initiated from the Global > Global Settings menu. Select the directory location and press backup now. Uninstall Security Expert from Windows Add or Remove Programs. Search for "Security Expert" to filter the results. Install Security Expert from available installation files. When asked for the license make sure to use the correct SSN.

Issue BACnet MSTP Capture Application Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP capture application provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution Download the latest version. Browse to Steve Karg's  BACnet Protocol Stack - Browse /bacnet-tools at SourceForge.net Select the version folder Select bacnet-tools-[n.n.n].zip file to download it From the zip file, extract mstpcap.exe Now you can use it via command prompt as described below or install it in C:\Program Files\Wireshark\extcap if want to use with modern Wireshark version.   To capture data follow these steps: Unzip file Open command prompt with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Bluetooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further information or instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue A Cisco Mediator controller is connected via BACnet/IP to a Niagara R2 UNC.  The UNC station provides data to and receives commands from the controller.  The Cisco Mediator controller can read BACnet values but when it attempts to overwrite setpoints and issue commands, they do not work. Environment Niagara R2 all versions Cause The installation contains 3rd party BACnet controllers that must share data and commands. Resolution To allow other BACnet controllers to write values or issue commands to exposed Niagara objects, a special "BACnet" user is required for the station. To create this special user, follow the steps listed on pages 4-6 & 4-7 of Tridium's BACnet Integration Guide.

Issue Xenta Repeater offers signal restoration and conditioning on LON networks Lon communication issues Completion-event failures Environment Vista Lon Networks Xenta Repeaters (Part # 007309120) Cause Lon Networks can suffer communications problems due to the physical length of the network and / or due to the number of devices on the network. A Xenta Repeater can help to resolve these problems and allow for a longer physical communications network and a larger number of devices to be used. Resolution A Xenta Repeater is a device that uses a standard Xenta 400 base and is installed in the middle of the Lon network channel and separates it into two segments. (Note: Lon channels are sections of a Lon network that are separated by a router while segments are sections of a channel that have divided using a repeater.) One segment of the Lon channel is connected to either of the pairs of COM 1 terminals and the other segment is connected to either of the pairs of COM 2 terminals. Each Lon segment must stay within the recommended length limits as seen below:   Cable Max. bus length, doubly terminated bus topology (m)/(ft) Max. node-to-node length, singly term. free topology (m)/(ft) Max. length, singly terminated free topology (m)/(ft) Belden 85102, single twisted pair  2,700 8,858 500 1,640 500 1,640 Belden 8471, single twisted pair  2,700 8,858 400 1,312 500 1,640 UL Level IV 22AWG, twisted pair  1,400 4,593 400 1,312 500 1,640 Siemens J-Y(st)Y 2x2x0.8  4-wire helical twist, solid, shielded 900 2,953 320 1,050 500 1,640 TIA568A Cat.5 24AWG, twisted pair  900 2,953 250 820 450 1,476   The following rules must be adhered to: A maximum of 128 devices can be placed on a Lon channel A maximum of 64 devices can be placed on a Lon segment A channel may use up to 2 repeaters creating a maximum of 3 segments If a router is not being used on a channel then there may only be 64 devices on that channel since the channel is made up of only one segment. It is recommended to limit the number of devices per segment to 50 when engineering a Lon network. This will allow for some devices to be added or re-distributed as needed during installation. The Xenta Repeater consists of two internally connected Lon transceivers, each with a transient suppression circuit. Data packets are picked up by the transceiver on one segment and re-broadcast onto the next segment using the second transceiver. Only Lon packets are read and re-broadcast rather than simply amplifying the signal along with all of the noise on the network. This provides for a strong, clean and noise-free signal on either side of the Xenta Repeater.

Issue The following error can occur when logging into Security Expert using a Remote Client:   Could not log on to Server. Please check your remote connection setup. The server has rejected the client credentials. Product Line EcoStruxure Security Expert Environment Security Expert Server / Client Cause The security policy settings are different between the Server and Client.   When installing the Security Expert Server and Clients, the default security policy is used. This requires that the Windows username and password that the operator has used to log in on a client machine is also a valid user on the computer that is running the Security Expert Server. These security requirements are very favourable for corporate networks and setups where the users and policies are easy to manipulate. For that purpose alone, the Security Expert Server and Client are installed with these settings by default.   All installations are not created equal however and sometimes the Security Expert Server is not located within a domain. In another scenario, the server may be in a domain but the operators need to connect to it from a machine that is not in the domain. In these cases, it has been requested that the security policy in place on a domain or the physical machine is disabled and although this is not recommended practice the security of the system can be maintained using a suitable VPN structure.   This solution should be used with full knowledge that the security of the system will rely on the operator user login name and password as well as the security measures put in place for a client to be able to hit the server with a login request. Protection of the infrastructure to the connection is beyond the scope of this document. Resolution The easiest solution would be to put the Client machine(s) in the same Domain as the Server.  However if this is not possible or if no Domain is used then you can still manually update the security policy instead. The following process is a manual edit of the XML configuration files  SecurityExpert.exe.config  SecurityExpertSV.exe.config  Both of these files are located in the .\Program Files\Schneider Electric\Security Expert directory on the Client and Server. It is recommended then to backup these two files prior to performing this task. Close all Security Expert clients and stop the Security Expert Data Service. We are first going to update the Security Expert Client configuration file SecurityExpert.exe.config on the client machine.  If using more than one Client, the change must be done for ALL clients Open Notepad as the administrator, browse to the specified location making sure the 'all files option' is selected.  Then open SecurityExpert.exe.config (Be aware that it may not have the file extension showing and will be called an XML Configuration file by default) Locate the netTcpBinding tag . Nested within this tag is the binding tag Ensure that you insert the below text after the opening binding tag and before the closing \binding tag . If you insert the text outside this tag, the application will fail to run.   "<security mode ="None"></security>" IMPORTANT You must ensure you enter "None" with a capital "N" (not lower case). Ensure you copy input text exactly as shown. Now save the file. If you get a write error then you need to open notepad as the administrator. Repeat the process for the Security Expert Server configuration file SecurityExpertSV.exe.config which is located in the same directory on the server machine.      Again, make sure the line is inserted after the opening tag and before the closing tag or the application will fail to run when you save the changes. Restart the Security Expert Data Service and test the connection settings.

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.

Issue After upgrading the Continuum workstation software, cannot edit workstation programs Environment Continuum Cyberstation Workstation programs Plain English Cause Not able to edit workstation programs. Firing order is edit locked. Resolution To resolve open up the Continuum Commandline program and type in "Firingorder editlock=false" This will unlock the firing order and programs will be able to be edited. In the simple case of editlock where a program may have been editlocked which is different than firing order editlocked. Simply select the program in question and press Ctrl+U or access the properties of the program by right click and select the CurrentStatus tab and press the "Force Object to unlock" button.

Issue Can not see bCX4040 in BACnet view following Find New BACnet Devices from the root. CyberStation and controller are located on the same subnet, no BBMD configuration is required. Environment CyberStation bCX4040 b4920 Cause Subnet mask mismatch between PC and bCX Subnet mask not property configured in controller or the PC Resolution Login to controller's configuration web page and set the subnet mask to the appropriate value for the network. Submit the changes and re-start the controller. If the mismatch is on the PC side, fix it in the network properties in windows control panel.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files