Building Automation Knowledge Base

Issue The default font size in the TGML Graphics Editor is 15. Can this value be changed? Environment TAC Vista - TGML Graphics Editor Cause Default Font Size in TGML Editor is 15 and it is hard coded in the software.  Resolution It is not possible to modify the default font size. When we change the font size, the TGML editor automatically remembers the last value used.

Issue When doing a LON interface to a third party device the Lon Link Manager displays some links with a status of “service type error".  This has been reported specifically with York and Field Server devices but can occur with other manufacturers as well. Environment G3 (Niagara) ENC, R2 UNC Cause The default service\link type in R2 and G3 is “standard”, but some third party devices require one of the other types. Resolution Typically the service\link type cannot be changed in the third party device so the default service\link type for the SNVT(s) in question must be changed in the R2 or G3 interface.  Reference the R2 LonWorks Integration Guide chapter 8 "Link Manager" or G3 LonWorks Guide chapter 3 "About Lon Link Manager" for details on changing the service\link type.  

Issue Can the Loytec L-VIS be used in a Vista Classic scenario? Environment Loytec L-VIS Cause The need to have a touch screen interface to a Vista Classic network. Resolution The L-VIS cannot be used in a Vista Classic system because it uses SNVTs to interface the Lon. LNS must be used. A solution to a Vista Classic scenario would be to touch screen PC or tablet to interface the graphics in an Xenta Webserver (5xx,7xx).

Issue Is there any support with Niagara R2 or G3 for Apple devices (iPod, iPhone, iPad)? Environment I/A Series R2 and G3 (all versions) Apple iPhone, iPad Android Cause Mobile device apps do not currently support Java script, and third party versions have not been validated by Tridium.   Resolution There is currently no support for the use of Apple devices with Niagara R2 or G3.

Issue Triggered an alarm for a Xenta 121 if the space temperature is too high or low from the setpoint. Environment Xenta 121-FC Xenta 121-HP Zbuilder Cause The Xenta 121 controller has a low spacetemp and a high space temp alarm. These alarms are triggered for the following reasons: Low Space temp alarm - In heating mode when space temperature is lower then Setpoint - nciSpaceTempDev High Space temp alarm - In Cooling mode when space temperature is higher then Setpoint + nciSpaceTempDev These alarms can be monitored here: Low Space temp alarm - nvoSystemStatus bit 13 High Space temp alarm - nvoSystemStatus bit 14 Resolution Specify the nciSpaceTempDev by using the ZBuilder plug-in and accessing the Configuration page. On the Lon\Node screen the Space temperature deviation is editable. The default value is 3.6 deg F or 2.0 deg C. Use a value that will not trip the alarms erroneously, but still warn if there is a problem.

