Building Automation Knowledge Base

Issue When browsing the IP network using the WorkPlace Commissioning Tool, third party devices are displayed in addition to the I/A Series BACnet devices but no information is known about those devices. Product Line TAC I/A Series Environment WorkPlaceTech Commissioning Tool 3rd party BACnet IP & MS/TP devices Cause 3rd party BACnet devices are sometimes connected to the IP network without the knowledge of the engineer  programming the I/A Series system. Resolution When performing a global browse of the IP network, unknown devices are sometimes displayed in the WorkPlaceTech Commissioning Tool device list display.  Since all data columns are not necessarily displayed, some of the device information may not be able to be directly determined. Right-click in the column headers and a menu of available data columns will be displayed. The following columns may be displayed at a minimum to allow identification of the devices on the network as well as the BACnet routing path to those devices:     Instance     Vendor     Model     Router     Network     Address   If the device is a BACnet IP device, the "Address" will be displayed as an IP Address and Port.  For example the address of a BACnet IP device communicating via port 47821 at IP 10.159.34.238 Address   =  10.159.34.238 : 47821   If the device is a BACnet MS/TP device under a BACnet IP device, the address is the MAC address of the device on the MSTP bus and the Router is the address of the BACnet IP router to that device in Hexadecimal numbers.  For example, for MSTP device #4 under BACnet IP Router address, 10.159.34.238 : 47821 10 = 0A, 159 = 9F, 34 = 22, 236 = EC and 47821 = BA CD  Address   =   4 Router      =   0A-9F-22-EC-BA-CD   If the device provides vendor and model information, that information will be displayed in the appropriate columns.

