Building Automation Knowledge Base

Issue I/A Series Software Compatibility with the Windows 7 Professional Operating System Product Line TAC IA Series Environment Microsoft Windows 7 Professional operating system (32-bit, 32-bit XP Mode, 64-bit XP Mode) WorkPlace Tech Tool (WPT) 5.7 and later PSI / XPSI  4.1 MNCI 4.0 MICROFLO Balance 4.0 PSOPRIF 11.6 Tree Tech 3.1 LON Flow Balance 3.0  Cause I/A Series software should only be run on tested and compatible equipment to avoid problems with software or hardware. Resolution See Product Announcement PA-00163 for detailed information on compatibility of current I/A Series Software tools and Windows 7. (Updated 3-14-12, replaces PA-00114 with PA-00163). See I/A Series (Niagara) R2 Windows Compatibility Matrix for information on the I/A Series (Niagara) R2 compatibility See WorkPlace Tech 5.8.x and 5.9.x Operating System and Microsoft Visio Compatibility for information on the I/A Series Workplace Tech compatibility

Issue The Following error is displayed when attempting to use webUI: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source) at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source) at sun.plugin2.applet.Plugin2Manager$AppletExecptionRunnable.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exception: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet Product Line TAC IA Series Environment Niagara R2 WorkPlace Pro 532 Cause Some servlets which the browser uses were left out of the webUser-2.301.532.jar files. Resolution The plan is to correct this issue in the next maintenance build release. The workaround is to replace the current webUser-2.301.532.jars with the webUser-2.301.530a jars. Reference How to install an I/A Series R2 JAR File.

Issue How can a Viconics BACnet thermostat instance number be changed with Niagara G3? Product Line TAC IA Series Environment Niagara G3, ENS, ENC-520 Cause The device Default Device ID is set to: 7x000+MAC address. The MAC address being the current Mac address of the BACnet device. Example, when a VT7300C5018B thermostat with a MAC address of 7 is connected to a network, its default Device ID will be 73007. There will be Device ID conflicts when the same Viconics model is used on multiple MS/TP networks and uses the same identical MAC address. Resolution How can the instance number be changed in a Viconics BACnet thermostat? lists how to change the Device ID (instance number) via the Viconics thermostat. However, it only allows for change of the MAC address portion of the Device ID. When changing the MAC address portion of the instance number is not enough, Niagara G3 can be used to change the entire instance number. The steps to change the Viconics thermostat instance number are as follows: Open (double-click) the BACnetNetwork Under the Database window, highlight the Viconics stat you want to change the instance number Click on the DeviceID button at bottom of screen and click yes Highlight the DeviceID number and change it to the desired number and click OK This screen show the device number it is being changed from to the device number it is being changed to – click OK If the change was successful, you should get a pop up stating: "Successfully changed remote device ObjectID!"

Issue XIF and Device Resource files for the Schneider Electric SE7000 Series Room Controllers Product Line EcoStruxure Building Expert, Field Devices, TAC IA Series Environment SE7000 Series Room Controller Cause In order to commission Schneider Electric SE7000 Series Room Controllers into an LNS system, the XIF is required. Resolution LonWorks External Interface Files (XIF) SE72_73_PIR.XIF (80:00:10:55:00:04:04:20) SE76_PIR.XIF (80:00:10:55:00:04:04:21) SE76RH_PIR.XIF (80:00:10:55:00:04:04:22) Device Resource File for XIFs listed above. For Datasheets for the SE7000 Series Controllers, see Where to find datasheets and information on the SE7000/SE8000 series room controllers.

Issue Need help with programming Need help to make graphic Installation questions Forum Environment BMS Security Video Cause A great way of getting help with various application programming and graphic making is to spread knowledge between all the great technician out there. A forum exist for this and people worldwide that works with SE Solution share their knowledge here. Resolution Please enter the forum by the link below. http://community.se.com/welcome

