Building Automation Knowledge Base

Issue Upgrade warning and Error Conversion Log Analysis Additionally upgrading an AS from version 1.3 to 1.4 can create a number of unresolved or invalid references. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, ASP, ASB Building Operation Enterprise Server Building Operation Device Administrator Conversion Log Cause When upgrading using the Device Administrator various warning and errors can be seen. Errors will prevent the upgrade, but warning will still allow the upgrade to continue. Starting in version 1.4, new rules have been put in place that will invalidate some bindings that had previously been made in older versions. These rules may cause errors to be produced in the Conversion Log found in the Device Administrator. The three new rules are: Public Numeric/Signal bindings will be dropped. Multiple bindings will be restricted to one. Binding to Local Node NVIs will be dropped. For more information regarding the rule changes made in version 1.4 see Reference Guide and References beginning with 1.4.x. Resolution Instructions on how to perform the Automation Server upgrade and how to obtain the Conversion Log, see Upgrading Automation Servers from 1.3 to 1.4. Breakdown of the Conversion Log The file paths given in the Conversion Log entries will direct you to the location of the unresolved or invalid reference. Depending on the type of entry it is, it may require further action to correct the problem.   Type of entries found in the Conversion Log WARNING: ERROR: Invalid_Property_Reference (destination) (source) Explanation: Either rule 1 or 3 has been broken. If a public numeric/signal is bound programmatically to another object then it violates rule number 1. The public numeric/signal in the program must be changed to an input or output before upgrading the database. If the destination of the binding is an NVI in the Local Node then it violates rule number 3. A change to the configuration of the local node must be implemented before performing the upgrade. In many cases the substitution of an NVO for the NVI will address this issue. Explanation: This binding should not have been allowed in SmartStruxure version 1.3. In the StruxureWare Building Operation Technical Reference Guide, you will find on page 2107 that BACnet priority 6 is reserved for future use. This binding needs to be made to a different priority. WARNING: ERROR: Object_Does_Not_Exist (object). Explanation: The object that the reference is trying to bind to does not exist. In other cases the binding was already broken in the source database so it will remain broken in the target database. The binding fix can be addressed before or after the upgrade. WARNING: Property (property) bound to (property), so binding to (property) is dropped. Multiple bindings are not allowed in SmartStruxure version 1.4 and above. Explanation: The object is being written to by multiple objects and/or programs. This violates rule number 2 and is no longer accepted. After the upgrade, only one of the bindings will be left connected and all others will be dropped. This will require changes to be made to the configuration to maintain the same operation. Note: In some cases this warning can occur due to a default value of a configuration object that is mistakenly interpreted as a duplicate binding. The binding is in fact preserved by the upgrade and no further action is required. WARNING: Discarding incomplete binding for (object) -unknown source. Explanation: Due to a version 1.3 defect, the source version configuration database contains an incomplete binding error. This is not a problem but it may be a sign that someone intended for the property to be bound to something but failed to do so. Therefore, the configuration should be examined after the upgrade has been completed to insure that everything is okay. No information has been lost in the upgrade but check the configuration to rule out any errors in the source version database. WARNING: Property (property) in (object) is Unit configured but is not configurable in the new. Explanation: This property has a selected unit configured in the source version database, while in the target version configuring the unit of this property is no longer possible/meaningful. These errors should be investigated to insure that there has been no negative impact on the operation. Generally this error will not be a problem and will require no further action. WARNING: Property REF in (object) is not defined in the new system, skip REF. Explanation: The REF property prior to version 1.4 held a back-reference to an object or property that was referring to the property at hand. Starting in version 1.4 and on, the back-references are handled by other means and are no longer represented in the configuration database. This information can not be upgraded but this is not a problem and no further action is required. WARNING: Invalid value for (property) in the object, (object). The default value has been applied. Explanation: The value seen in the source version is invalid or can not be found; therefore the upgrade process sets it back to the default value. No further actions needs to be taken. WARNING: The declared instance (instance) is obsolete but contains non-default data which has been discarded. Explanation: If the instance is a SavedUserTokens or System/Remote Server warning then the warning can be ignored. No further action is required. WARNING: Property (property) in (source) is not an acceptable property type and is not configured. Explanation: This has to do with the lead reference for shadow Alarm Control Panels that cannot be properly upgraded due to changes to the type of system in version 1.4. There is logic in place that automatically sets the lead reference to the ES again. This is a warning that can be ignored. Explanation: There have been changes made to the type of system. This change prevents the hidden SynchSource property of the Time Zone setting in the source version of the database from being upgraded automatically. If the lead reference was set for Time Zone in the source database, this may have been erased and will have to be done again after the upgrade. This should be followed up manually. Explanation: The new referencing scheme expects all references to be relative so if there is a full binding path it is perceived as an error. This is not an issue and requires no action. Explanation: MatchedDevice is a hidden property that can not be seen. This warning refers to old items that have not been cleaned out. This warning can be ignored. Note: Also keep in mind that the upgrade process considers any empty link "not an acceptable Property". This error can be ignored, no changes need to be made. INFORMATION: Property "Value" in (location) is Unit configured but is not configurable, default unit is used. Explanation: This property has a configured unit that is no longer allowed to be configured in the target database, a fixed default value is used. This is unlikely to cause a problem, no further action needs to be taken.  

