Building Automation Knowledge Base

Issue When attempting to detach an AS, PCT continues to shown the server as being attached to the ES.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool 1.x (PCT) Cause In PCT, when an AS is detached from its parent ES, the ES name still appears in the Added to parent column of the Servers list. Resolution Once the AS has been detached from an ES it can be added to another ES though Workstation using the following steps even though the "Added to parents" column shows otherwise.   To create a SmartX server In WorkStation, in the System Tree panel, select the Servers folder. On the File menu, point to New and then click Server . In the Create Object wizard, in the Name box, type a name for the SmartX server. In the Description box, type descriptive information about the SmartX server. Click Next . In the Configure IP/DNS Address and Port page, in the Address box, type the IP address or fully qualified domain name of the SmartX server. Notice If the SmartX server has been assigned a dynamic IP address, use the fully qualified domain name of the SmartX server instead of the IP address. In the Protocol box, select a protocol for the SmartX server. For more information, see EcoStruxure BMS Server Communication . In the Port box, enter a port number. Click Create. In the Log on dialog box, in the Password box, type the custom password if required. Click OK.   For more information, see Creating a SmartX Server

Issue In the Xenta Servers, it is possible to set the communication port to RS232 or RS485. In EBO this is not possible on the Automation Server (AS) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server  Xenta 500 Xenta 700 Xenta 900 Cause The AS serial ports are RS-485, not RS-232. Resolution There are two solutions to consider when Xenta is using an RS-232 connection: If the connected device also has a RS-485 connection switch to that. (Optionally replace the device with one that has RS-485.) Use a RS-232/RS-485 converter. The converter must have automatic data direction detection and control on the RS-485 side, since our Automation Server devices have no RTS signal (to enable the transmitter) available externally.

Issue Running an I/NET Seven report and only seeing the first 500 people or doors in a system. Keyword search: Crash when an attempt to open, Crystal Reports, and failure. Product Line TAC INET Environment I/NET system and desire to run reports over a lot of data Cause The Crystal Reports that I/NET is using has a default value of 500 objects to be listed in a report. If you require more objects to be listed in a report, this requires a windows registry change to do this. Resolution Note in the attached document the registry location may change slightly based on the version of I/NET and SevenReports installed version.   If unsure or the locations cannot be found search for the following registry keys: BrowseTimeout - This entry controls how long, in seconds, the Info Report Designer will browse for records. MaxNBrowseValues - This entry controls how many unique records the Info Report Designer will browse before stopping and displaying the records found. For the Release 2.40a and above running the NON_RDC release HKEY_CURRENT_USER\Software\Business object\Suite11.0\Crystal Reports Designer\ For the Release 2.41 and above running RDC version: HKEY_CURRENT_USER\Software\Business object\Suite11.0\Crystal Reports Designer Component\ In the Crystal Report terminology, an object could be people or doors, in which case make the registry change based upon the largest number you have. For example, if a site has 5000 people and 500 doors, set the registry to accommodate 5000. The steps required to make these changes are in the Crystal Report Tech support paper linked to this article.

Issue 'Program interface does not match previously defined interface' when downloading/commissioning a Xenta 400/300 controller. NS, #59 Environment Vista System Plugin TAC Xenta Programmable Controllers LonMaker/NL220 Cause You get this error if you have 2 controllers that are using the same device template (XIF file) and one is system program version <3.5 and one is >3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. Controllers can share device template even if they have different applications as long as the are using the same SNVTs. Different types of Xenta controllers can also share the same XIF file. Resolution To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and it’s own template. Open the application form System plug-in by right clicking on controller and select configure-edit. To give the application a new XIF either add a “dummy” SNVT or go to device configuration and uncheck the tick box for “XIF header generated according to LonMark standard” Hit F12, select commands and generate. F12 again and save the application to the hard drive by selecting File-save as. In system plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and TAC Database. If you are asked to resynchronize, do so. In Menta create a new application with just one PVR block in it. Go to the controller, connect a serial cable and download the small application that you just created. Go back to the system plug-in and download the controller. Commission in LonMaker.

