Building Automation Knowledge Base

Issue Is it possible to use 24VDC as power supply to the OP7? Environment OP7 power supply adapter included in package. Cause The documentation only recommends using 24VAC as power supply. Resolution Usage of 24VDC is not tested, and therefore not recommended or supported.

Issue Installing Echelon Network Interfaces on Windows 7 Operating Systems Environment Microsoft Operating Systems: Microsoft Windows 7 (64-bit and 32-bit) Windows Server 2008 R2 (64-bit), Windows Vista (32-bit) Windows XP (32-bit) Windows Server 2003 (32-bit) Echelon Network Interfaces: i.LON 10 Ethernet Adapter i.LON 100 Internet Server i.LON 600 Internet Server PCLTA-21 PCI Network Interfaces PCLTA-20 PCI Network Interfaces PCLTA-10 ISA LonTalk Adapter PCC-10 PC Card Network Interface SLTA-10 Serial Network Interface (requires separate driver) SmartServer and SmartServer 2.0 U10 USB Network Interfaces U20 USB Network Interfaces Cause Installing Echelon Network Interfaces on computers with newer Windows Operating Systems. OpenLDV 4.0 Resolution Install and use Echelon OpenLDV network interface driver version 4.0 and above. You can download OpenLDV 4.0 from the Echelon website here Echelon Network Interface(s) manuals can be found here. Echelon has released OpenLDV 5.0. It can be downloaded from here. 

Issue The lib-2.301.532.v1.jar file is missing objects that were present in previous builds.  Here is list of those objects: lib\programObjects\hvac\RemainingOverrideTime.sns lib\programObjects\hvac\StartupInhibitor.sns lib\programObjects\hvac\TriStateOutput.sns lib\programObjects\lon\BooleansToMfgNvTypeBits.sns lib\programObjects\lon\BooleansToSnvtStateTypeBits.sns lib\programObjects\lon\FloatToSnvtHvacModeEnum.sns lib\programObjects\lon\MfgNvTypeBitsToBooleans.sns lib\programObjects\lon\SnvtLevDiscEnumTransposition.sns lib\programObjects\lon\SnvtStateTypeBitsToBooleans.sns lib\programObjects\lonHoneywell\XL15AnvoFTStatusDemux.sns lib\programObjects\lonHoneywell\XL15AnvoLogicOutputDemux.sns lib\programObjects\lonHoneywell\XL15AnvoStStpStatusDemux.sns lib\programObjects\miscellaneous\MinMaxAvg.sns lib\programObjects\miscellaneous\NumberRamp.sns lib\programObjects\miscellaneous\PulseGenerator.sns lib\programObjects\miscellaneous\WatchdogTimer.sns lib\programObjects\muxDemux\DateTimeDiscreteComponents.sns lib\programObjects\muxDemux\ExtractTextSegment.sns lib\programObjects\muxDemux\ParseString.sns Environment Niagara R2 version 532 Cause A compiling error with the jar file. Resolution This error has been corrected in a new 'lib' jar file: lib-2.301.533.v1.zip.

Issue 7771 (Modbus ICI) will not keep station address after station restore. Environment I/NET Seven 7771 (Modbus ICI) Cause The cause is the EEPROM rev in that unit. Resolution Update EEPROM to version 3.32 to work correctly in I/NET Seven.

Issue Getting the error message “Can not access controller” when downloading to an MNB-300 controller with WorkPlace Tech 5.7.7. Environment WorkPlace Tech 5.7.7 Cause Corrupt database Resolution   Use backup copy of application or create a new application.

Issue Unable to successfully use Gmail SMTP server to send out alarms via email from I/A Series G3.  Various errors can be seen in the console output. Some of the errors are indicated below but they may not be limited to these. Error: BOutgoingAccount could not dequeue persistent email: 550 The address is not valid java.lang.Exception: Valid CryptoService not found Environment Enterprise Network Server / Enterprise Network Controller I/A Series G3 version 3.5 and above I/A Series G3 maintenance builds version 3.4.55 and above Cause Improper configuration of the EmailService's OutgoingAccount and missing CryptoService in the station. Resolution Procedure and properties settings required when using the Gmail SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.gmail.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@gmail.com Password: Your Gmail account password Enabled: true Use Ssl: true (Gmail requires SSL) Transport: SMTP Use Authentication: true (Gmail requires authentication when sending out emails) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. If you are still having an issue with authentication, it may need to allow less secure apps to access your Gmail account. Refer to https://support.google.com/accounts/answer/6010255?hl=en for details.  Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 (crypto 3.4.64 / crypto 3.5.34) from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue Is it possible to delay the alarm that occurs when OPC Server goes offline? Environment TAC Vista 5.1.X Vista OPC server or client add-on Cause Due to network issues or temporary circumstances a customer may wish to delay this alarm to allow for short breaks in network communication Resolution It is not possible to delay this alarm, but the alarm can be filtered in Vista workstation.