Issue Get "Value does not fall within expected range" error message when trying to view values from a Vista node in webstation. Environment Vista 5.1.X Webstation 5.1.X Vista in network (master with at least 1 slave) Cause This is a COM error caused by a difference in regional settings on the Vista servers. E.g. 100 000.00 may be retrieved as 100,000.00 if other settings are used on another server. This will cause a mismatch. Resolution Ensure that the settings for digit grouping and decimal symbol are the same on all Vista servers. Click on Start\Control Panel\Regional and language options. Select Customize and check the settings on the Numbers tab. Compare these settings with the other Vista servers.

Issue Continuum reports an Unknown Model Number error. Product Line Andover Continuum Environment Controller Model number Bootloader Learn Cause Possible reasons why Continuum may report an Unknown Model Number error. Controller is in bootloader mode. Controller is not responding fast enough due to a comm issue. The controller type saved in the Continuum database is different from the controller type physically installed. The total number of controllers exceeds the maximum number of nodes allowed on the Master. The baud rate of the bLink is not correctly set for the MSTP bus. The comm bus is not stable. Problems introduced to the bus due to a bad controller or electrical interference. Resolution Communication issue must be troubleshot by using a combination of Controller error logs and LAN capture analysis. A controller can be brought out of bootloader mode by flashing the firmware.  Create the device manually. Attempt to learn the controller onto the bus with no other controllers attached Correct misaligned baud rate settings. Run an ACCTrace at the Workstation during a learn to detect duplicate IDs. Other articles that address this issue: Unknown model number error when learning I2/b3 device Learn Process stopped and get an error "Can not learn this controller, it contains an unknown model number"

Issue Virtualization using VMWare, Virtual Server or other products is useful when deploying applications Is virtualization supported with Continuum?  Will Continuum work in a virtual environment?  Environment Continuum WMWare Virtual Server Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause Continuum compatibility with Virtual Machines (virtualization - VMWare) Resolution VMWare VSphere 5.5 and 6.0 has now been qualified to work with Cyberstations and Web.Client in Continuum v2.0 and above. Note that this will require a software licence and that the virtual environment must comply with the minimum system requirements for Cyberstation and Web.Client Server. See the latest Continuum v2.0 Compatability Matrix for details.                                                         There have been reports from the field from engineers that  have used Continuum and SQL server with various virtual software not currently qualified. If there are any issues with this implementation with an unqualified solution, then it would be necessary to install Continuum on a supported configuration (see the Continuum Compatibility Matrix) prior to involving engineering to evaluate any problems. This solution has not been tested and is outside of what we currently support. These include: Other VMWare environments, Microsoft Virtual PC (HyperV), Citrix, Windows 7 XP Emulation, etc. Marathon Redundant SQL Servers is a very specific solution which does use virtual machine. This is an isolated case and does not apply to standard implementations of Continuum or Webclient.