Issue Some things to look for when you get ID 0 errors when doing a Save to Database Product Line Andover Continuum Environment Continuum Database Cause There are several causes such as date and time settings, scan variables, IP addresses, etc. Some troubleshooting steps are listed below based on different possible causes. Resolution Confirm that the date has been set in the controller. Edit the scan system variable and put a description in the description field. Doing this will update the LastChanged attribute of the Scan system variable. Verify that an IP address has been configured in the controller. If you are saving a remote site back that is earlier than revision 1.52 you need to set an IP address in the remote controller. Verify that the CX controller is at least revision 1.5 Verify that the controller is not reset. In some rare cases we saw that you would have a problem if you created the CX controller while offline editing. The correction in this case was to go offline edit, delete the CX in Cyberstation, go online, recreate the CX and then do the save to database. If the controller you are saving back has to go through a firewall and the firewall has blocked the access to the other IP addresses of the other controllers this controller knows about. Port numbers 33487, 33440, and 33456 are blocked in a router. Specifically port number 33456 is used for the save to database functionality. Make sure Firewall programs are not blocking the network connections. Disable any firewall programs before doing a “Send to DB”. Create a debug file (Acc_Dump_Debug.txt). See the Infinity-to-Continuum Upgrade document. Look in the debug file and see where it failed and act accordingly. 

Issue Unable to use plug-ins to configure devices in LonMaker or NL220, even after installing the DRF kit. Product Line TAC Vista Environment LonMaker NL220 Device Plug-in Cause The DRF (Device Resource Files) kit is not installed before devices are added in Lonmaker or NL220 (and other tools) Resolution The DRF kit must be installed and properly registered in the PC before any devices are created. If you are in this situation you will need to remove all devices and the device templates and you need to start all over. It is therefore recommended that the DRF kit are installed before adding any device and that you create one device and test the plug-in to make sure that the DRF kit are properly registered before adding a number of devices into the database.

