Issue Sending a text message (SMS) from an alarm Product Line Andover Continuum Environment Continuum CyberStation CX9900 CX9680 CX9640 Netcontroller Netcontroller II bCX4040 Cause There is no simple way of sending a text message (SMS) from Continuum to a mobile phone. Resolution The below are possible options to send an SMS message:-   Single output (Digital Output) to a GMS modem or auto dialer (single alarm). SMS PE Driver (output via RS232) to a 3rd party GSM modem for more complex alert text. Please see instructions and sample PE code. Send alarm email via outlook or exchange server to an email/SMS Gateway service  Send an email from bCX or NC2 to a email/SMS Gateway service.

  Issue Erratic communication problems encountered during system migration from legacy products to AS-P controllers due to mismatched duplex settings. Product Line EcoStruxure Building Operation. Environment SpaceLogic AS-P SpaceLogic AS-B Cause Legacy controllers or existing devices supporting only Half-Duplex are incompatible with AS-P/AS-B controllers, which support Full Duplex 10/100BASE-TX communications. Resolution To address this issue, follow these steps: Install a managed switch: Introduce a managed switch between the devices to enable effective communication. Configure port settings: Utilize the features of the managed switch to configure each port according to the required duplex mode, either Half-Duplex or Full-Duplex. By implementing a managed switch, you can ensure compatibility between Half Duplex and Full Duplex devices, resolving communication problems and facilitating a smooth migration process.

Issue Automation Server has license violation although correct embedded license is activated. ASBaseLicenseStatus has license violation status "inform"   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Adjusting the Automation Server time and date to an earlier time, ex. prior to license activation time, causes license violation. Resolution Make sure that Automation Server has correct date, time and timezone or configure the Automation Server to synchronize its clock with a network time server, refer to: Time and Time Zone Configuration in Automation Server.

Issue Using the OPT Block with a StruxureWare Time Schedule Object. Environment Function Block Editor Cause The Xenta Time Schedule which the OPT Block has the ability to send a positive or negative minutes till next change. The StruxureWare Time Schedule dose not include this item. This is the online help article that defines the parts of the OPT Block Resolution In the Function Block Editor, create 3 RI blocks. One will be bound to the Value attribute of the Analog Schedule One will be bound the ScheduleDefault attribute of the Analog Schedule One to the TimeToNextTransition attribute of the Analog Schedule Create an XPB block with the function "A!=B". Connect the Value RI to A and the ScheduleDefault RI to B. Label this XPB "Status". Create an XPI block with the function "a?B*-1:B". Connect the status XPB block to "a" and the TimeToNextTransition RI to B. This Block can be connected to the TmL input of the OPT block. This is an export of the demo application below which shows the bindings. (right click and choose Save link as...)

Issue V-Box fails to install network interface/Virtual Adapter during Project Configuration Tool Installation. Product Line EcoStruxure Building Operation Other Environment OracleVM VirtualBox (all versions) Project Configuration Tool (all versions) 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 Some security or anti-virus software prevents V-Box from installing virtual adapter during PCT/V-Box installation or prevent PCT from connecting to a virtual adapter.   Example: The anti-virus software can flag V-Box file as possible threat. Resolution Uninstall or Disable security and Anti-virus software. Install PCT. Install or Enable the software after PCT works properly.   NOTE:  You may have to disable and/or completely remove the security software even after PCT is installed and works properly.  Contact your IT group to get assistance with getting exceptions entered to have PCT work correctly in conjunction with your security software.

Issue TC series thermostats which one support Modbus protocol? TC series thermostats which one support time schedules? Environment TC100 (TC103) TC300 (TC303, TC353) TC500 (TC503, TC553) Cause Due to different TC thermostats models support different features, customers need to double check the selection guide to make sure the selected model can support all features which are required. Resolution Click here  to view a matrix which contains all TC series thermostats and their supported features. Additional information can be found on the Buildings Business Extranet website (Products > Field Devices Asia Pacific > Thermostats).

