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 Trying to run DBCreate and the Windows Authentication does not allow me to login and sysadmin (sa) password not known. Product Line TAC INET Environment I/NET Seven Windows XP / Windows 7 Cause This is normally related to the logged in user not having either Administrative privileges to the PC and / or the correct access privileges to the SQL Server. Resolution The best solution is to verify / modify the logged in account is part of the Administrator group and that the Administrator group has access rights to the SQL Server database(s). Another solution would be to change / modify the sysadmin (SA) password and use the SQL Server authentication. Refer to Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility or Lost/ Forget/ Modify the SysAdmin SQL default password created during the installation of TAC Vista 5.X.X in typical mode on how to achieve this. Caution: Note that changing this password may impact on other applications using SQL Server. Both of these solutions may also require IT personnel to get involved. A possible workaround maybe to run the application at a higher authority level. To do this perform the following steps: Windows XP: Locate Application, in this case DBCreate within Start > Programs> INET Right-Click on DBCreate - Database Create Utility shortcut and select the option "Run as.." Login with the Administrator or known user with administrator privileges Connect using > Windows Authentication should now be possible Windows7: Locate Application, in this case DBCreate within Start (Windows7 icon) > All Programs > INET Right-Click on DBCreate - Database Create Utility shortcut and select "Run as administrator" option From DBCreate application Connect using > Windows Authentication should now be possible

Issue Alarms are produced by Sigma controllers, but these alarms are not received at the Enterprise Server Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Enterprise Server Sigma 4.08 Alarms Delayed alarms Transition Cause When Sigma alarms are manually tested from the Enterprise Server, the alarms are received normally, but alarms occurring during normal operation on the Sigma system, can be delayed, or not displayed at all at the Enterprise server. This issue is caused by the firewall. If the Enterprise Server is initiating the communication with the Sigma controllers, then the firewall will normally allow any alarm messages from the Sigma controllers to pass through the firewall, and the alarms be displayed normally. When the Enterprise Server is not initiating the communication the Sigma controllers, then the firewall will normally prevent any Sigma alarm messages from passing through, and therefore the Sigma alarms will not be displayed. Resolution The solution is to allow inbound communication to the Enterprise Server PC on port UDP 49152 Depending on the firewall used, the configuration steps can vary. If Windows Firewall is not used: Consult your vendor manual. Example of Windows Firewall not being used If Windows Firewall is used but managed by the IT department: Consult with your IT department. Example of Windows Firewall being managed by IT If Windows Firewall is used and you can manage it: See below Windows Firewall A quick solution is to use "SBO Firewall Config". While the tool is not officially supported, it has been used by various sites. To manually add the exception to Windows Firewall, refer to Using Sigma on Windows 7 with firewall.

Issue Continuum / Vista / I/NET / StruxureWare etc will not connect to any of the controllers on the LAN when using a Windows 7 and above PC. Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment I/NET 2.4x Continuum Vista StruxureWare Windows 7 8 8.1 10 Cause This is due to Microsoft improving their security in Windows 7 and above that will now block many types of connections across a network. Resolution To enable communications across the network; Disable all firewalls and any Anti-Virus software on the PC. (SE laptops, right click on McAfee shield, Quick settings and un-tick everything, this will temporarily disable the AV and firewall) Disable User Administrator Control (UAC) (As per Disabling administrator rights messages in Windows 7 OS and above) Re-install I/NET Seven / Continuum / Vista etc

Issue Improper wiring can damage controllers. Product Line Andover Continuum Environment All i2 and b3 24VAC-powered controllers. Cause Improper wiring, such as reversing the conductors, may result in damage to one or more controllers. Resolution Each i2/b3 low voltage powered controller must have its own 24 VAC step down or isolation transformer. X2 of the transformer must be connected to earth ground AND to the terminal marked with the ground symbol on the controller. X1 of the transformer must be connected to the terminal marked "L" or "24VAC". Here's an example of the proper wiring - the i2_b3+887+Installation+Instructions.pdf. Please reference Field bus (Infinet or MSTP) will shut down as soon as device is connected for more information on why the RS485/MSTP will go down if power is wired incorrectly.