Issue TS-57XX and TS-67XX 10 K thermistor (no 11 K shunt) sensor resistance table Environment Site with thermistor sensor Cause TS-57XX and TS-67XX 10 K thermistor (no 11 K shunt) sensor resistance table Resolution   Temp (°C) Temp (°F)  Sensor Ohms  -40.0° -40.0° 239,700 -39.0° -38.2° 226,000 -38.0° -36.4° 213,100 -37.0° -34.6° 201,100 -36.0° -32.8° 189,800 -35.0° -31.0° 179,200 -34.0° -29.2° 169,300 -33.0° -27.4° 159,900 -32.0° -25.6° 151,200 -31.0° -23.8° 142,900 -30.0° -22.0° 135,200 -29.0° -20.2° 127,900 -28.0° -18.4° 121,100 -27.0° -16.6° 114,600 -26.0° -14.8° 108,600 -25.0° -13.0° 102,900 -24.0° -11.2° 97,490 -23.0° -9.4° 92,420 -22.0° -7.6° 87,650 -21.0° -5.8° 83,150 -20.0° -4.0° 78,910 -19.0° -2.2° 74,910 -18.0° -0.4° 71,130 -17.0° 1.4° 67,570 -16.0° 3.2° 64,200 -15.0° 5.0° 61,020 -14.0° 6.8° 58,010 -13.0° 8.6° 55,170 -12.0° 10.4° 52,490 -11.0° 12.2° 49,950 -10.0° 14.0° 47,540 -9.0° 15.8° 45,270 -8.0° 17.6° 43,110 -7.0° 19.4° 41,080 -6.0° 21.2° 39,140 -5.0° 23.0° 37,310 -4.0° 24.8° 35,580 -3.0° 26.6° 33,930 -2.0° 28.4° 32,370 -1.0° 30.2° 30,890 0.0° 32.0° 29,490 1.0° 33.8° 28,160 2.0° 35.6° 26,890 3.0° 37.4° 25,690 4.0° 39.2° 24,540 5.0° 41.0° 23,460 6.0° 42.8° 22,430 7.0° 44.6° 21,440 8.0° 46.4° 20,510 9.0° 48.2° 19,620 10.0° 50.0° 18,780 11.0° 51.8° 17,980 12.0° 53.6° 17,210 13.0° 55.4° 16,480 14.0° 57.2° 15,790 15.0° 59.0° 15,130 16.0° 60.8° 14,500 17.0° 62.6° 13,900 18.0° 64.4° 13,330 19.0° 66.2° 12,780 20.0° 68.0° 12,260 21.0° 69.8° 11,770 22.0° 71.6° 11,290 23.0° 73.4° 10,840 24.0° 75.2° 10,410 25.0° 77.0° 10,000 26.0° 78.8° 9,602 27.0° 80.6° 9,226 28.0° 82.4° 8,866 29.0° 84.2° 8,522 30.0° 86.0° 8,194 31.0° 87.8° 7,879 32.0° 89.6° 7,579 33.0° 91.4° 7,291 34.0° 93.2° 7,016 35.0° 95.0° 6,752 36.0° 96.8° 6,500 37.0° 98.6° 6,258 38.0° 100.4° 6,027 39.0° 102.2° 5,805 40.0° 104.0° 5,592 41.0° 105.8° 5,389 42.0° 107.6° 5,194 43.0° 109.4° 5,007 44.0° 111.2° 4,827 45.0° 113.0° 4,655 46.0° 114.8° 4,490 47.0° 116.6° 4,331 48.0° 118.4° 4,179 49.0° 120.2° 4,033 50.0° 122.0° 3,893 51.0° 123.8° 3,758 52.0° 125.6° 3,629 53.0° 127.4° 3,505 54.0° 129.2° 3,385 55.0° 131.0° 3,271 56.0° 132.8° 3,160 57.0° 134.6° 3,054 58.0° 136.4° 2,952 59.0° 138.2° 2,854 60.0° 140.0° 2,760 61.0° 141.8° 2,669 62.0° 143.6° 2,582 63.0° 145.4° 2,498 64.0° 147.2° 2,417 65.0° 149.0° 2,339 66.0° 150.8° 2,264 67.0° 152.6° 2,191 68.0° 154.4° 2,122 69.0° 156.2° 2,055 70.0° 158.0° 1,990 71.0° 159.8° 1,928 72.0° 161.6° 1,868 73.0° 163.4° 1,810 74.0° 165.2° 1,754 75.0° 167.0° 1,700 76.0° 168.8° 1,648 77.0° 170.6° 1,598 78.0° 172.4° 1,550 79.0° 174.2° 1,503 80.0° 176.0° 1,458 81.0° 177.8° 1,414 82.0° 179.6° 1,372 83.0° 181.4° 1,332 84.0° 183.2° 1,293 85.0° 185.0° 1,255 86.0° 186.8° 1,218 87.0° 188.6° 1,183 88.0° 190.4° 1,149 89.0° 192.2° 1,116 90.0° 194.0° 1,084 91.0° 195.8° 1,053 92.0° 197.6° 1,023 93.0° 199.4° 994 94.0° 201.2° 966 95.0° 203.0° 939 96.0° 204.8° 913 97.0° 206.6° 887 98.0° 208.4° 863 99.0° 210.2° 839 100.0° 212.0° 816 101.0° 213.8° 794 102.0° 215.6° 773 103.0° 217.4° 752 104.0° 219.2° 732 105.0° 221.0° 713 106.0° 222.8° 694 107.0° 224.6° 675 108.0° 226.4° 658 109.0° 228.2° 640 110.0° 230.0° 624 111.0° 231.8° 607 112.0° 233.6° 592 113.0° 235.4° 576 114.0° 237.2° 562 115.0° 239.0° 547 116.0° 240.8° 533 117.0° 242.6° 520 118.0° 244.4° 507 119.0° 246.2° 494 120.0° 248.0° 482 121.0° 249.8° 470