Issue How to display custom text and properties of an alarm in the email notification. Product Line EcoStruxure Building Operation Environment Email Notification Substitution Codes Cause There may be certain situations where a specific property of the monitored value needs to listed in the alarm email that is sent out. For example when an alarm is triggered, the value at the time the alarm state changed my need to be documented in the notification email. These are called substitution codes. Resolution The properties of the Email Notification can be set to customize the message that is sent out when an alarm changes states. As seen in the properties window of the Email Notification above, the "Subject" and "Text" can be changed to say whatever is desired. There are special codes that can also be entered into these fields to pull actual properties from the value that went into alarm. Below is a table that lists all of the Codes for the different value properties. This same information can also be found on the EcoStruxure Building Operation WebHelp. Substitution Codes for Notifications Code Description @(AcknowledgedBy) Writes the user that acknowledged the alarm. @(AcknowledgeTime) Writes the time the alarm was acknowledged. @(AckRequired) Writes an indicator if the BACnet alarm requires acknowledgement. @(AlarmState) Writes the present state of the alarm. @(AlarmText) Writes the alarm messages that is added to the alarm. @(AssignedID) Writes the unique ID of the user the alarm is assigned to. @(​AssignedState) Writes the current assigned state the alarm is in. The possible values are Unassigned, Assigned, and Accepted. @(​AssignedTo) Writes the name of the user or group that the alarm is assigned to. @(​AssignedToDomain) Writes the domain of the user or group that the alarm is assigned to. @(BACnetEventType) Writes the BACnet event type for this alarm. @(BACnetNotificationType) Writes whether the BACnet notification was an alarm or event. @(BasicEvaluationState) Writes if the alarm is active or not. @(Category) Writes the category name of the alarm. @(CommandValue) Writes the value which was commanded for a BACnet command failure alarm. @(ConfirmedNotification) Writes an indication whether a BACnet notification was issued as a confirmed or unconfirmed BACnet message. @(Count) Writes the number of times the alarm has toggled between the alarm and reset states. @(Deadband) Writes the value of the deadband used for limit checking for BACnet out of range alarms. @(DeviceName) Writes the name of the I/NET device that generated the event. @(​DisabledCause) Writes the cause of the alarm being disabled. An alarm can be disabled by User, Shunt variable, and System. If the alarm isn't configured correctly it can be disabled by System. @(ErrorLimit) Writes the difference limit that was exceeded for BACnet floating limit alarms. @(EvaluationState) Writes the present evaluation state of the alarm. For example, Upper limit alarm is displayed when the monitored value reaches the upper alarm limit. @(EventFromState) Writes the event state of the object prior to the occurrence of the alarm condition for BACnet alarms. @(CWSid) Writes the EcoStruxure Web Service identification of the alarm on the external system. @(CWSSourceId) Writes the EcoStruxure Web Service identification of the external object that generated the alarm. @(ExceededLimit) Writes the value of the limit that was exceeded for BACnet out of range alarms. @(ExceedingValue) Writes the value that exceeded a limit for BACnet out of range alarms. @(FeedbackValue) Writes the value that differs from the commanded value for a BACnet command failure alarm. @(FirstName) Writes the first name of the individual whose key/card was used at the I/NET door point. @(Hidden) Writes the visible status of an object. False is displayed when the object is shown. @(IndivNdx) Writes the individual number of the individual whose key/card was used at the I/NET door point. @(LastName) Writes the last name of the individual whose key/card was used at the I/NET door point. @(Logging) Writes whether the alarm should be logged or not. @(MessageText) Writes the text of an I/NET action or dispatch message, if there is one. @(MonitoredObject->DESCR) Writes the description property of the monitored object. @(MonitoredObject->NAME) Writes the name property of the monitored object. @(MonitoredObject->NOTE1) Writes the note 1 property of the monitored object. @(MonitoredObject->NOTE2) Writes the note 2 property of the monitored object. @(MonitoredObject->LabelText) Writes the label text of the monitored object. This requires that a MonitoredVariable is configured. @(MonitoredValue) Writes the value depending on the alarm states selected under 'Notify on transition to'. @(​MonitoredVariable) Writes the path of the monitored variable. @(NewMode) Writes the new mode of the monitored object for a BACnet change of value alarm. @(NewState) Writes the new state of the monitored object for a BACnet change of state or change of life safety alarm. @(NewValue) Writes the new value of the monitored property for a BACnet change of value alarm. @(NotificationClass) Writes the distribution information of an alarm notification within a BACnet system. @(OperationExpected) Writes the next operation requested by the monitored object for a BACnet change of life safety alarm. @(OriginalAlarmText) Writes the alarm text from the matched alarm. This substitution code is only available for Alarm Decorators. @(PossibleOperatorActions) Writes the possible actions one can perform on the record, given permissions. @(PreviousAlarmState) Writes the previous alarm state. @(Priority) Writes the current priority level of the alarm state. @(ProcessId) Writes the process identifier configured by the notification for a BACnet alarm. @(ReferencedBitString) Writes the new value of the monitored bitstring property for a BACnet change of bitstring alarm. @ (Report) Writes the name of the report connected to the notification. @(SEQNO) Writes the sequence number of the record. @(SetpointValue) Writes the value of the setpoint when the alarm condition occurred for a BACnet floating limit alarm. @(​Source) Writes the path of the source object. @(SourceName) Writes the name of the source object that generated the alarm. @(SourceObject->DESCR) Writes the description property of the source object. @(SourceObject->NAME) Writes the name property of the source object. @(SourceObject->NOTE1) Writes the note 1 property of the monitored object. @(SourceObject->NOTE2) Writes the note 2 object of the monitored object. @(​SourceServer) Writes the path to the server where the source object is located. @(StatusFlags) Writes the status flag of the object. @(SystemAlarmId) Writes the alarm ID generated by the system. @(TenantNdx) Writes the tenant number of the individual whose key/card was used at the I/NET door point. @(TimeStamp) Writes the time and date when the event was generated. @(TriggeredTimestamp) Writes the time and date of the last state transfer from normal state to alarm state. @(TYPE) Writes the record type.

Issue Using BACnet IP to add a SmartStruxure Lite MPM to a StruxureWare Building Operation Enterprise Server or Automation Server Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Workstation Cause SmartStruxure Lite systems may desire an Enterprise Level Solution to bring multiple sites into one system. Resolution Configure the SmartStruxure Lite MPM for BACnet IP as shown in MPM BACnet Integration. Ensure that the BACnet Network ID is Unique to the system and does not match the Network ID in use by the Enterprise Server Save the BACnet Configuration Be sure to Right Click on the Root Object of the MPM and save the database. Open StruxureWare for Building Operation Workstation Right Click on the Server Object and add a BACnet Interface Ensure that the BACnet interface has a unique BACnet Network ID which does not match the Network ID used by the MPM Expand the BACnet Interface Click on the Server Object and select the Device Discovery Tab Select BACnet Devices NOTE: There have been instances of Skype causing interference with this process. Please completely close Skype if you are using it and unable to discover any devices. ALSO NOTE: There may be 2 instances of the MPM shown. If so, use the MPM that is part of the Enterprise Server BACnet Network Drag the MPM to the BACnet Interface/IP Network object in the Enterprise Server System Tree Right Click on the Device and Upload it If any devices are connected to the MPM such as a Zigbee Wireless State or Enocean switch, these will be discovered in the BACnet Network configured in the MPM Add these devices to the Enterprise Server by dragging and dropping them to the BACnet Interface/IP Network object Right Click and upload all devices.

