Building Automation Knowledge Base

Issue What personnel attributes are exposed to Plain English in the controller, which work for elevator access control? Environment CyberStation ACX controllers CX controllers with AC-1 family Cause What personnel attributes are exposed to Plain English in the controller, which work for elevator access control? Resolution DepartmentCode is the only personnel attribute in Continuum that works well in a small elevator application. There are some sample PE files on The Exchange Download Center. Once you get beyond a few floors and cabs with varying access for cardholders it is unmanageable. Use the Continuum Reports Elevator Control Add-On.  Learn more about Andover Continuum Elevator Control Features.

Issue If a controller will be offline for an extended period of time, is there a way to make it not show up in the Alarm View as offline? Environment CyberStation Network level controllers (CX, ACX, bCX) Cause If a controller will be offline for an extended period of time, is there a way to make it not show up in the Alarm View as offline? Resolution Edit the controller and on the general tab select the "Out of Service" checkbox. This sets the "To State" in the Active Alarm View to "Return to Normal" and the Value to "Out of Service". It also relieves the workstations from the task of probing and looking for a response to a probe until the out of service flag is removed.

Issue What are the differences between the Niagara G3 ENS-UNL, ENS-LMT-100 and ENS-LMT-3? Environment Niagara G3, Workbench all versions Cause The Enterprise Network Server datasheet does not indicate these part numbers and their differences.  Resolution - ENS-UNL (formerly ENS-1) Enterprise Network Server (ENS) with support for connection to Unlimited Enterprise Network Controllers (ENC). - ENS-LMT-100 Enterprise Network Server (ENS) with support for connection to 100 Enterprise Network Controllers (ENC). - ENS-LMT-3 (formerly ENS-LMT) Enterprise Network Server (ENS) with support for connection to 3 Enterprise Network Controllers (ENC). Note: All ENS includes Workbench as standard. - ENS-LMT-100-UP Upgrade from ENS-LMT-3 to ENS-LMT-100 - ENS-LMT-UNL-UP Upgrade from ENS-LMT-100 to ENS-UNL Upgrade of controller limit from 3 to no limit requires purchase of both upgrade parts. * Upgrade of controller limit from 3 to no limit requires purchase of both upgrade parts.  

Issue This issue has been seen Modbus TCP between I/A Series G3 ENC and Eaton PXM meters where the PXM does not respond to the ENC within the message timeout period.  The ENC discards the request and sends a new message with a different transaction ID. The Eaton PXM meter responds using the previous transaction ID causing the ENC to discard the message and generate an error. Environment I/A Series G3, ENC-410, ENC-520 Cause Transaction IDs become out of sequence. Resolution The driver now recognizes that the device is responding out of sequence and resets the session with the device. Upgrade ModbusTCP module to revision 3.5.34.1 or newer. 

Issue Customer wants to email alarms from standalone CyberStation. IT dept will not allow use of corporate Exchange Server. Partner added MS Exchange and MS Outlook to the PC running CyberStation. Outlook can send email but CyberStation will not send email alarms. Environment Standalone CyberStation v1.93 MS Exchange and Outlook Cause With MS Exchange and MS Outlook on the PC running CyberStation, CyberStation will not send email alarms. Resolution After confirming and reconfirming that the email setup was "by the book" but CyberStation still would not email alarms, the partner moved CyberStation and Outlook to another PC and left MS Exchange on the first PC. Emailing alarms is now working fine. We do not know definitively that all three cannot reside on the same machine, but it looks that way.

Issue Continuum is configured with a separate Continuum Network for each time zone.  However, when a workstation in one time zone sets the time in a controller in another time zone to the current time, the UTC offset does not adjust the time by the number of hours difference between the two zones. Environment Cyberstation Time Zones Continuum Networks UTC Time Synchronization Cause Need to synchronize controller times across multiple time zones. Resolution The local time for controllers in each Continuum network must be set by a workstation program.  Controller times are set on each Continuum Network by setting the time in the Infinity Controller with the lowest ACCI ID.  This is done using a Plain English program in the workstation.  All other Infinity Controllers will automatically synchronize the time and date to the controller with the lowest ACC ID. If the workstation and the Continuum Controller are in different time zones, the program must compensate for the time difference by calculating the controllers local time from the workstations local time.   This does not happen automatically. This is because the value that is being set in the controller is the system variable that represents the controllers local time and date, and not some external time and date.

