Building Automation Knowledge Base

Issue What ElecType can be used with the current range of controllers Environment Continuum NC2 NC11 CX9900 CX9940 bCX bCX4040 bCX9640 ACX57 b3 i2 Cause What ElecType can be used with the current range of controllers Resolution The current range of Continuum controllers can't use most of the options available in Continuum (ElecType) as many of these are for older controllers. See Continuum help (in Cyberstation) for the best descriptions of use. Current range of controllers mostly use (see specific spec. for full details):- Voltage, Digital, Counter, ACCTemp(DegF), ACCTemp(DegC), Supervised To use any other analog sensors, within the current range of controllers, including thermocouples and RTDs, they need to be converted to a 0-10Vdc (or preferably 0-5Vdc) or 4-20mA and use "Voltage" ElecType   Other ElectTypes below. For CX9400 controller:- RTDTemp(DegF), RTDTemp(DegC), RTD1000TempF, RTD1000TempC, ThermCoupJTempF, ThermCoupJTempC, ThermCoupKTempF, ThermCoupKTempC, ThermCoupTTempF, ThermCoupTTempC, ThermCoupETempF, ThermCoupETempC, ThermCoupRTempF, ThermCoupRTempC, ThermCoupSTempF, ThermCoupSTempC, ThermCoupBTempF, ThermCoupBTempC, RTDTempF2W, RTDTempC2W, RTD1000TempF2W, RTD1000TempC2W Not Used:- ACC_InputCurrent, ACC_Keypad, ACC_Pressure, ACC_Airflow Older Controllers:- TankProbe

Issue When changes are made to the BACnet schedule in a third party device, the object editor crashes when the changes are applied. ACCTrace file shows the following error: The datatype of a BACnet property value specified in a service parameter does not match the datatype of the property referenced by the specified Property_Identifier. Environment CyberStation Continuum BACnet Trane SC Schedule Object Cause The object type is not fully support by the third party controller.   Consult the devices PICS statement. Resolution In some cases third party vendors will implement BACnet object types for internal use while not allowing other vendors to write to these object.  Occasionally it may be possible to write values to some of the objects properties.  However, when Continuum tries to write to a value to the unsupported property the object error will crash.

Issue Setting up a single user (SQLExpress 2005) v1.93 CyberStation and the SQL Service Manager is not popping up like it should (on the Windows taskbar). Environment Standalone CyberStation SQLExpress 2005 Cause Previous versions of CyberStation had a SQL Service Manager application in the Windows taskbar. When installing a standalone v1.93 CyberStation this application is not there. Resolution SQLExpress 2005 does not install that application. This application is not required to run CyberStation.  If for some reason there is a need to stop SQL Server there is a workaround. Go to Control Panel>>Administrative Tools>>Services. Then scroll down to SQL Server (SQLExpress). You can stop SQLExpress by right-clicking it.    

Issue When trying to save a simple InfinityProgram to map a third party BAcnet point, the error "Cannot find the item" is generated by the PE editor. Environment CyberStation ver. 1.81 bcx4040 Cause When trying to save the simple looping InfinityProgram below the error "cannot find the item" (on the ReadProperty statement) is generated. The LeavingChWTemp is updating fine on the BACnet side. It's just not mapping to the Infinity side.  Line 1 ReadProperty(BacnetDevices\BNet_3021\YKVSDIMK5005\LeavingChwTemp) Goto Line 2 Line 2 If (TS > 1) Then Goto Line 1 Resolution ContinuumExplorer had two BACnet icons on the tree - one with all the BACnet controllers and points and one with no controllers and points. The "empty" one was renamed BacNet_1. CyberStation was restarted. The program saved correctly. It appears that CyberStation was not referencing the correct BACnet instance and therefore Plain English could not resolve the path in the ReadProperty statement. Once the duplication was removed all worked fine. Note: There should never be more than one BACnet icon in ContinuumExplorer. In the case it was not determined how this situation occurred.   

Issue Using the SendMail function in the NC2 and ACX2 to know if CyberStation is shut down would be a nice feature. Environment CyberStation NC2, CX9680, bCX4040, bCX9640, ACX5720, ACX5740 Cause When a standalone CyberStation is not monitored 24x7 and it is emailing critical alarms or pulling extended logs, it is important that it remains up and running as much as possible. How can the newer controllers' email capability be used to add this functionality. Resolution The SendEmail function can be used for this purpose. Set up the bCX via the "Email setup" controller webpage. This will require at least one Outgoing SMTP Server be accessible to your controller. The workstation commstatus is not a supported function within Plain English (although it may appear to compile in a program), so the workaround is to write a workstation program that sets a numeric in the controller on fixed timeframe. An InfinityProgram in the controller can monitor that numeric value and send the email if the value is not updated. Here are two sample programs for your use that provide a starting point for this application: ======= 'Fallthru program in CX triggered by minute which sends an email every 30 minutes while the workstation is offline 'Note: Set (Minute-Heartbeat) long enough for a CyberStation reboot/restart to avoid false alarms on an intentional shutdown.  Checking: If Minute = 10 and (Minute - WSHeartbeat) > 4 then goto Sending If Minute = 25 and (Minute - WSHeartbeat) > 4 then goto Sending If Minute = 40 and (Minute - WSHeartbeat) > 4 then goto Sending If Minute = 55 and (Minute - WSHeartbeat) > 4 then goto Sending Stop Sending: SendEmail('theemailaddresshere', Date, 'CyberStation is offline') Goto Wait30m   Wait30m: If TM < 29 then goto Wait30m E: If TS > 60 then Goto Checking ========== ========== 'Looping, autostart program in workstation Wait30s: If TS > 29 then goto SetRemoteFlag   SetRemoteFlag: MyNetwork\My_bCX\WSHeartbeat = Minute Goto Wait30s   E: If TS > 2 then goto Wait30s ======  Note: For LAN Systems a workstation can monitor the other workstations using the CommStatus attribute.

