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,208
  • TAC Vista 2,045
  • EcoStruxure Building Operation 1,839
  • TAC IA Series 1,822
  • 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:
Helpfulness
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • …
    • 48
    • 49
    • 50
    • …
    • 507
  • Next »

Multi-Purpose Manager (MPM) as a BBMD

Issue Will the Multi-Purpose Manager (MPM) act as a BACnet IP BBMD?   Product Line EcoStruxure Building Expert Environment Site using BACnet and one or more  SmartStruxe Lite Multi-Purpose Manager (SSL MPM)  Cause Can the MPM act as a BBMD Resolution The MPM cannot act as a BACnet Broadcast Management Device (BBMD), but it can be a foreign device to another BBMD BACnet protocol includes broadcast traffic which does not pass through on-site routers. For BACnet devices to network across a wide area or across multiple separate sites connected by the Internet, it is necessary to register the BACnet devices with a Schneider BBMD using the Foreign Device Registration function in Building Expert. For a Multi-Purpose Manager (MPM) running Building Expert to function as a BACnet device, when being managed remotely over a standard TCP/IP network, it must be configured as a Foreign Device. It must also be registered on an Automation Server (AS) on the remote network that acts as a BBMD. Once done, BACnet devices can send messages to the BBMD, which are translated by the BBMD so they can pass over a standard on-site router. Then BBMD forwards the messages to the appropriate destination MPM controlling the Devices for which the BACnet messages were originally intended. Then the MPM translates the messages received over the network from the BBMD into standard BACnet messages and passes them on to the intended Devices as if they were direct BACnet messages. This Foreign Device Registration feature allows a single user with a StruxureWare Building Operations (StruxureWare Building Operation) terminal to remotely oversee multiple disparate sites simultaneously using BACnet, without having to install expensive direct connections to each site. You must have Firmware release version 2.9 or higher installed on your Manager to use Foreign Device Registration function. Here is the BACnet-Specifications-PIC-Statement.pdf And the  explanation on how to setup the DR-ForeignDeviceRegistration.pdf
View full article
Picard Product_Support
‎2018-09-11 06:54 AM

Last Updated: Lieutenant MaximeLaudren Lieutenant ‎2022-08-18 08:56 AM

Labels:
  • EcoStruxure Building Expert
3462 Views

Discovering Lon Devices in SmartStruxure

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document 
View full article
Picard Product_Support
‎2018-09-11 02:56 PM

Last Updated: Janeway Jonas_Brissman Janeway ‎2022-03-17 02:39 AM

Labels:
  • EcoStruxure Building Operation
5281 Views

Understanding BACnet BBMD Distribution Mask.

Issue When configuring a BBMD what is the Broadcast Distribution Mask and what are the valid settings for the field. Continuum EcoStruxure Building Operation Product Line EcoStruxure Building Operation, Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution When configuring a BBMD the BACnet protocol defines two methods of propagating the broadcasts messages to other networks. The two methods are referred to as One-Hop also known as a Directed Broadcast and Two-Hop.   Note: In this article the subnet mask is shown using Classless Inter-Domain Routing(CIDR) notation. An IPV4 address is 32 bits long, CIDR notation defines the number of bits used for the subnet mask. The most commonly used are: /8 or 255.0.0.0 /16 or 255.255.0.0 /24 or 255.255.255.0 /32 or 255.255.255.255 One-Hop With the One-Hop method the local BBMD transfers the message directly to the remote devices via the remote router. In this case the IP routers have to support the transfer of IP broadcast messages to remote IP subnets Figure 1 Figure 1 above illustrates the one-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a message directly to the broadcast address of the 192.168.1.0/24 subnet, it is then up to Router2 to send the directed broadcast to all devices on the subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks. (i.e a bCX hosting an MSTP network on COMM2)   Two-Hop With the Two-Hop procedure a BBMD device transfers broadcast messages to a further BBMD in the remote IP subnet, which then distributes the messages in its local network as IP broadcast messages for its IP subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks.(i.e a bCX hosting an MSTP network on COMM2) Figure 2 Figure 2  above illustrates the two-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a unicast message to each BBMD device on its table, it is then up to each BBMD device on each subnet to send a broadcast that will be heard by all devices on the subnet. Which distribution mask should be used? As mentioned earlier, in order for the one-hop method to work, the router on the remote subnet MUST be configured to process incoming messages sent to the broadcast IP address, the two-hop method on the other hand is guaranteed to work, so when in doubt use the two-hop method. Most sites use two-hop distribution for the reason stated above,, the only obvious disadvantage of the two-hop method is that it is a little more verbose than the one-hop method since the message appears twice on the subnet, once as a unicast sent to the BBMD device and then again as a broadcast sent by the BBMD device. In Building Operation and Continuum the distribution mask defaults to the two-hop method (/32 or 255.255.255.255) How to configure the distribution mask For one-hop enter the subnet mask of the remote network in the distribution mask, the system will apply the mask to the IP address to obtain the broadcast address for the remote network. For two-hop enter 255.255.255.255, this tells the system not to do a direct broadcast and instead do a unicast to the remote BBMD device. Sample distribution mask In the BBMD table of a bCX shown in the screen shot above, BDT #1 and #3 use the two-hop method while BDT entry #2 uses the one-hop method.
View full article
Picard Product_Support
‎2020-12-17 06:47 AM