Issue Getting error for Weather Server:  ERROR [19:32:28 06-Sep-11 EDT][http.proxy] Error resolving www.weather.gov java.net.UnknownHostException: www.weather.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:369)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.net.BHttpProxyService.get(BHttpProxyService.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getAdvisories(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) WARNING [19:32:29 06-Sep-11 EDT][weather] Unable to load advisories for zone MIZ061 java.net.UnknownHostException: www.weather.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:360)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.naming.BIpHost.openSocket(BIpHost.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getFeed(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.advisory.BNwsAdvisoryAlarmExt.getAdvisories(BNwsAdvisoryAlarmExt.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) ERROR [19:32:29 06-Sep-11 EDT][http.proxy] Error resolving www.nws.noaa.gov java.net.UnknownHostException: www.nws.noaa.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:369)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.net.BHttpProxyService.get(BHttpProxyService.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) WARNING [19:32:30 06-Sep-11 EDT][weather] Updating current conditions failed for WeatherReport java.net.UnknownHostException: www.nws.noaa.gov - Authoritative Answer Host not found    at java.net.InetAddress.lookupHostByName(InetAddress.java:360)    at java.net.InetAddress.getByName(InetAddress.java:221)    at javax.baja.naming.BIpHost.getInetAddress(BIpHost.java)    at javax.baja.naming.BIpHost.openSocket(BIpHost.java)    at javax.baja.net.HttpConnection.connect(HttpConnection.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java)    at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java)    at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java)    at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java)    at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated)    at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java)    at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java)    at javax.baja.sys.BComponent.doInvoke(BComponent.java)    at javax.baja.util.Invocation.run(Invocation.java)    at javax.baja.util.Worker.process(Worker.java)    at javax.baja.util.Worker$Processor.run(Worker.java)    at java.lang.Thread.run(Thread.java:823) Environment Niagara G3, Workbench all versions Cause No address entered for DNS or IP Address incorrectly entered. Resolution Configuration for the DNS is located under the ENC/ENS Platform.   Open the Platform Select TCP/IP Enter the IP address for the DNS in the DNSv4 Servers slot and save changes. The network administrator should be able to provide the correct DNS address.

Issue I/A Series R2 Enterprise Server station is unable to connect to the SQL database The following errors are seen in the Enterprise Server station's Standard Output: ERROR: Could not open database connection [/SQL2005/services/DatabaseService] java.sql.SQLException: Charset 0x0904D00031/Cp850 is not supported by the JVM. "The program can't start because MSVCR71.dll is missing from your computer. Try re-installing the program to fix this problem." Environment I/A Series r2.301.529 SQL Server 2005 Java Runtime Environment 1.6 Cause JRE 1.4.1 which I/A Series R2 uses does not know how to support the CP850 character set. Even though the computer has been installed with JRE 1.6, I/A Series R2 is still using JRE 1.4.1. Resolution To enable I/A Series R2 to use JRE 1.6, follow these steps: Download and install JRE 1.6 if it has not been already installed. The latest version can be found here http://www.java.com/en/download/manual.jsp. Go to Windows Services and stop the Niagara service. In Windows Explorer, go to \niagara\r2.301.529\nre\ and rename the 'jre' folder to 'jreold'. In Windows Explorer, go to C:\Program Files\Java (this is typically the path of the Java install). Copy the 'jre6' folder including its contents and paste it to the \niagara\r2.301.529\nre\ directory. Rename the 'jre6' folder to 'jre'. In Windows Explorer, go to \niagara\r2.301.529\nre\lib and open the 'nre.properties' file using a text editor program (eg. Notepad). Comment out the 'java.options...' parameter. Add the parameter shown below, save and close the file. Start the Niagara service and run the station. Check in the Standard Output window to see if the error has been cleared and that the DatabaseService has successfully connected to the SQL database. ######################################################## # # File:  nre.properties # #    NRE properties # # Revision History #   21 Aug 03   Brian     Original version. # ######################################################## # Virtual machine to use: jview|hotspot vm=hotspot #vm=jview                       # List of Java options to pass thru to the VM (hotspot only) # Used with original install 1.4.1 # java.options=-Xmx1024MB # List of Java options to pass thru to the VM (hotspot only) # USed with 1.6 java -Xmx1G   Notes: This solution can be applied to a similar error but with a different charset encoding error other CP850. You may encounter the following error when you try to run WorkPlace Pro after performing this fix. "The program can't start because MSVCR71.dll is missing from your computer. Try reinstalling the program to fix this problem." To resolve this, go to \niagara\r2.301.529\nre\jre\bin and locate the file MSVCR71.dll. Copy this file to the C:\WINDOWS\system32 directory.

