Building Automation Knowledge Base

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue Cannot find any installation instructions documentation for the WorkPlace Tech Tool software, versions 5.8 or 5.8.1. Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.8 & 5.8.1 Cause An updated version of the document "WorkPlace Tech Tool Version 5.7 Installation Instructions" has not yet been released by our publications group. Resolution The existing "I/A Series WorkPlace Tech Tool Version 5.7 Installation Instructions", F-27367 can be used for installing the release 5.8 or release 5.8.1 of the WorkPlace Tech Tool software. There are two items applicable to the newer versions of the WorkPlace Tech Tool software that are not covered in the published installation instructions. The WorkPlace Tech Tool software, releases 5.7.7, 5.8 and 5.8.1 will run on the 32 bit versions of Windows-XP, Windows Vista or Windows-7.  These releases of the software will also run in XP-Mode under the 64-bit version of Windows-7.  See I/A Series (Niagara) R2 Windows Compatibility Matrix and the linked PA-00163 product announcement for more information on Windows 7 compatibility.  Make sure that the computer meets or exceeds the recommended requirements, not the minimum requirements, for the operating system being used. Beginning with release 5.8.5 of the WorkPlace Tech Tool software, Windows 7 64-bit Professional and Microsoft Visio 2010 is supported (32-bit version only), in addition to the documented Microsoft Visio 2003 and Microsoft Visio 2007 (32-bit versions). The use of Visio 2010 and its ribbon bar menu system are described in the WorkPlace Tech Tool release 5.8 release notes.  This same version of the release notes (5.8) is applicable to the use of Visio 2010 with the WorkPlace Tech Tool software release 5.8.1.

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue XIF files for the standard MNL controllers are available on The Exchange Download Center.  Please do not use with SmartStruxure.  See XIF files for Version 1 and Version 2 of MNL controllers. Product Line TAC IA Series Environment I/A Series standard (fixed profile) controllers: MNLRF2 - Fan Coil profile MNLRH2 - Heat Pump profile MNLRR2 - Rooftop profile MNLRS1 - Satellite 1 / Rooftop profile MNLRS2 - Satellite 2 / Rooftop profile MNLRV2 - VAV profile MNLRF103 - Fan Coil profile MNLRH103 - Heat Pump profile MNLRR103 - Rooftop profile MNOTPVA3 - VAV profile MNLRF3 - Fan Coil profile MNLRH3 - Heat Pump profile MNLRR3 - Rooftop profile MNLRS3 - Satellite 3 / Rooftop profile (revised previous Satellite 1) MNLRS4 - Satellite 4 / Rooftop profile (revised previous Satellite 2) MNLRV3 - VAV profile Cause XIF files are available if needed. Resolution Download the file TAC_LLC.zip from The Exchange Download Center. Also see the accompanying Readme file.

Issue How to order more LonMaker credits in order to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LNS credits see Ordering more LNS credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To order more LonMaker credits: Echelon LonMaker v3.1 Open up a LonMaker database and go to LonMaker menu > LonMaker Credits Info... Here you can view how many LonMaker available credits that you have. Click on Add Credits... In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, click the Copy to Clipboard button to copy the PC key generated by LonMaker License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, open up the LonMaker License Wizard again. Click Next and paste the application key into the field titled "Application Key". Click Finish. Echelon LonMaker v3.2 Turbo Open up the LonMaker License Wizard by going to Start > All Programs > Echelon LonMaker > LonMaker License Wizard. Here you can view how many LonMaker credits that you have available. In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, click the Copy to Clipboard button to copy the PC key generated by LonMaker License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your Schneider Electric Buildings Business Order Entry Department (888-444-1311) so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, open up the LonMaker License Wizard again. Click Next and paste the application key into the field titled "Application Key". Click Finish.

