Building Automation Knowledge Base

Issue Importing of AutoCAD .dwg files fails to import into StruxureWare Building Operation Grahics Editor Environment StruxureWare Building Operation site Cause Importing of AutoCAD .dwg files fails to import into StruxureWare Building Operation Grahics Editor Resolution It is the third party library Leadtools that fails to convert the file. The files in question are constructed with version post 2010 but our Leadtools library is from 2006. To fix this issue the Leadtools library needs to be updated. This will be fixed in a future release. The dwg drawings will need to be saved in an earlier release for compatibility with Graphics Editor.  

Issue WorkStation will play audible alarms but the same alarms will not play in WebStation Product Line EcoStruxure Building Operation Environment Building Operation WebStation   Cause Alarms can be viewed in WebStation but they do not have audible alarm sounds.  Resolution Audible alarms are available in WebStation from 3.2 onward.   See online help topic: WebStation and WorkStation Differences - EcoStruxure WebHelp

Issue Seeing a pop up warning message when updating modules or making changes to an online Controller. “It has been detected that your programming contains links between controllers, but the firmware on one or more of these controllers does not support this. Therefore the manual command you are trying to perform may not behave as intended. Are you sure you wish to continue?” Figure1 - Pop up message Product Line EcoStruxure Security Expert Environment Security Expert Client SP-C Cause Configured Programmable Functions are trying to query the state of inputs on expander modules but this is failing due to one or all of the expander modules being offline. Resolution Bring all the expander modules online and the error message will no longer be seen.

Issue How to check the amount of used memory in a TAC Menta/TAC Xenta application. Product Line TAC Vista Environment TAC Menta Xenta 281 Xenta 301 Xenta 401 Cause When programming applications for TAC Xenta, you may want to be able to check the size of your application, to verify that it can be downloaded to the device. Resolution To be able to check how much memory an application is using, the application needs to generated. In TAC Menta, edit mode: Select Option, Simulate to enter Simulate mode. In Simulate Mode, select Commands, Generate, to generate the application. To be able to check the Memory usage, you have to return to Edit mode, Select Options, Edit. Now you can check the Memory usage by selecting Options, Memory Usage... As this calculation is done on your PC, and not in the device, and that the memory in the TAC Xenta device is dynamic allocated, it is a recommendation to have at least 10% free memory in each category to avoid future problems. For more information about the Advanced button, please see TAC Menta Advanced Memory Usage: BPR Size Calculator.

Issue Sigma controllers that have been cold started do not recover correctly. Product Line EcoStruxure Building Operation, Sigma Environment Sigma Server Building Operation Enterprise Server Cause Having imported a Sigma database into the Sigma Interface on the Enterprise Server, and following a controller cold start, Sigma controllers fail to fully recover. The controller correctly receives the Backup server number, but fails to request the data from the Sigma Server. Resolution This issue is resolved as follows; Data Import the Sigma Data. Stop and restart the Enterprise Server using the Software Administrator Cold start a controller to confirm that it fully recovers. Note: A  restart of the Enterprise Server will be required again if any new additional controllers are to be added to the Enterprise Server. This workaround only works for ARM7 controllers, for V53 devices, the Sigma 4.08 (3.46.79) Hot Fix is available on the Download Centre and needs to be installed at the Sigma Server machine. Note; this hotfix is a separate item to any other Sigma hotfix and the correct Sigma Transition Tool version needs to be installed.

Issue There is a display issue with PE programs running in a b3 device, depending on program code the current line shown maybe incorrect showing a line that is NOT the line the program is currently at, this issue exists in all versions of SBO. Note that program execution is not effected, the execution of the program iscorrect, it is only the CL shown that maybe incorrect. Issue will be fixed in SBO 1.6 Environment Workstation AS b3 Cause Firmware defect Resolution The defect has been corrected and the fix will be released in SBO 1.6 Currently there is not hot fix available for this issue.

