Building Automation Knowledge Base

Issue When looking at the waveforms on an Infinet bus some waves appear at an amplitude of 5 volts while other waves have a 3 volt amplitude. Product Line Andover Continuum Environment RS485 Infinet transceivers Pico scope Oscilloscope Cause Generation I controllers such as CX9900 and i1 and earlier versions of Infinet controllers are manufactured with a 4.5 volt transceivers. Generation II controllers such as the CX9680, i2 and b3 controllers are manufactured with a 3.5 volt transceivers. Resolution It is perfectly fine to wire an Infinet bus that contains both first and second generation controllers.  For more information on RS485 see General Information on RS-485 Communication.

Issue Not clear to as to which alarms can be sent out to SNMP traps. The cx controller the SNMP Alarming option is enabled on?  Subnet controllers? Other cx controllers without the options enabled? Product Line Andover Continuum Environment bCX1 with SNMP alarming enabled CX99xx with SNMP alarming enabled CX9680 with SNMP alarming enabled ACX57xx with SNMP alarming enabled Cause The documentation and ordering information is not clear as to what the SNMP Alarming option enables the controller to do. Resolution The SNMP Alarming option enables the controller to sent out its own alarms and the alarms of its attached Infinet controllers to SNMP traps. It will not enable that controller to do the same for other CX controllers on the network. For all alarms to be sent to SNMP traps, you will need to enable the SNMP Alarming option for each CX controller. Also see the articles below for more information on SNMP options and configuration. Options: SNMP Flashing options for Netcontrollers and BCXs Configuration: Where can I get information on SNMP Alarming?

Issue Need to confirm the correct part number to upgrade I/NET Do I need to pay for the I/NET software to upgrade the site? When can I use a SEAT license? What are the rules / definitions for using SEAT / SITE Licenses with I/NET? Product Line TAC INET Environment I/NET Software I/NET 2000 I/NET Seven to 2.4x Cause Confusion with part numbers and license restrictions within I/NET software offering.  Resolution  Ordering information is usually contained within each of I/NET's Product Announcements. These are found on The Exchange Download Center as well as on Software and Firmware compatibility matrix for older versions of the traditional product lines. When upgrading from a “minor” revision, upgrades from v2.40 are free. All you need is the new version of v2.4x software which can be downloaded at no charge from the Buildings Business Extranet website. To download TAC I/NET Seven software, refer to Downloads and Schneider Electric software, tools, documents, and tips. Upgrades from pre-2.4x versions (i.e. v2.3x and below) are paid upgrades. Standard upgrade prices are the same whether upgrading from I/NET Seven v2.31 or I/NET 2000. When upgrading, all host PCs must be upgraded to the same version.  Upgrade / New Ordering part number information can be found in How many software versions of I/NET Seven are there? For information that needs to be provided during the ordering process or if you have an issue with the Site License key refer to License or CD Key Issues. I/NET Seven Software Definitions Site Licenses SEVENHVAC SEVENMAX SEVENSEC Definition of a SITE: “A building or collection of buildings at single or multiple locations owned and operated by ONE end user, upon which I/NET is installed.” Seat License: SEVENSEAT Definition of a SEAT “A license for an additional PC at a SITE as defined above, irrespective of configuration i.e. Remote Client, Filemaster, Equalized Client etc.”

Issue Triggering an alarm or message if a point goes old in I/NET Product Line TAC INET Environment I/NET Cause Need to track or actively monitor points that are frequently found with an Old flag. Resolution Connect to the controller that contains the point you wish to monitor. Create an internal DA or DI point to use as a monitoring point. (Set 0 as normal and 1 as alarm) Add a Calculation extension to this point with this Calculation: OLD(P0) [where P0 is the point you wish to monitor going old] If you wish to use one point to monitor several points that may go old, simply use the OR symbol which is " | ". The expression will look like this: OLD(P0)|OLD(P1)|OLD(P2)... Results: Whenever the monitored point goes old, your internal monitoring point will change to a value of 1. Remember that the calculation only runs once every scan interval so a longer scan interval will delay your results. For further information, read I/NET Indirect Point "Old Data" Filtering Techniques.

