Building Automation Knowledge Base

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 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 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 The status of a Forced BACnet value is not reflected in a Graphic or the Watch Window. Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause This is functioning as designed. It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. Resolution It was designed so that the "Forced" status for BACnet values would not be displayed in graphics or the watch window. For a workaround using a PE Script program to show the forced icon for a BACnet value see How to show the forced icon for a BACnet value in a Graphic. In EBO version 3.0.1 and later this issue only occurs on internal BACnet points, points which are located in the Application folder under the BACnet interface for the SmartX server.

Issue Is a Vista license necessary for I/NET Host tool features or is the I/NET CD key sufficient? What is the difference in the I/NET Integrated and I/NET Security licenses? Environment Vista Server I/NET Host Tool Cause The I/NET Host tool requires a Vista license file to run. Certain editors and features in the I/NET Host Tool are common to both the Integrated and Security license. Some features are specific to the Integrated or Security license. To have all of the features purchase of both licenses is necessary. AMT is not included with the I/NET host tool product as Vista is expected to handle alarms messages and transactions Common Features System features Change password Connect/Disconnect Logon/Logoff Quit Work offline Host features Host configuration editor Host password editor Host phone numbers editor Host software restore editor Netcon function editor Network configuration editor System view Tap features Host, link, and site tap configuration Site tap remote configuration Site tap save/restore Controller features 7720 configuration editor Action messages summary Alarm extension editor Calculation editor Control description editor Conversion coefficient editor DCU configuration editor DCU save editor DCU restore editor DCU password editor DPU configuration editor Engineering units editor Event extension editor Event sequences summary I1/I2 state parameters editor Lighting circuits editor Lighting zones editor LCD page definition editor Lookup table editor MCU configuration editor MR configuration editor Resident point editor Special days editor State descriptions editor Time schedule extension editor Trend extension editor Trend plot view dialog Summaries Configuration summary Controller summary Disabled points summary Off-normal points summary Reporting features SevenReports (operates in view-only mode if no I/NET CD key is installed) I/NET Integrated only Controller features Consumption extension editor DDC modules summary Demand control extension editor MR DDC summary Override billing equipment mapping editor Override billing extension editor Override billing parameter editor Runtime extension editor Temperature control extension editor Unitary control configuration editor Unitary control extension editor I/NET Security only Controller access features Elevator extension editor DCU AIC editor Door extension editor Personnel schedules SCU parameters editor Host access features Access control options editor Access control wizard AIC editor Door extension editor Groups editor Individuals editor Key translation editor Personnel schedules Pin generation dialog Recycle bin SCU editor Tenant editor User search Summaries Door tenant summary Resolution Purchase of an I/NET Host Tool license is necessary for the integration with Vista Workstation to function. Use the feature list to determine if only one license or both licenses are required by the customer. Attached is the PA for all the required software Here

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 attempting to detach an AS, PCT continues to shown the server as being attached to the ES.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool 1.x (PCT) Cause In PCT, when an AS is detached from its parent ES, the ES name still appears in the Added to parent column of the Servers list. Resolution Once the AS has been detached from an ES it can be added to another ES though Workstation using the following steps even though the "Added to parents" column shows otherwise.   To create a SmartX server In WorkStation, in the System Tree panel, select the Servers folder. On the File menu, point to New and then click Server . In the Create Object wizard, in the Name box, type a name for the SmartX server. In the Description box, type descriptive information about the SmartX server. Click Next . In the Configure IP/DNS Address and Port page, in the Address box, type the IP address or fully qualified domain name of the SmartX server. Notice If the SmartX server has been assigned a dynamic IP address, use the fully qualified domain name of the SmartX server instead of the IP address. In the Protocol box, select a protocol for the SmartX server. For more information, see EcoStruxure BMS Server Communication . In the Port box, enter a port number. Click Create. In the Log on dialog box, in the Password box, type the custom password if required. Click OK.   For more information, see Creating a SmartX Server

