Issue Troubleshoot Security Expert Controllers showing offline in the client. Product Line Security Expert Environment Security Expert Cause Require some common troubleshooting steps to help determine why controllers may be offline to the client. Resolution The main items to check are: Refer to the Troubleshooting Security Expert Controller Connectivity - Application Note on Exchange Restart the client software. Power restart the controller. Remove power Wait for all LED's on the controller to go completely off Apply power to the controller. In the controller web interface, on the Settings page, check that Event Server 1 has the correct IP address. Check that the Firewall is disabled. Check any Anti-Virus Firewalls/settings as well. Restart the Security Expert services under the PC's Services option in Control Panel. These need to be restarted when any changes are made. Confirm that the module versions are all the same. Go to About  > Version and check there. If the database has not been upgraded to the same version as the client software, then this can cause communications issues. On the Security Expert Server check that MSMQ is still enabled in Windows Features as this is now a requirement. If MSMQ was installed after Security Expert, you'd need to reinstall Security Expert to allow it to run correctly. If MSMQ is installed and controllers are still not coming online then anecdotal evidence suggests enabling Windows 8 Compatibility Mode may help. Set the Windows 8 Compatibility Mode checkbox in the Properties page for C:\Program Files (x86)\Schneider Electric\Security Expert\SecurityExpertEvtSvr.exe.   Also, note that if you have imported a database backup, then you will need to check/change some other settings as well to ensure everything is set up for your specific server and controller.   Under Global > Download Server confirm that your computer name is the name of the PC where the download server service is running. Under Global > Event Servers ensure that the computer name is the name of the PC where the event server service is running. Under Sites > Controllers confirm the Serial number, IP Address, Download Port, Download Server and Control and Status Request Port match what is set in the controller's configuration web page (browse to the controllers IP Address to view). On that same General tab go to Diagnostic Windows and open the download and event server windows. Review the information contained and if there are any errors shown. Right click the controller and select Get Health Status. Review the status messages displayed.

Issue There is no built-in Credential Type for the HID 37-Bit badge with no site code (H10302). Product Line Security Expert Environment Security Expert Server Cause Security Expert does not have the HID 37-Bit badge (H10302) with no site code as a built-in available Credential Type. Resolution 1) In the Security Expert Client, select Sites -> Credential Types 2) Create a new Credential Type with a name of your choosing. 3) Under Configuration, select the Format as Wiegand. 4) In the field labeled Wiegand or TLV Format, enter the following exactly as written:                                                        A,FACILITY,0,MSB,BIN__B,CARD,35,MSB,BIN__PBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBP_EXXXXXXXXXXXXXXXXXX.................._..................XXXXXXXXXXXXXXXXXXO 5) Save   NOTE: This article assumes that the reader is familiar with creating and deploying Custom Credentials, If this is not the case, then please reference Section 8 (page 55) of the Transition Guide Security Expert - Continuum Access Control to Security Expert - Reference Guide

  Issue When upgrading a MP-V from v1.xx to a later release the Box Flow reading is zero when there is a velocity pressure. Product Line EcoStruxure Building Operation Environment SmarX IP controller MP-V   Cause When a MP-V-7A or MP-V-9A is upgraded from v1.xx to v3.xx firmware. The MP-V does not control and the Box Flow reading is zero. The damper will rotate to 100% with a Velocity Pressure reading.   The Balanced k-factor and the Balance flow correction are found to be at zero:       Resolution During the upgrade process the flow data is not retained.   Before the upgrade at v1.xx, backup the flow balance data under the Flow Balance Data object,     Continue and complete the upgrade process, re-hosting the controller and downloading the objects. Finally, restore the flow data.