Issue Totally remove the existing program from an ASC Product Line TAC INET Environment I/NET Seven All ASC Controllers Cause If an ASC is not working correctly, it may be necessary to replace the existing program and start over with a new database. Resolution Perform a memory clear on the ASC. See Reset the memory in an ASC Controller for detailed instructions. Reload the BIN files (UPD) to the controller. This is done by doing an ASC Update function in the I/NET editor Once the BIN files are loaded, bring the Points up to the Host PC. This is done by doing a MCI Update function in the I/NET editor

Issue Every time you compile a program object you get a message saying the "Program is not signed"   Product Line TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4 Enterprise Server Cause Tridium's Niagara N4 product will at some point in the future require code signing Resolution Create the main certificate in our Workbench to be used for signing our Program Objects. Go to the top drop-down menu on the Workbench and select "Tools - Certificate Management". Note: do not open the Certificate Management of your Platform. That is different and will be used for our running stations, not for this purpose. On the "User Key Store" tab, press "New" to create a new certificate. Fill in all the required fields. Make sure you change the "Not After" date so the certificate does not expire in just 1 year. Select the specific "Certificate Usage" as "Code Signing"   Press "OK" and set a password for your certificate. Remember: this password will be asked by the workbench at the point of compiling your code. Now select the new certificate, then press the "Export" button below   Export the certificate without the private key. You will be prompted then to give your certificate file a name and store it in your computer. We would also recommend exporting the certificate again, this time with the private key included, and storing it with an indicative name, in case you want to transfer it to a different machine. Change tab and move to the "User Trust Store". From there, press the button "Import" at the bottom and select the certificate without the private key. It should appear in green as accepted in the windows above. Go to the top drop-down menu, and select "Tools - Options" Find the "Code Signing Options" on the left-hand side, and on the "Signing Cert" section select the certificate we have just created and accepted on our Workbench. Then press OK to confirm. Open the local host Platform, and double-click the platform Certificate Management. Select the tab "User Trust Store", then press the button "Import" and select again the certificate without the private key. On the station running locally, you can now compile your code. Note that the first time the Workbench will ask for your password (the one you assigned when creating the certificate). Add the password and see that the code now compiles with no certificate error If you try compiling code on a Jace, it will return the "Certificate not trusted" until you add the certificate to the Jace Certificate Management too. On the Jace Platform, double click the "Certificate Management", then select the tab "User Trust Store". In there, press "Import" and select your certificate without the private key. Your program objects will now compile correctly.  

Issue How to configure Global I/O across controllers in Access Expert Product Line Access Expert Environment Access Expert Win 8.1 and above Version 3 Cause There are no guidelines on how to control points across controllers on a Version 3 instance. Resolution Setting up Global I/O utilizes Alarm Definitions and behaves similarly to Triggers and Procedures. The event source of the Alarm Definition is the Trigger for the action. The Alarm Action will act as the Procedure that occurs after the trigger has been activated. Example: In the example below, when the input on controller 1 is activated, the output on controller 2 will be pulsed. The Alarm Action of pulsing the output is set up on the Alarm Actions page and uses a Trigger and Procedure to Execute the pulsing of the output. If you are attempting to do Global I/O in Version 2, this feature is not supported. It will only work in Version 3. For this example, we are pulsing the output on Controller 2 from input on Controller 1 for a duration and we need two triggers to accomplish it. The following steps will describe how to configure them:    Step 1: Create a Trigger and Procedure for the Input on the first controller and assign the source accordingly.   Step 2. Create the Second Trigger on the Second Controller. Step 3: Create an Alarm Action to Execute this procedure and assign it accordingly. Step 4: Create the Alarm Definition. The Event Source is the object that will do the “Trigger”, the Alarm Action is the “Procedure” and the Event type is the triggering action for the Source. In this example, the filter query is setting this action to only occur when the input is activated instead of any input status change. 5. Trigger the Alarm and look at Hardware Status and Live Monitoring Window.

