Building Automation Knowledge Base

Issue When doing Xenta server to Xenta server communication, via other projects network, a good troubleshooting technique is to determine if the two Xenta servers are truly communicating to one other over TCP-IP. This is possible via the online status of the imported Xenta server in the project tree. Environment Xenta 511, 527, 555, 701, 711, 721, 731, and 913 Cause Two Xenta servers are set up to communicate to one another, but they are not passing data properly. Troubleshooting step number one should be to determine if the two Xenta servers are online to each other on the TCP-IP Resolution To  check the online / offline status of a Xenta server follow these steps: Login to the web browser of the Xenta server that that is configured to receive data. Navigate to the project tree similar to the image below. 3.  Within the project tree, browse down to the Xenta servers and check the online status as shown here:

Issue This issue has symptoms as below: Blank page, No ID code or number displayed in login webpage and can not login to Xenta Server. Can not access Xenta Server via webpage. The following blank page is displayed: Login page is displayed, but project name and ID code or ID number are not: Environment Windows Server Environment TAC Vista 5.1.X Xenta Server Ver 5.1.X Cause Windows Server "Internet Options" Security Settings are not set properly. Resolution Need add the Xenta Server IP address into "Trusted Sites" in "Internet Options>>Security>>Trusted Sites". If didn't add the IP address into "Trusted Sites", blank page would display; If just "http://%Xenta Server IP address%" is added into the "Trusted Sites", would get login webpage which didn't include project name and ID code in the login page; Need remove "http://%Xenta Server IP address%" from "Trusted Sites", and add "https://%Xenta Server IP address%" into "Trusted Sites" list;   Then could get correct login webpage,  

Issue Host Lost Message Definition Environment I/NET Cause Host Lost messages are caused when I/NET has lost communication over the Ethernet LAN with a host workstation, Xenta 527 or NPR. Resolution Host masks are enabled or disabled by using the far left bit mask of group 1.  You can enable/disable these from showing up in AMT by: Open AMT Select Edit>Configuration Toggle the far left bit of Group 1 Click OK   Alternative Resolution Open I/NET configuration Modify the Active Profile Click Host Masks Modify Each Host Device Toggle the far left bit of Group 1

Issue What are the proper steps for inputting people in the Datacard ID Works Program? Product Line TAC INET Environment I/NET Seven Datacard ID Works Video Badging software Cause A new user or personnel needs to be added to the access control system. Resolution Logging into the ID Works Program The default user name is lower case admin The user password is also lower case admin   Choose the badge project for the card you are going to print. If you do not see the Project in the window area, select the "More Projects" button to see the complete list of projects.   Once you choose the project, a window will pop up for you to log into the ID Works Project.   You have a choice on how to log in. You can either choose to check the box next to "Use Trusted Connection" or under the "INetThirdParty" Login ID the password is lower case passinetdb3p. Typical process is to select the "Trusted Connection" option.   Select a New Production Form to fill out   Fill in all the information listed on the Production Form including taking the photo.   Print the badge. On the top ICON line the second one in going from left to right is the "Print" icon. Before printing the badge, make sure the Blank cards in the printer magazine are the correct ones, then click the Print icon. Printing the badge will also save the information in the I/NET Seven system and the ID Works system.  There is NO need to save the info first, and then print the badge.   With the Production Form on the Screen, DO NOT choose the RED X (X) on the icon task bar to clear the page. See Step #9 for further information on this matter.   If by accident, the RED X (X) button is clicked, the following window pops up. If "Yes" is clicked, all of the information and photos entered in the previous steps will be deleted from the I/NET Seven System and ID Works system. If this pop up is encountered, be sure to choose "No."   In order to refresh the project, go to the top task bar and choose the "Record" option. In the drop down list choose the “New” option. Then select a new Project for the next badge, this process will open a new clean Production Form to fill out.