Issue Serial connection to I/A Series R2 UNC VxWorks Target Shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers: UNC-410-1 UNC-410-1-N UNC-520-2 UNC-520-2-N Cause There maybe a need to access the UNC via its serial port if the IP address of the UNC is unknown or for troubleshooting purposes when the UNC's Ethernet port is not functioning. Resolution Hardware required for connection to UNC'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 a computer A 2-pin jumper for connection to the UNC's "Mode" connector Refer to the Installations Instructions for UNC-520 (page 15) for details on the cable and adapter (applies for both UNC-410 and UNC-520). Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) also refers to these pin outs. Connection to UNC's VxWorks Target 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 UNC's RS-232 port and the RS-232 COM port used on the computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to UNC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port used on the computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: Hardware Click OK. On the UNC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 17 UNC-520 Installation Instructions for position of the Mode connector (top right corner). With the HyperTerminal session active, remove power from the UNC, let it cycle down, then reapply power. After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... To enter commands to the UNC, press any key to break out of the boot sequence. A prompt similar to the following is shown: [VxWorks Boot]: To determine the IP address / subnet mask of the UNC, do not break the auto-boot sequence as described in step 7. Allow the UNC to finish booting. When the controller stops displaying new messages, press ENTER to reach the command prompt. The prompt is similar to the following: -> Using the scroll bars on the HyperTerminal window, scroll up until the section that begins with the line 'Press any key to stop auto-boot...'. The IP address of the UNC is listed on the line that begins 'inet on ethernet (e)' The IP address is listed (in dotted decimal), followed by a colon, and then the subnet mask (in hexadecimal). Disconnect from the UNC when complete. Press the 'Disconnect' button on the HyperTerminal toolbar. Exit from the HyperTerminal application, selecting to Save if planning to reuse this HyperTerminal setup for future connection to an UNC. Remove the 2-pin jumper from the Mode connector of the UNC. Reboot the UNC by removing the power connector, waiting for all lights to extinguish, and plugging the power connector back in. * If troubleshooting the UNC, send the HyperTerminal start up messages to Product Support for analysis.

Issue Encountered the error 'The Bcpv3 service is not installed under Config/Services' while trying to add a discovered BACnet device to the station database Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server / Workbench Cause The default view of the BacnetNetwork is now the 'Bcp Bacnet Device Manager' instead of the standard I/A Series G3 'Bacnet Device Manager'. This happens when the Distech Controls EC-NET-AX Support Package  v3.0.2.8 (I/A Series G3 support files for Proview) is installed on the computer running the station. Refer to BCP Device Manager showing up with the BACnet Device Manager. The Bcp Bacnet Device Manager is used to discover and add Distech devices. Using it to discover and add I/A Series BACnet controllers will result in the 'The Bcpv3 service is not installed under Config/Services' error. Third party non Distech devices may also exhibit the same symptoms. Resolution Discover and add BACnet devices using the 'Bacnet Device Manager' instead of the 'Bcp Bacnet Device Manager'. The 'Bacnet Device Manager' is now the 2nd view of the BacnetNetwork (right-click on the BacnetNetwork and go to 'Views' > ' Bacnet Device Manager').

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

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 Modbus integration to Schneider Electric's PM1200 Power Meter Product Line TAC IA Series Environment I/A Series R2 Modbus Async (asynchronous) Integration Cause Requires the correct settings / configuration for Modbus integration to PM1200 power meter Resolution In WorkPlace Pro, open the UNC station and make changes to the following settings to integrate to the PM1200 power meter via Modbus Async (asynchronous). In the ModbusAsyncService properties, 'Comm' tab, ensure that the COM port settings matches the communications settings in the power meter. In the ModbusAsyncService properties, 'General' > 'Config' tab, change the floatByteOrder to 'order_1_0_3_2'. In the ModbusGenericAI object, the dataType should be set as 'Float'. dataAddress > addressFormat should be set as 'Modbus'. Use the register address as per the PM1200 documentation. Refer to the following documentation for details. PM1000 Series Power Meters Users Guide Modbus basics