Issue Can old generation temperature sensors or new generation temperature sensors be used on CXR, CXT, CZT, CSC5252, CSC5352 ? Environment CXR CXT CZT CSC CSC5252 CSC5352 CSC 5252 CSC 5352 Cause Can old generation sensors or new generation sensors be used on CXR, CXT, CZT, CSC5252, CSC5352? Resolution Existing old generation sensors can be used on the current range of discrete controller, however they CANNOT be used/mixed with new generation sensors. Note, when replacing sensors or upgrading a controller to the current version, terminal numbers are different between old generation and new generation sensors, see the datasheet for terminal numbers. For the CXT datasheet click here. For the CXR datasheet click here. For the CZT datasheet click here. For the CSC5252 or 5352 datasheet click here.

Issue The Sigma Release Note for version 4.07 references the Sigma Standard Edition Installation and Users Guide, but does not specify where to obtain it. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Users may be unaware of the location or availability of the referenced guide due to lack of direct links or visibility in the release notes. Resolution The Sigma Standard Edition Installation and Users Guide is attached to this article Attachments: Sigma Standard Edition Installation and Users Guide-0111.pdf

Issue How are BACnet controllers established as being Online / Offline? Product Line EcoStruxure Building Operation Environment BACnet Cause BACnet controllers may appear offline in the system, even though they can still be communicated with. This raises questions about how their online/offline status is determined. Resolution The online/offline status of BACnet devices is managed by the BACnet device manager plugin, which processes BACnet I-Am messages to maintain a device table.   The following rules and mechanisms are used to determine the status of BACnet controllers: Device Discovery and Initial Probing When a new device is discovered, an entry is added to the device table. The system probes the new entry up to four times at 5-second intervals. If the device does not respond within this time, it is declared offline. Offline Detection via MSTP Driver Building Operation uses the MSTP dev driver to monitor token passing. If three consecutive tokens are missed, the device is marked as offline. Probing Offline Devices Once a device is offline, the system sends a Who-Is message every 60 seconds. Offline devices are probed indefinitely at 60-second intervals until they respond. Online devices are never probed. Status Transition A device is considered online once it responds to a request. If it fails to respond, its status is updated to offline, and probing resumes.

Issue Resizing the drawing from 11"x17" to 17"x22" just enlarged the size of the objects.  No additional space was available for more objects. Environment WorkPlace Tech Tool software (any version) Supported version of Microsoft Visio Cause Changing the Visio "Printer Paper" size does not resize the WPT drawing page size. Resolution Both the Device Definition page and the Background page needs to be resized and the resizing is a two step process. Select "Background" tab From File menu, select "Page Setup" Click "Page Size" tab - this window shows current drawing page size Select the desired drawing page size either by selecting a pre-defined size or a custom size.  We distribute our pre-defined application files with the page size set to 25% oversize (for printing on 11x17 paper) -- custom size 13.75" x 21.25" Click "Print Setup" page and select your printer paper size in the first field (we use Tabloid (B) 11in x 17in) In the Print Zoom section of the window, select Fit to 1 across x 1 down Click OK to save the settings and close the window. Select "Device Definition" page and repeat steps 2 through 7 on that drawing page. If there are any other pages in the application drawing, such as custom object pages, repeat step 8 (including 2 through 7) for each of those pages.  

Issue An Enterprise Central has two Enterprise Servers, both connected to External Log storage as pictured below. How can the EC access trend logs in both External Log storage locations when it is only connected to one of them? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause It is only possible to specify a connection to one External Log storage location in the EC Resolution When a user needs to access trend data from a specific log located in, for example, an AS-P while the Workstation is connected to the EC, the following process occurs: The EC contacts the specified External Log storage for the log data using the trend log ID. If the trend log ID is not found in the specified External Log storage, the EC then contacts the Enterprise Server (ES) associated with the AS-P to request the log data. The ES connects to the External Log storage specified within it and retrieves the log data using the trend log ID. The ES delivers the log data to the EC, which in turn delivers it to the Workstation for access. This process ensures that the EC effectively manages connectivity to External Log storage systems and retrieves the required trend data for users.

