Building Automation Knowledge Base

Issue Cannot delete personnel. A personnel object will not be deleted due to distribution failures. Product Line Andover Continuum Environment Cyberstation Cause If a person has an area assigned and the controller or door has been deleted, the distribution to remove that person from that controller cannot be accomplished successfully. Resolution First, remove all areas from the personnel object before deleting the object. This is by design. The reasoning behind this is to allow a person to be removed from the network before disabling access. Other things to check if distributions are failing: If running MSDE or SQL2000: Check to make sure the Agent is running. Check for duplicate tables and make sure they're all DBO Check Security Continuum DB make sure there is only one DBO linked to Andover97. If using SQL 2005: Look at the jobs under the Agent. They trigger every 5 minutes and are responsible for the task of deleting the personnel objects marked for deletion. At times there are errors for why the jobs are not running properly. If the above steps do not correct the issue then it could be an issue with the database. The PSS engineer may request the database to perform analysis to reproduce what is happening and offer suggestions to correct the problem.

Issue Is the new PSI / XPSI rev 4.1 compatible with Windows XP and Vista? Environment PSI / XPSI rev 4.1 Windows XP and Vista Cause Install PSI / XPSI rev 4.1 in a Windows XP or Vista Operating System (OS) Resolution The new PSI / XPSI rev 4.1 is compatible with Windows XP and Vista. Download PSI rev 4.1 from The Exchange. The zip file includes an installer and a READ.ME file that includes Release Notes and Installation Instructions. Note that the Patton Electronics RS-232 / RS-485 converter that has been widely used with the earlier versions of PSI (3.13) will not work with the new PSI / XPSI rev 4.1.  The B&B Electronics model USOPTL4 USB converter has been successfully tested with PSI / XPSI rev 4.1. Other recommended converters are listed in the Release Notes.

Issue S-E L2SV Linkage Kit and S-E L7SV Linkage Kit compatibility with Satchwell Plug and Seat Valve Bodies. Environment Satchwell 1 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 2 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 3 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 7 series Plug and Seat 2-port and 3-port Valve Bodies. Cause Use the correct S-E Linkage Kit with Satchwell Plug and Seat Valve bodies. Resolution 1.  Observe specification number of Satchwell Plug and Seat Valve Body Generally where a Satchwell AL series Linear Actuator is fitted to a Satchwell plug and seat Valve Body, the Actuator may be replaced by an equivalent S-E Forta or MV15B series Linear Actuator and appropriate S-E Linkage Kit. It should be noted however that neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series MZ/MZF or a Satchwell 7 series VZ/VZF plug and seat Valve Body. The internal screw threads of the Neck Adaptors included in the S-E L2SV Linkage Kit (880 – 0124 – 000) and S-E L7SV (880 – 0126 - 000) Linkage Kit are compatible with the external screw threads on Satchwell 1, 2 & 3 series Valve Body necks only. The external screw threads on Satchwell 7 series Valve Body necks however differ to those on Satchwell 1, 2 & 3 series Valve Body necks. Consequently neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series Valve Body. A S-E Forta series Linear Actuator may be mounted on a Satchwell 7 series Valve Body however using Linkage Kit 880 – 0135 – 000.  No equivalent Linkage Kit is currently available for use with the MV15B series Linear Actuator. The Satchwell Valve Body series may be determined from the Valve Body specification number stamped on the Valve Body Identification Collar, where the single middle digit of the specification number denotes the series. In the case of a Satchwell 7 series Valve Body for instance the single middle digit of the specification number will be the number 7 (e.g. 626 – 7 – 402)

