Label: TAC IA Series - Building Automation Knowledge Base - Communities

Issue Customer wants to archive the BACnet controller backup images created through the Backup function of the WorkPlace Commissioning Tool. Environment WorkPlace Tech Tool software version 5.7.x or newer Windows XP Professional or Windows 7 Professional Cause The actual location of the Backup folder has changed between Windows XP and Windows 7 Resolution If the computer operating system is Windows XP, the specified backup project folder is in the following location: c:\Documents and Settings\All Users\Application Data\WorkPlace Tech\Backups If the computer operating system is Windows 7, the specified backup project folder is in the following location: c:\ProgramData\WorkPlace Tech\Backups Further information on the contents of the backup project folder can be found in the Release Notes documentation for WorkPlace Tech Tool 5.7.2, F-27526-2, pages 10-13.  Please note that the full file path shown in this document is based on the use of the Windows XP operating system.

Issue The FDA requires Building Automation systems to meet their standards which are outlined in Chapter 21 CFR and FDA Part 11. Environment Vista I/NET Andover Continuum TAC I/A-series Satchwell Sigma Cause Finding documentation on Schneider Electric Building Automation Systems which comply to The Food and Drug Administration rules. Resolution Vista 21CFRPart11 support in TAC Vista 5.pdf FL-VISTA-REGIND-A4 mod RO.pdf I/NET - currently unavailable Andover Continuum With the addition of the 21 CFR Part 11 compliance pack, Continuum can meets these requirements. Satchwell Sigma SoftwareOverview.pdf Advanced Security Module.pdf Note: Validation to 21CFR Part 11 can only be performed on whole operational systems and as such, a sub-system comprising the Satchwell Sigma building management system cannot be validated in it own right. Satchwell Sigma would normally be validated as part of a whole operational system. TAC I/A Series - currently unavailable

Issue The issue occurs when the instance Number is changed.  After the instance number is changed the MNB-1000 will look normal in the current WorkPlace Commissioning Tool (WPCT) session, but the next time WPCT is opened the MNB-1000 will either be unable to be found or the controller icon will be displayed as a gray rectangle with a question mark in it.   Selecting Extended Data will cause a loss of communications with the controller as signified by red exclamation point (!). Environment Any MNB-1000 with 1.510 firmware Cause This is a firmware issue present in 1.510 only. Resolution Cycling power to the MNB-1000 after changing the instance Number will correct the issue. Once communications is established upgrade the MNB-1000 firmware version 1.511 to prevent the possibility of this happening in the future.

Issue The IP address can be entered into a UNC-410 using the Admin Tool but after rebooting or power cycling the device, the IP address is reset back to the factory default. Environment I/A Series (Niagara) R2 UNC-410-2(-N) with serial number greater than 36218 Cause The newer UNC hardware manages stored OS configuration data in a different manner than the older UNC-410 devices.  Because of this change, the factory default operating system has the capability to read, but not permanently change the device IP address. Resolution You must use the Admin Tool Installation Wizard to install the r2.301.527 (or newer) version of the OS and NRE (system software) before you can save any new Ethernet address information to the UNC. Follow the procedure in the UNC-410 installation manual (F-27391) section "Upgrade, License and Configure the Host" to install the OS and NRE system software and to configure the required software modules.  Click here to see the referenced page of the manual.

Issue During initial setup, the incorrect ethernet IP address or subnet mask was entered.  Now when rebooting the UNC, I cannot reconnect to it using the I/A Series R2 Admin Tool.  How can the incorrect information be changed? Environment UNC-520 or UNC-410 Cause Network connectivity cannot be established if the IP address or subnet mask was entered incorrectly.  Likewise, if an invalid subnet mask is entered, the UNC may not boot completely (or at all). Resolution The following information is provided in more detail in the section "Determining Network Settings", subsection "JACE-4/5" of chapter 3 of the Niagara Networking & Connectivity Guide.  This document is provided with and installed with the I/A Series (Niagara) R2 software. Required hardware: Serial Cable Terminal Emulator software on computer (such as "Hyperterminal" or "Putty") Procedure: Configure the Terminal Emulator to run at 9600 baud, 8 bits, one stop bit, no parity, hardware flow control Jumper the upper two pins of the Console "MODE" connector,  located in the upper right corner of the UNC-520 circuit board (See photo at right). Connect the terminal emulator via a UNCC-405 serial cable to port COM1 on the UNC and power-cycle the UNC. Wait for the UNC to complete its bootup process (do not break out of the boot process). Check the displayed information to determine what IP address and subnet mask was entered. Power cycle the UNC and when the console display shows "Press any key to stop auto-boot"., press the space bar. Follow the procedure in the section "Determining Network Settings", subsection "JACE-4/5" of Chapter 3 of the Niagara Networking and Connectivity Guide for the procedure to step through the settings changing them if necessary.  Please note that the figure 3-8 may not include all lines of information shown for your UNC. If the serial console is showing any errors after you have verified the IP address / Subnet mask entries, please provide product support with a text copy of the serial console output showing the error messages.

