Notifications

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

Building Automation Knowledge Base

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

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Various issues have been observed regarding the use of the I/A Series R2 WorkPlace Pro or I/A Series G3 Graphics access. The following is a partial list of known issues caused by the Ethernet firewall built into the Trend Micro Internet Security Suite software: When attempting to install an R2 UNC license using the Admin Tool, the error "Unable to install license" is displayed. When attempting to connect to a UNC from the WorkPlace Pro tree, a "Cannot connect" error occurs. When attempting to access G3 graphics using the web browser, the user is unable to log into the station serving the graphics. When attempting to access R2 graphics using the web browser, the user is unable to display the graphics pages. When attempting to paste a .gif file to a UNC's remote library, WorkPlace Pro stops responding and must be closed with Windows Task Manager. When attempting to open a local station on the computer, using WorkPlace Pro, the Windows hourglass is displayed and the station never opens. This list will be updated as additional issues are encountered. Environment Computer running "Trend Micro Internet Security Suite" I/A Series R2 (Niagara) WorkPlace Pro software or attempting to use the computer to view I/A Series G3 (Niagara) graphics. Cause The I/A Series R2 software requires bi-directional communications over Ethernet port 80 unless the software has been user-configured to use a different Ethernet port. The Trend Micro Internet Security Software Suite has a built-in firewall that blocks incoming access to Ethernet port 80. The Trend Micro software does not allow this port to be unblocked because it considers web access to a "workstation class" computer as a security risk. Resolution The best solution to this issue is to use a different Internet Security software package on the computer that does not block the use of Ethernet port 80. One approach is to use the "Server" version of Trend Micro Internet Security instead of the "Workstation" version. Since port 80 is typically used on server systems as the IIS (Internet Information Services) access port, the Server version of the software does not block that port. The alternate solution is to configure the I/A Series R2/G3 (Niagara) software to use a different Ethernet port for HTTP communications and Web services. This change would need to be made in the R2 or G3 software installed on the computer as well as in every UNC or ENC being accessed from this computer. See New installation of the I/A Series (Niagara) R2 WorkPlace Pro software cannot connect to existing UNC for more information.

Issue Can the Text Font size be changed on Listviews, Reports, EventView, Active Alarm Window Product Line Andover Continuum Environment Continuum Cyberstation Cause Trying to change the font size Resolution Listview - Most Font attributes/styles can be changed but the Font size adjustment is greyed out EventView - Most Font attributes/styles can be changed but the Font size adjustment is greyed out ActiveAlarmWindow - Most Font attributes/styles can be changed but the Font size adjustment is greyed out Report - Text Font is not adjustable Groups - Some adjustment of Font are possible For EpiBuilder see Adding fonts to EpiBuilder or EpiDesigner

Issue "invalid data on _schedule address_" error when downloading application Environment Xenta Programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause This error can occur when the time schedule data has become corrupted in the Xenta programmable controller. Resolution To fix the controller either: Clear the MTA file by using the clear application process (see Xenta Controller Will Not Download / How to Clear the Xenta Application for more information) Download the MOT file and empty the application memory (see Instructions on how to download an .MOT file into a Xenta Programmable controller for more information).

Issue System alarm message, Physical device not defined/configured, in the alarm window. Product Line TAC Vista Environment TAC Vista (all versions) TAC Xenta programmable controllers Cause This message is displayed when there is a TAC Xenta 401/30x/28x that is attached to the physical network, but the name is not in the TAC Vista database. It is there to alert that there are unconfigured controllers on the network. Resolution Download to the controller from TAC Vista Remove the controller if it is not needed. For an alternative cause and resolution for the message, see Physical device not defined/configured.

Issue "Controller doesn't know Infinet Id" error when attempting to share data from a BCX9640 to a b3 under a BACnet BCX 4000 Product Line Andover Continuum Environment BCX9640 b3 BCX4000 Cause A program that is attempting to map a point value from a BCX 9640 to b3 under a BCX 4000 receives a program error "Controller doesn't know Infinet Id." The infinity protocol does not get routed. Resolution The BCX4000 must be upgraded to a BCX4040 by requesting this from repair. Follow Share data between standard Continuum controllers and Continuum BACnet controllers to get the best performance.