Issue Too much LON communications traffic can cause LON communications errors. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series MNL 800 Building Operation Automation Server Premium LON Network  I/A Series R2, AX, N4 Jace LON Network Cause Sending output LON SNVT values too frequently or more often than reasonably needed. Resolution There are a series of NCI (configuration) objects that control the transmission and reception of these data values on the LON network. One of four NCI objects (nciSndHeartBeatA, B, C, or D) is assigned to each NVO object in the application program. This value regulates the periodic LON transmission queuing of the NVO object values for each binding. One of four NCI  objects (nciRcvHeartBeatA, B, C, or D) is assigned to each NVI object in the application program. This value regulates the fallback timeout for each NVI object value. If a value is not received via the binding in this time period, the NVI object value will revert to its application-defined default value. In an MNL-800 controller, there are two additional NCI objects that are used to regulate the flow of data onto the LON network. The nciMinOutTime object is used to throttle the transmission of all data values queued to be sent via bindings over the LON network. This NCI object sets the transmission time interval between each NVO value being sent on the network. The important fact here is that the product of the number of bound NVO values times this interval (nciMinOutTime) must be LESS than the shortest nciSndHeartBeatX (X=A, B, C or D) interval. For example, if the Send HeartBeat is set to the default of 120 seconds and there are 60 NVO SNVTs bound from this controller, the nciMinOutTime must be set to a value of fewer than 2 seconds.  The recommendation for setting this SNVT value one half the shortest nciSntHrtBr divided by the number of NVO SNVTs bound from the controller.   The nciMinPropTm object is used to regulate the transmission queuing of changing bound NVO object values. This timer acts as a time-based filter to prevent a rapidly changing NVO value, such as a constantly changing temperature, from overwhelming the communication capacity of the LON network. Typically this value is set to a value of 1 to 5 seconds. Additional information can be found in Chapter 6 of the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). BACKGROUND: This section is provided to give the reader a basic understanding of bound LON communications, as applied to LON controllers in general. Data communications across a LON network is accomplished by using a LON Network management tool to create a binding between a device with a data source (NVO object) and one or more devices with data receivers (NVI objects) in other LON controllers. The device containing the data source will send the bound data value at a periodic rate, as defined by the associated SendHeartBeat NCI object, and whenever the value of that object changes. If the NVI object does not receive a value from the sender (bound NVO object) within a specified time period, as defined by the associated ReceiveHeartBeat NCI object, the NVI object will use a local fallback value until such time as it receives a new value via the binding.

Issue How to program a limit block for use in Niagara G3. Environment Niagara G3 Cause Limit are configure using the Reset object in the kitControl palette in the Math folder. Resolution Use the Reset object found in the kitControl palette in the Math folder.  To use it set the "Input Low Limit" and the "Output Low Limit" to the lowest desired output.  Set the "Input High Limit" and "Output High Limit" to the highest desire value. kitControl-Reset This component performs a linear “reset” on the inA value. Reset is available in the Math folder of the kitControl palette. Reset operation is defined by the following four slots: Input Low Limit — must be less than the Input High Limit Input High Limit — must be greater than the Input Low Limit Output Low Limit — may (or may not) be greater than the Output High Limit Output High Limit — may (or may not) be greater than the Output Low Limit For example, a Reset object is used to establish a hot water control setpoint, based on the outside air temperature at inA. When the outside air temperature is 0°F, the hot water setpoint is 200°F. When the outside air temperature is 75°F, the hot water setpoint is 100°F. The Reset object is configured as: Input Low Limit = 0.0 Input High Limit = 75.0 Output Low Limit = 200.0 Output High Limit = 100.0 Whenever the inA value is beyond the input limits, the output is limited by the corresponding output limit (in this case, 200 at 0°F or below, 100 at 75°F or above). When the input is at an intermediate value, the output scales linearly. For example, when the outside air temperature is at 38.2°F, the Reset output is 149.1°F.

