Building Automation Knowledge Base

Issue When accessing an I/A Series R2 or I/A Series G3 station web page, a popup window is displayed warning of a possible security vulnerability. The popup warning is displayed differently depending on the browser version and Java version installed on the computer used for viewing the graphics. -------------------------------------------------------------------------- With Java 7 update 11 or newer, and Internet Explorer 8 or 9, the following popup windows is displayed (location string will vary):   Note that even if you check the "Do not show" checkbox, you will receive additional prompts because the prompt is displayed for each Java applet encountered in the current browsing session.  Likewise, if you close the browser and reopen it, navigating to the same site, the prompts will again be displayed. If accessing I/A Series G3 graphics, the following screen may be displayed: A variant of this message is as follows: --------------------------------------------------------------------------- If using a recent version of the Firefox web browser, the following message is shown in the graphic applet window: "This plugin has security vulnerabilities.  Click here to activate the Java(TM) Platform SE 7 U Plugin."   --------------------------------------------------------------------- When using the Mozilla Firefox browser to access I/A Series G3 graphics, the following security warning may be displayed (Click "I Understand the Risks" and follow prompts to continue):   Environment Windows computer Internet 9 or Firefox web browser Cause Known security vulnerabilities with the Java JRE software Resolution Since the issue is being reported by the Java software or the Java plugin in the browser, there is nothing we can do to directly resolve the issue. There are several workarounds possible, depending on how the site deals with browser security issues. The most secure approach is to allow the applet to be run each time you are prompted. If using Internet Explorer, click the [Run] button on the security warning popup window. If using Firefox, two actions may be needed.  First if the warning "This connection is untrusted" is displayed, click the "I Understand the Risks" Unfortunately, this is a Java issue, not an I/A Series R2 software issue. Oracle has added this popup to its browser plugin to warn the user that a downloaded Java applet may be unsafe to execute. According to information published by Oracle, it may take them up to two years to correct all the known security issues in the Java-JRE. Many of the known issues date back to before Oracle assumed ownership of Java. The only workaround at this time is to downgrade the Java-JRE to a version that does not notify its user that the Java applet to be executed may pose a security risk. We did some testing on Windows 7 with IE9 and found that Java 1.7.0.9 (Java 7 update 9) does not cause the prompt to be displayed. In addition, we found that in some cases we were able to greatly reduce the number of times the prompt appears in Java 1.7.0.17 by setting its security setting to Low (Java control panel applet, Security tab). On one of the virtual machines that we tested this on, the prompt would be displayed the first time you accessed the site and would not be displayed again until you closed the browser and reopened it. On a second computer, the prompt would be displayed each time you accessed a new site or re-opened the connection to the same site but not on multiple screen accesses from the same site. We are not sure at this time why some systems exhibit this different behavior. Note that when using Firefox 19.0.2 and Java 7 update 9 or earlier, a different message is displayed when the web page attempts to open a java window. This window is not displayed when using any version of Java that includes its own security warning popup. The security warning popup I am referring to is the same one displayed when using Java 7 update 17 and other recent versions on Internet Explorer 9 or Firefox 19. This message is designed to notify the user that there is a known security vulnerability with the addon being used, in this case, the out-of-date Java plug-in. There is a workaround published on the mozilla support site that documents a procedure for disabling these warnings when using the earlier versions of Java 7. This workaround does not solve the Java popup warning issue for the Firefox 19.0.2 / Java 1.7 update 17 combination. I did not test it with other combinations other than Firefox 19.0.2 / Java 7 update 9. Here is the configuration change for Firefox 19: Open Firefox Open a New tab Browse to about:config i.e., enter the string in the browser address bar Accept the security warning In the displayed list, right click on extensions.blocklist.enabled In the selection window, click Toggle to change the entry to false Close and reopen the browser. This will disable the security warning for all browser plugin applets, including Java 7 update 11 and earlier, Java 6 Updates 31-38, Adobe Flash Player 10.2.*, 10.3 or 11.0-11.4, Microsoft Silverlight 4.1 and earlier or 5.0/5.1, and about two dozen other plugins that have known security issues. At this time we have not found any workarounds for disabling the Java security warning popup that occurs with Java 7 update 12 and newer with either Internet Explorer or Firefox. As additional information regarding this issue becomes available regarding Java and Internet browser updates, this article will be updated as required.  Depending on site security restrictions, it may be necessary to disable Java when not using it for accessing I/A Series R2 or G3 systems.  See the following instructions from the Java web site: To disable Java - http://java.com/en/download/help/disable_browser.xml To enable Java  - http://java.com/en/download/help/enable_browser.xml In some cases, you may be able to bypass the warning but all your graphics pages do not  load.  This issue is sometimes caused by a security issue with some of the cached java temporary files.  There is a workaround, as follows: In the Windows Control Panel, open the Java applet. Under the "General" tab, "Temporary Internet Files"  section, click [Settings] Uncheck the box "Keep temporary files on my computer" Click [Ok] to save the change then click [OK] to exit the Java control panel.

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

