Building Automation Knowledge Base

Issue PE programming required to display a check list doc, report etc on specific alarm link of an object such as a door. Environment Continuum provides built in functionality to run a program when any of the 8 alarms associated with an object goes into alarm. In order to execute some actions on a specific alarm some PE programming is required. This article provides sample User Defined PE Alarm function to display a particular document depending on which of the alarm links associated with a door object is active. Cause Not known cause Resolution Configure the Cyberstation that will be displaying the doc, report etc for User-Defined Alarm Function (See Cyberstation online help for instructions on how to do the configuration). In the PEAlmFunction use code to qualify the alarm and display the doc or report that applies to the particular alarm type. -- SAMPLE CODE Arg 11 AlarmENROLL Arg 12 EventNOTIF  if EventNOTIF is not "DoorAlarm" then return 'Only looking for door alarms in this example. if AlarmENROLL = "Door Forced Open" then SHELL "C:\Temp\CheckListForDoorForcedOpen.doc" if AlarmENROLL = "Door Ajar" then SHELL "C:\Temp\CheckListProcedureForDoorAjar.doc" -- END SAMPLE CODE NOTE: The alarm function will be invoked every time any alarm comes in; in the example above all door alarms have been associated with the same EventNotification (DoorAlarm) in order to make sure the function can execute only when door alarms are reported.

Issue Can the FX-40 license be upgraded from version 3.3 to 3.5, and can a feature ("jcin2") be added to it? Environment I/A Series (Niagara) G3 Cause A branch / partner office is working with a customer building that has a FX-40 installed in it and wants to program it. Resolution Schneider-Electric cannot process the license file from a Johnson Controls FX-40 (equivalent to an ENC-410).   Both the upgrade to version 3.5 and the addition of the "jcin2" feature must be processed through JCI.

Issue A computer was installed with version 3.5.34 of Tridium's Vykon-branded Niagara AX and Schneider-Electric's TAC-branded Niagara G3.  An error appeared indicating that the core distribution files were missing. Environment Niagara G3 Workbench Cause The sw directory was missing under the 3.5.34 directory. Resolution Un-install both versions and re-install just one of them. The Vykon-branded and TAC-branded licenses files can be kept in a separate directory and swapped in-and-out as required.

Issue After an upgrade to Vista 5.1.5 the LNS port in Vista is offline and nothing is communicating. Downgrading back to Vista 5.1.4 the LNS port comes back online. Environment Vista Server 5.1.5 Cause Vista Server 5.1.5 is not communicating to the LNS server properly. Resolution Vista Server hotfix 14 addresses this error within Vista Server 5.1.5. Please use the following steps to correct this issue: Download TAC Vista Server 5.1.5 Hotfix 14 from The Exchange Download Center. Run the TACVista515HotFix51514.exe file. Reboot the machine.

Issue A GCM has lost its database and an older backup exists. The backup was done with SIGNAL software. Since then, the SIGNAL host computer was replaced. After placing a copy of the older backup in the UPLOAD directory, SIGNAL's download feature does not recognize the file. Environment SIGNAL for Windows 95/98 (version 4.4.1) SIGNAL for Windows XP (version 5.0.0) GCM-84000 series GCM-86000 series Cause The updown.dat "index" file used as reference by SIGNAL's download feature does not exist. It must contain at least one entry indicating that a backup copy of the GCM database exists in the UPLOAD directory. Resolution Even though the GCM lost its database, use SIGNAL's upload command to create a new backup copy of the GCM.  This process will create a new updown.dat "index' file and a file containing a backup copy of the GCM database.  The filename will be similar to:  UP016724.G1 Using Windows Explorer, go to the SIGNAL\UPLOAD directory and rename file UP016724.G1 to test.G1 Paste a copy of the older backup file and rename it to match the filename created in step 1 (UP016724.G1) Return to the SIGNAL desktop and perform a download.  SIGNAL will proceed to use the older backup file that was renamed. When the download is complete, review the database in the GCM with Terminal Mode to ensure all blocks are working and to make any programming changes. 

Issue What details are available on the "Condition Threat Level" feature in Continuum. Environment Continuum Cause What details are available on the "Condition Threat Level" feature in Continuum. Resolution Detailed information: Available in the "Access Control Essentials Guide" page 153 (Condition Threat Level) and 149 (Area Lockdown). This document is installed with your Continuum software on your Cyberstation. General information: To download the documents below, you must log in to The Exchange . Feature Blast v1.80 (Area lockdown support) Video support ACX Series Controller NetController II

Issue Integration of multiple Continuum databases. Environment Cyberstation Cause Unsupported configuration. Resolution DO NOT share a controller between databases, doing so will cause communications issues amongst others. Alarms can be reported to the other 'sites' via email etc but integration within the Continuum system is not possible.

