Building Automation Knowledge Base

Issue Executing a Project Builder File should launch Visio and open a drawing. Instead, Visio opens but stops short of the file opening. Environment Project Builder Visio Cause Project Builder is disabled in Visio. Resolution In Visio go to Help>About Microsoft Visio Click on Disabled Items button in the pop up. Ensure Project Builder is not listed If so, select the Project Builder Listing Click the Enable button. Restart Visio.

Issue Support for Finger Print readers. Environment Windows X Continuum 1.9X Cause Bioscript readers are offered and supported by: Security Center of Excellence Resolution Continuum Integration software for specific Bioscript and Cogent biometric readers are offered and supported by the Security Center of Excellence:   COE@Buildings.Schneider-Electric.com

Issue Receiving Large Incorrect numbers in the log viewer. Environment Continuum 1.9X Windows XP Netcontroller II 9680 Cause NetController II needs updates. Resolution Go to: The Exchange Download the latest  NetController II  Flash. Edit the controller. Update OS Reload the controller.

Issue When adding a physical layer Xenta repeater, or Loytec smart-switch, to split a single channel into multiple segments, there is no need to represent that repeater/smart-switch in the LON network.  It will be invisible to the LNS database, and will function only on the physical layer. Environment LON Network with more than 64 devices on a single segment Xenta Repeater, Loytec Smart-Switch Cause A single LON segment can have up to 64 devices (though a conservative recommendation is typically closer to 50).  A segment is a single LON wire that is separated from another segment either by a physical layer repeater, smart-switch, or router.  A channel can have up to 3 segments separated by a repeater with a limitation of 128 devices (or nodes) total on the channel. Resolution There is no need to represent a physical layer repeater/smart-switch on the LON drawing or in the LNS network.  It will be operating on the physical layer either amplifying signals or filtering noise and bad data, and repeating messages on the wire.  The LON network will only see a single channel without any indication that there are 2 segments, other than the fact that there may be more than 64 devices on that channel.

Issue Each time the PC starts the below prompt indicating that the license server manager could not determine where to find the licensing data it needs.  This has to be manually re-entered on each restart of the computer. Environment Vista 5 Windows XP Cause Security settings or policies on the workstation are not allowing the registry setting to be saved or are been overridden during start up. Resolution Security settings or policies on the workstation must allow this setting to function or not be overridden. For information, the registry setting is located in the following registry key. "HKEY_LOCAL_MACHINE - FLEXlm License Manager - TACLIC_LICENSE_FILE" key.

Issue How many global objects can be used in a Sigma controller or IC? Environment X96 controllers X32 controllers Integration controllers - All types Cause Configuration and engineering issue. Resolution A controller or IC can have a maximum of 50 received globals. There are no such restrictions on the number of globals a controller can transmit, but when engineering a Sigma system, additional communications and loading on the controller must be taken into account.

Issue Temporary day cards set between 9:00am and 6:00pm, are not disabling until the next day or until the controller has been reloaded Environment All windows versions I/NET Seven version 2.15 or below Cause This was an issue with the I/NET software not synchronizing with the controllers in real time after updates where made to the controllers and personnel. Resolution Upgrade to version 2.16 or above as this was fixed in hot fix 2.15b

Issue Customer gets the error "Denied Entry SEL" when they swipe any of their cards Environment All windows Versions All I/NET Seven Versions Cause This is due to Time Schedules not present in I/NET Resolution Create Time Schedules for the doors. In the 7920 (Mipped) 48 K boards and SCU door controllers, put in a door schedule from 00:00 to 23:59 so it is 24 hours. If a Secondary Schedule is set up for an individual on doors that are controlled by a 7920 DPU that use the standard EPROM chip, a “Deny Entry Select Message” will be generated in the Transactions. If 7910s are present then the same above rule applies.