Issue Satchwell AR Series 7 Rotary Actuator requires replacement Product Line Field Devices Environment Satchwell AR Series 7 Rotary Actuators installed on Air Dampers, Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Actuator types :- ARE ARM ARX Cause Obsolescence of Satchwell AR Series 7 Rotary Actuators Resolution Replace Satchwell AR Series 7 Rotary Actuators with appropriate Schneider Electric MD Series Rotary Actuators and Linkage Kits selected from the following :- Satchwell AR Series 7 Rotary Actuators installed on Air Dampers. ARE Series 7 = MD20A-24 ARM Series 7 = MD20B-230 ARX Series 7 = MD20B-24 N.B. Schneider Electric MD20 Series Actuators are supplied with a Direct Damper Mounting Kit enabling the Actuator to be installed direct on to an Air Damper Spindle. Should the Actuator be required to operate an Air Damper remotely by means of a Damper Crank Arm and associated Connecting Rod and Universal Connectors, then this may be achieved through the installation of the following Linkage Kit :- ZG-MD20 Damper Linkage Kit (914-1063-000) Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies. ARE Series 7 = MD10A-24 + Linkage Kit 914-1071-000 ARM Series 7 = MD10B-230 + Linkage Kit 914-1071-000 ARX Series 7 = MD10B-24 + Linkage Kit 914-1071-000 N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE Series 7 = MD20A-24 + Linkage Kit 914-1070-000 ARM Series 7 = MD20B-230 + Linkage Kit 914-1070-000 ARX Series 7 = MD20B-24 + Linkage Kit 914-1070-000 N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the Schneider Electric MD Series Actuator as appropriate :- MD – S1 One independent Mains Voltage rated changeover contact Auxiliary Switch MD – S2 Two independent Mains Voltage rated changeover contact Auxiliary Switches   Product information. For details of MD10A please see here For details of MD10B please see here For details of MD20A please see here For details of MD20B please see here For details of MD-S1 please see here For details of MD-S2 please see here For details of Linkage Kit ZG-MD20 please see here For details of Linkage Kit 914-1070-000 please see here For details of Linkage Kit 914-1071-000 please see here

Issue When installing PCT 2 the following error is seen: Error: System.Management.Automation.CommandNotFoundException: The term 'Get-VM' is not recognized as a name of a cmdlet, function,script file, or executable program. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause The Hyper-V Module for Windows PowerShell is not installed. Resolution Follow these steps in Windows 10 to install the Hyper-V Module for Windows PowerShell: Right-click on the Start button and click Programs and Features. In the Programs and Features dialog, click Turn Windows features on or off In the Windows Features dialog, check the box for Hyper-V Module for Windows PowerShell and click OK. The dialog will signal completion and the module will be installed.