Issue Temperature readings from an I/A Series Micronet LON controller is displayed as a Fahrenheit value in an I/A Series R2 UNC station The default units of measure has already been set to Metric in the WorkPlace Tech application Environment I/A Series R2 Cause SNVTs defined as a temperature is converted to Fahrenheit by the LonWorksService in the UNC station. Resolution The temperatureUnits property needs to be changed to the desired unit. Here are the steps to accomplish this: Right-click on the LonWorksService in the UNC station and go to Properties. Go to the 'General' > 'Config' tab. Change the temperatureUnits to 'celsius'. Click 'Apply'.   The definition of the temperatureUnits property is: Temperature units are the only units that Niagara R2 allows you to modify. The LonTalk protocol measures all values in SI units, therefore, temperatures are measured in degrees Celsius. With this property set to Celsius, no temperature conversion is performed—the value coming off of the wire is assumed to be in degrees C. If set to Fahrenheit, any SNVT defined as a temperature is converted.

Issue A controller with only 2 available outputs is being used to control a 3 stage device. Environment Three stage device control where lower stages must remain active. Cause Hardware or space limitations may prevent there from being enough outputs to control a three stage device. Resolution Two controller outputs in conjunction with a DPDT (dual pole, dual throw) relay can be configured to control a three stage device. This will allow you to activate stage 1, stages 1 and 2 or all three stages by activating either one or both of the controller outputs. An example of when this might be used is to control three stages of heat or a three stage fan. A standard "ice cube" type relay can be used (IDEC RH2B or similar) and should be wired as shown in the diagram below.   The controller should be programmed to activate only output 1 for stage 1, activate only output 2 for stages 1 and 2 and finally to activate both outputs for stages 1, 2 and 3. Note that certain application specific controllers may not allow the outputs to be configured in the way described above and thus cannot take advantage of this setup.

Issue Is there a wiring diagram available for the HOA BACnet Series Digital Output Override Cards for IA BACnet Controllers? Environment IA, MNB-300, MNB-1000, MNB-1000-15, BCS-HOA-3-BACNET, BCS-HOA-4-BACNET Cause Is there a wiring diagram available for the HOA BACnet Series Digital Output Override Cards for IA BACnet Controllers? Resolution A wiring diagram on the HOA card can be viewed in the attached document.

Issue Attempting to make programming changes to a Niagara R2 UNC-510 station.  After the changes are done, performing a backup fails.  The "save runtime db" does not complete. Environment Niagara R2 UNC-500, UNC-510 Cause The backup process (save runtime db command) requires free memory on the smart media card.  There must be enough free memory to (at least) equal the size of the .sns file. The smart media card (listed as '/sm' on the Summary tab of the Admin Tool) holds the station database (.sns file), graphic images, and other files accessible using the Remote Library. The table below summarizes flash drive volumes and usages by model.  Note that a jace in the table is a UNC. Refer to the Niagara Capacities Engineering Notes for more information. Resolution Access the Remote Library via Workplace Pro and delete unnecessary files.  As files are removed, monitor the Free File Space on the Summary tab in Admin Tool.  When the '/sm' increases a few kilobytes, try performing a 'save runtime db'.  If the command is successful, then the free file space created is adequate.  If it does not, repeat steps 2 and 3 until it is.

Issue A MicroZone II (MZ2) indicates "cold reset" or "warm reset". What do these error messages mean? Environment MicroZone II (MZ2) controller Cause The error messages are in response to interruptions to the controller's  24 Vac power. Resolution For a detailed explanation of the "cold reset" and "warm reset" messages, see the MicroZone II Programmer's Manual, F-23118, "System Resets". Click here  to see an excerpt from the manual.