Issue In the Xenta Servers, it is possible to set the communication port to RS232 or RS485. In EBO this is not possible on the Automation Server (AS) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server  Xenta 500 Xenta 700 Xenta 900 Cause The AS serial ports are RS-485, not RS-232. Resolution There are two solutions to consider when Xenta is using an RS-232 connection: If the connected device also has a RS-485 connection switch to that. (Optionally replace the device with one that has RS-485.) Use a RS-232/RS-485 converter. The converter must have automatic data direction detection and control on the RS-485 side, since our Automation Server devices have no RTS signal (to enable the transmitter) available externally.

Issue Running an I/NET Seven report and only seeing the first 500 people or doors in a system. Keyword search: Crash when an attempt to open, Crystal Reports, and failure. Product Line TAC INET Environment I/NET system and desire to run reports over a lot of data Cause The Crystal Reports that I/NET is using has a default value of 500 objects to be listed in a report. If you require more objects to be listed in a report, this requires a windows registry change to do this. Resolution Note in the attached document the registry location may change slightly based on the version of I/NET and SevenReports installed version.   If unsure or the locations cannot be found search for the following registry keys: BrowseTimeout - This entry controls how long, in seconds, the Info Report Designer will browse for records. MaxNBrowseValues - This entry controls how many unique records the Info Report Designer will browse before stopping and displaying the records found. For the Release 2.40a and above running the NON_RDC release HKEY_CURRENT_USER\Software\Business object\Suite11.0\Crystal Reports Designer\ For the Release 2.41 and above running RDC version: HKEY_CURRENT_USER\Software\Business object\Suite11.0\Crystal Reports Designer Component\ In the Crystal Report terminology, an object could be people or doors, in which case make the registry change based upon the largest number you have. For example, if a site has 5000 people and 500 doors, set the registry to accommodate 5000. The steps required to make these changes are in the Crystal Report Tech support paper linked to this article.

Issue 'Program interface does not match previously defined interface' when downloading/commissioning a Xenta 400/300 controller. NS, #59 Environment Vista System Plugin TAC Xenta Programmable Controllers LonMaker/NL220 Cause You get this error if you have 2 controllers that are using the same device template (XIF file) and one is system program version <3.5 and one is >3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. Controllers can share device template even if they have different applications as long as the are using the same SNVTs. Different types of Xenta controllers can also share the same XIF file. Resolution To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and it’s own template. Open the application form System plug-in by right clicking on controller and select configure-edit. To give the application a new XIF either add a “dummy” SNVT or go to device configuration and uncheck the tick box for “XIF header generated according to LonMark standard” Hit F12, select commands and generate. F12 again and save the application to the hard drive by selecting File-save as. In system plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and TAC Database. If you are asked to resynchronize, do so. In Menta create a new application with just one PVR block in it. Go to the controller, connect a serial cable and download the small application that you just created. Go back to the system plug-in and download the controller. Commission in LonMaker.