Issue Vista licensing dongle has been lost or stolen from the site. Vista will not run without a valid license. Product Line TAC Vista Environment Vista Licensing Dongle Cause The user dongle has been lost, stolen, or is missing. Resolution You must contact Order Entry for a replacement dongle PN=000857510. Order Entry, Phone: 888-444-1311, E-mail: ccc.service@buildings.schneider-electric.com. See Vista Dongle Guide to get the old Dongle number. Call or email PSS when you receive the new Dongle with both Dongle numbers. PSS will then rehost the license to the new Dongle number. Note: Order Entry/Product Support will be able to assist in verifying which licenses were previously purchased for the site if you do not know.

Issue Communications with the Sigma controllers are not possible. Product Line Satchwell Sigma Environment Communications ARCnet RIP Firewall Cause Communications with the Sigma controllers are not possible because the Windows Firewall is blocking messages. Resolution This article assumes that the Sigma system is using RIP Listener, and that it is operational on the Sigma server. If persistent routes are used, please see Persistent routing on the Sigma server. Turn off the Windows firewall, does this allow normal operation, if it does then follow the steps below. Open the Windows firewall and choose the "Exceptions" tab. Choose Add Port. Enter name "Sigma" - Port number "49152" - "UDP" Select "OK" Repeat the process for RIP Listener. Choose Add Port. Enter name "RIP" - Port number "520" - "UDP" Select "OK" With the Windows firewall turned on test the Sigma communications.

Issue Unable to get a Dual FT Channel L-IP-33ECTBB to communicate after installing in LonMaker. Product Line TAC Vista Environment LonMaker Loytec L-IP Cause Using a "generic" router stencil in the LonMaker drawing as you would when installing a single FT channel L-IP will not work with the Dual FT Channel device. This is because of a virtual 1250 backbone internal to the Dual channel L-IP that the two FT channels hang on. Resolution To properly install a L-IP-33ECTB, use the stencil provided by Loytec. This can be downloaded via the following link: Loytec website Search for "shapes" and download the "LOYTEC Shapes Version 5.0.0" file. Also see How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver.

Issue Configuration of a simple Autodial system. Product Line Satchwell Sigma Environment Sigma Autodial Remote sites Cause Clarification of the setup requirements for a simple configuration. Resolution A simple configuration will consist of the main Sigma site and one remote site. Although this description is based on Sigma 4.05 SEB, the general configuration applies to all releases. Steps to be taken; Configuration of the Sigma server. (Autodial setup.doc). Download CO??.set to the DNN. Connect the modem to the DNN (port ?), using the appropriate connection lead. (Connection lead details). Configure RIP listener on the Sigma server. (See Sigma server communication to ARC-net/Ethernet sub-nets via a DNN failing). If RIP cannot be used add Persistent routes to the Sigma server. (See Persistent routing on the Sigma server). You will need to add routes to the remote site networks. Using the examples show in the Autodial Setup.doc, the following should be entered. Route add -p 192.168.100.0 MASK 255.255.255.0 10.158.72.123 (this is for the Ethernet network). Route add -p 192.168.2.0 MASK 255.255.255.0 10.158.72.123 (this is for the PSTN network). Request data from the remote site, the modem should attempt to dial. Go to the remote site and connect the modem to controller (port ?) using the appropriate connection lead. Connect locally to the controller and download the CO??.set file. Coldstart the controller and allow it to recover from the Default Sigma server.