Issue When working with numbers that are 7 digits or longer the number is displayed in exponential format and there is a loss resolution in the lower digits that can cause an issue with metering applications. This can be an issue when using pulse counter inputs. Product Line Andover Continuum Environment All Continuum controllers and modules that support Pulse counting with Counter inputs Cause The number formatting throughout the Continuum product is 32 bit IEEE Floating point notation, for numbers up to 7 digits long they will be displayed as a regular decimal number, for larger numbers they will be displayed in exponential format: Significant digits × base exponent This allows Continuum to work with huge numbers like 123.45 x 10 67 but has the disadvantage that as the numbers get larger there will be a loss of resolution in the lower digits starting with the units. Resolution When working with pulsed inputs from meters try to keep the size of the numbers down, putting scaling factors of x10 and x100 only makes the numbers bigger, so where possible scale the numbers down and upscale the units. For example when scaling an input where you would enter a conversion of: Value+(ElecValue * 10) Instead use: Value+(ElecValue*0.1) and change the units to Kilo Units, Mega Units etc. If you have to measure large pulsed numbers another option is to split the large numbers across 2 Numerics, so in Plain English when a value gets to 999,999 then add 1 more pulse, you get 1 in the upper number and 0 the lower number. This can then be displayed on a graphic with 2 adjacent text boxes. Where very accurate metering is required the best solution is to use meters with an intelligent data interface that supports one of the common open protocols supported by Continuum (i.e. BACnet MS/TP, Modbus or M-Bus via X Drivers). This solution means there is no chance of missing a pulse or Continuum getting out of sync' with the meter. Note: If you need to set the lower number back to zero, then the object first needs to be disabled. If this is a BACnet bCX then the BACnet name (eg BACnetDevices\bCX25\Counter2) needs to be used within the PE Program

Issue I/O-modules go offline After adding more than 16 I/O modules, some I/O modules start going offline Only 16 out of 20 I/O modules comes online Environment TAC Vista TAC Xenta 700 Server TAC Xenta I/O modules Cause In TAC Vista 5.1.0 and earlier, the default value for Receive Timer is set to 24576 milli seconds. That is too long time if you want to keep 20 I/O-modules online (the Xenta 700 device does not answer some of the I/O-modules). TAC Vista 5.1.1 and newer have the receive timer set to 2048 by default, though this only applies to new installations (i.e. if you upgrade it will keep the old value) . Resolution Open the properties window of the Lonworks network Change the receive timer to 2048 ms.  All the I/O modules should now come online. If not, lower the receive timer one step, though not less than to 768 ms.

Issue Cisco switches reporting connected Sigma devices using more than one MAC Address which appear to be transmitted from the Sigma device connected to the port.  The error alarm reported "%PORT_SECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address 0050.b401.1e46 on port FastEthernet1/0/35" Environment All ARM7 Sigma Ethernet devices Cisco Catalyst 3550 Series Switches Cisco Catalyst 3560 Series Switches Cisco Catalyst 3560-E Series Switches Cisco Catalyst 3750-E Series Switches   Cause Sigma controllers broadcasting high number of Sigma globals (typically 40 per second). Upgrading BAS2800+ systems to Sigma can result in higher levels of Sigma global data than seen previously. Cisco switch set to 10Mb half duplex which mistakes the source MAC address of the Sigma global from a controller on one port with that of a controller on another port. Cisco switch has Layer 2 Security feature enabled, see Click Here High collision rates may also be seen at the switch. Resolution Identify those Sigma objects that are broadcasting global data at high rates and suppress the rate of change of the Sigma object. This can be achieved by: Running Wire Shark Ethernet trace program to record the Sigma broadcast Ethernet packs per Ethernet sub-LAN. Email each of the saved capture files (per LAN) to your local product support for a global analysis report. If possible then increase the connection speed of the Cisco ports. New firmware for the ARM processors has been created to addresses the issue. You can find the firmware and release note on the Exchange

Issue A Controller with X Driver support has been loaded up with the M-Bus (or M Bus) X Driver and connected to a M-Bus to RS-232 converter (i.e. Westermo AD-01) but is not getting data from the M-Bus meter. Note: This is M-Bus (Meter Bus) and not Modbus which is a different protocol Environment bCX1 and Netcontroller II 2nd Generation controllers with X Driver port enabled MBus, M Bus, XDriver, X-Driver Cause Incorrect comm port settings for the M-Bus interface will stop correct communications to the M-Bus meters. Resolution DefaultMode = Xdriver Baud = Baud300 Parity = Even Stopbits   = StopBit1 Datalength = Databits8 Connect up and configure the system as detailed in the M-Bus manual as supplied (downloaded) with the M-Bus X Driver software. Unless specified otherwise in the manual for the specific 3rd party meter being used, set up the Comm port on the Controller with the above parameters: These settings should be entered and verified through the Command line, then printed back to verify they have been accepted.

Issue Network Security and transport types. Environment CyberStation CX9680 ACX5740 ACX5720 Cause Can not set up network security when the transport type is configured for TCP. Resolution Network security is only supported with UDP transport type.

