Issue Dumping or reloading a NetController using HyperTerminal. Environment Windows HyperTerminal CX9900 CX9400 CX9200 Command Terminal Configuration Guide Infinity and Continuum Window Interface Cause Not known cause. Resolution Click here for instructions on using HyperTerminal to dump or reload controller.  For full details on using the Window interface as used on Infinity and 1st Generation Continuum controllers, you can download the Command Terminal Reference Guide.

Issue Understanding and configuring controllers for Access Control using SystemStatus and AccessServer system variables. Product Line Andover Continuum Environment Access Control CX9702 ACX57xx Netcontroller Netcontroller II Cause Operators can be unsure what the various values for SystemStatus and AccessServer are and what they need to be set to for successful access control. Resolution 1. SystemStatus The first thing to realize is that there are four different modes that an Access controller can be set to, the SystemStatus indicates the mode controller is currently in. This is an Access-only system variable and will default to NoDatabase if left unconfigured. These four values are as follows: Normal — The controller is working normally. NoComm — Local controller has lost communications to the Workstations configured as Primary and Secondary Access Servers. NoDatabase — The Access server and the local controller have been reset or have otherwise lost connection to the database to check access card numbers and personal identification numbers (PINs). Can also indicate that the local controller has lost comms to the Access Server and has no local personnel database to authenticate to. ColdStart — Indicates the Access Controller SystemStatus initial value, before any door has been configured. The sequence for how SystemStatus gets set is as follows: On a ColdStart if the AccessServer = 1-190 it is set to NoDatabase when the first door is configured. When CyberStation finishes the personnel distribution, it explicitly sets the value to Normal.  On a ColdStart if the AccessServer  > 190 it is set to Normal when the first door is configured and the controller is communicating with the Primary and/or Secondary Access Server workstations. Note: Upon initial configuration, or a restart, the CyberStation can fail to set the SystemStatus to Normal; leaving the controller in NoDatabase mode. If this occurs, the value can be manually set to Normal to "kick start" the controller. 2. AccessServer The second thing to look at is that the value of the AccessServer SystemVariable has been set. This should be set to the ACC Net Id of the Workstation configured as the Primary Access Server (> 190) for local then remote validation or set to the controllers ACC Net Id for local validation only. 3. Door Object Additionally Door objects need to be configured to handle the above conditions, there are a number of ways they can require authentication when a card is presented, these are listed in the Entry Reader and Exit Reader tabs of the Door object in the form of check boxes. The main ones being validate site, validate card, valid pin, and Door Forced Lock Schedule. Tick whatever options are required.

Issue Need linkage kit for TAC ball valves: VB-2213-XXX-9-XX and VB-2313-XXX-9-XX. Product Line Field Devices Environment Ball Valve Linkage Kit Cause Replace linkage components on the valve bodies. Resolution Part # AV-610 Click here to download the Installation Instructions from the Exchange Extranet.

Issue Report or Extended Trend Log not showing the most recent data Product Line EcoStruxure Building Operation Environment Interval Trend Logs Extended Trend Logs Cause The extended trend log will only pull information from the Trend log when the Threshold is reached. Resolution OPTION 1 - Use the maximum Transfer Interval property. Edit the Extended Trend Log Change the Maximum Transfer Interval property from "Disabled" to the maximum time you want to go between updates in the extended trend log. NOTE: You should not set every extended trend log to 1 minute as this will cause unneeded strain to the system. If you need current data, look at the Trend Log. Use Extended Trend Logs and Reports for Historic information. OPTION 2 - Use the Transfer trigger variable Create a Digital Value on the Enterprise Server. This can be controlled by a program or a schedule to force the Extended trend log to update before reports are run Edit the Extended Trend Log Set a the Transfer trigger variable as the Digital Value created above. There are many options with Extended Trend Logs, see System Reference Guide chapter 40. Additional Notes 1. Extra care should be taken when configuring B3 and Infinet Extended Trend Logs - See Technical Reference Guide for full details. "You configure extended trend logs differently in Infinet (and b3) devices than you configure extended trend logs in other EcoStruxure Building Operation devices. For example, you bind the Monitored trend log property to the Infinet device (and b3) point or value configured for trend logging. Also, the Threshold property is not relevant when monitoring extended trend logs regardless of the value you specify. Finally, you cannot use smart logs when configuring extended trend logs in Infinet devices (and b3). Instead of using smart logs, you use the Maximum transfer interval property to specify the transfer interval." (Technical Reference) 2. To debug logging issues the Force transfer is very helpful, Force transfer Executed by the user to manually force a transfer even though transfer threshold is not reached. (Right click on the Extended Trend Log/Activation/Force Transfer)

