Building Automation Knowledge Base

Issue 'Operlist.txt file missing' alarms are seen in the Sigma Alarm Manager. Operlist.txt files have been downloaded to the controllers and the controller's contents show that the operlist.txt file exist.  Environment Sigma 4.07 build 3.45.48 (upgraded from BAS2800+ or Sigma versions prior to 4.04) Cause The operlist.txt file is required for Sigma controllers. Starting from Sigma 4.04, the Sigma controllers uses a dummy operlist.txt file. There is no longer the need to create this file manually. The Sigma server automatically creates a suitable dummy operlist.txt file for downloading to the controller. However, if an operlist.txt file exists in the controller / outstation folder, then that file will be sent to the controller and not the dummy one. In this case, the existing operlist.txt files still exists in the controller / outstation folders.  Resolution Delete the existing operlist.txt files from the controllers / outstation folders. A quick way to do this is to use the Windows Search function to search for the file name 'operlist.txt' inside the C:\Sigma\Data folder and delete all the files together.    In Sigma System Diagnostics, download the operlist.txt file to all controllers. A dummy operlist.txt file will be created in each controller / outstation folder and the file will be downloaded to the controller. 

Issue Where can the Zelio relay family be ordered? Environment Zelio relay Cause Unable to order through Schneider Electric Buildings organisation. Resolution The Zelio relays are available through the Schneider Electric Power business organisation. Please contact the regional Schneider Electric front office for more information.

Issue If the actuator is closing in the wrong direction, how can that be changed? Environment Forta series actuator: M300 M400 M750 M800 M1500 M3000 Cause Depending on application, you may want to change the direction of the actuator movement. Resolution Invert the control signal by changing dip switch no 7 settings. For changes to take affect, the power supply needs to cycled or the manual operation handle needs to be lowered and raised back to normal position.

Issue After transitioning an INET security system to Security Expert, SCU1200 and SCU1280 controllers do not come online Product Line Security Expert, TAC INET Environment Security Expert Controller (SP-C) I/NET SCU1200 I/NET SCU1280 Cause The INET-to-Security Expert transition brings each SCU1200/1280 into Security Expert as an Input Expander but there is a known issue that causes the devices to remain offline. R&D is working on a fix. Resolution The workaround for bringing a SCU1200/1280 controller online in Security Expert is to create a Reader Expander and then edit the inputs and outputs associated with the SCU1200/1280 to point to the Reader Expander you’ve just created.   Important:  Create a backup of your Security Expert database before proceeding with the instructions that follow.   For a transitioned SCU1200/1280, create a Reader Expander as follows: In Security Expert, navigate to Expanders > Reader Expanders. Choose a Controller from the drop-down list. Click the Add icon. Define a Name for the expander.  The transition tool would create a name like SCU1200 <703503> for the expander.  In this example, the SCU’s link address is 70, its station address is 35, and its point address is 3. When manually defining the name of the new expander, you may wish to use this naming convention to keep the system uniform. Set the Physical Address of the expander.  This address should be 1 higher than the point address of the SCU.  So, for SCU1200 <703503>, the point address is 3 (703503) and so the physical address of the expander should be set to 4. Set Port 1 Network Type to “Third Party Generic”. Set Port 2 Network Type to “Third Party Generic”. Expand the Commands section and enter the following commands:       PortOne=INET       HardwareType=INET Navigate to the Reader 1/2 tabs and perform the following steps: Set Reader 1/2 Keypad Type to “None”. Uncheck Allow Reading Opened/unlocked. Uncheck Display Card Detail when Invalid. Navigate to the Reader 1/2 Options tabs and perform the following steps: Uncheck Door Sense Enabled. Uncheck REX Enabled. Uncheck Invert REX Input R1/2. Uncheck Always Allow REX R1/2. Save the expander. When presented with the Configure Module wizard, perform the following steps: Set Inputs to 0. Set Outputs to 0. Uncheck Add Trouble Inputs. Uncheck Add Doors. Click Add Now.   Edit the inputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Inputs. For each input associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the input.   Edit the outputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Outputs. For each output associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the output.   When you have finished with all of the steps above, perform a Module Update on the Reader Expander.  Repeat these steps as necessary for other SCU1200/1280 devices.  Once you have verified all SCU1200s/1280s are working properly, you can delete the Input Expanders that were created by the transition tool since they are now unnecessary.

Issue Controller comm is lost after enabling Network Security after properly configuring the Controller and Workstation. Environment Network Security NCII CX9680 ACX5740 ACX5780 Cause Network security activation was being inhibited by the domain user security policies. Resolution In this case both the controllers and Windows network security policies had been configured properly for Continuum.  This fact was confirmed when the IT department got involved.  Once they relaxed some of the security policies on this machine Continuum network security began to work as expected, both from the controller and Cyberstation point of view. The customers IT personnel did not share with us what policies were responsible for the activation issues.