Issue How to calculate total memory required for controller to store logging information for the required duration. Product Line EcoStruxure Building Operation, Andover Continuum Environment NetController (CX9900, CX9940, CX9680, bCX9640) InfinetController (i2xxx) BACnet Controller (bCX4040, bCX9640, b3xxx) Cause Need to know how much memory is needed per point to determine the maximum number of entries and minimum interval time that the controller can use. Resolution The general equation of calculating memory use for controller logging is as below; * Memory usage per point = { 8bytes + (4bytes * NumberOfLog) } In addition to that, each controller requires minimum 1~2KB of freemem after the controller logging memory allocated.  Regarding the log interval, if the point is being logged for controller only, you can set the interval in seconds unit.   But if you configure the point for ExtendedLog as well, the logging interval should be in minute unit. Again, if there many objects with one minute interval for Extended Logging, it will affect the performance of the Cyberstation and also increases the size of ContinuumDB dramatically in short period of time. In this case, consider increasing the log interval to 5 ~ 15 minutes for Extended Logging.

Issue Will there be any problems wiring two HID iClass RP40 readers to one reader channel?  Environment ACX57xx, AC-1 Cause Need two readers on a vehicle entrance at different heights Resolution Tested (2) HID RK40 (iClass with keypad). The RP40 uses less power but should be very similar. Not recommended to power the two readers from the same reader input unless you are sure the reader input can handle the combined peak mA rating of the two readers. ACX5720 - worked fine. The RK40s were powered with different reader channels and then just doubled up the 1-DATA, 0-CLK and LED1 terminals on the ACX with the DATA1, DATA0 and Green LED leads from the readers. AC1 - worked fine. The AC-1 terminals are small so a single piece of wire was used off the DATA/1, CLK/0, and LED terminals of the AC-1 and landed on a terminal block with DATA1, DATA0 and Green LED leads from the readers. The RK40s were powered with an external power supply.  

Issue Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147) lcaErrNsLicenseViolation 147 LNS license access failure. Product Line TAC Vista Environment LonMaker, NL220 LNS Network Cause Feedback from Echelon on this error message. A variety of conditions may cause this error. Some relate directly to internal licensing components. For example, the license DLLs may not have installed properly, the files that identifies the license (nsseng.exe for the LNS Server, lonmaker.DSL for LonMaker) do not exist, or the Crypkey licensing components (crypserv.exe and ckldrv.sys) are not running properly. You can resolve these problems by deleting the files that may be causing problems, and re-installing LNS. The license DLLs, as well as the crypserv.exe and ckldrv.sys files, can be found in the Windows 'LNS Licenses' folder, and the Crypkey files can be found in the Windows 'system32' folder. Note that you must stop the 'CrypkeyLicense' service and 'NetworkX' driver before deleting the Crypkey files. Certain conditions on the PC operating the license may also cause this error. For example, if the PCs file system is corrupted or low on space, or if the license files have been manually deleted, tampered with in any way, or moved by some disk-defragmentation utilities, this error will occur. You can resolve these situations by ordering a replacement license key. If the PC clock is set back to a time before the creation of the license or before the last time credits were purchased, this error will occur. In some cases, this can be resolved by rebooting the PC. Otherwise, it may be necessary to order a replacement key. The error may occur if the license has been transferred out of the PC, manually terminated, or if there are zero maximum credits. In this case, you need to purchase additional credits for the license. For more information on licensing, see Chapter 13 of the LNS Programmers Guide. Resolution It is very likely that you have corrupted LNS Credits. To determine if this is the case and how to solve it please reference Corrupted LNS Credits.  