Issue When an old OGC graphic is converted to a TGML graphic in TAC Vista the conversion will fail if the name of the OGC graphic is longer than 36 characters. The OGC to TGML converter will just close with no error message. Product Line TAC Vista Environment Vista Workstation Cause The OGC to TGML converter does not support OGC graphic names longer than 36 characters, but if you try converting with longer names, the converter just closes down without any error message indicating why the conversion failed. This is a defect in the OGC to TGML converter which is reported to R&D. Resolution Rename the OGC graphic to a name with 36 characters or less.

Issue Schedule configured with occupied events that spans mid-night, yet the schedule is going unoccupied at mid-night. Schedule has been configured to apply occupied event at mid-night but it appears this functionality is not working as expected. Environment Cyberstation bCX b3 Cause Documentation Resolution Add occupied event at mid night to override the internal unoccupied event that is placed at mid-night.

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 for assistance. Issue After switching the recovery model from Full to simple, the shrink task fails to shrink the transaction log file. Product Line Continuum Environment Continuum Microsoft SQL Server Cause A transaction log cannot be shrunken while there is a process actively accessing the log file. Resolution Use the log_reuse_wait_desc function in a SQL query to help you identify the process that is preventing the shrinking of the transaction log. Open SQL Server Management Studio.  Click on the New Query button. In the query window type the following SQL statement: SELECT log_reuse_wait_desc FROM sys.databases WHERE name = 'ContinuumDB' Note: The name in single quotes should be the name of the Continuum Database. In some cases, it may have been changed to something other than "ContinuumDb." This query will return one or more of the following keywords.  Each of the following keywords indicates a transaction log process that is taking place. Here is a list of keywords that could be returned. NOTHING CHECKPOINT LOG_BACKUP ACTIVE_BACKUP_OR_RESTORE ACTIVE_TRANSACTION DATABASE_MIRRORING REPLICATION DATABASE_SNAPSHOT_CREATION LOG_SCAN OTHER_TRANSIENT For example, if this query were to return REPLICATION, this would indicate that the replication process has control of the transaction log.  In that case you might investigate the replication configuration or perhaps even turn replication off temporarily to successfully shrink the log. You can find a detailed description for what each keyword indicates by searching the following website Eight Reasons Transaction Log Files Keep Growing

Issue Structured SNVTs disappear from database following a LearnNv. Product Line TAC IA Series Environment G3 versions 3.6.406, 3.7.106, 3.8.37 Cause Modifications made to the LonWorks jar. Resolution Download and install the new LonWorks jar for the revision in question. See Lonworks 3.8 to obtain the latest LonWorks modules.

Issue When a user logs on to Workstation and accesses the hyperlink, the website is displayed without prompt for login credentials Product Line EcoStruxure Building Operation Environment Building Operation Workstation Microsoft Internet Explorer Cause EcoStruxure Building Operation software uses Microsoft Internet Explorer to present web pages. How the page logs on is an IE function and not a function of EBO Workstation Resolution  Log off from the web site before logging off from Workstation  Configure Internet Explorer to delete browsing history on exit Go to Internet Explorer settings and then the Internet Options On the General tab, under the Browsing history, enable the checkbox for 'Delete browsing history on exit' (computer restart may be required)

Issue WebReports returns only partial results for the Consumption Report when using the Meter Utility Type   Product Line EcoStruxure Building Operation  Environment Building Operation Report Server Building Operation WebReports Cause This is a limitation of the Meter report, where the report returns approximately 50 Meter reports at a time regardless of how many meters are selected. Resolution It is recommended that 30 - 40 meters at most be selected at a time for this report.  Selecting more meters for the report may result in data overlap and unexpected output. For more information regarding Consumption Reports, see the following help topic Energy Monitoring Reports