Issue Various issues have been observed regarding the use of the I/A Series R2 WorkPlace Pro or I/A Series G3 Graphics access.  The following is a partial list of known issues caused by the Ethernet firewall built into the Trend Micro Internet Security Suite software: When attempting to install an R2 UNC license using the Admin Tool, the error "Unable to install license" is displayed. When attempting to connect to a UNC from the WorkPlace Pro tree, a "Cannot connect" error occurs. When attempting to access G3 graphics using the web browser, the user is unable to log into the station serving the graphics. When attempting to access R2 graphics using the web browser, the user is unable to display the graphics pages. When attempting to paste a .gif file to a UNC's remote library, WorkPlace Pro stops responding and must be closed with Windows Task Manager. When attempting to open a local station on the computer, using WorkPlace Pro, the Windows hourglass is displayed and the station never opens. This list will be updated as additional issues are encountered. Environment Computer running "Trend Micro Internet Security Suite" I/A Series R2 (Niagara) WorkPlace Pro software or attempting to use the computer to view I/A Series G3 (Niagara) graphics. Cause The I/A Series R2 software requires bi-directional communications over Ethernet port 80 unless the software has been user-configured to use a different Ethernet port. The Trend Micro Internet Security Software Suite has a built-in firewall that blocks incoming access to Ethernet port 80.  The Trend Micro software does not allow this port to be unblocked because it considers web access to a "workstation class" computer as a security risk. Resolution The best solution to this issue is to use a different Internet Security software package on the computer that does not block the use of Ethernet port 80.  One approach is to use the "Server" version of Trend Micro Internet Security instead of the "Workstation" version.  Since port 80 is typically used on server systems as the IIS (Internet Information Services) access port, the Server version of the software does not block that port. The alternate solution is to configure the I/A Series R2/G3 (Niagara) software to use a different Ethernet port for HTTP communications and Web services.  This change would need to be made in the R2 or G3 software installed on the computer as well as in every UNC or ENC being accessed from this computer. See New installation of the I/A Series (Niagara) R2 WorkPlace Pro software cannot connect to existing UNC for more information.

Issue Downgrading an UNC to an earlier Niagara build Product Line TAC IA Series Environment I/A Series R2 Universal Network Controller (UNC) Cause Station is unable to run in an UNC with newer version of Niagara R2 because a 3rd party module does not have an updated JAR file Resolution The procedure to downgrade an UNC would be to use the version of WorkPlace Pro that you want the UNC to be and commission the UNC as per what you would do for a new UNC or to upgrade an UNC. The modules installed in the station should also match the Niagara version of the UNC. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330?. Refer to Procedure 4 on pages 9 and 10 of the UNC-520 Installation Instructions for details on installing the software to an UNC-520. It is important to note that newer UNCs with the newer boot flash chip requires I/A Series R2 version r2.301.527 or newer. Installing the UNC with newer boot flash chip with an I/A Series R2 version lower than r2.301.527 will make the UNC inoperable. Refer to Cannot get my I/A Series (Niagara) R2 UNC to boot after downgrading the system software to a version earlier than release 529 for details.

Issue BACnet Service does not start after enabling BACnet IP on a UNC station. The following error messages are seen in the UNC standard output. ERROR: Error initializing IP link layer. [IpLinkLayer.updateLocalAddress] java.lang.NoSuchMethodError: tridium/nre/Platform.getLocalHost()Ljava/net/InetAddress; ERROR: Cannot startService [Sys: BACnetService [12] BACnetService] java.lang.NullPointerException ERROR: Run error [BTrprt] java.lang.NullPointerException Product Line TAC IA Series Environment I/A Series UNC running at version r2.301.5xx prior to version r2.301.535 with BACnet 2.305.535a. Cause Most I/A Series R2 Niagara JAR files are backward compatible. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330? for details.  There were some changes to the BACnet service IP to support the new JACE-603/645 platforms. Because of these changes to the R2 core, the BACnet 2.305.535a JAR file is not backward compatible.  Resolution Upgrade the UNC to version r2.301.535. Refer to the Installation Instructions for upgrade procedure. 

Issue What is the Part Number for the optional battery for the JACE-NXT (TRD-NXT-R2)? Product Line TAC IA Series Environment I/A Series R2 JACE-NXT (TRD-NXT-R2) Cause An optional battery is required for the JACE-NXT (TRD-NXT-R2). Resolution The part number for the optional battery is TRD-NPB-BATT, per the Spec Data sheet for the JACE-NXT, F-27769. There is also an optional UPS that includes a battery, TRD-NXT-UPS, per Hardware platforms to replace the I/A Series R2 UNC-600 or UNC-610. See Product Announcement PA-00223 for further information on the JACE-NXT.   *Update - The NXT platform has been withdrawn. Refer to PA-00373 for details. 