Issue What is the processor and memory type & speed that is used in Continuum controllers? Environment All Continuum controllers Cause The processor speed for the i2/ b3 controllers are not defined on the datasheets. Resolution The bCX1 uses the Coldfire processor and it is running at 66Mhz. It has 32Mb SDRAM and 16Mb Flash memory.   The Netcontroller II uses a MCF5275 processor running at 150 MHz. It has 128Mb SDRAM and 32Mb Flash memory. The i2/b3 controllers also use a Coldfire processor but at 40MHz frequency. The memory on the i2/b3 controllers varies from model to model and these are detailed on their specific datasheets on the Buildings Business Extranet. Some examples are: b3920 1Mb SD RAM, 2Mb Flash, b3810 256Kb SDRAM 1Mb Flash, b3850 128Kb SDRAM 1Mb Flash.  

Issue Webpinpoint requires mime types and if a selected option is missing, the object doesn't show in IIS Environment Windows 7 Windows Vista Windows Server 2003 Windows Server 2008 Cause If all the IIS options in IIS that are specified in the webclient installation guide are not selected then objects for webclient installation will not be available. Resolution In Windows Control Panel> Programs and Features> Turn Windows Features On/Off  Make sure that Common HTTP Features> Static Content    is checked If not, check this options and restart the PC

Issue Launching all graphics on multiple Cybers shows Pinpoint as a white screen Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The active polling rate may be too high Resolution Set the active polling rate to 100 milliseconds Default is 30

Issue Want to install both Continuum LAN key and webClient Server Key (WEBC-PRO) to enable both Cyberstation and webClient functionality on the same computer. Environment Continuum Cyberstation webClient Server Cause Want to merge two functions of Continuum onto the same machine to save the cost of one computer. Resolution No, you can only install one Continuum Security Key on any PC. In a LAN environment you will need to have the Continuum Cyberstations and webClient Server on separate computers. To have both the functionality of a Cyberstation and a webClient Server on a LAN system will require two PCs.  

Issue Using PE functions designed to take multiple arguments (Minimum, Maximum, Average) with just one argument causes undesired behavior. Environment CyberStation i2 devices b3 devices Cause Functions expecting more than one argument require that more than one argument is passed. Resolution Make sure to always pass at least two arguments to PE functions that are designed to take multiple arguments such as Minimum, Maximum, Average etc For example: OAT = Minimum(MyNetwork\MyCX\Myi2Device) The line above may cause undesired controller behavior Replace the line above with the following line OAT = MyNetwork\MyCX\Myi2Device

Issue Request to exit motion sensor seems to be causing nuisance alarms. Environment CyberStation, ACX family, AC1 family, REX motion sensor  Cause Even though the exit request variable is "On" in the door object, if the door opens and closes more than once, a forced entry alarm is created. This causes issues when the REX motion never turns off and multiple users exit the door. Resolution In Continuum controller firmware once the door is closed and locked a change of state of the REX input is required to keep the alarm shunted. To simulate this, trigger the REX motion detector and then open the door while it is unlocked. The door relocks 1 second after opening. If the door REX signal goes OFF and then ON again, the door unlocks. If, while the door is unlocked, the REX signal goes OFF and ON and OFF and ON the door can be opened and closed with no forced entry OR it can remain open and no door ajar will occur. The same is true if you do not check 'unlock on exit request' - it's just harder to test because you cannot watch the REX signal as easy as the unlock output. The key to avoiding the nuisance forced entry alarms is to let the REX motion sensor cycle quickly - have it turn on and then off after 1/2 to 1 second. The forced entry alarm will be shunted until the door relocks. Then if there is still motion at the sensor the REX will come on again and the controller will continue to shunt the alarm.

Issue Need to be able to change any schedule inside a bCX1-CR from another BacNet/IP workstation like Citec SCADA. Environment BACnet bCX1-CR Citec SCADA Cause It is a project requirement to change schedules in a bCX-CR1 from a third party BACnet workstation. Is this possible? Resolution The answer to your question is not a simple yes/no. Please see page 8 of Product Implementation Conformance Statement bCX1-CR It describes the "writable" properties of the schedule objects in the bCX1-CR v4.5. Make sure that the BACnet workstation (B-OWS) that you wish to use to edit schedules in the bCX1-CR v4.5 supports (in its PICS) the properties that your customer needs to be able to edit. For example, from the linked PICS, it appears the Next_Transition_Time is not writable in the bCX1-CR v4.5. If this is a property that your customer requires the Citec SCADA to edit in the bCX1-CR v4.5 then there may be a problem. Since we do not provide support for Citec SCADA we cannot say whether or not it will work. You will need to talk to Citec or make a judgment based on their PICS.  

