Notifications

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Viconics stats are only showing as offline in Continuum using the "controller status" notification when being accessed Product Line Andover Continuum Environment Continuum Viconics Stats Cause Viconics BACnet stats must be probed in order to return alarms Resolution There are 3 probe types that can be set up in Continuum. Probe, ProbeOnDemand and ProbeOff. These types can be configured in Cyberstation and in the Viconics Stat from Continuum Explorer (Edit>General Tab>ProbeType drop down selection) "Probe Time" can also be adjusted on the Cyberstation (default is 60 seconds) Testing Results Cyberstation Probe Type changed to "Probe", Probe Time=60 seconds. Viconics stat set to it's default of "Probe Off" Remove mstp connector result: no alarm until the Viconics stat is opened (This probes the device) Cyberstation Probe Type changed to "Probe", Probe Time=60 seconds. Viconic stat set to "Probe" Remove mstp connector result: alarm comes in automatically after 60 seconds Probe Type and Probe Time Definitions (Continuum Help) Consider and these options and their affects on the system when making a selection Probe - Probing occurs at the interval specified in Probe Time. The default is 60 seconds. The advantage of this is that CyberStation detects a device going offline regardless of whether or not CyberStation is attempting communications with the device. The disadvantage is excess probe traffic for devices. ProbeOnDemand - Probing does not occur unless a communications transaction with the target device fails. Once a transaction fails then probing occurs at the interval specified in Probe Time until the device comes back online. The advantage is that additional requests to the controller fail immediately. The disadvantage if that node failure is not detected until a CyberStation application needs to communicate with a controller. ProbeOff - Probing does not occur. The advantage is that there is never probe traffic to the device. The disadvantage is that each request to the device fails only after the transaction times out. Also see the following article related to Viconics stats and performance: Problems and cautions when communicating with TAC (Viconics) Bacnet communicating thermostats

Issue Obix is being used import logs from the R2, UNC-520 station into a Niagara G3, ENS. The problem is that some logs are being split into multiple histories in the ENS. A single log in the UNC is split into multiple histories when imported into the ENS. Product Line TAC IA Series Environment Niagara G3, ENS Niagara R2, UNC-520 Cause The problem is on the R2 side. The R2 web server uses multiple threads, each servicing a single HTTP request. The R2 oBIX server has a method to resolve the requested URI to an object in the station - usually a Node of some kind. If multiple requests are coming into the oBIX server at the same time, the URI resolution can be invoked by multiple threads. So if one thread resolved a URI to a particular Node, then a second thread came in and resolved a second URI to a second Node, sometimes the second Node could be used to fulfill the first request (as well as the second request). This resulted in multiple copies of the same history when brought in to the G3 ENS. Resolution Once this problem was clearly identified, the solution was simply to synchronize access to the URI. The new obix-2.301.535i.beta.jar synchronized this process to eliminate the splitting logs. Download and install the new R2 obix-2.301.535i.beta.jar file in all UNCs which archives their logs to the ENS. Reference How to install an I/A Series R2 JAR File for more information.

Issue To re-use a point in an ASC, should one delete it or just edit as needed Product Line TAC INET Environment I/NET Site Cause A point in an ASC needs to be repurposed from its original design. Resolution The point can merely be edited, provided it is available for re-use. Check closely in the functional description of the points in the specific TCON for that controller to ensure this is permitted on the point in question.

Issue When opening a Xenta Server (Xenta 5/7/913) trend log, it will display estimated value for a constant period of time. For example: A trend log trends room temperature every 30 minutes. An operator opens the trend log at 9AM, the trend log displays all the trend log values fine till 8AM. All values after 8AM before 9AM display as estimated value. Open the trend log again at 9:30AM, estimated values start at 8:30AM. Product Line TAC Vista Environment Xenta Server (Xenta 511, Xenta 527, Xenta 701, Xenta 711, Xenta 913) Cause Estimated value in trend log can have various causes. If it is always a constant period of time, it could be caused by the wrong time setting in Xenta Servers (most likely is the wrong day light saving minutes setting). Daylight saying time in a Xenta Server is set to 60 minutes by default. If Vista Server PC is set to not using daylight saying, then Xenta trend will not display the last hour trend since it believe the time is not reached yet. Resolution Please refer to Xenta Servers and Time Synchronization for step by step guide of manually setting up the Xenta Server's time. After the time setting change has been made, Xenta Server will reboot itself. When the reboot finishes, reopen the trend log and the issue should be solved.