Issue A Network 8000 LNC-100 cannot communicate to LON devices under it even though all the devices can be accessed with WorkPlace Tech or a LON commissioning tool. Product Line TAC IA Series Environment NETWORK 8000 LNC-100 LON devices WorkPlace Tech Cause If the LON network is known to be good and otherwise functioning, this issue indicates a problem with the LON interface in the LNC-100. This is typically caused by accidentally attempting to commission the LNC-100 using LonMaker or other LON commissioning tool. Attempting to commission the LNC-100 will result in its LON interface being set into a network state called HARD - OFFLINE. Resolution The condition can be corrected using the Echelon NODEUTIL program to set the interface network to the required CONFIGURED - ONLINE state. NodeUtil can be downloaded from The Exchange Download Center. After downloading NodeUtil to your computer, open a command prompt window and launch NodeUtil in that window.  After launching NodeUtil, perform the following steps to correct the problem. Press the F key to execute the Find function.  This will browse the connected LON network for all attached LON devices.  In the list of found devices, the LNC-100 will be identified with the program id "C 1 11.0A". Press the G key to execute the Go To Device function.  Enter the device number of the LNC-100 (program ID "C 1 11.0A") as displayed in the list of discovered devices.  The device menu will then be displayed. Press the S key to display the status of the device.  Typically 17 lines of status information are displayed followed by the "Device Status" menu.  Press Y to clear the error status.  The "Device State" line will usually show a state of either Configured, Off-line or Hard, Off-line. Press the  M key to change the device mode and state. After selecting the M command, the list of mode options is displayed.   Press the S key to select the State menu. The list of State options will be displayed.  Press the C key to set the device to the Configured state. A status message will be displayed followed by the DEVICE prompt. Press the M key again to display the Mode options then press N to set the device into the OnLine mode. A status message will be displayed followed by the DEVICE prompt. Press the S key again and verify that the Device State is now Configured, On-line. Press the D key to display the domain address table of the LNC-100.  One or two lines of device domain address information will display.  If two domain addresses were defined in the SYS: SIM block of the device, two lines of information will display, otherwise only one line will display.  Verify that the address information (Subnet, Node and Domain ID) are as set in the SYS: SIM block. The data entered for Domain0, Subnet0 and Node0 will be displayed on the Index 0 line. The data entered for Domain1, Subnet1 and Node1 will be displayed on the Index 1 line. Press the E key to exit the Device level and press the E key a second time to exit the program.

Issue What is the A/D resolution of the Inputs and Outputs on the Xenta product line? Environment Xenta 28x Xenta 30x Xenta 4xx I/O Modules Cause Due to project specifications and requirements it is important to know the input and output resolution of the Xenta product line. Resolution The Xenta Product line has resolutions for inputs and outputs accordingly: Controller Thermistor Inputs Universal Inputs Analog Outputs 281 12 bit   12 bit 282 12 bit   12 bit 283 10 bit   12 bit 301 12 bit   12 bit 302 12 bit   12 bit 421A/422A   12 bit   451/452 12 bit 12 bit   451A/452A   12 bit 8 bit 471   12 bit   491/492     12 bit

Issue What Oil can be used for the DWT0001 pocket sensor to prevent problems with condensation? Condensation causes the temperature sensor to corrode. Environment Pocket sensor DWT0001 STP660 Cooling Condensation Cause If a pipe sensor pocket is mounted incorrectly on a cooling system condensation can build up in the pocket and corrode the sensor. Resolution Cooling system sensor pockets should be mounted at an angle to prevent condensation building up in the pocket.  See datasheet for the DWT0001, click here.  For the STP660 click here. The recommended oil to use is either  ‘Fina 'Solco' AC43 or Shell 'Dialo Oil B'.

