Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

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

Building Automation Knowledge Base

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

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
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
Options
  • My Knowledge Base Contributions
  • Subscribe
  • Bookmark
  • Invite a Friend
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
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,209
  • TAC Vista 2,045
  • EcoStruxure Building Operation 1,840
  • TAC IA Series 1,823
  • TAC INET 1,458
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 329
  • Satchwell MicroNet 252
  • EcoStruxure Building Expert 228
  • EcoStruxure Access Expert 148
  • CCTV 53
  • Project Configuration Tool 46
  • EcoStruxure Building Activate 13
  • EcoStruxure Building Advisor 12
  • ESMI Fire Detection 6
  • Automated Engineering Tool 4
  • EcoStruxure Building Data Platform 3
  • EcoStruxure Workplace Advisor 1
  • EcoStruxure for Retail - IMP 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
4
Thumbnail of SmartX IP Controllers
Schneider Electric
SmartX IP Controllers
1
Thumbnail of EcoStruxure™ Building Advisor
Schneider Electric
EcoStruxure™ Building Advisor
1

Related Forums

  • Intelligent 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:
Views
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • …
    • 38
    • 39
    • 40
    • …
    • 507
  • Next »

Change CX level controllers message count to improve I2 communications

Issue How to change the CX level controllers message count to improve I2 Infinet communications. Throttling adjustments using accinfoframe1 and accinfoframe2. Product Line Andover Continuum Environment accinfoframe, accinfoframes, acc info frame Continuum Cyberstation CX 9680 Infinet I2 bus Cause Improve I2 communications on the infinet bus. Changing the CX level controller's message count on the Infinet bus to improve alarm delivery and exported data times when heavy polling is occurring. Resolution TPA-BOST-00-0004.00 describes several fixes, including one that improves field bus with heavy traffic. One of the fixes speeds up graphics and field bus reloads. With the latest version of the firmware the ability to throttle the number of messages during token passing has been added. This will allow a variable to adjust an Infinet bus based on the amount of traffic a particular bus is experiencing. With the latest firmware versions 2.100028, 2.000030 for the Netcontroller 9680 there are variables that can be used to adjust the number of messages per token pass. This is very similar to the MaxInfoFrames setting on Bacnet the devices; we'll call them “accinfoframe” for this document and examples. The value can be adjusted for values of 1-128. Since the TPA was issued, the value is defaulted to 128 and if no accinfoframe variable is created the default value is 128. In order to have the ability to adjust the number of messages in the supported controllers, an infinity numeric needs to be created in the CX/BCX. The name of the variable has to be correctly spelled but is case insensitive. The names are accinfoframe1 and accinfoframe2. Accinfoframe1 will be the setting for comm1 one and accinfoframe2 will control the setting for comm2. When configuring accinfoframe1 or accinfoframe2, make sure to select the SetPoint and back up the flash on your controller, so that you retain the settings in case of power failure. Example of when to use throttling: There will be instances where the accinfoframe variables will need to be throttled. For instance, lets theorize a site “ChillerPlant” and the ChillerPlantCX(9680) has 100 infinet controllers located on Comm1. In our scenario we have 3 workstations each running a graphic polling 2 points(200 points) from each Infinet controller and we are running listviews of infinitynumerics on 8 of the Infinets controllers or perhaps hundreds of points that are being collected for extended logging. As one might think, communications would begin to slow down when polling for values on approx 600 points not to mention the point to point communications of the listviews and extended logs. With all of this traffic, the CX will dominate the network token. Since it can do 128 messages when it receives the token and it receives the token between every Infinet, the token round time can go into minutes. This means that the Infinet controllers can take minutes to deliver alarms and exported data. Another potential scenario is if one selected 4 Infinet controllers to reload, the bus may very well be overloaded at this time and may be receiving errors on the reloads in the distribution window. One of the error messages that could be expected is “Unable to reload object CarlNet\My_9680\My_I2_814\Num_1. An invalid response was received from a remote service request.” In this example we could create a infinity numeric on the CX named accinfoframe1(for Comm1) and start to reduce the number of messages CX would generate before passing the token. On the other extreme, if the ACCInfoFrame setting is set too low, such as to 1 as in the earlier versions of Netcontroller II firmware, this extreme traffic could cause such issues as extreme slowness of graphics and listview updates, Extended logging not being capable of retrieving the required data at the required intervals, and possibly the Infinet controllers randomly appearing to be offline to the system. In the example above the question is “What value should the accinfoframe1 be set to?” The answer entirely depends on how much traffic is on the Infinet bus. How many extended logs, how many listviews, how many graphics, alarms and Plain English programs are creating traffic on the bus? The quick way out here would be set the accinfoframe1 to a value of 1. We know for a fact that this would slow the bus down, and you might want to increase the number to 5. As mentioned this is all dependent on the amount of traffic on the Infinet bus. Or we could take a more in depth approach and find out what the token round time is on the bus and adjust our accinfoframe1 based on token round time. We could create the following points. TOKEN ROUND TIMER PROGRAM InfinityNumeric MaxTokenItem InfinityNumeric MaxTokenRound InfinityNumeric TokenRoundTime Logsize:100 Logtype: LogMaximum InfinityProgram TokenRoundCalc InfinityDateTime LastDateExport Program code: Initialise: LastDateExport = PointMapsTests\Infinity2\i2_851\Date Goto DoTokenRoundCalc DoTokenRoundCalc: If LastDateExport <> PointMapsTests\Infinity2\i2_851\Date then TokenRoundTime = (PointMapsTests\Infinity2\i2_851\Date - LastDateExport) – 1 LastDateExport = PointMapsTests\Infinity2\i2_851\Date Endif MaxTokenRound = maximum(TokenRoundTime) MaxTokenItem = maxitem(TokenRoundTime) E: If TS >= 5 then Goto Initialise The program and points above created in the CX will allow the token round time to be captured and one could essentially get very creative and change the accinfoframe value dynamically through Plain English programming. For these examples we just want to find out the token round time and manually adjust the accinfoframe1 variable to avoid any reload errors. The TokenRoundTime, MaxTokenRound and MaxTokenItem numerics can be added to a watch window or a graphic to visually monitor the TokenRoundTime. If you see that your TokenRoundTime is 5, 10 15 seconds, this is an indication you need to reduce the accinfoframe1 value. As a rule of thumb a TokenRoundTime of less then 2 seconds is acceptable, while keeping the TokenRoundTime below 0.7 seconds is ideal.
View full article
Picard Product_Support
‎2018-09-07 05:18 AM