Issue Privilege software version 2.01 crashes during installation on Windows XP. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Privilege Administrator Incompatibility with XP Resolution Uninstall any previous Privilege Administrator (Please see How to uninstall Privilege Administrator 2.01 software for details on uninstalling the software) Download "Privilege Windows XP crash hotfix" (PS202.zip) Install PS202 by running setup.bat. Install Privilege Administrator 2.01 again.

Issue MN-S# sensor connected to MNB-1000 showing all segments lit up Product Line TAC IA Series Environment I/A Series MNB-1000 Cause Connecting a UI to a Binary Input set as a binary type "pulse" in the MNB-1000's database will cause this. Resolution Per UI inputs of the MNB-1000 do not support pulse inputs, pulse inputs connected to an MNB-1000 must use a DI input. Correct the database so the pulse input uses one of the DI inputs. Connect that DI to a Binary Input object set to binary type "pulse." Compile and download and the issue will clear.

Issue After powering off, pressing the reset and Reset IP button a bCX1 controller still will not start up. CPU does not flash and controller will not respond to a ping. Product Line Andover Continuum Environment bCX1-CR-INF 9640 bCX1-CR 4040 Cause The controller is connected to an Ethernet network that is in a broadcast storm condition. This scenario can also occur if a patch lead is inadvertently looped back onto the same Switch/Router. Resolution Disconnect the Ethernet cable from the controller and it will start up correctly. On a very busy network or under a broadcast storm condition the controller will protect itself as detailed in Controllers go offline during a broadcast storm.

Issue SmartStruxure Lite provides Script library and Firmware upgrades through a password protected website. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite (SSL) Cause Requesting further documentation, firmware, and login credentials to the SmartStruxure Lite website (SmartStruxure Lite Solutions) Resolution SmartStruxure Lite can be purchased over the counter by anyone. To get access to the SmartStruxure Lite website for downloading firmware,scripts, and further documentation, site engineers will need to go through the training program. Until this is completed, they will need to seek support from a trained SE partner or branch for support.

Issue Errors in Vista Workstation alarm window: "Failed to execute report XXXXX-YYYY, Error in "DDE Execute" command[27]" "Warning logged in B0WARLOG.TXT on node XXXXXX" Contents of B0WARLOG.TXT: "Could not open report XXXXX-YYYY, hRes=[-2147467261]Invalid pointer" Product Line TAC Vista Environment Vista Server Microsoft Windows 7 Microsoft Windows Server 2008 Cause Vista Server does not support running as a service under the local system or interactive user account. A PC account that has local administrator rights must be used to run Vista Server. Resolution Follow the registration instructions for Vista Server in Registering/Unregistering TAC Vista Server as a Windows service when registering TACOS.exe as a service.

Issue What is the best way to update Modbus RTU points through the X Driver? Product Line Andover Continuum Environment Continuum Modbus RTU XDriver Cause Requesting values directly will cause additional polling to occur and may conflict with the Plain English polling program. Resolution Polling of the X Driver points should be performed by a single Plain English program (or sequenced programs) that ensure only 2 requests are made per second (See Typical data throughput rates for Modbus XDrivers). Whenever programs, graphics, alarms, list views etc are going to be used to read the X Driver values then annex points should be used. An Annex point is a numeric point (not an X Driver point) that will get automatically updated by the X Driver if its name is put into Parameter 6 of the X Driver point. Annex points are required for block reads, but even if you are doing an individual value read, this is the most efficient way of mapping the X Driver point value into another point that can be used by the rest of the system. Another advantage of using annex points is that if an invalid or bad value is received by the X Driver, it does not update the Annex point even though sometimes the X Driver point itself can go to a NotSet or a 0 value until the next valid read is received. The annex point always holds the last known good value. Also see Using Modbus RTU X Driver to connect to PM700 and PM750 Power meters for an example application for polling Schneider Electric power meters.

Issue What is the correct cable to use to communicate with the NPR 2000 via its serial port? Product Line TAC INET Environment I/NET Site Cause The getting Started book incorrectly specifies that you may connect the com port of the computer to the com port of the NPR 2000 using a standard serial cable. Resolution The correct cables are the same cables used to connect to a 77xx01 emutap, the CBL072. Cable Connectivity to I/NET has more information on this cable.