Issue Is 64-bit Internet Explorer supported for use with WebClient? Product Line Andover Continuum Environment WebClient Cause The Compatibility Matrix now mentions 64-bit Internet Explorer is NOT supported as the browser for the WebClient clients Resolution IE 64-bit Support Webclient does not support 64-bit Internet Explorer with WebClient See the Cyberstation and WebClient 2.03 Compatibility Matrix - Andover Continuum - PA-00664 R2  WebClient browser support section: Only the 32-bit version of Internet Explorer - Internet Explorer 10 and 11 Compatibility View for AlarmView Be sure to turn on the Compatibility View in the separate IE browser window that displays the Alarms view. Also turn off popup blockers in the browser window. For more information on the Alarms view, see the web.Client online help   Using IE 32-bit in 64-bit Environment</strong? In a 64-bit environment, both the 64-bit and the 32-bit versions of IE10 and IE11 are installed when you install IE. 64-bit version is under "C:\Program Files\Internet Explorer" 32-bit version is under "C:\Program Files (x86)\Internet Explorer" See the following article for using Webclient with Microsoft Edge: https://community.se.com/t5/Building-Automation-Knowledge/Internet-browser-alternatives-for-accessing-Continuum-WebClient/ta-p/363440

Issue How can you use Loytec's LPA software with the AS as the interface Product Line EcoStruxure Building Operation Environment Automation Server Loytec LPA Cause A Loytec LPA can be a valuable troubleshooting tool to diagnose communication problems on a LON Fieldbus. Resolution As the Automation Server uses Loytec's Lon chip, it is possible to use Loytec's LPA software over the Lon port on the AS. Some Prerequisites:   A license is required to use the LPA software. Either the "LPA-IP" or the "LPA-IP-SW" package depending on your setup. LPA (loytec.com) shows a product overview.   Downloads | Software - Device Firmware and Readme (loytec.com) to download the software. Create a free login in order to download software from Loytec's home page For additional help Buying and registering the LPA software read LonTalk Protocol Analyzer Software License and Registration Steps Lonworks troubleshooting read Troubleshooting LON Network Communication Troubleshooting Lon communication with TAC Xenta's read Actions for reducing Bandwidth in a Vista network There is a limitation when using LPA through an AS. Refer to Not all traffic on a segment is captured when using the LPA through an Automation Server Please make sure that you have a LonWorks interface configured in the Automation Server before proceeding. You will also need to add a Local Node to the interface and to commission it. Make sure to set the LPA state to Enabled under the Advanced tab in the properties for the LonWorks Interface: Once the above have been checked and understood the following steps can be performed:   Start the LPA software Click on "Profile -> Network Interface..." Click on "Remote LPA Assignment" Click on "Add Device" Enter the IP address of the Automation Server, click on "Get Info" and click on "Add Device and Restart Search" Select the Automation Server device and click on "Assign/Add" Select the interface you want to assign to the Automation Server, and click "Assign" With the interface assigned, click "OK" Select the Building Operation interface and click "OK" Now the LPA software is using the Automation Server as the interface Start a new LPA log