Issue Need information on how exactly SmartStruxure checks whether BACnet devices are still online or have gone offline. Product Line EcoStruxure Building Operation Environment Enterprise Server - ES Automation Server - AS BACnet devices Cause Understanding how communication status is verified can help with troubleshooting comm loss issues. Resolution After a device is discovered via the WHO-IS/I-AM service and moved into the SmartStruxure database, SmartStruxure uses the following scheme to check on the communication status of the device. For IP Device The server will send a Read Property message to read the devices's system status*** every minute, as long as a reply is received the device is deemed to be ONLINE. If no reply is received by the APDU Timeout the server will retry up to 3 times, if there is no response the device will be considered to be OFFLINE. For MSTP Device The server listens as the token is being passed around the bus and if a device fails to get the token it will be tagged OFFLINE. For both IP and MSTP Device Once the device is tagged OFFLINE, the server will check on the device once a minute by sending a WHO-IS message with the ID of the device, if an I am is received the device will be considered back ONLINE and the ReadProperty 'probe' check (for IP) or token pass check (for MSTP) will resume once a minute. ***In version 1.4 and below the ReadProperty will read the name property of the device. See sample Wireshark capture below, NOTE that in the sample below 10.169.90.31 is the Broadcast address of the sub net where the ES is located. NOTE: For efficiency the BACnet engine may combine the reading of the system status property with other read property requests into a single Read Property Multiple.

Issue Error messages in Workstation saying "No valid license to add AS found", when trying to add one more AS-P to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Demo License file Cause The error message is caused by an expired demo license. When using the Demo License file, the ES checks the Licence at startup, and when doing some operations, like adding AS-Ps. If the Demo license expires, the ES may still work, but you cannot add any more AS-Ps. License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution Download a new demo license file from EcoXpert Extranet – The Exchange, and upload it to License Administrator. After the new Demo license file has been added to the License server, you may also need to restart the ES to make sure the new license file will be in use. For more information about the Demo license, please refer to the article EcoStruxure Building Operation Evaluation License for 2.0 and up. When using EBO 2022 v4.0.x and later, the error message (No Valid License to add AS found) can also be displayed if the attached AS-x embedded demo license has expired. Add a current embedded demo license to the device administrator and then re-activate the license to all AS-x servers that require it. Please refer to the article How to activate a demo license on an Automation Server at EBO 2022  Go to Control Panel> System and copy the Device Name Update @localhost in License Administrator > License Server Address to the @"Device Name" Reboot the System(PC) Example The Device Name is "computer1".     Update the License server address to "@computer1" since the Device Name is "computer1"  

Issue Factors to consider using oBIX vs. BACnet IP to exchange data between Niagara R2 and G3 systems Product Line TAC IA Series Environment Niagara R2 version 522 and later Niagara G3 version 3.4 and later Cause Planning factors to consider as to which method is better suited for the customer Resolution Either solution has pros and cons regarding implementation. One needs to think about what fits and how much engineering is required.  If the R2 UNCs (Jaces) are nearly full (CPU and/or memory or less than 40% idle time), then oBIX probably can't be used. It requires some resources to drop in the oBIX service. But if their CPU usage is good (> 40% idle time) and the resource count isn't near the limit, the oBIX service should fit into the UNC. With oBIX, one has access to much more information in the R2 station than with BACnet. BACnet just gives access to its standard objects (BV, BO, AV, AO, etc). oBIX would provide access to just about anything in the station, though some things might be in a string format. One could get trend logs and such using oBIX.  Please also note that R2 oBIX is server only - no R2 "shadow objects" exist to obtain remote oBIX data (e.g. from a G3 station). For additional details, refer to the following documents: Niagara AX-3.x oBIX Guide Niagara R2 to Niagara AX via oBIX Engineering Notes   With BACnet IP, one would need to set all the R2 points 'Foreign Address' field for any point to be available to the G3 station.  Then, configure the G3 BACnet network, and discover the R2 devices and points (Note that if the G3 station is a supervisor, or Enterprise Server, a BACnet license feature with the appropriate number of BACnet points must be purchased).   A G3 supervisor PC should handle 5000 oBIX or BACnet points, provided the station is properly licensed.  