Issue When replacing a brand x valve with a Forta M800, a linkage kit may be necessary. Product Line Field Devices Environment Forta M800 VSB VSB4F VSB F AG52 8800129000 Cause Linkage kit requirement for application. Resolution Linkage kit required between Controlli VSB valve and Forta M800 is the AG52, part no 8800129000.

Issue Receive data from Trend log (Seven Trends) with incorrect base time hh:12 even though it is set to 00:00.   Environment I/NET Seven  Seven Trends Xenta Server 527 / 527-NPR / 731 Cause When using a Xenta Server as an I/NET NetPlus Router (NPR) and have configured a Trend (Seven Trends) with a sample count of 24 and sample interval of 60 minutes it appears that the time is incorrectly reported to the I/NET Host.  This issue will be rectified in a future release of the Xenta Server firmware.  Resolution As workaround to this issue, the Sample Count value below 24 should be used.   This is issue is not seen when using a Direct Connect configuration 

Issue Schneider Electric part number equivalent to Belimo NM24-US Environment Belimo NM24-US MD10B-24 part no 8751015000 Cause Cross reference for replacement of existing actuator. Resolution The Belimo NM24-US seems to be obsolete. The replacement today would be the MD10B-24, part no 8751015000.

Issue The hard drive fills up with logs generated by PostgreSQL/Timescale. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause Trend meta table missing information Resolution In the ES, go to the TimeScaleDB configuration. Set Trend and Event storage to false and click save. Set Trend and Event storage to true and click save.

Issue Synchronizing time across many networks and multiple time zones Product Line Andover Continuum Environment Continuum Cyberstation Cause Guidelines for implementing an efficient yet compact Cyberstation PE program to synchronize time on large installations consisting of many Continuum networks across multiple time zones. Resolution The solution presented here requires that in each network the time master (controller with the lowest ACCNetId) is identified by setting its description to PTM. (Primary Time Master) It is also recommended that the controller with the second-lowest ID is identified as the STM. Obviously, the program itself could identify the time master for each Network but doing this outside of the program makes for a simpler, more robust implementation. To implement the solution, simply create a program in one of the Continuum Cyberstations and insert the code provided below. Configured the HOUR System Variable in the Cyberstation to trigger the program. The program, as written, will sync the time once a day at 3:00 AM There is a local variable (Verbose) that controls the level of information the program prints to the message window, recommends this be set to print everything when the implementation is first put in place to ensure it is operating as expected, then print only errors afterward. 'This program synchronizes time between Cyberstation and controllers across Networks and time zones. 'Program is triggered by the HOUR system variable 'SETUP 'In each network, the controller with the lowest ACCNetID must be identified as the Primary Time Master ' by setting its description to PTM 'Optionally, the controller with the second-lowest ACCNetID can be identified as the Secondary Time Master ' by setting its description to STM 'v1.0 SE PSS 1010 1011 1110 - FOR PROOF OF CONCEPT PURPOSE ONLY '-------------------------------------------------------------------------------------------------- Object theCX Object theNetwork Object theWS 'The Workstation where the program is running Number WS_UTCOffset 'The UTC Offset of theWS Number syncDone Number Verbose 'Prints to theWS message window. Set to 1 to print errors only, set to 2 to print synchronization information. Line INIT If Hour <> 3 then Stop 'sync time once a day at 3am theWS = CurWorkstation() 'get the name of the Cyberstation where the program is running WS_UTCOffset = getname("root\" ; theWS Alias ; " UTCOffset") 'and theWS UTC Offset Verbose = 0 'default to silent operation Goto SynchronizeTime Line SynchronizeTime If OpenList("Network", theNetwork) is Success then While GetObject(theNetwork) is Success 'for each Network... If Verbose = 2 then Print "Syncronizing time on NETWORK: " ; theNetwork Alias If OpenList("InfinityController", theCX, theNetwork) is Success then While GetObject(theCX) is Success 'for each CX controller in the network... syncDone = False 'reset the sync done flag 'Print theCX alias REMOVE COMMENT TO PRINT CX NAME, HELPFUL WHEN DEBUGGING THIS PROGRAM If theCX Description = "PTM" and theCX CommStatus = OnLine then 'is this controller the time master and if so, is it ONLINE? If Verbose = 2 then Print "Time syncronized on NETWORK: " ; theNetwork Alias ; ", CONTROLLER: " ; theCX Alias ; " (Primary Time Master)" getname(theNetwork Alias ; "\" ; theCX Alias ; "\Date") = Date + ((theNetwork UTCOffset - Cyber221 UTCOffset) * 60) 'synchronize its time syncDone = True 'we're done with this network... Break '...so break out of the inner while loop Endif If theCX Description = "STM" and theCX CommStatus = OffLine then 'look for a secondary time master if primary not online If Verbose = 2 then Print "Time syncronized on NETWORK: " ; theNetwork Alias ; ", CONTROLLER: " ; theCX Alias ; " Secondary Time Master" getname(theNetwork Alias ; "\" ; theCX Alias ; "\Date") = Date + ((theNetwork UTCOffset - Cyber221 UTCOffset) * 60) 'synchronize its time syncDone = True 'we're done with this network... Break '...so break out of the inner while loop Endif Endwhile CloseList(theCX) If syncDone = False and Verbose > 0 then Print "No time master found online for NETWORK: " ; theNetwork Alias ; "," ; Date Else If Verbose > 0 then Print "ERROR, can't open Controller list " ; Date Endif Endwhile CloseList(theNetwork) Else If Verbose > 0 then Print "ERROR, can't open Network list " ; Date Endif Stop Line E If Verbose > 0 then Print "Program hit ERROR line, " ; Date Stop

Issue Which valve actuator is the correct choice for V222?  Environment V222 7212254000 7212258000 7212262000 7212266000 7212270000 Forta M22 M50 Cause Suitable actuators for V222 Resolution For V222 DN65 to DN100, the Forta series is the recommended actuator. For V222 DN125 and DN150, M22 or M50 should be used. The Forta series actuator will not fit these valves.

Issue The entries are displayed in the order they are entered into the table, is there any way to change the order so that the list of attributes is alphabetical? Environment Continuum Personnel Manager Cause The list of Allowable Attribute Values is not sorted alphabetically and is not able to be sorted. The entries will stay in the order they were entered. Resolution Unfortunately there is no way to re-sort these attributes into another order. They will need to be removed from the list and then re-entered in the order that they need to be presented. (Note: Defect#958 has been raised for this issue.)

Issue The maximum number of backups in Vista is 20. Is it possible to change this limit? Product Line TAC Vista Environment Vista Server Cause When backups in Vista are set up, you can specify the maximum number of backups that should be created before the oldest is overwritten. The default is two, and the maximum is twenty. Resolution It is not possible to change this limit as it is a hard-coded number in Vista.

Issue CyberStation error on startup Environment CyberStation v1.91, Windows XP Pro SP3 Cause Windows user permissions Resolution Random DLL files didn't have the proper permissions.  The steps to fix it: 1)       Log in as the user that can't start CyberStation. 2)       Launch ProcessMonitor. 3)       Launch CyberStation (it should error out) 4)       Click the filter button in ProcessMonitor then filter for Process: "Continuum.exe" or Result: "Access Denied" 5)       Find one that failed.  Log in as the admin user and change the permissions. 6)       Repeat for each failed file.