Last Updated: Administrator DavidFisher Administrator ‎2019-07-09 09:00 AM

Labels:
  • Andover Continuum
3344 Views

Explanation of BACnet MAC address

Issue In EBO BACnet device discovery, how is the BACnet MAC address defined? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause A BACnet device is uniquely identified by a network number and a MAC address. Resolution BACnet MS/TP A BACnet MS/TP device supports device MAC addresses in the range 0-127 for masters and 0-254 for slaves. Device MAC addresses are often configured using DIP switches or a configuration tool.   BACnet/IP MAC addresses for BACnet/IP devices are a combination of the IP address and BACnet/IP UDP Port expressed in hexadecimal notation. For example, if a BACnet/IP device is configured with an IP address of 192.168.1.5 and a UDP port of 47808 then:   IP address expressed in hexadecimal is 192 = C0, 168 = A8, 1 = 01, 5 = 05 UDP port expressed in hexadecimal is 47808 = BAC0   Therefore the MAC address will be, C0:A8:01:05:BA:C0   BACnet/SC BACnet/SC nodes are identified by their 6-octet virtual MAC (VMAC) address in form of a IEEE EUI-48 identifier which is randomly generated. A BACnet/SC device attempts to resolve its own VMAC in the network. If it detects another device is already using this VMAC, it will generate a new Random-48 VMAC address and try again.
View full article
Kirk Mahmoud_Sayed Kirk
‎2022-10-26 03:04 PM

on ‎2022-10-26 03:04 PM

Labels:
  • EcoStruxure Building Operation
3364 Views

How do you reset the Viconics VT7200, VT7300, &amp; VT7600 LON series thermostats back to factory default values?

Issue How do you reset the Viconics VT7200, VT7300, & VT7600 LON series thermostats back to factory default values? Product Line Field Devices Environment SSL SE7000 Cause There's no button or command that sets the thermostat to its default parameter settings. Resolution Either set them manually or through the snvts available via a LON integration.  The Viconics Lon Integration Manual will help with identifying the proper snvts to use.
View full article
Picard Product_Support
‎2018-09-06 02:29 PM

Last Updated: Administrator CraigEl Administrator ‎2023-03-29 04:57 PM

Labels:
  • Field Devices
3343 Views

TGML graphics to display "OFF" and "ON" instead of "0" and "1"

Issue TGML graphics to display "OFF" and "ON" instead of "0" and "1" Product Line EcoStruxure Building Operation, TAC Vista Environment TGML Graphics Editor Cause Data in the Vista database is stored as 0,1 but may be displayed using paired texts. Those paired texts can be set to show up on the graphic, or a unique conversion can take place in TGML. Resolution If you use default snippets that come provided with the editor, you have the option of displaying a value with either NumericPresentation or TextPresentation. The only real difference between the two is that TextPresentation defines the binding's behavior format as "Presentation" rather than "None." This will only display built in presentation formats -- an alarm state will show up as "Alarm" or "Normal" -- or if you've defined paired text within a binary point in the Vista database, that will show up instead of (0,1). This does not, however, explicitly give you the option from within the Graphics Editor to convert decimal values into text. The example TGML code below describes how to take a value that is showing up as "0" and "1" and make it read instead as "OFF" and "ON." <Text>Value   <Bind Attribute="Content" Name="Value">     <ConvertValue SignalEqualTo="0" AttributeValue="OFF"/>     <ConvertValue SignalEqualTo="1" AttributeValue="ON"/>   </Bind> </Text> Cut and paste this TGML code into the editor's Source view to view it in the editor. Just be sure to paste it between the opening tag and closing tag. If all you see in the Source view is one self-closing tag, that is because the page is empty. Either add separate opening and closing tags, or go back to Design view and add one object to the page to automatically split them.You can see here that a Text object has a binding associated with it. That binding's target attribute is "Content" because this will alter the content of the Text. (We could also change the text's stroke color, background color, font size, position on the page, etc., by changing our binding's target attribute.) ConvertValues underneath the binding tell the binding how to alter the Text's content. A SignalEqualTo 0 will write "OFF" to the content and a SignalEqualTo 1 will write "ON" to the content. The number of ConvertValues is not limited to only two. There could be a third one to say that a value of 2 should read "STANDBY."
View full article
Picard Product_Support
‎2018-09-06 02:34 PM