Issue CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output, but the Xenta 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. If replacing the sensors would be too costly and time consuming, this is a viable option that will allow you to drop the voltage output on the CO2 sensor using 1000 ohm resistors. Product Line TAC Vista, EcoStruxure Building Operation Environment 102-AX Cause CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output but the 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. Resolution NOTE: It is recommended that the incorrect sensors be removed and replaced with new sensors that have the proper specifications to match the 102-AX capabilities. If the sensor replacement is not an option please follow the instructions below. Please see the image below: You will need (2) 1000 ohm (1k) resistors to complete this conversion. Wire one resistor directly to the output wire of the CO2 sensor Land that resistor to U3 on the 102-AX Jump a second resistor from U3 over to M on the 102-AX Land the other output wire from your CO2 sensor on M with the jumped resistor Also see Using a 4-20mA CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 4-20mA CO 2 sensor input on Universal Input 3.

Issue How many MSTP networks can you connect to an Automation Server (AS or AS-B)? Product Line EcoStruxure Building Operation Environment Version 1.3 and newer MSTP Network on an StruxureWare Building Operation Automation Server (AS or AS-B) BACnet MSTP Devices Cause Require 2 separate MSTP networks, either to use 2 different Baud rates or to speed up the network and split the devices across the 2 ports. Resolution You can create 2 separate MSTP networks under the BACnet interface of an AS-B or AS (version 1.3 or higher), one on Comm A the other Comm B. Each can run at different Baud rates if required. For the number of supported devices please reference, Maximum number using StruxureWare Building Operation (Scalability and Capacity). Please be aware that the listed maximum is for the Automation Server allowing you to distribute between the two comm ports.

Issue HID PIN Pad reader for I/NET Part NumberHID PIN Pad reader for I/NET Part Number Product Line TAC INET Environment I/NET Access Control Cause HID PIN Pad reader for I/NET and which part number to use? Resolution iPortal shows several PIN pad readers from HID (HID-6136CKD000214 HID-6136CKD000009) but only one works with I/NET. Here is a pdf document which helps to explain which part number works with I/NET. The 09 means the 8 bit blast which is required for compatibility. Want to use Pin Pad only without using the proxcard? The RK40 will do Prox only or Prox + Pin but not Pin only. See Essex Pin Pad Reader programming for Pin Only or for higher security Pin Only see Code-Guard Scramble Pin Pad Reader Programming.

Issue Downgrading an UNC to an earlier Niagara build Product Line TAC IA Series Environment I/A Series R2 Universal Network Controller (UNC) Cause Station is unable to run in an UNC with newer version of Niagara R2 because a 3rd party module does not have an updated JAR file Resolution The procedure to downgrade an UNC would be to use the version of WorkPlace Pro that you want the UNC to be and commission the UNC as per what you would do for a new UNC or to upgrade an UNC. The modules installed in the station should also match the Niagara version of the UNC. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330?. Refer to Procedure 4 on pages 9 and 10 of the UNC-520 Installation Instructions for details on installing the software to an UNC-520. It is important to note that newer UNCs with the newer boot flash chip requires I/A Series R2 version r2.301.527 or newer. Installing the UNC with newer boot flash chip with an I/A Series R2 version lower than r2.301.527 will make the UNC inoperable. Refer to Cannot get my I/A Series (Niagara) R2 UNC to boot after downgrading the system software to a version earlier than release 529 for details.

Issue Adding an object to an already opened Trend chart does not work correctly. Product Line EcoStruxure Building Operation Environment Webstation Open chart Adding objects Cause An AS or ES is logged into using a Webstation, and an existing Trend chart is opened. An object is then selected in the System Tree, and then using the right-hand menu, the "Open Chart" and "Add to already open chart" is selected. Values are not added to the already opened chart. This issue is caused by a Java 7 update 51 a specific fix is not available. Resolution Possible workarounds; Use an earlier version of Java. Change Java security level to Medium. Add site to the exception list For further details on "adding to the exception list", refer to Webstation graphics not working after Java updated to Java 7 update 51.

Issue Sigma Release Notes. Sigma Upgrade Information. BAS Upgrade Information. Product Line Satchwell Sigma Environment Sigma, BAS Cause Where are the release notes available from? FAQ's regarding the upgrade of BAS to Sigma. FAQ's regarding the upgrade of previous releases of Sigma to the later releases of Sigma. Resolution Sigma release notes are available from The Schneider Electric Exchange Extranet TThe Sigma 4.08 release note can be downloaded here. For upgrade information, see How to upgrade a BAS system to Sigma.

