Building Automation Knowledge Base

Issue ADI FSCO Panel Integration Product Line TAC Vista Environment ADI FSCO Panel Xenta 913 Cause Integration to an ADI Fire/Smoke Control Panel. Resolution This document details the process for integrating an ADI FSCO Panel (www.adipanel.com) with a TAC Xenta 913 through the ModBus serial interface. Comm Settings In XBuilder, right click the "RS232-485 A" Serial Port, add a ModBus Slave interface. The comm settings necessary are shown below:   The ADI FSCO Panels speak RS232. The 913's baud rate is adjustable in XBuilder from 300 to 19200. The panel's baud rate is adjustable via DIP switches from 2400 to 19200. There is no right or wrong speed, they just need to match. Parity is even, 7 data bits, 1 stop bit, and ASCII framing mode. On the ModBus serial line slave, right click and add a device. If it has not been created yet, you will need to create a device template first. The device requires a ModBus address. With an ADI FSCO Panel, this address is always 1. Physical Connections The RS232 port is an RJ45 port on the left front of the 913 labeled “A.” If you are creating your own patch cable to tie into the ADI FSCO Panel, the pin-out is as follows:   1 - White Orange 2 - Orange 3 - White Green – TXD 4 - Blue – RXD 5 - White Blue – GROUND 6 - Green 7 - White Brown 8 - Brown     TXD ties to the ADI FSCO Panel on the terminal block labeled "IN." RXD ties to "OUT" and GROUND ties to "GND." Signal Connections When populating connection objects between an ADI FSCO Panel and a Vista database, the best option is to use a Multi-Connection Object. Right click on the root folder in the System pane of XBuilder and select New > Object > Multi-Connection Object. The Multi-Connection Object can be populated by dragging and dropping points from the ADI Device Template and Menta. The Send Option in the Connection Manager lets you select either Periodically, Write on change, or Write initially and on change. Choose to write initially and on change. Each point also has a designated Period. Just because a point is not set to update periodically does not mean the period ceases to have any effect. If too many points are on the same period, it can overwhelm the 913. So regardless of the Send Option, the Period (s) should be staggered. Set the first 20 points to 10 seconds, the next 20 points to 11 seconds (for example – in reality, just avoid having hundreds of points at the same period.) When finished populating all data fields of the Connection Manager, hit the Validate button on the bottom left corner and make sure there are no errors. Menta Programming Menta files that accept data from an ADI FSCO Panel do so through PVBs and PVRs. These come default with the "Backup" option selected. This is used to store the value in non-volatile memory on power loss. When using a PVR for a setpoint, this is a good thing. However, when something is constantly writing a value to this public variable, and it in turn is constantly writing values to flash memory, it can cause the controller to lock up and stop working. You must de-select the "Backup" option from any PVBs or PVRs in a Menta file that are accepting data from a connection object in a 913. Disclaimer This document is intended to address some of the most common (and most commonly overlooked) settings when integrating with an ADI FSCO Panel through a serial ModBus connection. Contact ADI for product information and to ensure that the correct FSCO Panel is ordered to facilitate this type of integration. No guarantee can be made that changes to the physical configuration, communication settings, or software format have not been made, so always check with your ADI sales representative first.

Issue How can I convert my BACnet B4920 to a BCX 4040 Using Cyberstation Environment Cyberstation BACnet B4920 bCX 4040 Cause Change model number from b4920 to bCX 4040 using Cyberstation. Resolution In Cyberstation V1.90 Service pack 1 the capability to convert a b4920 to a BCX 4040 has been added. In order to change the model you open the controller editor on the b4920 and from the model pulldown, select bcx 4040. This is a non reversible change so make sure you have a database backup before doing this. Once the model is changed, you will need to edit comm2 and verify that it has the same settings for the MSTP as comm1 did on the b4920. If you have not already done so you will also have to reassign any I/O points that were on the b4920 to different hardware such as XP modules or another b3 Controller. The conversion will leave the I/O points in the database but all the channels will be set to "0" so that any programs that reference them will stay in tact. Make sure to set the Bcx up with the same ACC Net ID and do not change the Bacnet Device ID or the comm2 and UDP Net ID's. They will stay the same as the b4920 had them. Once you have connected the BCX to the network and the MSTP controllers to comm2, you simply reload the Bcx, but you do not have to reload the b3 controllers. They should come online after the Bcx is reloaded. Prior to this version a deletion of the b4920 and all b3 controllers was required, and edited dump files needed to be imported into the Cyberstation to recreate the BCX and b3's, followed by a reload of all controllers.