Issue When using Advanced Display and logging in to Webstation, it startups in kiosk mode with limited functionality. Example:   Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display Cause When running Webstation in Advanced Display it is by default started in kiosk mode Resolution Open SmartX HMI Kiosk in Advanced Display In "Webstation setup" delete the part ?kiosk# Example: https://192.168.42.116/?kiosk#  Webstation be started in kiosk mode https://192.168.42.116/  Webstation will start normally

Issue The first time a TGML graphic is opened after logging in through Workstation it takes a long time (approximately 30 seconds) before the graphic is shown Product Line TAC Vista Environment Windows Domain TAC Vista .NET Framework Cause This is usually only an issue when the PC has either no or a bad internet connection or is located behind a proxy server. The reason this is happening, is because an application using e.g. signed .NET Framework dll files will check for certificate revocation each time it's launched. That can only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang until a given timeout is reached. The default timeout is 35 (15+20) seconds. For a deep explanation of certificate revocation check and the base of this article, read this article. Resolution There are two solutions that can be implemented. The first is mandatory and the second is optional. The first solution solves the slow TGML opening issue, while the second seems to have a positive overall performance impact but doesn't solve the slow TGML opening issue. A third solution is to get internet connection for the PC, but that is usually not an option. Solution 1 : Lowering the timeout 1. Open the "Local Group Policy Editor" by typing "gpedit.msc" (no quotes) in "Start"->"Search programs and files..." 2. Navigate to "Local Computer Policy"->"Computer Configuration"->"Windows Settings"->Security Settings"->"Public Key Policies" 3. Open the object to the right called "Certificate Path Validation Settings" 4. In the tab "Network Retrieval" check "Define these policy settings" and write 1 in both retrieval timeout settings 5. Click "Apply" and "OK" and close "Local Group Policy Editor"   Solution 2 : Manually installing the newest certificate lists 1. Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl 2. Copy the two files to the PC having the issue 3. Open a command prompt and navigate to the folder where the files are located 4. Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

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 Failed to read events from the event log database. Product Line TAC Vista Environment TAC Vista Workstation Cause This error is sometimes displayed upon login to the TAC Vista Workstation. It indicates there is a problem with the connection between the Vista Server and the SQL database that stores event data. Resolution Before making any further tests, make sure you have MSXML 4.0 SP3 installed and then check if it works. It can be downloaded here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=15697 The first thing to check is the SQL connection. Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Make sure SQL Server Agent is running. Right-click on My Computer and select Manage Navigate to Computer Management (Local) > Services and Applications > Services Find SQL Server (TACVISTA) -- assuming the default SQL instance is being used. Make sure the service status is running.  Start the service if needed. If there is no problem with the SQL connection, check the Server object's Network Master. In Vista Workstation, right-click on the Vista Server object and select Properties On the General tab, in the Network pane, check the Master: name In a one-server network, the Network Master must be set to the Server object name. Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. Are they empty or are they consistently growing with files? This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. In the case of the error "Failed to read events from the event log database", it is possible that a queued file is causing the error prompt and that deleting it will fix it. If the data is not of dire importance, delete all the files inside both of the $queues folder. For more information see An efficient method for deleting all queued files in the $queues folder. Reconfigure the log database Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab Change SQL configuration from Typical to Custom Change the Log database name Hit Apply. It will warn you: "TAC Vista integrated SQL backup/restore function will not be available in custom configuration." Hit OK. It will then warn you: "No log database was found on SQL Server. Create and configure a log database?" Hit Yes.   At this point, if no backup features are necessary, and the error has cleared, this is a viable solution. It is not, however, recommended to maintain a site without any log backups. The next step would be to switch the Vista Server Setup SQL configuration back to Typical. Hit Apply. You will be warned: "Log database was found but needs to be reconfigured. Reconfigure log database?" Hit Yes.   After reverting to typical SQL settings, the error should clear. If it has not, it may be time for some database management. Performing Database Maintenance Follow the steps in the article Performing database maintenance with Vista 4.5.0  to set up a log and event backup and to clean up old data. Schedule a backup to occur (now or soon after) The next time you log into Vista Workstation, the error should be cleared. If the error is sporadic, it could be the event viewer has too many events If the error only occurs when logging in to Vista Workstation, and doesn't happen every time, it could be that too many events are being brought into the Event Viewer on login. All events specified in the filter for the event viewer are uploaded to the Workstation. If too many events are specified, problems occur. In Workstation, go to the root TAC Vista folder Right-click $Eventview and select properties Go to the Date and Time tab Set the Time period to Last 1 Hour(2) instead of Last 1 Week(s), which is default Check the Windows Event Log If all else fails, check the Windows Event log for more information about the error. Checking this may provide you with the answers you need, or at least give you more information to provide to Product Support if you need further assistance. Instructions available in Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Right-click on My Computer and select Manage Browse to Computer Management (local) > System Tools > Event Viewer > Application Look for Type Error events with Source Vista. This may help you determine the source of the error.