Issue How to Set Up BACnet Enabled ABB Variable Frequency Drives for Use With Continuum Product Line Andover Continuum, Other Environment ABB Variable Frequency Drives Continuum Cause ABB VFDs must wired and configured properly to be used with a BACnet Continuum network. Resolution When wiring an ABB drive up to the Continuum BACnet MSTP network make the following connections: Terminal X2 Type (+) (-) Reference Drive Only 29 30 31 Bypass 27 28 29  ABB recommends that when using a two conductor cable with shield that the shields not be connected  to any pin (Note that pin 29 would be unused) but simply connected together with a wire nut. However, they do say that the shields can be connected to pin 29 if the drive communication is intermittent.  If the ABB drive does not have an E-Clipse bypass (E-Clipse is the ABB brand name for the bypass portion of the VFD) use the following settings:  Parameter  Setting Notes 9802  BACNET  Sets the communications protocol of the VFD. 5302  MAC ID Create a unique ID. A good practice is to set this to the Infinet ID + 1000. For example, if the Infinet ID is 5 then set this to 1005. 5303  Baud Rate  Set the baud rate being used on your BACnet network. 5311  Device Instance ID                   This is the Infinet ID and should be set to an available number between 1-127. This will display as a hexadecimal value in the BACnet side of Cyberstation. 1001  COMM  Set this if you want to start & stop the VFD over BACnet. 1103  COMM  Set this if you want to control the drive speed over BACnet. 1604  COMM  Set this if you want to reset VFD faults over BACnet. If the ABB drive does include a bypass the following settings must all be entered (notice that 5302 and 5311 are now specific to the VFD portion of the unit whereas the 5002 and 5011 are specific to the bypass portion) All of these parameters as well as the parameters listed above must be entered at the bypass. Parameter Setting Notes 5302  Drive MAC ID  Create a unique ID specific to the VFD. 5311  Drive Device Instance ID  This is the Infinet ID specific to the VFD. 5002  Bypass MAC ID  Create a unique ID specific to the bypass. 5011  Bypass Instance ID  This is the Infinet ID specific to the bypass. NOTE If the ABB drive is ACH550. Then the parameter below need to be set as a minimum. Other points will also need to be set depending on your site requirements, but the ones below will get communications up and running    Parameter  Setting Notes 5301   x5xx -This parameter indicates the active protocol and its revision. It should read x50xx if BACnet is properly loaded. If this is not the case, confirm that drive parameter 9802 = BACNET (5). 5302  MAC ID -This parameter sets the drive’s BACnet MS/TP MAC ID. A temporary value of 0 places the protocol channel in reset. 5303  Baud Rate -Set the baud rate being used on your BACnet network. 5304 Set to 0 -This parameter sets the BACnet MS/TP character format as follows: 0 = 8N1 1 = 8N2 2 = 8E1 3 = 8O1. 5311 EFB PAR 11  - Instance ID part1 This parameter, together with parameter 5317, EFB PAR 17, sets BACnet instance IDs: • For the range 1 to 65,535: This parameter sets the ID directly (5317 must be 0). For example, the following values set the ID to 49134: 5311 = 49134 and 5317 = 0. • For IDs > 65,535: The ID equals 5311’s value plus 10,000 times 5317’s value. For example, the following values set the ID to 71234: 5311 = 1234 and 5317 =7 5317 EFB PAR 17  - Instance ID part2 This parameter works with parameter 5311 to set BACnet instance IDs. See parameter 5311. 1001  COMM -Set this if you want to start & stop the VFD over BACnet. 1103  COMM -Set this if you want to control the drive speed over BACnet. 1604  COMM -Set this if you want to reset VFD faults over BACnet.

Issue Workstation is alarming that the SQL has reached the 4G limitation, but the Version of SQLServer is a Full version which is unlimited in size. SQL should be able to grow until the hard drive capacity is reached. There seems to be normal functionality of the SQL Server and there are not any $queues building. Environment SQL Vista 5 Cause When Vista is installed, The parameter how large SQL can be is written into the properties of $Backup_LDB. If a Free version of SQL is used, such as the one included in Vista, A limit of 4G or 3820MB is written to this Value. Even if you Install a Full Version of SQL at a later date, this Alarm Limit will remain. Resolution In Workstation, select the Vista Server, this displays the contents of the Vista Server in the Main pane. In the Main pane, double-click on the object $Backup_LDB, this displays the properties of $Backup_LDB in a new window. In the $Backup_LDB property window, Scroll to the last property, "DB Size Alarm Limit (MB)" Increase this value to a higher logical value of your choice considering limitations of the system hard drive space. Note: 1 Gb = 1024 Mb, 1 Mb = 1/1024 Gb and 1 Mb = 0.0009765625 Gb