Issue A Network 8000 LNC-100 cannot communicate to LON devices under it even though all the devices can be accessed with WorkPlace Tech or a LON commissioning tool. Product Line TAC IA Series Environment NETWORK 8000 LNC-100 LON devices WorkPlace Tech Cause If the LON network is known to be good and otherwise functioning, this issue indicates a problem with the LON interface in the LNC-100. This is typically caused by accidentally attempting to commission the LNC-100 using LonMaker or other LON commissioning tool. Attempting to commission the LNC-100 will result in its LON interface being set into a network state called HARD - OFFLINE. Resolution The condition can be corrected using the Echelon NODEUTIL program to set the interface network to the required CONFIGURED - ONLINE state. NodeUtil can be downloaded from The Exchange Download Center. After downloading NodeUtil to your computer, open a command prompt window and launch NodeUtil in that window.  After launching NodeUtil, perform the following steps to correct the problem. Press the F key to execute the Find function.  This will browse the connected LON network for all attached LON devices.  In the list of found devices, the LNC-100 will be identified with the program id "C 1 11.0A". Press the G key to execute the Go To Device function.  Enter the device number of the LNC-100 (program ID "C 1 11.0A") as displayed in the list of discovered devices.  The device menu will then be displayed. Press the S key to display the status of the device.  Typically 17 lines of status information are displayed followed by the "Device Status" menu.  Press Y to clear the error status.  The "Device State" line will usually show a state of either Configured, Off-line or Hard, Off-line. Press the  M key to change the device mode and state. After selecting the M command, the list of mode options is displayed.   Press the S key to select the State menu. The list of State options will be displayed.  Press the C key to set the device to the Configured state. A status message will be displayed followed by the DEVICE prompt. Press the M key again to display the Mode options then press N to set the device into the OnLine mode. A status message will be displayed followed by the DEVICE prompt. Press the S key again and verify that the Device State is now Configured, On-line. Press the D key to display the domain address table of the LNC-100.  One or two lines of device domain address information will display.  If two domain addresses were defined in the SYS: SIM block of the device, two lines of information will display, otherwise only one line will display.  Verify that the address information (Subnet, Node and Domain ID) are as set in the SYS: SIM block. The data entered for Domain0, Subnet0 and Node0 will be displayed on the Index 0 line. The data entered for Domain1, Subnet1 and Node1 will be displayed on the Index 1 line. Press the E key to exit the Device level and press the E key a second time to exit the program.

Issue Need the Part Number for a Xenta 527 or 527-NPR Environment I/NET Vista Cause There are 2 Varieties of the Xenta 527 available: The Xenta 527 and the Xenta 527 NPR. While these devices share some similarities, there are some key differences. Resolution There are 2 Varieties of the Xenta 527 available. The Xenta 527 and the Xenta 527 NPR. The Xenta 527 is sometimes referred to as the Xenta 527 - Web Server.  This part can be used on I/NET systems, or I/NET systems that integrate with Vista.  The Xenta 527-NPR is use on I/NET systems.  It is a scaled down version of the standard Xenta 527 that will only provide the functions needed for I/NET.  This serves as a direct replacement for existing NPR devices. The Part numbers for these devices are as follows: Xenta 527 (Web Server) - 007308200 Xenta 527 (Web Server) Package of 3 - 007390130 Xenta 527-NPR - 007308210

Issue Installed the tool under Windows 10 but was unable to assign a port in the tool's connection settings because there are no ports showing in Windows Device Manager. Product Line Andover Continuum Environment RoamIO2 BACnet Service Tool Cause Windows legacy hardware configuration. Windows 10 by default does not include the legacy ports. Resolution Legacy ports must be added to the Device Manager. 1. Open Device Manager from Windows Control Panel. 2. Select 'Action' then 'Add legacy hardware' or Go to "Start" and type hdwwiz.exe then press Enter 3. Next 4. Next 5. Next 6. Select 'Ports (COM & LTP) then Next 7. Select Microsoft/Standard Serial over Bluetooth link then NEXT 8. Complete the legacy hardware installation, Device Manager will then show the ports. 9. In the Service Tool select the appropriate port.   When the connection has been established from Windows PC to RoamIO2 device, the BlueTooth settings in Windows will indicate 'Connected'  NOTE that if it only indicates paired there will be no data transfer even though the blue LED is illuminated on the RoamIO2 device. (see screenshot below)

Issue Is there a template to help create the custom AccessFormat array? Product Line Andover Continuum Environment Creating a Custom Card, Access Format array for non standard Wiegand formats Cause As there is sometimes confusion on the way that the bits are counted from 0 or 1 and how to use a Plain English program to initialize the array an easy way to lay out the data would be useful. Resolution The attached Excel spreadsheet works as a template to enter the Access Format data. Click here to download Format Template.xls. Enter your required Wiegand format bit definition in the box at the top, then this will allow you to define the numbers to go in the AccessFormat array lower left, which automatically fills in the example program on the right. Also see: Setting up a custom Wiegand format access cardfor information on setting up an AccessFormat array. Determining Custom Card formats on Deciphering Custom Card formats. What is the range of Wiegand Card numbers and Site Codes I can use on Continuum? on maximum card numbers.