Issue Xenta 555/731 resets when an alarm is blocked or unblocked. Environment Xenta 555, 731 XBuilder Cause If you set an alarm object to email you when the alarm is blocked or unblocked, the Xenta will send the email, and change the alarm state to blocked or unblocked, but then performs a reset. Resolution Work around for now is to not check the blocked and unblocked condition to send emails in XBuilder

Issue How to install hotfixes that replace executable files. Environment Continuum Cyberstation Cause No longer need the existing executable file and want to replace with the hotfix file. Resolution The correct way to install a hotfix that replaces an executable file is to either delete the original file before installing the hotfix or to do the below. In Windows Explorer drag and drop copy the original file so you end up with a file called Copy of xxxxx.exe Delete the original file through Windows Explorer. Then extract the hotfix file into the Continuum directory through Windows Explorer.

Issue If a Variable status alarm is setup on a BACnet point it never triggers. Environment Workstation V1.8.1  and earlier Cause The reason is that the 3 available triggers (Forced, Overridden and Offline) do not apply to the BACnet protocol. If you open up the bindings page for a BACnet point you will see that none of the BACnet point attributes are the same as these 3 trigger statuses. Resolution Although from the SBO side you can force a point, what actually happens is that the value becomes commanded at "Command priority 8" (by default). The BACnet protocol does not have a Forced attribute. There is also no attribute listed for Overridden and Offline point in the BACnet standard. Because of this the Variable Status Alarm does not apply to a BACnet point.  

Issue In Niagara G3, how can the status (up / down) of a device object be trended? Environment Niagara G3 Cause Recording a connected controller's communication status Resolution Within the Wire Sheet that contains the device shadow object: Insert a StatusDemux object (from the kitControl pallet, Util folder).  Link the "Status" from the device object to the "In Status" of the StatusDemux object Insert a Boolean Writable object.  Link the "Down" slot of the StatusDemux object to the "In10" of the Boolean Writable object Add a BooleanCov history extension to the Boolean Writable object.  This will then track the up / down status of the device.