Issue Creation and testing of a Scheduled Action to retime the Sigma controllers. Environment Sigma Scheduled Actions Retiming controllers. Cause The Scheduled Action to retime Sigma controllers does not appear work. Resolution Create the Action to Retime the Sigma controllers. 1 - In Sigma Setup, select "General - Scheduled Actions - Actions". 2 - Highlight "Actions" and select "New". 3 - Give the Action a title, "Retime Controllers" for instance. 4 - Highlight the new action, and in the "Select Required Actions" window select, "Retime Devices". Save the changes. Create the type of schedule you require. 1 - Highlight "Daily" and select "New". 2 - Give the Schedule a title, "Retime Controllers" for instance. 3 - Highlight the new schedule, and in the "Actions" window select, "Retime Controllers". 4 - Select the Days / Times you require, and save the changes. Testing the operation of the new "Retime Controllers" schedule. 1 - Allow the system to operate normally and then confirm that the controller retime has taken place, by using the "Transaction Logging", or by checking the controller times, to confirm this. OR 2 - Manually change the PC Time / Date to confirm that the schedule operates correctly. If using this method then make sure that the PC clock is allowed to pass through midnight automatically. An example of this, would be to set the controllers retiming to take place at 00:05 and then set the PC clock to 23.55. This ensures that the PC time passes through midnight, before the "Scheduled Action" is run at 00:05.

Issue What X Drivers are available? Environment All Continuum controllers that support X Drivers (XDrivers) 3rd Party interfaces Cause How to find out what standard X Drivers are available to integrate with Continuum controllers. Resolution The Third Party Communicates Interface and Protocol Brochure can be found on The Exchange Download Center that lists all available X Drivers and product compatibility. Also all of these listed drivers are available for download from The Exchange Download Center here for use on X Driver enabled controllers. Should a new driver development be required, or other special interface; then you can contact the team that develop X Drivers: Adam.Summers@Schneider-Electric.com You will need to provide protocol details if you require a quotation.

Issue Customer has a specification requirement to be able to open and edit MNL or MNB controller application files via a link on the associated I/A Series (Niagara) G3 graphic screen. Environment I/A Series (Niagara) G3 ENS Server Cause Specification issue. Resolution A WorkPlace Tech application file can NOT be opened automatically via a I/A Series (Niagara) G3 graphic link for the following reasons: Workplace Tech does not have a provision for opening an application file from the command line. The WorkPlace Tech Tool software would have to be installed on each computer that needed to open an application. The WorkPlace Tech Tool software would need a separate license for each computer on which it is installed. There are no provisions for centrally managing a shared WorkPlace Tech application library. A WorkPlace Tech application CAN be viewed via the Visio Viewer application.  This can be performed via a graphic link provided that the Visio Viewer application is already installed on the computer being used to view the application file.

Issue Cannot connect to a Network Share with Pinpoint Graphics. Environment Continuum 1.93 Windows Server 2008 Windows 7 IIS Cause Due to enhanced security by Microsoft a Domain Service Account needs to be applied to IIS for the share. Resolution Open IIS Management Create a  Virtual Directory Enter the name "New Graphics Files" Enter the path   \\servername\sharename Click on "Connect as" Enter Service account name and password. Notes* Service account should be a member of the Backup Administrators group.

Issue Plug-in will not launch. Results in error "Active X: could not create object" Environment Windows 7 32 bit Windows Vista NL220 LonMaker Vista Plug-ins Cause Needs to be run as an administrator. Resolution Verify Administrator account is logged in. Install Toolpack (or hotfix) as administrator Take note of the installation location, and go to this folder after the installation of the hotfix. The default location for these plug-in application files is: C:\LonWorks\apps\TAC Run file: TACXenta102AXPlugIn.exe, as administrator and click Deregister Plug-in, then Register Plug-in. Open NL220 or LonMaker and register the Xenta 102-AX plug-in.

Issue Receiving a RPC error when switching to another graphic in webClient. Environment Windows 7 Continuum 1.93 Windows 2008 Server Cause Windows Defender is running on Client systems. Resolution Open Control Panel Select Administrator tools Open Services Disable Windows Defender

Issue Can not enter the unlock code in WorkPlace Tech Purchasing Software, the “Unlock” button is grayed out. Environment WorkPlace Tech Tool software, release 5.7 or newer Cause WorkPlace Tech Purchasing Program was not properly closed after the codes were generated.  The Purchase program was closed using the “X” button, not the “Done” button.  Registry and file information does not get saved to the computer when the purchase program is closed using the “X” button. Resolution Re-run the purchasing program and select the same options. This time close the purchasing program using the "Done” button, not the “X” button.