Issue Replacement of ARE, ARX and ARM rotary actuators Product Line Field Devices Environment Satchwell ARE1xxx Satchwell ARE2xxx Satchwell ARE7xxx Satchwell ARX1xxx Satchwell ARX2xxx Satchwell ARX7xxx Satchwell ARM1xxx Satchwell ARM2xxx Satchwell ARM7xxx Cause Obsolescence of Satchwell ARE, ARX and ARM actuators. Resolution ARE actuator                                                               Replaced by ARE1301                                                                          MD20A-24 (p/n 875 1029 000) ARE1302                                                                          MD20A-24 (p/n 875 1029 000) ARE2301                                                                          MD20A-24 (p/n 875 1029 000) ARE2302                                                                          MD20A-24 (p/n 875 1029 000) ARE2303                                                                          MD20A-24 (p/n 875 1029 000) ARE2304                                                                          MD20A-24 (p/n 875 1029 000) ARE2351                                                                          MD20A-24 (p/n 875 1029 000) ARE2352                                                                          MD10A-24 (p/n 875 1019 000) ARE2354                                                                          MD10A-24 (p/n 875 1019 000) ARE2355                                                                          MD10A-24 (p/n 875 1019 000) ARE7301                                                                          MD20A-24 (p/n 875 1029 000) ARE7303                                                                          MD20A-24 (p/n 875 1029 000)   ARX actuator                                                               Replaced by ARX1201                                                                          MD20B-24 (p/n 875 1025 000) ARX1202                                                                          MD20B-24 (p/n 875 1025 000) ARX2201                                                                          MD20B-24 (p/n 875 1025 000) ARX2202                                                                          MD20B-24 (p/n 875 1025 000) ARX2203                                                                          MD20B-24 (p/n 875 1025 000) ARX2251                                                                          MD10B-24 (p/n 875 1015 000) ARX2252                                                                          MD10B-24 (p/n 875 1015 000) ARX2253                                                                          MD10B-24 (p/n 875 1015 000) ARX7201                                                                          MD20B-24 (p/n 875 1025 000)   ARM actuator                                                             Replaced by ARM1601                                                                        MD20B-230 (p/n 875 1021 000) ARM1602                                                                        MD20B-230 (p/n 875 1021 000) ARM2601                                                                        MD20B-230 (p/n 875 1021 000) ARM2605                                                                        MD20B-230 (p/n 875 1021 000) ARM2606                                                                        MD20B-230 (p/n 875 1021 000) ARM2607                                                                        MD20B-230 (p/n 875 1021 000) ARM2651                                                                        MD20B-230 (p/n 875 1021 000) ARM2656                                                                        MD20B-230 (p/n 875 1021 000) ARM2657                                                                        MD20B-230 (p/n 875 1021 000) ARM7601                                                                        MD20B-230 (p/n 875 1021 000)   Options To fit replacement actuator to an existing MB screwed valve use linkage kit - LMD/MB (p/n 914 1071 000) To fit replacement actuator to an existing MBF flanged valve use linkage kit - LMD/MBF (p/n 914 1070 000)   If 1 end switches are required, the reference is MD-S1 (p/n 914 1060 000)  If 2 end switches are required, the reference is MD-S2 (p/n 914 1061 000)  

Issue String Bindings between Infinet Controllers fail Product Line EcoStruxure Building Operation Environment Infinet Controllers I2 Controller String Transfer Cause Direct string transfers between Infinet Controllers were possible in Continuum (via an import PE Program), but not in EBO via Script Program Resolution Following a Continuum Conversion, direct string transfers (via an import PE Program) downloads correctly but the Strings do not update. This type of transfer is not seen often, but was possible in Continuum. See the Knowledge Base article Passing InfinityString object between Continuum controllers The workarounds are Bind string values direct (object to object), but this will force an EBO transfer via the ASP, so if the AS is not available the transfer will fail. Also more bandwidth is used. Rewrite the script to avoid using string transfers, by using numerical Objects

Issue InfinityProgram that sets the value of a local string object from the value of a remote string object frequently gets disabled. Product Line Andover Continuum Environment CyberStation CX9900 CX9702 CX9640 CX9680 ACX5720 ACX5740 i2 field devices Cause Passing string objects between controllers does not use the system's Import/Export system, strings are passed by point to point operation which can produce large amounts of traffic on the Infinet field bus. The program will disable if not properly written to account for events in the field bus that will knock controllers offline (i.e. field bus reconfigurations) Resolution Care must be taken when writing the program to 1. Fetch the string value at a reasonable interval instead of in every scan 2. Keep the program from disabling due to communication errors, bus reconfigurations etc, typically an error line (E:) is added to the problem to handle errors graciously. If possible transfer the value via a numeric point so that the I/E system is used as opposed to point to point.