Issue Vista trend log links in reports are not updating after upgrading Vista. Environment Tac Vista 3.2.1 - 5.1.6 Excel 2000 - Excel 2010 Cause Compatibility issues between the different versions of Excel mean that it is not possible to upgrade the Vista version and the Excel version simultaneously. This is especially applicable when upgrading an older system (3.2.X) which runs on an older operating system with an older version of Excel. Resolution Below is a table with a suggested upgrade plan taking into account the introduction of the SQL logdatabase in Vista 4.5.0 and Vista/Excel/OS compatibility: Vista Version Excel Version SQL to Vista version Excel version SQL Comments Upgrade Plan TAC Vista 3.2.1 2000 -   3.2.1 2000 SP1 - Excel upgrade 3.2.1 2000 SP1 -   3.3.3 2000 SP1 - Vista upgrade 3.3.3 2000 SP1 -   4.0.1 2000 SP1 - Vista upgrade 4.0.1 2000 SP1 -   4.2.5 2000 SP1 - Vista upgrade 4.2.5 2000 SP1 -   4.5.0 2000 SP1 MSDE Vista/SQL upgrade 4.5.0 2000 SP1 MSDE   5.0.3 2000 SP1 2005 Vista/SQL upgrade 5.0.3 2000 SP1 2005   5.0.3 2007 2005 Excel upgrade 5.0.3 2007 2005   5.1.6 2007 2005 Vista upgrade

Issue There is an error in the date format in automatically generated reports. Environment Vista 5.1.X Excel Cause The regional settings are incorrect for the account running the TAC Vista service. Resolution Run a report manually and check that the formatting is ok. Check and make a note of  the regional and language settings for the user that is logged in. Check which account is running the TAC Vista service. Change the regional and language settings to those noted in point 2.

Issue On the delivery tab of the EventNotification editor there's a checkbox that says, "Send to all workstations". Why is it grayed out?   Environment CyberStation Cause On the delivery tab of the EventNotification editor there's a checkbox that says, "Send to all workstations". Why is it grayed out?   Resolution This was added to the editor many versions ago, expecting to be implemented. A decision was made to not implement it but it was never removed. One reason for not implementing this was that many large systems have many workstations spread over multiple sites and time zones. This checkbox would make it too easy to cause unwanted alarms sent to too many locations. It was decided that a better idea was to require the programmer to thoughtfully select individual workstations.   

Issue Getting “Lost Sync with system clock - resetting control engine” warnings messages in R2 Enterprise Server? Environment Niagara R2, Enterprise Server, UNC-520, UNC-410 Cause The cause could be any one or a combination of several things listed in the resolution. Resolution The following settings should be verified in both the UNC and Enterprise Server. The following settings are for the Enterprise Server (ES): serverEnabled = true if syncing with UNC. clientEnabled = true if the ES is getting its time from an internet time sync server or site’s server. If not, clientEnabled= false. clientResetTolerance: the default is 30 sec with is too tight. Set it for a minute or more. (Remember to enter value as seconds, not minutes.) timeProtocolServer*: If clientEnabled = True, then all three slots should contain an address of a time sync server. If only one server is being used, then all three slots should be filled in with the one time sync server (same server). No slot should be left blank.   UNCs TimeSyncService settings: serverEnabled = false clientEnabled = true clientResetTolerance: the same would apply as the server timeProtocolServer*: the same would apply as the server reboot the UNC after any changes.

Issue I/A Series R2 (Niagara) Enterprise Server displays "ERROR: Cannot subscribe: Invalid node : (specifies node)". Environment I/A Series R2 (Niagara) Enterprise Server, all versions. Cause These errors are related to invalid subscriptions (swids) typically caused by changing the parent container or object name on the UNC without deleting and recreating the associated external link. The swid name changed but the external link is still referencing the invalid swid.   Resolution Review the links specified in the error message(s) and correct them.

Issue 'Unsupported feature' error when saving a program with the sendemail keyword in PE with Cyberstation 1.74 SP2 on a 9680 or 57xx controller Environment Continuum 1.74 SP2 9680 Netcontroller 5740 Netcontroller 5720 Netcontroller Cause Sendemail feature was added to the 2nd generation of controller, but will not work through a program with 1.74 SP2 Resolution Several feature were added in 1.8x including the sendemail functionality to use to send an email directly with controllers in a program. Upgrade to 1.8x or above.