Issue How to view the current Priority level controlling a BACnet object using Plain English. Environment Continuum Cyberstation BACnet AnalogOutput, AnalogValue Cause 3rd party is controlling a BACnet object at an unknown priority level. We want to see what the current Priority level is and relinquish this control. Resolution We can use the PriorityArray attribute to view the value of each Priority level. Then using a For loop we can loop through all 16 priority levels to determine the current priority level controlling the BACnet object. Below is a program that will allow you to see the current priority (aaPriorityValue) controlling your object (PriorityTest) and at what priority level (aaPriorityIndex). You will need to create two numerics (configure as AnalogValue) for this program to work (aaPriorityIndex and aaPriorityValue). With the method below we can see if a non-zero value is the current priority and at what priority level.  Unfortunately a 0 value is seen the same as a NULL value (both seen as 0), so if a 0 value is currently controlling the object we are unable to determine at what priority level this is set. If aaPriorityValue is 0 and aaPriorityIndex is < 16 then we know that aaPriorityIndex is the level of the non-zero value and can relinquish all priorities down to that level if needed. Still not exactly what we want but it does give a bit of flexibility to actually control the current priority level. ======================= ' Program to get the highest priority value and its index number ' Flow: Looping Numeric count Numeric PriorityValue CALC:   For count = 1 to 16   'Loop through the priority array, looking for the first non-Null value     PriorityValue = ReadProperty(PriorityTest PriorityArray, count)     If PriorityValue is not NULL then       Break 'stop at the first non-Null value. Side effect, also first non-zero value     Endif   Next count   If PriorityTest = 0 then 'Check for 0 value     aaPriorityValue = 0     aaPriorityIndex = count   Else 'If not 0 or NULL value, set current priority value and index     aaPriorityValue = PriorityValue     aaPriorityIndex = count   Endif =================================  

Issue What is the maximum size you can set the EventLogSize in a Continuum Access Controller? Environment ACX5720 ACX5740 CX9900 Netcontroller II Cause The default setting of the EventLogSize system variable is 1,000, how much can I increase this by? Resolution The EventLogSize system variable determines how many Event log entries that a controller will buffer; if it ever loses Ethernet communications to the workstations. So is only utilized during a network failure. Typically the default 1,000 is sufficient for most projects, but this figure can be increased depending on the available Freemem in the controller. So the more personnel, doors and other objects created in the controller the lower the max value that can be entered in EventLogSize. Each event will use 68 bytes from the Freemem value of your controller, so by checking the available Freemen you can calculate the maximum size of EventlogSize that can be defined. However never use all the available memory from a controller, always leave a few thousand bytes of Freemem for future use. Typically the value can be increased to over 100,000 on most configurations if so required.

Issue Each Cyberstation has a path to pinpoint graphics and the graphic file could be different on each Cyberstation. A way is needed to access and update one set of pinfiles. Environment Continuum Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Configuration is needed to allow updating and accessing one set of pinpoint files. Resolution Share a folder (Microsoft sharing and permissions) on one Cyberstation or Server that will contain the Pinpoint graphic files (including backgrounds and images) Copy all edited pinpoint and graphic files needed to the shared folder Go into Pinpoint on each Cyberstation and go to the View > Options Edit the Graphic, Image and Background paths to point to the shared folder. Once there are not Red Xs, the path has resolved and pinpoint will then use that folder for its graphic files on that Cyberstation

Issue A Niagara R2 UNC has been operating for more than two years communicating with ASD devices.  Recently, the station stopped polling them without any external influence.  The ASD devices remain online and operational but the UNC station stopped polling them.  A reboot of the UNC resolved the issue.  What caused it? Environment Niagara R2 UNC-520, version 522 or older Cause An issue related to a timer rollover event caused the UNC system time to stop updating if the UNC has not had a reboot in 2.26 years.  This, in turn, stopped the ASD driver from polling since it relies upon the system clock. This issue affects other drivers as well. Resolution The short-term solution is to reboot the UNC before 2.26 years (or 828 days). The ideal solution is to upgrade to version r2.301.529.  The polling issue was fixed in this version.

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.