Issue In the Niagara G3 ASD Device Manager, MicroNet 2000 devices can not be discovered. Product Line TAC IA Series Environment I/A Series G3 ENC-410 or ENC-520 MN-ASDI integrator with attached MN-FLO / MN-FLO3T / MN-HPFC devices Cause It appears that the ASD Device Manager checks all MN-ASDI integrators, with DIP switch addresses 1-7, for devices in the range of 1-31 under them. Resolution When using the ASD Device Manager to discover MicroNet 2000 devices (MN-ASDI integrators on the ASD bus, and the controllers on the U-buses under the integrators), set the Start Address and End Address in the range of 1 -31. For example, assume there is an MN-ASDI with DIP switch address = 2, and on the U-Bus under the integrator there is an MN-HPFC with DIP switch address = 3. In the Discovery Filter, set the Discover Mn2k flag= true, Start Address = 1, and End Address = 31. The Device Manager will put a MnHPFC_35 object and a MnGen_32 object in the upper pane. The ASD Device Manager assigned an ASD device address = 32 to MN-ASDI, and an ASD device address of 32+3 = 35 to the MN-HPFC. It appears that the ASD Device Manager checks all MN-ASDI integrators, with DIP switch addresses 1-7, for devices in the range of 1-31 under them, and then assigns an ASD device address in the range of 32 – 224 to the integrators, and in the range of 1-254 to the MN-FLOs and MN-HPFCs.

Issue NL220 Data base will not open and an error, "Database cannot be accessed you may be in single user mode NS #22" is produced. Product Line TAC Vista Environment LNS LonMaker Vista NL220  Cause Administration rights are not granted to the Microsoft server computer user preventing the database from opening. Resolution To work around admin access from IT: Close NL220 Right-click Relaunch using "Run as Administrator"

Issue How many Vista logs can Vista 5.1.9 handle? Product Line TAC Vista Environment Vista Server 5.1.9 Cause There are no official limitations or documents on how many trend logs you can add to a Vista server. The following items listed in the resolution will assist in determining the performance of the Vista Server Resolution The following items listed are the restrictions that limit the performance of the Vista Server: The DSS writer can handle around 40 logs per second. Vista server trends are often limited by how many values per second the Lon network interface can handle. (Typically 40 for a Loytec port and 10-15 for 911 or LNS port in Vista). Size of the SQL database, 100GB for Vista trend logs is a very large SQL database. Vista can handle this provided the computer hardware is of a high-performance nature, and the SQL database and computer hard disk must have regular maintenance performed.

Issue Needing to monitor a controller's online or offline status. I/NET AMT will generate a station lost alarm when a controller is offline, however it is sometimes desired to have a point that can be monitored to alarm as well. Product Line TAC INET Environment subLAN Controller Lan; C-LAN Xenta 527 Cause I/NET AMT will generate a Station lost alarm when a controller is offline, however it is sometime desired to have a point that can be monitored to alarm as well. Resolution Monitoring SubLAN Controllers Connect to the Sub Lan Interface Controller (7798, 7793) Create an internal DA point called LLSSPP_Offline, with LLSSPP being the address of the subLAN device Add a Calculation to the point LLSSPP_Offline Enter this Calculation: OLD(P0) Set P0 to equal any External input point the subLAN device LLSSPP Click okay The result of this calculation is that the point will equal 1 whenever the referenced point goes old Monitoring Controller LAN or C-LAN devices Connect the Controller you wish to monitor Change an external point's Global Level to "Link" (If a point already is set to system, use it.) Connect to a second Controller on the same physical C-LAN (for best results use one physically closer to the NPR or Tap) Create an indirect point referencing the point created in step 2 Create an internal DA point called LLSS_Offline, with LLSS being the address of the controller Add a Calculation to the LLSS_Offline point Enter this Calculation: OLD(P0) Set P0 to equal the indirect point created in step 4 Click OK The result of this calculation is that the point will equal 1 whenever the indirect point goes old, which should only occur when the controller is offline.  Monitoring NPR or Xenta 527 devices Connect to a Controller under the device you wish to monitor Change an external point's Global Level to "system" (Use an existing global point if available) Connect to a second Controller under the device you wish to monitor Change an external point's Global Level to "system" (Use an existing global point if available) Connect to a controller underneath a different NPR or 527  Create an internal DA point called Link _LL_Offline, with LL being the Link address of the 527 or NPR being monitored Create 2 indirect points referencing the global points created in steps 2 and 4 Add a Calculation to the Link _LL_Offline point Enter this Calculation: OLD(P0)&OLD(P1) Set P0 and P1 to equal the indirect points created in step 7 Click okay The result of this calculation is that the DA point will equal 1 whenever both of the referenced indirect points go old.  This should only happen when communication is interrupted to both controllers indicating the most likely cause is the NPR being offline. Please be aware of other potential causes of 2 controllers on the same link going offline. Examples include power circuit failure or cut wire when selecting which controllers to monitor. 