Last Updated: Administrator DavidFisher Administrator ‎2019-06-05 01:26 PM

Labels:
  • EcoStruxure Building Operation
  • TAC Vista
3346 Views

SLP Sensor Modbus RTU issue when used with RPC or Automation Server

Issue SLP Sensor Modbus RTU issue when used with RPC or AS Communication errors are seen during normal Values are updated very slowly, can take up to two minutes to populate/update the 15 objects within the SLP.   Product Line EcoStruxure Building Operation Environment Modbus RTU RPC Modbus Automation Server + Premium  SLP SpaceLogic Sensors LSA_APP_REV2.03.19 and REV2.05.21 Cause Once the Modbus communication is set up between RPC (or AS) and the SLP,  although the values updates fairly regularly, multiple communication errors are also seen The SLP read speed needs to regulated to prevent overwhelming it The SLP Modbus transmission voltage is less than the AS Resolution Use with RP-C SLP struggles to respond to every request from the RP-C, changing the baud rate to 9600/19200 and increasing the "Silence characters" in the interface to 255 (maximum possible) should stabilize the communications.  The character spacing cannot be adjusted enough in the RP-C to allow communication at 38400 or 76800 Use with AS/AS-P  Adjust the “Poll point delay” in the Modbus Interface to 80ms The Silence characters and Transmit guard bits may also need to be increased Baud rate up to 38400 has been tested.  
View full article
Dave_Shore Schneider Alumni (Retired)
‎2021-02-03 06:29 AM

Labels:
  • EcoStruxure Building Operation
3353 Views

Modicon Switch Ordering and RSTP Configuration using EBO with MPX/RPX

Issue Modicon Switch Ordering options and how to configure the Ethernet Switch for RSTP for EBO Product Line EcoStruxure Building Operation Environment Modicon RSTP Switch (Not Connexium) Building Operation Automation Server Premium MPX and/or RPX Controllers Ethernet Switch Configurator Cause Schneider Electric Industry Offers an RSTP enabled Ethernet Switch that can be used with EBO instead of 3rd party Switches Resolution The following video will illustrate the following steps for Ordering and installing the Modicon Ethernet Switch with EBO The Modicon Connexium Ethernet Switch has been replaced by the updated Modicon Switch Modicon Switch Part Numbers and Email address for ordering Connect and use the SE Ethernet Switch Configurator executable for Switch configuration Set the Time and use the Syslog for troubleshooting Configure EBO and the controllers (MPX/RPX) for RSTP Test the Modicon Switch, EBO, and the MPX/RPX controllers for RSTP     Related Links: Modicon Switch Part Numbers and Ordering Information - (see attached Part Number slide) MCSESM Switch Installation Manual MCSESM Switch Configuration Manual Ethernet Switch Configurator Software - look for  SchneiderElectricEthernetSwitchConfigurator2303_Windows_x86.zip Other Modicon Switch documents RSTP Troubleshooting Community Thread TGML Graphic Setup Video (Training Department)
View full article
Admiral Alan_Wood Admiral
‎2022-07-06 08:35 AM

Labels:
  • EcoStruxure Building Operation
3352 Views

Continuum Controller types and their model type numbers

Issue Need the ability to identify controllers on a network and in a database Product Line Andover Continuum Environment Continuum Infinet Bacnet Cause Controllers have an internal model type number reference that can be used to identify which controller is in use on a system Resolution Here's a list of most of the Continuum controller types and their associated numbers Network Controllers Types 9001 1 9200 6 8000 7 9300 18 AC256P 19 9400 22 9410 32 9900 42 9940 44 9924 50 b4920 52 9702 53 bCX9640 55 bCX4000 56 bCX4040 58 9680 61 5720 63 5740 65   Infinity Controller Types 800 2 810 3 850 4 851 5 853 7 890 8 700 9 891 10 892 11 920 13 780 19 865 23 866 24 867 25 701 28 781 29 i2850 40 i2851 41 i2853 42 i2865 43 i2866 44 i2867 45 i2920 46 i2800 47 i2804 48 i2810 49 i2814 50 i2608 51 i2616 52 i2624 53 i2885 54 i2886 55 i2887 56 i2888 57 i2889 58   Bacnet B3 Controller Types b3850 59 b3851 60 b3852 61 b3853 62 b3920 63 b3865 64 b3866 65 b3867 66 b3885 67 b3800 68 b3804 69 b3810 70 b3814 71 b3608 72 b3624 73 b3887 74
View full article
Picard Product_Support
‎2018-09-11 07:45 AM

Last Updated: Administrator DavidFisher Administrator ‎2019-08-22 06:56 AM

Labels:
  • Andover Continuum
