Issue Application Director output window and LON proxy point indicates fault: java.lang.ClassCastException: javax.baja.sys.BDouble ERROR [14:56:22 20-Aug-14 EDT][lon1] Could not decode nv update data Misc9:nvoSpaceTemp java.lang.ClassCastException: javax.baja.sys.BDouble    at javax.baja.lonworks.londata.LonFacetsUtil.makeLonQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.LonFacetsUtil.getQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.BLonData.primitiveFromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromNetBytes(BLonData.java)    at javax.baja.lonworks.BNetworkVariable.receiveUpdate(BNetworkVariable.java)    at com.tridium.lonworks.NvManager.receiveLonMessage(NvManager.java)    at com.tridium.lonworks.loncomm.NLonComm.routeToNvListener(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonComm.receiveLonMessage(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonLinkLayer$AppBufferReceive.run(NLonLinkLayer.java)    at java.lang.Thread.run(Unknown Source) Environment I/A Series G3 (all versions) Cause This error is related to a mismatch between the lonworks module running on the ENC/JACE versus the version being used within the Workbench modules folder.  A different version of Workbench and/or lonworks module is being used to engineer the ENC/JACE. Resolution Review the versions between the Workbench and ENC/JACE and match the versions.

Issue TGML graphic uses the NAM Standards component to display a SmartX Sensor Device with a dynamic cover model. The graphic always shows a blank faceplate instead of the correct face - 3 buttons, LCD, or Touchscreen. Product Line EcoStruxure Building Operation Environment SmartX Sensor Device (Living Space Sensor/Room Unit Device) NAM Standards Team Components TGML Library TGML Graphic Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Cause A script running inside the graphic component is expecting a well-formatted string representing the cover model on the cover model input binding. If that data is not delivered properly, the component defaults to a blank cover. Resolution Verify that the proper component is being used based on Sensor Firmware. Verify the proper IP controller firmware is installed to meet compatibility with the Host Server and also contain desired features. Once a controller is upgraded and the sensor has had time to upgrade, check the Sensor - Properties - Basic Tab - Application Software version. If greater than or equal to 1.02.05, then use Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Otherwise use Thermostat - SmartX Living Space Sensor - Dynamic   The TGML component should work as expected, but factors outside of the graphic can make it not work right. Click on the SmartX Sensor Device and look at Properties > Basic > Status Information > Cover model. Does that show a valid cover model (ex: SXWSCBXSELXX) or does it show ASCII gibberish? If showing nonsensical ASCII string, hotfix firmware is available to address this. Install firmware at or higher than 3.02.03.02109, which includes fix for Defect# 46054 and 47266 affecting the Cover Model SmartX IP Controller v3.02.03.02109 - Firmware Package File Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=6b61d413-5cf8-47c0-ac4d-135391d375bf&title=SmartX%20IP%20Controller%20v3.02.03.02109%20-%20Firmware%20Package%20File Release Notes v3.02.03 - SmartX IP Controller Firmware Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=1e29da8d-cf49-418d-92e5-e022bc4f33c7&title=Release%20Notes%20v3.02.03%20-%20SmartX%20IP%20Controller%20Firmware If the Cover Model is populated with a proper value, a previous firmware upgrade may have caused string values to stop writing properly through the TGML binding. There are two different resolutions to try in this order: Restart the AS-P Delete the SmartX Sensor Device (be sure to select "Keep references") and add it back as a new object with the same name and address.   The binding controlling the dynamic display of different cover models on the graphic can be overridden. Inside the TGML component are 3 groups named "3 Button," "LCD", and "Touchscreen." All are hidden. Find the proper face and change it to default to Visible. Find the Bind named "CoverModel" and delete the binding and script beneath it. This is what is responsible for auto-changing the cover and is no longer needed.

  Issue For an AS-P running on EBO 4.0.3.176, in Device Administrator, it is showing the State-Ready (Device crash logs available). When trying to download the debug info, it populates the below error and does not get rid of the logs.   ERROR: Failed to run devadmin3 command cmd with arguments -u -m devadmin3 --sa -v cmd 172.20.214.78 -b *** "rm -f /var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz" :rm: can't remove '/var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz': Permission denied   Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Not running Device Administrator correctly Resolution When opening Device Administrator, ensure to run as administrator as below. This will clear device logs.  

Issue Access Event Viewer running in a CyberStation other than the primary access server works initially but after some period of time stops displaying access events. Product Line Andover Continuum Environment CyberStation MSMQ Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Product support has identified several scenarios that can result in Cyberstations other than the primary not showing events in the Live Event Viewer. The commonality with all these cases is that the Primary Access Server(PAS) will always show the events, so before using any of the solutions specified below make sure that is ONLY workstations other than the PAS that are not displaying events in their Live Event Viewer   NOTE also, that we are referring strictly to the Live Event Viewer in this article so it is assumed events are showing in a list view including the Access Events tab that shows events in the door's editor.   CAUSE #1 (Primary failed over to Secondary then back to Primary) In systems configured with a Primary and secondary Access Server (SAS), it has been found that after a failover to the SAS due to the PAS going offline, event viewers in other workstations continue to show events UNTIL the PAS WS returns online and resumes its role of PAS at which point all workstations (other than the PAS) stop displaying events in their Live Event Viewers.   CAUSE #2 (MSMQ issue reported and fixed by Microsoft) Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at Cyberstations other than the PAS do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Please see MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   ISSUE #3 MSMQ CleanupInterval setting is too short. Resolution SOLUTION #1 First, make sure the ControllerStatus notification object is configured to send the offline alarm to all the Workstations in question. Second, put a PE program in the SAS to serve as a monitor to let the Live Event Viewer know when the PAS has returned online, this is accomplished by referencing an object from the PAS  SAMPLE PE POGRAM SOLUTION #2  (MSMQ issue reported and fixed by Microsoft) Click MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   SOLUTION #3 In the Windows registry add the key \SOFTWARE\Microsoft\MSMQ\Parameters\CleanupInterval The recommended setting is 3600000 which is the number of milliseconds in an hour   For additional information about the CleanupIntervalKey, see the following article from Microsoft: http://msdn.microsoft.com/en-us/library/ms703235(VS.85).aspx

Issue What HHC (Hand Held Console) cable do I need to connect to a DCU, UCI, or PCU? Product Line TAC INET Environment I/NET HC7410 HHC (Handheld Console) Cause Can not locate documentation to indicate which cable is required. Resolution Original HHC: The part number is 602135-0003. It is a six foot (or 1.8 m) coiled, silver modular cable. Refer to the appropriate controller TCON for more details.   HHC (Hand Held Console) is also called the HC7410. Refer to TCON 073 for more details. Updated USB HHC: This is the replacement for the HHC. TCON318 has more information. The HHC-USB-IF cable allows you to connect the hand-held console (HHC) port of a TAC I/NET device to the USB port of a PC. You can then use the HHC emulator running on the PC to configure the I/NET device’s controller LAN address, tap emulation, baud rate settings, monitor and control points, and perform the other typical local maintenance functions supported by the earlier HC7410 console product. The HHC-USB-IF cable can be used with the model 7716, 7718, 7756, 7780, 7790A, 7700, 7740, and 7750 Distributed Control Units (DCUs), and the model 7760 UCI

Issue Configuring NTP and troubleshooting in the Niagara Frameworks Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace Cause Guide to configure and test NTP server and Jace sync operations Resolution Please familiarize yourself with the official documentation of the NTP functionality. NTP and its configuration are comprehensively documented in the Niagara Platform Document. The official documentation is updated frequently and may contain information that supersedes the content of this article. Using the ntpq utility program The NTP Project maintains the NTP software that is compiled and included with Red Hat Enterprise Linux (and other most other Linux distributions). To get the software for Microsoft Windows, Meinberg ports the software and provides it. With this software, you not only get the ntpq utility program, you also can run the NTP client/server on your PC. In this way, you can use your PC as an NTP time server to your JACE. NOTE: The Client and Server (Time Only) options were added in 4.9. Using Server creates potential attack surface for 'Mode 6' queries. But to query with ntpq as described below, it must be set to Server, at least temporarily. Be advised that you should not have your JACE exposed to the Internet. Consult the Niagara Cyber Defense page for more details. Using the ntpq utility program, you can query a JACE that is configured for NTP, and get a list of the peers known to the JACE and a summary of their state. For this use the -p option, and provide the IP address to the JACE. The command will look like this: ntpq -p 192.168.1.140 The output of the command will look something like this: The ntpq man page at ntp.org fully documents the details of the table above. Only a few details will be covered here.  The row that begins with * (asterisk), has been declared the system peer. The second row begins with a space, indicating that it is an unreachable peer.  The third column is for the stratum. Stratum 0 is an actual time source, like an atomic clock, that provides time to a stratum 1 NTP server. A stratum 2 server gets its time from a stratum 1 server. A stratum 3 server gets its time from a stratum 2 server, and so on.  Reach is a circular log buffer containing a set of eight bit-flags, expressed as an octal number. Convert octal to binary to determine the reach for the last eight attempts. For example, 376 converts to 11111110, which means that we failed to reach the server the last time, but the other 7 were successful.    Using the NtpPlatformServiceQnx spy page Right-click the NtpPlatformServiceQnx and select Views > SpyRemote.         As you scroll down the first section of interest is the one that shows the NTP Configuration File. It reads what we've written to the file ntp.conf and displays it.                                          NTP Configuration File #/home/niagara/etc/ntp.conf: Niagara Network Time Protocol Configuration File #Use the NtpPlatformService UI to modify this file. #Created: 24-Sep-19 4:53 PM EDT # #Niagara NtpPlatformService variable, do not modify #ntpEnabled true #syncAtBoot true #server list server 192.168.1.2 burst prefer server 192.168.1.3 burst server 192.168.1.4 burst peer 192.168.1.5 peer 192.168.1.6 #ntp features enabled enable ntp stats #ntp panic value, if offset exceeds this, ntpd should exit (disabled if 0) tinker panic 0 #gather information about statistics statistics clockstats loopstats filegen clockstats file clockstats type none nolink enable filegen loopstats file loopstats type none nolink enable The next section of interest is for the NTP Daemon Log. You'll only see this section if Generate NTP Statistics is set to true. It's generally not necessary to consider these statistics.                                                       Generate NTP Statistics Jan 30 08:45:14 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd161a.aa0c9b85 Jan 30 08:46:14 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd1656.2b9be356 Jan 30 08:46:18 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd165a.aa0c9453 Jan 30 08:47:18 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd1696.2b9bca8b Jan 30 08:47:22 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd169a.aa4e33f0 Jan 30 08:48:22 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd16d6.2b9bd269 Jan 30 08:48:29 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd16dd.aa8fa9b9 Jan 30 08:49:27 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1552.126c471e does not match aorg 0000000000.00000000 from sym_active@172.16.10.99 xmt 0xe1dd1717.2b9bcbe9 Jan 30 08:49:34 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1553.126c40f0 does not match aorg 0000000000.00000000 from sym_active@172.16.10.197 xmt 0xe1dd171e.aad12b7e Jan 30 08:51:18 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd1203.21caf133 does not match aorg 0xe1dd175e.153d05cf from sym_active@172.16.11.205 xmt 0xe1dd1786.c4cb59c2 Jan 30 08:51:33 nto ntpd[8740900-1]: receive: Unexpected origin timestamp 0xe1dd11bb.218961dc does not match aorg 0xe1dd175c.153d0991 from sym_active@172.16.10.171 xmt 0xe1dd1795.1de9a94c Jan 30 08:51:40 nto ntpd[8740900-1]: receive: KoD packet from 172.16.10.158 has a zero org or rec timestamp. Ignoring. Jan 30 08:52:44 nto ntpd[8740900-1]: receive: KoD packet from 172.16.10.158 has a zero org or rec timestamp. Ignoring. The next section is NTP Daemon Drift. After NTP has synchronized with reliable time servers for a significant amount of time, it will write the calculated drift (in PPM) to a file, such that it can initialize with this value on reboot. It will use this calculation of how far the clock drifts, to correct the clock in real-time, in increments too small for any application to detect.   NTP Daemon Drift 20.185   NTP Daemon Clock Stats is next. It reads what is in the clockstats file. In this example output, the file does not exist and the spy page tells us so.                                                     NTP Daemon Clock Stats Modified Julian Day | Secs. Past UTC Midnight | Clock Address | Last Time Code Error reading /var/run/ntpdstats/clockstats: /var/run/ntpdstats/clockstats (No such file or directory) The final section of interest is NTP Daemon Loop Stats. If you're not getting data here, then the configured servers/peers might not be reachable.    NTP Daemon Loop Stats Modified Julian Day | Secs. Past UTC Midnight | Time Offset Secs. | Drift Compensation | Estimated Error | Stability | Polling Interval 58860 29871.775 0.000000000 20.226 0.000976563 0.000000 6 58860 30081.780 0.000753215 20.226 0.000976563 0.000000 6 58860 30150.781 0.000753034 20.226 0.000976563 0.000000 6 58860 30688.793 0.000018819 20.227 0.000976563 0.000213 6 58860 31155.803 -0.000220479 20.220 0.000976563 0.002179 6 58860 31221.804 0.002128888 20.229 0.001234668 0.003595 6 58860 31233.872 -0.001539013 20.228 0.001736532 0.003385 6 58860 31385.925 -0.000336908 20.225 0.001679057 0.003345 6 58860 31498.941 0.000431773 20.228 0.001608116 0.003294 7 58860 31841.815 0.000467697 20.230 0.001543370 0.003195 7 58860 32276.675 0.000795988 20.235 0.001484403 0.003499 7 58860 32546.942 0.009518751 20.274 0.003382136 0.013979 7 58860 32666.611 0.000412569 20.274 0.004513791 0.013078 7  

Issue Are usernames and passwords encrypted during transmission from the Remote Client or Web Client to the Sigma Server? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause There is a need to understand the security measures in place for credential transmission between clients (Remote and Web) and the Sigma server, particularly regarding encryption. Resolution   Usernames are not encrypted during HTTP transmission from either the Remote Client or the Web Client to the Sigma server. Passwords are encrypted during HTTP transmission from both the Remote Client and the Web Client to the Sigma server.  

Issue How many client licenses are currently used? Which host is using the licenses? Product Line EcoStruxure Building Operation Environment Licensing Cause Information about license usage is needed to ensure licensing is adequate. Resolution Information about current license usage can be found in the FlexNet License Administrator found on the server where the Building Operation License Administrator is installed. FlexNet License Administrator has a web interface accessed through a web browser. The address is the server address and port 8888. If on the license server go to: http://localhost:8888 If on a remote machine to access the FlexNet License Administrator go to: http://[license server ip address]:8888 Once accessing the FlexNet License Administrator, switch to the Concurrent licenses view by clicking on the Concurrent icon. Scroll down to the client.station in the Feature column. The column In Use (Available) shows the number of client licenses used. (The number of client licenses available is displayed in parentheses). (Click on Hosts to display a list of hosts taking client licenses.)

Issue Unable to see EWS objects/points under an EcoStruxure Web Services interface Product Line EcoStruxure Building Operation Environment EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause An EWS License may be needed to allow your ES/AS to use EcoStruxure Web Services Resolution Purchase and install an EWS License if required.     Note: The EWS option is NOT required when using EWS to integrate between two Schneider Electric systems or services. Refer to PA-00349 for details.   This includes the new Smart Connector by Schneider Electric which does not require an EWS License but does require a Smart Connector License as usual

Issue After installing a new SQL server and installing CyberStation on a workstation PC, Database Initialization is unable to connect to the database. Product Line Andover Continuum Environment SQL Database Initialization Cause The Database has not been assigned with a correct owner. Resolution In SQL Server Management Studio, highlight ContinuumDB. Right Click on ContinuumDB. Select "New Query" In the query field type SP_ChangeDBOwner 'Andover97' Run the query Once the query returns Success, it should be possible to Initialize the Database successfully.

  Issue PCT v1.3.3.75 fail to start SmartX server in versions 1.8.x and 1.9.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Defect, user can create SmartX server v1.8.x and 1.9.x but the servers can't start properly. Resolution Uninstall PCT v1.3.3.75 Install PCT v1.3.2.110 (Download), (Client Installer) Install server packages 1.8.x and 1.9.x

Issue How is time synchronized between the Controllers and Security Expert Server?  Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controllers (SP-C, SP-ACX, SP-AC1, SP-DCU) Cause Require details on different ways the Controllers can have their time set. Resolution There are two methods for synchronizing time on the Controllers. Periodically updated by the SNTP Time Server configured under the controllers Time Update tab. SNTP Time Server The controller polls its SNTP Time Server every 11 minutes.) A third-party NTP server such as Meinberg NTP, can be used. These servers synchronize with four or more internet time sources and are considered reliable. Ensure that UDP Port 123 is open on any firewalls, as this port is required for NTP communication. Without an SNTP Time Server configured, time is updated on the Controllers by the following methods. Time is updated manually by the Operator right-clicking the controller and selecting Set controller date/time. This will set the controllers time to the current time of the Workstation. Set Controller Time Time is updated to the server time whenever a “Force Download” is initiated for that controller. Force Download

Issue Is a Vista license necessary for I/NET Host tool features or is the I/NET CD key sufficient? What is the difference in the I/NET Integrated and I/NET Security licenses? Environment Vista Server I/NET Host Tool Cause The I/NET Host tool requires a Vista license file to run. Certain editors and features in the I/NET Host Tool are common to both the Integrated and Security license. Some features are specific to the Integrated or Security license. To have all of the features purchase of both licenses is necessary. AMT is not included with the I/NET host tool product as Vista is expected to handle alarms messages and transactions Common Features System features Change password Connect/Disconnect Logon/Logoff Quit Work offline Host features Host configuration editor Host password editor Host phone numbers editor Host software restore editor Netcon function editor Network configuration editor System view Tap features Host, link, and site tap configuration Site tap remote configuration Site tap save/restore Controller features 7720 configuration editor Action messages summary Alarm extension editor Calculation editor Control description editor Conversion coefficient editor DCU configuration editor DCU save editor DCU restore editor DCU password editor DPU configuration editor Engineering units editor Event extension editor Event sequences summary I1/I2 state parameters editor Lighting circuits editor Lighting zones editor LCD page definition editor Lookup table editor MCU configuration editor MR configuration editor Resident point editor Special days editor State descriptions editor Time schedule extension editor Trend extension editor Trend plot view dialog Summaries Configuration summary Controller summary Disabled points summary Off-normal points summary Reporting features SevenReports (operates in view-only mode if no I/NET CD key is installed) I/NET Integrated only Controller features Consumption extension editor DDC modules summary Demand control extension editor MR DDC summary Override billing equipment mapping editor Override billing extension editor Override billing parameter editor Runtime extension editor Temperature control extension editor Unitary control configuration editor Unitary control extension editor I/NET Security only Controller access features Elevator extension editor DCU AIC editor Door extension editor Personnel schedules SCU parameters editor Host access features Access control options editor Access control wizard AIC editor Door extension editor Groups editor Individuals editor Key translation editor Personnel schedules Pin generation dialog Recycle bin SCU editor Tenant editor User search Summaries Door tenant summary Resolution Purchase of an I/NET Host Tool license is necessary for the integration with Vista Workstation to function. Use the feature list to determine if only one license or both licenses are required by the customer. Attached is the PA for all the required software Here

Issue The EBO system previously operated as expected with Active Directory (AD) integration. Following an upgrade or hotfix, AD users are unable to authenticate and log in to the Enterprise Server (ES). Workstation login error: User account not associated with a group The Workstation Error when trying to login is: User account not associated with a group.     Error(s) message in ES trace log may include: WinES\server\nsp_servers\csc\accountaccess\source\AccountAccess.cpp(486) Workstation Error: User_Not_Associated_With_A_Group (0xc002a) in module Account_Access(28). Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The Windows AD integration performance in EBO was improved since version 2022 by storing and comparing the SID for the AD-groups. During the upgrade from version 3.2.3 to EBO 2022 all EBO groups should have been updated with an AD-connected group SID. This was not done as the AD server was offline when doing the upgrade of the ES. Resolution To enable the legacy method of matching groups during logon, configure the following property: Steps: Open the ES.properties file, typically located at: C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\etc\config Add the following line: NspServer.Windows.Group.MatchByName = true Save the file and restart the Enterprise Server for the changes to take effect.     To take advantage of the Active Directory (AD) performance enhancements introduced in recent versions of EcoStruxure Building Operation, it is necessary to re-establish the link between AD groups and their corresponding EBO groups. Procedure: Open the relevant EBO group configuration. Locate the Windows group name property. Temporarily change its value to an empty string or any placeholder text. Re-enter the correct value, which should match the associated AD group name. Save the changes to complete the re-connection process.   Completing the previously described procedure ensures that the hidden External SID property for the EBO groups is correctly populated. This property was not updated during the upgrade because the process was performed without an active connection to the AD server.  

Issue Clarify the differences between I/A Series R2 time zone settings such as CST vs CST6CDT or PST vs PST8PDT, and how they compare to America/City time zone entries.  Product Line TAC IA Series Environment I/A Series R2 UNCs and Enterprise Servers Cause Time zones in I/A Series R2 can be specified in multiple formats: Abbreviations (e.g., CST, PST) Abbreviation with daylight savings offset (e.g., CST6CDT, PST8PDT) Region-based identifiers (e.g., America/New_York, America/Chicago) These variations exist because of different ways to represent location and daylight savings rules. Resolution All three formats represent the same time zone and daylight savings schedule for U.S. regions: Region Abbreviation Abbreviation + DST America/City Format Eastern Time EST EST5EDT America/New_York Central Time CST CST6CDT America/Chicago Mountain Time MST MST7MDT America/Denver Pacific Time PST PST8PDT America/Los_Angeles Daylight Savings: Starts: 2:00 AM, second Sunday in March Ends: 2:00 AM, first Sunday in November For areas without daylight savings or with unique rules: Use America/City (e.g., America/Phoenix for Arizona, America/Indianapolis for parts of Indiana). For fixed offsets without daylight savings, select Etc/GMT±xx (e.g., Etc/GMT-5 for UTC-5).

Issue Is it possible to rename an ES after an AS has been created? Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation 1.9 and lower Enterprise Server Automation Server Cause Not possible to rename the Enterprise Server or Automation Servers once attached as a multi-server system Resolution It is not possible in the earlier revisions 1.9 and lower to rename an ES or an AS once created under an ES. From EcoStruxure 2.0 and above this is possible;  Refer to WebHelp for additional details: Server Rename

Issue Xenta Controllers can report "offline" status if they encounter bandwidth limitations Completion Event Failure warnings CRC Errors showing in controller properties Loytec Multi-port router/switch channel LED blinking fast red (traffic overload) Product Line TAC Vista Environment Lon Networks Vista Xenta LPA Loytec Protocol Analyzer Cause HMI Vista on-line/off-line presentation is based upon receipt of the heartbeat messages. Every TAC Xenta 280/300/401 controller is periodically sending a message to the other members of its TAC Xenta reporting (including the group master) that it is on-line. Proprietary "LACNet-IAm" and "LACNet-GroupIs" are sent every 15 seconds to HMI Vista. Without the HMI receiving these heartbeats, Vista will display the controller or group in an offline state. The TAC Xenta group is specified by the tag_0 and the TAC Group is specified by tag_1 bindings in LonMaker or NL220. Resolution Actions for reducing Bandwidth: TAC Xenta 100s Slow down the SendHeartBeat Check sensors etc that are affecting all bound nvo's Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. 3rd Party LonWorks devices Change update rates for nvo's. If possible, the product manual should show how. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. TAC Xenta 280/300/401 TACNV and SNVTs Verify delta and period values make sense for the particular signal and application. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. Increase the trend log time span (the total log time) if possible. Of course, this will increase the memory usage in the Xenta, but this will make TAC Vista to do the fetch more seldom and result in reduced traffic. TAC Xenta 280/300/401 + TAC Xenta I/O Modules If sensitive sensors (i.e. pressure sensors) are connected to I/O Modules, a high load of communication will be generated. Bandwidth issues may arise when 401s with many I/O Modules are each reading multiple sensitive sensors. Increase the Min Send Time for every I/O Module. Min Send Time is how often the I/O module is allowed to communicate with the TAC Xenta. This setting is located in Device Specification in Menta. Reduce Trend Log definitions in the controllers. If possible, try to have all your "high speed sensors" connected to one, or a few I/O modules, so it's only a few I/O modules sending a lot to the Xenta. LonWorks routers Implement L-Switch routers to reduce traffic on high bandwidth segments. Set router to Configured Mode, not Repeater Mode. Vista Server Trend Log Stagger Vista server Trend Log start times so that they do not all attempt to get fetched at once. See also Troubleshooting LON Network Communication More information can be found in Tool for LON / LPA Capture Traffic Analysis (login required) which discusses the LPA Analyzer Tool. This may be useful for interpreting the LP file data.

Issue The following errors are in the Windows Application Event Viewer: Email, Failed to send email - MAPILogonEx failed in InitSession function!, Result is 80040111 Email, Failed to send email - Email (MAPI) initialization failed in InitSession function!, Result is 80040111 Email, Failed to send email - InitSession failed in CACEmail::Init, Result is 80040111 Product Line Andover Continuum Environment CyberStation 1.9x Cause If the errors are only logged on startup of CyberStation then they are not likely an issue. However, if these are being logged more than just on startup they may indicate other issues, such as RPC errors. Resolution If you are not emailing alarms these errors may be able to be stopped. Run a listview [1] of all EventNotifications and display the AlarmOptions attribute. Check if the word email shows up. Edit the EventNotifications where it does show up and remove all emailing from the Actions tab. CyberStation creates some of these EventNotifications in the templates folder and they are setup for emailing by default.

Issue After the TAC Menta file has been downloaded all other IO modules operated normally but one IO module will not come online Product Line TAC Vista Environment Xenta401 XENTA301 XENTA281 Cause If the IO module that will not come online has IO points set up in it, then chances are one of the points is set up incorrectly. For example, it may be referencing a Universal Input, but in an Analog Output only IO controller. This is typically caused by changing the IO module from its original type. The TAC Menta was not updated correctly after the change and an analog input was left referencing an analog output in the new controller. Resolution Check all the points in the affected controller for correct and valid references. Once corrected download the controller. TAC Xenta I/O modules do not come online after a download from System Plug-In is a related article.

Issue TS-57XX and TS-67XX 10 K thermistor (no 11 K shunt) sensor resistance table Environment Site with thermistor sensor Cause TS-57XX and TS-67XX 10 K thermistor (no 11 K shunt) sensor resistance table Resolution   Temp (°C) Temp (°F)  Sensor Ohms  -40.0° -40.0° 239,700 -39.0° -38.2° 226,000 -38.0° -36.4° 213,100 -37.0° -34.6° 201,100 -36.0° -32.8° 189,800 -35.0° -31.0° 179,200 -34.0° -29.2° 169,300 -33.0° -27.4° 159,900 -32.0° -25.6° 151,200 -31.0° -23.8° 142,900 -30.0° -22.0° 135,200 -29.0° -20.2° 127,900 -28.0° -18.4° 121,100 -27.0° -16.6° 114,600 -26.0° -14.8° 108,600 -25.0° -13.0° 102,900 -24.0° -11.2° 97,490 -23.0° -9.4° 92,420 -22.0° -7.6° 87,650 -21.0° -5.8° 83,150 -20.0° -4.0° 78,910 -19.0° -2.2° 74,910 -18.0° -0.4° 71,130 -17.0° 1.4° 67,570 -16.0° 3.2° 64,200 -15.0° 5.0° 61,020 -14.0° 6.8° 58,010 -13.0° 8.6° 55,170 -12.0° 10.4° 52,490 -11.0° 12.2° 49,950 -10.0° 14.0° 47,540 -9.0° 15.8° 45,270 -8.0° 17.6° 43,110 -7.0° 19.4° 41,080 -6.0° 21.2° 39,140 -5.0° 23.0° 37,310 -4.0° 24.8° 35,580 -3.0° 26.6° 33,930 -2.0° 28.4° 32,370 -1.0° 30.2° 30,890 0.0° 32.0° 29,490 1.0° 33.8° 28,160 2.0° 35.6° 26,890 3.0° 37.4° 25,690 4.0° 39.2° 24,540 5.0° 41.0° 23,460 6.0° 42.8° 22,430 7.0° 44.6° 21,440 8.0° 46.4° 20,510 9.0° 48.2° 19,620 10.0° 50.0° 18,780 11.0° 51.8° 17,980 12.0° 53.6° 17,210 13.0° 55.4° 16,480 14.0° 57.2° 15,790 15.0° 59.0° 15,130 16.0° 60.8° 14,500 17.0° 62.6° 13,900 18.0° 64.4° 13,330 19.0° 66.2° 12,780 20.0° 68.0° 12,260 21.0° 69.8° 11,770 22.0° 71.6° 11,290 23.0° 73.4° 10,840 24.0° 75.2° 10,410 25.0° 77.0° 10,000 26.0° 78.8° 9,602 27.0° 80.6° 9,226 28.0° 82.4° 8,866 29.0° 84.2° 8,522 30.0° 86.0° 8,194 31.0° 87.8° 7,879 32.0° 89.6° 7,579 33.0° 91.4° 7,291 34.0° 93.2° 7,016 35.0° 95.0° 6,752 36.0° 96.8° 6,500 37.0° 98.6° 6,258 38.0° 100.4° 6,027 39.0° 102.2° 5,805 40.0° 104.0° 5,592 41.0° 105.8° 5,389 42.0° 107.6° 5,194 43.0° 109.4° 5,007 44.0° 111.2° 4,827 45.0° 113.0° 4,655 46.0° 114.8° 4,490 47.0° 116.6° 4,331 48.0° 118.4° 4,179 49.0° 120.2° 4,033 50.0° 122.0° 3,893 51.0° 123.8° 3,758 52.0° 125.6° 3,629 53.0° 127.4° 3,505 54.0° 129.2° 3,385 55.0° 131.0° 3,271 56.0° 132.8° 3,160 57.0° 134.6° 3,054 58.0° 136.4° 2,952 59.0° 138.2° 2,854 60.0° 140.0° 2,760 61.0° 141.8° 2,669 62.0° 143.6° 2,582 63.0° 145.4° 2,498 64.0° 147.2° 2,417 65.0° 149.0° 2,339 66.0° 150.8° 2,264 67.0° 152.6° 2,191 68.0° 154.4° 2,122 69.0° 156.2° 2,055 70.0° 158.0° 1,990 71.0° 159.8° 1,928 72.0° 161.6° 1,868 73.0° 163.4° 1,810 74.0° 165.2° 1,754 75.0° 167.0° 1,700 76.0° 168.8° 1,648 77.0° 170.6° 1,598 78.0° 172.4° 1,550 79.0° 174.2° 1,503 80.0° 176.0° 1,458 81.0° 177.8° 1,414 82.0° 179.6° 1,372 83.0° 181.4° 1,332 84.0° 183.2° 1,293 85.0° 185.0° 1,255 86.0° 186.8° 1,218 87.0° 188.6° 1,183 88.0° 190.4° 1,149 89.0° 192.2° 1,116 90.0° 194.0° 1,084 91.0° 195.8° 1,053 92.0° 197.6° 1,023 93.0° 199.4° 994 94.0° 201.2° 966 95.0° 203.0° 939 96.0° 204.8° 913 97.0° 206.6° 887 98.0° 208.4° 863 99.0° 210.2° 839 100.0° 212.0° 816 101.0° 213.8° 794 102.0° 215.6° 773 103.0° 217.4° 752 104.0° 219.2° 732 105.0° 221.0° 713 106.0° 222.8° 694 107.0° 224.6° 675 108.0° 226.4° 658 109.0° 228.2° 640 110.0° 230.0° 624 111.0° 231.8° 607 112.0° 233.6° 592 113.0° 235.4° 576 114.0° 237.2° 562 115.0° 239.0° 547 116.0° 240.8° 533 117.0° 242.6° 520 118.0° 244.4° 507 119.0° 246.2° 494 120.0° 248.0° 482 121.0° 249.8° 470