Building Automation Knowledge Base

Issue Extended Jace 9000 Commissioning Time. Product Line TAC IA Series Environment I/A Series Jace 9000 Cause With the release of the Jace 9000 using Ubuntu Core 20 Linux as it’s operating system the commissioning/upgrade times increase as compared to the previous Jace 8000. Initial commissioning times can take longer then 15 minutes to finish. There are scenarios where multiple reboots are needed after the initial commissioning is completed. Once the commissioning has been completed for the Jace 9000, boot times should be significantly lower. Resolution Users will need to reboot their Jace at least twice and will need to set more time aside for commissioning of the new Jace 9000s. Please allow for a minimum of 15 minutes for commissioning. If you continue to experience issues with bootup or commissioning on the Jace 9000,  please contact your country level product support. Please note that the JACE-9000 does not print a lot of output on the debug port when you cycle power so give it time to fully bootup.

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 It may be necessary to replace the Security Expert Server and/or the Security Expert Software Product Line EcoStruxure Security Expert Environment Security Expert Cause In case of upgrade, software issues or PC/Server hardware failure replacing the Security Expert Server may be needed Resolution 1. Hardware Reset If the server footprint changes, for example, the previous server’s hard drive or motherboard died, then a hardware reset will be required before the license can be used on the new server. Contact Schneider Electric Product Support to tell them that your server hardware profile will be changing and a hardware reset is needed. 2. Stop the Security Expert services Right-click on the service and select Stop Note: While the services are stopped, the controllers will save incoming events (up to 50,000 per controller). Once that limit is reached, the events are First in First out. 3. Back up the SecurityExpert and SecurityExpertEvents databases If the database is encrypted, export the encryption certificates. See the Security Expert Installation Manual for specific instructions on backing up and restoring databases and encryption certificates. https://ecoxpert.se.com/search?documentUUID=71d622e3-2fc1-477a-b08a-5b37ac4b2756&title=SX-SRVR%20Security%20Expert%20-%20Client%20Server%20-%20Installation%20Guide  4. Uninstall Security Expert from the old server From Windows Programs and Features, Right-click Security Expert> Uninstall Once the Uninstall is complete, Manually Restart the Server/PC 5. Disconnect the old server from the network. Connect the new server with the same IP address and/or hostname. If the IP address or hostname of the server changes, update the event server settings in the controllers via the controller’s web page to match the new server. 6. Install Security Expert on the new server and activate the license Ensure that the new Security Expert installation is the same version or higher. 7. Stop the Security Expert services Restore the encryption certificates and databases to the new SQL Server instance. 8. Updating the Database If you are restoring a database from an older version to a later version, uninstall and reinstall Security Expert to upgrade the database. 9. Start the Security Expert Data Service 10. Update the Download Server In Security Expert, navigate to Global | Download server and update the Computer name to match the new Server name. 11. Update the Event Server Computer name in Global | Event server 12. Restart the Security Expert Event Service You should start receiving events from controllers 13. Start the Security Expert Download Service

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 For hardware failure or persistent issues, it is necessary to replace Security Expert hardware components Product Line EcoStruxure Security Expert Environment Security Expert SP-C or SP-C-Web controller Expanders (i.e. RDM2 or SP08) Card Readers Cause A hardware failure occurs or a persistent issue happens that requires steps to replace Security Expert hardware Resolution At times it's necessary to replace Security Expert hardware   Steps to replace Security Expert SP-C Controllers: 1. Determine if the original controller has encryption turned on If the failed controller was setup for encrypted communications with the Security Expert server, the newly installed replacement controller will not have the encryption keys to be able to decode the packets from the server. Attempting to bring it online will be unsuccessful. On the controller's Configuration tab press the Disable controller encryption, then Yes to confirm. A replacement controller will typically be unencrypted. As soon as it shows online you can decide if you want to encrypt it. If it was already encrypted in Security Expert before replacing it, you might need to hit the encryption button again to get it in sync. Note: It can be helpful to use the event server diagnostic. If you see messages including “unencrypted” set encryption on the controller and see if it comes online. 2. Disconnect the old controller from its networks unplug ethernet and RS-485 module network and other hardware 3. Replace the Serial Number in Security Expert In Security Expert, navigate to Sites | Controllers. Replace the Serial number of the old controller with that of the new one. 4. Disable encryption In the Configuration tab, click Disable controller encryption. 5. Default the Controller If the controller has been used on a different server, default the new controller. See the SP-C Installation manual for detailed steps on performing a controller default https://ecoxpert.se.com/search?documentUUID=b4fb1237-fd07-2ee5-d9ad-4324178c364c&title=SP-C%20Security%20Expert%20-%20Security%20Purpose%20Controller%20-%20Configuration%20Guide  6. Enter the event server settings on the controller Log in to the new controller's web interface. In Settings, enter the same IP settings, event server and ports as those of the old controller, then restart the controller. Note: Remember to remove the jumper used to default the controller 7. Connect the new controller to the networks and hardware The controller should come online in Security Expert if all the network settings, serial number and encryption settings are in sync. 8. Download the controller In Security Expert, right click on the controller record and select Force download. The controller should receive the download. 9. Enable encryption Once the controller is online, in the Configuration tab click Enable controller encryption in Security Expert if desired. Steps to replace Security Expert SP-C-Web Controllers: 1. Take a backup of the old SP-C Web controller Login to SP-C Web, In System | Backup controller This creates a .bak file prompting to save in a folder or in the downloads folder 2. Disconnect the old controller Unplug the controller from the ethernet network, the RS-485 module network and other hardware. 3. Register the new controller Log in to the new controller and register it in System | Licensing 4. Restore the previous backup taken Navigate to System | Backup and Choose File and browse to the previously created .bak file 5. Configure the IP settings In System | Settings, enter the same IP settings as those of the old controller, then restart the controller 6. Connect the new controller to the networks and hardware and Test Steps to replace Security Expert Expanders: 1. Disconnect the old expander from the RS-485 module network and any inputs, outputs or card readers. 2. Connect the new expander to the module network and hardware. 3. Set the new expander's address to the same as that of the old expander.  In Security Expert, navigate to Sites | Controllers, right-click the controller and select Module addressing.  In SP-C-WEB, use the Expanders Wizard. To address a keypad, power cycle it and then press [X], [Enter]. Enter the new address and press [Enter] to save. Note: Sometimes the old expander can remain in the module addressing window even after being physically disconnected. To free up the address, module update the expander record. This will fail, but the address should become available. 4. Module update the new expander. The expander should start operating normally using the programming from the original expander. Steps to replace Security Expert Card Readers: 1. Disconnect the old card reader from the reader port. 2. Connect the new card reader 3. Apply any Custom Configurations If the reader needs any custom configuration, apply it within two minutes of the reader starting up using the config card. 4. Wiegand and RS-485 readers should connect automatically For OSDP readers, put the card reader into installation mode, then send an OSDP install mode command to the reader expander.   Additional configuration after controllers have been replaced If used at the site, areas that are configured for duress alarms default to un-armed after a SP-C has been replaced and need to be re-armed via forced arming. If used at the site, the alarm dialer (Contact ID) "Service Mode" defaults to "0 - Manual Mode" after a SP-C has been replaced (see the arrow below) and needs to be changed to "1 - Start with controller OS". Service mode Test the replaced hardware to ensure the issue is resolved