Last Updated: Administrator CraigEl Administrator ‎2022-09-12 08:46 PM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
6308 Views

Deleting Custom Reports

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Deleting reports built in Reports Builder using Building Operation WebReports Environment SmartStruxure Building Operation running Reports Server and Microsoft Report Builder Cause Reports built using SQL interface such as Microsoft Report Builder cannot be deleted using the Manage Reports in Building Operation WebReports Resolution Building reports on the SQL side must be deleted on the SQL side.   From the first screenshot below, you can see that when using WebReports, in the Manage Reports tab, custom reports which are made are considered System Reports and the Delete button is grayed out.  Here I have created Top Alarms Test 1 report, which has been selected. Using SQL Server Management Studio, I penetrate to the tb.ReportGroups and see the isSystemOwned is True for the report Top Alarms Test 1 The isSystemOwned is changed to False for the selected report(s) Top Alarms Test 1 Viewing WebReports, in the Manage Reports tab, the Top Alarms Test 1 report is selected and the Delete option is available.
View full article
Picard Product_Support
‎2018-09-11 06:59 AM

Labels:
  • EcoStruxure Building Operation
1860 Views

Replace 7792 (7790) and 7793 (7790A) LIU with 7798C

Issue Separate a 7792 or 7793 into two 7798C Split SAV files  Product Line TAC INET Environment I/NET Seven 779x Controllers Cause Need to replace a 7792 or 7793 which has two station addresses and replace with two 7798C Controllers which have one station address Resolution To split the required SAV Files: Download and Extract the attached SAV_Split_EXE.zip Make a backup of the I/NET Seven system using DBCreate. Perform Station Save to all the required controllers Copy the SAV files that need to be split to the same location where the ZIP file was extracted too in step 1. Run the SAV_Splt.exe The commands are showing the Sav_Splt.txt file contained within the ZIP file and shown below Purpose: Use this tool to create two 7798 SAV files from a dual-station 7793 SAV file. Syntax: Sav_Split.exe (with no parameters will check all save files in the current directory and split 2 station 7793s.) Sav_Split.exe LLSS (where LL = Link and SS = Station) Result: The resulting files will be named DCULLSS-0.SAV and DCULLSS-1.SAV. Rename these files appropriately to match the link and station of the 7798 into which each will be loaded. Example: SavSplit.exe 0906 Results: DCU0906-0.SAV and DCU0906-1.SAV     Finally check the split files using the "Work Offline" mode within I/NET Workstation. Any issues or additional questions please raise a case with your local support   For SAV file upgrade information see How to upgrade bin and SAV files in I/NET controllers.
View full article
Picard Product_Support
‎2020-10-20 06:44 PM

Last Updated: Administrator CraigEl Administrator ‎2022-08-07 10:58 PM

Labels:
  • TAC INET
1962 Views

Graphic/TGML are slow and/or not responsive

Issue TGML pages are slow to load in Workstation TGML objects are not responsive Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation TGML Cause The driver of the graphic card is outdated or not supported. Resolution Visit the webpage of the PC's brand and update the driver for the graphic card.
View full article
Picard Product_Support
‎2018-09-06 09:40 AM

Last Updated: Captain SharlinaRe Captain ‎2022-08-24 08:43 AM

Labels:
  • EcoStruxure Building Operation
2198 Views

Which controllers support the String object?

Issue Can Strings be used in all controller types? Product Line Andover Continuum, EcoStruxure Building Operation Environment All Continuum Controllers b3, i2 Controller (EcoStruxure Building Operation) Cause Some Controllers do not support strings Resolution The String class of object are supported in the following products: CX series (including all Netcontrollers), bCX series, CMX series, ACX series, i2 series (except i2885, i2887), BACnet series (except b3885, b3887), DCX 250, CyberStation.
View full article
Picard Product_Support
‎2020-10-05 07:32 AM

on ‎2020-10-05 07:32 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
1948 Views

INET DPU/SCU Transition Architecture - Controller LAN