3341 Views

PARSER_CODE_ERROR Error in COD file - Error:15

Issue   PARSER_CODE_ERROR Error in COD file - Error:15 When directly downloading a Menta file a Parser Code Error is displayed. This is a Parser Error that is alerting you to the fact that there is a problem with your Code. An error in the Menta file is stopping it from downloading successfully. Product Line TAC Vista Environment Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Direct downloading a Menta file (via the RS-232 port, a serial cable, and Online Simulation Mode) can bring to light Parsing Errors that are not reported by the System Plug-in. These errors will result in unsuccessful download attempts without any indication of the failure. To find them, direct download the Menta file. The download gets to where it is parsing the file before it fails:  There are three known reasons why the parsing of a Menta file will fail with Error Code 15. With some careful investigation of the error the cause can be determined, although checking all known causes is not prohibitively time consuming. Either the Menta application is too large, contains SmartStruxure Function Block following a cut-and-paste of code, or the file has corrupted public values indicated by the values being shown in scientific notation. Resolution First, determine the source of the error. Three known issues are discussed below: Corrupted public values show in scientific notation The Error:15 window attempts to show the user where in the Menta code the error is occurring. Without a fairly intimate knowledge of the inner workings of Menta, this can be less than helpful. However, if scientific notation in a PVR is causing the error, the error window will show this. The first line states: PVR     3,Z4 R1.0762e-042 This is showing that a PVR in the Menta program has a value of 1.0762e-042. It may take some searching, but you will need to locate the PVR in the Menta file that has this corrupted value and change it back to something valid. Also check public constants in the file to make sure they are not corrupted.   SmartStruxure Function Blocks in TAC Menta application This error also appears if there are any SmartStruxure specific Function blocks in the application. RO, BO, RI, BI, TSCHI, ERROR, II, IO, PI, PO Check the if any of the blocks are in the COD file (in the error window), find the blocks and replace/remove them.   Menta Application is too large The only other option is that the Menta application is too large. So if the Error:15 window comes up and does not indicate scientific notation in any of the values, it has to be that the file didn't fit inside the controller. Check the memory in Menta under Options > Memory Usage. You want to see free space in all categories. If there are any negative numbers then that portion of the application is too large. Bear in mind that this is a simple estimation by Menta as to the memory needed. Trend logs, OP tree, network description files and the Menta application all need to be stored in the controller, so sometimes a very low, albeit positive, number can indicate problems as well. Try cutting down on trend logs or OP trees to free up space if the application cannot be reduced.
View full article
Picard Product_Support
‎2018-09-07 03:17 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-17 06:58 AM

Labels:
  • TAC Vista
3324 Views

BACnet error message when trying to use WriteProperty to a 3rd Party BACnet device

Issue When trying to use WriteProperty to a 3rd Party BACnet device the following error is generated : "An attempt has been made to write to a property defined as inaccessible through the BACnet protocol write service" Product Line Andover Continuum Environment BACnet  Cause The error can be seen when using WriteProperty OR when attempting to Manually Command a BACnet Point on a 3rd Party Device Resolution The property that is being commanded, is not available to be written to in the 3rd party device. Many properties and object classes cannot be written to on BACnet devices, this is often defined in the devices PIC Statement which has hopefully also been BTL Tested. Some BACnet devices allow writing to be enabled/ disabled, but this must be set up on the 3rd Party device itself depending on the site requirements.  An example of this is in the Jace unit where there is a regular BACnet user that has no write capabilities from 3rd party devices, so to allow this requires a tick a box for "Super user".
View full article
Picard Product_Support
‎2018-09-11 03:53 AM

Last Updated: Admiral David_Kendrick Admiral ‎2023-06-20 04:54 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
3337 Views

Integrating EBO with ESMI Fire Detection Panel

Issue Would like to monitor and control points and alarms from an ESMI Fire Detection Panel in EBO. Product Line EcoStruxure Buildning Operation Environment Building Operation Automation Server Premium (AS-P) ESMI Fire Detection Panel Cause The integration between ESMI Fire Detection Panel and EBO enables the user to visualize and operate ESMI Fire detection systems effectively from graphics in EBO. Resolution The interface between the ESMI Fire panels and EcoStruxure Building Operation (EBO) is handled by the AS EN54 FIRE SmartDriver. The event and command information is sent/received by the Fire panel using RS-485 communication to/from the AS-P using the SmartDriver.   This resolution is in three steps: Enable communication via RS485 (INFO protocol in Fire panel) Use the AS EN 54 Fire Configurator to create the layout for EBO Install/configure the SmartDriver and create the Fire graphics in the AS-P   Step 1 - Enable communication via RS485 (INFO protocol in Fire panel) This video shows how to enable communication from an ESMI Fire panel and an AS-P over RS485. This is a prerequisite for using the Fire SmartDriver in the AS-P.     Step 2 - Use the AS EN 54 Fire Configurator to create the layout for EBO This video will give you a quick introduction to the AS EN54 Fire Configurator. The AS EN54 Fire Configurator is a Windows application that imports floor plans and configuration files to create the EBO interface, devices, points, alarms and graphics.     Step 3 - Install/configure the SmartDriver and create the Fire graphics in the AS-P This video shows how to connect an EBO SmartX Server to an Esmi Sense Fire detection panel (FDP). And how to create and edit the Fire graphics in the EBO SmartX Server, The fire graphics provide the user interface to visualize and operate Esmi Fire detection systems.  
View full article
Janeway PeterEdvik Janeway
‎2021-11-24 02:24 AM