Issue During SQL install portion of Continuum installation the following error message is received. "SQL Express is not installed properly. Please contact technical support representative." Product Line Andover Continuum Environment Continuum Cyberstation (All Versions) Microsoft SQL Express (Version dependent upon Continuum version) Cause Bit Locker has been installed on the system to which Continuum Cyberstation is being installed. Bit Locker enforces specific password requirements across all Microsoft Windows products. Find the SQL installation log at C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20190627_092341\Summary_WTUSLVSE076617L_20190627_092341.txt *NOTE* The parent folder of the log will include the date and time of the installation. The log file name format will be Summary_(your computer name)_date_time.txt At the bottom of the log, you will see an Exception summary which gives full detail of what the error is: "Exception summary: The following is an exception stack listing the exceptions in outermost to innermost order Inner exceptions are being indented Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException Message: The specified sa password does not meet strong password requirements. For more information about strong password requirements, see "Database Engine Configuration - Account Provisioning" in Setup Help or in SQL Server 2012 Books Online. HResult : 0x84b40000 FacilityCode : 1204 (4b4) ErrorCode : 0 (0000) Data: SQL.Setup.FailureCategory = InputSettingValidationFailure DisableWatson = true Stack: at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs) at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId) at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream) at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context) Inner exception type: Microsoft.SqlServer.Configuration.SqlEngine.ValidationException Message: The specified sa password does not meet strong password requirements. For more information about strong password requirements, see "Database Engine Configuration - Account Provisioning" in Setup Help or in SQL Server 2012 Books Online. HResult : 0x851a0013 FacilityCode : 1306 (51a) ErrorCode : 19 (0013)" Resolution Update or use password for new database that meets the minimum standards of: 8 Characters 1 Capital letter 1 Numerical character 1 Special character (!,@,#...) 1 Lowercase letter This will allow SQL Server to be installed

Issue When using PIN code or PIN with card number for door entry, the door does not open. A time out message "Entry PIN t/o" is shown in AMT. Product Line TAC INET Environment I/NET PIN Pad Reader Cause There may be two causes of this message: There is an output format for PIN Pad called burst format. There are several types of burst format available, for example 4 bit, 8 bit, 26 bit etc. For I/NET, it only accepts 8 bit and 26 bit type. If the burst format isn’t correct, there will be "Entry PIN t/o" message appeared, which means timeout for waiting for PIN entering. The digits of PIN are less than 6 bits. Resolution The following solutions are recommended for the two causes of this issue: For cause 1, the burst format of the PIN pad should be changed to 8 bit or 26 bit (Usually using 8 bit. If the extended PIN function is needed, 8 bit type should be chosen). For HID reader, there is a configuration card to change the burst format to specific type. Refer to HID relative documentation. NOTE: In most instances the Configuration Cards must be presented to the reader within 5 seconds of powering up the reader. For cause 2, if the digits of PIN are less than 6 bits, a "#" button needs to be pressed after entering the PIN. If this solution can't work, you can change the PIN to 6 digits by adding "0" ahead of the PIN. For example, the PIN is "3325", the PIN entered should be "003325".

Issue Script programs in b3 controllers will not autostart after reboot of the controller Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation AS-B Cause The program is not configured to autostart in StruxureWare Building Operation. Resolution In the Properties of the program object, ensure that the Autostart field is set to True. For further information on these properties please refer to Webhelp

Issue How is the mac address (ethernet id) of the Continuum master controllers calculated? Product Line Andover Continuum Environment bCX CX9200 CX9400 CX9900 CX9600 CX9702 CX9680 ACX5720 ACX5740 Cause Mac address must be unique. Resolution The controller mac address is assigned at the factory. The first three numbers (0:40:11) are fixed and represent the manufacturer, the next three numbers ar5e the unit's serial number converted to hex. Example: Manufacturer = 0:40:11 SN = 557746 which converted to hex = 882b2 Mac address = Manufacturer + SN ~ 0:40:11:8:82:b2   Windows calculator has a programmer mode that can be used to convert from decimal to hex.

Issue I/NET - Locating partners. SSL - How are SmartStruxure Lite products purchased in the UK? Product Line EcoStruxure Building Expert, TAC INET Environment Partner I/NET SmartStruxure Lite Purchase SSL Cause I/NET - Require engineer to visit for maintenance, servicing, installation or advise. SSL - There is confusion how SmartStruxure Lite products can be purchased. Resolution I/NET Click here to be linked to the available UK I/NET partner list. SmartStruxure Lite The SSL equipment requires training to install and programme correctly, therefore these products are installed, programmed and commissioned by trained Schneider Electric Partners. These products can only be purchased through the Partner network. To locate a Partner, use the following link, select SmartSruxure Lite and browse to the correct location on the map: Schneider Electric Partners

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.

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 What is the purpose of the Max Info Frames attribute in a Continuum BACnet controller? Product Line Andover Continuum Environment BACnet MS/TP, MaxInfoFrames Optimizing MSTP Cause Information on the Max Info Frames function. Resolution The Max Info Frames setting on the BACnet controller object editor specifies how many messages that the controller can send out to other controllers when it has the token on the network. For instance, a B3 controller has a default of 2 for this setting. If it receives the token on the MSTP network and it has 5 COV or Event notifications to send to other controllers or workstations, it will send the first 2, and wait until it gets the token the next time around and send 2 more, etc. The BCX controller has a default of 8 for Max Info Frames. This setting is changeable through the BACnet controller editor, however care should be taken not to increase it to too large a number. The larger the setting, the more time that particular controller can hold the onto the token, which in turn denies other controllers on the network the capability of sending out their data in a timely manner. It should only be adjusted if there is a definite need for increased messaging, but on the MSTP network it is not recommended to go above 10, although we do not limit the value. In a Cyberstation Version 1.8 or above the setting can be made on the details page of the BACnet controller device editor. If adjustment of this parameter is done using any Cyberstation prior to version 1.8, the setting will not stay at the new value after a controller reload from the Infinity side, it will revert to it's default. You will need to create a PE program in the controller to set this parameter to the desired value if it is reloaded. The program should be autostart and fallthru, and use the "Writeproperty" keyword to set the parameter. The syntax should be as follows: Line SetMaxInfo WriteProperty ("Full Bacnet path name of controller", MaxInfoFrames, "New Value") Stop

Issue When starting TreeTech communications one or more error messages similar to the following will be displayed in the "... Licensing System Error" window. N8K PTP ... License Expired N8K Serial TLP ... License Expired N8K Ethernet TLP ... License Expired DMS PTP ... License Expired DMS Serial TLP ... License Expired DMS Ethernet TLP ... License Expired Product Line TAC IA Series Environment Windows 2000 or Windows XP (TreeTech 1.x) Windows Vista or Windows 7 (TreeTech 3.0)  Cause No license installed for the IOS (I/O Support module) required for communications between the TreeTech software and the field panel.  Resolution Use the "Purchase WIB Software" to purchase a license for each of the required IOS modules. The following modules are available: IOS-SRL Serial I/O server for NETWORK 8000 and DMS IOS-NW8-ETH NETWORK 8000 Ethernet I/O server IOS-DMS-ETH DMS Ethernet I/O Server (The following license is available only to partner offices for use on the engineer's desktop and laptop computers) IV-DEMO-CDE InVue Demonstration Package (includes Tree-Tech and all IOS drivers)   After adding the desired modules to the license form, click the "Accept Order" button and select the option to save the order to a file. The saved file may then be emailed to IASeries.WIB_Order@schneider-electric.com for processing.

Issue Point under the Application folder of MP-x device shows error "Contains unresolved BACnet reference" Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation IP-IO Cause Incomplete entry in point's BACnet priority array. The screenshot below shows the XML file obtained from exporting the point, as it can be seen, 'Priority16' is missing the 'Type' section. Resolution Perform the following steps to correct the problem: Export the point out to a file. Delete the point. Import the file created at step 1, once the point has been re-created via import the unresolved error is gone. NOTE: There is no need to make any modifications to the XML file, it can be imported as is, the system will automatically correct the incomplete entry for priority16.

Issue When trying to install TAC Vista and running the installation file the only option available in the installation wizard is to uninstall TAC Vista. Product Line TAC Vista Environment Vista server Cause A registry key which is not taken away when uninstalling TAC Vista is indicating to the installer that Vista is already installed. Resolution NOTE: Serious problems can occur if you modify the registry incorrectly. Make sure that you follow these steps careful. Open the Registry: go to Start > Run and type "regedit" Remove the folder for TAC Vista Server under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall The Vista folder will contain "TAC Vista Server" in the "Display Name" field and can be found by selecting each folder.

Issue The path to the templates and libraries is not documented Product Line EcoStruxure Building Operation, TAC Vista Environment Graphics editor Cause In order to use your own color and gradient templates and to copy component and snippet libraries you need to know the path to these files and folders. Components and snippets can preferably be managed directly through the graphics editor. Resolution In TAC Vista The libraries and templates are one and the same for all users: Colors and gradients: C:\ProgramData\TAC Graphics Editor\Brushes Components: C:\ProgramData\TAC Graphics Editor\Components Snippets: C:\ProgramData\TAC Graphics Editor\Snippets In SmartStruxure Each user has their own set of libraries and templates: Colors and gradients: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Brushes Components: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Components Snippets: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Snippets

Issue Is it possible to install TAC Vista Webstation on a PC that does not have Vista installed? Product Line TAC Vista Environment Vista Webstation 5.x.x Cause For security reasons some customers need to have TAC Vista Webstation installed on a PC located in the DMZ. The purpose of a DMZ is to add an additional layer of security to an organization's local area network (LAN); an external attacker only has access to equipment in the DMZ, rather than any other part of the network. Resolution TAC Vista Webstation must be installed on a PC where TAC Vista server is already installed. To resolve this you can install an empty Vista server on the PC and connect it to the Vista network together with the Vista servers already installed. After that you can install Webstation on the PC with the empty Vista server.

Issue How do I change out a failed B4920 or BACnet BCX controller? Product Line Andover Continuum Environment B4920 BACnet BCX controller Cause Failed device Resolution Place Cyberstation Offline. Edit existing B4920 or BCX Controller object on the Infinity side and note the following: ACC Net ID BACnet Device ID Network ID - UPD Network ID - Comm2 (MS/TP network ID) IP Address, Subnet Mask, Default Router (Gateway) Address Name of the controller Physically disconnect power and MS/TP data cables from existing B4 or BCX Controller. Remove existing B4 or BCX Controller. Install replacement B4 or BCX Controller. Connect MS/TP data cable to the replacement B4 or BCX Controller. Connect power to the replacement B4 or BCX Controller. Use a web browser to connect to the login page of the B4 or BCX at IP Address 169.254.1.1. Use the controller configuration web page to configure the following values: ACC Net ID (enter the value from Step 2 a) BACnet Device ID (enter the value from Step 2 b). This is very important - do not use the new controller's serial number or you will likely have trouble communicating with the new controller on the BACnet side.  BACnet Network ID - UDP (enter the value from Step 2 c) BACnet Network ID - Comm2 (enter the value from Step 2 d) IP Address, Subnet Mask, Gateway Address (enter the values from Step 2 e) Name (enter the value from Step 2 f) If this device is a BCX, the user will want to reset the BACnet MAC ID - Comm2 value, if that value was non-zero in the device being replaced (there is no record of this value in Cyberstation). Click the Submit to Controller button then Commit Changes button and then CommitChanges/Restart Controller button. Allow sufficient time for the controller to restart. In CyberStation, on the Infinity side, edit the controller object and change the serial number to that of the new controller. Save the object.   Go back to Online mode in CyberStation. The new B4 or BCX should now be online in the Infinity view. Reload the B4 or BCX Controller. Verify existing Points and Programs are running correctly. Perform a “Backup to Flash” operation on the B4 or BCX Controller. Check that the controller is online in the BACnet side. Note that the Device Node ID on the BACnet side is the serial number of the old (replaced) controller. This is as it should be since we do not want to create a new BACnet device; we just want to replace the controller hardware. Edit objects on the BACnet side to verify that there are no errors.   Test alarms, graphics, communication to b3's/3rd party devices, etc. 

Issue Getting "Failed CreateDNWACServer. Cause: Object reference not set to an instance of an object. URL: “http:///DNWACServerFactory/WACServerFactory.soap" when trying to open a graphic through WebPinpoint with Continuum version Product Line Andover Continuum Environment Windows XP Windows Vista Webclient Windows Server 2003 Windows Server 2008 Cause Configuration of mime types and correct path to the file must be made Resolution Make sure Microsoft .Net 2.0 is not installed as this will cause the above error message. We did not support Microsoft .Net 2.0 until the 1.74 release. Check to make sure that on the machine that the browser is being run from has the NetBIOS over TCP/IP enabled. This can be found in the advanced properties of the TCP/IP settings on that machine. Make sure that “Directory Browsing” is enabled for the NewGraphicsFiles in the IIS configuration. This can be found by running the IIS Service manager and expanding the explorer until you see the NewGraphicsFiles virtual directory. Right-click on the virtual directory and select properties. There will be a checkbox for “Directory Browsing” in the middle of the page, make sure this is selected. On XP add the aspnet to the DNWACServerFactory folder security tab on the folder.

Issue Is it possible to use the TAC Xenta 102B device with room unit STR150? Product Line TAC Vista Environment STR150 TAC Xenta 102B Cause It is possible to use STR150 together with the TAC Xenta 102B device with system program 1.20 or higher. Resolution To use an STR-150 on a TAC Xenta 102-B controller, set nciAppOption bit 14.