Issue Request for database schemas for SecurityExpert and SecurityExpertEvents databases. Product Line EcoStruxure Security Expert Environment Security Expert Client, Security ExpertServer Cause Various entities request database schemas for SecurityExpert and SecurityExpertEvents databases for reasons like access to the stored data for third party reporting packages. Resolution Schneider Electric does not publish or provide the Security Expert database schemas. Database schemas change over time with new revisions which may result in broken tables. Anything required should be available using the Security Expert SOAP Web Service Software Development Kit (SX-SOAP-SDK). The SDK will allow the extracting, transforming and storing of data into a separate database. Third-party applications/tools can then report on that data stored in a separate database. This allows the integrity of the Security Expert databases to remain intact. The Security Expert SOAP SDK can be purchased as part number SX-SOAP-SDK.

Issue There is a need to be able to display pdf files from within a webpinpoint graphic Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause instructions to open a pdf file with webpinpoint Resolution Within a graphic in Cyber Pinpoint, add a Windows Control> Web Browser object Edit the object and go to object properties and select the .pdf to display (Change the file type drop down to all files from .htm)  It is recommended to place the pdf files in C:\program files\Continuum\NewGraphicsFiles for permissions reasons.  Once that object has been selected, it can be saved and run in Cyber Pinpoint The same object will open up webpinpoint and the pdf will display.

Issue Background image is cut off when viewing TGML graphic Fit the image to the background, but it does not stretch to fit when viewing the graphic White bars on the side or top of live graphic Environment TGML Cause The TGML root object has a few attributes that default to: Background = #FFFFFF (white) Stretch = None Height = 600.0 Width = 800.0 These may not be appropriate for the graphic being created. Resolution In the TGML editor, navigate to the Objects pane. If the Object pane is not visible, go to View > Objects and make sure that is checked. Click on the root Tgml object.    Available properties are shown in the Properties pane below. If the Properties pane is not visible, go to View > Properties and make sure that is checked.   In a pure TGML graphic, the Background color will represent the color behind all of the components. If a large background jpg or bmp image is used, the Background color will represent the color that will show up as bars on the top and right of the graphic when it is not sized perfectly to fit in the viewer's window (if Stretch is set to None). Stretch will have three different options (this is also a user defined option, this attribute merely sets the default presentation): None -- The size of the graphic in the TGML editor is preserved in the viewer's window. This may result in blocks of color on the top or right of the graphic. It may also result in sections of the graphic being cut off from the view requiring the user to scroll to view. Uniform -- The graphic is stretched to fit the larger of either the height or width of the viewer's window. The aspect ratio of the graphic is preserved. This may result in blocks of color on the top or right of the graphic. Fill -- The graphic is stretched in both the horizontal and vertical direction to fill the entire screen. This may result in a stretched or skewed presentation of the graphic. Height and Width will set the height and width of the graphic when Stretch is set to None. In a pure TGML graphic with all vectored components, the height and width are merely relative to the size of the components and aren't of great concern. However, when a background jpg or bmp image is used, the height and width should be set to match the dimensions of the background image.

Issue Niagara R2 is installed on a computer, but the HostId is unknown. The user needs an alternative method to find the HostId without accessing the license.properties file. Product Line TAC IA Series Environment Niagara R2 Cause The HostId is required for licensing or troubleshooting, but the usual method (checking license.properties ) is unavailable. Resolution Open the Niagara Console (found in the Niagara R2 Program Group). Type the following command: nre -hostid Press Enter. The HostId will be displayed on the screen. Additional Info: The nre command can also display other system details. Use nre -help to view available options.

Issue Product specifications and application details for the SE 7000 or SE 8000 range of room controllers are required. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE8000 • SSL SE7000 Cause Full details of the products are required. Resolution The best source of information is in the online Product Selection: Room Controller Selector Tool This tool will allow you to select the correct unit for your application, then from the different tabs you will be able to see: Product Overview, Spec's, Dimensions, related accessories and to download the required documentation from the Links tab. Note: The installation guide can be downloaded from the Links tab and contains detailed application setup, product specification and dimensions. For BACnet versions of the controllers the PIC's statements can currently be downloaded from the Viconics section of the BTL official site using the corresponding VT7xxx part number, see link: BTL Listings for Room controllers Note: The SE8000 and SE8300 Series BTL Certification Listing is anticipated for late 2015.