on ‎2021-11-24 02:24 AM

Labels:
  • EcoStruxure Building Operation
3329 Views

Xenta 527 Appears offline: Troubleshooting steps.

Issue Xenta 527 Appears offline: Troubleshooting steps. Product Line TAC INET Environment I/NET Xenta 527 Xenta 527-NPR Cause Possible Causes: Ethernet Communication is down Ethernet Port is closed Device is configured incorrectly Device failure Resolution Ethernet Communication is down Using the command prompt, ping the device's IP and trace its route. "ping (Insert IP Address)" and "tracert (Inset IP Address)" Watch to see if the Domain server prints out the correct Hostname.  If the device is shown as offline, there may be an error with Firewall settings or Ethernet communication at the Host Workstation. Connect to the router via Internet Explorer If neither of these is possible, Communication is definitely down on the Workstation side. Next, check the Xenta Server side. Disconnect the Ethernet cable from the Device and plug it into a laptop. See if you are on the network.  Ethernet Port Is closed. If the above process shows that Ethernet communication between the Workstation and Router is valid, you may have the port closed. Use a crossover cable to connect a laptop to the device and see if you can connect to a controller ON THAT LINK in I/NET. Look for live values in Controller Summary.  If you can do this, and you can show that Ethernet communication between the two devices is working, then you most likely have a firewall on port 50069 Contact the building IT department Device is configured incorrectly If, in the above process, you cannot connect to I/NET while directly connected to the Router via an Ethernet crossover cable, the device may be configured incorrectly. Open the active I/NET configuration Profile. Ensure that TCP/IP is enabled Add the Router’s IP address to the Reference Host Table Restart the I/O server Check communication Connect to the 527 via HyperTerminal type setip and verify you have been using the correct IP address and hostname type inethost and add the Workstation’s IP address to the Reference host table. restart the 527 Communication should be restored. Device failure Observe the "Run" light on the device.  It should be solid green. Observe the TCP/IP port LED. If you are actively communicating, this should be blinking. If you are unable to connect to the device via a HyperTerminal Direct Connection or Internet explorer while directly connected, you may have a device failure Cycle Power on the device Connect via HyperTerminal (if you cannot do this, try using the failsafe mode. If that fails, replace the device) Type the command “format” to format the device type “setip” and enter the IP information Download and install the latest system file for the 527 you are using. Remember that the 527 and the 527-NPR use different install files. Configure the I/NET communication in HyperTerminal Other Troubleshooting Steps See if the communication error shows up on multiple computers and, if possible multiple locations. There may be an error with Firewall settings or Ethernet communication that only affects part of a large system Host Workstation. Use a different Ethernet port to connect the 527 or workstation to Direct connect to a controller on the controller LAN via TAP and see if any stations are offline.  It is theoretically possible that some form of electrical failure on the controller LAN has caused the 527 to appear offline.  If you cannot see the entire controller LAN from anyone on one device, you should troubleshoot Controller LAN communication. If this is a recurring issue for the site, please download and use the attached 527 offline response document for information gathering and troubleshooting.
View full article
Picard Product_Support
‎2018-09-10 12:27 AM

Last Updated: Guinan RobertAndriolo Guinan ‎2022-11-07 06:32 PM

Labels:
  • TAC INET
3329 Views

Setup External Log Storage using AVEVA PI system

Issue How to configure the EcoStruxure BMS External Log Storage feature using PI System. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need EBO to send selected trend logs and the event log to AVEVA PI System directly without the need for intermediate storage or specialized PI System connectors. Resolution The following video will illustrate how to: Install and configure AVEVA PI system (PI Server and PI Web API) for testing. Configure PI system settings in EBO. Configure trend logs to be written to PI system. View and organized the data in PI system Explorer. Things you need: EBO 2023 (V5.0.3) or higher with valid AVEVA PI System connection license or demo license (Enterprise Server, AS-P, AS-B or Edge Server). AVEVA PI server and PI web API with valid license (Check EBO Information Technology System Planning Guide for tested versions). For more information about PI system recommended architectures, system requirements and installation instructions, please check AVEVA documentation, PI System™ | AVEVA, OSIsoft - PI System and YouTube video published by AVEVA for detailed instructions about installing and setting up PI system Setting up a PI System Development Environment From Scratch - YouTube Note: In EBO V7.0.1 or higher, values can also be read and hosted from an AVEVA PI System, refer to: Hosting Points from AVEVA PI System
View full article
Kirk Mahmoud_Sayed Kirk
‎2023-08-08 12:11 AM

Labels:
  • EcoStruxure Building Operation
3333 Views

Outlook 2007 and Outlook 2010 with Continuum email alarms