Issue In a Niagara G3 station with a BACnet MSTP integration, the following error appears in the application director output: Transaction Timed out! invokeId 223 TransactionException in poll() for BacnetDevice {Kens_RM106}:pl=PollList [Kens_RM106 device:7219 3000:13] 196608025 {160} 10 PLEs) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) .... Hundreds & hundreds more Environment Niagara G3 Cause MSTP trunk / traffic issues Resolution See the discussion about an identical issue at Niagara-Central.com.  Here is a link:  https://community.niagara-central.com/ord?portal:/discussion/DiscussionThread/11258

Issue How to recover the AD v3 password if lost / forgotten? How is a factory reset done on an Advanced Display version 3 (AD v3)? Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V3 Cause If losing the kiosk password for AD v3, it is not possible to get a recovery password. If the kiosk password is lost for the AD v3 a factory reset must be done on the tablet to be able to get out from the kiosk mode. Resolution The following video will show the steps to perform a factory reset on an AD v3:

Issue Automation Server Classic support for hosting MPX or RPC Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Classic, AS-P, AS-B Building Operation SmartX MPX, MPC, MPV field controller Building Operation SmartX RPC field controller Cause The original Automation Server (Classic) can be set up to fully host (host server) and configure both MPX and RPC devices, but the Architectural Guidelines do not specify how many devices can be fully hosted. Resolution Full hosting of MPX, RPC is only supported and tested on AS-P, AS-B and Enterprise Server. This is confirmed in the MPX and RPC Specification Sheet. "MP-C/MP-V/RPC can either be used as a standalone BACnet/IP field controller or as part of an EcoStruxure BMS with a SmartX AS-P or AS-B server or an Enterprise Server as the parent server." MPX, RPC can be simply be BACnet hosted on an Automation Server Classic, but the use as parent or host server is not supported or tested.

Issue Functional block names are shorter in XIF file, LonMaker or NL220 than the names defined in SmartStruxure Environment Automation Server Externally Managed LonWorks Network Cause LonMark defines how a xif file must be structured and written. There are especially three rules that comes into play when creating the functional blocks from an Automation Server in the externally managed LonWorks network. In the LONMARK® Device Interface File Reference Guide it states that: "If the static interface contains functional blocks, the device selfdocumentation string must be formatted as described in The LONMARK Interoperability Guidelines." In the LONMARK® Application-Layer Interoperability Guidelines it states that: "Manufacturers are free to assign any functional profile number to new non-inheriting profiles, as long as they are in the range of 20000 to 25000, inclusive; and as long as the number is unique for the program ID template and scope of the resource file set containing the functional profile." In the same document it also states that: "The device self-documentation string is a string of up to 1024 bytes (subject to device memory limits)" and also "If the name is text, it must consist of ASCII printable characters, be of no more than 16 characters in length". Due to the above mentioned rules, any functional block defined in the Automation Server will always start with a functional profile number from 20001 and up and the name of the functional block (excluding the 5 digit profile number) will not be longer than 16 characters. If the name defined in SmartStruxure is longer than 16 characters, the characters from 17 and up will be deleted. If the complete length of the self documentation string is longer than 1024 bytes, the maximum character length will be lowered by one until the complete string fits within 1024 bytes. Resolution The only way to get around this is to either make fewer functional blocks on the Local Node in SmartStruxure, or to make their names shorter.

Issue Using 3.7.106 and want to display a PDF file on a Niagara G3 / AX graphic. It's been done in the past but with "Default Web Profile" "Applet Reload on Hyperlink" set to "False" the PDF does not display. Is there a way to do it without setting the "Applet Reload on Hyperlink" to "True"? Product Line TAC IA Series Environment Niagara G3 / AX revision 3.7.106 and higher Cause More secure changes made to G3 / AX Resolution Instead of creating a hyperlink button with hyperlink: file:^blahblah.pdf Use: http://137.19.60.55/ord?file:^blahblah.pdf This opened the PDF in the browser (it left the default web profile but the back button returned to it).