Issue DVR incorporated with I/NET Seven and Pelco Integral or Digital Sentry Product Line Pelco, TAC INET Environment I/Net Seven Pelco Integral or Digital Sentry DVR CCTV Cause Send back a Integral DVR and it comes back as a Digital Sentry or confusion revisions of I/NET Seven and Pelco Integral of Digital Sentry Resolution This chart to clarifies which versions of I/NET Seven are compatible with which Pelco DVRs: For the latest products (after 2.31 revision) please visit Software and Firmware compatibility matrix for older versions of the traditional product lines which has the most recent Pelco compatibility.

Issue A Macro comes installed in the default directories with Menta. This macro will create a PWM signal that can be used for a variety of purposes in Menta. It will not, however, drive most industry-standard PWM hardwired actuators. For information on this, see Pulse Width Modulated (PWM) outputs in Menta. Product Line TAC Vista Environment Menta PWM actuator Cause Creating an a pulse width modulated output. Resolution Go to Program Files > TAC Menta > Library > Macro Block Library > Miscellaneous > Function > PWM.aut and PWM.doc These two files will give you a PWM function for Menta and an explanation. In simulation mode it will appear that the PWM increments at very crude levels but when the application is downloaded the processor actually runs at less than 1 second increments. Download this application to a controller and connect up a transducer and vary the control signal to be comfortable with the performance. Use a PVR block to generate a manually controlled signal.

Issue What if an NPR 2000 goes away and never comes back even after cycling power to it? Product Line TAC INET Environment I/NET site Cause Cold starting an NPR 2000 is a common troubleshooting technique to clear up a number of communication problems that may arise. Resolution If said NPR stops communicating and doesn't come back no matter what, you should cold start it and do a software restore. (See that procedure in How to cold start an NPR 2000.)

Issue What do the HVAC, SEC, and INT options on the Continuum Security Key provide access to? Product Line Andover Continuum Environment Continuum Security Key Continuum Cyberstation Cause Unsure as to what restrictions these various Security Key Options place on the activity that can be performed and what can be viewed within Continuum. Resolution HVAC - Provides access to HVAC specific objects such as viewing BACnet controllers, creating BACnet objects and polling for new BACnet Devices. SEC - Provides access to viewing and creating Security specific objects such as Door, Area, and Personnel objects. INT - Provides access to all of the above. This key will be able to view/create both HVAC and Security related objects. Any Workstation with a SEC key will not be able to view any BACnet Devices or objects in the database and any with an HVAC key will not be able to view Security related objects in the database. For more information see Different options on the CyberStation security key.

Issue How is the time synchronized between the Automation Server and Xenta Programmable Controllers? If the time synchronization is offline, what can be done to correct this? Product Line EcoStruxure Building Operation Environment Automation Server Building Operation Workstation Cause Time Synchronization occurs between the Automation Server and the Xenta Programmable controllers during two events: When the Xenta programmable controller is commissioned. Periodically the time is synchronized (default 10 minutes, but configurable). For the time synchronization to work properly it is critical to ensure that the time zone of the automation server is correct and the date/time of the automation server is correct. Resolution Walk through these steps to troubleshoot the synchronization of the Automation Server and Xenta controllers. Check that all Xenta devices are at software revision 3.74 or higher Check the local time of the Xenta programmable controller by accessing the properties of the programmable controller and using the "Xenta" property tab group. The local time is listed there. Check the time zone of the automation server. By default the "Factory time zone" needs to be changed for proper operation. Check the server time of the Automation Server in the Basic property tab of the Automation Server. Check Time Synchronization Interval setting of the LonWorks Network object under the advanced tab in the Xenta General section. Default is 10 minutes. Either wait for the interval to elapse or manually commission the controller to synchronize the time and check the local time of the controller to ensure it completed properly. Note: Keep in mind that the time displayed time in Workstation reflects the time zone of the local machine. If you are logging into an Automation Server in a different time zone, the alarms and events will be displayed in your local time, not the time of the Automation Server's time zone. For more information on Time settings and Synchronization see Time Synchronization of the ES and AS.

Issue Personnel distribution shows error 5310 Product Line Andover Continuum Environment Cyberstation Cause Error 5310 (0x14BE hex) indicates a duplicate card number. Resolution Take a LAN capture of the distribution using Using WireShark to analyse communications on an Ethernet network and send it to PSS for analysis, a PSS engineer will decode the packet to extract the card number and card type that is being rejected as duplicate. Armed with the card number and type find the offending record in the DB and eliminate the duplication.