Issue Need the Part Number for a Xenta 527 or 527-NPR Environment I/NET Vista Cause There are 2 Varieties of the Xenta 527 available: The Xenta 527 and the Xenta 527 NPR. While these devices share some similarities, there are some key differences. Resolution There are 2 Varieties of the Xenta 527 available. The Xenta 527 and the Xenta 527 NPR. The Xenta 527 is sometimes referred to as the Xenta 527 - Web Server.  This part can be used on I/NET systems, or I/NET systems that integrate with Vista.  The Xenta 527-NPR is use on I/NET systems.  It is a scaled down version of the standard Xenta 527 that will only provide the functions needed for I/NET.  This serves as a direct replacement for existing NPR devices. The Part numbers for these devices are as follows: Xenta 527 (Web Server) - 007308200 Xenta 527 (Web Server) Package of 3 - 007390130 Xenta 527-NPR - 007308210

Issue Cannot commission an IC3 LON controller in LonMaker. It has become applicationless and the red service LED is flashing or is permanently lit.  Product Line Satchwell Sigma Environment Satchwell Sigma Controller IC3 IC LON FTT-10 NodeUtil Cause The Echelon chip has become 'locked' and requires resetting.  This can be caused by corrupted controller files, very high LON traffic (> 50% Bandwidth), or the controller has started from "start-up mode" or cold start.   Resolution The Echelon chip can be reset using NodeUtil.exe  .  This is a DOS-based program that can be loaded onto a laptop with an FTT-10 Echelon adaptor. A clean working set of controller files will be downloaded to the device. In the case of a flashing red LED - Download 'clean' files to the controller Start NodeUtil on the laptop and plug LON cable into the controller Reset controller (via onboard reset button) Activate the plug-in LON card service pin and the Neuron Id should appear on the laptop. Note: If further controller resets and service pin activations fail to generate the service pin echo then discard the plug-in card and replace with a new one. From the NodeUtil menu select 'R' and enter the Node Id number Confirm the reset of 3150 Node The service LED should stop flashing and the controller should now be 'Configured' that is not 'applicationless' In the red LED is permanently lit - Download 'clean' files to the controller, the Echelon chip will become locked again. Repeat the reset procedure using NodeUtil.exe, this will allow the controller to work, but the plug-in card will need to be replaced. Example of NodeUtil process; NODEUTIL> (H)elp with commands A -- (A)dd node to list. D -- Set the (D)omain of the network interface. E -- (E)xit this application and return to DOS. F -- (F)ind nodes in the current domain. G -- (G)o to node menu............. H -- (H)elp with commands. L -- Display node (L)ist. M -- Change node (M)ode or state. O -- Redirect (O)utput to a file. P -- Send a service (P)in message. R -- (R)eboot 3150 node. S -- Report node (S)tatus and statistics. T -- (T)ransceiver parameters. V -- Control (V)erbose modes. W -- (W)ink a node. Z -- Shell out to DOS. NODEUTIL> Received an ID message from node 2. Program ID is ICLON1a NODEUTIL> Received an ID message from node 2. NODEUTIL> (R)eboot 3150 node Enter node id for reboot (0-2) [2] :2 *** Neuron 3150: Rebooting will reset comm. params, node state on-chip EEPROM variables and buffer configuration Are you sure you really want to do this? (Y/[N]): Successfully rebooted node NODEUTIL> A second solution has been provided by a customer and could be considered if the above suggestions does not provide a solution. Alternative reset procedure provided by a customer is as follows: - 1. Removed the IC LON from both the LON and the Sigma network. 2. I used SCDU tool to re-node the ICLON to a random IP address, which I believe cleared the database and the files etc. 3. I removed the power form the ICLON and then removed the LON daughterboard card from the ICLON mainboard. 4. Re-instated power and re-installed the LON daughterboard card. 5. Connected with NODE Utility as per the product data-sheet below. And cleared the LON comms buffers as the suggested method. 6. Checked that the red constant service light ceased from the constant illumination. And witnessed that the Green LON heartbeat LED was operational. 7. Re-Node the ICLON to the original IP and check operation. * The Sigma IC-LON plug-in card can be purchased using the part number S-LON. The S-LON has been discontinued as of 29th December 2017 and it is now in the service period (limited quantities available for purchase). Refer to PA-00528 for details.

