Issue On a jobsite doing a backup of a GCM and its ASD controllers.  After an upload of the GCM is complete, the ASD controllers appear in the tree (the upload of the GCM created them).  Do they also need to be uploaded individually? Environment TreeTech (any version) Cause Understanding all the steps in a proper / complete upload of a GCM and its controllers. Resolution The first step is to upload the GCM. The second step is to upload each individual ASD controller (Microzone II, Microflo II, etc...).  Each upload will take less than a minute.

Issue A computer running UltiVist locked up and was rebooted.  Each reboot brings it right back to its locked up state.  How can this be prevented? Environment OS/2 UltiVist Cause A task or program does not execute properly and causes OS/2 to lock up with no response from keyboard or mouse. Resolution Boot up from the installation diskettes to gain access to a command prompt.  On the hard drive, modify the config.sys file to include the following lines: set restartobjects=startupfoldersonly set autostart=programs,tasklist,folders,warpcenter These lines will prevent the computer from running programs or tasks that lead to its locked up state.

Issue Does the JACE-6E or JACE-7 support multiple FTT-10A LON cards? Environment JACE-6E, JACE-7, LON FTT-10A Cause Application requires multiple FTT-10A LON trunks. Resolution Yes ... the JACE-6E / JACE-7can support two individual FTT-10A cards.  Purchase (2) TRD-NPB-LON (FT-10A Lon Adapter cards) and (1) ENC-DRV-LON driver.  Add one LonNetwork for each physical port.  Under each LonNetwork within the Lon Comm Config, specify the port's Device Name (e.g. LON1 and LON2).  Reference the Niagara AX Lonworks Guide for more details.

Issue Is Niagara G3 version 3.7 compatible with all the legacy drivers? Environment Niagara G3 Cause Sales request Resolution The ENC-520-2 can be installed with version 3.7 as well as any of the legacy drivers (ASD, GCM, DMS, MicroSmart).

Issue In Niagara G3, how many stations can connect to one Enterprise Network Server? Environment Niagara G3 Cause Planning a large installation Resolution An Enterprise Network Server running on a 32-bit server can handle up to 150 stations. An Enterprise Network Server running on a 64-bit server can handle up to 500 stations.

Issue Does Niagara G3 support or use the Service Location Protocol (SLP)? Environment Niagara G3 Cause Query made by an end customer Resolution No.  Niagara G3 is not aware of or uses the Service Location Protocol (SLP).

Issue Getting LON messages TException E_QUEUE_FULL {LonAsyncRequest} in the standard output window. Environment R2, Niagara, Lon Service Cause If also in the message there is a line that includes: "lonextras.control.PollSnvtTempSetptCmd.execute" these messages are being caused by the use of the special object from the LonExtras jar called PollSnvtTempSetptCmd.  Resolution When the station is booting up the PollSnvtTempSetptCmd object  will begin its polling function before the station has finished rebooting causing the queue to fill up before the station starts.  There is an object in the LonWorks jar - Conversion container called SnvtTempSetptCmd that will perform the same function as the PollSnvtTempSetptCmd except it does not poll which is not necessary in most cases.  Replace all PollSnvtTempSetptCmd objects in the station with the SnvtTempSetptCmd object.

Issue The UNC and Enterprise server, as well as many other Schneider-Electric Buildings products, use a TIME protocol server to provide clock synchronization. The address of that Time Protocol Server no longer works. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Schneider Electric Buildings products that rely on the use of TCP TIME protocol servers for time synchronization. This includes the I/A Series R2 UNC & ES and the I/A Series G3 ENC & ENS as well as other IP ethernet based products. Cause Many server sites are discontinuing support for the TCP TIME protocol because it is so bandwidth intensive. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. The site http://tf.nist.gov/tf-cgi/servers.cgi lists most of the currently available TIME protocol servers as well as the status of the entire TIME protocol system. Resolution If the product supports the use of the NTP time sync protocol, switch to the use of that protocol. If the device only supports the TIME protocol, consult the web site http://tf.nist.gov/tf-cgi/servers.cgi for currently available sites.