Issue Is there a way to reset the password for web access to a BCX? Product Line Andover Continuum Environment Continuum site with passwords other than the default Cause The password was changed by mistake. Resolution Restore the controller's user names, passwords and configuration settings to the original factory values (Reset IP button using a two stage operation) The location of the Reset button and the Reset IP button on the controller board. Page 124 in appendix A of the Technical Reference Guide. If you cannot get into Continuum Explorer and edit the controller user under that controller and set the password. You will have to reset the controller and then re-commission and then reload.  Try acc/acc first and then after that the following: Using the Reset IP button The Reset IP button has two stages of operation: Stage 1 is initiated by depressing the button for 5 seconds. After 5 seconds, the IP address, and all network-related addresses entered on the Network Configuration page, are returned to the original factory default values. Stage 2 is initiated by depressing the button for 35 seconds. After 35 seconds, the database is cleared and all persistent configuration data is erased, with the exception of the error log. Note: Depressing the button for 35 seconds performs both operations, setting the IP address back to the factory default setting and clearing the database. When you initially depress the Reset IP button, the CPU Indicator LED will begin blinking. At 5 seconds, the LED will stop blinking and remain lighted in a continuous state. If you release the button before 5 seconds has passed, no changes are made. If you release the button after 5 seconds, but before 35 seconds, stage 1 is executed, but stage 2 is not. The IP address has returned to the original factory value, but the database has not changed. Please see Default IP address for BCX, ACX57xx, CX9702 and Netcontroller II for information on default IP addresses.

