Building Automation Knowledge Base

Issue 1. The Sigma default user name TAC USER does not work with Sigma 4.05 SEB 2. Tried the user access password and could not logon Environment Sigma 4.05 SEB Cause The default user name changed at Sigma 4.05 SEB Resolution From Sigma 4.05 SEB onwards the default user name is SIGMA USER. The password remains unchanged.

Issue Is the I/A Series (Niagara) R2 WorkPlace Pro and Enterprise Server software compatible with the Microsoft Windows 7 operating system? Product Line TAC IA Series Environment I/A Series (Niagara) R2 software, any version (See specific version note in Resolution section) Microsoft Windows 7, all editions, 32-bit or 64-bit (See specific version note in Resolution section) Cause PCs upgraded to Windows 7 operating system. Resolution The I/A Series (Niagara) R2 software has not been certified for use with the Microsoft Windows 7 operating system. The I/A Series (Niagara) R2 releases 529 and 532 has been informally tested on the Microsoft Windows 7 Professional (32-bit) operating system, Windows 7 Professional (32-bit) XP-Mode and Windows 7 Professional (64-bit) XP-Mode.  No issues have been reported with the exception of R2 Niagara Application Tunneling.  The R2 Niagara Application Tunneling must be configured to run in "Silent Mode" when run in any Windows 7 environment.

Issue Loytec (LTA, lon port) offline in TAC Vista when running TACOS as a service Environment TAC Vista running as Service Loytec NIC device Lconfig/NIC legacy driver Cause For TAC Vista to use the legacy driver, it must be running before Vista starts. When running TACOS as a service, by default, it will start prior to the legacy driver and the LTA port will show offline. For this reason, the legacy driver must also run as a service.  Dependencies on the Vista Server service must also be configured to ensure that the legacy drivers starts first. Resolution First make sure that the legacy driver is set up to run as a service Open Lconfig and click on advanced. Select "run as service" and click ok.   Reboot computer From the  start menu, select run, and type regedit Go to  HKEY_LOCAL_MACHIN\SYSTEM\ControlSet001\Services\TACOS\ Double click on depend on service Type in LoytecSrv on a new line.   Reboot computer.

Issue Availability of IPSEC on older controllers which request higher security constraints on networksLAN sites which have Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which has IPSEC enabled. Environment Network of IP level controllers communicating with Cyberstation Cause Higher Security constraints on networksLAN sites which has Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which have IPSEC enabled. Resolution Older versions of Andover Continuum controllers do not support network security such as IPSEC. However, the new versions of CyberStation and the new controllers, such as NetController II 9680 and ACX57x0, can be configured to communicate with controllers that do not support network security.   Another point to take note of is whether or not your site has purchased the network security option for this NetController II 9680 or ACX 57x0 controller.   IPsec is an end-to-end security scheme operating in the Internet Layer of the Internet Protocol Suite. It can be used in protecting data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-network), or between a security gateway and a host (network-to-host).   Network Security Configuration Guide (zip)

Issue Not generally available Product Line Field Devices Environment I/A series Field device Cause Information not provided with the documentation supplied. Resolution The STR800 Series User manual can be downloaded by selecting this link. The STR800 Temperature Sensor RoHS Certificate can be downloaded by selecting this link. The STR800 Wall Module Specification Sheet can be downloaded by selecting this link. Other STR800 documentation is available on the Schneider Download Center.

Issue Polling data from one Xenta Server to another can be accomplished over IP by importing XBuilder Projects. This will only bring over data points that reside in the Network Pane of the XBuilder Project.  If points are being calculated in a Menta object, for example, they would not be available following an import. Product Line TAC Vista Environment XBuilder Xenta Server 701, 711, 721, 731 Fixing Write Over IP Cause Importing another projects network brings over only data points that reside in the Network Pane of the XBuilder Project. In order to avoid a write over IP situation, data from the System pane sometimes needs to be browsed into the other controller's project. Resolution Expand the Network pane beneath the Xenta 700 and find the Variables folder. Right click on the Variables folder and select New Variable (if desired, choose New Folder to organize the points that need to be sent over IP). Create a variable for each point that needs to be imported into the receiving Xenta Server. Drag and drop Variables onto the Menta object outputs to associate them   Note: Only Menta object Outputs allow for this drag-and-drop functionality.  If they are public signals, then either: Add an RO, IO, BO point on the output of the signal Use a connection object in XBuilder to transfer the value to the Network Pane variable. In the receiving controller's XBuilder project, right-click on the IP Backbone and select New > Other Projects Network.  Now the Menta object variables are available.