Issue AS-P is restarting on its own intermittently. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (All Versions) Cause Log entries found within the system_log.txt file confirm that the intermittent restart issue is caused by power interruption. See the below example of what to look for: Apr 08 19:03:34 AS-P-04619A kernel: pmem: shutdown interrupt: pid=0, comm=swapper/0 Apr 08 19:03:34 AS-P-04619A kernel: [<80013920>] (unwind_backtrace+0x0/0xe0) from [<801f569c>] (pmem_shutdown_irq+0x54/0x74) Apr 08 19:03:34 AS-P-04619A systemd-journal[1360]: Journal stopped -- Reboot -- Apr 08 19:03:54 cpud pmem_util[656]: Found SyncBlock Partition at sector 0x5dc00, 192000 sectors long. pmem_util[656]: ---------------------------------------------------- pmem_util[656]: SyncBlock Header summary (from previous power fail): pmem_util[656]: Sequence number:             94 pmem_util[656]: Exit critical regions:       0ms pmem_util[656]: SyncBlock file systems sync: 20ms pmem_util[656]: SyncBlock write map:         0ms pmem_util[656]: SyncBlock write speed:       6399kB/s (Wrote 128kB) pmem_util[656]: Total power fail time:      ~130ms pmem_util[656]: ---------------------------------------------------- pmem_util[656]: Finished moving 240 sectors (120kB) pmem_util[656]: Exit Resolution When an AS-P detects a power outage, regardless of how brief, it will initiate the process to backup the run-time and configuration data from memory to storage and reboots itself.  Check the power source connected to the AS-P and take appropriate actions to improve uninterrupted power delivery. An example would be to deploy a UPS solution.

Issue Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at workstations other than the primary access server do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Product Line Andover Continuum Environment CyberStation Microsoft Windows 7 Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Cause Problem in Microsoft MSMQ component. MSMQ service might not send or receive messages after you restart a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008. This will cause any Continuum component that uses MSMQ (such as Alarms and Access Events) to fail. Microsoft has issued a hot fix for this MSMQ problem. Resolution Use the following command prompt test to verify the problem netstat -ano | findstr 1801 The command tests whether MSMQ is listening for messages. For example, Continuum WS 'A' is the primary access server (PAS) with an Event Viewer 'EV' up,  a second Continuum WS 'B'  is also displaying the same EV. If MSMQ is functioning normally you should see the following. 1. is the IP address of WS 'B' that has established a link to WS 'A'  2. is the IP address of WS 'A', the PAS in this case. 2560 is the listening MSMQ process PID  You can clearly see that there is a MSMQ process (2560) in WS 'B' LISTENING on port 1801 If there is no MSMQ process listening the output of the command will show the loopback or localhost IP address 127.0.0.1 and you have to install the following Microsoft hotfix: Package: ----------------------------------------------------------- ----------------------------------------------------------- See Microsoft KB Article Number: 2554746   ** In very rare occasions, removing MSMQ and adding MSMQ again to the PC is required. ** Once it is re-installed, please refer to Access event viewers running in a workstation other than the Primary Access Server stop displaying events to set the MSMQ CleanupInterval setting to one hour in the primary access server.

Issue The Runtime tab of an Infinet controller editor shows the maximum number of 255 for both the Infinet Error Count (InfinetErrCount) and Reconfigs.  What is the command to reset them to 0? Product Line Andover Continuum Environment Infinet controller NetController (CX9200, CX9400, Cx9702, CX99xx) NetController II (CX9680) bCX9640 Cause Having an unstable Infinet can cause both Infinet errors and Reconfigs to occur.  An engineer may want to reset the Infinet Error Count (InfinetErrCount) and Reconfigs to 0 and check how fast they both reoccur. Resolution Either execute the command from the Command Line of Continuum Explorer or create an InfinityProgram in the CX controller to reset them as below: *   Set Comm2 Reconfigs = 0 *   Set InfnetCtrlName InfinetErrCount = 0                NB  Make sure the whole path is specified!!

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (701) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Vista, I/NET, LON, MicroNet, ModBus Xenta Servers (Xenta 5XX/7XX/913) Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.4 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Xenta 511 X         C   X Xenta 527 X X     X C   X Xenta 527-NPR   X       S     Xenta 555 X   X     C   X Xenta701 X         ST 10   Xenta 711 X         C 10 X Xenta 721 X         ST 20 X Xenta 731 X X X   X C 20 X Xenta 913 *** X X   X X S     * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service.  NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.5 major features please read Xenta Server after version 5.1.5 (5.1.5 included) Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue While trying to login to either WorkStation or WebStation, or during the startup of the Enterprise Server, an error "Error -25: License server system does not support this version of this feature." appears. Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 2.0.x or later Building Operation Webstation version 2.0.x or later Building Operation Software Administrator version 2.0.x or later Cause The activated license is not at an appropriate version for the corresponding software. The licenses activated in the EBO License Administrator need to be at a version greater than or equal to the version of the Building Operation software being used.  Resolution 1. Workstation - If the Workstation license activated in License Administrator is at Version 1, this license will need to be upgraded to be compatible for any system EBO 2.0 and beyond. To do this, simply notate the Entitlement ID and then return the Workstation License. Once returned, reactivate the license from the previously recorded Entitlement ID. This will upgrade the 1.X License to be used with newer systems. 2. Enterprise Server - If the error is received on an ES, verify that all ES licenses are in place. If the system was upgraded, it is necessary for all previous versions of ES/AS licenses to remain activated in the License Administrator. 