Issue The LNS credits and the NL220 credits quantities do not match Product Line TAC Vista Environment NL-220 Cause Some LNS credits have been consumed while another NL220 dongle was used on the system. When you commission a device, both a NL credit and a LNS credit are consumed. When using another dongle on a given computer, (likely in “move” mode) it will consume a NL credits from it and a LNS credit from the computer. This can bee seen from the NL220 information bar. Resolution If the LNS credits are inferior, this means you are running in deficit. To fix this, you should order additional LNS credits to level up their quantity. When we deliver you credits, we send at the same time NL and LNS. This is why the dongle has to be confirmed on the computer when ordering credits and also why we highly recommend to commission devices only when the dongle is confirmed. Ordering more LNS credits is a link on how to order LNS credits.

Issue How Many Remote Workstations can be connected to TAC Vista Server using a DEMO LICENSE Product Line TAC Vista Environment TAC Vista 5.x.x Demo License Cause Need to know how many remote users can access a single TAC Vista server using a Demo License. Resolution There is no limitation number announced by the Schneider. Practically, if too many Remote Workstations connects to the TAC Vista Server, It will slow down the speed of the Server and for sure will get some un-expected errors will occur. And if the TAC Vista Server have many graphics and too many Remote Workstations trying to access the same graphics page all at a time, it should affect the performance. But it will not be a problem with 15-to-20 remote connections when the Server PC have a very good configuration. Note: If the Server PC having a high configuration and using the Windows XP the speed differ with the PC using Windows server 2003 or 2008 or Higher. Use "Demo TS_OK_" demo license, if the Vista Server accessing with Windows Remote Desktop Connection. Remote Workstations need to use individual "Demo TS_OK_" demo license file in each machine. Remember that when using the "Demo License" files, Vista does not work on "License Server". Related Articles: How many Remote Workstations can connect to a single TAC Vista Server? Monthly temporary (demo/evaluation) license files for Vista 5 'Unable to request license' message when using Demo license with Remote Workstation Windows Remote Desktop (RDP) is not supported by the TAC Vista Licensing system Remote Desktop Connection issues When Starting Vista Server

Issue Unable to view rooms with Screenmate. After logging in and typing a room number, Screenmate takes a long time searching for the room and eventually times out. Product Line TAC Vista Environment TAC Vista 5.1.X Screenmate 5.1.X Cause This may be caused by slow network communication if Vista is running on a number of networks on a node. Vista will check all nodes for the given Screenmate ID and this can take a long time if there are a lot of objects and/or nodes. Resolution To resolve this issue it is possible to activate a caching function that collects the names of all the available Screenmate objects on all the nodes and stores them in a cache file. This means that the next time a user tries to view a room Screenmate will check in the cached file instead of asking all nodes for their Screenmate objects. To activate this function do the following: Locate the web.config file for TAC Vista web By default this is in c:\inetpub\wwwroot\TACVistaWeb51X\ Open the file (with notepad) and locate the key TAC.WebStation.ScreenMate.CacheEnabled Change the value of this key to "True" and save the changes to the file. Create the cache file Open a web browser and type in Localhost/ScreenMate Try to browse to a room once logged into Screenmate. This will create the cache file. Check under C:\Windows\Temp and see that a file named ScreenMateCache.dat has been created. If the file isn't created: Temporarily delete the other Vista nodes in Vista workstation so that only the master is left. Rerun the steps above - this will create a file containing the local screenmate objects and speed the process up. Add the other TAC Vista nodes again and repeat the steps above shown under "Create the Cache File". The next time the process should be much quicker, once this file is created. If problems persist check the authority settings described in The ScreenMateCache.dat file is not created on a Windows 2008 server.

Issue Event notification is grayed out in the AS and will not allow configuration. Cannot add a category within the AS. Product Line EcoStruxure Building Operation Environment SmartStruxure Shadow AS Event Notification Cause The Event Notification in the AS can be locked due to a shadow relationship with an Event Notification in the ES. Resolution Note the IP address of the AS, as the shadow relationship can be re-established after necessary changes are made. Remove the shadow relationship to the ES to allow configuration of the AS. Detailed instructions can be found in Unable to add an Automation Server underneath an Enterprise Server. Re-established the shadow relationship if needed.