Issue .MTA file not updated .MTA file does not show the correct value when exported/imported The Menta project does not have the correct value when imported into a new database Product Line TAC Vista Environment Vista Menta Xenta OP Cause The upload/download parameter does not save any changes in values to the .MTA file. It only saves it to the device and Vista database. This means that if you export a project and import it to a new database the .MTA file will contain the initial values chosen when you last saved the Menta project. To get the values saved to the .MTA file, you need to edit the Menta project and save it again. However, to trigger the save correctly, you need to change the project. For example, add a comment or move a block, then hit save. Resolution  Below is the correct way to edit a project in a new database.  On the client PC, start by doing an upload parameter; this ensures that the values stored in the Xenta are present in the Vista database. Edit the Menta project(s) and add a comment (This can be a comment like "John brings the project home to make some changes") now the project can be saved, and all new values will be stored in the .MTA file.  Export the database/project Import the database/project to the new PC Make the desired changes Edit the Menta project(s) and add a comment (This can be a comment like "John has made the following changes ....") now the project can be saved, and all new values will be stored in the .MTA file. Export the database/project Import the database/project into the client's PC Now make a download parameter; this ensures the Xenta will get updated with the changes you have made.

Issue After several days or weeks, all Xenta Servers go offline in Vista. They can't be reached via the web interface, however they can still be pinged. Environment TAC Vista Xenta 511, 527, 701, 711, 721, 731, 913 Cause We have identified a memory allocation issue where the memory was not released properly for a Microsoft component (secur32.dll). This can be seen in the memory when the heap for this Microsoft module was re-allocated and tried to double its size after a certain time interval. The re-allocation required that a continuous block in memory was available for a successful re-allocation to be done. As a result of a failed re-allocation, all Xenta Servers went offline in TAC Vista Workstation. Resolution If the Vista PC is running Windows 2003 Server there is solution, but older Operating Systems (like Windows 2000/XP) will likely never get this fixed. Newer Operating Systems like Server 2008/Windows 7 don't suffer from this bug.   The solution provided by Microsoft is not included in any Windows update or Service Pack release for Windows 2003 currently available. Microsoft has confirmed that this will be included in the next Service Pack release for Windows 2003; Service Pack 3. (release date is not known at this time).  Step-by-step instructions:  1. Download http://www.microsoft.com/downloads/details.aspx?FamilyID=3ce0efe2-82ec-4134-9891-37efeab24e3a 2. Start a DOS prompt and go to the download folder, then type “WindowsServer2003-KB968389-x86-ENU.exe /b:SP2QFE” (without quotes) and hit Enter 3. Reboot PC 4. Check that you have the correct version of secur32.dll in Windows\system32. If the update has completed successfully, it should be 5.2.3790.4530 QFE .

Issue Lookup table for the AIC Analogue Input Configuration for different sensors. What types of sensors can be used with the MPM controller? Product Line EcoStruxure Building Expert Environment Multi Purpose Manager AIC Cause A lookup table is required for a sensor that is not listed in the AICs. What sensors can be used? Resolution For the Satchwell range (new generation or T range) STP660, STC600, STR600 series. Note the engineering output is Celsius.   For the TAC range STP100 series, STC100, STR100 series, STD100 series. Note the engineering units is Celsius.   For the Andover range STP500 series, STC500, STR500 series, STD500 series. Note the engineering units is Celsius.   AIC 1 to AIC 10 are empty Analogue Input Configurations, the remainder are pre-configured as below. For 10K Type II in Celsius use AIC 11 For 10K Type II in Fahrenheit use AIC 12 For 10K Type III in Celsius use AIC 13 For 10K Type III in Fahrenheit use AIC 14 For 1K PT1000 RTD Platinum in Celsius use AIC 15 For 1K PT1000 RTD Platinum in Fahrenheit use AIC 16 For 1K PT100 RTD Platinum in Celsius use AIC 17 For 1K PT100 RTD Platinum in Fahrenheit use AIC 18 For 1K NI1000 RTD Nickel in Celsius use AIC 19 For 1K NI1000 RTD Nickel in Fahrenheit use AIC 20