Issue How many Remote Workstations can connect to a single TAC Vista Server? Product Line TAC Vista Environment TAC Vista Server Remote Workstation Cause Need to know how many remote users can access a single server for project specifications. Resolution There is no limitation number announced by the Schneider. Practically, if too many Remote Workstations connects to the TAC Vista Server, It will slow down the speed of the Server and for sure will get some un-expected errors will occur. And if the TAC Vista Server have many graphics and too many Remote Workstations trying to access the same graphics page all at a time, it should affect the performance. But it will not be a problem with 15-to-20 remote connections when the Server PC have a very good configuration. Note: If the Server PC having a high configuration and using the Windows XP the speed differ with the PC using Windows server 2003 or 2008.

Issue Have (10) i2885-V-WL (Wireless Infinet) which need to be changed to regular RS-485 hard-wired (Infinet). How is this done? Environment CX9680 i2885-V-WL Cause Have (10) i2885-V-WL (Wireless Infinet) which need to be changed to regular RS-485 hard-wired (Infinet). How is this done? Resolution Simply flash any Infinet II –V VAV Controller from a wireless Infinet to a wired Infinet II or even to a wired BACnet or Wireless BACnet –VAV controller in just one step. The –V VAV Series are the first Andover Continuum controllers to allow a change in the controller operating system with a simple firmware upgrade. The hardware model number doesn't change. For example, an 866-V will always be an 866-V, but through software that same 866-V can change in firmware from an i2866-V to a b3866-V-WL with one upgrade in the field. Also, the i2 -V controller firmware type can be identified using two onboard LEDs (i.e. wired vs. wireless, BACnet vs. Infinet). Notes: The Roam-IO2 cannot be used to flash a wireless controller to a wired one. The Roam-IO2 cannot communicate to a wireless controller. Non -V controllers should not be flashed in the field. Trying to do this runs the risk of turning the controller into a brick.  To flash non-V controllers, send them to repair.

Issue If a database is downloaded to the controller after the box has been balance will it lose the balance data? Product Line TAC IA Series Environment All versions of MNB VAV controllers MNB-V1 MNB-V2 Cause In MNB VAV controllers the flow balance data is preserved in a different area of EEPROM than the application data. Resolution Balance data in an MNB VAV controller is not affected by the downloading of its database.

Issue A CX9200 running Continuum v1.500030 will not upgrade the node count from 64 to 127. Environment CX92000 Xdriver, Webserver Cause A CX9200 running Continuum v1.500030 will not upgrade the node count from 64 to 127. Resolution CX9200 boards were manufactured before UPD flash files were used to upgrade the options set in EEPROM (like the node count). The CX9200 options are upgraded by loading a serial DMP file (available through Repair) and then resetting the controller. In this particular case, the controller would appear to accept the dump file with no error, but the node count did not change. The issue was resolved by upgrading the firmware chips to version 1.52 or later, and then loading the dump file from the Repair Dept. To avoid paying for a firmware upgrade just to increase the node count, the workaround is: Temporarily install v1.52 firmware chips Do the upgrade with the DMP file Reinstall the old chips Note: A similar thing is true if looking to add the Webserver option to a CX9200. If you have Continuum v1.52 chips installed, then you can get a dump file from the Repair Department to add the webserver option. If the board is older than v1.52 you will need to send the board into Repair for them to make the change.