Issue Further explanation on the Mifare Reader and cards as it relates to I/NET Seven Environment I/NET Seven Mifare readers and cards Cause At the present time, I/NET Seven can ONLY read the Proximity side of the card. I/NET does not support any of the read/write functions the Card Chip or the Reader Chip in the MIFARE mode can do. If you want to utilize both the Proximity side of the card and the Smartcard chip, the only Schneider Electric Product that does this is the Andover Continuum product line. Please note the Continuum product only has the read capability for the Smartcard chip and the Proximity chip. The Continuum product does not have the ability to write to the Smartcard chip. Resolution What is MIFARE? MIFARE technology is a 13.56 MHz contactless technology that is owned by Philips Electronics. They do not make cards or readers, but they make and sell the card and reader chips on the open market. Card and reader manufacturers such as HID use this technology to create unique products for use by end-users. MIFARE is often considered to be a "smart card" technology. This is based on the ability to read and write to the card. In reality, MIFARE is simply a memory card (as opposed to a processor card). The MIFARE contactless smart card and MIFARE card reader/writer were originally developed to handle payment transactions for public transportation systems. With a short read-range, MIFARE was uniquely suited to perform increment/decrement functions. Although contact smart cards could also do the job, contactless readers are faster and easier to use, and there is virtually no maintenance on the readers, or wear and tear on the cards. To date, the use of MIFARE for contactless access control applications has been limited. This is due to the short read-range when compared to the options available with proximity (125 kHz technology). Why is HID offering a card with both HID proximity and MIFARE technology in one card? Many HID customers are currently using HID proximity for access control. The customer now wishes to use MIFARE technology for cashless vending or transit. Since the customer only wants to carry one card, it makes good sense to have one card with both technologies. Likewise, many customers are currently carrying a MIFARE card for cashless vending or transmit applications. This is highly likely outside of North America. The customer is now interested in implementing an access control system using proximity. Again, the multi-technology card allows for use of a single card with multiple applications.

Issue The STR-150 Wall Module with Display is not compatible with Xenta 100 controllers that are earlier than SW-version 1.2. The space temperature (nvoSpaceTemp) is displaying an invalid or default value (either 621.81 degrees Fahrenheit or 327.67 degrees Celsius). In newer versions of Vista the value will display "Invalid Value". Product Line TAC Vista Environment STR-150 Xenta 101-VF Xenta 102-ES Xenta 103-A Xenta 104-A Cause Software for Xenta 100 series controllers previous to version 1.2 is not compatible the STR-150 wall module. Resolution The STR-150 is only compatible with Xenta 100 series controllers that are software version 1.2 or later. If a wall module with display is required for a Xenta 100 controller with software that is older than version 1.2 there are two possible solutions: An identical Xenta controller can be purchased with the latest software version to replace the old controller. An STR-350 stat can be used and connected to the Xenta controller via SNVT bindings.

Issue STR-250 Wall Stat displaying °C instead of °F Environment Xenta 102-AX M/STAT MR-VAV-AX I/NET Vista Cause Device is set to incorrect Engineering Units Resolution Plug the M/STAT into the jack on the thermostat.  The initial display shows the set temperature. Press the Service button.  This prompts you to enter the service mode password.  Default password is 183.  Use the +/- keys to set each digit and the enter key to submit.  If the password is incorrect, the display will blink. If the password is correct, the first menu option – Unit Parameters (UP) – is displayed.  Press enter. Hit the select button until Engineering Units (EU) is displayed.  Press enter to view the current value. Use the +/- keys to change the value between Systeme International (Si) and Imperial Units (iu), press enter. Press the service key to escape out of the menu.  If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT.  Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue Is the LCMA-103 (UIO board) interchangeable with the GCMA-106 (SIO board)? Environment LCM-84110, LCM-84210, LCMA-103 GCM-84111, GCM-84121, GCM-84211, GCM-84221, GCMA-106 Cause Not applicable Resolution No, the LCMA-103 is not interchangeable with the GCMA-106.

Issue The Curve Fit Object not functioning in MNB / MNL controllers.  Its output always reads ‘NA’ regardless of the input. Environment MNB controllers (all versions), MNL controllers (all versions) Cause N/A Resolution 1. Open the Curve Fit object’s properties in WorkPlace Tech 2. Change Data Point values “X1’ and “Y1” from “0” to “1” 3. Compile and download the application to the controller 4. Reopen the Curve Fit object’s properties in WorkPlace Tech 5. Change Data Point values “X1’ and “Y1” from “1” back to “0” 6. Recompile and download application to the controller again An additional alternative is to use non-zero values for Data Points "X1" and "Y1" (e.g. 0.01). The curve fit object should function correctly now. 

Issue Handle id limits on Continuum controllers. Environment All master level controllers (bCX, CX) All b3 controllers All i2 controllers Cause Handle id limits on Continuum controllers. Resolution Field controllers have a total limit of 255 objects, approximately 50 of them are reserved for system variables and other system objects, leaving approximately 200 that can be user created in the field controller. All IP level devices in the Continuum line follow the handle specifications of the Continuum protocol. This includes the BACnet devices such as the bCX-4040. Handle numbers for most object types (including all BACnet types) are in the range 7,000 to 65,535. That allows for 58,536 objects, which is more than the memory can hold. Continuum style alarms (not BACnet alarms) have handles in the range 1,000 to 4,999. Controller will run out of memory before it runs out of handles.