Issue Unable to successfully install Continuum keyless license software. Product Line Andover Continuum Environment Continuum Keyless Soft License Hasp Key Utility Sentinal HASP License Manager Cause Various causes. Resolution The following articles address issues with the Continuum Keyless license software. Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped Web based email should not be used to deliver Keyless Licensing information files (c2v) or activation files (v2c) How to determine the Continuum version, features and the Hasp license ID on a Keyless Continuum License Hasp Key Utility will not activate keyless license Version Error Getting Id. -- Key Id Not Found Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped

Issue Continuum general preferences show the system is configured to purge extended log data after X days, yet the extended log data is not purged. Product Line Andover Continuum Environment CyberStation Cause LAN System The SQL agent responsible for purging extended log data is missing or disabled. For Single User system see Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table Resolution LAN Systems (for Single User see Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table) In SQL Server Management Studio expand SQL Server Agent, then expand Jobs If ExtLog_Purge_ContinuumDB job is present verify its properties (see image below), make sure the job is enabled and properly configured to run.  If the job does not exist it can be recreated by following these steps: Close ALL Continuum Cyberstations/Web Client From SQL Server Management Studio run the following query against the ContinuumDB update ACDBVersion set ACDBVersion = 0 Run Continuum DB Initialization and update the database from the server tab, when prompted to run the ImportExport fixup tool select NO Verify the job was created then run Continuum

Issue Is there any way to get the Xenta Server trend log data without TAC Vista? How to get the Xenta Server trend log values from the web interface How to e-mail the Xenta Server trend log values Product Line Satchwell MicroNet, TAC Vista Environment TAC Xenta Server TAC Xenta 511, 527, 555 TAC Xenta 711, 731 Cause The TAC Xenta Server is installed standalone and TAC Vista can not be used to view or save the trend logs. However if you want to collect and store data from multiple trend logs on a regular basis we do strongly recommend using TAC Vista. Resolution There are two ways to get the trend log data from a Xenta Server (except for TAC Vista): 1. Manually copy the trend log values from the Xenta Server web interface In XBuilder, create a trend log page and drag the trend log to it Log in to the web interface and go to the trend log page Right click the trend log signal name and choose "view values" Copy/paste the values to for example Excel.   2. Forwarding the trend log data as an e-mail First make sure that the SMTP settings in XBuilder are correct. For troubleshooting on this, see Troubleshooting sending emails from a Xenta Server Create a receiver group and define one or more e-mail addresses to receive the trend log data. Highlight the trend log.  Under Log Data Transfer Settings, click the Receiver Group box, and select the Receiver Group list. In the Subject box, type a suitable subject. If desired, also type a suitable text in the Body box. In the Log Events Included box, click Yes to attach log events to the e-mail message. You must also specify when the log data is forwarded. For this, create a time object which you drag to the "send data" signal on the trend log. When the trend log data is forwarded, the receiver group e-mail addresses will receive the trendlog data as an attached .log file. For more information, see chapter 8.2.2. in the TAC Xenta Server – Web Server, Technical Manual

Issue When defining a Communication Port - Loytec the Network interface drop down is empty when the device is connected and recognized by LConfig. Product Line TAC Vista Environment Vista 4.4.0 - 4.5.0 Vista 5.x.x LoyTec NIC Cause Vista Server will only display Loytec devices connected to the computer when Vista Server is launched or started. If the NIC was connected to the computer after Vista Server was started it will not be visible until Vista Server is restarted. Resolution To populate the Network interface drop down with the currently connected devices: Shut down Vista Server Restart Vista Server If Vista is running as a service, then LConfig should function as a service also and service dependencies should be utilized to ensure that Vista Server (TACOS.exe) does not start until after LConfig.