Issue Does TreeTech version 3.1 & 3.2 support all block types in all types of GCMs and LCMs? Product Line TAC IA Series Environment TreeTech version 3.1 or 3.2 GCM-84xxx GCM-86xxx SIM-xxxxx LNC GIM-2100 LCM-8xxxx Cause Block types supported are not listed in the Tree-Tech Engineering Guide document, F-26640 Resolution The following table lists the sub-devices supported by TreeTech 3.1 or 3.2 for each Network 8000 device type. GCM (rev 4.x & 5.x) ASDGCM (rev 4.x & 5.x) GIM-2100 / SIM-GCM (All rev)  LCM (rev 4.x)  LCM (rev 4.x)  MICROZONE-II  LCM (rev. 5.x)  LCM (rev 5.x)  PEM    MICROZONE-II  LIM    PEM      LIM   The following table lists the block types supported by each device family.  GCM 4.X ASD-GCM 4.X GCM 5.X ASD-GCM 5.X GIM-2100 SIM-GCM LCM 4.X/5.X AI AIPLC ALARM AO AOPLC APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DIPLC DO DOPLC DPT EDL EMS ENTHL FLOW HILO HOLI LIMIT LOGIC LOOP MATH MOMEN MTR MZHP1 MZONE MZRT1 MZSAT MZST1 OSS POLL PULSE PWM RAMP RESET RLCM RNET SEQ SGCM SLECT SNET SYS TOTAL TREND TSTAT VVBOX WEEK   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LIM LIMIT LOGIC LOOP MATH MOMEN MTR OSS PEM1 POLL PWM RAMP RESET RLCM RNET SEQ SGCM SGRP SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WEEK ZONE2   AI AIPLC ALARM AO AOPLC APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DIPLC DO DOPLC DPT EDL EMS ENTHL FLOW HILO HOLI LABEL LIMIT LOGIC LOOP MATH MOMEN MTR MZHP1 MZONE MZRT1 MZSAT MZST1 NIM NSCHD OSS POLL PULSE PWM RAMP RESET RLCM RNET SEQ SGCM SLECT SNET SYS TOTAL TREND TSTAT VVBOX WEEK   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LABEL LIM LIMIT LOGIC LOOP MATH MN MNFLO MOMEN MTR NIM NSCHD OSS PEM1 POLL PWM RAMP RESET RLCM RNET SEQ SGCM SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WEEK Z2HSC Z2SCH ZONE2   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LIM LIMIT LOGIC LOOP MATH MOMEN MTR OSS PEM1 POLL PWM RAMP RAV21 RDS21 RDV21 RESET RNET SEQ SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WAV21 WDV21 WEEK ZONE2   ALARM AO APT BTUH CALEN CNTR1 CNTR2 COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LABEL LIM LIMIT LLLB1 LOGIC LOOP LWC1 MATH MN MNFLO MOMEN MTR NIM NSCHD OPM1 OSS PEM1 POLL PWM RAMP RECP1 RESET RMA1 RNET ROOF1 SEQ SGRP2 SIM SLECT SNET SYS TOTAL TREND TSTAT UNTV1 WEEK WMA1 WSHP1 Z2HSC Z2SCH ZONE2 AI ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DO DPT EDL EMS ENTHL FLOW HILO HOLI LABEL LIMIT LOGIC LOOP MATH MOMEN MTR NSCHD OSS POLL PULSE PWM RAMP RESET RGCM SEQ SLCM SLECT SYS TOTAL TREND TSTAT WEEK   NOTE 1: Refer to the table at the beginning of chapter 4 of the GCM/LCM Programmer's Manual, F-23120, for more information on what object types are supported in specific versions or types of controllers. NOTE 2: The block types listed for the "GIM-2100 / SIM-GCM:" encompass the blocks supported by all the devices of the group.  You will be able to create any block type listed however, an error will be displayed when you attempt to download an unsupported block type into a specific controller in the GIM-2100 / SIM-GCM family.  Please refer to the controller manual (LNC, SIM-York, SIM-Trane, SIM-CCN, SIM-MTech or GIM-2100) for information on the block types supported by that controller type. The following ASD device blocks are supported by TreeTech. MICROZONE II PEM LIM AO DO EMS HOLI LOOP OSS RESET RGRP SCHED SEQ UI UTIL WINDO AO AS AT AV DI DO EMS LOOP RESET RGRP SEQ UTIL WINDO EMSA EMSD HOLI OVI RGRP RO SCHED UTIL WINDA WINDD  