Issue Satchwell "AMS" and "AMSH" series Spring Return Rotary Actuator requires replacement by S-E M700 Spring Return Linear Actuator due to obsolescence. Product Line Field Devices Environment Satchwell "AMS" series Spring Return Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Satchwell "AMSH" series Spring Return Rotary Actuator installed on Satchwell MZF or VZF series 125mm and 150mm Plug and Seat Valve Body. N.B. Where a Satchwell "AMS" series Spring Return Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. See Replacement of Satchwell V V series Butterfly Valve Body Cause Obsolescence of Satchwell AMS and AMSH series Spring Return Rotary Actuator. Resolution The new actuator is 24Vac and the control signal will need to be converted from 230Vac to 24Vac, this could be achieved by a transformer and 2 off 230Vac relays. The old signals switch the coils of the relays. The relay contacts switch 24Vac to the new actuator. Replace Satchwell AMS or AMSH series Spring Return Rotary Actuator with S-E M700 Spring Return Linear Actuator and Linkage Kit: AMS = M700 + L7SV (880-0126-000) Linkage Kit. N.B. M700 is available with two different spring return actions M700 - SRSU (880-0430-000) = Spring Return Spring Up ( M700 - SRSU will CLOSE a Satchwell Valve.) M700 - SRSD (880-0440-000) = Spring Return Spring Down ( M700 - SRSD will OPEN a Satchwell Valve.) Should the Satchwell AMS series Actuator include a wired Auxiliary Switch then the following S-E M700 Actuator specifications which include 2 independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches should be considered as appropriate: M700 - S2 - SRSU (880-0431-000) M700 - S2 - SRSD (880-0441-000) Alternatively Auxiliary Switch Pack S2 (880-0104-000) - Two independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches may be purchased separately permitting local installation. Particular care should be taken when selecting a TAC Forta M700 Spring Return Actuator to replace an existing Satchwell AMS Spring Return Actuator. Please refer to Replacement of Satchwell "AL..S" series Spring Return Linear Actuator. Please check the latest catalog for current equipment.

Issue Mixing version of Sigma data Product Line Satchwell Sigma Environment Opening customer's Sigma data files in Sigma on another computer. For example: an engineer needs the site information on his laptop while carrying out a maintenance visit. Cause When a specific Sigma version is loaded onto a computer, only data files from the same Sigma version should be used. Resolution It is known copying over the whole Sigma folder from another version of Sigma to your computer can appear to work, this should not be done. Any files that have been looked at, on another computer, in this way should not be restored onto the customers machine. Some issues caused by doing this will not always be obvious as many of the Sigma tasks are completed in the background. The site could be left with a potential issue or corrupted files. Rather than uninstalling Sigma and re-installing the correct versions on the main computer operating system, Virtual machines each with different Sigma versions could be created. Further information, showing Sigma release numbers against Build numbers, can be found in How to identify the Sigma Version installed on a Computer.

Issue An error message indicates that EPICLM.exe can't be found in data1.cab using the Epi integration for badging or a 1309 when installing Cyberstation Product Line Andover Continuum Environment Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Kaspersky Anti virus is identifying and removing the file from the data1.cab during a scan. Resolution Place the cab file or the EPICLM.exe as an exclusion in Kaspersky's or EST NOD32 scan. For additional information see Kaspersky's website. http://support.kaspersky.com/4084 Note: The data1.cab file may need to be restored from the original CD or Continuum install zip file and then uninstall/reinstall EpiBuilder with the exclusion list in place to repair the problem. See Uninstalling and reinstalling EpiBuilder or error opening EpiDesigner configuration database for more information.