Issue Getting an Unable to save because attached device is not specified error when trying to import a Cyber export file, even when using a file that has just been exported from the same Cyberstation.  Environment Export Import 1.9x Cause Improper path specified. Resolution The problem was resolved by adding the target InfinityController to the path statement.

Issue After replacing the BCX controller cannot bring b3 controllers online. Environment Node Count BCX4040 b3 Cause BCX was enabled for only 8 MSTP nodes. Resolution Replaced BCX with a 127 node BCX.

Issue During the startup of an ENC-520 station, the following warning message appears in the application director output: Platform Service Access Platform Service Qnx will not be added, feature 'accessControl' is not licensed. How can this warning be corrected? Environment Niagara G3 Cause This service is for a product line, offered by Tridium, that is no longer available. Resolution Remove the platAccess module from the ENC and reboot.

Issue Part numbers for SVEA Lighting modules. Environment SVEA LON Lighting Cause Part numbers no longer listed. Resolution The SVEA Brand of lighting control products became obsolete as of 1st January 2011. Please see Product Announcement PA-00139.

Issue Is it possible to use the V321 and V311 valves in applications with a glycol content up to 50%? Environment V311 V321 Cause   Some valves are not suitable for use in applications with glycol content in media. Resolution The V321 and V311 can be used in applications with deaerated water with glycol-type antifreeze agent (max 50%)

Issue Satchwell IAC 600 controllers remain Offline when connected to the Xenta. Environment IAC 600 Xenta 555 Cause A Satchwell IAC 600 controller fitted with DDC253 firmware remain Offline when connected to the Xenta 555.  Resolution This firmware is not compatible with the Xenta 555 and must be replaced. As this DDC253 firmware was fitted into an IAC 600 with specific hardware, the firmware cannot be changed, therefore the controller must be replaced.