Issue If there is an online selection tool for all the HVAC sensors (room temperature sensors, duct pressure sensors, etc.) Environment All Schneider Electric Buildings product lines Cause Since Schneider Electric manufactures a huge amount of sensors for different product lines. Sometimes it takes a bit of time to search for the right sensor. Therefore, Schneider Electric developed an online selection tool to help customer pick the right sensors. Resolution Click here to go direct to the online HVAC sensors selection tool. Select the desired features of the sensor. All sensors match the requirements will be displayed on the right. Datasheets can be accessed by clicking on the image or the part number. NOTE: the listed sensors may not be available in some region. Please contact the local sales or Support team to confirm the information.

Issue Individuals added via Datacard ID Works are not getting access to doors Product Line TAC INET Environment I/NET ID Works Cause I/NET uses audit trail messaging to ensure that ID Works data is broadcast out to the site. Resolution Open AMT Select Edit>Configuration Note the Group 1 Masking Settings Open I/NET Select Access>Options Select Group 1 for Audit Trail Messaging Ensure that the masking for Audit Trail is set the same as the AMT Configuration Select Edit>Host Computer>Network Configuration Choose the Link that is connected to the Video Badging PC Verify the Host Number Set up Automatic DPU Restore Function. 's means of communication, then make sure that the Host Masking is set to match the AMT Masking for Group 1 If you are still having issues make sure you are using the correct ID Works Template The Templates are available on the I/NET CD in the Support Folder If you are using your own template ensure you have these required fields: IndividualId TenantName GroupName RecType TempStart TempStop TempStartDate TempStartTime TempStopDate TempStopTime IssueLevel

Issue The "Host Mask" "NP Routers" "Advanced IP" and "CCTV" Buttons are grayed out in I/O Server Editor Product Line TAC INET Environment I/NET Seven rev 2.40 and 2.40A through current release Windows 7 32-bit Cause Issue 1. There is an issue in Windows 7 and running I/NET Seven 2.40 or 2.40A in the Service Mode. Please note this is unique to Windows 7 Only. This does not occur in Windows XP Pro. Issue 2. When editing the Configuration Profile, "Host Mask" "NP Routers" "Advanced IP" and "CCTV"  are not available Resolution Issue 1. There are two solutions to this issue: Leave the site at I/NET Seven rev 2.40 or 2.40A and change the operation from Service Mode back to Application Mode. Upgrade the site to I/NET Seven rev 2.41. With this load the operation can return to Service Mode. Issue 2. When I/NET I/O server is not running, or you select Start/Programs/I/NET/Configuration Profile the configuration profile is like the screen shot below.  Starting I/NET starts the I/O Server which is visible on the tool bar by the clock. Right clicking offers the below menu: Select Configure from this menu and modify the active profile enables the Host Masking, NPR Routers, Advanced IP, and CCTV.

Issue Endura DVR missing the Video in I/NET Seven Rev 2.41 Product Line Pelco, TAC INET Environment I/NET Seven rev 2.41 Endura DVR Cause The Endura Workstation software that comes with the DVR (by default) is set to "Multicast". If this has not been changed, then you DO NOT have to change the three I/Net files listed below. If the Endura Workstation software was changed from the default (Multicast) setting to a "Unicast" setting. Then you WILL have to change the three I/Net files listed below. What is the Pelco definition of “Multicast” mode? By default, Endura encoders and Pelco network IP cameras are default to stream live video in Multicast mode. A common symptom of multicast routing issue is where the date and time stamp can be seen on the workspace but the video is black. This symptom is commonly associated in a layer 3 routing network where appropriate multicast routing protocol has not been enabled globally or inside the VLAN. Resolution The resolution is to modify three files that are installed with I/NET Seven rev 2.41. These three files are located in this directory on the PC – C:\Program Files\INet Seven INetAMT.exe.config INetCfg.exe.config INetW.exe.config Note: If the above three files are not in the I/Net folder, then you have not delete the previous SDK driver. You must delete the previous driver thru the "Add and Remove" option in Control Panel. Once removed then go into the I/Net CD and select the "Support" folder and manually load the new SDK Driver. Then proceed with the rest of the process in this article. Use Notepad to open each one of these files one at a time and change this setting from the "default" of "False" to "True." After making all of the changes in the three file, shut down the I/NET and IO Server ICON. Restart the I/NET again, and the Video should show up in the I/NET program