Issue Need to log a User off of a Continuum Workstation from a remote Cyberstation. Product Line Andover Continuum Environment Continuum Cyberstation Cause No documented solution on how to log off a remote Workstation. Resolution If you know the name of the User that is currently logged on, you can open that User object from another Workstation and disable the user. This will immediately log that user off of their current session in Continuum and lock them out of the system until their User object is re-enabled. To determine the name of the User, you can use the solution in Is there a way to determine who is actively logged into CyberStation and onto which workstation? to determine what users are currently logged on to Continuum using the Activity Log.

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. Issue When Vista Server is started the startup process just hangs. Product Line TAC Vista Environment Vista Server 5.x Cause There can be several causes for this issue. A common issue with this situation is the Vista database has been restored from site without the Lonworks NL220 or LonMaker database. When the Vista server is opened it is unable to contact the Lonworks database and repeated attempts cause the server to hang. Resolution It is possible to prevent the Vista server communications as well as other parts of the Vista server communication. Reference TAC Vista dll Manager to download a tool from the Community that will allow you to disable DLL files and find the cause of the issue. If you are seeing the scenario as stated in the above cause, you would disable Option "10: Network communication" and "11: Field bus communication" in this tool then select the Update button You must remember to enable the options once you have finished with the site database. If you forget to do this the Vista server will not function correctly when you want to run a live database.

Issue Drop downs not visible on secondary monitor used with I/NET Product Line TAC INET Environment Windows XP I/NET Seven 2.41 Cause As of 2.41 I/NET is not intended to be a multiple monitor platform Resolution Modify the display settings to configure the monitor with the I/NET display as the primary monitor Upgrade to I/NET 2.41 using Windows 7 as this problem has not been seen with this specific installation Use I/NET on your primary monitor and AMT on your secondary monitor. If it doesn't work, please refer to Drop list of point control in I/NET summary on secondary monitor does not work.

Issue Launching Menta by opening an MTA file causes a Buffer Overrun Error The error message: "Buffer overrun detected ... A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated." Product Line TAC Vista Environment Menta Cause Menta's buffer for opening files is limited; if the file you are trying to open by double-clicking has a very long path (of 142+ characters), you will receive the Microsoft Visual C++ Runtime Library Buffer Overrun error message. Resolution Work arounds: Shorten the path to the Menta file. If it is possible to decrease the number of subdirectories or the length of the directory names to make the total path length less than 142 characters, this will correct the problem. Note: Never modify a Menta file name within Windows; only change Menta file names using the Menta application by using "Save As..." from the File menu. (See "Cannot open file" error when opening a Menta file for resolution if this occurs.) If it is not possible or practical to change the path to the file, files with long paths can still be opened by launching Menta using the Start Menu or a desktop icon. Select File > Open and browse to the Menta file, then click "Open". Opening the file via this method will expand the path length limitation to over 200 characters.

Issue Which substitution codes are available for write to file notification objects? Customer wishes to write dynamic values to file. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3/1.4 Cause When using write to file notification objects it may be desirable to have dynamic text containing actual values etc. Resolution For write to file notifications, the substitution codes can be used in the message but not in the file name. A substitution code for notifications has the form @([property]) where [property] is replaced by one of the alarm properties. If you use a substitution code that is invalid for the specific alarm event, the substitution code is replaced by an empty string. For alarm email notifications, see Displaying different properties of an alarm in an email notification.

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. Issue Getting error inserting a row in the database when refreshing a personnel template. Product Line Andover Continuum Environment CyberStation Cause AreaLink table contains NULL instead of zero in the ClearanceLevel column. Resolution WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Run the following query: Update AreaLink Set ClearanceLevel = 0 where ClearanceLevel is null

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Viconics stats and controller offline alarms

Logs from multiple R2, UNCs are being split when brought into the Niagara G3, ENS via Obix

Re-use a point in an I/NET ASC

Xenta Server Trend log has estimated values for a constant period of time

Privilege software version 2.01 crashes during installation on Windows XP

MN-S# sensor connected to MNB-1000 showing all segments lit up

bCX1 controller will not start up, the CPU LED flashes 5 times and remains on steady

SmartStruxure Lite access and login to the SmartStruxure Lite site

Periodic report will not run when Vista Server is running as a service

When should the Modbus RTU Annex points be used?

Cable to communicate with the NPR 2000 via serial port

Replacement of Satchwell "AMS" or "AMSH" (high torque) series Spring Return Rotary Actuator

Opening customer's Sigma data files in Sigma on another computer

Error "1334 EPICLM.exe can't be found" when attempting to print preview, print a badge, or 1309 when installing Cyberstation

How to log a User off of a Continuum Workstation remotely

Vista Server hangs on startup

Using multiple monitors with I/NET

Launching Menta by opening an MTA file causes a Buffer Overrun Error

Available substitution codes for write to file notification objects

Error inserting a row in the database when refreshing a personnel template

Building Automation Knowledge Base

Related Forums

This is a heading