Issue The Modbus IP X Driver can operate in 2 modes Client & Server, can it poll multiple servers in "Client mode", or serve to multiple clients in "Server mode"? Environment Modbus TCP/IP X Driver XDriver IP X-Driver, X Driver, Client Server Cause Clarification required on the functionality of Modbus IP interfaces. Resolution A Continuum controller can only support 1 IP level X Driver. The Modbus IP X Driver can be configured in Client or Server mode but not both (that would require 2 Controllers)  In Server mode the Modbus IP X Driver can serve data out to multiple clients on the same network. In Client mode the Continuum Modbus IP X Driver can co-exist with another IP Modbus client on the same network/ device. It can also poll multiple servers. When polling a 3rd party Modbus IP Server that can also be polled from a second Modbus IP Client, you will need to determine from the supplier if it supports multiple simultaneous sessions. In both Client and Server configurations the number of different sockets (different IP addresses it can talk to) is dependent on the controller used. A bCX1 has a total of 128 IP sockets, but a number of these are used by the regular workstation comms, others can be used for add on options like SNMP alarming, so I would not recommend on communicating with more than around 80 different devices from 1 controller. Currently the NCII only has around 30 available sockets (although this is planned to be increased in a future firmware revision).  

Issue Opening Pinpoint in webClient results in one or all of the following error messages: Unknown error. Server:http://localhost/DNWACServerFactory/WACServerFactory.soap C:\User\SEEB\AppData\Local\Temp\PPxtF\WPPCachw\PinFiles\???.pin contains an invalid path. Runtime Error! C:\Program Files\WebClientPinpoint\WPinpoint.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. Product Line Andover Continuum Environment Windows Vista, Windows 7 and Windows Server 2008 Continuum Cyberstation 1.93 Cause This is due to an error in the webclient install guide, page 88, where you are asked to edit the web.config file Resolution Find the web.config file, normally in program files/continuum DNWACServerFactory, the file is called "web" Edit the file with notepad and delete the content Copy the following text in its place and edit the "machine name" to your PC name, in this example the name is "WORKSTATION1" <configuration>          <system.runtime.remoting>                  <application>                          <service>                                 <wellknown mode="Singleton" type="DNWACServerProxy.WACServerFactory, DNWACServerProxy" objectUri="WACServerFactory.soap"/>                        </service>                        <channels>                                <channel ref="http" machineName="WORKSTATION1">                                </channel>                        </channels>                 </application>         </system.runtime.remoting>         <system.webServer>                 <security>                         <requestFiltering allowDoubleEscaping="True"/>                 </security>                 <directoryBrowse enabled="true"/>         </system.webServer> </configuration> Save changes to file and restart the PC. webclient and pinpoint should work normally now NOTE: If the "RunTime Error!" occurs on a Client machine and the operating system is Windows 10, download "MSXML 4.0 SP2 Parser and SDK' x86 file from Microsoft. This will resolve the access to the graphics from the client machine. Here is the link: https://www.microsoft.com/en-us/download/details.aspx?id=19662

Issue Some Netcontrollers support 32 I/O Modules, others only 16, how to find out what the limit is when adding more modules to an existing system. Environment Continuum Netcontroller CX9900, CX9940, Netcontroller II CX9680, CX9940 16IO-T X Driver Cause When a site is being extended by adding extra IOU Modules, it needs to be determined if the Netcontroller will support these additional modules. Resolution If the controller is online to Cyberstation, Edit the controller and check the value of "Max IOU Modules" on the Options tab, this will show 16 or 32. If the controller is not online the following apply: All Netcontroller II (CX9680) controllers support 32 IOU Modules. All Netcontroller 1 CX9900 with 8Mb RAM support 32 IOU modules, Most CX9940 with 4Mb RAM support 32 modules the only exception was the 4M-16I/O-T (now obsolete) that supported 16 modules. To determine if the CX9940 is a 4M-16I/O-T, check that the Model on the right side of the unit is defined as CPU-4M also that there are no connectors for the RS485 fitted to the unit on Comm1 or Comm4 (you will see holes where the connectors are not fitted). The CX9940 16IO/T can support an X Driver on RS232 Comm1, but no other port. The 4M-16I/O-T and 8M-32I/OT Do not support any Infinet nodes and cannot be upgraded to support them as the required hardware is not fitted as the time of manufacture.