Issue How to configure an alarm to see when controllers go offline. Environment Continuum Continuum Controllers Cause Want to see an alarm when controllers go offline / online. Resolution There is a default EventEnrollment already created that does this. To setup controller offline alarms, do the following: Go to the "Templates" folder in Continuum Explorer where a number of default EventNotifications are found. Open the "ControllerStatus" EventNotification and go to the Delivery tab. Add in the Workstations that where this alarm is to be sent too. Now any time a controller goes offline or comes back online, an alarm entry will be received at the Workstation entered in step 2. The other EventNotifications in this folder can be used to provide alarms on the subnet controllers status (InfinetStatus), IOU modules (IOModuleStatus), etc... ***Important: CyberStations detect controller’s offline status via a mechanism that periodically probes the controllers for their communication statuses; the default period for the probe is 60 seconds. If data is consistently being passed then no probe goes out. A Probe will go out if the controller has not heard from the other controller after a minute and no data has been passed. If an ACK is not received then it will try 3 more times with a 5 second delay after each retry. If it does not get a response after the 3rd retry then it will mark the controller offline and register a node failure alarm. If a controller goes offline for a short period of time (60 seconds or less) it is possible that not all recipient CyberStations will see the controller offline. If the CyberStation designated as the logging CyberStation for the ‘ControllerStatus’ alarm misses the offline condition the alarm WILL NOT be logged in the database.  

Issue How to add a calibration factor or offset value to an input using automatic scaling. Product Line Andover Continuum Environment Continuum Universal Input Cause If using the Conversion field to offset the ElecValue on an input that is using an automatic scale, the resulting value will not be calculated properly. Resolution For this to function with an input using an automatic scale we need to setup an InfinityFunction to do the scaling for us and then add/subtract our offset from this result.   1. Create a new InfinityFunction in the controller called “IPConvert” 2. Paste the below code (between the lines) into the function and save it. ======== 'This InfinityFunction must be called from the conversion line of the input 'This InfinityFunction will allow an offset to be applied to a universal input 'Example Conversion line in the Input - IPConvert(EngScaleTop, ElecScaleTop, EngScaleBot, ElecScaleBot, -1) Arg 1 EngTop 'Engineering Units -  Top of Scale Arg 2 VltTop 'Voltage -  Top of Scale Arg 3 EngBot 'Engineering Units -  Bottom of Scale Arg 4 VltBot 'Voltage - Bottom of Scale Arg 5 Offset 'Amount to Offset returned value Numeric Slope, C Slope = ((EngTop - EngBot) / (VltTop - VltBot)) C = EngBot + (Slope * (minimum(VltTop, maximum(ElecValue, VltBot)) - VltBot)) Return C + Offset ========== 3. Go to your inputs on that controller that need to use this function. 4. confirm that the auto conversion fields have been set to the scale range you require. 5. type the below into the conversion field, replacing the “-0” at the end with whatever offset is required. IPConvert(EngScaleTop, ElecScaleTop, EngScaleBot, ElecScaleBot, -0)

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 Prior to XBuilder 5.1.1, it was not possible to change the type of an Xenta Server in an XBuilder project once it had been created.  Sometimes there is a need to move the project to a different type of Xenta Server without losing all the links and bindings within the project. Environment Xenta Server XBuilder 5.1.0 or earlier Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In XBuilder 5.1.0 or earlier, it is not possible to edit the Xenta Server type in the network pane of the XBuilder project Resolution Upgrading to Vista/XBuilder 5.1.1 or later will allow you to easily change the device type directly from XBuilder.  Note that this must be done from an XBuilder project that is saved to the computer. If the project is in a Vista database start by opening the XBuilder project, clicking on File > Save as and then save it to the computer. Then, close XBuilder, reopen XBuilder and open up the saved copy of the XBuilder project from the PC. In the XBuilder Project menu select 'Change Target type...'.  Choose your preferred target device from the drop-down list.   If it is not possible to upgrade, the following instructions allow an XBuilder project to be transferred to a different type of Xenta Server without losing graphic bindings or bindings between objects on the System pane and the Network pane.  The one proviso is that the target Xenta Server's hardware must be able to support any network defined in the source project and have the same or better Menta and User graphic capabilities.   There are many different combinations of Server types and BMS platforms that these instructions could apply to in general.   The example given here transfers an Xenta 555 project to an Xenta 731.  The Xenta 555 has a Lonworks network and a Modbus network and is part of a Vista database.   Creating the Xenta 731 in the Vista database: Open the Vista database containing the Xenta 555 project. Right-click on the 555 and select Edit from the dropdown menu. The XBuilder project opens.  Keep this open for the following steps. In the Vista database create a new Xenta 731.  The name is not important but it should be similar but not identical to the 555 it will replace. Transferring the Lonworks network to the Xenta 731: In Vista, drag and drop the LON network from the 555 to the 731. Right-click on the 731 and select Edit from the dropdown menu. The 731 project opens in a new instance of XBuilder.  Rename the default folder in the system pane to the same name as the top level folder in the 555 project. In the 731 project right-click on the LON object in the Network pane.  Select 'Refresh network from TAC Vista'. Transferring the Modbus network to the Xenta 731: In the 555 project, right-click a Modbus device and select 'Edit Device template' When the device editor opens, select File | Save as.. Save the file in the default location with the default name. Repeat steps 2 to 3 for all Modbus devices in the network. In the 731 project recreate the Modbus network using the templates just saved.     Transferring the System objects to the Xenta 731: In the 555 project, right-click an object below the top level folder and select 'Copy'. Move focus to the 731 project, right-click on the top level folder and select 'Paste'. Repeat steps 1 and 2 for each object and folder below the top level in the 555 project.  Selecting a folder also selects all the objects and folders beneath it.  Although it is possible to copy the top level folder in the 555 project, it is not possible to paste it into the 731 project. Graphics bindings are retained and the reference paths are automatically updated with the new network tree i.e. 'TAC_Xenta_555' is replaced with 'TAC_Xenta_731'. Some object bindings will be broken e.g. Time objects.  These must be rebound manually. When all objects have been copied across and rebound if necessary, close the 555 project. Deleting the Xenta 555 and downloading the project to the Xenta 731: In the Vista database, delete the Xenta 555. Generate the 731 project.  There will be a warning message offering to copy the original TGML files to the new default location.  Select 'Yes'. The 731 project should now generate without errors. Download the project to the Xenta 731.   If the 555 only contains a Modbus network, a similar methodology will also work with standalone 555 and 731 projects.  