Issue Warning - Platform running low on RAM disk space (Niagara G3 Release 3.2.5 and higher) Environment I/A Series G3 (typically embedded ENC/JACE platforms) Cause Low disk warning for history RAM disk A station fault will be generated if the free disk space on the history / alarm RAM disk falls below the minimum percentage specified on the PlatformServices property sheet. Resolution During station startup,  /niagara/bin/ramdisk.sh is invoked to create the RAM disk partition.   The RAM disk is named /aram0 and symbolic links are created from /alarm -> /aram0/alarm /history -> /aram0/history.  After the RAM disk is created it is populated with the contents of the alarm.zip and history.zip files.  During a station save or shutdown, the alarm and history files on the RAM disk are zipped and stored under the station directory in alarm/alarm.zip and history/history.zip.  If this fault occurs, users should take one or more of the following actions to prevent history/alarm data from being lost: Reduce number of histories that you are collecting Reduce number of records in each history Increase history RAM disk system (requires reboot). Action 3, above, will reduce the available system memory and should only be taken if there is sufficient free system memory.  Rather than writing history and alarm records directly to persistent storage, a Niagara G3 station stores history and alarm records in a RAM disk. This approach reduces the number and frequency of writes to flash.  Be careful not to increase too much otherwise you risk consuming all the available JACE free RAM causing the niagarad to crash.  Review the free system memory and make sure to leave a buffer of at least 1 MB of free RAM.  The RAM disk size is stored in /niagara/lib/platform.bog and can be adjusted using Services -> Platform Services. After reducing the number of histories, etc. the RAM disk will still indicate a low warning message until the unused histories are removed from the history storage.  Delete the unused histories using the Database Maintenance view on the history component view within the station.

Issue How do I configure oBIX (Open Building Information Exchange) to integrate a Niagara R2 station and a Niagara G3 station? Product Line TAC IA Series Environment Niagara R2 version 5.22 and later Niagara G3 version 3.4 and later Cause This document provides an overview of the integration of an R2 UNC to a G3 Enterprise Server using oBIX (Open Building Information Exchange). Resolution The R2 UNC must be licensed for "obix" and the obix jar file must be in the remote library of the UNC. Add the "ObixService" to the Services container of the UNC. Re-boot the UNC. The G3 Enterprise Server must be licensed for obix. Double-click the Drivers Component in the G3 Enterprise Server to open the Driver Manager. Add an Obix Network. Double-click the new Obix Network to open the Obix Client Manager. Click the "New" button at the bottom. Add a new "R2 Obix Client." Double-click the new R2 Obix Client. Enter a name for the UNC. In the Lobby field, enter http://, followed by the IP Address of the UNC, followed by "/obix". Enter the UNC's station username and password. Click OK. After a few seconds the state of the client should be "Attached." Expand the UNC Device in the Nav Tree. Double-click the points component to open the Obix Point Manager. Click the "Discover" button. After the points are discovered, expand "Lobby" and then "Config." (The Lobby is the root of a Server's oBIX object tree.) You can now scroll to see the containers and objects in the UNC's station. You can add UNC points to the G3 Enterprise Server's database in the usual manner. If you wish to have "link control" of objects in the UNC from the G3 Enterprise Server, then add an "Obix Export" object in the R2 Logic. These Obix Export Objects (analog, binary or multistate) are found in the Obix jar file in the remote library of the R2 UNC. Link pOut of the Export Object to pIn (if available) of the object you wish to control. Then link sOut of the R2 object back to the feedbackInput (fIn) of the export object. If no Priority Input is available on the R2 object, simply link the sOut of the Export Object to the sIn of the R2 object. No link to the feedbackInput of the Export Object is required. Return to the G3 Enterprise Server and discover the points in the R2 UNC. When adding the Export Point to the obixNetwork, the Export Objects default to type "Numeric Writable" so they can be commanded from the G2 Enterprise Server.

Issue The Xenta 7xx from factory it has the default IP address 192.168.255.2, which also is stated in the manual. But when you run the “format” command on a Xenta 7XX, you will get IP address 172.22.1.5. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 527 NPR, 555, 701, 711, 721, 731, 901, 911, 913 Cause The format command will wipe all memory from the Xenta Server. Its IP address will need to be reset, system program will need to be reloaded, and XBuilder project will need to be redownloaded. Resolution The Xenta from factory has the default IP address 192.168.255.2 subnet mask 255.255.255.0 After the “format” command it will have IP address 172.22.1.5 subnet mask 255.255.255.0 See IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for instructions on setting the IP address to the desired address.