Issue In some cases, if the block connected to reset (rs) of a Run Time (RT) block is a trigger (TRIG) block, the RT block will never reset. Environment Menta Xenta Cause If the order of the TRIG and RT block is not correct, the RT block will miss the pulse from the TRIG block. This only seems to happen when the block connected to the TRIG block is a PV block such as PVB. If the block connected to the TRIG block is e.g. a physical input such as DI the problem doesn't occur. Resolution There are two solutions to this problem Solution 1: Create the blocks in the correct order First create the "TRIG" block and then create the "RT" block. If you already have both, then delete the "RT" block, save and create a new "RT" block. Solution 2: Add a DELB block Add a "DELB" block before the "TRIG" block. This will make the "TRIG" block hold the signal long enough for the "RT" block to detect it.

Issue Missing "restore" option when right-clicking on my Enterprise Server even though logged in as admin user. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and above Cause The admin user is member of multiple groups. The software permissions within that group have deny access set to Server Restore as well as other commands. Resolution Move the 'admin' (or Administrator) user to only be a member of the Administrator group and not any other groups otherwise you need to ensure that the correct permissions are set to each group and the correct users are assigned to those groups. For further detail of User Permissions in SmartStruxure Solution refer to following How software permissions work in SmartStruxure.

Issue Unable to access to JACE-645 via its Ethernet Port. The following is seen when connected to the JACE's Serial Shell. Product Line TAC I/A Series Environment JACE-645 (TRD-T-645) Cause The boot sector of the nand flash has become corrupt and/or the nand flash chip may have failed. Resolution The unit cannot be recovered in the field. The options are: An attempt can be made to re-image the unit but this may not be always successful. Contact Product Support for further details. Replace the unit. Refer to PA-00502 - End of Commercialization for JACE 600 and JACE 700 for replacement options.

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 for assistance. Issue How are the pull down lists populated in the Personnel Manager for fields such as Department, Hair Color etc? How to edit/remove entries from those lists. In the screen shot below the site has changed the name of a department from 'Technical Support' to 'Product Support', how to go about removing the old department name from the list. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Cause Documentation Resolution The 'Department List' is populated from the department column of the Personnel table, the Personnel Manager walks the column and adds to the list any department name string that is not already present on the list. Since the list is dynamically populated from that database, to remove an entry from the list, all instances of personnel objects that have been assigned to that department must be changed until no personnel object remains with a department string equal to the string that we want removed from the list. In cases where only a few personnel objects are assigned to the department string to be removed, we can manually edit those personnel objects and change the department. In many cases the manual approach is not practical due to a large number of personnel objects that will need to be manually modified, in such cases the change can be made directly in the SQL database using the following query. ***** MAKE SURE TO HAVE A FRESH BACKUP OF THE DATABASE BEFORE MAKING ANY CHANGES DIRECTLY IN SQL **** update personnel set department = 'Product Support' where department = 'Technical Support'--------------------------> To rename an entry on the list. update personnel set department = NULL where department = 'ISIS'------------------------------------------------------------> To remove an entry on the list. Note the all personnel assigned to ISIS department will now have a BLANK department