Issue What does it mean on an MNL-800 if both the top green LED (Transmit) and the Amber LED (Receive) are on continuously? Product Line TAC IA Series Environment MNL-50 MNL-100 MNL-200 MNL-800 MNL-V1R MNL-V2R MNL-V3R Cause LEDs indicate LON traffic on the trunk Resolution For an explanation of the Transmit (Green LED) and Receive (Red LED) see F-26724, MNL-800 Installation Instructions, Table 1 LED Indications: LED Operation Status Green ON Normally ON indicating controller is powered and not actively transmitting data on the LON. Flashes OFF Flashes OFF while actively transmitting data on the LON. Amber OFF Normally OFF unless actively receiving data from the LON. Flashes ON Flashes ON while actively receiving data from the LON. Red OFF  (Neuron - normal communications) indicates the Neuron is operating properly allowing normal communications to and from the HVAC application. OFF  (Neuron - Offline) Neuron responds to network management messages only. In this state, communication to and from the HVAC application is not possible. To correct, place the Neuron online by downloading an application using WP Tech or configure using a third party management tool. Blinking The service LED blinks at 0.5 Hz rate (1 second ON, 1 second OFF) to indicate that the Neuron is unconfigured (i.e. communications parameters not loaded). Corrective action: Configure the Neuron by downloading an application using the Work Place Technician's Tool or configure the neuron using a third party management tool. ON Indicates Neuron is not operating properly. Replace controller.  Heartbeat (Green LED) Blinking (Normal Operation) The heartbeat LED blinks at 0.5 second ON, 0.5 second OFF to indicate controller is operating properly. Wink Mode Wink mode provides a visual means for identifying the controller using WP Tech or third party management tool. During wink, the heartbeat LED blinks as follows: With revision 1.x firmware: 2 seconds ON, 0.5 seconds OFF; cycles five times for a total of 12.5 seconds of wink time. With revision 2.x (or later) firmware: 3 seconds ON, 1 second OFF; cycles three times for a total of 12 seconds wink time. Diagnostic Blink (RAM/ROM Failure) The heartbeat LED repeats a pattern of 2 quick flashes followed by pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink (ROM Failure) The heartbeat LED repeats a pattern of three quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. Diagnostic Blink  (RAM Failure) The heartbeat LED repeats a pattern of four quick flashes followed by a pause. To correct, turn power OFF then ON. Replace controller if necessary. OFF Indicates controller is not operating properly. Check power. Replace controller if necessary.      If the amber LED is blinking fast enough, it appears to be ON continuously, so it is receiving data at a high frequency. The other MNL devices on the same LON should all be behaving the same way, indicating a lot of LON traffic. Confirm with a LON protocol analyzer. If excessive LON communications traffic is suspected, see How can LON communications be throttled in MNL-800 controllers? for a method of throttling LON traffic.