Issue Does Continuum support Outlook 2007 and Outlook 2010 as the client for emailing alarms? Product Line Andover Continuum Environment Continuum Cyberstation (v1.93 and above) Microsoft Outlook 2007 (32-bit) Microsoft Outlook 2010 (32-bit) Cause Sending out alarms as emails using Microsoft Outlook. Resolution Outlook 2007(32-bit) and Outlook 2010(32-bit) have been tested by QA with Continuum for emailing of alarms. This is mentioned in the Cyberstation Installation guide. Outlook Express does not work and is not supported. MS Outlook/Exchange 64-bit is not supported across all versions.  For specific information on how to set up emailing of alarms on your Cyberstation please refer to the Continuum Help available on your Continuum Cyberstation or see Creating an EventNotification Email and Page Distribution List. Note: Outlook 2013 and above has not been tested by SQA, but reports from the field are that it does work. In the new versions of Outlook, they have changed the name of the "Personal Distribution List" to the new name of "New Contact Group" Please see How to create a distribution list from your contacts in Outlook for info on how to set up these groups,
View full article
Picard Product_Support
‎2018-09-10 12:41 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 07:06 PM

Labels:
  • Andover Continuum
3319 Views

Using Telnet to test connectivity

Issue How to use the Telnet command to troubleshoot network connectivity and check for blocked network ports. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, Pelco, EcoStruxure Building Expert, Access Expert, Security Expert Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet.     Open Windows Command Prompt Enter :telnet <address_of_remote_server> <port_number>" - telnet 192.168.1.2 443 Result if Port open: blank window with blinking cursor Result if Port closed: error message displayed similar to "Connecting To 192.168.1.2…Could not open connection to the host, on port xx: Connect failed" The example above test for connectivity against the remote server that has the IP address of 192.168.1.2 over port 443
View full article
Lieutenant JG LocNguyen Lieutenant JG
‎2020-01-27 11:23 AM

Last Updated: Kirk AdamSteele Kirk ‎2023-08-16 11:11 PM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • EcoStruxure Security Expert
  • EcoStruxure Workplace Advisor
  • TAC IA Series
  • TAC INET
  • TAC Vista
3322 Views

Sensor pocket thread specification

Issue Thread size/standard. Product Line Field Devices Environment Pocket Well Pocket STP 50mm Brass  9121040000    Pocket STP 100mm Brass  9121041000    Pocket STP 150mm Brass  9121042000    Pocket STP 200mm Brass  9121043000    Pocket STP 250mm Brass  9121044000    Pocket STP 300mm Brass  9121045000    Pocket STP 400mm Brass  9121046000   Pocket STP 50mm Stainl.steel 9121050000    Pocket STP 100mm Stainl.steel 9121051000 Pocket STP 150mm Stainl.steel 9121052000    Pocket STP 200mm Stainl.steel 9121053000    Pocket STP 250mm Stainl.steel 9121054000    Pocket STP 300mm Stainl.steel 9121055000    Pocket STP 400mm Stainl.steel 9121056000 Cause This information is necessary if an adaptor or similar is required for installation. Resolution The thread is of cylindrical type, and follows DIN 228 and BSP (British Standard Pipe) which both are identical. Size of thread is G1/2. For additional information on Pocket materials, please see Sensor pockets material specification Stainless steel and Sensor pockets material specification nickel plated brass.
View full article
Picard Product_Support
‎2018-09-06 03:28 PM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 06:02 PM

Labels:
  • Field Devices
3316 Views

Rules for Upgrading