Issue   Invalid database version. (Subsystem: LNS, #81)[DB #-2038] Environment LonMaker 3.1 Cause A computer running LNS version 3.2 or higher (sometimes called LNS Turbo) can open any LNS database. If the database being opened is LNS version 3.1 or earlier, the database will be upgraded. This process is irreversible. Once the database is upgraded, earlier versions of LNS can no longer open it. The opposite is not true. If a computer running LNS version 3.1 attempts to open a 3.2 database, this error will appear. Resolution The LNS version must be at 3.2 or later to open a 3.2 database. Either upgrade the LNS version on the PC attempting to open the database, or revert to an earlier version of the database before it was upgraded (if possible). To upgrade your LNS version to 3.2: Navigate to http://echelon.com/support/downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks.

Issue An error is received on Continuum startup on videoLaunch Method 'There is an installation configuration problem, and this application is unavailable...constructor error' not found. Environment Windows XP SP3 Windows Server 2003 Continuum 1.91 Webclient 1.91 Cause Some PCs come with .net 3.5 pre-installed. If Continuum 1.91 is installed the installation will complete, but then the method, constructor error is received. The compatibility matrix indicates that we require .net 3.5 SP1.  Resolution Install .net 3.5 SP1 and attempt to start Continuum. If the same error pops up then do the following: Remove continuum from Windows Add/Remove programs from Windows Control Panel Reboot the PC Install 3.5 SP1 by running donetfx35.exe (This is on the service release CD in the NetFramewrok3.5 folder) It contains SP1. Reinstall Continuum This error could also occur if 1.90 is being used and .net 3.5 SP1 is installed

Issue An Internet Explorer ActiveX function involving the running of Java applets used to display the I/A Series R2 graphics prevents the Java applet from executing properly. Environment I/A Series R2 software release 522.v2, 529 or 532 Cause Microsoft changed the procedure by which Internet Explorer handles third party ActiveX applets, including the Java applets used in the I/A Series R2 system.  This change was applied as an update to all older versions of Internet Explorer and is included in Internet Explorer 8. Resolution There was a workaround provided with the R2 522.v2 release that can be used to prevent this Java applet activation issue from happening. The update consists of adding or modifying some of the information in the station.properties files and applies to both ES based stations and UNC based stations. 1. To update the Enterprise Server / WorkPlace Pro, save and backup the station database accordingly. While in the admin tool, open the station.properties file.  Select menu item Admin Tool -> Host -> Edit File -> System Properties.  Edit the file by adding the following text to the end of the file.   Make sure not to delete the # character as this specifies a comment line.  Save and close the system.properties file (File ->Save). # This is used to disable the IE ActiveX activation fix. If set to # to false, then the user will be required to click on the applet # before he is able to interact with it (only effects IE users). ie.activex.activation=false 2. To update the UNCs, log into the UNC using the Admin Tool and open the station.properties file.  Select menu item Admin Tool -> Host -> Edit File -> System Properties.  Edit the file by adding the following text to the end of the file. Make sure not to delete the # character as this specifies a comment line.  Save and close the system.properties file (File -> Save). # This is used to disable the IE ActiveX activation fix. If set to # to false, then the user will be required to click on the applet # before he is able to interact with it (only effects IE users). ie.activex.activation=false

Issue Temperature inputs not reading the correct values Environment Cyberstation IOUs Controller Cause Bad input Bad controller Bad sensor Resolution Replace sensor with a 10k ohm resistor.  Temperature input should read roughly 77°F or 25°C.  If it does then the problem is with the sensor.  If it does not then the problem is either with the input board or that particular input itself.

Issue Error message when opening Vista 5.1.5 Webstation: "HTTP Error 404.2 - Not found. The page you are requesting cannot be served because of the ISAPI and CGI Restriction List settings on the web server." Product Line TAC Vista Environment Windows 2008 server (32-bit & 64-bit). Webstation 5.1.5, 5.1.6, 5.1.7 Cause ISAPI (Internet Services Application Programming Interface) and CGI (Common Gateway Interface) services are not activated by default in Windows 2008 Server. Resolution After following the installation instructions in the Vista 5.1.5 TPA-VSTA-11-0002.01 (or Send to controller fails with "Not enough memory" error in Distribution View) do the following: Click on Start and then Run. Type inetmgr Once Internet Information Services Manager has opened, change to "Detail View" in the View menu. Double-click on ISAPI and CGI Restrictions Feature.   Under the "ISAPI and CGI Restrictions" right-click on ASP.NET v4.0.30319 and select "Allow". Webstation should now work.

Issue Satchwell ALX series Linear Actuator requires replacement. Environment Satchwell ALX series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Cause Obsolescence of Satchwell ALX series Linear Actuator. Resolution Replace Satchwell ALX series Linear Actuator with MV15B-24 Linear Actuator and Linkage Kit :-  ALX = MV15B-24 + L7SV (880-0662-000). Note: this part no. is for both actuator and linkage kit.  N.B.  Should the Satchwell ALX series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the MV15B-24 Actuator as appropriate :-  S2 – MV15B = Two independent 250 volt 10 amp / 3 amp rated SPDT Auxiliary End Point Switches.    Particular care should be taken when selecting an S-E Forta MV15B-24 Actuator to replace an existing Satchwell ALX series Actuator. The S-E MV15B-24 Actuator may be used to replace an existing Satchwell ALX series Actuator but it should be noted that where an existing Satchwell ALX series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single S-E MV15B -24 Actuator (12VA) will also be required. (e.g. S-E Transformer Type TR32)  Where an existing Satchwell ALX series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALX series Actuator (3.5VA) only. In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E MV15B-24 Actuator (12VA) (e.g. S-E Transformer Type TR32)

Issue Satchwell AR Series 1 or AR Series 2 Rotary Actuator requires replacement Environment Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Satchwell ARE ARM & ARX Series 1 and Series 2 Rotary Actuators Cause Obsolescence of Satchwell AR Series 1 or AR Series 2 Rotary Actuators Resolution Replace Satchwell AR Series 1 or AR Series 2 Rotary Actuators with appropriate S-E MD Series Rotary Actuators and wire as follows: Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies ARE ARE Series 1 & 2 Wire Colour BLUE  =  MD10A-24 or MD20A-24 Wire Number 2 ARE Series 1 & 2 Wire Colour RED  =  MD10A-24 or MD20A-24  Wire Number 3 ARE Series 1 & 2 Wire Colour BLACK  =  MD10A-24 or MD20A-24  Wire Number 1 ARE Series 2        Wire Colour WHITE  =  MD10A-24 or MD20A-24  Wire Number 5  ARX ARX Series 1 & 2 Wire Colour RED  =  MD10B-24 or MD20B-24 Wire Number 3 ARX Series 1 & 2 Wire Colour BLUE  =  MD10B-24 or MD20B-24  Wire Number 2 ARX Series 1 & 2 Wire Colour BLACK =  MD10B-24 or MD20B-24  Wire Number 1  ARM – UP TO MARCH 2006 ARM Series 1 & 2 Wire Colour RED  =  MD10B-230 or MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLUE  =  MD10B-230 or MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLACK  =  MD10B-23 or MD20B-230 Wire Number 1  ARM – SINCE MARCH 2006 ARM Series 1 & 2 Wire Colour BROWN  =  MD10B-230 or MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLACK  =  MD10B-230 or MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLUE  =  MD10B-230 or MD20B-230 Wire Number 1  Note: Should the Satchwell AR Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the S-E MD Actuator as follows: MD – S1  One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch  AR COMMON Wire Colour ORANGE  =  MD-S1 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S1 N/O contact Wire Number S3      AR N/C contact Wire Colour WHITE  =  MD-S1 N/C contact Wire Number S2  MD – S2  Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches  AR COMMON Wire Colour ORANGE  =  MD-S2 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S2 N/C contact Wire Number S2  AR COMMON Wire Colour BLACK  =  MD-S2 COMMON Wire Number S4 AR N/O contact Wire Colour RED  =  MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Colour BLUE  =  MD-S2 N/C contact Wire Number S5   Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE ARE Series 1 & 2 Wire Colour BLUE  =  MD20A-24 Wire Number 2 ARE Series 1 & 2 Wire Colour RED  =  MD20A-24 Wire Number 3 ARE Series 1 & 2 Wire Colour BLACK  =  MD20A-24 Wire Number 1 ARE Series 2        Wire Colour WHITE  =  MD20A-24 Wire Number 5  ARX ARX Series 1 & 2 Wire Colour RED  =  MD20B-24 Wire Number 3 ARX Series 1 & 2 Wire Colour BLUE  =  MD20B-24 Wire Number 2 ARX Series 1 & 2 Wire Colour BLACK =  MD20B-24 Wire Number 1  ARM – UP TO MARCH 2006 ARM Series 1 & 2 Wire Colour RED  =  MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLUE  =  MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLACK  =  MD20B-230 Wire Number 1  ARM – SINCE MARCH 2006 ARM Series 1 & 2 Wire Colour BROWN  =  MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLACK  =  MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLUE  =  MD20B-230 Wire Number 1  Note: Should the Satchwell AR Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the S-E MD Actuator as follows: MD – S1  One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch  AR COMMON Wire Colour ORANGE  =  MD-S1 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S1 N/C contact Wire Number S2  MD – S2  Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches  AR COMMON Wire Colour ORANGE  =  MD-S2 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S2 N/C contact Wire Number S2  AR COMMON Wire Colour BLACK  =  MD-S2 COMMON Wire Number S4 AR N/O contact Wire Colour RED  =  MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Colour BLUE  =  MD-S2 N/C contact Wire Number S5

Issue Declaration of Conformity on I/A Devices Environment MicroNet 2000 Family of Products (MN Controllers & MN Sensors) MicroNet BACnet Family of Products (MNB Controllers & MNB-ROAM-IA) MicroNet LON Family of Products (MNL Controllers & MN Sensors) UNC/ENC Family of Products (UNC-410 & ENC-410 Controllers) UNC/ENC Family of Products (UNC-520 & ENC-520 Controllers) Cause Help locate information regarding Declaration of Conformity for I/A Series hardware. Resolution Information on Declaration of Conformity for I/A Series are available on The Exchange Download Center.

Issue How to load up archived data in a report using Seven Reports Product Line TAC INET Environment I/NET Seven  SevenReports Archiving Cause Reports show nothing or have one blank page and fail to show data that meets the date window specified Resolution When using Seven Reports to view data, archived data can be viewed and put into a report.  From the Archives pull-down menu, Mount/Dismount the archive files. Files, by default, are stored in the c:\INET Seven Data\Arch folder. After mounting the needed reports (look at the date of the files in the archive folder), the report used must have the word ARCHIVE in the file name. This specifies that the reports will be pulled not from the current database but rather from the mounted files and on the dates specified. The reports should now be from the Archived files mounted. Archive Reports are located on the install CD under CD\Program Files\INET Seven\Reports To download, click on the link below and select to save the report to your hard disk in the c:\INET Seven Data\Reports folder:   I/NET Seven Release 2.20 and Prior files: ArchiveOverrideBillingSamples.rpt ArchiveRuntimeSamples.rpt ArchiveTransactionsDoors.rpt ArchiveTransactionsIndividuals.rpt ArchiveAnalogSamples.rpt ArchiveConsumptionSamples.rpt ArchiveDemandSamples.rpt ArchiveDiscreteSamples.rpt   I/NET Release 2.21 to current: ArchiveAnalogSamples_xi.rpt ArchiveConsumptionSamples_xi.rpt ArchiveDemandSamples_xi.rpt ArchiveDiscreteSamples_xi.rpt ArchiveOverrideBillingSamples_xi.rpt ArchiveRuntimeSamples_xi.rpt ArchiveTransactionsDoors_xi.rpt ArchiveTransactionsIndividuals_xi.rpt   Tip: In some instances, while the report is running and the data is being compiled, if you move the mouse or strike a key, the process starts all over. The solution is to start the report and wait for a few minutes if you have input a broad range of data to search and produce.

Issue Multiple passive 4-20mA sensors needs an external power supply and connected to a Sigma controller.  How can this be done? Environment Sigma AI Passive 4-20mA 12v DC or 24v DC Cause Non-passive 4-20mA sensor have a built in power supply.  A passive 4-20mA sensor requires an external power supply when connecting to a Sigma controller Resolution Use a 12v or 24v dc power supply as the external power supply per sensor The positive side must be connected to the Sigma controller The correct jumper settings (current mA) are required before connecting the external supply.

Issue A door value is reported as unlocked when it should be locked, is there a way to confirm the physical state of the relay output without going to the panel and looking at the hardware? Environment CX9680 ACX5720/40 CX9900 CX9702 Cause Need to verify the physical state of the relay controlling the door lock remotely. Resolution In Continuum, output points (including doors) have an attribute called 'OverrideValue' that reads feedback in the hardware to report the physical state of the output. The overridevalue flag can be printed from the command line as seen in the screen shot below. In the example above, a door configured with default strike time of 10 seconds reports the physical state of the relay output after a valid access or Exit Request transaction.

Issue Is a license required for the S4 BACnet to N2 Routers? Environment S4 BACnet to N2 Router-16 S4 BACnet to N2 Router-32 S4 BACnet to N2 Router-64 S4 BACnet to N2 Router-128 S4 BACnet to N2 Router-256 I/A Niagara R2 I/A Niagara G3 I/A BACnet Metasys N2 network Cause Additional information on 3rd party router Resolution No license is required. But you will need to fill out the S4_Group_Order_Form and send it to CCC at the time of ordering. Link to S4 BACnet to N2 Routers for additional information

Issue Error Messages: Windows - Delayed Write Failed Windows was unable to save all the data for the file D:\VISTA DB _23032011\$queues\insertevents. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Windows - Corrupt File The file or directory \VISTA DB _23032011\$queues\insertevents is corrupt and unreadable. Please run the Chkdsk utility. Product Line TAC Vista Environment TAC Vista Cause Problem with Operating System (or) Hard Disk Fault (or) Link between $queues with Vista Database. Resolution As there may be several issues that are causing this, there are three options to look at: OPTION 1: Restore the OLD TAC Vista Data Base Backup. Refer to TAC Vista Technical Manual chapter 26 for re-storing database procedure.   OPTION 2: There might be a linking problem with this folder and Vista.  Here are the steps to check if this is the problem: If the problem still exists, Check for hard disk errors. Find the $queues - folder in existing database folder ( \DB\$queues) Copy the files to an other location and delete current folder (Refer to An efficient method for deleting all queued files in the $queues folder) Recreate it with same folder names and copy back the files into $queues-folder. If the problem still exists, Check for hard disk errors.   OPTION 3: Check for hard disk errors, follow the below procedure: Go to "My Computer", Right click on Hard Disk Drive – typically - C, and Click on Properties. Go to Option "Tools" and Click on "Check Now" under "Error-Checking"

Issue The platform daemon for the localhost displays this error: ERROR   [09:21:09 28-Jun-2011] [tid=712] app registry: app svr_station NOT created, maximum app limit reached All of these stations were part of a migration from one version of G3 to another.  All the station folders were copied and pasted prior to starting Workbench. Environment Niagara G3 version 3.5 and older Cause More than 32 stations are not supported on any G3 platform (3.5 and older).  This is not a license restriction. The 32 station limit applies to the number of station folders on the hard drive under the release directory.  This is only a constraint for engineering the stations.  In Release 3.6, 3.7 & 3.8, the limit is  in excess of 150 "station" folders. Resolution If one computer (running Workbench) is being used to engineer more than 32 stations, then some of the station folders will have to be cut / pasted back and forth with some other temporary folder on the hard drive. Example: A job will have 35 total stations when complete.  In order to engineer them from one computer, 3 station folders will have to be cut out from beneath the parent "stations" folder and put in a temporary folder elsewhere on the hard drive. When there is a need to engineer one of the three cut stations, use Windows Explorer to move it back into the Niagara "stations" folder and remove some other station folder.  Always maintain 32 sub-folders under the "stations" folder. In Release 3.6, 3.7 & 3.8, the limit is  in excess of 150 "station" folders.