Issue What is the pin configuration for Modbus RTU when using a 9 pin comm port on a BCX controller. Environment BCX Modbus RTU Cause Connecting a BCX or CX controller to a Modbus RTU device. Resolution RS232 connection for a 9 pin BCX comm port.   BCX Comm 1 (9 Pin)            RJ 45 Connector @ Modbus device Pin 1 CXD        -->                 Pin 1 DTR Pin 7 RTS        -->                 Pin 2 CTS  Pin 4 DTR        -->                 Pin 3 CXD Pin 8 CTS        -->                 Pin 4 RTS Pin 5 GND       -->                 Pin 5 GND Pin 3 TD           -->                 Pin 6 RD Pin 6 DSR        -->                 Pin 7 DSR Pin 2 RD           -->                 Pin 8 TD        

Issue  Interstation links between UNC and Enterprise Server are not functioning. Product Line TAC IA Series Environment Windows 7 Windows Vista Windows XP Niagara R2 Cause Windows Firewall is enabled by default on desktop operating systems post Windows XP SP1. The Windows Firewall must be configured to allow unsolicited messages such as alarms and inter-station links from UNC's to be received by the Enterprise Server. Resolution WINDOWS FIREWALL OVERVIEW Windows Firewall is a “state-full packet filter” firewall by default. This means that all TCP packets trying to enter a system with the Windows Firewall enabled will be discarded unless those packets are responses to queries from that system, or if the packet is destined for a port that has an exception create for it. In other words, unless an exception is created, or the Windows Firewall is disabled a valid message such as an alarm or an inter-station link from a UNC will be blocked by the Windows Firewall and won’t be received by the Enterprise Server. Windows Firewall allows for exceptions to be created for particular ports and from particular ranges of IP addresses. For example, one could create a rule that accepts unsolicited packets on port 25, but only from the range of addresses from 192.168.0.1 through 192.168.0.254. There are two kinds of exceptions: program exceptions and port exceptions. A program exception is where the Windows Firewall is instructed to open ports that a certain program needs for unsolicited communications. This is the preferred method since Windows Firewall is only open while the program is waiting to receive the connection. In contrast, a port exception is the Windows Firewalls' way of acting like a port-filtering router. In other words, Windows Firewall can be configured to let in any traffic on a particular port whether it's solicited or not. Creating a Program Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Program..." Click the browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” adding it to the list of programs. To specify which TCP/IP devices can use the port, click Change Scope and select one of the following To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK. The program will appear selected on the Exceptions tab under Programs and Services. Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Right click Inbound Rules and select New Rule Select program and click Next. Click the Browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” and click Open to add it to the list of programs. Click next. Select Allow the connection and click next Select the Network profiles that the rule applies to and click next Domain The domain profile applies to a network when a domain controller is detected for the domain to which the local computer is joined. If you select this box, then the rule applies to network traffic passing through a network adapter connected to this network. Private The private profile applies to a network when it is marked private by the computer administrator and it is not a domain network. Newly detected networks are not marked private by default. A network should be marked private only when there is some kind of security device, such as a network address translator or perimeter firewall, between the computer and the Internet. The private profile settings should be more restrictive than the domain profile settings. Public The public profile applies to a network when the computer is connected directly to a public network, such as one available in airports and coffee shops. The public profile settings should be the most restrictive because the computer is connected to a public network where the security cannot be as tightly controlled as it is in an IT environment. Name the exception and click Finish Creating a Port Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Port..." In the Port number field type 80 Select TCP. Type a short name for the port To specify which TCP/IP devices can use the port, click Change Scope and select one of the following. To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK twice. The Port will appear, selected, on the Exceptions tab, under Programs and Services. Repeat the procedure to add an exception for port 3011 Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Select  Connection Security Rules: From right side menu, select “New  Rule” Select Rule Type then select Custom then click Next: Select “Protocol and Ports” then select the TCP protocol type, specify required ports, then click Next. This screen capture     shows the configuration for the I/A Series (Niagara) R2 required ports: On the “When does this rule apply screen, click Next, leaving all three areas checked. On the next screen, name the rule “Niagara 80, 3011 TCP” and click “Finish”. Repeat steps 3 through 7, above, selecting UDP instead of TCP.  All other entries are the same except in step 7 the rule name will be UDP instead of TCP. After completing step 8, the Connection Security Rules will be displayed in the center section of the program window.  You should see the following two rules:  