Issue Values are not refreshing automatically in Screenmate Environment - Screenmate - TAC Vista Cause The Automatic Refresh does not apply to Screenmate, as such values will not automatically update.  This feature only applies within Webstation. Resolution To get the latest values you must manually refresh Screenmate, as the Automatic refresh setting does not apply to this object.

Issue Need a way to see if the Xenta server is overloaded. Environment Xenta Server 5.1.6 Xenta 511, 527, 701, 711, 721, 731, 913 Cause Need a way to see if the Xenta Server is overloaded. Resolution Below are some commands to use via the serial port in HyperTerminal to check if the Xenta Server is heavily loaded. Type sprof a 50 Wait 50 seconds Type ps all Processes that have used the CPU in the device during the past 50 seconds are shown The first process in the list (n/a) is the idle process. In the example below, that rt(%) is 86.915%. That means the load for the processes in this list has been 13.085% for the last 50 seconds. But then we need to add the processes which is not included in the list. In the bottom of the page it is written SumCpuUsage if this is for example 95% then 5% is used to something else which is not included in this list. That means that the total CPU usage during the last 50 seconds is 13.085%+5%= 18.085% dsh/>sprof a 50 dsh/>ps all Timer: 1513732615 Profiling: Passive TaskSwitch: 28556  ProcessName   pid pri rt(us)   rt(%)  semaphore stackusage   n/a          0   0   43917288 86.915 - 0       50

Issue What schedule attribute can be used to get the Next Occupancy Time & Next Unoccupancy Time on my graphics? Environment Continuum CyberStation PinPoint Schedule Cause Need to display a schedules Next Occupancy Time on a PinPoint graphic. Need to make a calculation using a schedules Next Occupancy Time in a Plain English Program. Resolution For a Continuum schedule those values will be accessible via the date times that are attached to the Occupancy Time  and UnOccupancy Time fields in the schedule. These fields update with the next time when the current occupancy period expires. The "TimePiece" Plain English keyword can be used to extract the different parts of the Date time value i.e. the Month, Hour etc. See Online help for formatting.

Issue Vista 5.1 License Packages Product Line TAC Vista Environment Vista 5.1 Licensing Cause The TAC Vista software is modular and each function can be purchased separately. For convenience we have bundled modules into various packages: Standalone, Standard, Manager, Professional and Enterprise. Resolution The table below describes the contents of each licensing package. Product Packages Standalone Standard Manager Professional Enterprise Workstation X X X X X Graphics Editor OGC       X X Graphics Editor TGML       X X Report Generator     X X X OPC Tool           IPCL Editor           Central IPCL Editor           Database Generator           I/NET Integrated           I/NET Security           Menta 5.1       X X XBuilder 5.1       X X ZBuilder           Vista Server X 1 X X X X OPC Client           System 7           Webstation3         X 2 ScreenMate3           Limited server. Server-to-Server network and ability to be used with Webstation and ScreenMate is disabled. Three Client Access Licenses, CALs (000882711). See product datasheet for part. nos. for various Client Access Licenses, CALs.