Issue Configuring the Xenta 102-AX to accept a 4-20mA CO₂ sensor input on Universal Input 3. A negative value is required on the CO₂ offset value, but it is not possible to enter a negative value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX 4-20mA output CO₂ sensor Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input. The best option is to always buy a CO₂ sensor that is compatible. However, if 4-20mA CO₂ sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20mA CO₂ sensor with a 0-2000ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to CO₂ Sensor Wire a 250Ω resistor across U3 and M. This converts the 4-20mA signal to 1-5V. In Vista Workstation, navigate to the 102-AX > UnivIn3_Sense. Open SCPToffsetCO2. This value needs to be -500, but negative values cannot be entered. To get around this: Change Value to 0 Change Scaling > Offset to 500. This alters the display of the offset value. Click OK. Open SCPToffsetCO2 a second time. The value is still 0, but it is being displayed as 500, due to the scaling offset. Change the value to 0 (because of the offset, 0 represents -500). Click OK Open SCPTgain. Set multiplier to 2444 Set divisor to 1000 Click OK. This value comes from 2000 (range of sensor) + 500 (offset) / 1023 Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid). Also see Using a 0-10 volt CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 0-10 volt CO₂ sensor input on Universal Input 3.

Issue Edit > Host Computer > Software Restore results in pop-up error "No entries in data base" Product Line TAC INET Environment I/NET Seven host Cause The network configuration does not have any entries saved in the database. Resolution Go to Edit > Host Computer > Network Configuration In the Link Summary window, find the correct Link. If the Cnf column has a plus sign (+) in it, then this link is not saved. If the correct link is not shown, reference Error: "No Entries in Database" for more information. Highlight the correct link and press "Save" With the correct link highlighted, click "Penetrate" Any controller with a + in the Cnf column has not been saved. Click "Save All" Hit "Close" on the Station Summary and "Close" on the Link Summary. There are now entries in your database. The software restores should now show the correct options. For instructions on performing a software restore, see How to upgrade bin and SAV files in I/NET controllers

Issue Getting error "Unable to find an object in the database.Root\FolderName\OldAreaName" when creating new Personnel, in Personnel Manager. Following a change to Area names, the Personnel Profiles no longer contain these changed Areas. Product Line Andover Continuum Environment Continuum 1.81 and above Cause Do not rename Areas without removing/replacing them from the Personnel Profile. Resolution Always remove Areas from Personnel Profiles before changing the Area name, then replace Area If you simply rename the Area without removing that Area from the Personnel Profile, then the Personnel Profile will either get corrupted or the changed Areas will get removed from the Personnel Profile. If the Personnel Profile is corrupted then it needs deleting. Delete from Personnel Manager, if the corruption is such that it cannot be deleted from Personnel Manager, see Cannot delete personnel profiles Once the Personnel Profile deleted, recreate as required.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

"Trend Micro" Internet Security Suite causes communications issues with I/A Series R2/G3 (Niagara) software

Can the Text Font size be changed on Listviews, Reports, EventView, Active Alarm Window, Groups

"invalid data on _schedule address_" error when downloading application

System alarm message, Physical device not defined/configured

"Controller doesn't know Infinet Id" error when attempting to share data from a BCX9640 to a b3 under a BACnet BCX 4000

Using a 0-10 volt CO2 sensor with a Xenta 102-AX

Can 2 MSTP Networks be connected to the same Automation Server?

HID PIN Pad reader for I/NET Part Number

Downgrading an UNC to an earlier Niagara build

Adding an object to an already opened Trend chart does not work correctly in Webstation

Sigma release notes and BAS upgrade information

DVR incorporated with I/NET Seven and Pelco Integral or Digital Sentry

Create an internal Pulse Width Modulated (PWM) signal in Menta

NPR 2000 offline despite power cycle

What the HVAC, SEC, and INT options on the Continuum Security Key provide access to

Time Synchronization of Xenta programmable controllers under Automation Server

Error 5310 on Cyberstation personnel distribution

Using a 4-20mA CO2 sensor with a Xenta 102-AX

"No entries in data base" when attempting software restore

"Unable to find an object in the database.Root\FolderName\OldAreaName" when creating new Personnel Profile

Building Automation Knowledge Base

Related Forums

This is a heading