Issue Sales literature shows the use of NV202, are these the only supported device and are these provided by Schneider  Product Line TAC INET, Security Expert Environment Security Expert SP-C I/NET Access Control Hardware   Cause The NetSys NV202 product was sourced to provide a solution for a large I/NET Site that had multiple 7798B / 7798C controllers communicating back to a single Xenta 527.  As these I/NET Controller LAN devices only communicate via RS-485, a method of using this existing RS-485 cabling to support the SP-C Ethernet connection needed to be sourced.  Tests were carried out to see their performance, which is provided in the resolution below.  These devices are provided by NetSys and if necessary should be purchased directly through their distribution centers.  Documentation for this device is also provided on their website.  Resolution The following shows the tests, methods, and results performed with the NetSys NV-202 on a transition I/NET Database with over 25,000 users and over 5,000 doors. Testing and Validation of proposed NV-202 based RS485 Network Replacement Solution Test Equipment 49 Netsys NV-202 devices and power supplies 25 SP-C Controllers Security Expert Software 4.2.251.19 installation on a PC with the following specification: Processor Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz Installed RAM 16.0 GB 240m Belden 9842 Twisted Pair cable PLUS 50 Ohm resistances for line length simulation to an equivalent run length of 840m 100Mbps switch for interconnection of server PC and controller LAN Test Scenario 30 NV-202 units and in the following network topology. Figure 1: Test System Topology Method The Security Expert server was loaded with a database backup from an I/NET Transitioned Site, which was then modified to include: Connection to the SP-C’s on the IP range 192.168.1.200-192.168.1.224. by modifying existing real-world controller records to match (Database ID’s 149 onwards) Increasing the record load on each controller to the full set of users in the database (21,522) to be downloaded by adding an Access Level containing a door on each controller to each User A Status Page containing an All Events window All controllers were connected to the same 100Mbps switch as the test PC containing Security Expert The last controller in the daisy chain had one input wired into Relay 1 of the controller; this was used to validate input change timing. Download was forced to all controllers Timing for each required parameter (as noted in Figure 2) was measured using the final controller at the end of the cable run, having worst-case characteristics of bandwidth/latency due to maximum number of daisy-chained NV-202 devices Figure 2: Tested Timing Parameters Results Command Response Time Manual commands (by right-clicking and selecting ‘Unlock Door’) were performed on the first door programmed on the SP-C. 25 activations were run and the worst-case results selected. Command response time is less than 2 seconds as stipulated. See Wireshark capture: Figure 3: Packet capture of a Manual Door Unlock command to the worst-case SP-C from Security Expert Software Status Changes Response Time Relay 1 of the SP-C was activated, which is wired to Input 1 of the same SP-C in order to close the input and trigger a status change. 25 activations were run and the worst-case results selected. Status Change response is less than 1 second stipulated. Door Status Changes response time Manual commands (by right-clicking and selecting ‘Unlock Door’) were performed on the first door programmed on the SP-C. 25 activations were run and the worst-case results selected. Door status change response is less than 1 second stipulated. Retrieve access data or user’s data Not applicable. This data is stored in the server database. Generate any single ad-hoc reports Not applicable, reports are generated by the server using data from the server database. Multiple access control levels Not Applicable to this test - Security Expert can store unlimited Access Levels, and associate any of them to a given User. Access Level/User quantity limitations are not affected by the NV-202. EOD download time: A Force Download operation was performed on the SP-C, and the time to completion recorded. 25 activations were run and the worst-case results selected. Maximum download time: 58 seconds per controller (noting 21,522 Users) Time synchronization – maintain synchronism Time update packets are successfully sent, Server and controller time maintained within 1 second. Time synchronization – accuracy Not Applicable to this test – time is updated periodically (not constantly) so not significantly affected by bandwidth or latency.
View full article
Guinan RobertAndriolo Guinan
‎2020-07-12 04:42 PM

Last Updated: Kirk AdamSteele Kirk ‎2020-07-15 04:24 AM

Labels:
  • EcoStruxure Security Expert
  • TAC INET
1831 Views

Unable to bring Suprema Biometric Reader online in Security Expert

   
View full article
HenrikTarpgaard Schneider Alumni (Retired)
‎2020-07-02 12:07 AM

Last Updated: Administrator CraigEl Administrator ‎2024-01-22 03:33 PM

Labels:
  • EcoStruxure Security Expert
1698 Views

What are the fields in the FIPS-201 PIV FASC-N?

Issue What are the fields in the FIPS-201 PIV FASC-N? Product Line Andover Continuum Environment CyberStation NC2 (9680) ACX2 (ACX5720, ACX5740) Cause Documentation Resolution The Federal Agency Smart Credential Number (FASC-N) consists of 40 total characters encoded as Packed Binary Coded Decimal (BCD) format with odd parity creating a 200 bit (25 byte) record.
View full article
Picard Product_Support
‎2018-09-11 06:29 AM