Issue When one of operator use "Operator A" account to login I/NET, he is only able to access group A (group A is a door group) of doors. When one of operator use "Operator B" account to login I/NET, he is only able to access group B (group B is another door group) of doors. Environment I/NET Seven 2.31 and above Cause Restricting Individual access in I/NET Resolution Log into I/NET with an Admin level user account Select Edit>Host Computer>Passwords Select the User you wish to limit access to Click modify The Host Passwords Editor will open Click on the Tenant Button at the bottom of the Window The Host Passwords - Tenants Editor will open Click "All No" to remove all permissions Check "Full Access" for any Tenant you wish to allow the user to have full access to If you wish the user to have some access check "Limited Access" The Host Passwords - Groups Editor will open Choose "Selected" for any group you wish the user to have full control of Choose "Read Only" for any group you wish the user to have read only access to Leave unchecked any group you wish the user to have no access to. Click OK to close out of all windows Log out and log back in with the modified user account to test control

Issue Card part numbers are built up using the manufacturer, technology, type and format. How is this defined? Environment All systems using access control cards and readers. Cause Clarification on the part numbering is required. Resolution The part numbers for all cards and readers are built up using the format below, also full details of the products and all available part numbers are defined in the Electronic Access Control (EAC) catalogue. Any cards or tags that have a part number that ends in 000 will be un-programmed i.e. 654 xxxx 000. Readers that have a part number that ends in 000 will operate with and pass through all formats with the corresponding technology. i.e. A HID ProxPoint reader part number 654 1301 000 will operate with all formats of prox cards and tags. Other technologies may require the reader format to match the card to operate correctly. i.e. A FlexPass reader 654 2306 400 is formatted with Continuum 37 bit format it will require matching cards like the ISO cards 654 2352 400 that also has the 37 bit format. When ordering cards: if it is a new site specify this on the order, you will then be sent cards with a card number 1 through the number of cards ordered, and the next available site code (also called facility code). However if you are ordering cards for an existing site you will need to specify the range of card numbers required and the site (or facility) code required.

Issue How to create a door that uses the "Two Man Rule" for security access. Environment I/NET Seven rev 2.10 and above Cause The “Two Man Rule” feature provides for configuring cards to be used either as an Escort or an individual requiring an Escort. An “Escort” card is granted access depending on a time schedule. An “Escort Required” card is granted access depending on the time schedule; however, there is another condition for “Escort Required” individuals. They only have access if an “Escort” or another “Escort Required” card with the proper Time Schedule, is presented to the reader within 10 seconds of their card read. Resolution Set up the Feature on a Door. Select the Features button.   In the Function Area create the Escort and Escort Required entries.   Select the Door that is going to utilize the Two Man Rule. Then choose the Schedule button. This is the Time Schedule the Escort will have for this Door.   This is the Time Schedule the Escort Required individual will have for this door.   Set up two special groups for the individuals that will have access to the Door using the Two Man Rule. These are the doors that are assigned to the Escort group.   These are the doors that assigned to the Escort Required group.   In this example, there are only these two individuals that have access to the Two Man Rule Door. However, this can be increased by assigning individuals to either of the groups based on the rights they are allowed to have.

Issue When using the Generate project command in XBuilder the Generate output screen will not show any errors even though it reports an error was encountered or the error is visible but the info message indicating what it was trying to build the caused the error is not visible. Using the Window-> Restore Default Settings does not correct this. Environment TAC XBuilder Cause A filter has been applied to the Output window. Resolution Right click in the Output window and ensure that each of the following options are selected: Show Info Messages Show Warning Messages Show Error Messages