Issue Creating a backup file to download into the controller so it can be extracted at a later date if needed. Extracting and restoring a backup file from a Xenta Server. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder 5.x.x Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the XBuilder project is not set up to send project backup file to target device, you will not be able to extract a backup in the future. On site technicians will be unable to service the XBuilder project if they do not have the original project stored on their PC. Resolution To create a backup to store in the Xenta Server When creating an XBuilder project, check the box titled “Send Project backup file to target device”. If space requirements are an issue, then this option may cause storage overruns. See The size of the generated project is xxxx KB, which exceeds the maximum size of 8192 KB. For an existing XBuilder project, on the menu bar go to Project > Settings… to access this feature. To extract a backed up project from a Xenta Server Connect to the Xenta Server on the 10Base-T port Verify ethernet communications (ping) Open XBuilder Go to Project > Get from Target...

Issue What if you need to send unique SNVTs to more than 13 controllers or groups from a Xenta base unit? Product Line TAC Vista Environment LNS System LON Devices LonMaker/NL220 Cause All devices with Neuron chips in them use an address table. This table holds the neuron addresses or group addresses of each device or group that receives a SNVT from it. That table only holds 15 entries and 2 of them are used in the base units for the TAC group and the Xenta group leaving only 13. Resolution If the signals are sent to a group that only occupies one entry in the address table of the sender and one in each receiver. If the binding is unacknowledged, one entry is taken in the sender for each node or group but not in the receivers. So what if you need a unique occupancy signal for 50 controllers? Or a unique temperature setpoint for them? A group binding will not do because that is one single value to the entire group. The Loytec L-Proxy communicates on Lon networks and is commissioned like other Lonworks devices but uses a proprietary chip set instead of a neuron. This allows its address table to contain 384 entries. It can also have up to 5 ports which can all be commissioned in the same network. So if you send all of your SNVTs from the base units to the L-Proxy (up to 125 of them from a 401), you can let the L-Proxy distribute them to the rest of the devices. Another benefit of that chipset is that the throughput is much greater than the neuron so it can handle such a load. Related Articles: Bind to more than 13 unique LON devices without running out of address table entries No more address table slots for a device involved in the attempted connection. (Subsystem: NS Connections, #15)

Issue Several Xenta 102-AX controllers need to have the CO 2 sensor shared among them in a LNS environment. Product Line TAC Vista Environment CO 2 (Carbon Dioxide) Xenta 102-AX nviCO2 nvoCO2sensor Cause Properly binding a CO 2 sensor output to multiple Xenta 102-AX VAVs. Resolution From the Xenta 102-AX VAV that is connected to the CO 2 sensor, create a binding from the UnivIn3Sense function block/nvoCO2sensor, to VAV_Controller function block/nviCO2 in the receiving Xenta 102-AX VAVs. It will also be necessary to set the send heart beats by following Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller.

Issue Can not connect a SCU controller directly to a Xenta Product Line TAC INET Environment I/NET controllers Xenta controllers Cause No Communication between a Xenta and a SCU controller. A SCU controller can not communicate directly to a Xenta because they speak different protocols. Resolution There must be an interface between an SCU and a Xenta controller, like a 7798C controller for example. The 7798C translates communications from a Sublan to a CLan. It also has a database that keeps track of rules set up by the admin. For a deeper understanding please review Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication.

Issue Continuum worked fine and after a reboot of the workstation, now not receiving alarms and/or controller online/offlines. Product Line Andover Continuum Environment Continuum Cyberstation CX controllers Continuum alarms Cause Communications issues between cyberstation and controllers. Resolution Continuum supports only one network card (NIC) in a Cyberstation. Dual NIC configuration not supported. Note: The issue with dual NIC is that when PC is rebooted there is no guarantee which NIC will become #1 or #2. Please see Cyberstation Access Event Views do not show live events but work on other Cyberstations as well.

Issue When integrating a Integral DVR system Vista crashes Video does not work in Vista CCTV video loss in Vista Product Line Pelco, TAC Vista Environment Vista 5.1.3 Vista Integral DVR SDK v6.6.1.57 Integral DVR SDK v7.0.8 Cause Vista uses the same SDK as Controlpoint uses for an Integral DVR system, this mainly means that Vista SDK needs to be at the same versions as Controlpoint's SDK. A good example of this would be that Vista 5.1.3 use SDK v6.6.1.57 and Integral Digital sentry 7 use a newer version of SDK that is not compatible with SDK v6.6.1.57, a integration of this system then causes Vista to crash. An integration with Vista 5.1.3 would need Integral Digital Sentry 4.1/4.2. Please reference Vista Video Compatibility for more information. Vista 5.1.5 has SDK 7.0.8.0 and it appears that HD support was not included prior to SDK7.0.24.0 Resolution Make sure you have the correct version of Integral Digital version versus Vista version. 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Integral Digital Sentry 4.1/4.2 X X X X X X Integral Digital Sentry 7 X X

Issue At the end of an alarm delay if the point is still in alarm, Continuum will generate the alarm notification regardless of how many times the point has "return to normal" (RTN) during the delay period. If the point goes in to alarm again, Continuum will generate the alarm soon. There is a perception that the alarm delay calculagraph should be cleared when the point has RTN. Product Line Andover Continuum Environment Cyberstation IP level controller Field Controller Cause The behavior of the alarm delay calculagraph in some situations is not what would be expected. Resolution Create an infinityNumeric point to trigger the alarm Create an program to set the alarm point to on/off For Example: The original alarm point is Fanfault, and delay time setting in the AlarmEnrollment is 60 seconds. Create an infinitynumeric named "Fan_alarm" and attach an AlarmEnrollment with a delay. Create the program below: Line detecting: Fan_alarm=off if Fanfault is on then go to setting Line setting if Ts>=60 then Fan_alarm=on if Fanfault is off then goto detecting Line E state=enabled if ts>1 then go to detecting For more detail about AlarmDelay Operation, see AlarmDelay operation.

Issue The Area schedule assignments from "Loose" Areas (ones that are individually attached to the Personnel object) can interfere with those assigned through a Template. Product Line Andover Continuum Environment Continuum Access Control Cyberstation Cause Wish to remove the "loose" Areas so that those assigned by the Template take over. Resolution Here are two methods to do this that will resolve this issue. For large numbers of affected Personnel, use the Personnel Import Utility for this by removing the areas you do not want from the import file. You may need to re-apply the template you want after this as well. See How to conditionally assign areas to personnel objects using the Personnel Input Utility XSLT transformation file that describes this method. For smaller numbers of Personnel the manual method may be better. For each Personnel object. Clear out template assignment. Save the object. Remove all Areas left assigned. Save the object. Re-assign the previous template. Save the object.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Cannot login to DBCreate using Windows Authentication

Sigma alarms are not received at the Enterprise Server

Problem communicating across the LAN on Windows 7 and above PCs

Caution not to reverse the power wiring conductors when installing the i2 and b3 24VAC controllers

Missing/Lost Vista 5 Licensing Dongle

Sigma - Communications with the site DNN's and ARCnet sub-lans are not possible

Dual FT-10 Channel L-IP will not communicate in LonMaker

Sigma - Configuration of a simple Autodial system

NL220 credit mismatch

How Many Remote Workstations can be connected to TAC Vista Server using a DEMO LICENSE

Unable to view rooms with Screenmate

Unable to setup alarm enrollments for AS, functionality is grayed out

XBuilder project backups stored in the Xenta Server controller

Send unique SNVTs to more than 13 controllers or groups

Sharing a CO2 sensor between Xenta 102-AX controllers

SCU controller can not communicate directly to a Xenta 527 or 731

Continuum supports only one network card on workstations

Vista crashes when integrating with an Integral DVR

How to clear the delay calculagraph when an alarm returns to normal

How to remove "loose" Areas from Personnel objects that have Areas assigned with a Template

Building Automation Knowledge Base

Related Forums

This is a heading