Issue When SmartStruxure and TAC Vista is installed on the same PC, the license system for one of the products doesn't work properly and you get no license. Product Line EcoStruxure Building Operation, TAC Vista Environment Flexera license system Cause SmartStruxure and TAC Vista uses the same license system vendor and also the same vendor daemon. That causes a conflict, and a special configuration is needed. Resolution To move a TAC Vista license to the EcoStruxure Building Operation(EBO) license server See video:       Or follow the steps below: Disable TAC Vista's license server and host the TAC Vista licenses in the SBO license server. Stop and disable the service "TACLicenseServer". This is done through "services" (Start-->run-->services.msc) on the PC. Make sure the correct license setup is made for TAC Vista. Refer to No license after reboot when TAC Vista Server (TACOS) runs as a service for further explanation. Create a folder for the TAC Vista licenses as a subfolder in the SBO license server installation folder. Give it the name "licenses" and place all TAC Vista customer licenses here. Do not place demo licenses in this folder. Open the SBO license server web page (http://localhost:8888) preferably with Chrome or FireFox Click on "Administration" Sign in using "admin" as user name. If you have logged in before, use the password you have defined. If not, enter "admin" as password and create a password as indicated in step 6a and 6b. If it is the first time you log in, enter a new password and click "Save". If it is the first time you log in, now click "OK". Click on "Vendor Daemon Configuration" Click on "Administer" Click the field "License File or Directory" and enter the folder name "licenses" on a new line. Scroll down and click "Save" Restart the SBO license service (Building Operation 1.6 License Server) Additional notes If your TAC Vista license is locked to a dongle, you need to replace the SBO vendor daemon file (taclic.exe) with the on from the license server hotfix produced for TAC Vista 5.1.9. Please contact Product Support Services for assistance and refer to this article.

Issue How can the true/false output from a Boolean object (i.e. Tstat) be changed to a numeric 0 or 100 in Niagara G3? Environment Niagara G3 Cause Represent a boolean on/off value with a numeric that can be used to drive other logic. Resolution Open the kitControl palette under the Util folder Use an object called NumericSwitch Link the output of the Boolean object into the InSwitch property of the NumericSwitch In the properties of the NumericSwitch object, set the "in true" value to 100 and "in false" value to 0 (or vice versa if reverse acting). The output of the NumericSwitch will be a numeric type.

Issue Error "Ensure that Vista Server is started" when the server is already running. Product Line TAC Vista Environment Vista Server Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). test Resolution These are some utilities created by Benjamin Roswall at Schneider Electric Denmark. They are not official releases nor are they supported by Schneider Electric. While they have been tested and used successfully, they should be used at your own risk.   DCOM Config 1.0.3.0.exe: Configure DCOM for TAC Vista Network If you want to run TAC Vista Web Applications on Windows Server 2003 Standard Edition, both Internet Information Services (IIS) and ASP.NET 2.0 must be installed. ASP.NET 2.0 must be installed and activated before you start installing TAC Webstation. Refer to Chapter 4 of the TAC Software Installation Manual for more information. If you've made it this far, then it's time to refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). Or just run this utility. Click the picture to download the utility.   Webstation installations will use Option 3. If Webstation doesn't come right up and start working after this, also download the next utility.   WEB.exe: Corrects common problems with Vista Webstation This utility will install and register the versions of ASP.NET required for running Webstation on the server PC. There are other articles on the command prompt commands to accomplish this, but this utility will take care of it for you. Click the picture to download the utility.   After this utility finishes running, restart the PC as instructed.

Issue Satchwell VEU 2-port Unit Control Valve is obsolete. Environment Satchwell VEU 2-port Unit Control Valve installations Cause Satchwell VEU 2-port Unit Control Valve requires replacement due to failure. Resolution Satchwell VEU 2-port Unit Control Valve may be replaced by Schneider Electric VZ219 series Unit Control Valve, although dimensional differences may apply. It should be noted that VZ219 series Unit Control Valves are available in both Flat Face and Compression fitting specifications. The latest issue of the Schneider Electric Valves and Actuators Catalogue should therefore be consulted in order to determine the availability of the particular size / kv / fitting combination required. It should also be noted that any Actuator installed on the Satchwell VEU 2-port Unit Control Valve will not be compatible with the replacement Schneider Electric VZ219 2-port Unit Control Valve and that a Schneider Electric MZ20 series Actuator of the appropriate operating voltage / signal type will also be required.