Issue Recommendations for RS-485 LAN communications wiring Environment I/NET C-LAN, Sub-LAN Cause A review of some of the I/NET manuals yielded several instances of the following description: The same communications cable will support a combination of 32 Application Specific Controllers (ASCs), Micro Regulators (MRs) and Door Processing Units (DPUs), connected together in a "multi-dropped" arrangement, as illustrated in Figure 2. The cable should be run in a contiguous node-to-node arrangement without stubs or branches. Resolution We recommend the RS485 LAN (Including the Host LAN, Controller LAN & Sub-LAN) be arranged in a contiguous node-to-node bus configuration without stubs and within the maximum 4000' (1210 m) / 5000' (1500 m) length with 24/22 AWG low capacitance twisted pair shielded cable. 7808 Repeater For the RS485 Token Passing Controller LAN (C-LAN), the model Repeater can be used to branch (stub) off the main LAN bus with a C-LAN bus extension. The 7808 Repeater acts as a single RS485 node on both of the C-LAN segments with both being wired in a contiguous node-to-node bus arrangement. Additional 7808 Repeaters can be applied along the main LAN to distribute additional branches (if needed). The distribution of Stubs/Branches along the main LAN can continue up to a maximum of 32 RS485 nodes (in total) along any one copper segment. There can be another 32 RS485 nodes on the copper segment on the other side of the 7808 Repeater. The 7808 Repeater provides the vehicle to - Stub off the main C-LAN Split the main C-LAN distance when length is greater than 4000' (1210 m) Split the main C-LAN cable length when inferior cable (higher capacitance) is introducing excessive distortion Divide the RS485 node count to a maximum of 32 RS485 nodes on any single segment of copper. I.e. the 7808 provides a separate copper segment on each of the two sides with full RS485 node count (32) and distance specifications Repeated/Tiered Stubbing The 7808 Repeater can further accommodate stubbing off of the stubbed C-LAN segment as long as no more than four 7808 Repeaters separate any two C-CLAN controllers on the controller LAN network. I.e. looking from any 77xx controller out to all of the other 77xx controllers on the same controller LAN, you must not have to go through more than four 7808 Repeaters to reach any of the other controllers (regardless of whether the application actually has any interaction with the other controllers). Old Commentary on C-LAN Tolerance Dating back to the first release and field applications of the Series 6000 followed by Series 7000 controllers, there have been many instances where our Branches and Partners have needed to use exiting wiring in a facility. Inevitably, either the cable characteristics were not as specified (low capacitance data grade twisted pair), or the cable characteristics were not known, or the cable's geographic routing was not conducive to a node-to-node bus configuration. The economic impact of using existing cabling was always a magnet that attracted the project engineer and had to be balanced with a perspective of risk vs. reward. In many cases the existing cables made a node-to-node bus difficult, or impossible to achieve, without rewiring the facility. In some instances, the bus could be accommodated but would inject a large additional copper length into the main bus with the cable run to and from the distant controller location, before proceeding along the bus. With the prescribed cable, the preference is for the bus. But in forced situations where the cable isn't what it should be, it may be better to have a 250' stub than inject 500' of bad cable in the middle of the main LAN segment, with the preferred accommodation being the addition of a 7808 repeater to handle (isolate) the stub. The 7808 Repeater was created specifically to resolve such installation problems, and in most cases it is indeed installed after the fact as remedy for a problem instead of a initial installation and design of the system. Early in the product life this issue/question on use of existing cabling prompted investigation on my part regarding potential guidelines as to where deviations in the recommended LAN configuration could possibly be tolerated. At the 19,200BPS data rate we are running on the C-LAN, there is a significant amount of tolerance for reflected wave distortion from impedance and loading mismatches on the cable. This creates a scenario where the installer can frequently get away with "minor" violation of one of the specified cabling constraints, but doing such is exhausting at least some portion of the system's tolerance for communications distortion and degradation. The problem is that continued successful violation of one recommendation is sometimes molded into what is thought to be standard practice and frequently followed by other and sometimes more subtle violation(s) and the system becomes intermittent because the tolerable margin of error/distortion has already long been exhausted. Standard LAN Installation Recommendations Designated Low Capacitance Cable  Cable Impedance of 100-150 ohms (120 ohm = RS485 standard and preferred) Conductor Gage of 22 or 24 AWG - Data Grade twisted pair with shield Specified maximum of 32 nodes on a copper LAN segment Maximum cable length (4000' (1210 m) for 24AWG) Node-to-node bus configuration without stubs Pass through connection of the cable shield at each controller location Earth ground connection on cable shield at one end only Earth ground connection to each RS485 controller on the designated ground terminal/conductor Any comments regarding I/NET and the subject of "Ts and Stars being allowed" has to be an interpretation of possible earlier commentary by myself and/or others at TCON, Schneider Electric regarding what the I/NET C-LAN system will "typically" tolerate. I.e. what you can probably get away with, if you must. The recommended RS485 wiring approach is that the LAN be configured in a node-to-node bus configuration using the specified cable characteristics, distance limits and node counts and the 7808. Repeaters can be used when stubs or distance extensions or node count requires. When economics of rewiring a facility inject an elevated tolerance for risk, it has been said that the C-LAN system will typically tolerate up to 10 stubs of up to 250 ft ("when other specs are not being violated"). That is a guideline of typical C-LAN tolerance and not a system installation recommendation or approval. The 7808 Repeater has often served as an insurance policy for some who have found the economic need to stub, and in some instances ran into subsequent problems. In other words, they injected stubs when needed and then added Repeaters later if needed to resolve a problem caused by the stub(s). Note that the 7808 Repeater is applicable only to the RS485 Host-LAN and C-LAN, and there is no such post installation solution for the Sub-LAN. The distances are typically shorter on the Sub-LAN and therefore typical tolerance in other areas is higher, but the recommendations remain the same. Termination In most cases the RS485 LANs on I/NET are not being terminated. This is also a tolerance associated with the I/NET RS485 protocol and speed and is a functional issue regarding the 7808 Repeater and the Sub-LAN's SLI (7790A or 7798). The 7808 Repeater depends on C-LAN biasing and is not tolerant of termination on the C-LAN. The C-LAN can indeed be terminated with a 120 ohm resistor at each end of the C-LAN "BUS", when 7808 Repeaters are not being used. This can be a first step in resolving a C-LAN communications problem prior to introducing 7808 Repeaters. The 120 ohm 1/2 watt termination will reduce distortion on the C-LAN and improve noise immunity. The Sub-LAN will not tolerate 120 ohm termination due to the 2.2K ohm biasing of the Sub-LAN required at the 7790/7798 controller. You will have to use a 620 ohm 1/2 watt resistor on the Sub-LAN systems

Issue A controller with only 2 available outputs is being used to control a 3 stage device. Environment Three stage device control where lower stages must remain active. Cause Hardware or space limitations may prevent there from being enough outputs to control a three stage device. Resolution Two controller outputs in conjunction with a DPDT (dual pole, dual throw) relay can be configured to control a three stage device. This will allow you to activate stage 1, stages 1 and 2 or all three stages by activating either one or both of the controller outputs. An example of when this might be used is to control three stages of heat or a three stage fan. A standard "ice cube" type relay can be used (IDEC RH2B or similar) and should be wired as shown in the diagram below.   The controller should be programmed to activate only output 1 for stage 1, activate only output 2 for stages 1 and 2 and finally to activate both outputs for stages 1, 2 and 3. Note that certain application specific controllers may not allow the outputs to be configured in the way described above and thus cannot take advantage of this setup.

Issue Error Message pops up when opening DbCreate: Microsoft Visual C + + Debug Library Debug Error! Program: C:\INet_DVR\Debug\DbCreate.exe abnormal program termination (Press Retry to debug the application) Environment I/NET DbCreate Cause Error occurs when opening DbCreate Msaddo15.dll needs to be registered Resolution Open the Command Prompt Type "cd\" Press enter Type "cd program files\common files\system\ado" Press Enter Type "regsvr32 msado15.dll" press enter

Issue Communicating to I/NET on a direct connect requires a cable that has to be connected from the PC to the controller. Product Line TAC INET Environment All versions of I/NET using Direct Connect to controllers. Cause Connecting to a controller from a PC if there are no Net Plus Routers for connectivity over the Ethernet. If a 7798C controller is being used then another programming cable needs to be used for the virtual HHC on that PC. Resolution To resolve this a cable part number CBL-072 connected to the PC and controller. To obtain the various part numbers for the cables, connecting to the iPortal and searching on %CBL% should bring up the required information. Maximum supported cable length is 25 feet (7.62 meters). ***See the comment below on the CBL-072*** Part number for the direct connect is CBL-072 The pin-out for this cable is shown below: Part number for the 7798C is CBL-082 The pin-out for this cable is shown below: Note: CBL072 is for direct connect between the computer and controller. CBL-082 is for programming with Virtual HHC. **********************************************************************  ***The CBL-072 looks to be no longer available From Schneider Electric (9/2017) *** You have two choices on the CBL-072: 1)            Build a new CBL-072 using the Pin-out above. 2)            Convert a CBL-082 into a CBL-072 (see steps below) To convert a CBL-082 into a CBL-072, cut the “Gray” wire connected to pin 5 on the D-Sub 9 connector at the PC end. Then remark the cable label to avoid future confusion on its use. ***********************************************************************