Last Updated: Administrator CraigEl Administrator ‎2023-04-18 08:41 PM

Labels:
  • Andover Continuum
4638 Views

EBO INET Transition ChangeSet Type Index error in Trace log

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line EcoStruxure Building Operation, TAC INET Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   
View full article
Guinan RobertAndriolo Guinan
‎2020-08-24 05:48 PM

Labels:
  • EcoStruxure Building Operation
  • TAC INET
1634 Views

SER8300 power supply voltage

Issue The SE8000 documentation states that the power supply voltage is 7 Volts DC but the circuit board sticker says 7 VDC/24 VAC. Can the controller be powered from 24 VAC? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause An incompatible relay pack might have been used. Resolution Typically the SER8300 range are intended to have power supplied by the SC3000 relay pack which supplies the 7VDC. If an SC3000 relay pack is not used, for example, if the SER8300 is just being used as a wireless device then it is acceptable to power it from 24VAC.
View full article
Picard Product_Support
‎2018-09-06 09:38 AM

Last Updated: Lt. Commander Ramaaly Lt. Commander ‎2022-04-05 06:41 AM

Labels:
  • EcoStruxure Building Expert
  • Field Devices
1627 Views

BACnet devices not found but are visible in other applications

Issue BACnet devices not found but are visible in other third party BACnet applications An update may cause devices to go offline Product Line EcoStruxure Building Operation Environment BACnet IP Network Building Operation EnterpriseServer Building Operation Automation Server (AS, AS-P, AS-B) Cause According to BACnet routing rules, each BACnet Device should have a unique BACnet Instance ID and each BACnet Network should have a unique BACnet Network ID  When a BACnet interface is created on an EBO Server, a BACnet IP network is created with default Network ID of 1. This is a local Network address and in not published on the network, it is therefore not a problem if this is duplicated with other EBO Servers. On many site this will remain at 1 for multiple EBO servers with no problems. If a third party BACnet device uses a published Network ID that is identical to the EBO local Network ID, then it will be ignored. There will be a "Duplicate of local network"  System Alarm and line similar to below in the trace log "nsp.pin.BACnet Device <device name>claims to be router to Network #1234 but that is a local network (BACnetMain)" Resolution If the EBO Server is not finding a BACnet device on a different network type (via BACnet routing like MSTP or virtual IP) then it could be the Network ID is identical to the local EBO Server Network ID. If this is the case, then simply change the EBO local Network ID and retest. BACnet Devices on the same IP network, including those on different IP subnets and linked via BBMD or Foreign Devices are not BACnet routed and therefore will not have this issue (no BACnet Network ID route is involved) Some earlier versions of EBO did not ignore these duplicate Network IDs, thus when up grading some devices could go offline. The workaround would be the same. The correction to the BACnet operation occurred in v1.9.3 and v2.0.2
View full article
Dave_Shore Schneider Alumni (Retired)
‎2020-06-19 06:01 AM

Last Updated: Sisko DavidChild Sisko ‎2020-06-19 06:01 AM

Labels:
  • EcoStruxure Building Operation
4537 Views

Health status shows "too many remote controllers assigned" message

Issue Controller Health Status shows, "Controller (ID **) has too many Remote Controllers assigned." What does this message mean, and is it a cause for concern? Product Line Security Expert Environment Security Expert Client SP-C Controller Cause This error message is related to cross controller communication. When using cross controller communications, the maximum number of controllers that can be linked together is 64. For additional details on cross controller communications, see page 4 of AN 180 Security Expert - Cross Controller Operations - Integration Guide. Resolution The controllers that are not taking part in cross controller linking are the ones that are showing the "Controller (ID **) has too many Remote Controllers assigned." message. Evaluate what values/controllers are being shared to ensure your programming is performing as expected. See AN 180 Security Expert - Cross Controller Operations - Integration Guide for further details on cross controller communications and which values use this. Limit the number of sharing controllers to 64 or split the controllers up into two systems.
View full article
Kirk AdamSteele Kirk
‎2020-06-22 04:22 PM

on ‎2020-06-22 04:22 PM

Labels:
  • EcoStruxure Security Expert
1046 Views

Why is the MSTP network on the Automation Server offline?

