Help
  • Get started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Brand Logo
Help
  • Get started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
close
  • Community Home
  • Forums
    • By Topic
    • By Topic
      EcoStruxure Building
      • Field Devices Forum
      • SmartConnector Forum
      EcoStruxure Power & Grid
      • Gateways and Energy Servers
      • Metering & Power Quality
      APC UPS, Critical Power, Cooling and Racks
      • APC UPS Data Center & Enterprise Solutions Forum
      • APC UPS for Home and Office Forum
      EcoStruxure IT
      • EcoStruxure IT forum
      • EcoStruxure IT™ Advisor CFD
      Remote Operations
      • EcoStruxure Geo SCADA Expert Forum
      • Remote Operations Forum
      Industrial Automation
      • Alliance System Integrators Forum
      • AVEVA Plant SCADA Forum
      • CPG Expert Forum DACH
      • EcoStruxure Automation Expert / IEC 61499 Forum
      • Fabrika ve Makina Otomasyonu Çözümleri
      • Harmony Control Customization Forum
      • Industrial Edge Computing Forum
      • Industry Automation and Control Forum
      • Korea Industrial Automation Forum
      • Machine Automation Forum
      • Modicon PAC Forum
      • PLC Club Indonesia
      Schneider Electric Wiser
      • Schneider Electric Wiser Forum
      Power Distribution IEC
      • Eldistribution & Fastighetsautomation
      • Elektrik Tasarım Dağıtım ve Uygulama Çözümleri
      • Paneelbouw & Energie Distributie
      • Power Distribution and Digital
      • Solutions for Motor Management
      • Specifiers Club ZA Forum
      • Електропроектанти България
      Power Distribution NEMA
      • Power Monitoring and Energy Automation NAM
      Power Distribution Software
      • EcoStruxure Power Design Forum
      • LayoutFAST User Group Forum
      Energy & Sustainability Services
      • Green Building Scoring and Certification Forum
      Light and Room Control
      • SpaceLogic C-Bus Forum
      Solutions for your Business
      • Solutions for your Business Forum
      Support
      • Ask the Community
  • Knowledge Center
    • Building Automation Knowledge Base
    • Geo SCADA Knowledge Base
    • Industrial Automation How-to videos
    • Digital E-books
    • Success Stories Corner
  • Events & Webinars
    • All Events
    • Innovation Talks
    • Innovation Summit
    • Let's Exchange Series
    • Partner Success
    • Process Automation Talks
    • Technology Partners
  • Ideas
    • EcoStruxure Building
      • EcoStruxure Building Advisor Ideas
      Remote Operations
      • EcoStruxure Geo SCADA Expert Ideas
      • Remote Operations Devices Ideas
      Industrial Automation
      • Modicon Ideas & new features
  • Blogs
    • By Topic
    • By Topic
      EcoStruxure Power & Grid
      • Backstage Access Resources
      EcoStruxure IT
      • EcoStruxure IT™ Advisor CFD
      Remote Operations
      • Remote Operations Blog
      Industrial Automation
      • Industrie du Futur France
      • Industry 4.0 Blog
      Power Distribution NEMA
      • NEMA Power Foundations Blog
      Energy & Sustainability Services
      • Active Energy Management Blog
      Light and Room Control
      • KNX Blog
      Knowledge Center
      • Digital E-books
      • Geo SCADA Knowledge Base
      • Industrial Automation How-to videos
      • Success Stories Corner
  • companyImpact

Building Automation Knowledge Base

Access this self-service resource 24/7 and post your questions or scroll through forums for answers on building automation.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Communities
  • Knowledge Center
  • Building Automation Knowledge Base
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we?ll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • Andover Continuum 2,192
  • TAC Vista 2,049
  • TAC IA Series 1,805
  • EcoStruxure Building Operation 1,715
  • TAC INET 1,461
  • Field Devices 712
  • Satchwell BAS & Sigma 475
  • EcoStruxure Security Expert 284
  • Satchwell MicroNet 254
  • EcoStruxure Building Expert 227
  • EcoStruxure Access Expert 124
  • CCTV 53
  • Project Configuration Tool 30
  • EcoStruxure Building Advisor 7
  • Automated Engineering Tool 4
  • EcoStruxure Workplace Advisor 1
  • Previous
  • 1 of 2
  • Next
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • Cody_Failinger
    Cody_Failinger
See More Contributors
Related Products
Thumbnail of EcoStruxure™ Building Operation
Schneider Electric
EcoStruxure™ Building Operation
3

Related Forums

  • Field Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

Building Automation Knowledge Base

Sort by:
Date
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 496
  • Next »

The localhost cannot be opened in the Admin Tool. The error messages: "Cannot open admin session. java.net.ConnectException: Connection refused: connect" is displayed i...

Issue The localhost cannot be opened in the R2 Admin Tool. The error messages: “Cannot open admin session. java.net.ConnectException: Connection refused: connect” is displayed in the popup. The error messages “Niagara service could not be started.” when attempting to start WorkPlace Pro via the console. Product Line TAC IA Series Environment Niagara R2, WorkPlace Pro Cause The WorkPlace Pro PC has AVG software installed. The AVG software stripped out the “niagarad.exe” executable file during the installation of WorkPlace Pro. The Niagara R2 service could not be started without the niagarad.exe file. . Resolution Turn off AVG software and then reinstall the WorkPlace Pro software.
View full article
Picard Product_Support
‎2018-09-06 10:17 AM

Last Updated: Administrator CraigEl Administrator 1 week ago

Labels:
  • TAC IA Series
831 Views

Cannot open admin session Java.net.connect Exception:Connection refused:connect

Issue When trying to open the admin tool in Niagara R2 Workplace Pro, the following error message appears: Cannot open admin session Java.net.connect Exception:Connection refused:connect Product Line TAC IA Series Environment Niagara R2 Workplace Pro Cause This error occurs because the local Niagara service is not running. Resolution Open the console of the desired version Type admininstall install /start Now you should be able to log into an Admin tool session.
View full article
Picard Product_Support
‎2018-09-06 02:56 PM

Last Updated: Administrator CraigEl Administrator 1 week ago

Labels:
  • TAC IA Series
1093 Views

What type of objects can be viewed/created using "Edit in Spreadsheet" mode

Issue What type of objects can be viewed using "Edit in Spreadsheet" mode Product Line EcoStruxure Building Operation Environment Edit in Spreadsheet mode Building Operation WorkStation Cause The objects that can be edited in Spreadsheet mode vary depending on the device or object you are viewing Resolution When you are viewing the AS IO Bus or an AS IO module, then clearly the only objects that cab be configured are Points. Below you can see the "IO" tab, but the "New" tab is greyed out. When viewing a "Folder" in an AS then possible tabs are "Alarm", "Value", "Folder" or "Trend". Below this can be seen (v1.3) LON device, Modbus Devices etc. will allow different access via the spreadsheet mode. This will vary for different versions If you need to find out what spreadsheet access is possible with your chosen device/folder, then it is best to navigate to the relevant Object, folder or device, enter Spreadsheet mode, then check what tabs are available when "New..." is select NOTES: If there is only a single possible spreadsheet object type, then even if there are zero of these object types created, then a blank spreadsheet is shown. If there is more than a single possible spreadsheet object type, and none of these object types are created, then no blank spreadsheet is shown. "New..." needs to be selected. When a row is selected, then an entry modified, all the text data in that row that is visible will be modified. Most EBO objects can be edited using Spreadsheet View with the exception of BACnet Objects. It follows that all objects that exist within MP/RP series controllers cannot be edited in Spreadsheet View as these are all BACnet Objects (This would include Modbus objects within the RP controllers that are actually BACnet objects) For further information refer to the Spreadsheet Overview EBO Webhelp topic  
View full article
Picard Product_Support
‎2018-09-11 12:58 AM

Last Updated: Administrator CraigEl Administrator 1 week ago

Labels:
  • EcoStruxure Building Operation
739 Views

Procedure for configuring the Windows Firewall for use with the I/A Series R2 (Niagara) software

Issue  Interstation links between UNC and Enterprise Server are not functioning. Product Line TAC IA Series Environment Windows 7 Windows Vista Windows XP Niagara R2 Cause Windows Firewall is enabled by default on desktop operating systems post Windows XP SP1. The Windows Firewall must be configured to allow unsolicited messages such as alarms and inter-station links from UNC's to be received by the Enterprise Server. Resolution WINDOWS FIREWALL OVERVIEW Windows Firewall is a “state-full packet filter” firewall by default. This means that all TCP packets trying to enter a system with the Windows Firewall enabled will be discarded unless those packets are responses to queries from that system, or if the packet is destined for a port that has an exception create for it. In other words, unless an exception is created, or the Windows Firewall is disabled a valid message such as an alarm or an inter-station link from a UNC will be blocked by the Windows Firewall and won’t be received by the Enterprise Server. Windows Firewall allows for exceptions to be created for particular ports and from particular ranges of IP addresses. For example, one could create a rule that accepts unsolicited packets on port 25, but only from the range of addresses from 192.168.0.1 through 192.168.0.254. There are two kinds of exceptions: program exceptions and port exceptions. A program exception is where the Windows Firewall is instructed to open ports that a certain program needs for unsolicited communications. This is the preferred method since Windows Firewall is only open while the program is waiting to receive the connection. In contrast, a port exception is the Windows Firewalls' way of acting like a port-filtering router. In other words, Windows Firewall can be configured to let in any traffic on a particular port whether it's solicited or not. Creating a Program Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Program..." Click the browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” adding it to the list of programs. To specify which TCP/IP devices can use the port, click Change Scope and select one of the following To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK. The program will appear selected on the Exceptions tab under Programs and Services. Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Right click Inbound Rules and select New Rule Select program and click Next. Click the Browse button Navigate to the c:\Niagara\Version\Nre\Bin folder. Select the file “nre.exe” and click Open to add it to the list of programs. Click next. Select Allow the connection and click next Select the Network profiles that the rule applies to and click next Domain The domain profile applies to a network when a domain controller is detected for the domain to which the local computer is joined. If you select this box, then the rule applies to network traffic passing through a network adapter connected to this network. Private The private profile applies to a network when it is marked private by the computer administrator and it is not a domain network. Newly detected networks are not marked private by default. A network should be marked private only when there is some kind of security device, such as a network address translator or perimeter firewall, between the computer and the Internet. The private profile settings should be more restrictive than the domain profile settings. Public The public profile applies to a network when the computer is connected directly to a public network, such as one available in airports and coffee shops. The public profile settings should be the most restrictive because the computer is connected to a public network where the security cannot be as tightly controlled as it is in an IT environment. Name the exception and click Finish Creating a Port Exception Windows XP Open Windows Firewall from the Control Panel and from the exceptions tab click "Add Port..." In the Port number field type 80 Select TCP. Type a short name for the port To specify which TCP/IP devices can use the port, click Change Scope and select one of the following. To allow connections from any device, including those on the Internet, select “Any computer (including those on the Internet)”, and then click OK. (This is the default and least secure option) To allow connections from your local subnet only, select “My network (subnet) only”, and then click OK. (This is more secure than the previous option but will still allow a malicious attack from a PC on the network) To define a custom list, select “Custom list”, and then type a list of IP addresses separated by commas. (This is the most secure option) Click OK twice. The Port will appear, selected, on the Exceptions tab, under Programs and Services. Repeat the procedure to add an exception for port 3011 Click OK to finish. Windows 7 Open Windows Firewall from the Control panel then select Advanced Settings: Select  Connection Security Rules: From right side menu, select “New  Rule” Select Rule Type then select Custom then click Next: Select “Protocol and Ports” then select the TCP protocol type, specify required ports, then click Next. This screen capture     shows the configuration for the I/A Series (Niagara) R2 required ports: On the “When does this rule apply screen, click Next, leaving all three areas checked. On the next screen, name the rule “Niagara 80, 3011 TCP” and click “Finish”. Repeat steps 3 through 7, above, selecting UDP instead of TCP.  All other entries are the same except in step 7 the rule name will be UDP instead of TCP. After completing step 8, the Connection Security Rules will be displayed in the center section of the program window.  You should see the following two rules:  
View full article
Picard Product_Support
‎2018-09-06 01:43 PM

Last Updated: Administrator CraigEl Administrator 1 week ago

Labels:
  • TAC IA Series
1350 Views

Restart modes of the second generation Infinity controllers

Issue bCX9640, CX9680, ACX5720 and ACX5740 do not have ACCRestartMode system variable. Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 ACX5720 ACX5740 Cause The restart mode of the second generation Infinity CX controllers (9640, 9680, 5720/40) is not user selectable. Resolution The second generation Infinity CX controllers (9640, 9680, 5720/40) have a fixed startup sequence as follows: Warm to Cool to Cold, meaning the controller will ALWAYS first attempt to WARM start, if warm start is not possible the controller will attempt a COOL start, if cool start if not possible the controller will attempt a COLD start. Warm start: Controller is re-starting with its RAM memory intact because the controller has remained powered or the memory has been kept by the battery. In this case all the configuration data (points, programs) and run time data (logs, points current values) is restored. Cool start: Controller is re-starting with its RAM memory erased or is unable to restore data from RAM for whatever reason. In this case the configuration data only (points, programs) is restored provided it has been previously backed up to flash memory. NOTE: Personnel objects are NOT kept in flash, upon cool start the controller will automatically request a personnel distribution from its access server CyberStation. Cold start: Controller unable to warm start or cool start, all configuration and runtime data will be lost. It must be reloaded from CyberStation.
View full article
Picard Product_Support
‎2018-09-06 12:20 PM

Last Updated: Administrator chris_clerc Administrator 1 week ago

Labels:
  • Andover Continuum
1524 Views

License server port used to reach Building Operation licensing server

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is: https://schneider-electric.flexnetoperations.com If the site of the old server has issues with the non secure communications or the communications forwarding between the previous and the new server, there is a tool available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.
View full article
Picard Product_Support
‎2021-02-17 02:51 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • EcoStruxure Building Operation
  • Satchwell BAS & Sigma
  • TAC Vista
5767 Views

Installing I/NET Seven on a 64-bit operating system

Issue Initialization errors when starting I/NET Seven 2.42 or higher Error: "You must install an instance of SQL 2008R2 (64bit) before completing the INET install" Product Line TAC INET Environment I/NET Seven 2.42 Windows Server 2008 64-bit Windows 7 64-bit SQL 2008 64-bit Windows 8 Cause I/NET 64-bit requires specific installation process in order to function on a 64-bit PC Resolution Installing SQL Download SQL2008 R2 Express 64 bit (SQLEXPR_x64_ENU.exe) from this location: http://www.microsoft.com/en-us/download/details.aspx?id=30438 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 or higher installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install I/NET Seven 2.42 or higher Install I/NET Seven 2.42 or higher using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET NOTE: If error occurs during SQL installation stating invoke or begin invoke failed, follow instructions at this link: http://support.microsoft.com/kb/975055 UPDATE: SQL2008 SP1 prevents the invoke failed error. It can be installed with the same instructions as above. Download it at this link: http://www.microsoft.com/en-us/download/details.aspx?id=25052
View full article
Picard Product_Support
‎2018-09-10 12:28 PM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • TAC INET
4812 Views

Changing a third party BACnet device's object identifier using VTS

Issue The object identifier of a BACnet device (device id) must be unique internetwork-wide, different vendors use different methods for calculating the device id default value. When integrating devices from different vendors sometimes it become necessary to change a device's default object id. Environment bCX4040 b3s Third party BACnet devices Cause BACnet integration Resolution If the BACnet device is a Continuum device (bCX4040 or b3) Continuum provides a mechanism for changing the default device id. For a third party BACnet device VTS can be used to write to the Object Identifier of the device in order to change the device id, note that this will only work if the device manufacturer has made the object identifier for the device object writable. Click here to download VTS Click here to see the procedure to follow to set a third party device id using VTS.
View full article
Picard Product_Support
‎2018-09-06 12:49 PM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • Andover Continuum
1651 Views

What can cause a Continuum controller to reset, cold start or lose data

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.
View full article
Picard Product_Support
‎2018-09-06 11:56 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • Andover Continuum
2483 Views

SpaceLogic SLP series sensor shows as Non-conformant BACnet Device in Discovery

Issue When discovering the SLP Series Living Space Sensors they show up in the BACnet discovery summary as Non-conformant. Attempting to add this non-conformant sensor results in a WorkStation error similar to the following:  Validation Error Workstation Error in "~/BACnet Interface/MSTP Network/Living Space Room Unit 4E5932F5_«1»_07/ForeignAddress". Property value "<device, 10000>" already assigned to "~/BACnet Interface/MSTP Network/SLPSTC2/ForeignAddress". COML Validator0 Product Line EcoStruxure Building Operation Environment BACnet MSTP Living Space SLP Series Air Quality Sensors Living_Space_REV2.05.21 Cause Building Operation does not allow duplicate BACnet IDs and hence, during discovery, if a device is found with a BACnet ID (Object Identifier) the same as an existing device it shows as a non-conforming BACNet device. The default device ID for SLP devices should be equal to (Vendor ID * 1000) + MAC Address. Where vendor ID is our Schneider Electric BACnet vendor ID = 10 and the MAC address is unique to each devices MAC address DIP switch setting. This will be corrected in a future release of the Living Space firmware.  Until corrected, and since the Device ID is a read/write attribute the customer is able to change it to avoid duplicates on the bus. Unfortunately, Building Operation does not currently have a method to write a new device ID. Resolution The current workaround is to use a third-party BACnet Explorer such as Yet Another BACnet Explorer (YABE) to write a new device ID value. Once the new ID has been updated the SLP device can then be rediscovered within Building Operations'. 
View full article
Spock RobertAndriolo Spock
‎2021-03-10 07:08 PM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • EcoStruxure Building Operation
858 Views

PCT Error: "VBoxManager.exe: error: Nonexistent host networking interface", "Failed to open project."

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.
View full article
Picard Product_Support
‎2018-09-10 09:30 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • EcoStruxure Building Operation
  • Project Configuration Tool
4141 Views

Error displayed when importing a device XIF into SmartStruxure

Issue When importing an XIF into SmartStruxure, errors can be generated that vary in nature. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server SmartStruxure Automation Server Building Operation Workstation Cause The XIF does not import successfully for a variety of possible reasons: There exists a device template in the server already that contains the same device ID as the XIF that is being imported.  The XIF does not comply with the LonMark Device Interface File Reference Guide published by LonMark. Resolution Before performing any of the steps below: Import the XIF file provided by the manufacturer of the Lon controller - if the manufacturer did not provide a XIF, try searching the LonMark product catalog If the provided XIF does not work, upload the XIF from the device to ensure that it is the correct file by following How to extract an XIF out of a Lon controller. Use the SBO SNVT Support tool found on The Exchange to identify unsupported SNVT's. Work through the troubleshooting steps below.   Device Template Fails without an Error This issue has been seen in some of the older versions of SmartStruxure (1.5 and older) and upgrading to the latest version will resolve the issue in many cases. If the issue occurs at the latest version of SmartStruxure: Use the SBO SNVT Support tool located on The Exchange to identify unsupported SNVTs. If the SBO SNVT Support tool does not identify any unsupported SNVTs, then send the XIF in to Product Support for further investigation.    Device Template Already Exists In order to complete the import of the XIF, follow these steps. Delete all controllers in that database that are using the device template that has the same device ID as the XIF file you are trying to import.  Now import the XIF again. Select the server in the system tree on the left and go to File > LonWorks import > Device Template. Click the Browse button and select the XIF you want to import. Click Import. Note: When the import is complete it will have overridden the old device template with that device ID. Two device templates with the same device ID will not be able to reside in the same database. For more information about device templates see Delete Device Templates.   Detailed Error Prompt with Specific Fields Listed Some examples of the detailed errors include but are not limited too: "Field X has error(s). The string must between X and X characters. nvoActualCapacity has X characters" on row X. "Field X has error(s). The number must between X and X. Field X has value X." on row X. "Field X has error(s). The value must be X but was X." on row X. Space or tab are not allowed in field 0Node Object on row X.   To Address these issues: Download Notepad++ to be able to better navigate the XIF by row number. Using Notepad++, open the XIF. NOTE: Backup the original XIF just in case there is a mistake when modifying. Find the row and field number prompted by the error messages and modify them accordingly. All the rules can be found in LonMark Device Interface File Reference Guide published by LonMark. Import the XIF again to verify whether it works. If not, contact Product Support for further investigation.
View full article
Picard Product_Support
‎2018-09-11 09:41 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • EcoStruxure Building Operation
2381 Views

WorkPlace Tech Lon communication configuration for use with EBO.

Issue When using an Echelon U10/U20 USB or other Lon network adaptor for communication with a laptop and standalone WorkPlace Tech, not WorkPlace Tech Editor, you must change the default configuration settings.  The default Lon Network Domain ID length (1 byte), Domain ID (18 decimal) and Subnet (254) in the AS-P conflicts with the defaults used by WorkPlace Tech. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech (Lon Network communication settings) Building Operation Automation Server Premium Building Operation Enterprise Server Cause Lon Network configuration Resolution Look at the LonWorks Network "Advanced" tab in the AS-P to determine the addressing information. Open the WorkPlace Tech WorkStation Communication Settings and select LonWorks.  Open the Change Address window Select the "Manual Setup" radio Button Modify to match the AS-P Lon Works Network configuration.  If a different Domain ID or subnet has been assigned in the AS-P, it will need to be assigned the same in WorkPlace Tech You can now browse the LonNetwork from the laptop.  If the MNL devices are assigned applications from the AS-P, do not modify the programs from the WorkPlace Tech Tool  
View full article
Picard Product_Support
‎2018-09-10 10:26 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • EcoStruxure Building Operation
  • TAC IA Series
2027 Views

Seeing "The SSN is invalid for this installation" error when downloading a license update.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. The SSN is invalid for this installation. Product Line EcoStruxure Security Expert Environment Security Expert Cause Wrong SSN being used. The SSN being used is different to what was used when Security Expert was initially installed. Resolution Uninstall Security Expert and re-install using the correct SSN. Backup the SecurityExpert and SecurityExpertEvents databases and copy the resulting backup files somewhere safe. Manual backups can be initiated from the Global > Global Settings menu. Select the directory location and press backup now. Uninstall Security Expert from Windows Add or Remove Programs. Search for "Security Expert" to filter the results. Install Security Expert from available installation files. When asked for the license make sure to use the correct SSN.
View full article
Picard Product_Support
‎2018-09-10 09:48 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • EcoStruxure Security Expert
1725 Views

Replacement of Satchwell "M 1201" Actuator forming part of combined Actuator / 2-port Valve Body assembly due to obsolescence.

Issue Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly requires replacement. Environment Stand alone Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly M 1201 Actuator 2-port Valve Body Cause Obsolescence of Satchwell “M 1201” forming part of combined Actuator / 2-port Valve Body assembly. Resolution There is no direct replacement for the "M 1201" Actuator and as a result both the "M 1201" Actuator and the 2-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly with Schneider Electric MD10B-230 Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B-230 Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. Satchwell MB series 3-port Rotary Shoe Valve Body may be converted for use as a 2-port Zone Valve by means of the installation of a plumber’s plug in Port 3 Install plumber's plug in Port 3 of MB series 3-port Rotary Shoe Valve Body. Tighten plumber's plug sufficiently to ensure PN 10 rating of Valve Body is not compromised. It is possible that the "M 1201" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B-230 Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.
View full article
Picard Product_Support
‎2018-09-10 04:56 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • Field Devices
1201 Views

Some attributes used within Continuum PE programs on b3 controllers are no longer appropriate with SmartStruxure

Issue Some attributes used within Continuum PE programs on b3 controllers are no longer appropriate with SmartStruxure Script programming Environment b3 AS ES ASP ASB MSTP bacnet Cause Some attributes used within Continuum PE programs on b3 controllers are no longer appropriate or cannot be used with SmartStruxure Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType
View full article
Picard Product_Support
‎2018-09-06 10:00 AM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
1062 Views

Learn Process stopped and get an error "Can not learn this controller, it contains an unknown model number"

Warning COMPLEX PROCEDURE REQUIRED. The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance. Issue In some situations, when doing a learn on the CX/BCX controller, the learn process aborts and an error prompt pops up, "Can not learn this controller, it contains an unknown model number." Product Line Andover Continuum Environment Cyberstation CX/BCX I2/B3 Cause Learn process has been executed more than once and at least one has not completed. Some controllers that reside in the CX/BCX have not been cleared and have a duplicate infinetID with some controller in the database. Reloading the CX/BCX controller will indicate which controller has the duplicate InfinetID. Resolution It is recommended to create I2/B3 controllers manually (not by learn) to avoid this problem. If this problem happens: Open the BCX/CX controller and click "reset" Reload BCX/CX controller, from the distribution properties window to find out which controller has the duplicated InfinetID Go to the Continuum Explorer, right click the i2/B3 controller which has the duplicated InfinetID and then select "send to text file" Open the text file, change the infinetID for this controller to another number that does not exist in the database. Delete the i2/B3 controller which has the duplicated ID and import the text file. Reload the CX/BCX controller, there will be no more error. Do learn again on the commport of BCX/CX controller, that should execute successfully. For any other installation issues that also result in this error, please refer to Unknown model number error when learning I2/b3 device
View full article
Picard Product_Support
‎2018-09-10 12:50 PM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • Andover Continuum
1568 Views

Where to find commands used in Security Expert objects to implement new functions

Issue Unable to find details on all commands that have been added to Security Expert objects to implement new functionality. Having this information available would help determine feature set possibilities. Product Line Security Expert Environment Security Expert Client, SP-C Cause Commands used in objects such as Controllers, Doors, and Access Levels may not be documented in the online help, installation, or operation manuals as they are being used to implement new functionality that has not been added to the Security Expert yet. There is no stand-alone list of all available Commands. Resolution Commands are listed in the firmware Release Notes and defined further in Application Notes.
View full article
Janeway AdamSteele Janeway
‎2020-07-28 05:08 PM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • EcoStruxure Security Expert
420 Views

How much ethernet bandwidth do LonWorks systems consume using Loytec L-IPs, iLons, etc.?

Issue How much ethernet bandwidth do lonworks systems consume using Loytec L-IPs, iLons, etc.? Environment TCP/IP ethernet network LNS System Cause IT professionals will sometimes hesitate to allow the control system to use the same TCP/IP network as the internet, phones, etc. They may ask what the expected bandwidth usage will be before granting access. Resolution It is impossible to explicitly state how much bandwidth a LonWorks system will consume on the ethernet. It depends heavily on the amount of LON traffic being sent by the controllers. The routers themselves do not produce traffic, they only pass the traffic onto and off of the ethernet. The traffic is created by the LON devices, Xenta controllers, Vista and LonMaker or other HMIs. Vista can create a maximum of 15 LON telegrams/second. This is very little traffic with respect to IP bandwidth. Unless you have made bindings into the LNS NI (which we never do in a Vista-scenario, since Vista cannot read these) there is basically nothing at all going out from LonMaker/LNS unless you are commissioning devices. Starting the LonMaker Browser also generates traffic. But this is also normally just in the design phase of the network, not in "operating mode". SNVT bindings or TAC network variables from one LON network to another over the IP channel also generate traffic. A typical Xenta can produce 2 SNVTs propagation/second and/or maybe 10 TACNV. This is not much (as IP-traffic), but if there are hundreds of nodes communicating simultaneously all passing through L-IP gateways, the amount of IP traffic will grow. If you are using a Loytec L-IP, it uses a protocol feature called "packet bunching". Before it sends out a packet on the IP side, it waits for an adjustable time (Aggregation Time, default = 16ms) if some packets are following, which have to be sent to the same IP addresses. If some packets are following, it puts the packets in the same IP frame and sends it all together in a single IP packet. The receiving node unpacks it and makes multiple EIA-709 (Lonworks) packets again.
View full article
Picard Product_Support
‎2018-09-06 03:12 PM

Last Updated: Administrator chris_clerc Administrator 2 weeks ago

Labels:
  • TAC Vista
764 Views

Release system memory usage after exporting projects in PCT (Project configuration tool)

Issue System memory usage stays high after exporting projects in PCT (Project configuration tool) Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The exporting process increases memory usage but is still withheld by the project after the process finishes.   Resolution Close the project exported.
View full article
Lt. Commander StephenYang Lt. Commander
2 weeks ago

Labels:
  • EcoStruxure Building Operation
  • Project Configuration Tool
33 Views
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 496
  • Next »
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account?Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2023 Schneider Electric, Inc