Issue Xenta Server reports it is in FAILSAFE mode without shorting out terminals 9 and 10. After connecting via HyperTerminal, restarting and trying to reset the IP address, the screen continues to scroll back to dsh/> Xenta Server has gone offline and can not connect directly to it using Ethernet. The Run light is flashing Green on first start up but then reverts to red and the LON light also flashes red. During boot up it pauses and reports an error (via HyperTerminal) in loading the RAM disk.  IP Address is set to 172.22.1.5 and can not change it.  Not able to load any firmware into the device – error received. "Error: Could not create remote directory." Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 527, 511, 555 Xenta Server 701, 721, 731 Cause Unknown corruption of the Xenta Server hard drive / flash drive, possibly due to electrical noise. Resolution To attempt to recover this device, try to format the device’s flash drive. To achieve this you can follow these steps using HyperTerminal or an equivalent application: (For further assistance with connecting to Xenta Servers and HyperTerminal refer to Connecting a serial cable to a Xenta 5/7/9xx controller).   Login and type the command FORMAT.  (May require device to be placed physically into the fail-safe mode by shorting terminals 9 and 10). The format command can take up to 3 minutes to complete but you should see the confirmation through HyperTerminal while this is occurring. If you have placed the device into Fail-safe mode, remove the link on terminal 9 & 10. Restart the device, by either cycling the power or typing the command RESTART through HyperTerminal. Set the IP address and IP settings (command SETIP). Install the latest firmware. You can download the latest firmware from The Exchange Extranet; ensure that you use the correct version since there various versions for the Xenta Servers. Run the firmware download to the device. During the download you may receive an error regarding "Failure to get the hardware version from the target device…", select OK Continue the installation The download will then occur, it will take some time and may appear that the software is not responding but this is normal. Be patient and if you don’t receive any errors then all should be ok. The device should now restart, after a 1-2 minute window the “RUN” LED should be a solid green. If after following these procedures, the device is still not responding as expected please send into Repairs via your normal repair process.

Issue Active alarms are appear stuck in the alarm viewer for objects that are no longer in alarm.   Alarm notifications will not clear from Active Alarm View. How can obsolete alarms be removed from the Active Alarm View Product Line Andover Continuum Environment CyberStation WebClient Cause When a Return to Normal (RtoN) notification is reported by a controller, if Cyberstation is unable to receive the notification due to a loss of communication, the status of the alarm notification will not be updated and the alarm will continue to be displayed as though it were active even though the point alarm state is now inactive. Resolution Method 1 Disable the object and change it's value so that a new alarm is induced. Refresh the object editor until it indicates that the alarm state is active. Enable the object so that it returns to a normal value. If necessary, acknowledge the alarm so that it can be removed from the alarm list. Method 2 Backup the Continuum Database. Edit the object to confirm that it is no longer in an active alarm state. From the Root/ListView folder, open the Alarms_AllActive Listview. Locate the alarm entry associated with the object. Right click on the line and select Delete. Restart Cyberstation to update the Active Alarm View from the alarm log.

Issue To assist locating data sheets if you do not have access to The Exchange or other Schneider Electric storage areas Product Line Satchwell MicroNet Environment MicroNet 50 series Controllers Micronet Touchscreens Micronet LCD SLink sensor Cause To assist customers that do not have access to our internet or partner websites. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MN 50 Series MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN350 Controllers MLi and data sheets for Satchwell MicroNet MN450 Controllers MLi and data sheets for Satchwell MicroNet MN550 Controllers MLi and data sheets for Satchwell MicroNet MN650 Controllers Download all of the above (file size 12.0 MB) Data sheets for MicroNet 100 series controllers ETC can be downloaded from MicroNet 100 series controller MLi's and Data sheets.