Issue Wiring detail for using the B&B Electronics model USOPTL4 converter with PSI / XPSI Revision 4.1 Product Line TAC IA Series Environment PSI (Personal System Interface) Revision 4.1 XPSI (Xtended Personal System Interface) Revision 4.1 B&B Electronics USOPTL4 converter Cause PSI / XPSI Revision 4.1 does not work with the Patton Electronics RS-232 / RS-485 converter, model 2089-bc, that was widely used with earlier versions of PSI (rev. 3.13) and XPSI (rev. 2.0). Resolution One converter recommended for use with PSI / XPSI Revision 4.1 is the B&B Electronics model USOPTL4. To connect directly to the RJ-12 jack on an ASD device, or on a stat: Cut the RJ-12 plug off one end of an RJ-12 cable. Connect Black and Yellow wires and tape back. Connect the Green wire to the RDB(+) on the screw terminal of the USOPTL4. Connect the Red wire to the RDA (-) on the screw terminal of the USOPTL4. All four switches of the DIP switch on the USOPTL4 must be in the ON position to allow it to work properly on the ASD bus.

Issue Problem when attempting to read/write trends and event. Environment Vista Workstation SQL Cause This could be because of a damaged COM+. Check the Windows eventlog for COM+ related errors.  TAC Vista uses COM+ to host DSS, the interface between TAC Vista server (TACOS) and SQL server, in versions from 4.3.0 to 5.0.1. As always, make sure to backup your computer before tampering with COM+! The COM+ catalog is a catalog of all the available COM+ applications, classes and attributes on a given system. Windows keeps this catalog to make sure that there's consistency between the various COM+ attributes and exposes it through various programming interfaces. If the catalog becomes damaged, programs that rely on COM+ won't work properly (or at all!). One example of such a service that depends on COM+ is the Volume Shadow Copy Service used by (among other programs) the Microsoft NTBACKUP application. NTBACKUP can make backups of system files or other locked files by using Volume Shadow Copy. However, if NTBACKUP fails with an error in the Volume Shadow Copy COM+ service, odds are the catalog has been damaged and needs to be repaired. (Another symptom of a damaged COM+ catalog is when many programs hang continuously for minutes on end, but this is a minor, less well-documented symptom.) Resolution To repair a damaged COM+ catalog, do the following: Locate the file %WinDir%\System32\Clbcatq.dll and rename it to ~Clbcatq.dll (note the tilde). %Windir% is an environment variable that usually translates to C:\Windows. Reboot the computer in Safe Mode. Open the Registry and delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3. Look in the %WinDir% directory for a subdirectory named Registration. Delete Registration entirely, including any files inside it. Reboot the machine normally. At a command line, type regsvr32 %windir%\system32\ole32.dll, and click OK on the acknowledgement that comes up. Open Control Panel | Add/Remove Programs | Add/Remove Windows Components. Click Next to reinstall COM+. You do not need to select any components to add or remove; COM+ is reinstalled automatically as a matter of course. You shouldn't have to reboot after this; the re-registered COM+ services should work immediately.

Issue LDF file of a database is growing rapidly. SQL Database Recovery Modes Explained Product Line Andover Continuum Environment Continuum  SQL Server Cause Recovery Mode setting could allow all transactions to be logged. Resolution The Full Recovery Mode basically logs all transactions successfully, failed, table creations, columns created etc... When the Continuum database is created, there are no additional tables added or columns added unless there is an update to the database to a different version. Some sites will require Full Recovery Mode but for most sites, we only need to know when an error occurs when updating or altering rows occurs and Simple Recovery Mode will log those. The Continuum Databases are created with Simple Recovery Mode. It is up to the individual site whether they need Full Recovery Mode. Most sites run with the default Simple Recovery Mode since there is no need to log every successful transaction but only want to catch the transactions that have an error. The Recovery Mode is especially important if your site is a single-user setup. Single user databases are limited in size and if you fill-up the .LDF log file, you can exceed Microsoft's database limitations in a short period of time. As for Enterprise versions of SQL for Continuum Lan systems, you'll need to watch your available disk space. Check what the Recovery Mode is set to by using SQL Server Management Studio Express, right-click your ContinuumDB and select properties, go to the Options tab, and check the Recovery model. See the image below for details.   Furthermore, if you have selected Full Recovery Mode in the past and now have a large unwanted .Ldf file that is causing you issues, then selecting Simple Recovery Mode at this point will also truncate your original Log file down to a more usable size retrospectively.  (Although it may take a few hours before you see any changes).