Issue After the user have logged in to TAC Vista Workstation it hangs and the only option is to close it Product Line TAC Vista Environment TAC Vista Workstation 5.x.x Cause When users log in to TAC Vista workstation all events specified in the Event viewer window is retrieved. If too many events are retrieved to Vista Workstation it can cause Vista workstation to hang. Resolution Under the TAC Vista server object open properties for $Eventview Open the "Date and Time" tab and specify a shorter time period. Click OK

Issue What is a quick way to determine the IP address of a MNB-1000 that is integrated to a Niagara R2 station?  Assume only Workplace Pro is available (Workplace Commissioning Tool is not available). Environment MNB-1000 Niagara R2 UNC-410 and UNC-520 Cause None Resolution The IP address is stored in hexa-decimal format within the properties of the controller's shadow object.  A unit-conversion calculator is required to determine the IP address in decimal format (the Windows calculator can do this task). To find the IP address, Locate the shadow object of the MNB-1000 Go to its Properties, Config tab Record the first 8 digits of the hexa-decimal number displayed at the "address - MAC Address" parameter.  The last four digits are the UDP Port number and are not part of the IP address Convert to decimal Example,     C0 = 192,  A8 = 168, 01 = 1, 96 = 150 BA:C0 = 47808 (UDP Port Number) MNB-1000 IP address is 192.168.1.150