Issue When downloading a controller in the Vista System Plug-in, messages are received saying the System Plug-in is waiting for the controller to restart, but this never completes successfully. This message may be shown many times. Environment Vista System Plug-in LonMaker Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause There may be several different causes including communications errors or a corrupted application. However, by taking the controller offline in LonMaker, any extraneous interaction with the controller is temporarily ignored during the download. Resolution First, please double check the Vista ToolPack version that is installed, and make sure the version matches TAC Vista Server version. If not, please uninstall the Vista ToolPack and install the correct version of ToolPack. TAC Vista ToolPack can be download from Extranet (Software and Firmware > Engineering Tools). In LonMaker force the controller's neuron chip into a configured, bypass mode: Right-click the controller and select "Manage" In the LonMaker Device Manager window click "Offline" Download the controller in the Vista System Plug-in. In LonMaker set the controller's neuron chip back to configured, online mode: Click "Online" in the LonMaker Device Manager window then close window

Issue Duplicate Infinet ids can result if previously configured i1/i2 device is connected to field bus after power up. Environment All i1 and i2 devices. Cause Duplicate Infinet ids can result if previously configured i1/i2 device is connected to field bug after power up. Resolution When an Infinet device with an assigned Infinet id comes up before it joins the Infinet token passing it performs a self test routine that detects whether its id is already in use, in which case the device rolls its own id back to factory default (zero) and stays off the bus until commissioned. In order to make sure the duplicate id detection works, the device MUST be connected to the Infinet BEFORE it is powered up.

Issue Resizing the drawing from 11"x17" to 17"x22" just enlarged the size of the objects.  No additional space was available for more objects. Environment WorkPlace Tech Tool software (any version) Supported version of Microsoft Visio Cause Changing the Visio "Printer Paper" size does not resize the WPT drawing page size. Resolution Both the Device Definition page and the Background page needs to be resized and the resizing is a two step process. Select "Background" tab From File menu, select "Page Setup" Click "Page Size" tab - this window shows current drawing page size Select the desired drawing page size either by selecting a pre-defined size or a custom size.  We distribute our pre-defined application files with the page size set to 25% oversize (for printing on 11x17 paper) -- custom size 13.75" x 21.25" Click "Print Setup" page and select your printer paper size in the first field (we use Tabloid (B) 11in x 17in) In the Print Zoom section of the window, select Fit to 1 across x 1 down Click OK to save the settings and close the window. Select "Device Definition" page and repeat steps 2 through 7 on that drawing page. If there are any other pages in the application drawing, such as custom object pages, repeat step 8 (including 2 through 7) for each of those pages.  

Issue "Windows 7 displays .NET 2.0 Not Installed" error when launching Pinpoint graphic in Webclient. When trying to open a Pinpoint graphic in WebClient, Windows 7 notifies me that .NET 2.0 is not installed even though .NET 2.0 is installed on the client machine, .  I have set the Windows 7 User Account Controls Setting to never notify but this has made no difference. Environment Continuum WebClient Windows 7 .Net User Account Controls Settings Cause Windows 7 in not presenting the notification that it wants to install software on the client machine. Windows 7 User Account Control Settings notification level set too high.   A reboot of the Windows 7 workstation is required in order to apply changes made to User Account Control Settings Resolution Change Windows 7 User Account Control Settings level Never Notify.    Reboot the PC Once the first graphic has displayed successfully the notification level can be increased and future graphics will launch successfully.

Issue LON communications not working and error in Application Director: Error initializing LonNetwork javax.baja.LonWorks.LonException: Unable to initialize local lon port {Lon1} Environment G3, ENC, niagara Cause Typically this indicates a hardware issue with the neuron in the ENC. Resolution Open the platform for the ENC and use the Commissioning Wizard to commission the ENC again and see it if recovers.  If error remains the unit must be replaced.

Issue Trying to add AMT filters and after configuring all the details for the filter, the windows closes but the new filter is not added to the list.  No errors are given. Environment I/NET Seven 2.40 Cause At this stage the actual cause is not known, it has been found on some site installations particular to this version. Resolution Upgrade to I/NET Seven 2.40a or above.

Issue Error message of "default port unable to find object in the DB" from InfinityProgram objects when trying to export the controller to a dump file backup by performing "Send To" --> "Text File" from workstation. Environment Continuum Workstation (LAN & SU) NetController (CX99xx, CX96xx, CX97xx) InfinetController (i2xxx , i1 controllers) Cause The controller was created by importing a dump file created from different system DB or by importing a dump file from a different type of controller followed by poor/incorrect modification. Resolution Recreate the InfinityProgram object again manually as below. Copy the source code of the InfinityProgram in a text file. Delete the InfinityProgram from Continuum. Create a new InfinityProgram with the same name. Paste the source code from the text file into the InfinityProgram editor, save the InfinityProgram.