Issue After installing a new Stand Alone Continuum system or upgrading it to use SQL Server 2005 Express (SQL Express) it is found that the ExtendedLog table is not being purged. (truncate delete purge) The tables fill up, resulting in a large Continuum database that can cause the system to slow down as it reaches its 4GB limit. Product Line Andover Continuum Environment Continuum Stand Alone v1.82 and above. Continuum Stand Alone system that has been upgraded from v1.81 or below. SQL Server 2005 Express Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Before Continuum v1.81, our Database engine for Continuum was MSDE. It used SQL Server Agent service to run maintenance tasks on the ContinuumDB. SQL Server 2005 Express does not have this SQL Server Agent and the scheduled maintenance tasks are added as Windows scheduled tasks during the creation of a new Continuum Database. "SQL Agent is a SQL Server service that is used to automatically schedule job execution for SQL Server. It is typically used to schedule the execution of DTS packages or to perform system maintenance tasks like database backups. While MSDE includes the SQL Agent service, SQL Server 2005 Express does not. However, you can use the Windows built-in Task Scheduler to schedule jobs for SQL Server 2005 Express. You can use Task Scheduler in combination with the downloadable DTS runtime to automatically schedule the execution of DTS packages. Likewise, you can use Task Scheduler in combination with the SQL Server 2005 Express command-line SQLCMD tool to regularly execute SQL Server 2005 Express system maintenance jobs like database backups and other database access jobs." See full article on this at http://technet.microsoft.com/en-us/library/cc966393.aspx The key here is that the scheduled tasks are added during the creation of a new Continuum Database. When upgrading Continuum you would typically install overtop the existing installation; upgrading your existing Continuum Database, which does not create the Windows scheduled tasks required to schedule events tables and ExtendedLog table to be truncated on a regular basis. Resolution Check Purge interval First thing to do is to confirm that your Extended Log Purge Interval has actually been set properly, by default this is set to 0 which disables automatic purging. Right-click your Continuum icon and select General Preferences. On line 10 - Extended Log Purge Interval, set this to the number of days you want to keep in your database. (typically 30 days) Once this is set, the next time the scheduled task runs it will truncate your table back to the number of days you have selected. If this was not set properly this may be all that is required. If it still does not purge and tasks have not been created then continue on with the below steps. Creating Scheduled Truncation Tasks Create a new Continuum database, at the end of this creation after closing the Database Initialization window, the scheduled tasks are created under Start -> Accessories -> System Tools -> Scheduled tasks. To create these scheduled tasks and associated scripts you will need to delete the DB, create a new one, and then restore your backed up database overtop. To do this follow the below steps: Shut down all Continuum Cyberstations. IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use SQL Management Studio Express and logon with the SA account. Browse to the Databases folder, right-click the ContinuumDB and select Delete. This will delete the ContinuumDB from the server and the associated .Mdf and .Ldf files from the harddrive. Open up Database Initialization. Select Stand Alone. Click on the Create New database radio button (bottom right) which opens up the needed fields. Confirm the Database name is ContinuumDB. Ensure the User Login ID is set to Andover97. Ensure the User Password is set to (not disclosed due to public access). Ensure the path is correct for the DB File location. Enter in the SQL Server's SA password. Enter the Windows username and password that has local administrator privileges. (IMPORTANT: Make sure that your Windows user has a valid username and password; the scheduled tasks will not be created if the Windows user does not have a password) Click Continue (This creates the two files ContinuumDev.mdf and ContinuumLog.ldf in the DB File Location) Click Close to close Database Initialization, this is the point at which the scheduled tasks and associated scripts are automatically created. Using SQL Management Studio, now restore the backed up database. Restore the backup over the top of the ContinuumDB on your new system: Right click on ContinuumDB -> Tasks -> Restore -> Database. Select "From device:" and add your Database file, making sure to tick the Restore checkbox to select the source. Next, go to the Options page and select "Overwrite the existing database" and press the "OK" button. Change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. use ContinuumDB go sp_changedbowner 'Andover97' go Now confirm that your Extended Log Purge Interval is set properly, by default this is set to 0 which disables automatic purging. Right-click your Continuum icon and select General Preferences. On line 10 - Extended Log Purge Interval, set this to the number of days you want to keep in your database. (typically 30 days) Once this is set, the next time the scheduled task runs it will truncate your table back to the number of days you have selected.