Issue Can badging be accomplished on a webclient PC Environment Continuum Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Customers have requested badging for webclient PCs Resolution Badging is not supported on the webclient PC. Repair will not enable this configuration. To resolve this, you will need a Cyberstation key with Epibuilder enabled for badging and a second PC with a webclient key

Issue A third party BACnet device does not support segmented messages but the bCX4040 does. Can the two devices communicate? Environment Continuum BACnet MS/TP MSTP bCX Cause A third party boiler BACnet MS/TP interface card is having difficulty communicating with a bCX4040. The manufacturer of the interface card has commented that the Continuum bCX uses segmented packets and the Bacnet interface card cannot communicate with a segmented packet delivery system.  Are these devices incompatible? Resolution The problem should not be related to message segmentation. This is because the bCX will try to send a segmented message and the third party device should send a response to the bCX indicating that segmentation is not supported. The BCX will then send only non-segmented messages to the device. So, the bCX supports message segmentation but can do both segmented and non-segmented messages on the same MS/TP bus.  Get an MS/TP capture with both devices on the wire while doing a Find BACnet Devices request from CyberStation and send to Product Support for review.

Issue Updating firmware from StruxureWare Building Operation and the still be usable with other BMS such as Continuum, I/A Series, I/NET, Sigma, and Vista Environment Site with more than one Building Management System  Cause Implications of updating firmware on a controller from the StruxureWare Building Operation side and still compatible with existing Resolution For the controllers available on the StruxureWare Building Operation network that have been configured, take precaution when updating the firmware and still expect compatibility with other systems. For example, at a Continuum site, with a b3 and the option to update of firmware from StruxureWare Building Operation, there are a couple of things to keep in mind. When selecting the b3, and the Update Firmware, it will ask you for the *.udp file. This can be downloaded from the extranet. The thing to keep in mind here is if you are using this controller in conjunction with Continuum, then pay particular attention to the Compatibility Matrix and the firmware which is compatible with the version of Continuum you are running. Updating a firmware that is not in line with the version of Continuum will create problems for the site. So when selecting the firmware *.udp, be sure of which firmware file you are selecting. The operating system in the b3 controller is no different between StruxureWare Building Operation and Continuum. The PE code may be different though, so he should be able to learn these controllers into Continuum as long as they have their user memory cleared out.  

Issue When a personnel object is created and Continuum launches the Personnel Manager, when the First Name, Last Name and Site Code is entered and the changes are applied, Continuum throws the following errors. Error Saving Data -- Unable to find an object in the database.Root\Card Access\... The personnel object was not created.   Environment Continuum CyberStation Personnel Manager Cause Illegal Characters in folder name Resolution Removed "&" and "/" from folder names. 

Issue There seems to be no way to delete the photo in a personnel object. Environment CyberStation Cause Keep the personnel object and delete the photos in the personnel object. Resolution There is no way to delete the photo once it has been captured into the personnel object, a workaround is to create a blank image using an application such as Windows Paint for example and then change the personnel’s photo to the blank image.

Issue Is it possible to email a temperature value twice a day to someone via Continuum? Environment SendEmail ACX2 NC2 bCX Cause A customer would like to get an email twice a day on a critical temperature in a lab. Emailing alarms is already done via CyberStation and Outlook. Can this be done, too? Resolution Yes, it can be done. And if you want it to NOT be emailed as an alarm, a good way to do it is to set up a bCX/ACX2/NC2 to be able to send email. Then write a Plain English program that uses the SendEmail function. You will need to write the temperature value to a string point. You can trigger the program to run twice a day. The syntax for the function is: SendEmail (to_string, subject_string, message_string, cc_string, bcc_string, signature_string)   See the CyberStation online help and search for SendEmail for more information.  

Issue When the mouse curser is hovered over bang in Continuum Explorer, the tool tip is not indicating what is wrong. Environment ACX57xx Cause Windows 7 is inhibiting tool tips on Bang indicators. Resolution The following registry entry is used to inhibit or expose the Tool Tips on a Mouse Over Note:  Always backup the registry before making any changes. HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced Data Type: REG_DWORD [Dword Value] // Value Name: ShowInfoTip Modify/Create the Value Name [ShowInfoTip] according to the Value Data listed below. Value Data: [0 - ShowInfoTip Disabled / 1 - ShowInfoTip Enabled] Exit Registry and Reboot following changes to the registry.

Issue Pinpoint will not start. When attempting to start it, an error related to MFC42.DLL pops up.. Environment CyberStation v1.71 Cause There was likely a file registration issue, deleted file or corrupted file. Possibly see the Windows Event Log for a related entry. Resolution Uninstall CyberStation on that workstation. Delete \Continuum directory. Reinstall CyberStation. Start CyberStation and Pinpoint.