Issue Need sample PE program for control of access to a storage cage gate by forklift operators where the gate is required to stay open (up) until the forklift operator cards at the reader a second time on his/her way out of the cage. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause Continuum PE programming guidelines Resolution This sample program was provided as proof of concept only and not intended as a complete solution to the use case.   Object : StorageCageControl Type : InfinityProgram LastChange : 1/29/2020 11:29:14 AM DeviceId : PSS\ACX2.10 Alias : StorageCageContr CreateTime : 1/29/2020 9:59:56 AM CreatedBy : Root\Acc TimeLocked : 1/29/2020 11:29:14 AM InstanceId : 7003/7002 ByteCode : 'SAMPLE program for controlling access to a Storage Cage gate 1/29/2020 AM 'Program is LOOPING/AUTOSTART ' 'DESCRIPTION 'On valid access to the cage by forklift operator, program will unlock the gate using the ' PermanentUnlock property to keep it unlocked until the forklift operator indicates the gate 'can be closed by presenting his/her card at the card reader. ' 'REQUIREMENTS '1. ACX2 or NC2 controller only, program wont work in NC1 or old ACX7xx as they don't support the PermanentUnlock flag '2. Set the StrikeTime attribute of the door controlling the gate to ZERO '3. Create GateLeftOpenALM InfinityNumeric, and attach to an alarm (Optional) Numeric CloseTimeOut Line Init CloseTimeOut = 15 'Notify gate may have been left open after CloseTimeOut minutes. Goto WaitToOpen Line WaitToOpen GateLeftOpenALM = False If CageGate ValidAccess then CageGate PermanentUnlock = True Goto WaitToClose Endif Line WaitToClose If CageGate ValidAccess then CageGate PermanentUnlock = False Goto WaitToOpen Endif If TM >= CloseTimeOut then GateLeftOpenALM = True 'Gate may have been accidentally left open Line E 'oops, runtime error, wait a bit then try again If TS > 30 then Goto Init EndByteCode Status : Active EndObject

Issue What are the PinOuts for the RS-232 Connection of the older 1st Generation CX controllers to connect through Hyper terminal. Product Line Andover Continuum Environment Hyper Terminal Continuum CX Gen 1 CX9900 Continuum CX Gen 1 CX9940 Continuum CX Gen 1 CX9400 Continuum CX Gen 1 CX9410 Continuum CX Gen 1 CX9200 Cause Need to direct connect to a first-generation controller to configure its IP address and ACC Net ID. Resolution The Hyper Terminal cable needs to have the below pinouts. RJ Connector - - - - - - - - - - - - - 9 Pin RS-232 PC Controller Comm3 Pin 1 - DTR - - - - - - - - - - - - - Pin 6 - DSR Pin 2 - CTS - - - - - - - - - - - - - Pin 7 - RTS Pin 3 - CXD - - - - - - - - - - - - - Pin 1 - CXD Pin 4 - RTS - - - - - - - - - - - - - Pin 8 - CTS Pin 5 - GND - - - - - - - - - - - - - Pin 5 - GND Pin 6 - RD - - - - - - - - - - - - - Pin 3 - TD Pin 7 - DSR - - - - - - - - - - - - - - Pin 4 - DSR Pin 8 - TD - - - - - - - - - - - - - - Pin 2 - RD On the RJ connector for the controller's comm3, Pin 1 is the furthest to the left with the insert clip facing away from you and the gold teeth facing you (download drawing). For the CX9200 and CMX controllers download the pinouts here. Download Command Terminal Reference Guide here