Issue AMT has stopped receiving data AMT is not receiving data A new link added to a system, is not sending messages or transactions Product Line TAC INET Environment I/NET Cause AMT can stop receiving data for several reasons. Connection between Remote Client with I/O and SQL is broken AMT is Paused Communication to the device is not functioning AMT Masking is not set correctly Host Masking is not set correctly Point Masking is not set correctly Door Editor Masking is not Set The software has frozen I/NET has reached its maximum online event size and FIFO is not working (very rare) Other Resolution Connection between Remote Client with I/O and SQL PC is broken. Check that no other I/NET PCs are connected to the SQL database. This may include an instance of I/NET installed on the SQL PC Restart the I/Net Remote Client with I/O to re-establish the connection with the SQL Server Wait several minutes for data to update. If this fails, ensure that there are no firewalls or communication failures between the 2 PCs. If using I/NET v2.42 there have been instances where this version does not pass events to the SQL Server.  This is fixed in v2.43 or greater. AMT is paused Right-click anywhere in an open Alarm/Transaction/Message window The bottom choice is either "Pause" or "Resume" If it is "Resume" click on that and AMT function will be restored Communication to the device is not functioning Minimize AMT and open I/NET Connect to the controller Select Summary>Controller If you see values and get no error messages this is not the issue If you cannot see values or get a "No Entries in Database" error, determine why communication is down AMT Masking is not set correctly In AMT Select Edit>Configuration Note the current settings, take a screen shot and save it if possible For troubleshooting purposes, select all of the check boxes under "Messages/Alarm" Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Host Masking is not set correctly (TCP/IP only) Right-click on the I/O server and select Configure Modify the Active Profile On the bottom of the screen click on "Host Masks" Select any NPR or 527 Note the current settings Check all boxes Click okay Repeat 4-7 for all NPR or 527 devices Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Point Masking not set correctly Connect to a controller that you expect to receive messages from Select Edit>Controller>Resident I/O Modify a point you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Messages and Alarms Click okay Go to the controller summary and attempt to trigger a message or alarm Door Editor Masking is not Set Connect to a controller that you expect to receive messages from Select Edit>Controller>Doors Modify a door you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Transactions and Alarms Click okay Attempt to trigger a message or alarm The software has frozen Restart the I/O server If this does not work restart the computer I/NET has reached its maximum online event size and FIFO is not working (very rare) Right Click on the I/O server and select Archive Configuration Enable Archiving if it is not enabled Increase the size of the maximum online events Restart the I/O server Trigger an Alarm or Event in I/NET Verify AMT  Other troubleshooting steps Force a Lan to reconfigure by changing the station address of the Xenta 527, then changing it back If AMT still will not function Repeat the above processes using an Event window with no filter.  It is possible messages are being received, just not to the open Window Close all open AMT windows Select System>New>Event Window Click Okay This opens an Event Window which will display all data coming into AMT Repeat the above troubleshooting processes The Controller LAN is having communication issues Cycle power on one of the Controllers on the Controller Lan to force a Lan Reconfigure Other solutions for this issue have been documented in these articles: No door transactions coming into AMT: Quick Poll is not enabled.  Typically applies to older sites. Transactions not Updating AMT Window using direct connect: For Direct Connect systems No Transactions or controller Events in AMT: Reliable Tap AMT messages stop after re-installing I/NET: Applies to recently upgraded sites.

Issue Attempting to make programming changes to a Niagara R2 UNC-510 station.  After the changes are done, performing a backup fails.  The "save runtime db" does not complete. Environment Niagara R2 UNC-500, UNC-510 Cause The backup process (save runtime db command) requires free memory on the smart media card.  There must be enough free memory to (at least) equal the size of the .sns file. The smart media card (listed as '/sm' on the Summary tab of the Admin Tool) holds the station database (.sns file), graphic images, and other files accessible using the Remote Library. The table below summarizes flash drive volumes and usages by model.  Note that a jace in the table is a UNC. Refer to the Niagara Capacities Engineering Notes for more information. Resolution Access the Remote Library via Workplace Pro and delete unnecessary files.  As files are removed, monitor the Free File Space on the Summary tab in Admin Tool.  When the '/sm' increases a few kilobytes, try performing a 'save runtime db'.  If the command is successful, then the free file space created is adequate.  If it does not, repeat steps 2 and 3 until it is.