Issue Error "Job Failed  java.lang.NoSuchMethodError: com/tridium/install/BDaemonPlatform.getNiagaraR2Enabled()Z" when attempting to perform an I/A Series G3 Station Backup in version 3.6.31 after having installed the August 2012 security updates. Environment I/A Series G3 JACE or ENC with release 3.6.31 and security patches 3.6.47 installed. Cause Internal software error in the backup.jar file, version 3.6.47.2 Resolution Remove the backup.jar file, version 3.6.47.2 from the modules folder on the I/A Series G3 WorkBench computer. Remove the file backup.jar from the \niagara\niagara-3.6.31\sw\3.6.47.2 folder. Verify that the original 3.6.31 backup.jar file is in the  \niagara\niagara-3.6.31\modules folder.  Note that when replacing the backup.jar file, the 3.6.47.2 file should be renamed so that it can be restored later. Open the 3.6.31 Workbench and open the platform of the ENC / JACE. Run the Software Manager and note that a newer version of the is shown as installed as compared to the avail. version. Select the "backup" module by clicking on it then click the [Downgrade] button then click the [Commit] button. Acknowledge the warning that a reboot will be required by clicking the [Yes] button. Wait for the module commit process to complete, the station to reboot and restart. After the station has restarted you can log into the Station through Workbench and perform the backup to a .dist file using the standard station backup procedure (by right-clicking on the station name and selecting "Backup Station").

Issue The descriptions of the MN-S and MN-S1 sensors both state that they are temperature sensor only, what is the difference? Environment MN-S MN-S1 MN-Sx Micronet 2000 I/A Series Micronet Cause The part number descriptions of the MN-S and MN-S1 sensors both state that they are sensor only, what is the difference? Part # MN-S Description: MicroNet 2000 Wall Temperature Sensor with Temperature Sensor Only          Part # MN-S1 Description: I/A Series Micronet S-Link Sensor Assembly Providing Temperature Only.   Resolution While physically and functionally similar the two sensor belong to different product families and are not interchangeable since they utilize different communications protocols. The MN-S communicating sensor is compatible with the Micronet 2000 product family and is used with MN-FLO, MN-FLO3T, MN-HPFC controllers that use U bus communication protocol for sensor data. The MN-S1  communicating sensor is compatible with the I/A Series Micronet  product families and is used with MNL and MNB range of controllers that use S-Link communication protocol for sensor data.

Issue A sensor connected to a DMS system displays the letters INH to the right of the real-time display.  What does this mean and how can it be removed? Environment DMS Cause It is unknown how the INH appeared on the point.  There are at least three ways to do it with programming but none were found in the database. The INH is short for 'inhibit'.  It prevents a point from generating alarms or changing conditions even though an alarm or change of condition exists.  It is useful during times when maintenance is being done on the associated HVAC system or if the HVAC system is scheduled off.  It prevents nuisance alarms. Sometimes it gets applied after a database glitch during a loss of power or communications.  This situation is rare but it can occur. Resolution To remove the INH and allow the sensor to alarm and change condition, it must receive the ENINH command.  There are several ways to apply the ENINH command.  The quickest way is to use command mode. In OPRIF, - use the up and down arrow keys to highlight the sensor with the INH applied to it. - press F8 to enter command mode - type ENINH then enter - press F8 to exit command mode - allow OPRIF a few seconds to update and refresh the sensor on the screen

Issue Upgrading an end customer copy of WorkPlace Tech from version 5.8.1 to 5.8.2. Is there a charge for it? Environment WorkPlace Tech Cause Cost estimating for end customer's system upgrade Resolution There is no charge when upgrading WorkPlace Tech from 5.8.x to 5.8.y. Charges apply when upgrading WorkPlace Tech 5.7.x to 5.8.x.  