Issue Procedure to replace EPROM when doing an upgrade. Environment All versions of I/Net software using Access Control on DPU 7910 and EPROM version of the  DPU 7920. Cause Upgrading the software and hardware on a system which work with each other. Resolution The following steps should be followed to ensure that the devices do not get damaged during the process of the upgrade: Remove power form the device Carefully remove the Eproms using the appropriate tools Replace new EPROM with correct orientation (notch on the chip) Power up the device again and hit the reset button. Verify that the transmit and receive lights are on and communications to the MCI has been re-established. Read a card and verify that the transactions are coming into AMT.

Issue Running Server/Client on a system Environment I/Net Seven version 2.13 and above. Cause Server client on a system that is running on different versions and not working. Resolution For Server/Client to work on a system, I/Net has to be installed on all the PCs and they all must be the same version as well. The following steps needs to be followed to configure this correctly: The Host PC that will be acting as the Server must have the current database. Modify the active profile in the Configuration Editor In the WorkStation Options, set this to be Standalone On the other PCs, this would be set to Remote Client An editor will come up stating the "the database will be replaced" Click on the proceed button to connect to the Server. Once completed, the client PCs would now be looking at the Server

Issue MN-LCD Uploading Environment Micronet LCD Display (MN50-LCD, MN50-LCDP, MN-LCD-100, MN-LCDP-100) Cause There are instances where an Micronet LCD has failed to upload a configuration from a MicroNet controller correctly. Resolution The following describes the correct process for downloading an LCD screen to a controller and uploading this to an LCD. If these procedures are followed, no problems should occur. How the LCD upload process works When an LCD configuration is sent to a MicroNet controller it is placed into controller RAM. When an LCD is connected to the controller it looks for the presence of this file and if it exists, this file is transferred to the LCD and stored permanently in EEPROM. This transfer process removes the controller copy of the LCD configuration; this means that should replacement of the LCD be required later the LCD scheme will need to be downloaded to the controller again. It is important to note that because the LCD file is initially stored in the controllers RAM it will be lost if the controller power is cycled or the controller is reset. LCD Download procedure Switch on power to the controller and then use VisiSat to configure and download the LCD configuration to the controller. If the controller is NCP and is to operate standalone, disconnect the communications from the controller before connecting the LCD and ensure that the LCD comms links are fitted to the controller (this is important). If the controller is NCP and is networked an MNN-COM card is required in the controller and the LCD must be remotely mounted. Make sure that the controller power is still switched on. Connect the LCD to the controller and apply power to the LCD. Note: Do not depress or hold any keys when connecting the LCD, this is only required if LCD firmware is revision J or earlier. Wait for the LCD to load its configuration. If the LCD configuration fails to load, check that the controller’s “Configuration Locked” property is not set to ”Yes” in VisiSat. Remove the protective strip from the LCD battery.

Issue Need to move a b3 controller to another comm port. Product Line Andover Continuum Environment Cyber Station BCX Controller Various versions of B3 controllers Cause Controller is installed on wrong comm port. Resolution Go offline editing Create all the Infinet controllers on the new destination commport assigning them the same or available Infinet ID as the controller that is on the original commport but a false serial number. Drag and drop copy all the points and programs from the original controller to the new controller. Once all the information is copied to the new controller then go and change the serial numbers of the original controllers to a false serial number. Verify that all the points and programs were correctly copied and are intact. Then go into the new controllers and change their serial numbers to what the serial numbers of there originating controllers were. Then move the physical infinet connection from the original commport to the new commport. Next go back to online editing. At this point you should see all your infinet controllers come back on line. Finally reload the complete site. Find new bacnet devices and save b3 controllers to database. It is important to note that if a site reload is not done, any controllers that are referencing points in the relocated controllers will have to have these object references verified and repaired in cases where the references have been lost.

Issue As part of installing InVue, what are the licensing requirements? Environment InVue 1.1 Cause InVue software re-installation on new server hardware. Resolution Two license files are required.  One license is for the Wonderware core and one license is for the add-on programs (like TreeTech, interface drivers, hrdbdde driver, etc...). The Wonderware license file was typically provided on a 3.5" floppy diskette.  The filename is wwsuite.lic.  It is installed in the following path:  C:\Program Files\FactorySuite\Common\License Install the file by using Wonderware's License Utility (available via Start > Programs > Wonderware FactorySuite > Common > License Utility). The license file for the add-on programs is provided during the software installation process.  Unlock codes must be provided to allow the programs to run.  A 30-day temporary license is provided during installation. The filename is WIBSSuite.lic. It is installed in the following path:  C:\Program Files\Siebe\WIBs\Core When the unlock codes are provided, use the Purchase WIB Software shortcut (placed on the desktop during software installation) to enter them.