Issue Is there a limit to the number of read/writes available for a BACnet Setpoint object? Environment WorkPlace Tech versions 5.1 and later Cause Not applicable Resolution The BACnet Setpoint object (analog or binary) is used for writing setpoint values to a controller, where it is stored in EEPROM. Observe normal precautions to avoid frequent writes to EEPROM. Excessive writes (typically greater than 100,000) can greatly shorten the life of the EEPROM and adversely affect its reliability. The BACnet Setpoint Priority object (analog or binary) represents a Value BACnet object type, of which the data is read-write accessible. This object can be used to write data to the controller. The Setpoint Priority object provides access to temporarily stored application values, usually setpoints or setup values, that are stored in RAM.  These setpoint values can be monitored and changed via BACnet communications, using the BACnet priority array.  When written from WP Tech, the default value is written to the priority array “relinquish default” location. Only this default value is stored in EEPROM. For more information, refer to the WorkPlace Tech Tool Engineering Guide Supplement (F-27356)

Issue How many additional workstations can connect to a Continuum standalone system? Environment SA CyberStation MSDE Cause Using Continuum stand alone installation as a database server for additional workstations. Resolution Stand Alone key is for 1 Cyber. MSDE supports up to 3 users, but a LAN key is needed with more than 1 Cyberstation. To upgrade SA to LAN, the Stand Alone key must be upgraded with a cookie. The Stand Alone machine with the database should have the SA key, up to two additional machines can use the Stand Alone machine as their database server. The additional machines need LAN keys.

Issue Unable to reload entire database using "Send to Controller" option. The error "Not enough memory" is seen in Distribution View when trying to reload some objects. Product Line Andover Continuum Environment Continuum b3 Series Controllers i2 Series Controllers Cause Data is corrupt in controller Database or individual points such as Infinity Programs have become corrupt and are unable to be reloaded to the controller. Resolution Clear the database in the controller and retry a "Send to Controller" as follows: Open the Device object of the i2 or b3 controller. Go to the "Runtime" tab. Press the "Reset" button to reset the controller and clear its memory. Retry "Send to Controller".

Issue There used to be an Inovonics wireless sensor solution available in our product catalog but this is no longer available. Is there another solution available? Environment All Controllers Inovonics Cause Inovonics devices are no longer distributed, and are only available through third party sales channels. Resolution Unfortunately, we no longer provide these sensors through our distribution channels.  Inovonics and other third party wireless devices are available through external distribution channels only.

Issue Graphics points appear OK, but are not dynamically updating. Alarms and messages appear in the AMT. Double clicking on a point on the graphics, the displayed value is significantly different to what is displayed on the graphics page. Graphics have question marks for the data. Rebooting the PC makes data viewable again on the graphics. This happens regularly over time. Product Line TAC INET Environment I/NET Seven 2.15B through to 2.30 Cause Changes in Microsoft Windows video/graphic files have meant changes were required to the I/NET Seven Software.   Resolution Upgrade your I/NET Seven system to 2.31 or above.

Issue How do I reset the view of the System Plug-In  to the original look. Environment System Plug-In Cause They folder pane has been modified and now the default layout is required. Resolution A reset to default will be required to get the original settings These steps will reset the view to default Open the System Plug-In Under the file menu select Default Settings A message will appear that "The command requires a restart to take effect." Shut down the System Plug-In Restart the System Plug-In  with the original default setting is applied

Issue Upgrading SQL server whilst Vista is running Environment Upgrading from SQL 2000 express -->  SQL 2005 express Upgrading from SQL 2005 express -->  SQL 2008 express Any other upgrade eg. express to full version. Cause Issues may arise if trying to upgrade the SQL log database whilst Vista is running. Resolution 1.Turn TAC DSS writer off a. Click on Start\Settings\Control panel\Administrative Tools\Services. b. Locate the TAC DSS Writer Service and right-click on it. c. Select "Stop". The service will be stopped. 2.Upgrade the SQL Database 3.Turn TAC DSS Writer on a. In the services console opened in step 1 right-click on the TAC DSS Writer Service and select start. Whilst SQL is being upgraded, the events and logs will be written to the $Queues\insertevents and $Queues\insertlogvalues folders. Once the upgrade is complete and DSS writer is running again the $Queues folders will be emptied and all values will be logged to SQL.