Issue A SIM block in an LNC-100 has a diagnostic ERROR output = 159. Environment Network 8000 LNC-100 Cause See the I/A Series MicroNet LON Network Controller manual, F-26566, Table 3.4, "SIM Block Error Codes", page 18: "Could not read the NV information from the node. NV index does not exist in the specified node. See Appendix A for NV index values. OR The node is possibly offline." Resolution Over the years, we have documented a few different cases of the ERROR = 159, and have found some different causes and resolutions. 1. On new installations, an incorrect data string in a SYS:SIM block could prevent the LNC-100 from communicating with any of the LON controllers, and every SIM block in the database would display ERROR = 159. For example, in one case, the data string in the SYS:SIM block was "DOMAIN0=010000, SUBNET0=1,NODE0=127,ENGLISH,HEARTBEAT=120".  Because the Domain address established by the network management tool used a one-byte address = 01, rather than the 3-byte address entered in the data string, the LNC-100 was not able to communicate with any LON devices. When the data string in the SYS:SIM block was edited to include the correct 1-byte Domain address, "DOMAIN0=01, SUBNET0=1,NODE0=127,ENGLISH,HEARTBEAT=120", the LNC-100 was able to communicate, and the diagnostic error in the SIM blocks was cleared. In another case, setting the NODE0=15, saving the change, then setting it back to NODE0=127 in the data string of the SYS:SIM block enabled LON communications. 2. On existing installations that have been working OK for years, some of the SIM blocks show ERROR = 159, while other SIM blocks continue to communicate normally. Because the LNC-100 continues to communicate normally with some of the LON controllers, you can rule out hardware failure of the LNC-100.       a. The LON nodes (controllers) associated with the SIM blocks displaying the ERROR = 159 might be offline. Use NodeUtil to check the status of the node, and to set it online if possible.       b. The LON controller may have been replaced, and the replacement controller not assigned to the same Domain, Subnet, or Node as the original. The SIM block will not be able to identify the replacement, will display ERROR = 159. Use NodeUtil to identify the LON address of the replacement node(s), and a LON network management tool to assign its Domain, Subnet, and Node to be compatible with the information in the data string of the SYS:SIM block.      c.  The LON controller may have been replaced by a newer model with a different profile, Program ID, and XIF file, so the points mapped in the SIM block no longer correspond exactly to the NVs in the newer profile. Use NodeUtil to extract the XIF file from the new controller, and check the NVs to determine if the NV index or SNVT type are different than those in the original controller. Edit the DATA field(s) in the SIM block to correspond to the new profile in the new controller.

Issue Both the BACnet Comm and the BACnet IP Port are enabled in an ENC-520, but BACnet devices are not being discovered. The Discover button it grayed out. Environment Niagara G3 all version, ENC-520-2, ENC-410 Cause No network adaptor was selected. The ENC's Adapter setting under the station’s BacnetNetwork/Bacnet Comm/Network/IpPort/Link was set to "none". Resolution A network adapter must be selected for the station. - Open the BACnetNetwork of the station and go to Bacnet Comm/Network/IpPort/Link - Click on the arrow next to the Adapter property and select the correct Ethernet adapter - save change - Make sure that the Object Id of the BACnet Local device is set to a unique value other than -1 - A reboot is required after the change. You should now be able to Discover the BACnet devices.  

Issue We are unable to connect to a Niagara G3 ENC-520 whose IP address was incorrectly set. How can the IP address be determined and changed if there's no access via its Ethernet port? Environment Niagar Workbench, ENC-520, ENC-410 Cause Incorrect entry of the IP Address or subnet mask can cause the ENC to appear unresponsive to WorkBench software. Resolution There are two methods available to determine the IP address and subnet mask entered for the ENC. The first method requires having access to the computer used to change the IP address of the ENC. Your Workbench PC records the “before and after” TCP/IP settings made from Niagara platform connections in a a file called "ipchanges.bog". You can review changes from Workbench using the following procedure. Do the following in Workbench: 1. In the Nav tree, expand “My Host” and then “My File System.” 2. Expand “Sys Home” and then “users.” 3. Expand your user folder, then expand “ipchanges.bog.” Child folders are “date-named” using the following convention: d for example, “d20041220171000” for 2004 Dec 20 5:10pm 4. Expand any folder of interest. Underneath each folder are two objects:    • priorValue — TCP/IP settings that existed before this change.    • newValue — TCP/IP settings that existed after this change. 5. Double-click a priorValue or newValue to see settings in the “Tcp Ip Host Editor” (see Figure). The second method requires the use of a terminal program, an UNCC-405 to adapt RS232 to RJ45, and a CBL-RJ45 cable (a standard Ethernet cable no longer than seven feet will do). The HyperTerminal program is used to directly connect to a ENC-520 to verify and to make changes to its IP address in order to make it accessible. HyperTerminal makes it possible to view the ENC's configuration and execute limited commands. Reference the section “Using serial system shell”, located in Chapter 1 of the Niagara AX Install & Startup Guide, on how to directly connect to ENC using HyperTerminal. After connecting to the ENC, use the procedure "Updating Network Settings", which is located in the same Chapter of the guide, to display and/or change the IP address or subnet mask. Failure to enter the subnet mask properly can prevent the UNC from being seen by WorkPlace Pro.          