Issue Looking at the Status Information on the MSTP network object under the BACnet Interface of the Automation Server, the status read online FALSE Environment Automation Server - AS Cause The AS is not being passed the network token. If the Automation Server sees the token being passed on the bus but it never receives the token the AS will tag the MSTP network status as OFFLINE.. Resolution Possible reasons/solutions. CAUSE: Baud rate mismatch with third party devices. SOLUTION: If device does not support auto-baud change the speed of the MSTP to that of the device. CAUSE: A device on the MSTP is using the same mac id as the MSTP port. SOLUTION: Resolve the duplicate id issue. CAUSE: A defective device on the MSTP SOLUTION: Identify the defective device and replace it.
View full article
Picard Product_Support
‎2018-09-11 06:29 AM

Labels:
  • EcoStruxure Building Operation
2396 Views

Disabling Device Ping Alarms in Niagara G3 (AX)

Issue Would like the ability to disable "Ping Failed" alarms in G3 Environment Tridium Niagara G3 (AX) network controllers (ENC, JACE-645, JACE6, JACE7) Cause Network communication issues sometimes causes device to timeout on a ping request, but quickly recovers. This failure causes an unnecessary alarm to be generated. Resolution 1.  Go to the Property Sheet of the appropriate network (e.g.. Lonworks Network, Bacnet Network) 2.  Expand Monitor, and set the Alarm on Failure field to False. 3.  Click Save  
View full article
Picard Product_Support
‎2018-09-06 09:38 AM

Labels:
  • TAC IA Series
3029 Views

Where to find Evaluation license for TAC Vista and EcoStruxure Building Operation

Issue Locate the Evaluation license for TAC Vista or EcoStruxure Building Operation Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista EcoStruxure Building Operation Cause There is an evaluation license available for TAC Vista valid one month and an Evalauation license for EcoStruxure Building Operation valid 3 months.  Resolution Evaluation or demo license files are available for licensed partners on the EcoXpert Extranet. Follow the link and search for "evaluation". You must first register using your business email (i.e. CustomerName@partnerdomain.com) address to gain access to these files. Note: You may use any email address to register and view content, but downloads will only be granted to approved partner domain names.
View full article
Picard Product_Support
‎2018-09-11 06:30 AM

Last Updated: Administrator CraigEl Administrator ‎2023-10-19 04:20 PM

Labels:
  • EcoStruxure Building Operation
  • TAC Vista
3887 Views

Configuring the Engage Mobile app

Issue What are the basics steps when setting up the Engage Mobile application to use it for the first time? Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) Cause The Engage mobile application enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. Resolution Below are the basic steps when setting up the Engage Mobile application to use it for the first time:  First create and configure the Occupant App Menu object. Make sure Bluetooth is enabled for the RP-C. Download the Engage mobile application and connect to the RP-C Available on App Store and Google Play To see details for every step please see video:  
View full article
Janeway Jonas_Brissman Janeway
‎2020-06-22 06:00 PM

Last Updated: Guinan RobertAndriolo Guinan ‎2020-06-22 06:39 PM

Labels:
  • EcoStruxure Building Operation
2303 Views

Continuum Analyzer Description