Issue After upgrading to I/NET Seven 2.40 from older versions, the graphic pages that has backdrops opens up showing lines on the page instead of the backdrop. Environment Windows 7 I/NET Seven version 2.40 and above. Cause When these pages were created originally, the user may have put some polygons initially and could not remove them. There was no way to see these at the time and hence was not an issue then. In Windows 7, the graphic editor picks these up and displays them on the screen on the forefront, hence the lines. Resolution To resolve this, there are several steps that needs to be followed: Open the graphic page and notice that the backdrop is not there and the lines may or may not be seen On the upper right hand corner, Right Click on the page and an editor appears, as the picture shows.   Left click once to clear out the editor, with the cursor in the place, i.e. upper right hand corner, hit the delete key twice. Place the cursor on the bottom left hand corner and hit the delete button once and then save the page. (This clears the lines out) Open up the new saved page and it should open up correctly then. If it still fails then repeat steps 1-4.

Issue Get a hard copy of all points in a controllers / system Get a hard copy of I/NET controllers' databases (SAV files) Environment I/NET Seven Cause Require a hard copy to view all points and database and / or extensions Resolution There is a feature under Network Functions which allows you to print (screen or default printer) any or all controllers save in your Network Configuration. This lets you get a printout of exactly what points and point extensions you have added to the controllers on your system. Select Edit >Host Computer >Network Functions from the main menu. The system displays the screen shown Choose the link of the controller(s) you wish to print from the drop-down list. The system now displays the controllers on the link you selected. Above the list are six push-buttons. Select the Print push-button. Choose the controllers you wish to mark for printing by either clicking on individual controllers in the list or by selecting All Yes. Controllers that are marked for printing will show a “Y” in the Print column of the list. Each click on a controller in the list will toggle the Print function between “–” and “Y”.  Select the Setup push-button at the bottom of the window. The window shown below appears. If you want the database report to print to the screen activate the Print to screen checkbox. Select the database items that you want to print by clicking on the Select checkbox. To select multiple links follow Steps 2 through 6 for each link and controller, selecting Close from the Database Print window to return to Network Functions, until you have selected each controller. Note: The TAC I/NET Seven system lets you select more than one link at a time but this results in a very lengthy printing session. If you do not want to tie up the printer for an extended period of time select only one link at a time. If N/A appears in the print column this means that the station exists for this controller, but no save file exists in the save file directory.   When you have selected the appropriate parameters, select Print to start the printing. When you have selected the appropriate parameters, select Close to return to the Network Functions window. Since database prints may be very long, make sure no manual control commands from the PC are needed during the time required for printing.   Select Close to return to the Network Functions window. This information is also available in TCON299 I/NET Seven Operators Guide - Chapter 2 Setup and Network Configuration