Issue Can I run multiple connections with Remote Desktop Services or Microsoft Terminal Server Services to allow more simultaneous sessions of I/A Series G3 Workbench on a computer? Environment I/A Series G3 Enterprise Network Server, ENS, Workbench Cause This occurs when a computer with a single Enterprise Server is configured with Remote Desktop or Terminal Server Services to allow multiple users to have concurrent sessions of the Workbench running simultaneously. Resolution The Tridium EULA (End User License Agreement) does not permit Workbench concurrent sessions. Per the EULA, each session should originate from a separately purchased and licensed version of Workbench.

Issue Do the I/ A Series (MNL- or MNB-) controllers support more than one S-Link sensor? Environment I/A Series controllers: MNL-50, MNL-100, MNL-200, MNL-V1, MNL-V2, MNL-V3, MNL-800, MNB-V2, MNB-300, MNB-1000 S-Link sensors; MN-S1, MN-S1HT, MN-S2, MN-S2HT, MN-S3, MN-S3HT, MN-S4, MN-S4HT, MN-S5, MN-S5HT Cause Want to connect 2 S-LINK sensors to an I/A series controller Resolution No, only one S-Link sensor per controller is supported. Currently, there are no plans to add the capability of supporting a second sensor.

Issue Can a UNC-600 or UNC-610 be replaced with a UNC-410?  The installed UNC is in disrepair and it only does a LON integration of approximately 25 controllers. Environment Niagara R2 Cause UNC onsite no longer working as well as being obsolete and un-repairable Resolution As long as the station being transferred from the UNC-6x0 is not large, then the UNC-410 will perform well as a replacement unit. The UNC-410 only has 300,000 resources and is limited to 27 LON controllers. If more LON controllers must be integrated, then a special request to open the license to a higher node count must be submitted to the Marketing Manager and approved by him.

Issue WorkPlace Tech is connection to the site via VPN. An ENC-520 on site is setup as a BBMD device. The ENC and MNB-1000 are on the same subnet. The ENC’s address is entered in the “Access a remote internetwork” in WPT Commissioning Tool. WorkPlace Tech initially discovers the MNB-1000 device. The MNB-1000 is displayed in the Commissioning Tool, but grayed out. The MNB-1000 controller eventually displays the Lost Communication Icon. Environment WorkPlace Tech Commissioning Tool - all versions Cause The default gateway is incorrectly set in the MNB-1000. Resolution MNB-1000 controllers must have a valid IP address, Subnet Mask address and Default Gateway address for the communication ports to function properly.   Use WorkPlace Tech Commissioning Tool to set the correct default gateway IP address in the MNB-1000.

Issue Serially connected to a GCM-84000 with a pc running OS/2 and UltiVist.  There is no existing database in UltiVist.  The GCM database will be uploaded to create a new one.  The COM port in the GCM was configured correctly.  The serial cable is also correct and tested with Hyperterminal.  The E: EQUIPMENT SEGMENT in UltiVist is configured correctly and a serial COM port has been added to the W: WORKSTATION & USERS segment.  The UltiVist Background Apps are all running and configured. When trying to access the GCM's Time and Date, an error appears in place of the time and date and reads:  PTP no running. Environment UltiVist GCM-84000 Cause The default settings of the COM port must be modified to suite connectivity to a GCM-84000 which are different than the settings required for a GCM-86000. Resolution Right-click the COM port in the W: WORKSTATION & USERS segment and go to Settings. On the Port Setup tab, ensure the following settings are changed as indicated: IDSR = OFF ODSR = OFF OCTS = OFF DTR = OFF RTS = ON Shut down UltiVist including the UltiVist Background Apps and re-start.  This will re-initialize the serial COM port with the new settings listed above.