Issue BACnet MSTP Sniffer Tool Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP Sniffer tool provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution The MSTP Tool was created by Steve Karg and is free to download. For further information about Steve Karg or BACnet MSTP tool it is available at  http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  To download a copy of the BACnet MSTP tool and instructions click here . To capture data follow these steps: Unzip file Open command prompt  with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Blue tooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue Laptops are now being supplied with an express card slot instead of a PCMCIA card slot. The LON PCC-10 cards are PCMCIA cards and will not fit in an express card slot. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Using the Lon PCC-10 Card in a laptop that has an express card slot and not a PCMCIA card slot. Cause The latest laptops are being supplied with express card slots. The option of a PCMCIA card slot is becoming harder to specify. Resolution Although the slot in the laptop appears to be the same as a PCMCIA card, the Express card slot differs in many ways to the PCMCIA slot the PCC-10 card requires. Express card slot to PCMCIA card converters are available but not all support the PCC-10 card. Some express card to PCMCIA card converters only support 32 bit PCMCIA cards. The PCC-10 is a 16 bit card. Basic testing has been carried out on an express card to PCMCIA card converter with a LON PCC10 card from Roalan Ltd. You can purchase the EC1632 converter direct from Roalan Ltd. website by credit card through the Sagepay secure web server. Alternatively, you can phone your order to +44 (0)1202 861512 or fax it to +44 (0)1202 891454. The product is plug and play on Windows Vista and Windows 7 with a downloadable utility for Windows XP. (Only required on some computers. It was not required on the Dell E6420 when testing the card.) You can download the utility here: EC1632.zip, or from Roalan's website. Further information on the converter is available on Roalan's website. You may also download the EC1632 Installation Guide. The card should be plug and play. If your PCC-10 card does not work when using the express card converter, check the PCC-10 card installation using under the control panel. If the card is not working correctly review The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. If you need to order a LON PCC10,PCMCIA card, they are available through Schneider Electric specification number WPA-LON-2.

Issue Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Controllers: ENC-410-1 ENC-410-1-N ENC-520-2 ENC-520-2-N Cause There maybe a need to access the ENC via its serial port if the IP address of the ENC is unknown or for troubleshooting purposes when the ENC's Ethernet port is not functioning. Resolution Hardware required for connection to ENC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors. RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430). A functioning COM port on your computer. A 2-pin jumper for connection to the ENC's 'Mode' connector. Refer to the Installations Instructions for ENC-410 (pages 10 & 11) or ENC-520 (pages 10 & 11) for details on the cable and adapter.  Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC also refers to these pin outs. Connection to ENC's serial system shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems 😞 Connect the cable and adapter between the ENC’s RS-232 port and the RS-232 COM port you are using on your computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to ENC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port you are using on your computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 57600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Click OK. On the ENC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 7 of the ENC-410 or ENC-520 Installation Instructions for position of the Mode connector. With your HyperTerminal session active and configured to log to a file, remove power from the ENC, let it cycle down, then reapply power.  The easiest way to power cycle the ENC is to unplug the 6-pin power plug from the circuit board, wait 15 seconds and plug it back in.  After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... Do not press any key, wait for the login prompt. If you did press a key to stop auto-boot, select option 1. At the login prompt, enter the platform user name, and at the password prompt, the platform password. The default user name is 'tac' and password is 'niagara'. The system shell menu should now appear. You should able to see the IP address of the ENC now. When finished using the serial system shell, do the following: Remove the 2-pin jumper from the Mode connector of the ENC. From the system shell menu, select the Reboot option. Type 'y' at the 'Are you sure you want to reboot [y/n]' prompt, and press Enter. Shutdown-related text appears in the HyperTerminal window, and then the connection is dropped. Press the Disconnect button on the HyperTerminal tool bar. Exit from the HyperTerminal application, selecting to Save if you wish to reuse this HyperTerminal setup for future connection to an ENC. If you are troubleshooting the ENC, send the HyperTerminal start up messages to Product Support for analysis.

Issue In a new installation, the ProView display (never configured previously) is powered and wired to the LON trunk back to a UNC-520.  In the station's LonWorks Service, a Find completes but the ProView display does not appear. Environment Niagara R2 version 529 or newer ProView Cause "New" ProView displays are somewhat unpredictable when added to a Niagara R2 station for the first time. Once it has been commissioned and programmed, its behavior improves. Resolution Add the appropriate shadow object from the 'distech' jar file (Ecdis210) to a container under the lonTrunk. The programID for the ProView display is:  90:0:83:32:b:84:4:15 In the LonWorks Service - Lon Device Manager, highlight the just-added Ecdis210 object and Commission. Use the SrvPin method to learn the neuronID (ProView display's service pin is located on the bottom to the left). Once the commission process complete, ProView is now available for programming.