Issue What is the mechanism used by the Continuum system to determine the communication status of third party BACnet devices? Product Line Andover Continuum Environment CyberStation bCX BACnet Cause To maintain the communication status of third party BACnet devices Resolution Continuum sends a read property message to read the vendor id from the device once a minute by default (or whatever the probe time is set to), as long as a timely response is received from the device Continuum keeps it online, if no response is received the device will be marked OFFLINE (after a retry) Once a device is marked OFFLINE Continuum will perform a WHO-IS once a minute (ARP if CyberStation) until an I-AM is received which will cause the device to be tagged back online, once the device is back online Continuum will resume probing the device via the read property message once a minute. Note that Continuum allows several probe options for BACnet devices, the behavior explained above is for when the probe type is set to 'Probe' ProbeOnDemand - Probing does not occur unless a communications transaction with the target device fails. Once a transaction fails then probing occurs at the interval specified in Probe Time until the device comes back online. The advantage is that additional requests to the controller fail immediately. The disadvantage if that node failure is not detected  until a CyberStation application needs to communicate with a controller.  ProbeOff - Probing does not occur. The advantage is that there is never probe traffic to the device. The disadvantage is that each request to the device fails only after the transaction times out.

Issue When creating a Modbus device template in XBuilder Device Editor which Modbus register data type should be used? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Modbus Register Bitmask Cause Lack of consistency between Modbus slave manufacturers there is a large number of data formats that can be selected. Each register format interprets the value differently based on byte order or purpose of the specific bits. Resolution Consult Modbus slave product documentation Use trial and error to find the correct register format. Perform communication logging to capture the raw data and compare with a known value to determine the format. As a tool to assist with these steps please consult the Definition of Modbus Registers.