Issue When a valid card is presented at a reader connected to an AC1 module, the reader’s LED will blink green for a fraction of a second then go solid red. Environment AC1 AC1Plus CX9702 ACX5740/20 ACX701 ACX781 Cause Incorrect wiring of card reader LED line. Resolution If card reader has two led lines make sure the right one is wired to the AC1/Controller. Typically when the undesired LED behavior is observed, swapping the LED line takes care of the problem.

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 When setting up Continuum Security levels is there an easy way to set up the different Security Groups? Sites that have upgraded from Infinity SX8000 may require the same security settings. Environment Cyberstation all versions. Cause It can be time consuming and complex setting up multiple user security levels. Resolution In the Workstation you can edit the Security settings to define the access (keys) and blocking (padlocks) for each group against each object class. You can also import/ export these security settings with *.SDF files, attached is a file Default Security V1.sdf that defines a default set of 8 security levels as per the Infinity SX8000: Click here for default security file Administrate Program Configure Enable/Disable Change Values Acknowledge Alarms View Only No Access Click here for a description of each of the above levels (Source: SX8000 Programmer's Guide). To add the "Default Security V1.sdf" file to your Continuum you will need to do as follows, in the bottom right hand corner of your screen there is the Continuum icon, right click on the icon and select Security... then under the Actions tab, right click next to "Access Distribution View" and click import All... then all you do is select the "Default Security V1.sdf" file you have already downloaded and then click open, this will now install the new default security options. Warning! Always make a database backup before attempting to change the security setting so that if a mistake is made you can always revert back to the backup.

Issue Continuum operation unacceptably slow. Product Line Andover Continuum Environment CyberStation All CXs, i2s and b3s Cause Wireshark capture shows lots of SMB traffic between the machine running CyberStation and the server. The Server Message Block (SMB) protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. Resolution Identify the application/service responsible for generating this traffic and stop it or relocate it to a different machine where it will not interfere with CyberStation operation.

Issue How to set-up the Sigma images on a Sigma server so they can be downloaded from a Sigma client Environment Sigma Images Firmware System Diagnostics Cause Image download is carried out via the Sigma System Diagnostics, but the images must be manually loaded on to the Sigma server first. Resolution   1. Download new Sigma controller images from The Exchange. 2. Copy the image file to the Sigma server C:\Sigma\Image location 3. Open the Sigma client System Diagnostics.    4. Select 'Node' and device number 5 Select Options - Download Files or (F6) 6. Select the new image file to download to the device (Note: Need to identify the controller type V53 or ARM7 before selecting filename as you can't mix the image and controller types)   To check the image file is being downloaded, on the Sigma server service icon select 'Toggle Debug (on/off)' and see if the transfer is going.      

Issue As of December 2010, Microsoft® Windows XP is no longer available, preinstalled on new computers. Is there a valid, legal and legitimate workaround for running our software products that will not run on Microsoft® Windows 7? Environment New computer that was purchased pre-loaded with Microsoft® Windows 7 Professional or Microsoft® Windows 7 Ultimate I/A Series software that runs only on Microsoft® Windows XP such as: I/A Series (Niagara) R2 - all releases I/A Series (Niagara) G3 - all releases prior to 3.6.x  Signal XP WorkPlace Tech Tool 3.2sp1 Cause Microsoft® Windows XP is no longer available on new computers. Resolution Downgrade the Microsoft® Windows 7 Professional / Ultimate installation to Microsoft® Windows XP. According to the Microsoft® Windows 7 Professional / Ultimate EULA (End User License Agreement) that the computer user must read when starting up a new computer, the following Operating System downgrade rights are available: Downgrade rights for Windows 7 are an end-user right, documented in the Software License Terms that customers accept upon first running Windows software. Windows 7 end user downgrade rights will be available through the sales lifecycle of Windows 7 which is up to two years after the launch date of a new version.  UPDATE:  As of November 2012, Microsoft has upgraded their Windows Lifecycle information, indicating that this upgrade right expires in February, 2014. More information is available from the Microsoft Windows web site and from the attached document.

Issue The Sigma IC3-Modbus reports that the Modbus devices are offline. Product Line Satchwell Sigma Environment Sigma IC3 Modbus IC Modbus Cause Communications with the Modbus devices has failed, or cannot be achieved. Resolution Testing of the IC3-Modbus must be carried out in a systematic way; the points listed below are only as a general guide: Confirm that the communications type, (2-wire or 4-wire) is correct for all devices connected to the Modbus 485 communications LAN. The IC3-Modbus only uses a 2-wire RS 485 LAN configuration. Ensure that the communications LAN to the Modbus devices is correctly connected. Confirm that the overall LAN length does not exceed the RS 485 maximum of 1200M. Ensure that the cable has been installed maintaining the 300mm segregation from other electrical services. Ensure that the communications cable is a Belden 8762 or similar, and that the cable screening is connected to a good earth at one end only. The other end of the screen should be isolated. (Note: In instances where high frequency noise is present, a 1uF filter can be connected between the isolated screen end and a good earth). Configure the Gateway.txt file, ensuring that the comms parameters match those of the Modbus devices. Add one object for the Modbus device nearest to the IC3-Modbus. Download the Gateway.txt to the IC3-Modbus and then warm-start it. Observe the IC3-Modbus RS 485 communications TXD/RXD LED's and confirm that the TXD is seen to flash on a regular basis. This will indicate that the Gateway.txt file is configured correctly. If the TXD and RXD LED's flash alternatively, then this suggests that normal communications is taking place. If the TXD LED does not flash, then this indicates a problem with Gateway.txt file configuration, and it will be necessary to check the "Low level Alarms" on the Sigma Default/Backup server for more information about the problem. If the TXD LED is seen to flash on a regular basis, but the RXD does not, then there are four possible conclusions: The communications cable between the two points is not continuous, or the cores are crossed. The Modbus device number does not match that set in the Gateway.txt. The register being requested is not a valid register. The Modbus device is faulty. Testing a Modbus device using a Modbus simulator. Download a Modbus simulator, there are several freeware/shareware products available on the internet. Using an RS232/RS485 converter connect directly from the PC/Laptop to the Modbus device. Review the appropriate registers to confirm if the device is working correctly. Testing that the IC3-Modbus is sending appropriate Modbus messages. Using an RS232/RS485 converter, connect from the PC/Laptop to the IC3 Modbus in parallel with the existing Modbus RS485 comms. Start PocketTerminal32.exe, select “Setup/Communication Ports” and set the comms port to match the Modbus parameters, then select “Display” and select to "Display Hex".     The trace programme will display blocks of Hex, as shown below. The message shown below is addressed to Modbus device 11 (Decimal 17), it uses function code 3, the register address is 66 (Decimal 96), only this address is required, and the message has an error check. The message will be shown as 110300660001992BFD which can be split into sections. If the controller replies, the complete Request and Reply will appear as: 110300660001992BFD110302142B3698 Request = 110300660001992BFD Reply = 110302142B3698 Again this message can be split up. 11 = controller address, 03 = Function code, 02 = Number of bytes of data, 142B = Data, and 3698 = Error check. To download a copy of PocketTerminal32.exe please Click Here.

Issue How to Retrieve Log values from TAC Vista MSSQL Database Environment TAC Vista and MSSQL Database Cause Requires third party access to retrieve Log Values from TAC Vista MSSQL Database Resolution 1. Refer to the attached PDF document for the procedure 2. Note: You’re limited to retrieve only one log object at a time

Issue What file formats can be used in Pinpoint? Environment Continuum Pinpoint Cause There are many image file formats available so there is a need to know which ones are supported in Pinpoint Resolution 1. Proprietary Pinpoint Files .pin    Proprietary file format for pinpoint graphic files .bck   Proprietary backup files for graphics panels 2. Image Files .jpg    Joint Photographic Experts group created this file standard .bmp  Bitmap image file .ico    Image file for icons in Microsoft Windows .emf  Enhanced metafile, 32-bit version of the 16-bit WMF (Windows Metafile) format .dib   Device independent bitmap file .html hypertext markup language files used for web browser controls 3. Video Files .avi    Audio video interleave is a multimedia container format .mov  An Apple QuickTime media container format .mpg  An audio video file format know as MPEG designed to compress video and audio (MP3) Pinpoint comes with a number of backgrounds and image files. Adobe Illustrator and other image file software programs can be used to create additional files in the above formats which can be used in Pinpoint.

Issue How to convert earlier versions of Microzone II PSI files to 3.3 revision or later Environment Network 8000 Microzone II, PSI/XPSI Revision(S) 3.13 and 4.1 Cause Error Not a valid application file!  File is not compatible with existing XPSI revision.  It must be upgraded with Zconvert.exe Resolution Procedure on how to convert Microzone II files to revision 3.3 or later and read me file.

Issue What version of Datacard ID Works Software integrates correctly with I/NET Seven? Environment I/NET Seven Datacard ID Works Cause Usually the customer wants to integrate the Access Control of I/NET Seven with Video Badging software. He is faced with what version is the correct one for this purpose. Resolution The ID Works Standard Version is the product you should choose for this integration. However, there are two different options in this Standard version: The “Full” Version - ID Works 6.5 with the designer option included With this version, badge templates can be modified and badges can be printed. This version will integrate into an I/NET Seven system. (Please Note that you cannot order Datacard thru Iportal anymore) You have to order thru Datacard.   The “Production” Version - ID Works without the designer option This version will not allow you to change any of the badge templates. It only allows for printing of badges. This version will integrate into an I/NET Seven system. (Please Note that you cannot order Datacard thru Iportal anymore) You have to order thru Datacard.  

Issue There are no existing objects in Niagara G3 that can split a 16-bit Modbus register into two 8-bit values with one representing the high byte (bits 8-15) and another the low byte (bits 0-7). Environment Niagara G3 all versions Cause Modbus integration of a 3rd-party product using 16-bit values which must be split into two 8-bit values. Resolution A program object is available below that will achieve this requirement.  The output of this object generates two 8-bit integer values and two string values for use with logic programming and display purposes.  Text file of program code

Issue ACX57xx supported communication channels  Environment CyberStation ACX5740 ACX5720 Cause Not known cause Resolution The ACX5740 and ACX5720 are ethernet devices only and can not be placed on the Infinet field bus.