Issue Integrating MNL-VAV controllers into the EBO system successfully Product Line EcoStruxure Building Operations, TAC IA Series Environment Building Operation Automation Server Building Operation Automation Server Premium I/A Series MNL VAV 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. Cause Lost flow balancing values during integration Lost S-link offset calibrations Resolution Use the following steps to bring a controller into the Automation Server with all data intact. Using WorkStation connected to the AS/AS-P; right click on the LonWorks Network and select New then Device. Choose the appropriate device object type from the list for the MNL-VAV controller being added, give it a name and click Next. Type in the Neuron ID or use the Service pin method to identify the controller. Check the box next to “Commission” and the radio button next to “Keep current configuration in the device” and click “Create” then click “Close” when complete. Right-click on the new device object in the tree and select MNL and then “Backup flow balance information”. When this is complete notice the blue circle with a white checkmark next to the nciHighFlowCal and nciLowFlowCal SNVT’s indicating the AS-P DB contains the balance data from the controller. If special S-link offset values exist in the controller right click on the device object in the tree and select MNL and then “Backup S-link offsets”. Right-click on the controller device object and select MNL and “Assign application” and click on the appropriate application file for this controller and click on “Assign”. Right-click on the controller and select MNL and “Download application”. Click on “Close” when complete. Right-click on the controller and select MNL and “Restore the flow balance information” Right-click on the controller and select MNL the “Restore S-link offsets”. Verify all data is correct and the controller is functioning properly.

Issue When a Modbus device comes back online after being offline a message is sent from the Building Operation Server to the Modbus device which looks similar to: WriteData TX on /dev/tac_comporta: 01 2B 0E 01 00 70 77 ReadData RX on /dev/tac_comporta: 01 AB 01 9E F0 This message can cause the Modbus device to restart or stop responding, is it possible to disable it? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 1.5.xand above Modbus Device Socomec Power Meters Crompton Integra 1221 Power Meter Cause A feature was added in release 1.5 that is intended to read the device's identification (0x2B). It works by polling this function code (FC). If the Building Operation server does not get a valid reply to this message, it assumes it is not supported by the device and will not request this again. This is usually not a problem but some Modbus devices, such as those listed in the Environment above, are unable to handle this message and will stop communicating with the AS or ES. Resolution In Building Operation 2.0.4 and above the option to enable or disable the device identification request (Function code 2B) has been introduced, allowing the poll interval (and online detection) to be set. Some devices will stop responding to poll requests if the device identification is enabled. Once disabled the AS or ES and the device may need to be restarted to enable normal polling without any device identification request being sent and stopping the normal responses from the device.   In previous versions this message cannot be disabled, however, if device polling is disabled the device identification request won't be requested, which can be used as a work-around. To turn off the device polling: Open Properties Set "Poll interval" to "Inhibit" The trade-off with this workaround is that the online detection for the device is turned off, so the device will never go offline in Building Operation. In some instances, the third-party Modbus device will need to be restarted to allow communication to resume.