Issue Upgrading  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Guidelines for upgrading to higher releases Resolution Non-Sequential Upgrades: Versions 1.9.1 and Newer Starting in version 1.9.1, non-sequential upgrades can be performed from versions 1.5.X and newer. Please refer to the "Upgrading" section of the Release Notes for the software version you are upgrading to. The "Upgrading" section will direct you to prior release notes that you need to read through before upgrading and point out items with limited runtime compatibility during the upgrade process.  NOTE: If upgrading a system at 1.5/1.6/1.7/1.8 with LON devices, please be aware that there are special steps that must be taken to prepare the database for upgrade. These steps can be found in the Release Notes as well.  Sequential Upgrades: Versions 1.8.1 and Older For versions 1.8.1 and older, the upgrade process is sequential. In other words 1.2.0, 1.3.0, 1.4.0, 1.4.0.4020, 1.5.0, 1.6.1 The upgrade process can be found in the System Upgrade Reference Guide. The primary released versions were 1.0.0.161 1.1.0.362 1.2.0.767 1.3.0.938 1.3.0.10100 SP1 1.3.0.20011 SP2 1.4.0.4020 1.4.1.68 1.5.0.532 1.6.0.250 (RC) 1.6.1.5000 1.7.0.255 (RC) 1.7.1.89 The minimum upgrade path would be: 1.0.0.161 Official Release 1.1.0.362 Official Release 1.2.0.767 Official Release 1.2.0.2207 1.3.0.938 Official Release 1.3.0.10100 1.4.0.4020 1.4.1.68 Official Release 1.5.0.532 Official Release* 1.6.1.5000 Official Release 1.7.1.89 Official Release Note: On one site, the AS would not upgrade from 1.5.0.532 to 1.6.1.5000. Going to the 1.6 RC resolved the issue.   1. In order to upgrade to 1.5 the site must be at 1.4.0.4020 or higher. Some sites may be still running at 1.4.0.818, which was the original 1.4.0 release. Although this is not officially supported and will not be tested, it is likely to experience the same upgrade as one from 1.4.0.4020. 2. An upgrade from 1.4.0.4020 to 1.5 will NOT offer any runtime compatibility, while an upgrade from 1.4.1 to 1.5 will offer runtime compatibility. Consequently, for a site to maximize its operational status through the upgrade, we have two different upgrade scenarios as described below. a. 1.4.0 to 1.5 – this process flow is designed to allow as much of the plant as possible to continue to operate through the entire upgrade. For the first three steps of the process the Enterprise Server will continue to aggregate the alarms from all of the 1.4.0 Automation Server. Once the halfway mark is reached the Enterprise Server can be upgraded and will begin to aggregate the alarms from the 1.5.0 Automation Server.              i. Upgrade one WorkStation in order to be able to communicate directly to any of the 1.5 Automation Server that are upgraded in b below.             ii. Upgrade 50% of the Automation Server             iii. Upgrade Enterprise Server and all but one WorkStation             iv. Upgrade the remaining Automation Server             v. Upgrade the remaining WorkStation b. 1.4.1 to 1.5 - In this process, we can take advantage of the support for runtime compatibility and the Enterprise Server will receive alarms from both the 1.4.1 and the 1.5 Automation Server.             i. Upgrade Enterprise Server and all but one WorkStation which can be used to talk directly to unupgraded Automation Server if configuration changes are needed             ii. Upgrade Automation Server             iii. Upgrade final WorkStation Note: some sites have experienced issues with the ES restart after upgrade because of the .Net Framework 4.5 upgrade and port 80 usage. Adjusting this port to an available port resolves the problem. The conversion log may indicate an upgrade warning similar to warning shown below, this warning can be safely ignored, and furthermore the upgrade program corrects the problem in the 1.5 database.           :02:11  WARNING:      Property PFE202_PF601.SI in (~/BACnet/Application/ELE/GRAPHIQUES/ECLUSES CD S4/PORTES_CE_S4) is not defined in the new system, skip           PFE202_PF601.SI. <script src="chrome://dce.addin/content/content_javascript.js"> </script>
View full article
Picard Product_Support
‎2018-09-07 02:08 PM

Last Updated: Gary Schneider Alumni (Retired) ‎2022-08-24 07:45 AM

Labels:
  • EcoStruxure Building Operation
3308 Views

SmartStruxure Hardware Input and Output Specifications

Issue Questions regarding specifications of SmartStruxure Hardware Inputs and Outputs Product Line EcoStruxure Building Operation Environment SmartStruxure I/O Modules: AO-8, AO-8-H AO-V-8, AO-V-8-H DI-16 DO-FA-12, DO-FA-12-H DO-FC-8, DO-FC-8-H RTD-DI-16 UI-8-AO-4, UI-8-AO-4-H UI-8-AO-V-4, UI-8-AO-V-4-H UI-8-DO-FC-4, UI-8-DO-FC-4-H UI-16 Cause Different I/O modules have different electrical specifications Resolution Universal Input Specifications Universal inputs can be configured as voltage, current, thermistor, resistance, digital or supervised inputs. Voltage Input Specifications: Range - 0 to 10 VDC Resolution - 12 bit Accuracy - ±(0.7mV + 0.2% of reading) Current Input Specifications: Range - 0 to 20 mA Resolution - 12 bit Accuracy - ±(0.03 mA + 0.4% of reading) Resistance Input Specifications: 10 Ohm to 10 kOhm 10 kOhm to 60 kOhm Thermistor Input Specifications: Range - -50 to 150° C (-58 to 302° F) Thermistors: 10k Type I (Continuum), 10k Type II (I/NET), 10k Type III (Satchwell), 10k Type IV (FD), 1.8k (Xenta), 10k Linearized (Satchwell DRT), 10k Type V (FD w/ 11k shunt), 1k (Balco), 20k (Honeywell), 2.2k (Johnson Controls) Digital Output Specifications Form C Relay: Terminal - Common (C), Normally Open (NO), Normally Closed (NC) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 3 A Form A Relay: Terminals - Common (C), Normally Open (NO) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 2 A LED Specifications: LED Polarity - Represents the actual state of the output; ON if the output is active, OFF if the output is inactive LED Color - Green Analog Output Specifications Analog outputs can be configured as voltage or current. Module Voltage Output: Range - 0 to 10 VDC Resolution - 50 mV Accuracy - ±100 mV Terminals - Voltage (V), Return Minimum Load - Source, 2 mA; Sink, -1mA Current Output: Range - 0 to 20 mA Resolution - 0.1 mA Accuracy - ±0.2 mA Terminals - Current (I), Return Maximum Load - Output load should not exceed 650 Ohms Supervised Input Specifications Supervised inputs can be used to detect sabotage. Detected resistor values - Open circuit, short circuit, contact open, and contact closed. 5 volt circuit, 1 or 2 resistors, monitored - Series only, parallel only and series and switch combinations. For a 2-resistor configuration, each parallel. Resistor value range - 1k to 10 k resistors should have the same value. The selected resistor value needs to be defined in the system. RTD Input Specifications The specifications of the RTD-DI-16 are extensive and thus are best viewed directly in the data sheet available on the Buildings Download Center: RTD-DI-16 Specification Sheet You can also download the specification sheet here: IO Module RTD-DI-16 Specification Sheet (July 2014).pdf.
View full article
Picard Product_Support
‎2018-09-11 01:25 PM