Issue Continuum supports different Wiegand card formats and Custom formats, what is the largest card number that can be used? Product Line Andover Continuum Environment ACX57xx (ACX5740, ACX5720) AC1, AC1-A, AC1 Plus ACX780, ACX700 Custom Wiegand - AccessFormat Array Corporate 1000, 26 bit, 32 bit, 37 bit. Cause When ordering access cards and configuring personnel you need to know the maximum numbers allowed. Resolution When configuring a Personnel object the maximum card number that can be entered is 4,294,967,295 the largest 32 bit number. This is the largest possible card number when working with Custom Wiegand. The maximum site code that can be used is 65,535 the largest 16 bit number. Other Wiegand formats: Continuum 37 bit: (Also known as Infinity 37) Card number range: 1 - 524,287.  Site Code range: 1 - 4,095 Note: This is a proprietary format and further format details are not available. Continuum 32 Bit (old format, not recommended for new sites): Card number range: 1 - 8,191.  Site Code range: 1 - 2,047 26 Bit open standard: Card number range: 1 - 65,535. Site Code range: 1 - 255 Corporate 1000 standard: Card number range: 1 - 1,048,575. Site Code range: 1 - 4,095 NOTE For custom formats the maximum format must not exceed 64-bits (i.e. start/end bit of the site code, card number, etc.) See Which HID card formats are supported by Continuum?.

Issue A Schedule or PE program can not change the value of a point because it is set by another process at a higher Command Priority. Product Line Andover Continuum Environment CyberStation bCX4040 B3s Cause Command value must be Relinquished at the priority that no longer needs to control the point's value so that a command with a lower priority can take control of it. Resolution Edit the point from the BACnet view. Go to the Command Priority tab, this tab shows the 16 priorities and their current statuses   Select the priority to relinquish and then click on the Relinquish button. The command with the next highest priority should then immediately take over.