Issue Getting error message in Vista that Menta is in 'stand alone' mode and cannot edit the .MTA Environment Vista Menta Cause This happens usually when Menta has previously been installed on the system in a "stand alone" fashion and then Vista was installed at a later time. Resolution Go to Start > Run and type "regedit" to open the Registry Editor Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > TAC > TAC Menta Double click the key named StandAlone. Change the value data to "No"   For a 64 bit OS, the path in the Registry Editor is HKEY_LOCAL_MACHINE>SOFTWARE>Wow6432Node>TAC Menta

Issue Power cycling the SE8000 room controller will cause the settings to revert to default. This requires reconfiguring each of the parameters once again. Product Line EcoStruxure Building Expert Environment Multi Purpose Manager Automation Server SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause This has to do with BACnet priority; if the configuration was not written with the appropriate priority, the Room controller will overwrite the parameters upon a power cycle and set them to default. Resolution There are a few ways to prevent the SE8000 from reverting to its default settings after a power cycle: Configuring each Room Controller locally by navigating to the configuration menu. (Centralized and Standalone system) Using a LUA4RC script (Centralized and Standalone system) Writing to points with a specific priority via the BACnet front-end (Centralized system) NOTE: Since Zigbee does not have any command prioritization mechanisms, setting the parameters from an MPM via Zigbee will not be retained after a power cycle and is strongly not recommended. All three methods can be used to configure a Room Controller prior to or after its installation. Configuration prior to installation can save a lot of time for the technician on site.     1 - Configuration on SE8000 (Local) Changing the parameters on the SE8000 locally will permanently save the settings and will also allow the user to change the parameters settings locally (e.g. Occupied cooling setpoint). This however can be time consuming.   2 - Configuration via LUA4RC This method is especially useful in standalone applications with no BACnet front end. If there are many parameters that need to be adjusted, it will be quicker to upload the script to each of the Room controllers rather than navigate to each parameter manually. By default, when you assign a value to a BACnet point, the write priority will be priority 16 Example: ME.MV6 = 2 --Set "Network Units" to Imperial (blocked by using priority 16, not user-adjustable) To write to another priority, an array is used Example: ME.MV4_PV[3] = 1            --Language will be blocked by user, room controller and bacnet front-end. Will be saved to memory and will stay after a power cycle NOTE: To release this priority, you can set it to nil (example: ME.AV25_PV[8] = nil). To access the relinquish default, priority 17 can be used Example: ME.MV10_PV[17] = 1    --Set "Occupancy Command" to "Local Occupancy"; here it is mandatory to have (_PV[17]) because thermostat must be able to toggle between "Occupied" and "Unoccupied" temperature Use the script below as a template for your LUA4RC script (remove comments to use less memory) if not init then ME.MV6 = 2           --"Network Units" ME.MV10_PV[17] = 1  --"Occupancy Command"  ME.AV46_PV[17] = 3   --"Standby Temperature Differential" ME.MV5 = 2           -- "Time Format" ME.AV67_PV[17] = 4   --Standby Time ME.AV68_PV[17] = 12  --Unoccupied Time ME.MV46_PV[17] = 3   --UI 16 Configuration ME.MV4_PV[3] = 1     --Language --Add all required configuration parameters init = true end   3 - Configuration Via BACnet: SE8000 parameters can be configured via the BACnet front end by using the following priorities: Priority 2 or 3: Using these priorities will permanently save the setting on the SE8000 and will not allow the user to change the settings locally. Relinquish default: This will allow the user to change the value locally on the SE8000. This is typically used with setpoints NOTE: using Priority 16 will not allow the user to change the value locally on the SE8000, however, the SE8000 will revert to value to default upon a power cycle. Another effective method is to push the configuration to multiple SE8000s across the network using a lua script. See Bulk Lua4RC upload via BACnet (Mass upload).