Issue Unable to connect to the ENC using its IP address. The ENC Ethernet port LED's appear to indicate normal operation. Product Line TAC IA Series Environment I/A Series Enterprise Network Controller Cause The ENC DHCP function was enabled by mistake on a system that does not have a DHCP server. The ENC when booted up will try to get an IP address from a DHCP server which does not exist and the ENC may not have a valid IP address. Resolution Connect to the ENC via its serial shell and perform the following procedure. Refer to Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal for details on connecting to the ENC serial shell. 1. Connect to the ENC serial shell using Windows HyperTerminal. Allow the ENC to boot up completely and you should see output messages similar to the following.   JACE 4/5 IPL Version 6.40 ECC to stop Autobooting on-board nand james startup version 6.41 launching devc waiting for /dev/ser1 creating symlink for /dev/serconsole Welcome to QNX Neutrino 6.4 on the ppc824x(james) starting /ffs0 filesystem ETFS_FS_2048 fs-etfs-jace2048: Truncating fid 0x2f from 337920 to 316718 bytes fs-etfs-jace2048: Truncating fid 0x64 from 5488640 to 13 bytes fs-etfs-jace2048: Truncating fid 0x1ce from 4096 to 0 bytes i2c: Using 100Mhz freq divider Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:20:96:08:ee:06 media: Ethernet none status: no carrier inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- bad battery detected, A/C power test will not function MESSAGE [12:38:25 19-Jun-2013] [tid=1] niagarad: starting, baja_home=/niagara MESSAGE [12:38:25 19-Jun-2013] [tid=1] webserver: web server started [tid = 4] MESSAGE [12:38:25 19-Jun-2013] [tid=1] app registry: station registry starting MESSAGE [12:38:25 19-Jun-2013] [tid=7] engine watchdog: station TEST0817_TIM watchdog thread started [tid = 8] MESSAGE [12:38:25 19-Jun-2013] [tid=7] station: station TEST0817_TIM starting login: tac Password: [2J [H J404 System Shell ------------------------------------------------------------------------- hostid: Qnx-J404-0000-15C8-14F9 serial number: 584966 build version: 2.5.25 build date: built on 2011-04-04 16:47:24 system time: Wed Jun 19 12:38:43 STD 2013 niagara daemon port: 3011 en0: inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- 1. Update System Time 2. Update Network Settings 3. Ping Host 4. Enable/Disable Ftp 5. Enable/Disable Telnet 6. Update Platform Account 7. Reboot L. Logout   2. Select option 2 for update the network settings. 3. Press 'enter' (enter leaves the field at the original setting) for each field until the 'IP address (clear to use DHCP)' field. 4. Type in the required IP address here and press enter. This will disable the ENC DHCP function. 5. Key in the subnet mask at the next line and select 'n' when prompted to use IPv6. 6. Press enter until you are prompted to save the changes.      [2J [HJACE Network Configuration Utility Enter new value, '.' to clear the field or '' to keep existing value Hostname : Domain <> : Primary DNS Server <> : Secondary DNS Server <> : Route <192.168.10.1> : Primary IPv6 DNS Server <> : Secondary IPv6 DNS Server <> : IPv6 Route <> : NET1 Ethernet interface IP address (clear to use DHCP) <> : 192.168.1.141 Subnet mask <> : 255.255.255.0 Enable IPv6 addressing on this adapter? (Y/n) : n Confirm new configuration Hostname : localhost Domain : Default Gateway : 192.168.10.1 Primary DNS : Secondary DNS : Default IPv6 Gateway : Primary IPv6 DNS : Secondary IPv6 DNS : NET1 settings: IP Address : 192.168.1.141 Subnet Mask : 255.255.255.0 IPv6 Addressing disabled Save these settings? (Y/n) : y    7. Reboot the ENC and connect to the ENC using Workbench. 

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 Echelon Node Utility with Loytec NIC-USB Network Interface Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Microsoft Windows 7 32-bit Echelon Node Utility 2.04 Echelon OpenLDV 4.0 Loytec NIC-USB network interface Loytec NIC driver version 4.1.3 Cause There is a need to run Echelon Node Utility using Loytec network interfaces. Resolution The easiest way to accomplish this, is to use the NodeUtil Launcher. This program scans the registry for known interfaces. It was created by an active Community member. * Do take note Schneider Electric Product Support does not provide support for the NodeUtil Launcher - for support please write the developer of the tool. Below are two methods to manually achieve this if you don't want to use the tool. Here are 2 methods to run Node Utility using Loytec NIC-USB network interface. Method 1 involves accessing the Windows registry to check the path name of the Loytec network interface. We are not modifying any entries in the registry but as always, we should be careful when we access the Windows registry. Using Windows registry incorrectly can cause serious problems that may require you to reinstall Windows. Method 2 will configure the Loytec NIC-USB to use LON1. If you have used an Echelon LonWorks interface as LON1, you will need to detach it before you can use this method. Method 1 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity Run Windows registry editor (Start > Run > regedit). Navigate to the path HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\DeviceDrivers. The interfaces will be shown here. Look for the interface with '_LDV'. Run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil using the command nodeutil -D"". See example below. Method 2 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity. Click on the 'Advanced' button. Check the option 'LON1 Support for device' and select the appropriate device in the drop down list. You will need to reboot the computer for this to take effect. Once the computer has restarted, run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil. Node Utility should now run.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment Windows 7 computer WorkPlace Tech Tool software version 5.7 or later Cause The WinPcap driver, used in WorkPlace Tech BACnet communications was configured to start on demand and the WPT module that is attempting to start WinPcap does not have the necessary Windows security rights.  Resolution NOTE 1:  Before using this procedure, please verify that the issue noted in WorkPlace Commissioning Tool UDP Port: "A critical error occurred in the communication server rtmonitor.exe" has been corrected, if present, and did not solve the problem. NOTE 2: If the computer is running Windows 7-64 bit, replace the following references to "Program Files" with "Program Files (x86)". To correct this issue, perform the following steps. Open Windows Explorer, i.e., "My Computer" or "Computer" from the Windows Start menu or computer desktop. Open the folder "C:\Program Files\WorkPlace Tech" For each of the following program files listed here, in turn: RTMonitor.exe, WPCT.exe, WPFB.exe and WPTech.exe Right click on the program name, Select Properties from the pop-up menu, Select the "Compatibility" tab. In the Compatibility display, click the button [Change settings for all users]. Locate "Privilege Level" section of the displayed window and check the box "Run this program as an administrator". (See snapshot below) Click the [OK] button to save the settings for all users. The window will close. You will see that the Privilege Level option is no longer selectable. Click the [OK] button to save the compatibility settings.   After setting the privilege option for each of the four programs in the Workplace Tech folder, repeat the same setting change for the Microsoft Visio program itself, VISIO.EXE. Depending on the version you are using, it will be located in the C:\Program Files\Microsoft Office\OfficeXX folder where xx is 14, i.e., Office14, for Visio 2010, 12, i.e., Office12, for Visio 2007 or 11, i.e., Office11, for Visio 2003. After setting these options, the computer should be shut down and restarted before using the WorkPlace Tech Tool software.  