Issue Basic Modbus RTU configuration to read a register from PM800 Power Meter. Product Line EcoStruxure Building Operation Environment Automation Server Modbus RTU PM800 Power Meter Cause Integrate power meters to a Building Operation front end for the user to view data and trend logs. Resolution Here are the steps to Configure a ModBus RTU interface in Building Operation to read the Line Voltage register from a PM800 Power Meter. (Assuming meter has already been properly wired to one of the serial ports on the AS) Create the Modbus Interface, in this case a Modbus Master Network.   Link the interface to a serial port in the AS in the Port Reference field, in this example to RTU device is wired to RS485-COMB   2. Under the interface create the RTU device. In this example the device id is 11, enter the appropriate id for the device. Once the device object is saved, the status should show 'Online' unless there is a communications issue. This is provided you have the online poll interval set. If this is disabled the device will stay offline until a Modbus register is polled and a valid response is received.    You can confirm that Building Operation is able to correctly detect the communications status of the device by disconnecting it from the commport and observing the status change to 'Offline', upon re-connection the status should once again display 'Online'   3. Under the device create a Modbus Point of type AnalogInput to get the value of the Line Voltage from the device. According to the documentation for the PM800 the register holding the line voltage is Function Code 3  and register  1124 The value of the point should now correspond to the line voltage in this case 125 volts.

Issue How to remove unwanted entries from the Alarm log, Access Event log, Error log, and Activity log automatically. Product Line Andover Continuum Environment Continuum SQL Server MSDE, 2000, 2005, 2008 Cause Want to setup automatic truncation of event logs and unsure how to do this in an SQL Server environment. Resolution MSDE Engine For MSDE, you can go to our Exchange online site and download the Standalone MSDE Database Utilities from the Tools, Utilities and Service Packs section of the Continuum part of our Exchange online web site. This is capable of automatically truncating the logs, as well making automated backups, checking for low hard drive space, etc. SQL Server 2000, SQL Server 2005 For full-blown SQL Server, you can easily create a scheduled Job. Details are described below. To create a scheduled Job that will truncate the Continuum logs in the SQL Server: 1. Open up SQL Enterprise Manager. Note that the SQL Server Agent service must be running in order to create a Job. 2. Highlight the Continuum database 3. From the Menu, select Tools \ Job Scheduling A wizard opens; "Welcome to the Create Job Wizard" Hit Next 4. Select Transact-SQL Command 5. Hit Next 6. For the Database Name, select ContinuumDB (or whatever the name of the DB is) 7. In the large white space for the Transact-SQL Command, cut and paste the code from our web site: /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 8. Hit Next 9. On the next screen, you are asked when you do want to run this job. Select "On a recurring basis" and hit the Schedule button. 10. On the Schedule page, set up whatever schedule you desire 11. Hit OK to close the Schedule Page 12. Hit Next 13. On the Job Notifications screen, you can choose (if you want) any email or net send alerts. This is optional 14. Hit Next 15. In the final page, you are given a summary of the Job you have just created and you can change the name of your Job to anything you want. It might be a good idea to give it a more descriptive name like "Weekly Log Truncation" 16. Click Finish and you are done. You should get a message that the job was created successfully. To verify that the Job is running correctly, you can go to the Enterprise Manager of SQL Server and click on the Management Folder, then expand the SQL Server Agent folder and click on Jobs. On the right-hand pane, you will see a list of created jobs. Scroll down and find the job that you just created. You can get information about the history of the Job, whether it ran successfully or not.   SQL Server 2008 1. Run Mgmt Studio and login as sa. 2. Make sure SQL Server Agent is running. Would expect it is by default. 3. Right-click on Jobs (under SQL Server Agent). Select New Job... 4. General tab - Name: TrimLogs // Owner: sa // Category: Database Maintenance // Enabled checkbox 5. Steps tab - New... // Step name: DateDiff // Type Transact-SQL script (T-SQL) // Run as: [null] // Database: ContinuumDB //Command: [pasted in code below]. Press OK. delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90   6. Schedules tab - New... // Name: Weekly // Schedule type: Recurring & Enabled // Occurs: Weekly // Recurs every: 1 week(s) on [whatever date and time]. Press OK. 7. Did not set up Alerts, Notifications or Targets. 8. Press OK. 9. Set it up to run a few minutes after creation. 10. After time passed, opened Mgmt Studio and double-clicked Job Activity Monitor. Saw TrimLogs had successfully run. 11. Ran query: Select count(*) from ActivityEvent to verify count went down.  