Issue Is there a way to translate Cyberstation to a language other than English and use different SQL collation sequences and code page? Product Line Andover Continuum Environment Continuum Cyberstation Cause Standard Cyberstation installation installs the SQL using Code Page 850 1.x Strict compatibility. Resolution The link below is to the Language Translation support guides. These provide detail on how to translate the Continuum Cyberstation user interface to a different language. It also details in Chapter 3 how to use a different SQL sort order. This would allow the use of different character sets for use in personal names Language Translation Support Guide V1.81 Language Translation Support Guide V1.94 Also, there is an additional Continuum Language Support document available in MSWord format Here. For Arabic specifically, additional MSWord Document Here.  There are freelancers that can be of assistance to help with your site. Upwork is a site with potentially low-cost translators. NOTE - No testing has been done with Continuum v2.0 due to a lack of demand for translation See Andover Continuum v2.0 Language Translation

Issue For troubleshooting and information gathering database queries are useful Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Cause At times engineers and onsite techs need some queries to gather information for troubleshooting or to correct issues. Resolution Click here to download some sample read only queries

Issue Factors to consider using oBIX vs. BACnet IP to exchange data between Niagara R2 and G3 systems Product Line TAC IA Series Environment Niagara R2 version 522 and later Niagara G3 version 3.4 and later Cause Planning factors to consider as to which method is better suited for the customer Resolution Either solution has pros and cons regarding implementation. One needs to think about what fits and how much engineering is required.  If the R2 UNCs (Jaces) are nearly full (CPU and/or memory or less than 40% idle time), then oBIX probably can't be used. It requires some resources to drop in the oBIX service. But if their CPU usage is good (> 40% idle time) and the resource count isn't near the limit, the oBIX service should fit into the UNC. With oBIX, one has access to much more information in the R2 station than with BACnet. BACnet just gives access to its standard objects (BV, BO, AV, AO, etc). oBIX would provide access to just about anything in the station, though some things might be in a string format. One could get trend logs and such using oBIX.  Please also note that R2 oBIX is server only - no R2 "shadow objects" exist to obtain remote oBIX data (e.g. from a G3 station). For additional details, refer to the following documents: Niagara AX-3.x oBIX Guide Niagara R2 to Niagara AX via oBIX Engineering Notes   With BACnet IP, one would need to set all the R2 points 'Foreign Address' field for any point to be available to the G3 station.  Then, configure the G3 BACnet network, and discover the R2 devices and points (Note that if the G3 station is a supervisor, or Enterprise Server, a BACnet license feature with the appropriate number of BACnet points must be purchased).   A G3 supervisor PC should handle 5000 oBIX or BACnet points, provided the station is properly licensed.  

Issue Decreasing network performance on TCP/IP layer. Direct Connections seem to work fine Product Line TAC INET Environment I/NET Cause The network may be trying to communicate to IP addresses that do not exist Resolution Set devices to static IP Delete any old or unneeded Reference Hosts from all devices Clear Routing Tables. Both Routers (see Clearing IP address in the 527 routing table) and Workstations (see Viewing the routing tables on a PC using I/NET Seven) Use a network analyser or work with the building IT department to determine if the issue is IP Network Related Splitting Links to DLA will help remove load from routers

Issue Version incompatibility of Vista and Xbuilder generates an error. TAC XBuilder The installed TAC Vista version is not compatible with XBuilder 5.1.8 The XBuilder projects created will not be possible to use with the installed TAC Vista. Do you want to start XBuilder? Product Line TAC Vista Environment XBuilder versions compatible with Vista 5 Xenta 913 Xenta 527 Xenta 511 Cause Incompatibility of versions when XBuilder checks installed version of Vista 5. Resolution This error message is generated when launching XBuilder. XBuilder checks the installed version of Vista against its version and will generate an error if it is not the same. However, this is only an issue when the XBuilder is to be loaded into a Xenta Server. When using a NON-Xenta server i.e. a stand alone device that is simple passing values, this message can be ignored. Please refer to Xenta Server firmware versus Vista Server versions for the Xenta Server compatibility matrix with Vista Server.