Issue Direct Connect to Xenta 527-NPR Product Line TAC INET Environment I/NET Xenta 527 Xenta 527-NPR Cause Newer versions of Xenta 527-NPR with 5.1.0 and 5.1.1 revisions are unable to be directly connected to the system. Resolution Using the FTP connection through IE (Internet Explorer) to connect to the device. Log on using the root username and password Now go to sys/system/hwconfig.cfg Copy out the hwconfig.cfg file and open it with Notepad Modify the part that says serial_A_function="7" and change it to "5" Save this and now copy it back in again. Restart the device Start I/NET and the direct connect through the NPR to the system should be working now. Warning: Reloading the system program (such as performing upgrades) will remove this change.

Issue How do the 7793 and 7798 handle retries?  Improving I/NET sublan communications Excessive MCU Lost messages in AMT Command Error messages in AMT Product Line TAC INET Environment I/NET sublan 7793, 7798 Cause If there are issues on the physical layer of the network, this will effect the reliability of I/NET communications. However, these risks can be lessened with some best practices. Resolution Best Practices and Troubleshooting measures to improve sublan communications: Ground the 24V line coming into MRs and ASCs Connect ground to the earth ground terminal of DPUs and SCUs. Bond the shield of the LAN cable all the way through the network, not landing it on any controller anywhere and then tie it to earth ground in one location. (see diagram)   SubLAN Communication Explained: The first packet to any sublan device goes out on the primary channel, terminals 1 and 2 of the sublan connector on the 93/98. If the device doesn't respond in time, a second packet is sent out on the alternate channel, terminals 4 and 5. If there is still no reply, a third packet goes out on the primary Finally, if there is still no reply, that device is marked as lost which generates an "MCU Lost" message. Optional Configuration for only using Terminals 1 and 2:  If you are using only Terminals 1 and 2 you could be missing 33% of it's retry capacity. If you follow wiring guides and best practices the device will answer on the first packet every time, however if you have not followed the guide all it takes is a little noise to make the retries necessary. If you are unable to use a loop configuration, or want to avoid the extra potential for noise and EMI, in stall a jumper on the sublan connector from terminal 1 to 4 and from terminal 2 to 5 The allows you to get the extra retry, without the extra cable This will also function if you have some controllers on channel A and some on Channel B The SLI doesn’t have to be at the end of line on sublan communication  

Issue StatusBackup "State" system variable is not able to be manually changed and attempting to set this variable to Enabled produces a script error instead of resetting the flash circuit breaker. Product Line EcoStruxure Building Operation Environment Building Operation v1.8 and below. b3/i2 Controllers Cause Feature to reset flash circuit breaker was not implemented in the earlier versions of Building Operation Resolution A new feature to reset the flash circuit breaker was implemented in Building Operation v1.9 to address this issue. The b3 BACnet Device Memory on-line help topic shows how this is manually reset from the WorkStation in the Device menu.

Issue When the remote I/O modules (MNB-1000-15) are powered for the first time, the status LED stays blinking red. Product Line TAC IA Series Environment I/A Series MNB 1000 -15 Cause This is a normal operation. Resolution When the associated MNB-1000 receives a database configured with remote I/O modules, it will initiate communication with the remote I/O modules. If it is successful, then the status LED with turn green.