Issue How do I locate the consolidated patch files (modules) for the I/A Series G3 maintenance builds (3.6.406, 3.7.106, 3.8.37).  Please note:  I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center and include all updates for the previous builds. Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.406, 3.7.106, and 3.8.37 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution Please note:  New I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center.  The new builds already include the consolidated patches listed below. Below the latest consolidated patch files for I/A Series G3 maintenance builds 3.6.406, 3.7.106, 3.8.37 are listed.  The files contain updated modules and a set of release notes.  The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.406_SE_05272015.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.10 bajaui 3.6.406.3 control 3.6.406.1 docMbus 3.6.406.5 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 kitLon 3.6.406.1 lonworks 3.6.406.5 mbus 3.6.406.5 modbusCore 3.6.406.3 modbusSlave 3.6.406.2 modbusTcp 3.6.406.2 modbusTcpSlave 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 obixDriver 3.6.406.1 opc 3.6.406.1 pdf 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 report 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.9 workbench 3.6.406.3 Consolidated_Patches_3.7.106_SE_07242015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.10 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.3 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5       Consolidated_Patches_3.8.37_SE_07242015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.10 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.39 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.3 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.11 workbench 3.8.38.5 zwave 3.8.38.1   ********* Previous Release History ********* Consolidated_Patches_3.6.406_SE_09112014.zip  ...  Click here for Release Notes alarm 3.6.406.2 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2 Consolidated_Patches_3.6.406_SE_11112014.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2   Consolidated_Patches_3.7.106_SE_09112014.zip   ...  Click here for Release Notes alarm 3.7.106.5 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_11112014.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_01222015.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.14 baja 3.7.106.8 bajaui 3.7.106.5 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 hx 3.7.106.2 kitControl 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.3 mbus 3.7.106.4 modbusCore 3.7.106.1 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.3 weather 3.7.106.1 web 3.7.106.16 workbench 3.7.106.5   Consolidated_Patches_3.7.106_SE_05272015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.9 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5         Consolidated_Patches_3.8.37_SE_09112014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.6 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_10012014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1       Consolidated_Patches_3.8.37_SE_11112014.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.6 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_01222015.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.9 baja 3.8.38.6 bajaui 3.8.38.2 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 hx 3.8.38.3 kitControl 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.3 mbus 3.8.38.4 modbusCore 3.8.38.1 modbusTcp 3.8.38.2 nDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.3 web 3.8.38.7 workbench 3.8.38.2 zwave 3.8.38.1 Consolidated_Patches_3.8.37_SE_05272015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.9 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.38.1 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.2 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.10 workbench 3.8.38.4 zwave 3.8.38.1 bajaui 3.8.38.2 bajaui 3.8.38.2 baja 3.8.38.6 baja 3.8.38.6               obixDriver 3.7.106.4 alarm 3.7.106.5 alarm 3.7.106.5 alarmOrion 3.7.106.2 hx 3.8.38.3 hx 3.8.38.3 hx 3.8.38.3   gx 3.8.38.1 gx 3.8.38.1 gx 3.8.38.1   hx 3.8.38.3   kitLon 3.8.38.1 kitLon 3.8.38.1   nDriver 3.8.38.1   nDriver 3.8.38.1