Issue What is the procedure for upgrading the I/A Series G3 software in an I/A Series ENC? Product Line TAC IA Series Environment I/A Series G3 Workbench software on computer (both the old version and new version need to be installed on the computer) I/A Series G3 ENC-520 or ENC-410 Cause Need to upgrade the software that is installed in the ENC. Resolution With the old version of Workbench running on the computer, backup the station running in the ENC.  All required graphic files, etc., stored in the ENC should also be backed up.  Note the station folder name for use in step 5, below. Verify that the license in the ENC is compatible with the new release to be installed. If not, use the License Manager (under the Platform) to install an updated license. If the correct version of the license is not currently available, it must be obtained and installed prior to beginning step 6, below. If the new release of the I/A Series G3 software has not already been installed on the computer, install it now. Verify that the Workbench computer has a license that is version compatible with the new release of the I/A Series software to be installed.  If the license is not version compatible, acquire a new license for the Workbench computer before continuing. Copy the entire named station folder (used in step 1) from the old release Stations folder to the new release Stations folder.  See NOTE below regarding the installation of a version downgrade. Run the "Install Platform Daemon" command from the Windows Start Menu folder for the new version of the software. Open the Workbench in the new version of the I/A Series G3 software and connect to the platform of the ENC to be upgraded. From the Platform menu, open the License Manager and verify that the ENC license has been updated to allow use with the new version of the I/A Series G3 software. Right-Click on the ENC platform in the Workbench tree and select Commissioning Wizard. Complete the commissioning process as documented in the Niagara AX Install and Startup Guide . On the first screen, select the operations to be performed.  The required minimum operations will normally be checked and shown in grey.  The "Install a station..." option needs to be checked if not already checked. Click [Next] to begin the commissioning process.  Continue through the various steps, as required.   When prompted, select the station copied in step 5. When prompted, verify that all required modules are available and are selected for installation. Allow the commissioning process to complete, following the prompts as required. The upgrade is now complete.  Start the station as required. NOTE: Do not use the process to directly downgrade the version of software installed in an ENC.  You must use the Platform "Distribution File Installer" to install the appropriate clean distribution (from the cleanDist folder under the software version to be installed.  Typically, only one clean distribution file will be available to be installed.  Select that file then click the [-> Install] button to downgrade the ENC software.  This process needs to be done as noted in step 5, above, after backing up the station but before beginning the commissioning of the device with the older I/A Series G3 software version.

Issue Using provisioning Niagara to schedule (automated) ENC station backup Product Line TAC IA Series Environment I/A Series G3 (AX) version 3.3 and above Cause The station in an ENC (Enterprise Network Controller) can be copied to the ENS (Enterprise Network Server) computer for backup. This can be done by a user using the ENC's Platform Station Copier. There is a need to have an automated process to back up the ENC's station periodically. Resolution Use provisioning Niagara and configure an automated station backup. Provisioning Niagara means an administrator can configure the Enterprise Network Server automation of the following: one or more pre-defined tasks (station backups, install software, update licenses, and copy files) against one or more (potentially many) stations in its Niagara Network done from the Enterprise Network Server in a way where results are recorded and can be referred to later. Refer to this document for a summarized procedure. You should refer to the technical document 'Niagara Ax 3.5 Provisioning Guide for Niagara Networks' for detailed information on using provisioning in Niagara. This document is included with the installation of the I/A Series G3 software and it is located in '\niagara\niagara-3.x.xx\docs\docProvisioningNiagara'. 

Issue While attempting to activate a purchased license, the entitlement ID shows that it is valid, but there is no available licenses that can be activated, or less available than listed on the entitlement certificate. The entitlement ID or certificate is lost. Unable to return the license in order to activate it on another PC Getting "This Operation is not applicable for Trusted Fulfillments" Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In order to activate a SmartStruxure license, it must be available and unused. If a license is already in use, it needs to be returned before it can be activated. Note that all handling of licenses are to be carried out using the License Administrator. Licenses are not returned or rehosted as it was done for TAC Vista. Resolution Refer to WebHelp article #6687 for instructions on how to return a license If you are unable activate a license because you don't have the entitlement ID or certificate, note the activation ID before you return the license, and send that to Product Support Services in order to get the associated entitlement ID Launch the License Administrator Go to the Diagnostics tab and click the refresh icon in the top left corner. The entry in the list that is labeled Entitlement ID is actually the Activation ID. In the case that the computer has crashed or you are unable to successfully return the license on your own, contact Product Support Services providing the following details: A copy of the entitlement certificate The site name An elaborate explanation of why you are not able to return the license yourself

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 Need to create PCT backup Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause Users need to backup all PCT data to prevent data loss or corruption. Resolution Since PCT 2.0 virtual machine resides in Hyper-V., the process is the same as backup any VM in Hyper-V Manager. Open Hyper-V Manager: Launch the Hyper-V Manager application on your server. Select the VM: Navigate to the virtual machine you want to back up in the left pane. Right-click and choose "Export": Right-click on the VM and select "Export" from the context menu. Choose a destination: Select the folder where you want to save the exported VM files. Start the export process: Click "Export" to begin the backup process. The "Export" process will create a "pct" folder from the folder in step 4. The 3 folders under "pct" folder are the backup for PCT 2.0 with projects and server packages installed.      

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 Need to move PCT storage file to another location Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The hard drive where the storage file resides may be full, or the space may be allocated for another purpose Resolution It's suggested to create a backup before proceeding, follow How to backup PCT 2.0 data to create a backup.   Open Hyper-V Manager Select "pct" under Virtual Machines then click "Move..." from the right-hand side menu Move "pct" Wizard Window will pop-out, click Next Select "Move all of the virtual machine's data to a single location" then click Next Select the NEW location for PCT then click Next. Check if the location is correct, then click Finish. Hyper-V will initial the process Once the Status shows the progress finishes. Click "Shut Down" from the right-hand side menu for "pct" image   Click "Stop Service" from the right hand side menu to stop Hyper-V as we need to modify the file location for PCT settings file   Open Windows Explorer and go to C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool Open the "settings" file Replace the old folder location with the new one then Save the file (I changed the folder from 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool' folder to 'D:\PSS\PCT 2 storage' Before modification After modification Go back to Hyper-V then click Start Service   Select "pct" then Click Start   Wait for a couple of minutes for the VM to start Go to https://192.168.10.2/ in a browser and PCT will start with all the existing projects

Issue Do IP settings go to defaults when flashing from 4040 to 9640? Product Line Andover Continuum Environment bCX9640 bCX4040 Cause Have a need to flash a controller from bCX4040 to bCX9640 over a remote connection access. Do not want to have to go to the site to reset IP settings.  Resolution Using CyberStation v1.93 a bCX4040 was flashed to a bCX 9640 and it did NOT lose its IP info. Notes: At the end of the upgrade an error was received: “The uprev could not communicate with the specified controller”. From the webpage it was noted that the IP address had not changed and the upgrade was successful. It did not come back online in CyberStation. From the webpage, resetting it still did not bring it back online in CyberStation. Changing the model number in CyberStation to bCX9640 (from bCX4040) to bring it back online was not an option. The flash upgrade had reset the ACCNetID to 1. The 4040 was then deleted (Bacnet side first then Infinity side) and a new 9640 was created. The proper ACCNetID was set up in the webpage and the changes committed. It was then online in CyberStation. Bottom line – IP address never changed. ACCNetID did. The controller never had to be touched during this process so remotely doing this is expected to work. This was only tested using the latest firmware and CyberStation v1.93. Of course, the best way to do this is on the bench not on a live system. Please be aware that the model flash change will cause node count and/or xdriver upgrades to be reset if they were added as post-factory-shipment upgrades (via the Repair Dept) since these upgrade UPD files are model specific. See Node or XDriver Upgrade of BCX Inf (9640) to BCX BACnet (4040) or reverse. Also see Update b3 or i2 OS, changing (converting) a controller, BACnet to Infinet or Infinet to BACnet .

Issue Due to a variety of reasons it is sometimes necessary to add an offset to the value obtained from a sensor to achieve the required accuracy. For example, a temperature sensor may be reading off by 0.5 degree as compared to a calibrated high accuracy temperature measuring device used as a standard. Product Line Andover Continuum, EcoStruxure Building Operation Environment All CX controller All i2 devices All b3 devices Cause Sensor tolerance. Resolution Add an algorithm in the conversion field of the input objects to adjust the value by the necessary offset. In the example here the conversion entered could be: Elecvalue + 0.5 or Elecvalue + TempSensorOffset where TempSensorOffset is an InfinityNumeric point that has been set to the amount of offset to apply.  While this example uses a very simple conversion algorithm, the input’s conversion can be thought of as a one line PE program that can use PE system functions. Elecvalue + Maximum(TempSensorOffset, 1.5)   Note: For inputs that use automatic conversion e.g. voltage inputs and InfinityFunction is required, see How to add a calibration factor or offset value to an input using automatic scaling for details.

Issue National Weather Service Data Showing Stale Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 8000 / 9000 Cause Due to recent changes with the National Weather Service, the current weather information displayed through Niagara is showing as “Stale” when using the NWS Weather Provider in the Niagara Weather Service. Resolution The Current Conditions “Last Update” time may be null or a current date, and the “Observed” time may be null or a date in the past. Current Weather View: Property Sheet:   This issue is being addressed in future releases. In the meantime to manually correct this behavior, make the below manual updates to the BNwsWeatherProvider components in the station: 1. Go to the Property Sheet view on the BNwsWeatherProvider component, click the ‘Slot Details’ button, then click the ‘Hidden Slots’ button to display the hidden slots. 2. Click the Flags for the “Conditions Server” slot which opens the “Configure slot flags” dialog.  Clear the checkbox for the Hidden slot flag, then click the OK button to clear the Hidden slot flag.  3. The “Conditions Server” slot should now display “(none)” in the Flags column.  4. Click the “Slot Details" button to toggle back to the default Property Sheet View.  The “Conditions Server” property is configured with the default value of “www.weather.gov”. 5. Update the “Conditions Server” property to “forecast.weather.gov” and save the change. 6. Invoke the “Update Weather Report” action on the Weather Report component and verify the Current data updates and no longer indicates a Stale status.              

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Modbus RTU communication is not performing as expected, and there is a need to review electrical installation or request/response packets. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Multi-purpose Controller Building Operation Room Controller Building Operation EZLogic Room Controller Cause Picoscope hardware and software provide the ability to review the electrical waveforms and decode as Modbus RTU Resolution Ensure proper setup and connection of Picoscope probes Set the switch on probes to 1X Connect the probes using the color coding on each end to ensure the connection is as follows: Connect Probe A to TX/RX - Connect Probe B to TX/RX + Connect the probe black reference alligator clips to the cable shield drain wire. Ensure the drain wire is connected to EGND at one location. Connect the Picoscope to the PC, then open Picoscope software and choose the device connected. Set the Scope Use 1 ms/div for 38400 baud Follow this thread for more information since BACnet and Modbus are both RS-485 protocols. BACnet - PicoScope Basics - Schneider Electric Community  Select Channel A Set to +/- 5V Select Channel B and repeat the setting. One may change to +/- 10V if you encounter spikes above the 5V range (overvoltage warnings).  Add Math Channel Click the Math Channels icon Select A - B  Add Serial Decoding for Modbus RTU Click Serial decoding icon Select MODBUS RTU On Page 1 select Master A - B Change Baud Rate to known baud rate, usually 38.4 kBd Change Parity to known parity, usually NONE (1 Stop Bit) Leave the rest at default and click Next  On Page 2 Recommend leaving as default of HEX, knowing you will have to convert for Slave IDs over 09. Leave the rest at default and click Finish  Set Waveform Adjust thumbnail size to preference Leave Capture Time = On (default) Set Max Waveform to 2000 (example has 5000)  Start and stop capture and select Waveform as example Set Trigger Using a waveform, set the threshold voltage just above the blue line voltage. For example, the blue line is at 0.8V, and the threshold is set at 1.92V. Adjust based on your collected waveform(s) Set the Pre-Trigger 0% puts Yellow Diamond to the left and 100% puts Yellow Diamond to the right. The recommended setting is between 5% and 20% (for example, 20%).  Start capturing Set Serial Decoding for MODBUS RTU to show buffer The Current Buffer shows only the waveform on the screen.  All Buffers show everything.  NOTE: The Buffer Number column references the waveform number

Issue When using the Modbus RTU X Driver on RS-485 what cable type should be used and what maximum distance would it give? Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RS-485 XDriver. bCX1, NC2 AS Cause Recommended cable type required. Resolution The Modbus RTU is a standard RS-485 network and you can use the same networking rules as per the Infinet network. As long as the baud rates are set the same you can even use an Infilink 200 or a B Link to act as a repeater. Unless the Third Party device manufacturer specifies different requirements the Belden 9182 or a similar cable that matches the Infinet specification would be suitable, again as per Infinet rules this would typically allow a maximum end to end distance of 1200 Meters. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

  Issue Is it possible to host the same third party BACnet device on the AS-P private networks on multiple automation servers, which are all connected on the same network? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Cause The design in question is a 3-storey accommodation building which includes 1 x BMS panel/AS-P per level. However, only 1 x Mitsubishi EW-50E BACnet gateway is being provided for the building. Resolution It is possible to host the same 3rd party BACnet device in multiple AS-Ps. Some caution is required, however, because if the user makes changes to an object in that device through one AS-P, that change may not be reflected in other AS-Ps. When viewing runtime variables, such as 'Value' and 'Status Flags', this is not a problem because the EBO server will always get new values from the wire. Where the problem can present itself, is when changes are made to configuration values because these are only updated in an EBO server during an upload operation. For example, if you set the hi-limit and low-limit values in an analog-value object from one AS-P, those values will not be updated in other AS-Ps until you do an upload of that object.   The other place where this problem may present itself is in schedules. An EBO schedule only writes values to a device when that value changes. For example, if you have a schedule configured to change the setpoint to 65 degrees at 5pm, EBO will only write a value of 65 if the current 'local' value is not 65. If this schedule only writes 1 time per day and someone has set the value to 70 from another AS-P, the first AS-P does not realize the value has changed so that schedule will not generate a write request to set the value to 65 (it will stay at 70). However, if you have a program or trend-log monitoring the value, the AS-P will be tracking that value and realize it is not 65 so you will see a write request at the scheduled time.   The system works this way because reading all values of all devices and all objects all the time is simply not practical. As long as the user is aware of how the system is designed, they can avoid these potential issues.   Make sure to use Static IP, so IP do not change, or you get multiple DHCP servers on the same network.   Another alternative is to host the BACnet device in one AS-P only, then using internal bindings to share the data with other AS-Ps.

Issue CyberStation is unable to connect to the database. ODBC test also fails when testing the connection to the database. Product Line Andover Continuum Environment CyberStation SQL server SQL management studio Cause SQL server not on UPS. Server shut down due to a power failure. Looking at the ContinuumDB using the SQL Management Studio shows the database has been marked as suspect.  ContinuumDB (SUSPECT) The database may be marked suspect for the following reasons System Issues Transaction Log File is Missing SQL Server Crash Database Files are inaccessible SQL Server Database Operation Failures Due to Improper shut down of SQL Server System (as mentioned above) Due to Sudden Power Outage Low Disk Space Issues Hardware Failure Resolution The database may have been damaged by the ungracious shutdown. The restore option is grayed out and must first be re-enabled before a restore operation can be allowed. How to recover a database in suspect mode Clear the suspect mode of the database using sp_resetstatus DatabaseName. This will clear the suspect flag and make the database available online. The SQL Server must be stopped and re-started. Change the database status to Emergency using the following command. ALTER DATABASE DatabaseName SET EMERGENCY; Restrict database to single user by changing the access mode as mentioned below ALTER DATABASE DatabaseName SET SINGLE_USER; If the restore option is now enabled skip step 4 Run the CHECKDB command with “REPAIR_ALLOW_DATA_LOSS” option. This option should be tried as the last option as it always behaves the way it is named. We are not sure of what data it removes. DBCC CHECKDB (DatabaseName, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS If the repair operation is successful the database is now usable but if a recent backup is available it is strongly recommended to restore the database. Restore the most recent backup of the Continuum database. Set the ContinuumDB owner using the query SP_ChangeDBOwner 'Andover97'  

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 Can I add the group bindings manually as the option to create group binding in the System Plug-in takes time and controllers are taken offline for the period of the process Environment Lonmaker Vista Cause This is  possible to do and works very well and effectively if you understand the process  Resolution Follow these steps to add TAG 0 system bindings and TAG 1 Xenta bindings to your new Xenta controller. In Lonmaker find the source of the TAG 0 binding buy finding any TAG 0 existing binding. Then right mouse click on the tag number and select Go to reference. This will take you to the source of the TAG 0 bindings. If a list of controllers appear then you are already at the source controller. Then Carry out a connection as normal in Lonmaker on that function block. Right click on the Virtual function block with the TAG 0 source and select the connect option. Select the TAG 0 option under the Hub tab then select the target tab and add the new Xenta controller to the system with the Add FB/SNs button. Then select the TAG 0 in the virtual function block of the new Xenta and click on the Add button. The select the OK button. This will add the TAG0 binding to the new Xenta device with the correct binding type. The next step is similar to the TAG 0 but for the TAG 1. You need to locate the TAG 1 Xenta group that you are adding the new Xenta controller into. Once you have located the TAG1 source use the same connection method as TAG0 but use the TAG1 in the virtual blocks. The final step is to download the added controller and the group master.

Issue How do our field controllers keep their own internal time? ( Clock , Real Time Clock , RTC , Frequency) Product Line Andover Continuum Environment Continuum Controllers Cause Not sure how the local time is kept on the controllers. Resolution Throughout the life of the Infinity and Continuum product line, the method of keeping the time on the controllers has changed. The older controllers (9000,9200,9400 era) used the AC frequency as a pulse, or heartbeat, to keep time. This was calculated at a 60Hz cycle and if there was a dirty power cycle or a different frequency power supply (say 50Hz), the local time on the controller would drift out over time. The newer controllers (anything with a Real Time Clock) use the Real Time Clock and its crystal to keep the time; this is in no way affected by the AC or DC power. On any newer generation controller that has a  battery backup (battery backed RAM), the battery also keeps the Real Time Clock functioning as well as the controller RAM in case of a power failure.