Issue Create a true PWM output from a Xenta programmable controller using a DOPU block in Menta. Environment Menta Cause Menta does not have a built in PWM functionality, so to control a PWM actuator, some additional programming is required to utilize a DOPO block as desired. Resolution Click the image above to download the Menta Macro. Load the macro into the Menta file. The HFB takes a percent signal input and outputs the required values to control a DOPU block, which in turn will pulse the physical DO on the Xenta controller to control a PWM actuator.

Issue Although all the cameras connected to Pelco Endura SM5000 system manager can be found by the video server, when using "Video Administrator" to try to assign alarm points to cameras, sometimes cameras cannot display properly,  such as "1-192.168.5.10"(SM5000 IP Address),  or return "not found' and get an error message such as "Camera or Video server maybe offline....". Environment Windows XP SP3 Cyberstation 1.92, Cyberstation 1.93 Pelco Endura SM5000 system manager Cause It is an Endura configuration problem. A camera should be added into a group. In and Endura system, there is a default group, if no additional group is created. Normally, cameras should be added into this default group. However, in some situation, some cameras will not be automatically added into that default group. In this situation, those cameras do not belong to any group; therefore, those cameras will not display properly in the camera's field drop down menu and cannot be selected. Resolution Create one or more groups in Endura system. Add the desired cameras into the groups created in step 1. Learn cameras again from the video server. Reopen the video administrator and add points to cameras.

Issue USB LON adapter from Echelon (PS3 Part Number:ECH-75010R) is not recognized by Workplace Tech. Environment USB LON adapter (ECH-75010R) Workplace Tech Cause The ldv32.dll file (Open LDV driver) loaded with Workplace Tech (located in C:\Program Files\WorkplaceTech directory) is an older version of the driver and it does not support USB interfaces. Resolution Download the latest version of the LDV driver (153-0212-01A_OpenLDV340.exe) The latest version of the LDV driver can be downloaded from the Echelon website (www.echelon.com) and it contains support for USB devices. In order to download from Echelon’s website, a (free) user account is required. Once it is created, proceed to “Recommended Downloads” and the LDV driver will be listed (towards the bottom) as "OpenLDV 3.4 Network Drivers for Windows Vista/XP/2000/Server 2003 (includes drivers for i.LON 10/100/600 RNI, PCLTA-20/21, PCC-10, and U10/20". The LDV driver is also posted on The Exchange Download Center. Install the new LDV driver Copy the ldv32.dll file from the C:\lonworks\bin directory, and paste it into the C:\ProgramFiles\WorkplaceTech directory. This driver is required for Workplace Tech version 5.6 or earlier. After installing the driver, Workplace Tech will now recognize the USB adapter.

Issue Automation Server is going online and offline when viewed from an Enterprise Server. NOTE: Depending on the network setup/IP switch arrangement, having a duplicate Automation Server (AS) IP address can manifest itself by the AS continually resetting itself (Status LED going red, then flashing green, then solid green, followed by red again) over a 1 to 2 minute cycle. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server StruxureWare Building Operation Workstation Automation Server Cause Duplicate IP address assigned to the AS. IP conflicts will cause the AS to go offline in the ES. Resolution Check that the AS has a unique IP address on the network. If not, consult the IT department to verify that they can provide a unique static IP address. Also, isolate the AS temporarily using a switch and see if the issue stops.

Issue Controller labelling and documentation does not describe how to connect expander modules or which modules are supported. Product Line EcoStruxure Security Expert Environment Security Expert SP-ACX SP-ACX-V2 SP-O8 SP-I16 SP-MRDM2 SP-RDM2 SP-I01 SP-IO84 SP-MI16 Cause Documentation is scheduled to be updated but due to UL certifications for some of these documents the process may take some time to complete. Resolution Expander modules are able to be connected to the SP-ACX and SP-ACX-V2 controllers. There is no restriction to the type of Expander Module, all modules are supported unless specifically stated that they are not. The Expander Module network is connected to the RS-485 port on the right-hand side of the controller just above the Digital Outputs port. This port should be labelled with N+, N-, NA, NB and is to be wired up as per the below diagram. Expander Module RS-485 port