Issue Using the RD and TD LEDs to help commission and Fault finding a Modbus RTU Continuum Xdriver Using the RX and TX LEDs to help commission and Fault finding a Modbus RTU AS, AS-P, AS-B Product Line Building Operation Automation Server Premium Continuum bCX4040 (BACnet) Environment Continuum Automation server Cause How to use the TD RD(TX RX) LEDs to help commission or check an installation Resolution Continuum The Comm Port LEDs on a net controller can be helpful when first setting up or fault finding an Xdriver (ModbusRTU) Every time the net controller transmits the TD LED will flash and every time another device on the bus transmits (such that the net controller can receive it) the RD LED will flash. Thus if Xdriver seems not to be working correctly this is often the first thing to check A simple check with Modbus RTU would be to stop any automatic polling on the network, then manually refresh a modbus point and watch for a single Transmit (TD) followed by a Receive (RD). SmartStruxure The Comm Port LEDs on an AS controller can be helpful when first setting up or fault finding ModbusRTU Every time the AS transmits the TX LED will flash and every time another device on the bus transmits (such that the AS can receive it) the RX LED will flash. A simple check with Modbus RTU is to create only a  single device (or inhibit polling to all but one device) and watch for a single Transmit (TX) followed by a Receive (RX). Modbus Simulation Another useful technique when commissioning or troubleshooting with Modbus is to simulation software on a PC (with RS232/485 convertor for RTU if required). A Slave device or the Master node can be simulated eg ModSim, ModScan, ModbusSlave, ModbusPoll, Mod_RSsim

Issue How can objects of a SmartStruxure™ Lite network be made available as BACnet points to third party BACnet building management system (BMS)? Product Line EcoStruxure Building Operation Environment SmartStruxure Lite BACnet Cause The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet and this will need to be changed if BACnet over IP is required. Resolution The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet. To verify or to change which BACnet protocol is currently in use, select the SmartStruxure Lite Manager that you want to configure from the left-side Network panel. Then choose the BACnet configuration list item. Define the Network Number (if the protocol selected is BACnet IP). Note: The Network number must be defined only on the monitor Manager. It shall be different then the Parent Network where the monitor is connected. A BACnet Device is uniquely located by a network number and a MAC address. Creating two or more B/IP networks, each with a unique network number, can be useful for limiting the propagation of local broadcast messages and for providing security by confining traffic to a particular geographic or logical area. Select the desired protocol type from the drop-down list between BACnet IP and BACnet Ethernet. Then choose an optional port number (if the protocol selected is BACnet IP). Default is 47808. Select the BACnet Priority of the BACnet write action of the SmartStruxure™ Lite's network monitor. Default is 10. Note: SmartStruxure™ Lite does not support BACnet Write Priority, per se. However, in Firmware version 2.4.x and newer, it is possible to assign the write priority for all SmartStruxure™ Lite BACnet points. Default value is 10, except if you upgrade a Manager using a version 2.3.x or older, BACnet priority will be 8, but can be changed. Click the Save button to apply the configuration changes. Click hit the Save All button to make the modifications permanent and reboot the Manager for the new options to enter into effect. Change the BACnet instance number of the Manager if required. IMPORTANT Each Manager must have a unique BACnet device instance number. A Manager device instance number can be changed by selecting the top-left icon inside the left-side Network panel.

Issue Wiring a MD10B-24 / MD20B-24 actuator to a Climatronic CXT / CXR / CSC Actuator Environment MD10B-24 MD20B-24 Actuator Climatronic CXT CXR CSC Cause The Climatronic controller switches the O volt side of the 24 volt supply, but the actuators shows that it requires 24 volts to open and close. Resolution The Satchwell range of Climatronic controllers have always switched the 0 volt side of the 24 volt supply to control the actuator position. CXT Controller - Terminals 13 and 14 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CXR Controller - Terminals 23 and 24 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CSC Controller - Terminals 33 and 32 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. The MD10B-24 / MD20B-24 datasheet shows the wiring as follows; For the complete MD10B datasheet, please click HERE. For the complete MD20B datasheet, please click HERE. The above actuator wiring shows a 0 volt connection to the common connection (1) and a switched 24 volt connection (2 or 3). To connect the MD10B-24 / MD20B-24 actuator to any of the above controllers it will be necessary to connect the actuator as follows. Controller 24 volt  (37) to connection wire (1). Controller Open signal (14, 24 and 32) to connection wire (2). Controller Close signal (13, 23 and 33) to connection wire (3). Please note that the actuator direction can be changed by repositioning the switch on the front of the actuator.