Issue Previously purchased WorkPlace Tech software is being moved from one computer to another. What proof of purchase is required for the software so that the purchase of a new copy is not required? How can they prove that they purchased the original copy if the original purchase order and invoice or license request form with unlock code cannot be located? Product Line TAC IA Series Environment WorkPlace Tech 5.x.x NOTE: Old installation must be of same major release (release 5) as the new copy being installed. If the old system has release 4 of the WorkPlace Tech software, the new computer will need to be running Windows XP and the release 4 version of the WorkPlace Tech software will have to be installed on the new computer. Cause Software needs to be migrated to a different computer. This could be due to an upgrade in hardware. Resolution The preferred proof of purchase is a copy of the license request form that shows the customer information, license requested, license unlock code, and the original sales order number. Depending on when or how the license for the existing copy of the WorkPlace Tech Tool software was ordered, this document may have been received by fax or email. If this information is available, a copy can be emailed along with the new license request form (requesting the same product license as the original) to IASeries.license@schneider-electric.com. Note that in some cases the new product code may vary slightly from the original. For example, the original license may have been for WP-TECH-52 and the new one for WP-TECH-58 or WP-TECH-50 -- these licenses are all equivalent. The WIB licensing team will verify the submitted information and if complete/correct, generate the new license unlock code. If the old computer is still functional, the License Diagnostic program can be used to generate a proof of purchase for the software installed on the computer. Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file. NOTE: If the old computer has WorkPlace Tech release 4.0.0, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed). If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open". This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. On the new computer run the "Purchase WorkPlace Tech Software" or "Purchase WIBs Software" from the icon on the desktop and fill out the Field Office & Shipping information sections using the information for your office. The "End Customer Information" must match the information from the old system. In the Package List, the same product should be selected as was licensed on the old system. In some cases, the part number may be slightly different, for example, the old system may have been licensed for WP-TECH-53U and on the new system, the product code may be WP-TECH-50U. These license product codes are equivalent. Add the selected package part number to the order list, click the [Accept Order] button and output the order form to a file. Click the [Done] button to exit the purchase screen and click [Done] to exit the Purchase program. Email the saved license diagnostic form and the saved order form to Product Support Services for verification. Product Support Services will verify the information and if correct, forward the information to IASeries.license@schneider-electric.com for processing. They will email the unlock code back to the requesting office. Follow the normal procedures to install the unlock code.

Issue Installed the tool under Windows 10 but was unable to assign a port in the tool's connection settings because there are no ports showing in Windows Device Manager. Product Line Andover Continuum Environment RoamIO2 BACnet Service Tool Cause Windows legacy hardware configuration. Windows 10 by default does not include the legacy ports. Resolution Legacy ports must be added to the Device Manager. 1. Open Device Manager from Windows Control Panel. 2. Select 'Action' then 'Add legacy hardware' or Go to "Start" and type hdwwiz.exe then press Enter 3. Next 4. Next 5. Next 6. Select 'Ports (COM & LTP) then Next 7. Select Microsoft/Standard Serial over Bluetooth link then NEXT 8. Complete the legacy hardware installation, Device Manager will then show the ports. 9. In the Service Tool select the appropriate port.   When the connection has been established from Windows PC to RoamIO2 device, the BlueTooth settings in Windows will indicate 'Connected'  NOTE that if it only indicates paired there will be no data transfer even though the blue LED is illuminated on the RoamIO2 device. (see screenshot below)