Issue This is the description of what the Continuum Analyzer does that is also available on the service release CD. Product Line Andover Continuum Environment Continuum Analyzer Windows 7 Windows 2003 Windows Server 2008 Cause The Continuum Analyzer description and what it does is in the service release CD. Resolution The Continuum Analyzer is designed to provide installers and troubleshooters with a point of reference for discovering problem areas within their installations. The software is proactive in that it enables you to 'clean' orphaned and mismatched objects from the database, thereby recovering from a minimal amount of database corruption. Continuum Analyzer also performs a system information check and provides full reporting on all aspects of the installation, as well as alerts regarding deficiencies. This article is provided to you as a guideline and an operational reference for use of the Continuum Analyzer. It is of the utmost importance that you review the current, Continuum Cyberstation Release Notes, before using this product. This document refers to specific changes made to the operation of the Cyberstation software in its new release. Installation Requirements Continuum Cyberstation software must also be installed on the given computer, and meet its hardware and software specifications as detailed in the, Continuum Getting Started Guide. Uninstall Previous Analyzer Versions If a previous revision of Continuum Analyzer is installed on the computer, it is important to remove it before installing a newer version. This is easily accomplished using the following procedure. Close all open applications before proceeding. Select Start, then Settings, and then Control Panel. Once inside the Control Panel, select the Add/Remove Software icon and select, Continuum Analyzer. When prompted, select Yes to remove all application components, and Remove All once uninstall begins. Close the Add/Remove applet and reboot your system. You may now proceed with installation of a newer version, below. Setup Procedure Close all open applications before proceeding. Setup will begin unpacking necessary files. Older versions of Windows workstation may require system file upgrades. An alert message will display asking you to confirm this operation. You may be required to reboot your computer. If this is the case, rerun setup after the computer restarts. The installation awareness screen prompts you for the location in which the files are installed. We recommend allowing the default installation directory. (C:\Program Files\Continuum\ContinuumUtilities\Continuum_Analyzer) When you are satisfied with the location, click on the large installation icon towards the left of the dialogue box. Figure One, below, details this screen. When prompted for creation of the program group in which the Analyzer will reside, select the default, or choose an existing program group for these icons. Setup will copy the necessary files into the installation directory on the hard drive. When finished, you are prompted that setup is complete and need to click, OK to verify. Setup is complete. Operation Modes Continuum Cyberstation software allows the user to define the type of database used to house the system information. Typical system configurations rely on the implementation of Microsoft SQL Server. LAN Mode This operating mode provides the user with all available information about the system installation, including SQL parameters used on the database server. This additional information can help reconcile issues that exist within the configuration of the SQL server. Stand Alone This mode diagnoses problems and lends the equivalent information presented through SQL implementation. Password Confirmation Continuum Analyzer requires the user to enter a password before launching the GUI. The password used should match the password of the SQL account used by Continuum. If all installation defaults were followed, the password is, pyramid97. Navigating the Interface The Analyzer uses an intuitive interface to easily collect and return data from Continuum installations. The interface is broken into 5 parts; a function toolbar, system toolbar, status prompt, report explorer, and the report window. Appendix B contains a screen shot of the analyzer display. Several toolbars located throughout the graphical interface permit point and click operation of the software. Function Toolbar This toolbar is located to the upper-left hand side of the Analyzer interface. Each toolbar feature is explained below. Button descriptions will also appear When the mouse is held idle over the selected feature. Save Reports to File Activating this button saves the Main and Suspect generated report to a *.csv file at the location specified by the user. The Save dialogue box prompts the user for the report destination. This file is required for proper technical support from Andover Controls Corp. Word Wrap This button wraps each line of output data to fit within the parameters of the display window. Run Begins data collection on the system. Clean The clean button removes references to suspect objects found during the initial database screening. After the items are removed from the database, the analyzer is automatically rerun to ensure that no remaining corruption exists. System Toolbar The System Toolbar features shortcuts to many of the same features as the Function Toolbar. This feature group also contains a button to close the program and a display window that monitors the integrity of the database and indicates corruption when found. Status Prompt The analyzer status prompt displays the progress of a current session. During an active session, the status indicator bar will fill to indicate that the analyzer has completed its review of the system. It may take Analyzer several minutes to complete its system scan. The status bar is located in the center of the system toolbar. Please refer to figure four for a detail of the system toolbar and status prompt. Log Selection Windows Analyzer allows a technician to specify log collection dates independently for both the Error and Activity logs using calendar menus as detailed below. This feature is helpful in reducing the amount of time necessary for the completion of an Analyzer scan, and identifying the point at which problems first occurred. The user may choose not to report on log collection by selecting one day ahead of the present date. Report Explorer Navigation The report explorer allows navigation through each report feature in a manner akin to the windows explorer file manager found in Windows. Navigate by double clicking on the desired report folder and selecting the appropriate report from the file list. Figure Seven details the report explorer below. The root of the Analyzer’s report explorer indicates to the user the mode in which the analyzer is running (LAN Mode or Stand Alone.) Each folder displayed below the root contains a report(s) on the system. Continuum Logs These log reports display two kinds of activity. The first report, Continuum Activity, displays all system user actions on the system during the period specified in the calendar selection window. The second report, Continuum Errors, shows the continuum error log during the dates specified within the parameters of the calendar selection window. Cyberstations This report area displays each workstation’s properties as detailed by the device table, and all Plain English programs that are installed at each workstation. Database Integrity This report allows a technician the ability to quickly identify an area of data corruption within the various link tables of the Continuum database. Each of the following reports specifies the type of link verified and a numeric display of how many broken links appear within the system. Typically, broken links detected by Continuum Analyzer can be cleaned from the system, using the clean feature. The clean feature removes all references to the orphaned item. Distributions Pending and failed distributions are monitored from within this report area. Failed distributions detail the name of the object and its status. The Pending distributions monitor the type, content, and numeric statistic of distributions waiting to complete. Field Devices Field device reports detect the variable parameters for different classes of objects configured in the field. This gives the technician a holistic reference point for determining any conflicting parameters within the system. Please refer below for information regarding the content of each report. Report Name Description CommPorts Infinity Controller communication port configurations InfinityControllers CX controller parameters InfinityInfinetControllers Defined parameters for infinet devices InfinityPrograms Details programs that reside on the CX controllers IOU Modules Parameters for each IOU configured within the system Networks Network Object parameters Each field device report displays values as an enumeration from within the database. Troubleshooting with the Analyzer requires that a technician be able to correlate each reported value of an attribute to the software value that Continuum displays within the object editor. Please refer to Appendix A for a definition and value range for variables discussed in the reports. General Continuum These detail all Continuum installation parameters, providing the technician with the ability to troubleshoot any problems that might occur at the software installation level. Aspects covered in this report segment include ODBC client connector details, connection status, domain user account information, and installation path. Workstation Workstation reports provide system information on the workstation hardware and operating system configuration. These reports help clarify any Continuum software compliance issues. SQL Server SQL Configuration information is provided through two reports, Database Configuration and Server Configuration. These values are used to trace possible problems back to a server configuration variable. Summary Report The summary report issues system details that provide a quick overview of the Continuum configuration in use at a particular facility. One set of data in particular is worth discussion, as the values here can lead to problems with the workstation performance of the system. The summary includes a section labeled Windows Registry Check. If the software installation was performed correctly, registry keys will be entered in the Local Machine hive of the registry. It is possible under abnormal installation circumstances that these registry entries are placed under the Current User hive. The Analyzer retrieves these registry values and displays them as follows in figure eight. If the machine is properly configured, the values will only display once, to the right side of the definition text. This indicates their presence in the appropriate location. If the values are located on the left-hand side of the definition text, the installation did not put the appropriate values in the correct location. Suspect Objects The suspect object report details three categories of data corruption detected within the database. If data corruption is discovered, the system toolbar and the report explorer will indicate such. The first category, Suspect Objects Correctable, contains any corrupt data that the Analyzer can repair using the clean command. Suspect Objects Manual Fix details configuration issues which require manually editing the erroneous variable. The final category, Suspect Objects Uncorrectable requires the assistance of Andover Controls TSD staff to remedy the problems. Please be aware that support for these issues requires that ACC TSD staff have a copy of the Analyzer report from the system in question. Figure nine details the report explorer icon displayed when corruption is detected. It is recommended that all suspect objects are saved as a file to aid in recreating the broken link objects. The Clean button is used after the Save Suspect Objects to File button to remove the broken objects from the database. Analyzer Report This report details all areas of data collection and is saved in a *.csv format. You may save a report in one of the following ways. Saving your Analyzer Reports The Continuum Analyzer generates two reports that can be saved for review. Both reports can be saved simultaneously, or individually using the reports menu option at the top of the Analyzer window. Suspect Objects Report The suspect object report is optionally generated when data corruption is discovered. If you do not see the visual indicators that suspect objects are present in the system, then there is no report to generate. However, if corruption is present, the report must be saved. All Cyberstation Workstations Invoke the analyzer by selecting the Continuum Analyzer icon from the Start Menu. You are prompted for a password. This password is the same as the password used to access your database from the ODBC connector. Figure Ten displays the password dialog box. If Continuum was installed with the default options, the database login password is Pyramid97. You may change the start date for log collection through the calendar menu, if necessary. Select, “Run” to begin analysis. The program will run for several seconds, an active display in the system toolbar details its progress. Save the report generated by each machine. Repair Data Corruption IMPORTANT! Note that this is option is NOT always available! If the Continuum Analyzer reports that data corruption was found, a stop sign icon appears in the report explorer and a Database Integrity Failed message appears at the top of the system toolbar. Select the option button labeled, Save Suspect Objects to File. Upon completion, select the Clean option. You’ll notice that after this button is selected, the database is cleaned and the Analyzer is run a second time, to ensure there is no remaining corruption within the database. Submit Analyzer Report The Continuum Analyzer Reports should be sent to our technical support department before upgrading if uncorrectable errors were found. Schneider Electric has a technical support address designed for this purpose. The email should include the following information. Subject: / Body: Dealership name Site Name File attachments: Analyzer Reports (each workstation) File attachments: Suspect Object Reports (each workstation) This email should be sent to Product Support All workstation analyzer reports and suspect object reports should be attached to a single email. Run Analyzer before Upgrade The Analyzer must be run again prior to the upgrade installation to verify that database integrity is stable. Using the Primary Access Server, run the analyzer, save the generated reports, and clean any suspect objects if necessary. Uninstall Continuum Make a note of the workstation and database settings within the Database Initialization Program. Uninstall earlier versions of Continuum from the workstations through the Add/Remove Programs icon located in the Control Panel. Select Continuum from the menu of programs and follow the automated procedure. You must reboot after un-installing. Install Continuum Refer to the Continuum Cyberstation Getting Started Guide for installation instructions. The first workstation upgraded should use the database initialization program to UPDATE an existing database. Ensure that the server name and authentication information is entered correctly. Verify that the workstation settings are IDENTICAL to those used in the previous installation of Continuum Cyberstation. Rerun Continuum Analyzer Rerun the Continuum Analyzer to verify that data within the tables is stable, and that all workstation settings are properly configured. If database corruption is present again, we recommend contacting our Technical Support Department for further information. Appendix A Field Translation Guide The Continuum Analyzer report references the exact table and column names used within the Continuum database. This appended reference should be used when trying to correlate settings and values from the analyzer report against values within the Cyberstation software. Please direct any further inquires to our Technical Support Department. Field Name Description Typical Values Autostart autostart on/off True/False Baud Enumerated value starting with 0 for 300. Each rate of speed has its own enumerated value 0=300, 1=1200, 2=2400, 3=4800, 4=9600 and 5=19.2 Command Whether a program can execute from command line on/off DefaultBaud When a Commport is created it is assigned the default baud of 9600 which is equal to 4 0=300, 1=1200, 2=2400, 3=4800, 4=9600 and 5=19.2 DefaultMode This is the mode the CommPort is configured to use. i.e., Infinet, printer 0=Printer, 2=Command, 3=Infinet, 5=Autoset, 6=Tanknet,11=Xdriver Description Text string entered into the object description field user defined DialPrefix Standard Commport initialization settings ATDT DialSuffix Standard Commport initialization settings |013 DirectConnect User selectable checkbox definition True or False. True if checkbox is selected Filesize Size of the program file in bytes 18 FlowControl UART data stream control 0=NoFlowControl, 1=XonXoff, 2=CtsRts, 3=XonXoffCtsRts HangUpCmd Standard Commport termination request @@@+++@@@ATH0|013 InfinetID Unique Identifier assigned to infinet controllers   IOU Number reference ID attached to the current module 1-32 Location Controller to which an object is attached User Defined MaxResponse Time Maximum amount of time to wait for a response in seconds Default 5 Sec ModelName Value obtained from hardware hardware/software type and version ModemInit Modem initialization string AT&F|013@@@@@@@@@@@ATEQ1&C1&D3S1S0=1W3\J\Q3%C1&W|013 Module ID Unique module identifier; hardware encoded in each module Not user Definable NetworkID Workstation's Energy Net identification number 1-190. 1-64 are recognized by the CXs and NetController. Ids above 64 are recognized by Workstations only. NetworkUTCOffset GMT offset of the network objects User Defined in minutes Owner Name of attached controller object User Defined Parity Standard Commport entries 0 PortNum Enumerated value of commport number to which a device is attached 0=1, 1=2, 2-3, 3=4 PrimaryAccessLogger Workstation computer designated as the primary access server 0=Not Primary, 1=Primary ProbeTime Probe Frequency time between TTL pings Default 60 Sec Program ID Internal Firmware reference ID 4th digit from the left represents IOU firmware revision SecondaryAccessLogger Workstation computer designated as the secondary access server 0=Not Secondary, 1 = Secondary SendToACX Whether or not the object must be sent to the corresponding ACX controller 0/1 SendToCX Whether or not the object must be sent to the corresponding controller 0/1 SerialNum Serial number of the network controller object 527853 Shareflag Whether program is able to run on any workstation on/off State Determines whether an object is active within the system or not TRUE StopBits Commport initialization setting 0 SynchDB Whether or not the object must be synchronized with the database 0/1 TerminalType Determines Commport emulation 0=VT100, 1=VT220, 2=Wyse TimeOutValue No user definition 0 TrackCxd Changed through checkbox selection True or False. True if checkbox is selected UiName Object name in database User Defined UTCOffset Number of minutes offset from GMT User Defined in minutes VersionNum Firmware revision number Ex. 1.53x, 1.2x, 2.1x, 4.5x XDriverFile Location of and name of any Xdriver assigned to the port User Defined
View full article
Picard Product_Support
‎2018-09-11 06:31 AM

Labels:
  • Andover Continuum
3406 Views

No longer possible to drag the application into the "Include types" box while doing a search

Issue Unable to drag and drop the Application folder into the include types box while performing a search of application files.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation v3.0.x  Building Operation Workstation v3.1.x  Cause Searchable interface not implemented on the Application folder (nor on other devices like b3). This is a known issue in v3.0.x and v3.1.x Resolution Rather than using the left mouse button to drag the application folder, right-click the application folder to drag and drop into the include types box. This is to be fixed in 3.2.1.x.
View full article
Commander JonGreen Commander
‎2020-06-04 11:33 AM

Last Updated: JohnBoehmer Schneider Alumni (Retired) ‎2020-06-04 11:37 AM

Labels:
  • EcoStruxure Building Operation
786 Views
  • « Previous
    • 1
    • …
    • 48
    • 49
    • 50
    • …
    • 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