Issue Configuring the Workplace Tech encrypted LON Tunnel Client  Product Line TAC IA Series Environment I/A Series WorkPlace Tech 5.9.4 Click for WorkPlace Tech 5.10.4 information I/A Series N4 Jace Cause How to handle the encrypted LON tunnel for single and multiple LON networks.  Understanding possible errors during tunneling. Resolution The following video will help us, Apply the Encrypted LON Tunnel in an N4 Jace Configure the Tunnel Client for use with multiple LON Networks on a single Jace Recognize a Timeout Error and how to handle it

Issue Unable to send out emails using Gmail SMTP server (smtp.gmail.com) with the following error messages in the station's standard output. "javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first." Authentication has been enabled in the system.properties file as per Mail Service in a Niagara R2 UNC station configured correctly but e-mails not being sent to the SMTP server. Product Line TAC IA Series Environment I/A Series R2 Cause As with most public SMTP servers, like Gmail, the outgoing mail SMTP server requires TLS (Transport Layer Security) or SSL (Secure Sockets Layer) which I/A Series R2 does not support. Resolution Use an SMTP server that does not require TLS or SSL.

Issue “IP_ADD_MEMBERSHIP failed” appears in the Application Director output during reboot of the Jace and in the Station Discovery on the Niagara Network after a failed discovery attempt Product Line TAC IA Series Environment ENC 520, 410, Jace 6E, 645, 700, 8000 controllers using G3/AX. The second Ethernet interface only applies to the Jace 6E, 700, 645 and 8000 Cause Incorrect or no default gateway assigned in the TCP/IP Configuration or Interface 2 is enabled and set for DCHP with no DHCP server available to that interface. See the notes on the illustration for possible configuration faults. Resolution Make certain you have a valid IPV4 or IPV6 (schema dependent) Gateway entered for the Interface 1 IP configurations. If set to DHCP, ensure there is a DCHP server available on the interface. Disable all unused interfaces and IPV6 if not applicable. If there are problems accessing or configuring the interfaces, you may need to use the System Shell of the ENC/Jace and correct the configurations there. Need to correct invalid IP address or subnet mask entered into an ENC or JACE

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue There may be a situation where the External Interface File (XIF) needs to be extracted out of the controller in order to properly set up the controller in a building automation system.  Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment External Interface File (XIF) NodeUtil Loytec XIF Builder Cause These tools will help with the extraction of an XIF file. An XIF file is used to create a Niagara R2 shadow object, a Niagara G3 LMNL file, LonWorks device template, and a SmartStruxure device template.  Resolution The device manufacturer should provide an XIF, and in most cases, a DRF kit as well. The XIF provided by the manufacturer of the controller should be used first but if issues arise it may be required to extract the file from the controller. There are a number of tools available that will create an XIF, but the DRF kit cannot be created by any tool and must be supplied by the manufacturer. This MUST be provided along with the device. The list below covers some of the tools which are available. NodeUtil                          (header: bad,           NVs: ok,                      DMA/File-SCPTs are omitted) Vista's XIF-builder           (header: bad,           NVs: almost ok..,       DMA/File-SCPTs are omitted)  Loytec plugIn                  (does a perfect XIF from a device using Loytec's stack)   NodeUtil is available from the Echelon website (free registration is required) - The NodeUtilLauncher package attached makes it easy to use NodeUtil with Loytec interfaces. Loytec XIF Builder is available from the Loytec website (free registration is required) Using Lonmaker and the XIF Builder. Using NL220 and the XIF Builder. If the uploaded XIF still contains some detailed prompted error, refer to Error displayed when importing a device XIF into SmartStruxure.

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.