Issue TGML graphics to display "OFF" and "ON" instead of "0" and "1" Product Line EcoStruxure Building Operation, TAC Vista Environment TGML Graphics Editor Cause Data in the Vista database is stored as 0,1 but may be displayed using paired texts. Those paired texts can be set to show up on the graphic, or a unique conversion can take place in TGML. Resolution If you use default snippets that come provided with the editor, you have the option of displaying a value with either NumericPresentation or TextPresentation. The only real difference between the two is that TextPresentation defines the binding's behavior format as "Presentation" rather than "None." This will only display built in presentation formats -- an alarm state will show up as "Alarm" or "Normal" -- or if you've defined paired text within a binary point in the Vista database, that will show up instead of (0,1). This does not, however, explicitly give you the option from within the Graphics Editor to convert decimal values into text. The example TGML code below describes how to take a value that is showing up as "0" and "1" and make it read instead as "OFF" and "ON." <Text>Value   <Bind Attribute="Content" Name="Value">     <ConvertValue SignalEqualTo="0" AttributeValue="OFF"/>     <ConvertValue SignalEqualTo="1" AttributeValue="ON"/>   </Bind> </Text> Cut and paste this TGML code into the editor's Source view to view it in the editor. Just be sure to paste it between the opening tag and closing tag. If all you see in the Source view is one self-closing tag, that is because the page is empty. Either add separate opening and closing tags, or go back to Design view and add one object to the page to automatically split them.You can see here that a Text object has a binding associated with it. That binding's target attribute is "Content" because this will alter the content of the Text. (We could also change the text's stroke color, background color, font size, position on the page, etc., by changing our binding's target attribute.) ConvertValues underneath the binding tell the binding how to alter the Text's content. A SignalEqualTo 0 will write "OFF" to the content and a SignalEqualTo 1 will write "ON" to the content. The number of ConvertValues is not limited to only two. There could be a third one to say that a value of 2 should read "STANDBY."

Issue The communication with TAC Xenta controllers is slow or inconsistent Product Line EcoStruxure Building Operation Environment TAC Xenta LonWorks communication Cause The Non group receiver timer is not properly set. Every device has a timer called Non group receive timer. The Non group receive timer is used to make sure that a re-sent Lon package will not be treated as a new message and to determine when a receiver buffer can be released. It is used in Acknowledged, Repeated and Request/Response transactions, but not in Unacknowledged ones. If this timer is set too low, a re-sent package, like Unacknowledged repeated message, may be treated as new messages, that will be sent on to the application. The communication buffers will not be released until the timer has expired. If the timer is set too long, that may result in the device running out of buffers, and new messages will not be received during this time. If a device has many SNVTs or TACNV’s being transferred there may be a need to increase the value of the Non group receiver timer. The default value for a programmable Xenta device is 768 ms. Resolution Change the Non group receive timer of the Xenta devices. The default value for a programmable TAC Xenta device is 768 ms. The recommended timer values are:   Number of network variables Non group receive timer value < 50 768 ms (default) 50 – 100 1024 ms > 100 1536 ms     The default value for the AS and AS-P  is 8,092 ms. There is no need to change that value.

Issue In a Niagara G3 station, what is the difference between a Station Save and Backup Station? Product Line TAC IA Series Environment Niagara G3 (AX) Jace/ENC Niagara G3 (AX) Enterprise Server (ENS)  Cause Help determine which feature (Station Save and Backup Station) meet the requirement. Resolution A Station Save only saves the config.bog file to the local device (if an ENC, it will save the file on the ENC; if an ENS, it will save it on the ENS computer).  The Backup Station function performs a complete backup of the connected ENC or ENS station, saved as a dist file on the Workbench computer. The backup dist contains the entire station folder plus the specific NRE config used by that ENC or ENS platform, including license(s) and certificate(s). The dist also contains pointers to the appropriate NRE core, Java VM, modules, and OS. If ever needed, you can restore a backup dist using the platform Distribution File Installer view. The backup dist file also contains the TCP/IP configuration of the host when it is backed up. When restoring the backup, the choice to restore these settings, or retain the TCP/IP settings currently in use by the target host is available.