Issue The purpose of this verification checklist is to provide documentation to the Project Manager that the Site Engineer has confirmed the Continuum Security configuration. Basic Settings Access Events Reporting Alarm Event Notification and Alarm Enrollments Door Alarms Other Alarms Time Sync Video including Pelco Digital Sentry IP Camera System Administrative Tasks Other Tasks Basic Checklist Access Events Reporting Checklist Alarm Event Notification and Alarm Enrollments Checklist Door Alarm Checklist Other Alarm Checklist Time Sync Checklist Video Checklist Administrative Tasks Checklist Other Tasks Checklist Environment Continuum with Security enabled Pelco Digital Sentry IP Camera System Cause Beneficial checklist for Verification of security site settings. Resolution Please find the attached pdf document which will walk you through the Continuum Security Checklist. The first section provides step by step instructions for novice users. The second section is the actual checklist where each task should be initialed by the Site Engineer, and the whole document signed by the Site Engineer and the Project Manager. To print the Checklist section of this procedure, start printing on page 21 of the attached checklist. Please find the attached pdf document which will guide you through a Pelco Digital Sentry IP Camera System Quick-Setup

Issue Where to go to download the Access Expert Device Administrator application. Product Line Access Expert Environment Server 2012 SQL 2012 and above Premise Install V2 Hosted V2 Applet V3 Cause There is no documentation on where to go to download the Device Administrator and how to program the SSC to communicate with the selected application. Resolution The following steps describe where to go and download the software and how to use it to program an SSC: Go to the EcoBuilding Exchange In the search field type Device Administrator Select the Access Expert Device Administrator and download to any location Browse to location and double click execute to run and install the program Accept Agreement and click next to continue installation Click Next to start installing the software Select the location where the file will be installed Successfully loaded software To complete installation, click on Finish Connect the device to a network switch that is open to the internet and launch the application by opening Access Expert device Administrator from the Schneider Electric group in All Programs Launch the application  Right click on the usb line or click on the green arrow to the top left to upgrade the software Once upgraded successfully, Right click again on the line and select properties then select the Ethernet 1 ConfigurationTab Select applicable choice whether it is DHCP or Static addressing being used and click on OK. Once the device comes back Online, select the DIP Switches Tab and check the box for Default User Using the IP address given from step number 13, open up IE and browse to that address Once opened, configure the SSC per Setting up an SSC (System Security Controller), EP1501 and EP1502 Mercury Controllers.

Issue TAC EM 5 Actuator requires replacement. Product Line Field Devices Environment EM 5 EM5C EM5 Actuator Cause TAC EM 5 Actuator requires replacement Resolution The TAC EM5 Actuator is totally obsolete and no direct replacement is currently available. Details of the TAC EM5 Actuator can be found in EM5 OBSOLETE.tmp.pdf. The TAC EM5 Actuator was capable of use in control systems having alternative electrical wiring connections.   Alternative 1 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA DC positioning signal. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. Details of the S-E MD10A-24 Actuator may be viewed in MD10A S-E.pdf. N.B. The S-E MD10A-24 should be checked for electrical compatibility with other control system devices that it is to be integrated with. It is unlikely that it will be mechanically compatible with the other control system devices such as the Control Valve Body. Arrangements may therefore need to be made for the design and manufacture of a suitable Linkage Kit.   Alternative 2 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA positioning signal with 16 Vdc output. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. It should be noted however that no 16 Vdc output is available from the S-E MD10A-24 and none can be connected. A 16 Vdc power supply should therefore be installed to provide power to any external Controllers or Auxiliary Units.

Issue What are the proper configurations in the network Poll Service to balance the BACnet packet traffic for better data handling? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series ENC and Jace 8000 Cause Improperly defined poll rates, and poll groups in the Poll Service. Resolution This video demonstrates the Poll Service configurations in a Jace (MS/TP and IP) and an Enterprise Server (IP)   About Polling  Polling Statistics  Polling Rate Tuning  About Polling Components   

Issue Is it possible to use both Modbus/IP and BACnet/IP on the same AS-P Ethernet Port 2? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Cause There is a need to have both Modbus TCP as well as BACnet/IP devices on the same AS-P secondary Ethernet port. Resolution This is not a common configuration so it has not been tested extensively. With regards to the architectural guidelines, consider the Modbus/IP as BACnet/IP devices. For example, where the maximum number of SpaceLogic BACnet/IP devices per private IP field-bus is 200, adjust this limit to 190 if you have 10 Modbus/IP devices on the secondary Ethernet port.