Issue Double click on a point in Vista. The Edit Properties window should pop up allowing you to view the value, set the Forced-By-Operator setting, and set the forced value. Sometimes double clicking it does not open any window. Product Line TAC Vista Environment Vista Workstation Double or dual monitor Cause The Edit Properties window is popping up off of the screen. Either it was dragged off of the screen accidentally or a second monitor was removed or is not accessible through remote connections. Resolution To display the dialog on the main screen: Double click a point in Vista. Do not click on anything else. The invisible Edit Properties window should be the current window. Press three keystrokes in this order: Alt + Space + X.  This is the Windows hotkey combination to the File menu, and will maximize the current window on the monitor. Possibly try hitting the Alt key twice. This brings the current window to the front. Alt + Space bar, then select Move with the mouse, after a tap of any arrow key, the mouse should lock onto the window allowing you to move it To prevent this from happening in the future: Download the TAC Vista Dialog Position Reset utility. Unzip and double click the executable file to run. Hit the Reset button.

Issue A service that requires the system to be open has been accessed prior to successfully opening the System object. TAC Vista System Plug-In The system is not open. (Subsystem: LNS, #67) Error: LNS #67 lcaErrSystemNotOpen Product Line TAC Vista Environment LonMaker Vista LNS Cause There are many circumstances that could cause this. For example, if you call the Validate method to validate a network database before opening the system, or if you call the Backup method to copy a network database before opening the system, this exception will be thrown. Resolution If registering or launching the TAC System Plug-in results in the error "System is not open, LNS #67" followed by "TACOSSysPin.Document launch failure Exception occurred," and "lnsplugin.api launch failure," then your LNS credits may be corrupted despite indications that they are not.  First reboot and try again.  If still fails, replacement credits have to be reordered from Echelon.  See description of LNS #147 in Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147). It is also possible to get LNS #67 without having corrupted credits.  This has been seen a couple of times on databases that are upgraded from LNS 3.1 to LNS Turbo.  It seems to be hit or miss whether the upgrade will cause this issue or not.  The Licensing Upgrade 2006 discussed in LNS #147 should be installed.  Defragmenting the computer can also cause this corrupted credits with no indication and a TACOSSysPin error. Replacement credits will fix the issue even though there is no indication that they are corrupted.

Issue On a fresh install of LonMaker Turbo, inactivated, the first time trying to open a drawing you may get the error:  The object was not found (Subsystem: LNS, #6) Extensions ‘Echelon_LMW_Demo’ Environment LonMaker Vista LNS Cause If you specify a network name with trailing spaces, the LonMaker tool will report an LNS #6 error (object not found), and report an unexpected error. An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. It should be noted that this error can also occur in some implicit assignments. For example, if the network interface to be used has not been explicitly assigned to the appropriate property, LNS will continue using the network interface previously assigned to the ActiveRemoteNI or NetworkInterface property, respectively. In such a scenario, this exception could occur even though no explicit assignment has been made, indicating that an implicit assignment maps to an unavailable object. A monitor set may be created while offnet (System.MgmtMode is set to lcaOffNet); however, a monitor set cannot be opened while offnet. Furthermore, attempts to query the MonitorSet.IsOpen property will get the error "The object is not found (Subsystem: LNS, #6)" when offnet Resolution Getting the activation code and activating the install should clear the error.

Issue NSS program ID changed. Requires upgrade or revert back to old interface. (Subsystem: NS, #171)  Environment LonMaker NL220 Vista LNS Cause If you open the Network Properties dialog, change the network interface from an LNS legacy Network Interface (also called NSI) to an LNS Fast Network Interface (also called VNI), or vice versa, and at the same time change from Offnet to Onnet, the LonMaker tool will report an NS #171 error (NSS upgrade required).  Resolution Change the network interface only -- remain offnet Click OK. Re-enter the Network Properties dialog and then change from Offnet to Onnet

Issue The Pelco Endura system with cameras at a location and integrating with the TAC I/NET Seven system. Environment Check the system requirements for the version of TAC I/NET Seven and Pelco Endura  Cause Configuration requirements of the Pelco Endura and TAC I/NET Seven are specific for the functionality in I/NET. Resolution Once your Pelco Endura system is configured and the Workstation has discovered all the devices and the System Manager is online with the cameras correctly configured, there are four basic requirements to connect TAC I/NET. Cameras have to have a unique friendly name other than default. Cameras have to have a unique camera number. Netframework 3.5 has to be installed. Windows Media Player 11 has to be installed.   If using I/NET Seven Release 2.40a then the following applies: Once INET and the requirements above are installed the Endura Install can be run. The installer for these files is located on the INET CD in the folder: Support\EnduraSDK. Note: Endura video does NOT work on Windows Vista or Windows 7.   If using I/NET Seven Release 2.40 or above: Dual NIC support is now available. For Endura, 100GB NIC and Router are suggested. 1 for I/O Server, 1  for video   Equipment used: NSMS200 Pelco Endura Network System Manager & Network Video Manager SM5000 Pelco Endura System Manager WS5070 Pelco Endura Workstation with Advanced Management Software WS5000 Pelco Endura Work Station Software package NET5301T Pelco Endura Video Encoder Spectra IV Pelco Camera Visit Pelco.com for more information. Click here to view an extended compatibility matrix for Endura and I/NET.

Issue Attempting to commission a controller in an LNS environment results in the following error: Cannot communicate with the device. (Subsystem:  NS, #26) Environment LonMaker, NL220 Cause An NS, #26 error indicates a complete failure to communicate.  Most often this will be the result of physical layer problems.  In some situations it maybe due to a failed controller. Resolution Check the obvious physical layer connections: Is the cable plugged into the laptop to connect to FT-10?  Is the router between the computer and device being commissioned online and communicating?  Are the wires terminated properly at the controller?  Is the controller powered? Are there end of line terminators fitted? Inspect the controller: Are the LEDs blinking as designed? Are you able to receive a service pin from the device? Does an MOT or NXE need to be reloaded to the device? Typical troubleshooting techniques will usually resolve an NS, #26 error once it is understood to be a complete lack of communication at the physical layer.

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Error number :      17040 Error description: Invalid format. (Subsystem: LNS, #40) Any tab except "Status" has some strange values. Trying to view or edit some values results in this error. Environment Xenta 102-AX Plug-in Xenta 104 Plug-in LonMaker NL220 Cause A value inside the device has been set with an invalid value.  It could be through an LNS browser, through an M/STAT or just through some glitch when setting a parameter. Resolution The device will need to be recommissioned using default values. CAUTION:  Recommissioning a device with default values will erase any user defined configuration parameters.  Record all important data for the box:  duct area, airflow setpoints, operating parameters, etc. Right-click on the device in the LNS Management tool.  In LonMaker, select Recommission. In NL220, select Repair. Choose "Manufacturer Defaults" for the initial values.  Click OK. Launch the plug-in again.  The values should now be able to be changed to the desired value.

Issue Get Authentication Mask The entire Disk RTI subsystem is damaged. Please consult the software provider. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Unspecified, but a PSU-specific fix file is the only way to correct the situation. Resolution Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. The following is for informational and archival purposes only. PSS does not have the ability to provide this file to our customers. Contact Product Support and provide the PSU ID. A PSU-specific fix file will be generated and sent back via email. Install the fix file Install the original .plf file again. Exception: If the fix file cannot be installed, make sure that the PSU ID printed on the sticker matches the PSU ID that it presents itself when running Dongleutil. If they do not match, see Error "License run-time information is damaged. Contact software vendor. PSU ID: XXXXXXXX PSU Type: Unknown subfamily: 255".

Issue Menta Parser Error when attempting to direct download a Menta application. Warning Reference to unsupported I/O Error in COD file - Error:13 (Y=___ X=___) Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The application may contain an I/O terminal that does not exist in the device type to which the application is being downloaded.  This error could also occur in situations where the same I/O terminal reference is used more than once in the application (this could be on the Xenta or the I/O module). Typically caused by copy/paste. Resolution It is possible to have a Menta application that looks to be error free during simulation or the generation of the XIF file, but when the application is downloaded to the controller and it is being parsed by the device it reports a warning about unsupported I/O and leaves the controller without an application. The error window that pops up when trying to perform the download directly from Menta is attempting to show where in the Menta file the error is occurring.  If you can read the point names that are highlighted it can help direct toward the invalid I/O termination.  The other option is to look in Options > I/O configuration and make sure there are no duplicates or invalid I/O terminations.  For example, a 401 doesn't have any onboard I/O so a termination of M0-K1 wouldn't be valid. Note: I t is recommended that all macro libraries have non-connected outputs and constant value inputs to force the user to edit these fields.

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are required.

Issue Troubleshooting LON Network communications. Product Line EcoStruxure Building Operation, TAC Vista Environment LON LPA Protocol Analyzer Cause Intermittent communication failures, high bandwidth, error packages, noise on the line -- these can be difficult to pin down and identify. Resolution These two documents produced by Loytec are invaluable resources in troubleshooting a LON network.  The first deals with common causes of noise on LON Wires.  The second details what to do once you've procured an LPA protocol analyzer -- how to use it and interpret data. LON Network Training Network Troubleshooting White Paper For a Vista system, also see Actions for reducing Bandwidth in a Vista network. For an EcoStruxure Building Operation system, also see Bandwidth Throttling. 

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. Issue When doing a LonMaker resynchronization, the operation fails on a certain subsystem or when doing a commission on a controller in Lonmaker an error is displayed: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102) Environment LonMaker 3.X Cause If re-commissioning or downloading and commissioning a controller in LonMaker fails or times out, this issue may crop up. LonMaker assigns the desired neuron ID to a temporary device while performing either of these commands, and if the operation fails, that temporary device will get stuck in the database with the same neuron ID as the controller the user was working on. A successful resynchronization will bring this "phantom device" to light where it can be deleted, but if it is the resynch that is failing, the steps below detail how to remove a neuron ID from a device in the LNS database so it can be deleted. Resolution Try to do a resynch command in LonMaker to get the temporary device to show itself on the Visio drawing. If this works, then the temporary device will show up with a randomly generated alpha numeric name on the same page as the controller you were trying the commission or download. After the resynch completes, delete the device from the page and repeat the commission or download. If the resynch operation fails with: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102), continue. Because the temporary device is in the LNS database, but not on the LonMaker Visio drawing, manual manipulation of the LNS database is required to remove this object. This is done with the LNS Object Browser. First, shut down LonMaker, then click START and chose RUN in Windows and type lnsobjectbrowser and click ok. The Startup Preferences are shown. Set the Client/Server Communication to Don’t change and the Local Network Access to Engineering Mode and then click Ok. After choosing settings in the Startup Preferences menu, the LNS Object Browser is displayed. Press F8 to take the object browser out of read only mode. Browse to the following: ObjectServer/Networks/Your_Network_Name/Systems/ Your_Network_Name/Subsystems/All/AppDevices. Note: Double-click to open each object. Within the APPDevices menu you will see the temporary device with the large alpha-numeric name. Double-click this device to get its properties in the right hand window. Double-click on the NeuronId line in the properties pane of this device and manually set the Neuron Id to 000000000000 (12 zeros) and click Ok. Exit out of the LNS Object Browser and re-open the LonMaker database. Perform another resynchronization of the database, and the suspect temporary device should now show up on the LonMaker drawing. Then, delete that device and re-attempt your work on the original controller.

Issue Integration to the Cummins ModLon 2 gateway with the Xenta 500 / Xenta 700 / Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Cummins ModLon 2 Gateway Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev files as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes. One generator: .dev file Two generators: .dev file   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.