Labels:
  • EcoStruxure Building Operation
3318 Views

Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot?

Issue Laptops are now being supplied with an express card slot instead of a PCMCIA card slot. The LON PCC-10 cards are PCMCIA cards and will not fit in an express card slot. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Using the Lon PCC-10 Card in a laptop that has an express card slot and not a PCMCIA card slot. Cause The latest laptops are being supplied with express card slots. The option of a PCMCIA card slot is becoming harder to specify. Resolution Although the slot in the laptop appears to be the same as a PCMCIA card, the Express card slot differs in many ways to the PCMCIA slot the PCC-10 card requires. Express card slot to PCMCIA card converters are available but not all support the PCC-10 card. Some express card to PCMCIA card converters only support 32 bit PCMCIA cards. The PCC-10 is a 16 bit card. Basic testing has been carried out on an express card to PCMCIA card converter with a LON PCC10 card from Roalan Ltd. You can purchase the EC1632 converter direct from Roalan Ltd. website by credit card through the Sagepay secure web server. Alternatively, you can phone your order to +44 (0)1202 861512 or fax it to +44 (0)1202 891454. The product is plug and play on Windows Vista and Windows 7 with a downloadable utility for Windows XP. (Only required on some computers. It was not required on the Dell E6420 when testing the card.) You can download the utility here: EC1632.zip, or from Roalan's website. Further information on the converter is available on Roalan's website. You may also download the EC1632 Installation Guide. The card should be plug and play. If your PCC-10 card does not work when using the express card converter, check the PCC-10 card installation using under the control panel. If the card is not working correctly review The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. If you need to order a LON PCC10,PCMCIA card, they are available through Schneider Electric specification number WPA-LON-2.
View full article
Picard Product_Support
‎2018-09-10 12:13 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 09:04 PM

Labels:
  • Satchwell BAS & Sigma
  • Satchwell MicroNet
  • TAC IA Series
  • TAC Vista
3312 Views

Error, "Unknown SMTP Host: smtp.broadband.rogers.com" when attempting send email message from an I/A Series UNC.

Issue I have a UNC-520-2 running Niagara 522 that is connected on a local network, with internet access. Alarm emails are not sent and I get the following error message: ERROR: Cannot send mail [/Dundee_2StClair/services/MailService] javax.mail.SendFailedException: Sending failed; nested exception is: javax.mail.MessagingException: Unknown SMTP host: smtp.broadband.rogers.com ; nested exception is: java.net.UnknownHostException at javax.mail.Transport.send0 (bytecode 611) at javax.mail.Transport.send (bytecode 9) at tridium.services.MailService.sendImpl (bytecode 29) at tridium.services.MailService.run (bytecode 44) at java.lang.Thread.run (line 5) Environment I/A Series R2 UNC (520, 410 or JACE-NSX/NXT) Cause Mail server address defined by name (smtp.broadband.rogers.com) No DNS server addresses defined in the IP address configuration of the UNC Resolution The error message indicates that there was no response from the SMTP server address specified.  In this case, since the SMTP server is specified by name instead of its IP address, it is necessary to provide one or more DNS (Domain Name Service) servers that can be used to resolve the address to its associated IP address. To enter one or more DNS addresses, access the UNC via the Admin Tool and select the Network Settings tab. On the lower part of the Network Settings screen, click the [Add] button and enter the IP address of the DNS server in the table.  Repeat this step if additional DNS servers are to be added.  Click the [Apply] to save the settings.  Here is what the screen looks like when two public DNS server addresses have been entered.
View full article
Picard Product_Support
‎2018-09-06 03:55 PM

Labels:
  • TAC IA Series
3304 Views

SmartStruxure - SE IntesisBox does not support Read Property Multiple (RPM).

Issue Binding a SmartStruxure Analogue value to a Analogue output in the SE IntesisBox (Panasonic Air Conditioning). Environment IntesisBox Panasonic RPM Read Property Multiple Cause Attempting to bind the analogue value to the IntesisBox analogue output causes the following error; Resolution In this case, the AS database has the wrong unit (no-units) associated with the object, since it does not match to the units in the device "Degrees-Celsius" the failure occurs' This is corrected in StruxureWare Building Operation 1.5, where the unit id is not uploaded if the device does not support read-property-multiple, and it appears from the device documentation, that the IntesisBox does not support RPM. As an immediate workaround, the user can configure the unit id of the analog output object directly - configure the "Value" property to have a unit of Degrees Celsius.  To view the IntesisBox Panasonic manual, please click HERE.
View full article
Picard Product_Support
‎2018-09-11 06:57 AM

Labels:
  • EcoStruxure Building Operation
3396 Views
  • « Previous
    • 1
    • …
    • 38
    • 39
    • 40
    • …
    • 507
  • 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 board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - 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 © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of