Issue Steps for setting up and configuring an Automatic DPU Restore are needed as well as an explanation on how it works. Product Line TAC INET Environment I/NET Seven 2.11 and above DPUs Cause The Automatic DPU Restore feature performs two functions. It assures that Access edits are sent to DPUs and that edits done by the badging system are sent to the DPUs. From the I/NET editor usually if an edit is done, it is sent to the appropriate DPUs. However, if any DPUs are not communicating at the time of the edit the Automatic DPU Restore will perform a DPU Restore/Warm Start when the DPU comes back on line. The Automatic DPU Restore feature configures up to five possible Restore Hosts which will minimize the number of hosts that attempt to send DPU Restore commands when the DPUs come back on line. ID Works is configured to send a message to it’s I/NET host which prompts the host to send its data to the DPUs. Resolution How automatic DPU restore works Since Host Masking is set for supervision, all Restore Hosts know who is online.  When an edit is done that could not be downloaded to a DPU the Automatic DPU Restore program enters the Host number of the designated Restore Host and the address of the off line DPU in its table.  If the designated Restore Host is not on line, the program checks the next Restore Host until it finds one on line and puts that Host number in the table.  If the Restore from local host box is checked for a link, that Host number is entered.  When the DPU comes back on line, all Restore hosts that should be masked to see the message check the table and if its number is in the table for the DPU it performs the  Restore DPU/Warm Start.  The Automatic Restore program runs every ten minutes so any DPUs that have come back on line that need to be Restored and can be are.  The Badging program uses the audit message to trigger a download to DPU using the Automatic Restore program since it is only set up to update the SQL database.  MSDE or SQL Server must be running on the Badging host.   How to set up and configure the automatic DPU restore Open AMT Select Edit > Configuration Note the Group 1 Masking Settings Open I/NET Select Access > Options   Select Group 1 for Audit Trail Messaging. Set up the Audit Trail for Group 1. Note: the masking here must match the AMT Group 1 setting.   Ensure that the masking for Audit Trail is set the same as the AMT Configuration. Masking here must match the masking set in Step 2 in the Audit Trail.   Select Edit > Host Computer > Network Configuration   Choose the links that you want to connect to the Reference Host PC, then choose the Modify button.   Verify the Host Number   Set up Automatic DPU Restore Function. Please note that #60 is the host number of the Reference Host PC. Check the Local Host Box.   Make sure in the I/O Server that the Host Masking for all the links that need to have Reference Host connections are set to match the AMT Masking for Group 1.

Issue Modbus slave device only supports function code 10 hex/16 dec for writing of holding registers. Environment Xenta 913 Xenta 701/711/721/731 Xenta 511/527 Cause In system program 5.1.4 a trigger was added to the Xenta Server software that enables the device to use only the Multi-Register function code. This command is executed from the console port or from the VXI web shell command webpage. VX M 1 = Enable Multi-Register write VX M 0 = Disable Multi-Register write VX M = Display current status of the trigger Note: This setting is persistent on the unit until the firmware has been reloaded. If the unit is upgraded the setting will need to be reapplied. Resolution Log In to the webpage of the Xenta Server Access the Utilities\Target System\VXI Web Shell Commands webpage. Issue a "VX M" command to display the current status. Issue a "VX M 1" to enable the multi register write command option. Some of the Xenta Servers with recent Modbus support do not have the VXI web shell commands web page and the console will need to be used instead. The VXI web shell commands web page should be available in firmware 5.1.6.