Issue When graphics are updating, a PI Live Data error pops up randomly or values may not always update Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause PI Live Data is a timeout error. Pinpoint is having a difficult time accessing the data from the location it is being requested. Resolution There are a number of reasons this error can occur. Try the following steps to narrow down the issue. Review the polling settings using Continuum Graphics (Pinpoint) update interval and polling speed Verify that the points that have been linked in Pinpoint are currently assigned to points that exist in an online controller. Too many points that have been changed and that are no longer linked can cause Pinpoint to timeout. Ensure that if pages are setup to navigate from one to the other that pages are not remaining open since this will multiply the number of values being requested.  Run acctrace to determine what other processes are running on the Cyberstation at the time of the crash Remove SmartStruxure if it's installed on the same PC and see if the issue goes away.

Issue When commissioning I/A MNL800 controller in LonMaker LNS network management tool, an error will happen: One or more devices failed to update successfully, due to the following problem: "A device encountered an operational or messaging error while its configuration was being updated. (Subsystem: NS, #4031)" Product Line TAC IA Series, TAC Vista Environment Vista I/A MNL800 LonMaker Cause The issue is possibly due to more than one MNL800 controllers in the LonWorks network have the same Program ID defined in the WPT that causes the commissioning failed. Resolution Open the program of the MNL800 in WPT, right click in the blank place and choose Hardware Wizard. Click Next and modify the Program ID so that each MNL800 has unique program ID. Then it will be fine to commission them in LonMaker. There is also another method to deal with this issue. Please refer to Error: NS #4031 lcaErrNsUpdateFuncError A device encountered an operational or messaging error while its configuration was being updated (Subsystem: NS, #4031).

Issue Virtual Hand Held Controller on Windows 7 OS Product Line TAC INET Environment I/NET site Cause Virtual HHC failure when using Windows 7 Operating System Resolution Here is a work around for this issue. After doing these steps it will very slow in updating. Only click once and wait, be patient it will work at some point with the HHC buttons. NOTE: The above is unnecessary if using the "new" HHC that comes with 2.44 which also works on Windows 7 64-bit without changing any settings. HHC Setting on Windows 7 Programming a 7798C controller with a Virtual HHC Console Cable Connectivity to I/NET

Issue After purchasing Webstation for a site, it still will not work even though the license is being read by LM Tools Product Line TAC Vista Environment Vista 5 Webstation Licensing LM Tools Cause When adding Webstation to an existing network it important to know if this was a Vista 5 "Stand-Alone" license or a "Full" version. Stand-Alone Vista will not allow any connectivity via IP. The needed license feature that comes in the Full version is "Vista.Server.Network". This can be verified by opening the site license in a text editor such as Notepad. Resolution Upgrade the site to a Full Vista license that contains the needed Vista.Server.Network feature. This will allow the Webstation to connect to Vista Server. A Demo license can be used in the interim until a Vista Upgrade License can be purchased, entitled and installed on the site. More information can be found in The Vista.Server.WebApps.Access license is missing.

Issue Can not find Controller Web Server documentation on the web sites. Product Line Andover Continuum Environment Continuum Custom Web Server pages Infinity Web Server Cause Unable to find Continuum Web Server documentation. Resolution The attached Web Server chapter is extracted from a Plain English programming guide.  The Infinity Web Server User Guide is also relevant to Continuum. Also an example program can be seen in How to create custom web pages in the CX controller using Plain English.

Issue An UltiVist client workstation failed to re-start and generated the following pop-up error: SYS3175 - A program generated an access violation at 1e1b1300. FIAHAPI.DLL 0001:00001300   Product Line TAC IA Series Environment UltiVist Cause Large file sizes cannot be handled by UltiVist. Resolution On the UltiVist client: Look for the almhist.d$$ file and delete it if it's greater than 10 megabytes in size.  The file is located in the \FI directory.  On a restart of UltiVist, this file will be re-created. On the UltiVist server: Look for the WSQxx.D$$ file in the \FI\ALARMS folder (where xx = workstation number) Follow instructions in The UltiVist server is not operating properly