Issue How do I locate the consolidated patch files (modules) for the I/A Series G3 maintenance builds (3.6.406, 3.7.106, 3.8.37).  Please note:  I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center and include all updates for the previous builds. Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.406, 3.7.106, and 3.8.37 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution Please note:  New I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center.  The new builds already include the consolidated patches listed below. Below the latest consolidated patch files for I/A Series G3 maintenance builds 3.6.406, 3.7.106, 3.8.37 are listed.  The files contain updated modules and a set of release notes.  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 or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.406_SE_05272015.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.10 bajaui 3.6.406.3 control 3.6.406.1 docMbus 3.6.406.5 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 kitLon 3.6.406.1 lonworks 3.6.406.5 mbus 3.6.406.5 modbusCore 3.6.406.3 modbusSlave 3.6.406.2 modbusTcp 3.6.406.2 modbusTcpSlave 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 obixDriver 3.6.406.1 opc 3.6.406.1 pdf 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 report 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.9 workbench 3.6.406.3 Consolidated_Patches_3.7.106_SE_07242015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.10 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.3 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5       Consolidated_Patches_3.8.37_SE_07242015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.10 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.39 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.3 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.11 workbench 3.8.38.5 zwave 3.8.38.1   ********* Previous Release History ********* Consolidated_Patches_3.6.406_SE_09112014.zip  ...  Click here for Release Notes alarm 3.6.406.2 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2 Consolidated_Patches_3.6.406_SE_11112014.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2   Consolidated_Patches_3.7.106_SE_09112014.zip   ...  Click here for Release Notes alarm 3.7.106.5 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_11112014.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_01222015.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.14 baja 3.7.106.8 bajaui 3.7.106.5 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 hx 3.7.106.2 kitControl 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.3 mbus 3.7.106.4 modbusCore 3.7.106.1 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.3 weather 3.7.106.1 web 3.7.106.16 workbench 3.7.106.5   Consolidated_Patches_3.7.106_SE_05272015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.9 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5         Consolidated_Patches_3.8.37_SE_09112014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.6 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_10012014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1       Consolidated_Patches_3.8.37_SE_11112014.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.6 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_01222015.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.9 baja 3.8.38.6 bajaui 3.8.38.2 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 hx 3.8.38.3 kitControl 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.3 mbus 3.8.38.4 modbusCore 3.8.38.1 modbusTcp 3.8.38.2 nDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.3 web 3.8.38.7 workbench 3.8.38.2 zwave 3.8.38.1 Consolidated_Patches_3.8.37_SE_05272015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.9 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.38.1 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.2 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.10 workbench 3.8.38.4 zwave 3.8.38.1 bajaui 3.8.38.2 bajaui 3.8.38.2 baja 3.8.38.6 baja 3.8.38.6               obixDriver 3.7.106.4 alarm 3.7.106.5 alarm 3.7.106.5 alarmOrion 3.7.106.2 hx 3.8.38.3 hx 3.8.38.3 hx 3.8.38.3   gx 3.8.38.1 gx 3.8.38.1 gx 3.8.38.1   hx 3.8.38.3   kitLon 3.8.38.1 kitLon 3.8.38.1   nDriver 3.8.38.1   nDriver 3.8.38.1

Issue Right after successfully creating a simple XML Web Service all the values show 0 and the Web Service is offline Product Line EcoStruxure Building Operation Environment Simple XML Web Service Workstation Enterprise Server Automation Server Cause Possible cause 1: SmartStruxure Workstation can handle URL's both with and without the final forward slash even if the URL is just an IP address and a port number. The ES or AS can't handle that, and so after creating the variables through Workstation, the Web Service goes offline after it is added to the server. Possible cause 2: The XML file or response is not UTF8 encoded but "UCS-2 LE BOM" encoded or something else. Resolution Solution 1: Add a final forward slash to the Web Service URL - e.g. http://localhost:8000 should be http://localhost:8000/ Solution 2: Make sure the XML file is correctly encoded in UTF8 - you can check and change the encoding with e.g. Notepad++

Issue Is it possible to 'hot swap' IO modules? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation I/O Modules Cause Some critical applications require 24-hour operation. Resolution The I/O modules allow hot-connection of terminal bases and hot-swapping of the modules to their bases. This design ensures continuous power and communication during service operations.

Issue UPC Barcodes and EAN Barcodes Environment Site ordering parts from Schneider-Electric Cause What are UPC Barcodes and EAN Barcodes Resolution The EAN contains a 13 digit number and the UPC contains a 12 digit number. EAN = 0012345678905 UPC = (0)012345678905 or 012345678905 GS1, the original source for barcodes has created the confusion between UPC (Universal Product Codes) and EAN (European Article Numbers also called International Article Numbers) Below is an example of a Schneider Electric SHR110 room RH/Temp sensor: