Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • You may be familiar with Communities' brand new layout from SE.com.
  • Don't forget to update your bookmarks and saved links with our new address (https://community.se.com/).
  • If you encounter any issues, please contact SchneiderCommunity.Support@se.com.
Close
Sign In Help
Important Announcement: WELCOME to the Schneider Electric Community! We have moved to a new address: community.se.com — bookmark it today and contact SchneiderCommunity.Support@se.com if you have any questions!
Schneider Electric
Help
Ask the Community Community Guidelines Community User Guide How-To & Best Practices Contact Support
Login / Register
Community Menu
  • Community Home
  • Forums
    • By Topic
        • Support
          • Ask the Community
        • EcoStruxure Building
          • SmartConnector Forum
          • Field Devices Forum
        • EcoStruxure Power & Grid
          • EcoStruxure Energy Hub User Group
          • 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
        • Remote Operations
          • EcoStruxure Geo SCADA Expert Forum
          • Remote Operations Forum
        • Industrial Automation
          • Industry Automation and Control Forum
          • Industrial Edge Computing Forum
          • Alliance System Integrators Forum
          • Machine Automation Forum
          • EcoStruxure Automation Expert / IEC 61499 Forum
          • AVEVA Plant SCADA Forum
          • Modicon PAC Forum
          • Harmony Control Customization Forum
          • Level and Pressure Instrumentation Forum
          • PLC Club Indonesia
          • Fabrika ve Makina Otomasyonu Çözümleri
          • Motorabgangstechnik & Antriebstechnik Forum
          • Korea Industrial Automation Forum
        • Schneider Electric Wiser
          • Schneider Electric Wiser Forum
        • Power Distribution IEC
          • Power Distribution and Digital
          • Solutions for Motor Management
          • Paneelbouw & Energie Distributie
          • Eldistribution & Fastighetsautomation
          • Elektrik Tasarım Dağıtım ve Uygulama Çözümleri
          • Електропроектанти България
          • Specifiers Club ZA Forum
        • Power Distribution NEMA
          • Power Monitoring and Energy Automation NAM
        • Power Distribution Software
          • EcoStruxure Power Design Forum
          • LayoutFAST User Group Forum
        • Solutions for your Business
          • Solutions for your Business Forum
      • Support
        • Ask the Community
      • EcoStruxure Building
        • SmartConnector Forum
        • Field Devices Forum
      • EcoStruxure Power & Grid
        • EcoStruxure Energy Hub User Group
        • 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
      • Remote Operations
        • EcoStruxure Geo SCADA Expert Forum
        • Remote Operations Forum
      • Industrial Automation
        • Industry Automation and Control Forum
        • Industrial Edge Computing Forum
        • Alliance System Integrators Forum
        • Machine Automation Forum
        • EcoStruxure Automation Expert / IEC 61499 Forum
        • AVEVA Plant SCADA Forum
        • Modicon PAC Forum
        • Harmony Control Customization Forum
        • Level and Pressure Instrumentation Forum
        • PLC Club Indonesia
        • Fabrika ve Makina Otomasyonu Çözümleri
        • Motorabgangstechnik & Antriebstechnik Forum
        • Korea Industrial Automation Forum
      • Schneider Electric Wiser
        • Schneider Electric Wiser Forum
      • Power Distribution IEC
        • Power Distribution and Digital
        • Solutions for Motor Management
        • Paneelbouw & Energie Distributie
        • Eldistribution & Fastighetsautomation
        • Elektrik Tasarım Dağıtım ve Uygulama Çözümleri
        • Електропроектанти България
        • Specifiers Club ZA Forum
      • Power Distribution NEMA
        • Power Monitoring and Energy Automation NAM
      • Power Distribution Software
        • EcoStruxure Power Design Forum
        • LayoutFAST User Group Forum
      • Solutions for your Business
        • Solutions for your Business Forum
      • Food & Beverage
      • Healthcare
  • Knowledge Center
    • Building Automation Knowledge Base
    • Geo SCADA Knowledge Base
    • Industrial Automation How-to videos
    • Digital E-books
    • Success Stories Corner
  • Success Stories
  • Events & Webinars
    • All Events
    • Innovation Talks
    • Innovation Summit
    • Let's Exchange Series
    • Technology Partners
    • Power Events & Webinars 
    • Partner Success
    • Process Automation Talks 
  • Ideas
        • Remote Operations
          • EcoStruxure Geo SCADA Expert Ideas
          • Remote Operations Devices Ideas
        • Industrial Automation
          • Modicon Ideas & new features
  • Blogs
    • By Topic
        • EcoStruxure Power & Grid
          • Backstage Access Resources
        • Remote Operations
          • Remote Operations Blog
        • Industrial Automation
          • Industry 4.0 Blog
          • Industrie du Futur France
        • Power Distribution NEMA
          • NEMA Power Foundations Blog
        • Knowledge Center
          • Geo SCADA Knowledge Base
          • Industrial Automation How-to videos
          • Digital E-books
          • Success Stories Corner
      • EcoStruxure Power & Grid
        • Backstage Access Resources
      • Remote Operations
        • Remote Operations Blog
      • Industrial Automation
        • Industry 4.0 Blog
        • Industrie du Futur France
      • Power Distribution NEMA
        • NEMA Power Foundations Blog
      • Knowledge Center
        • Geo SCADA Knowledge Base
        • Industrial Automation How-to videos
        • Digital E-books
        • Success Stories Corner
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
  • Communities
  • :
  • Knowledge Center
  • :
  • Building Automation Knowledge Base
How can we help?
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: 
82790members
350628posts

Building Automation Knowledge Base

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

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

Are repeaters required every 32 nodes on an RS-485 bus?

Issue Are B-link or Infilink repeaters required every 32 nodes on an RS-485 bus when using i2 or b3 controllers? Infinet 1 controller had this requirement Environment Continuum Cause Infinity version 1 controllers required a repeater every 32 nodes. i2/b3 controllers do not have this same node count requirement. Resolution If you are going to be using i2/b3s with no 3rd party bacnet controllers on the segment, it’s less than 4000ft with approved cable, the runs are totally daisy chained without any "Y's" or "T's" in the network runs, then no Infilink/B-link repeaters are needed. The reason for this is that Continuum uses 1/10th load transceivers allowing the full 127 nodes to be used. If you are mixing b3s with 3rd party non-Andover controllers or mixing infinity version 1 infinet controllers with i2s, then you will need a repeater every 32 nodes and every 4000ft. If the distance exceeds 4000 ft, you will need a repeater.
View full article
Picard Product_Support
‎2018-09-06 02:52 PM

Labels:
  • Andover Continuum
629 Views

StruxureWare ETL tool error loading tags from extract task

Issue Performing Load Sources in the StruxureWare ETL tool causes an error with the following header. Environment Extract Transform Load Administration Tool (ETL) Energy Expert (formally Power Manager) Enterprise Server Automation Server Cause The SBO EWS Extract Task settings are incorrect in regards to the SmartStruxure Server that is trying to be accessed.  There was no endpoint listening at... This error is due to the use of the incorrect port number in the Web Service URL. The HTTP request is unauthorized with client authentication scheme 'Digest'. This error is due to the use of the incorrect admin username and/or password.  Resolution The settings of SBO EWS Extract Task need to be verified and corrected.  Click on the Tasks tab in the ETL tool and select the "SBO EWS Extract Task". The extract task setting will be displayed on the right side of the screen. Verify that a valid admin username and password has been entered into the Web Service User Name and Password fields.  Verify that the port number in Web Service URL address corresponds to the port number being used by the Enterprise Server.  Checking the HTTP, HTTPS and TCP port number being used by the Enterprise Server Open the Software Administrator. The ports are listed on the Enterprise Server tab. 
View full article
Picard Product_Support
‎2018-09-10 07:10 PM

Labels:
  • EcoStruxure Building Operation
2373 Views

How to change the Baud Rate of a field bus (Infinet or Bacnet MSTP) when there is an Infilink or B-link on the network

Issue How do I change the Baud Rate of a field bus (either Infinet or Bacnet MSTP) if there is either an Infilink or B-link on the network? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet BACnet Cause The Infilink and B-link must have their baud rate set manually. Resolution All Infinet or Bacnet B3 controllers autobaud on initial startup or when the fieldbus commport is changed from the parent controller's commport editor. The Infilink and B-link must have their baud rate set manually. The proper procedure to change the fieldbus baud rate is to first go to the commport editor and change the fieldbus baud rate. At this point a message is sent to all field bus controllers to change their baud rate. They will all change immediately, however the Infilink and B-link have not yet changed, so the bus will now be in a confused state and there will be offline issues. The next step is to go to the Infilink or B-link repeater and manually change the baud rate to the new setting. At this point the network should work normally, however if the procedure is not followed there may be network issues where you have some controllers that are running at different baud rates causing the network to be totally shut down. If this is the case the way to resolve the issue is to make sure the Infilink or B-link repeater is set to the desired baud rate and power down or reset those controllers on the network so that they will all synch up to the correct Baud Rate upon power up. ** Changing many controllers A method that may help when needing to change the baud rate of many controllers is to bypass the b-link Connect segment 1 of the b-link directly to the BCX comm port and change the baud rate Reconnect the B-link and verify the controllers are now online, repeat the baud change if necessary. Repeat this process for each segment You may still have some isolated controllers that need to be powered off/on. Related: BACnet bCX MSTP network loses communication when a b-Link is added or removed
View full article
Picard Product_Support
‎2018-09-07 12:59 AM

Last Updated: Administrator CraigEl Administrator 2 weeks ago

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
2484 Views

MNL-800 LON SNVT Programming Standards

Issue MNL-800 LON SNVT Programming Standards Environment Workplace Tech Tool software (any version) MNL-800 controller application Cause Problems occasionally arise as a result of improper LON SNVT programming and configuration in the MN-800 device application.  These issues include problems with the re-commissioning of the updated controller and potential network variable mismatch situations. Resolution  The following standards will prevent these problems from occurring. Network variables MUST be manually indexed. This prevents issues with the network variables becoming renumbered when application programming changes are made. (See NOTE 1) Change the application "Program ID" any time network variables are added or removed from an application.  To change the "Program ID" use the WPT Hardware Wizard,  (See NOTE 2) Select Hardware Wizard from Application Menu Click [Next] in MicroNet Setup Wizard screen Change the displayed program ID by entering a different program ID or adding a suffix letter/number. Maximum length is 8 characters. Click [Finish] to save the changed program ID and exit the MicroNet Setup Wizard.  In addition, one method of minimizing the need to repeatedly change the "Program ID" as the application is developed and debugged is to add a few extra common SNVT input and output definitions when first creating the application, leaving them unconnected to the application program.  If one of these SVNTs is needed, it is available in the LON network image (XIF file) and it is not necessary to change the "Program ID". If the MNL-800 controller has firmware version 2.0 (or later) installed, the standard nci network variables do not have to be indexed as the highest numbered SNVTs in the application.  It is perfectly acceptable to number them as the first 17 indexed SNVTs. Note that there are 17 standard network variables (12 nci, 2 nvo & 1 nvi), not just ten nci SNVTs. SNVT variable names should be limited to 16 characters or less.  Longer names are accepted by the WorkPlace Tech programming tool but the names will automatically be truncated by the LON Network Management tool when commissioning the controller. In addition, when programming the MNL-800 applications with the WorkPlace Tech Tool version 5.0, or later, it is not necessary to put each MNL-800 application in a separate project. NOTE 1: If using the WorkPlace Tech Tool version 5.8 or above, you can use the "Object Indexer" to automatically number all the network variables for you.  This tool also includes functions for detecting duplicate SNVT index numbers and for detecting gaps in the assigned index numbers. NOTE 2: If using the WorkPlace Tech Tool version 5.8 or above, you can set an option in the Hardware Wizard to automatically generate a new ProgramID and reindex the network variables when compiling the application.  Please be aware that this automatic generation of the ProgramID will require the Echelon network image for this device to be updated in any Echelon compatible network management tool.  Please refer to the documentation for the network management tool to determine what actions will be required. For example, if Niagara was used to manage the LON network, then the old shadow will need to be deleted, a new one added, and the device points rediscovered and the device re-commissioned.  
View full article
Picard Product_Support
‎2018-09-06 02:50 PM

Labels:
  • TAC IA Series
2035 Views

Input scaling issues with the use of 0 to 5 Vdc and 0 (or 4) to 20 Milliamp transducers on a MNB controller.

Issue Input scaling issues with the use of 0 to 5 Vdc and 0 (or 4) to 20 Milliamp transducers on a MNB controller. Environment MNB Series Controller application program using Analog Input voltage or current inputs. Cause The resolution of the Analog Input object value is determined by the maximum value that can be processed. If the scaled input range is less than 163.84, the output resolution is 0.01 If the scaled input range is greater than 163.84, the output is an integer value. Resolution When programming the Analog Input object in the WorkPlace Tech Tool, it is important to properly configure the input range and scaled value range for this object. If configured for a 0 to 5 VDC input, the sensor properties must be configured as follows: Input Sensor Type (Type): 5 - Volts Input Low Value (LInput): 0 Scaled Low Value (LScale): 0 Input High Value (HInput): 5 Scaled High Value (HScale): (value, up to 16383, corresponding to 5 volt input) See note below. If configured for a 0 to 20 milliamp or 4 to 20 milliamp input, the sensor properties must be configured as follows: Input Sensor Type (Type): 4 - Milliamp Input Low Value (LInput): 0 or 4 (depending on transducer) Scaled Low Value (LScale): 0 (value corresponding to LInput sensed value) Input High Value (HInput): 20 Scaled High Value (HScale): (value, up to 16383, corresponding to 20 milliamp input) See note below. NOTE: The HScale value should be set to give an output value for the Analog Input object that corresponds to the maximum temperature, flow, cfm, etc. that the sensor is measuring. The resolution of the value processed by this object must be taken into account when setting the HScale value because the input to output scaling and precision depends on this scaling constant. If the HScale value is less than 163.83, the input resolution is two decimal places and if greater than 163.83, integer resolution. An example of where this scale range is critical would be the use of a 0 to 5 volt air pressure transducer measuring an air pressure of 0 to 2 InWC. If the HScale is set to 2, the output would only resolve to 0.01. If the HScale value were set to 2000, the output would be in thousandths of an InWC, giving you an effective resolution of 0.001. Since this value is one thousand times the actual measured pressure, this 1000x scale factor would also have to be taken into account in any use of that value within the application.
View full article
Picard Product_Support
‎2018-09-06 02:50 PM

Labels:
  • TAC IA Series
879 Views

Version compatibility between StruxureWare Building Operation Technician Tool and servers

Issue Is a certain version of Technician Tool Mobile Application compatible with all versions of StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool Automation Server Enterprise Server Cause The Technician Tool will always be backwards compatible, meaning that the latest version of the tool will work with any version of SBO. Older versions of the Technician Tool may not work with a newer version of SBO. Resolution Please note: Mobile experience to be replaced with EcoStruxure™ Building Operation v2.0 WebStation. For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool Always use the latest version of Technician Tool Mobile Application when possible, as that will work with all SBO versions.
View full article
Picard Product_Support
‎2018-09-06 08:37 AM

Labels:
  • EcoStruxure Building Operation
1257 Views

How to test the NiCAD Battery on a Controller

Issue There appears to be a low battery on the control board. How can the NiCAD Battery be tested on the controller to see if it needs to be changed? Product Line TAC INET Environment I/NET Seven Cause Possible low battery on control board. Resolution There are some checks you can make regarding the battery condition. The battery has a design life of 7 years and sometimes lasts much longer. With power applied to a controller for at least 72 hours, take a DMM and measure the DC voltage across the battery. It should be in the neighborhood of 4.2-4.3 vDC. Remove power from the controller board and take the same measurement again. The beginning voltage should still be between 4.1-4.3 vDC and should start slowly tapering off (a tenth of a volt over a period of minutes would be normal). When the battery voltage reaches 3.6 vDC this is the threshold at which the battery can sustain the RAM memory. Any voltage below this value will subject the RAM memory to loss of data (+ - a tenth or two). If the initial voltage with power applied to the controller is less than 4.0 vDC after 72 hours, the battery may need replacing. If the battery voltage drops rapidly after power is removed from the controller, the battery needs replacing. If the controller memory inexplicably gets lost (not counting power surges, brownouts, etc.) and a station restore is needed, the battery may need replacing. Normally the above-mentioned tests will show that the battery has lost its storage capacity. The TAC part number for the White NiCAD battery that is on most of the I/Net Controllers is 01-2100-545. These batteries can no longer be ordered through the Customer Care department. For further battery info please reference Replacement I/NET Controller NICAD Battery info.  
View full article
Picard Product_Support
‎2018-09-07 01:02 AM

Last Updated: Administrator CraigEl Administrator 1 week ago

Labels:
  • TAC INET
1350 Views

Webclient unavailable DCOM error or webclient is currently unavailable

Issue Webclient currently unavailable Error 80070005 Check your DCOM permissions when launching webclient or webclient is currently unavailable. Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A remote reboot will not write DCOM permissions the same way a local reboot does. Other Server configurations can cause this. Resolution A webClient installation was performed using Windows Remote Desktop or some other remote access software and the reboot after the webclient install was executed using the remote software. To fix this, reboot the Webclient server directly from the server itself. There are security permissions that do not get written properly when rebooting remotely and a direct reboot corrects this problem. Start Continuum on the Webclient PC locally, not remotely. Be sure Continuum has been started on the webclient PC. Also see, Webclient unavailable error when attempting to logon which mentions making sure the Network Service is selected for the default app pool. 64-bit OS will cause this error as well. Webclient versions pre 1.94 are not supported on any 64 bit platform. If that doesn't work then a complete reinstall and reboot on the server will be required. Remote installs are typically problematic. If changes were made to .net try the following steps: Start> Run> cmd (Enter)  To get to a DOS prompt cd\Windows\microsoft.net\framework\v2.0.50727 (change directory to this folder) run the command aspnet_regiis.exe -i (It will say installing .net, this re-registers .net with IIS) Restart Windows on the webclient PC and restart Continuum
View full article
Picard Product_Support
‎2018-09-07 03:05 AM

Last Updated: Administrator CraigEl Administrator 1 week ago

Labels:
  • Andover Continuum
1406 Views

EcoStruxure Energy Expert. (Formerly Power Manager) licensing access issue

Issue When attempting to access the dashboard URL via the web browser or in SBO Workstation, the following message is displayed. Product Line EcoStruxure Building Operation, EcoStruxure Energy Expert Environment Power Manager 1.2 and newer Power Manager Expert 8.1 and newer Building Operation Workstation Cause A Power Manager 1.2 or newer system running a permanent license allows the user to a log into the Management Console, manual authentication URL, and through the EWS interface in SmartStruxure Workstation. After upgrading to the latest version of Power Manager this access no longer works. The Ports match in License Manager and FlexNet and this site has previously worked. The cause to this issue is that the URL being used has changed starting in PME 8.1. Resolution This issue is due to a change made in the dashboards URL starting in Power Manager 1.2 / Power Manager Expert 8.1. The URL needs to be changed by replacing "Web" with "Dashboards" in the URL found in the EWS link settings or when logging in directly with a web browser.    Example: http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fWeb%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324... http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fDashboards%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324...   Also in the newer versions of Power Manager, there is a limit regarding what can be accessed in PME when using a Power Manager license. In Power Manager 1.2 and on you can access: /Reporter /Dashboards /Trends /HierarchyManager /RateEditor and use the integration toolkit to get into SBO if necessary. Power Manager is now known as EcoStruxure Energy Expert.
View full article
Picard Product_Support
‎2020-12-09 05:45 AM

Labels:
  • EcoStruxure Building Operation
1237 Views

Error during SQL Configuration step for 1.8 WebReports

Issue Error during SQL Configuration step for 1.8 Reports Server Environment WebReports Installer Cause This can happen for various reasons: Possible cause 1 The Microsoft .NET Framework installation is damaged after installing Microsoft SQL Server. Possible cause 2 In one of the steps during SQL installation, we have to configure NT AUTHORITY\SYSTEM. If user fails to change this and move ahead with default user then create database step would fail. Possible cause 3 The operating system is not using English as its selected language. Resolution Solution 1 Quit the WebReports Installer Package Remove/reinstall or repair .NET Framework 4.5 (Available from Microsoft .NET download site or direct download - WebInstaller - OfflineInstaller) Repeat the installation of WebReports   Solution 2 Set the SQL server service log on properties to "Local System" (NT AUTHORITY\SYSTEM) Restart the SQL server service Repeat the installation of WebReports   Solution 3 Replace the WebReports OS with an English version of Windows. 
View full article
Picard Product_Support
‎2018-09-11 11:52 AM

Last Updated: Administrator CraigEl Administrator 1 week ago

Labels:
  • EcoStruxure Building Operation
2671 Views

Changing BACnet Port for Continuum Cyberstation

Issue Changing BACnet Port for Continuum Cyberstation Environment Continuum Cyberstation BACnet controllers Cause Changing the BACnet Port number that Continuum Cyberstation communicates on Resolution By default Continuum Cyberstation communicates on port 47808 in hexadecimal that is BAC0. The BACnet controllers BCX & B4920 have the ability to have their default ports changed. If you change the BACnet port of a BACnet master and want to communicate with the Continuum workstation, you'll need to make a registry change in each workstation. Changing the Continuum Workstation BACnet port This key location is different in 32-bit and 64-bit systems. In 32-bit; the key to change is located in the registry at the path "HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum\Settings". In 64-bit; the key location is now under the "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Andover Controls\Continuum\Settings\" key. Once you're at that path you'll notice a key named "Cyberstation Port" .The value is stored in hexadecimal, so to change it make sure that you enter your new value in hexadecimal. After changing the value in the registry, the Continuum Cyberstation will need to be restarted. Changing the BCX or B4920 BACnet port To change the port on the BACnet controllers either BCX or B4920, open the configuration page in Internet Explorer by putting in the IP address and edit the port settings to the port number that you are changing to. This number will be in regular decimal format. Once changed make sure you save your change and commit the changes to the controller which will restart the controller. Changing the Continuum Workstation BACnet port example. Open the registry editor from Start\Run and enter regedit from the workstation. and explore down to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum\Settings and open the Cyberstation Port key and enter BAC1 which is hex for 47809. If you have the Continuum Cyberstation running you'll need to restart the Cyberstation Once restarted, open the continuum explorer and select the Root and right click and select find new BACnet devices. The controller you have changed will appear as will all of its MSTP devices. Changing the port on a BACnet master controller example. To change the BCX/B4920 BACnet port to 47809 which is BAC1 in hexadecimal. Then log onto the configuration page of the BCX and change the BACnet Port Number -UDP, notice it is displayed in hex but on the controller configuration page you'll change the number using regular decimal. We'll change this to 47809, apply our changes and then on the left hand side select commit and apply on the commit page, which will restart the controller and the new port changes will be in effect. NOTE: If you already have BACnet network established, first delete my whole BACnet side, since after making port changes you don't want other controllers making an attempt to communicate with the previous port number in its known routing table.  IMPORTANT: Anytime you edit a registry, make sure you have backed up the registry and have a contingency plan in case you edit or delete some that that you should not have.  
View full article
Picard Product_Support
‎2018-09-06 02:46 PM

Labels:
  • Andover Continuum
1119 Views

Description of error messages on the LCD display of the old style Infinet controllers

Issue There is an error message on the LCD display of the old style Infinet controllers. What do these errors mean? Product Line Andover Continuum Environment Infinet Controller Cause Information on the error code received on the LCD display. Resolution Infinet controller is displaying error 1 on its LCD display. This message indicates that the controller received a bad packet of data on the Infinet. If the problem persists follow troubleshooting instructions. Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying error 2 on its LCD display. This message means that it could not pass a token to another controller on the Infinet. If the problem persists follow troubleshooting instructions. (No response to the Infinet token pass) Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying an error 3 on its LCD display. This means that the input reference voltage is out of range on the analog inputs. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 4 on its LCD display. This means that the analog output reference voltage is out of range. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 5 on its LCD display. This indicates the controller underwent a reset of power down and retained memory ( warm start). If there is not reason for this to occur power outages etc., then troubleshoot the problem. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Measure the AC power at the controller, Verify it is within specification (nominal +/- 20%). Typically 24 VAC power that is daisy chained will drop the voltage along the connections leaving the power below the acceptable level even if the transformer is sized correctly. Verify that any outputs that are driving inductive loads such as relays, actuators, or valves, have a varistor across the coil n the field device. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.
View full article
Picard Product_Support
‎2018-09-06 02:46 PM

Labels:
  • Andover Continuum
1644 Views

All inputs on an Infinet controller read 999.99 when viewing the electrical value (elecvalue).

Issue All inputs on an Infinet controller read 999.99 when viewing the electrical value (elecvalue). Environment Infinet Controller Cause This indicates that the internal voltage reference is out of range. Resolution Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input.  Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact from a high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diagnostics.  Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. This method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Lastly, a board or controller replacement may be necessary
View full article
Picard Product_Support
‎2018-09-06 02:46 PM

Labels:
  • Andover Continuum
1841 Views

LED on card reader on ACX57xx (ACX2) flickers when it supposed to be solid green

Issue LED on card reader on ACX57xx (ACX2) flickers when it supposed to be solid green Environment ACX57XX Some reader types from HID (such as I-class reader). Cause ACX57XX has new system variables added to get the status of reader connection to controller.(Rdr1Connected ~ Rdr8Connected). In order to check the Status, ACX57xx checks the voltage presence on the LED channel of each reader port. This function causes the LED of some reader types to flicker at a high frequency. Resolution Set the Rdr1Connected ~ Rdr8Connected system variables to Disabled to keep the LED from flickering.
View full article
Picard Product_Support
‎2018-09-06 02:45 PM

Labels:
  • Andover Continuum
594 Views

"Shared Memory" error on startup of Continuum

Issue Start up of Continuum Workstation sees the below error. The Continuum Workstation may continue to start up if the OK button is pressed or may crash.   ContinuumServer.exe error An error occurred during initialization of Continuum Shared Memory by "ContinuumServer.exe". Please restart your system. If this problem persists, please contact technical support. Product Line Andover Continuum Environment Continuum v2.0 SP1 A Windows 32-bit Operating System Cause Beginning with the Andover Continuum 2.0 SP1 Release, Continuum applications now take advantage of the upper memory address space that is available natively on 64-bit Operating Systems (OSs). In order to access these memory addresses on 32-bit OSs, you must reconfigure your 32-bit OS to support applications that are Large Address Aware (LAA).  Resolution Enabled Large Address Aware (LAA). A Windows batch file is included as part of the Continuum 2.0 SP1 release that allows you to reconfigure your 32-bit OS to support applications that are LAA. You will need to ensure that Windows Firewall and Windows Defender are turned off and then run the "laa_update.bat" batch file as an administrator from the installation CD or zip folder.  See page 19 of the Cyberstation v2.0 SP1 Installation Guide for further details.
View full article
Picard Product_Support
‎2018-09-10 12:57 PM

Labels:
  • Andover Continuum
1455 Views

Do 3rd party BACnet MSTP devices count as nodes on a BCX controller that is node limited?

Issue Do 3rd party BACnet MSTP devices count as nodes on a BCX controller that is node limited? Environment BCX controller Third-party BACnet MSTP devices Cause Knowing the information will ensure there is not more node than the   BCX  controller specifies. Resolution Yes they do count as nodes. If you do go over the node count you will see operational problems with the BCX BACnet controller. The BCX controller will scan lock when it tries to perform a time sync to the MSTP network. Modbus nodes communicating via xDriver are not part of the node count.
View full article
Picard Product_Support
‎2018-09-06 02:45 PM

Labels:
  • Andover Continuum
1117 Views

Email/SMS addresses to send alarms directly to a cell phone

Issue What address to use to email/SMS alarms from a SmartStruxure Server, Xenta controller, or Vista to a cell phone Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Vista Server Automation Server Enterprise Server Email, SMS, Text Alarms Cause Vista and SmartStruxure are only capable of sending out SMTP email alarms; however, it can accomplish a "paging" or SMS functionality by sending emails to mobile providers' default email addresses. Resolution For the following services use: T-Mobile 0123456789@tmomail.net Virgin Mobile 0123456789@vmobl.com Cingular 0123456789@cingularme.com Sprint 0123456789@messaging.sprintpcs.com Verizon 0123456789@vtext.com Nextel 0123456789@messaging.nextel.com AT&T 0123456789@txt.att.net 0123456789 = the 10 digit cell phone number When setting up the "From" email address in the Server Setup, it needs to have an @xyz.com for example, at the end of the from address to allow the text message to go through. Note that these addresses could change and you should consult your service provider for details.
View full article
Picard Product_Support
‎2018-09-06 02:45 PM

Last Updated: Administrator DavidFisher Administrator ‎2019-08-28 06:21 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • TAC INET
  • TAC Vista
1713 Views

Power Over Ethernet with Andover Continuum Controllers

Issue While Continuum controllers and EcoStruxure controllers do not utilize Power over Ethernet (POE), can plugging in a Continuum or EcoStruxure controller into a POE switch damage either the POE port or the controller? Product Line Andover Continuum, EcoStruxure Building Operation Environment PoE Ethernet Cause Controllers must be installed on a subnet served by a POE switch. Resolution According to the IEEE standard, a POE switch shall determine if the connected device is POE capable before turning on the power. The detection if a connected unit is POE capable is done by measuring the resistance between the pair #2 - #3 and pairs #1 - #4. On a POE capable unit the resistance is 25kohm, with some tolerance. If it is lower or higher it is not considered to be POE capable. As there are no Continuum or EcoStruxure ethernet controllers that apply a 25K ohm load, a properly functioning switch port will not enable PoE power and the device will not be damaged. Find information on the PoE standard in the Fundamentals of Power Over Internet (PoE) PDF
View full article
Picard Product_Support
‎2018-09-07 01:26 AM

Last Updated: Administrator mroche1 Administrator ‎2022-05-18 09:10 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
1292 Views

Where can I find Cyberkeywriter2.exe to upgrade my CyberStation key.

Issue Where can I find Cyberkeywriter2.exe to upgrade my CyberStation key. Environment Cyberkeywriter2.exe CyberStation Cause There are 3 locations from which you can obtain the Cyberkeywriter2 executable file. Resolution Download Cyberkeywriter2 on The Exchange Download Center Cyberstation CD Do a search of the CD for "Cyberkeywriter2.exe" Cyberstation Workstation From Windows Explorer, search for "Cyberkeywriter2.exe"
View full article
Picard Product_Support
‎2018-09-07 01:45 AM

Labels:
  • Andover Continuum
891 Views

Adding a BCX1-CR-32-INF controller into Cyberstation and the drop down list does not show this as an option

Issue Adding a BCX1-CR-32-INF controller into Cyberstation and the drop down list does not show this as an option Environment BCX1-CR-32-INF CyberStation Cause In CyberStation when adding a controller to the system the drop down list will only show Model numbers and will not show the part number. Resolution See below for examples: BCX1 Router Only Model Number = 4000 BCX1 Bacnet Version Model Number = 4040 BCX1 Onsite Version Model Number = 4020 BCX1 Infinet Version Model Number = 9640  8Meg Netcontroller Model Number = 9900 4Meg Netcontroller Model Number = 9940 2nd Gen Netcontroller Model Number = 9680 ACX2 (8 Door) Model Number = 5740 ACX2 (4 Door) Model Number = 5720
View full article
Picard Product_Support
‎2018-09-06 02:44 PM

Labels:
  • Andover Continuum
713 Views
  • « Previous
    • 1
    • 2
    • 3
    • 4
    • …
    • 489
  • Next »
Labels
  • Andover Continuum 2,194
  • Automated Engineering Tool 4
  • CCTV 54
  • EcoStruxure Access Expert 95
  • EcoStruxure Building Advisor 7
  • EcoStruxure Building Expert 231
  • EcoStruxure Building Operation 1,625
  • EcoStruxure Security Expert 261
  • EcoStruxure Workplace Advisor 1
  • Field Devices 706
  • Project Configuration Tool 26
  • Satchwell BAS & Sigma 473
  • Satchwell MicroNet 256
  • Security Expert 1
  • TAC IA Series 1,802
  • TAC INET 1,462
  • TAC Vista 2,050
  • « Previous
  • 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
2

Related Forums

  • Field Devices Forum
Previous Next
Invite a Colleague
Found this content useful? Share it with a Colleague!
Invite a Colleague

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 Practices
  • Experts Leaderboard
  • Contact Support
 
  • twitter
  • facebook
  • linkedin
  • youtube
  • blog
  • instagram
Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account..

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

Privacy Notice Terms of Use Customize Preferences
© 2022, Schneider Electric