Issue How to configure a Niagara R2 UNC as a LON Node  Environment Niagara R2 Cause How to configure a Niagara R2 UNC as a LON Node  Resolution Steps to configure UNC as LON Node

Issue Niagara G3 (NiagaraAx) Open NiCS (Niagara Compatibility Statement) Environment Niagara G3 (NiagaraAx) Cause NiCS attributes: Niagara G3 (NiagaraAx) licenses has brandId="TAC". A station's ability to accept NiagaraAx data from another NiagaraAx station depends on the accept.station.in="*" field in its license. A station's ability to share NiagaraAx data with another NiagaraAx station depend on the accept.station.out="*" field in its license. A station's ability to allow a copy of WorkBench to connect to it and engineer the station depends on the accept.wb.in="*" field in its license. A copy of WorkBench's ability to connect to a NiagaraAx station to engineer it depends on the accept.wb.out="*" field in its license. (Where "*" is the brandId) 'Open' licenses may be required when there is a need to: Allow sharing of a station's NiagaraAx data to another station which has a different brandId in its license. Accept NiagaraAx data from another station which has a different brandId in its license. Allow a WorkBench connection from a copy of WorkBench that has a different brandId in its license. Allow a copy of WorkBench to connect to a station which has a different brandId in its license. Resolution Niagara G3 open NiCS licenses have the following: “accept.station.in="*”; “accept.station.out="*”and “accept.wb.in="*”and “accept.wb.out="*”. The "*" is a wildcard designation to allow all brandIds. You can specify new licenses to have open NiCS by selecting the 'Request open NiCS (Niagara Compatibility Statement)' checkbox in the I/A Series G3 license request forms. You will need to purchase the part IA-LIC-CHG for each existing Niagara G3 that needs to have an open NiCS. 

Issue How many controllers can be connected to an ASD bus before a repeater is required? Environment Global controller with an ASD bus connected (GCM, UNC, ENC, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, SIM-YORK) ASD controller (LIM-1,MicroFlo II, MicroZone II, MN-ASDI integrator, PEM-1) Cause Requirements for ASD bus installation. Resolution A maximum of 32 nodes are allowed for each ASD bus segment.  Each controller and repeater count as one node, so a bus segment with a master (GCM, UNC, etc.) and a repeater can have 30 other nodes on it ( MZII, MN-ASDI, etc.) For details, See the Network 8000 Hardware Installation Practices manual, F-23061-1, "Network & Communication Wiring", "Repeaters - RS-485".

Issue WorkPlace Tech revision 5.7.7 installed on a Windows Server 2003, 64-bit machine, receives the following error: Environment WorkPlace Tech Tool version 5.7.7 Windows 2003 Server, 32 bit or 64-bit Windows 2008 Server, 32 bit or 64 bit (multiple processors) Cause WorkPlace Tech Tool (WPT) is not supported on computers with Windows Server operating systems, nor on computers with 64-bit operating systems. Resolution Install on an approved hardware platform, per the Installation Instructions.

Issue On an FTT-10 trunk  segment wired in a Loop Topology, where should the LON-TERM1 terminator be installed? The Loop Topology is a subset of the Free Topology. Environment LonWorks FTT-10 network including I/A Series MNL controllers wired in a Loop Topology. Cause Installation detail Resolution In a Free Topology segment, only one termination (LON-TERM1) is required, and may be placed anywhere on the free topology segment.

Issue How to set an LNC-100 back to factory-default settings. This will erase all block programming and device configuration. Environment Network 8000 LNC-100 and related controllers based on the GCM-861X0 series platform, including the GCM-86110, GCM-86120, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK Cause Sometimes it is necessary to manually clear the controller EEPROM in order to reload a database. Resolution Follow the steps below: Backup the controller database. Clear the controller's EEPROM. This is accomplished by pushing the reset button and the EE CLR button and holding both for at least 20 seconds before releasing. The reset process is complete when the top two red LEDs on the right edge of the controller begin blinking in their normal sequence (second LED blinks twice as fast as top LED). This process will clear the user programmable memory (including all block programming), returning the controller to its original factory condition. This step is important as it insures there will be no conflict between the new revisions firmware and the older version. The procedure above is excerpted from Technical Bulletin 99-27 , steps 1 and 2.