Issue Satchwell CZU Mk3 Zonemaster Controller requires replacement. Product Line Field Devices Environment Stand alone Fan Coil Unit Temperature Controller. Satchwell CZU Mk 3 Zonemaster Controller. CZU 3201 CZU 3202 CZU 3203 Cause Obsolescence of Satchwell CZU Mk3 Zonemaster Controller. Resolution Replacement of Satchwell CZU Mk 3 Zonemaster Controller with S-E Satchwell CZU Mk 4 Zonemaster Controller. The CZU 4201 may be used to replace the following CZU Mk 3 Controllers :- CZU 3201, CZU 3202, CZU 3203 N. B. CZU 3201 Controllers provided an additional -9 to +9 V d.c. output enabling connection to peripherals such as the Satchwell NSU 1401 Night Set-back Override Unit, TSU 1402 Two Step Auxiliary Unit and SSU 1403 Signal Selector Unit. CZU 3202 and CZU 3203 Controllers provided an additional -0.5 to +9 or -9 to +0.5 V d.c. output enabling connection to the Satchwell NSU 1401 Night Set-back Override Unit. Additional outputs are not provided on the CZU 4201 Controller and in those applications where these are required then it will be necessary to consider an alternative Controller to the CZU 4201. Details of the CZU 4201 may be viewed  here. A remote Satchwell Adjustable Room Temperature Sensor such as the DRT 3451, or a remote Satchwell Duct Temperature Sensor from the DDU range of Sensors may have been installed and connected to the Controller. Any existing remote Satchwell Temperature Sensor may be retained for connection to the CZU 4201. Should the remote Satchwell Adjustable Room Temperature Sensor require replacement then this may be replaced by an S E STR 612 Adjustable Room Temperature Sensor. Details of the STR 612 may be viewed here. Should the remote Satchwell Duct Temperature Sensor require replacement then this may be replaced by an S E STD 670 Duct Temperature Sensor. Details of the STD 670 may be viewed here.

Issue In Niagara G3, a BACnet proxy point was initially added to the database as Read only; how can it be change to a BACnet Writable proxy point? Environment Niagara G3 all versions Cause BACnet proxy point type (read only. writable, etc.) is selected when the proxy point is first added to the database. The BACnet Proxy Point was initially discovered and added to the database as Read Only Proxy Point. Resolution Unfortunately, once the BACnet Proxy Point is added to the database its Type value can not be changed. The Proxy Point will have to be deleted, rediscovered and re-added to the database. This time when adding the Proxy Point to the database, make sure to select writable for Type.

Issue In Function Block Editor, it is possible to define units for function blocks, and these units can only be set to basic units. There is no way to add a metric prefix to the unit. For example W or Wh can be used, but it is not possible to define kW, MW or kWh, MWh. Unit configuration in Function Block Editor v. 1.8 Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 1.8 or earlier Cause Metric prefixes are not implemented for function blocks in Building Operation version 1.8 or earlier. Resolution Upgrade EcoStruxure Building Operation to version 1.9 or later. When editing a function block In Function Block Editor click Select unit and choose unit and Prefix. Function block with prefix in v. 3.0

Issue Is it possible to just install the IA Commissioning Tool (WPCT) or IA Flow Balance Tool without having to install WorkPlace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series WorkPlace Tech Commissioning Tool I/A Series WorkPlace Tech Flow Balance Tool Cause  WorkplaceTech is not required on the PC but the operator needs to use the WPCT and or Flow Balancing Tool. Resolution It is possible to install the WPCT and/or the IA Flow Balancing software without having to install WorkPlace Tech.  At the time of the WorkPlace Tech installation, there are three options to select from: WorkPlace Tech Flow Balance Tool Workplace Tech Commissioning Tool WorkPlace Tech 5.x. WorkPlace Tech Flow Balancing Tool is preselected.  It cannot be deselected – it must be installed.  You can choose to install the WorkPlace Commissioning Tool by selecting it. If WorkPlace Tech is not needed then do not select the box next to it. WorkPlace Tech will not be installed during the installation process.