Issue Process to use I/NET Encryption feature to encrypt an existing network or segment of network Environment I/NET Cause I/NET system contains or protects items that need addition security or separation from other I/NET networks. Resolution To encrypt the Xenta 527 and Host network   Important: ********** The Unencrypted and Encrypted UDP ports should be different from each other     (Ex. Unencrypted: 50069, Encrypted: 49152) ********** The Unencrypted UDP port for all routers and workstations should be the same (Ex. Routers: 50069, Workstations: 50069) ********** The Encrypted UDP port for all routers and workstations should be the same (Ex. Routers: 49152, Workstations: 49152) ********** The Encrypted password for all routers and workstations should be the same (Ex. Routers: Test, Workstations: Test)   Choose an unencrypted UDP port, either default 50069 or a number between 49153-65535 Set the workstation Advanced IP UDP setting to the chosen unencrypted port Shutdown I/NET, Shutdown I/O Server(make sure I/O server is shut down) <-check Task Manager to see if all I/NET services are shutdown Bring all new 527 routers online within the network Log into the 527 web interface, go to I/NET configuration profile Set 527 UDP to the chosen unencrypted port you chose in step 1, set the host reference to the workstation IP that is the filemaster/standalone Save and Restart 527, restart I/NET Filemaster/Standalone Bring up NP routers under I/O server, check if all routers in the network have appeared in the list If not all routers have appeared in the list check the unencrypted udp port of the workstation and 527 udp port match Once all routers have appeared in the online list, click on each router and modify its Advanced IP settings Check mark the Enable Encryption box, the default encryption port is 49152, make sure you leave the encryption port default or choose an encryption port that will be the same for all routers Enter a password for encryption(Ex. Test), make sure the password is the same password for each router Click OK, the router should restart with the new encrypted settings Repeat steps 10-13 on all routers within the list All routers should disappear one by one from the Online list as you enable encryption on each router and OK the settings change Under the main IO configuration screen click on Advanced IP Check mark the Enable Encryption box, the default encryption port is 49152 or choose the encryption port that corresponds to the same exact encryption port you choose for the routers Enter in the password for encryption exactly as was done for the routers Click OK, Click OK on the main screen to save the settings Shut down I/NET, Restart I/O Server(make sure I/O server is shut down) Restart I/NET Open up IO configuration once logged in Click on NP Routers The routers you have encrypted should appear back onto the Online list Troubleshoot: If the routers you have do not appear back onto the list, check each router’s web interface and make sure that the UDP port is set to the encrypted port. If the routers come back but there Name appears as numbers (Ex. 1023,1124) then what happened is the routers are encrypted but the host workstation cannot understand the encryption. To undo everything and start over uncheck encryption on the host workstation and then login to each of the router’s web interface and reset the UDP port to the default I/NET port. Make sure to restart I/O server to make changes take affect. Test the encryption by having standalone machines and other filemasters not on the same encrypted port try to pull up the routers either by NP routers in IO configuration or Host->Netcon, they should not be able to see any of the routers/host workstations that were encrypted.     To add a 527 to an existing encrypted network   Bring the router online on the chosen unencrypted port Shutdown I/NET and I/O server Modify IO configuration Uncheck enable encryption on host settings Advanced IP Make sure the unencrypted port is the same port with the router you are bringing online Shutdown I/NET and I/O server and then restart I/NET Modify the active IO configuration, under NP routers you should be able to see the new router but none of the old encrypted routers Modify the new router’s Advanced IP settings Enable encryption on the new router and assign it the default/chosen encrypted port and enter in the chosen password for encryption Click OK, the router should restart with the new encrypted settings Edit the Advanced IP of the host workstation Recheck enable encryption and reenter the default/chosen encrypted port Reenter the chosen encrypted password Click Ok to confirm settings Shutdown I/NET and I/O server then restart I/NET Modify the active IO configuration, go to NP routers All routers should appear on the list now, the existing encrypted routers on the network and the new encrypted router on the network

Issue A project calls for an ETR503-LCD which I can purchase though the Schneider Electric iPortal. Is this a programmable smart sensor? Environment Continuum field controllers ETR500 ETR501 ETR502 ETR503 LCD ETR Cause A project calls for an ETR503-LCD which I can purchase though the Schneider Electric iPortal. Is this a programmable smart sensor? Resolution The ETR503-LCD is not a programmable "smart" sensor. It's a wall-mounted 10K thermistor sensor with an override pushbutton and setpoint slider. These points can be programmed as inputs and Plain English can be used to perform control or alarming but the LCD is fixed function - just displays the temperature. There are no terminals or jack for extending the RS-485 network for a field service tool. The data sheet  and manuals can be found on the iPortal website. https://iportal2.schneider-electric.com/

Issue Cannot ping the MNB-1000 to test network connectivity.  Looking for an alternative method of network diagnostics, possibly by use of the second Ethernet port on the MNB-1000. Environment MNB-1000 (firmware 1.510 and later) Also can be used, but not required, with earlier firmware versions. Cause All Ethernet functions except for BACnet UDP messaging and router management functions has been disabled in the MNB-1000 firmware versions 1.510 and newer.  This prevents the use of Ethernet ICMP messaging (PING command, etc.) for diagnosing the Ethernet connection to the MNB-1000 controller. Resolution A computer can be plugged into the second (lower) Ethernet port on the MNB-1000 to allow network troubleshooting, device configuration and programming.  Plugging in a computer into the second port and assigning it an address on the same subnet as the MNB-1000, you can then ping other devices on the network to verify outgoing network connectivity.  Since the ICMP messaging has been disabled in the MNB-1000 itself, you can also ping the computer on port 2 from other computers on the Ethernet network to verify incoming connectivity.  NOTE: When performing troubleshooting in this manner, you need to remember that the MNB-1000 itself still will not respond to PING commands but will pass the ping commands and all other Ethernet or IP messages through to the second ethernet port.