Issue Customer is installing a new server computer and the host operating system is Windows 7 64-bit.  Will the current version of OPRIF (Operator Interface) version 11.6 operate properly if installed? Environment DMS OPRIF 11.6 or PSOPRIF 11.6 or Operator Interface 11.6 Cause Upgrade of computer hardware and unavailability of Windows XP Resolution OPRIF 11.6 will only operate on a Windows 7 64-bit operating system with XP mode installed. For a compatibility chart, see Product Announcement PA-00163.

Issue What are the effects of a connection object on the I/NET controller lan? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta 527/913/731 I/NET Cause The I/NET communication protocol has a maximum baud rate of 19,200 bps and this allows for a maximum of 10 messages a second to occur on the I/NET controller lan. This limit applies to the entire controller lan not just a single controller. Optimal performance will be at 5 or 6 messages a second on the controller lan. Resolution Any connection objects involving I/NET points need to be aware of the limits imposed by the controller lan protocol and adjust the periods of connection objects to avoid exceeding these limits. Every connection object that the source is from I/NET requires the value to be read from the I/NET controller before it can determine if the value has changed to send to the target of the connection object. If the default period of 10 seconds is used for all connection objects then only 100 points will consume 100% of the bandwidth on the I/NET controller lan to meet the demand and negatively impact the performance of the I/NET network. Instead count the number of connection objects with source values from I/NET. Divide this number of 4 to allow room for values being written to the I/NET network to determine the minimum recommended period for your connection objects to avoid overloading your I/NET controller lan. Ex: 250 points being sent from I/NET to a 3rd party system / 4 writes a second = 63 second period. This could result in some larger then expected periods and some points might be more critical then others which will require some prioritization. If of the 250 points only 15 require faster response time then they can use a lower period, but this will affect the period used for the lower priority points. It is recommended to avoid periods below 10 seconds if at all possible. Ex: 235 points at lower priority / 4 messages a second = 59 second period 59 second period for low priority points / 10 second period of high priority points = 6 polls per point * 15 points at high priority = 90 reads for high priority points. 235 points + 90 polls = 325 values read from I/NET / 4 messages a second = 82 second period for lower priority points to accommodate 15 high priority points.

Issue BACnet controller objects that have not been overridden are displayed on I/A Series R2 graphic screens in the purple color as if they were overridden. Environment I/A Series R2 (Niagara) Graphic screens displaying values representing physical BACnet controller inputs. Cause Purple BACnet values (I/A Series R2 graphic override color) are internal BACnet points that can not be modified (display only).  This behavior is normal and began to appear in MNB controller firmware versions 1.2 and higher.  Per the BACnet specification, read-only type points must be set to indicate an override condition.  The root cause is a design change required by the BACnet specification to bring the controllers into compliance for BTL certification.  The ASHRAE BACnet Specification 135-2004 specifies that the "read-only" type objects (e.g. Analog Value, Binary Value, etc.) OVERRIDDEN flag is: Logical TRUE (1) if the point has been overridden by some mechanism local to the BACnet device.  In this context "overridden" is taken to mean that the Present Value property is not changeable through BACnet services. In this case, the override is meant to indicate to Niagara that the point is locally overridden (by the controller) and cannot be changed by the Niagara BACnet service (or user). Resolution There are several approaches that can be used to display these objects without the background showing the purple color. One approach is to use a native Niagara AI object to buffer the value where the override condition is not transferred.  In addition, if the BACnet points and Analog Input objects reside in a poll-on-demand container, the BACnet points will not be polled unless a gx type object is added and directly attached to the BACnet point.  The graphic page will have a gx type object linked to the Analog Input object (displaying the value without the override) and another gx type object (invisible) linked to the BACnet point to start the point polling. A second approach is to configure the GxText object so that the object property "statusColorEnabled" is false.