Issue Steps in obtaining a Return Authorization (RA) number for a defective Niagara R2 UNC. Product Line TAC IA Series Environment Niagara R2 UNC Cause Failed unit requires repair or replacement. Resolution Before calling Customer Service for a Return Authorization, review the following steps to ensure the unit needs to be sent back to the factory. Symptom: Unit has a constant / steady heartbeat LED A UNC with a steady heartbeat LED indicates that the unit is not booting to the operating system. If a power cycle does not correct, there is not a way to recover without repairing with the factory fixtures. The only alternative is to provide a return authorization for repair or replacement. UPDATE: There are some issues that have been identified since this article was originally published that are field repairable.  To identify these field repairable issues, connect the serial console (see Need to correct invalid IP address or subnet mask entered into a UNC 520), power cycle the UNC and capture the console output.  Provide the console output information when you contact Product Support. Symptom:  Unit has a rapid heartbeat A rapid heartbeat typically indicates a memory issue.  During shipping the memory card has been known to have shifted in its socket. Power the unit down and remove then reseat the memory card in the UNC several times and then power up and monitor. Symptom: Unit is continuously rebooting In a new unit, this continuous rebooting could be a memory issue.  During shipping the memory card has been known to have shifted in its socket. Power the unit down and reseat the memory card in the UNC several times and then power up and monitor. Typically, if the fuse is bad you would see a watchdog or battery failure in the standard output window every 15 minutes or so. The fuse in the UNC-410 and UNC-520 is soldered into the board and is not field replaceable. The UNC-510 fuses are field replaceable.  Remove the shield from the UNC enclosure and remove the board from the shield. The main fuse (F1) is a 5 X 20 mm Fast Acting 1.5 amp 250 volt (Bussman GMA-1.5). The battery fuse is a 5 X 20 mm Slow Blow 2.0 amp 250 volt (Bussman GMD-2A). The battery fuse is the fuse on the right when the power connector is oriented to the upper right. Both fuses are labeled on the circuit board legend. The control board tests the battery’s charge every 5 minutes by placing a momentary short across the battery and monitoring its recovery. A failing battery will cause the unit to reset and reboot when self- tested. Remove the battery red wire and if the unit continues to operate, replace the battery. To test the battery, disconnect the battery and measure the voltage across its terminals with a voltmeter. It should read above 12 Vdc. The charging circuit in all UNCs usually provides a voltage of 13.5 Vdc (approximately).   Replacement battery, part number UNC-500-BAT. Notes: UNC will power itself down within 5 minutes after the power fails. The battery will retain the clock and other dynamic memory data for about 12 hours. A fully discharged battery will recharge in about 12 hours. The life of a battery is 3 to 5 years under normal conditions. Excessive discharge cycles or operation at high ambient temperature (>122F) will shorten the life of the battery. UPDATE: There are some additional issues that have been identified since this article was originally published can cause the UNC to continuously execute a Watchdog Reset and become disabled. See I/A Series R2 (Niagara) station opened in the Admin Tool displays "Disabled"), for more information on this issue. Symptom: AC power failure or Transformer problem The UNC-410 and UNC-520 have an internal transformer. The transformer voltage and wiring should be verified before returning the unit.. This is a center-tap transformer and is wired to the first three terminals on the circuit board connector.  The wires, top to bottom, should be Green, Green Yellow, and Green respectively. The voltage should read approximately 30 VAC Green to Green and approximately half the value (15 VAC) between either Green wire to the Green Yellow wire. Returning unit for repair The symptoms above are a sample of common, sometimes field repairable, failures in a UNC. If the UNC-410 or UNC-520 needs to be sent to the factory for repair, you will only need to return the circuit board (UNC-410-500 or UNC-520-500), not the entire UNC. The printed circuit assembly will be exchanged or repaired and returned. The repaired UNC will come with a 3 month warranty. To issue a Return Authorization (RA#) the factory will need to know the following information: The product part number Is the unit still under warranty? Warranty note: Warranty on a new UNC is 2 years from date of manufacture. The date code format is yyww. Example:  0815 is  2008 week 15 Serial number Job name (site name for unit) Factory order number Project ID Host ID (in the license file) The reason for return Network settings (IP, Subnet, name) Username and Password Station DB Username and Password Any special shipping instructions Have a purchase order number ready when you call. Note: Customer Support Services sends/bills for advance warranty replacement units. When the customer returns the correct unit within 30 days, a credit is then issued., Call Schneider-Electric at 888-444-1311 and select option 2 (Product Support). Product Support will enter a support case identifying the unit and that an attempt to troubleshoot was done prior to issuing the RA number. The caller should request the Product Support Case number and RA number for future reference. An RA will be issued based on the following criteria: Credit AWR (Advance Warranty Replacement). Customer is sending back an inoperable unit to the factory for credit and needs a replacement unit right away. OOWR&R (Out of Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. IWR&R (In Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. NOTE: When issuing an AWR, hold the defective unit and use the packaging from the replacement to return the UNC board. This will help guarantee that the units are not damaged during shipment. When the units are received damaged and improperly packed, they are returned as received and no credit issued. Ship the device to: Schneider Electric 1354 Clifford Ave.   Dock 3 Loves Park, IL. 61111 Attn: Repair Dept. RA ###### Put the RA # on the outside of the box. Include your return address in the box.

Issue Can the XPSI 4.1 software communicate to a GCM via a modem connection? Product Line TAC IA Series Environment XPSI/PSI 4.1 GCM-86xxx GCM-84xxx Cause When capturing trend log data over an unapproved modem, the program lost sync with the incoming data after receiving about 10 lines of log data. Resolution The only modem currently approved for communications with GCMs is the USRobotics 56k (USR5686E). The configuration information for this modem was published in Technical Bulletin 00-47 with model update information published in Technical Bulletin TB03-04. NOTE: If using the USR5686E with older modems, the V.92 communications protocol must be disabled -- see Modems fail to connect with the USRobotics 5686 series V.92 modems for details.

Issue Can an ENC-520 be ordered with 512MB of RAM? Product Line TAC IA Series Environment I/A Series G3 ENC-520 / ENC-520-2-N Cause Need for 512MB RAM in an ENC-520 instead of the standard 256MB RAM Resolution There is no option to order an ENC-520 with 512MB or any other RAM size other than 256MB. New ENC-520s ordered will be of the extended memory version and shipped with 256MB of RAM. Also refer to related Can I upgrade the ENC-410 or ENC-520 memory in the field or return to the factory to have the memory increased?.   

Issue An I/A Series R2 (Niagara) station opened in the Admin Tool displays "Disabled." What does this error message mean? Product Line TAC IA Series Environment An I/A Series R2 (Niagara) UNC. Cause When a station is in the disabled mode, it indicates that the station has rebooted multiple times in a five minute period. Possible causes are rapid fluctuations in the AC power supplying the UNC, a bad battery, or a station with less than 20% idle time. Resolution Disconnect the battery, then cycle power to the UNC and see if it boots up normally. Run the system spy: in a browser, enter  http:// (ipaddress of UNC):3011/system/spy. Login with the hardware user name and password. At the bottom of the page, click on "Reset Counter", then check to see if the idle time exceeds 20%. If not, the station will need to be tuned to increase the idle time. Check battery per Niagara R2/G3 UNC/JACE reboots every 15 minutes with "Battery test failed" logged. See Batteries for the UNC-410 and UNC-520 are interchangeable for battery part numbers.

Issue Since both products -- Xenta programmables and the UNC 520 -- speak LON protocol, there is some assumption that integration should be seamless.  In the case of ASCs, this is true, but Xenta programmable controllers use some forms of proprietary communication that can complicate the integration. Product Line TAC IA Series, TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B UNC-520 Niagara Tridium Cause Xenta programmables use proprietary communications for three main purposes: To communicate their online status between group members and group masters To communicate between a base unit and associated I/O modules To pass proprietary TAC Network Variables between two programmable controllers In a UNC-520, the first function would be taken over by the new network manager (Local Lon Device).  However, the second two must use Group Bindings set through a Vista compatible network management tool like LonMaker or NL220.  If the controllers are commissioned into the UNC-520, that communication will be broken and I/O modules will go offline and no network variables will pass. Resolution  It is possible to engineer a TAC Vista network as usual, using an LNS management tool to create group bindings to facilitate proprietary communications.  A UNC-520, set to non-network management mode could then be implemented on top. However, any attempt to commission the devices into the UNC-520 network will break that proprietary communication.  To prevent this scenario from occurring, the simplest method is: Do not use proprietary TAC Network Variables to pass data between controllers. Use only SNVTs which will be available to a third party LON network manager like the UNC-520 Make no SNVT bindings in a temporary LonMaker or NL220 database.  Let the UNC-520 handle all network management duties. Do not define Xenta I/O modules in the Menta Device Specification. Use only Xenta 421A, 422A, 451A and 452A I/O modules.  These have the capability to act as stand-alone LON nodes. Define the modules as LON nodes, configure them using Configuring inputs on Xenta 421A or 451A when using the controller as a stand alone Lonworks node. Bind to the inputs and outputs of the I/O modules in the UNC-520.

Issue Where are the reports of fixed issues/bugs for the various product lines located? Product Line TAC Vista, TAC INET, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, EcoStruxure Building Operation, EcoStruxure Building Expert, Access Expert, Security Expert Environment Technical Product Announcements Cause TPAs contain information of changes made per version of the different product lines. A TPA may report enhancements and/or broken functionality. Resolution Navigate to Exchange Extranet to view all TAC Vista documents tagged as TPA. The documents will be listed in reverse chronological order. Log in to view these documents. See Register for The Exchange Download Center for more information on registration.

Issue I/A Series G3 Modbus TCP communications to random Modbus devices randomly drop offline and stop communicating with the ENC or Enterprise Network Server.  Both the modbusCore and modbusTcp modules are at version 3.6.31. Product Line TAC IA Series Environment I/A Series G3, Modbus TCP 3.6.47 and lower Cause There were a few updates to the Modbus core and TCP modules between 3.6.31 and 3.6.47. Issue 18656 corrected communication reliability when there are a large number of Modbus TCP devices under a single ModbusTcpNetwork. Issue 19897 corrected transaction ID synchronization when a retry occurred. Issue 23578 added the ability to control the maximum transactionID used for ModbusTcp (I/A Series G3 Modbus TCP communications to Siemens Moore 353 controller stops updating after a period of time after ENC/JACE reboot or station start). Resolution Download the following modules from The Exchange Download Center: modbusCore-3.6.47.1.zip modbusTcp-3.6.47.1.zip Install to the appropriate I/A Series G3 Workbench modules folder Upgrade the modules in the ENC/JACE.

Issue Time Zone Database shows +0 for all time zones when the platform date is in 2016. IA Series G3 version 3.6.407 IA Series G3 version 3.7.108 IA Series G3 version 3.8.41 Product Line TAC IA Series Environment IA Series G3 versions 3.6.407, 3.7.108, and 3.8.41 Cause This error appears when listing the contents of the Niagara Time Zone database where the Time Zone Database shows +0 for all time zones when the platform date is in 2016.  The issue is related to an error within the 3.8.41 baja and hx modules and only affects the display within the Platform view only.  The actual behavior and operation of the Time Zone remains accurate.  Prior IA Series G3 versions (e.g. 3.8.38, 3.7.106, and 3.6.406) or earlier will not exhibit this issue. Resolution Download and upgrade the baja and hx modules available in the latest consolidated patch files. baja 3.6.407.3 (or higher) and hx 3.6.407.1 (or higher) baja 3.7.108.3 (or higher) and hx 3.7.108.1 (or higher) baja 3.8.41.2 (or higher) and hx 3.8.41.1 (or higher) The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area (reference Latest consolidated patch files for I/A Series G3 maintenance builds with details).  Download and install the appropriate patch for the version.

Issue Where to obtain the documentation for I/A Series G3 software. Product Line TAC IA Series Environment I/A Series G3 software and hardware Cause Documentation is provided as a part of the software package.  Resolution The current documentation for any release of the I/A Series G3 software (except for proprietary drivers) is installed with the full software installation.  The documentation can be found in the docs folder under the \Niagara\niagara-x.x.x\ installation folder. Refer to Documentation for the I/A Series G3 Schneider Electric proprietary drivers for information on the availability of the I/A Series G3 Schneider Electric (TAC) proprietary driver documentation.

Issue I/A Series G3 weather service will not connect - error indicates java.net.SocketTimeoutException: connect timed out.  A browser on the same computer is able to access www.weather.gov without issue.  The application director output window displays the following ... WARNING [12:56:28 05-Dec-13 EST][weather] Updating forecast failed for Battle$20Creek java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at javax.baja.naming.BIpHost$SocketFactory.open(BIpHost.java:271) at javax.baja.naming.BIpHost$SocketFactory.open(BIpHost.java:264) at javax.baja.naming.BIpHost.openSocket(BIpHost.java:129) at javax.baja.net.HttpConnection.connect(HttpConnection.java:263) at javax.baja.net.HttpConnection.connect(HttpConnection.java:238) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java:76) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java:55) at com.tridium.weather.nws.NwsForecastReader.getForecast(NwsForecastReader.java:135) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:450) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:269) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1357) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server ENC JACE Cause The connection timeout may be related to the proxy server.  By default, the weather service driver contacts the various weather.gov sites (alerts.weather.gov, graphical.weather.gov, etc.) directly as opposed to routing through the proxy server.  The connection times out as the proxy server is unable to route the request. I/A Series G3 (3.4 and higher) provides a service that can be added to the station.  The HttpProxyServer service is used to configure the station so that outbound web services know how to get through an outbound non-transparent proxy server.  The HttpProxyServer service located in the net module. Configure this service to the proxy server that will be routing. The user guide states the following. All services that make use of the bajax.baja.net.HttpConnection class will automatically roll over to using the proxy server once the HttpProxyService has been configured and enabled. The Weather Service is one of the services that is affected by this feature. Resolution Verify the updated weather modules are installed, see Weather information provided through the weather module in I/A Series G3 is no longer updating. weather-3.4.67.3 or higher weather-3.5.39.5 or higher weather-3.6.37.4 or higher To use this component: Open the net (Network API) module in the Workbench palette. Add the HttpProxyServer to the Services of the station. Configure the following properties in the Property Sheet view as required.     Status - This display only property displays the status of the Http Proxy Service. Fault Cause - This display only property provides an error message that indicates the reason for a fault. Enabled - This property has a true (enabled) and false (disabled) option. Server - This property provides a text field for entering the address of the proxy server you are connecting to. Port - This property is for specifying the port number for communicating with the proxy server. Exclusions - This text field allows you to designate addresses that are allowed to be contacted directly, therefore “excluding” them from having to be contacted through the proxy server. The default addresses in the field are typical addresses followed by a slash (/) and the subnet mask designation. Authentication Scheme - This property provides the following two options:      None - no authentication is required at the proxy server when this option is set.      Basic - basic authentication is required at the proxy server when this option is set. User - This is the login name to be used when authentication is set to Basic. Password - This is the password text that is to be used when authentication is set to Basic.