Building Automation Knowledge Base

Issue Error when starting Seven Reports getting an error "Copy of prompt.dll failed Error Code 2". Environment All versions of I/NET Seven and Windows OS. Cause Administrative privileges on the PC needed to run Seven Reports. Resolution Log off of I/NET and I/O Server. Shut the PC down and restart it. Log back in as an Administrator and run the Seven Report again.

Issue Is it possible to use Control Description (command) delays on MR controllers? MR (Micro Regulator) DO points not turning ON (or not turning OFF) - sticking. Environment I/NET Seven MR (Micro Regulator) Controllers Cause The Control Description command delay was not implemented in the MR as it was not intended to be used for control of multiple high power devices, which this feature was designed for; also, the MR does not have the memory capability to support the timer queue to handle it. Note: The Control Description command delay does function within the SLI (7793 / 7798B1 / 7798C) although this function is supported here it is not intended for the control of multiple subLAN devices, such as the MR.  You should not rely on this control function from the SLI.  Undesired results can be expected if this is implemented and is not supported. Resolution The Control Description Command Delay is not supported within subLAN devices and should not be implemented.  Alternative methods of delaying startup of control devices are: Using Time schedules; the Master / Slave time schedules feature.  Within the slave schedules you are able to delay / adjust the start time by minutes. The combination of using Master / Slave ATS and Host ATS provides a powerful and simple user interface in modifying all the Master Schedules from a single location. Refer to TCON 300 Chapters 4 and 7. MR Functions (DDC); If your control delays are required within the MR, a method available to use is the MR-DDC Relay modules are the delay before break (DDB) or delay before make (DBM) timers.  An even simpler method would be to stagger scan rates (using prime numbers) within your MR Function DDC modules.  Refer to TCON 300 Chapter 13. The DDC modules have there own scan rates and control the point based on this scan rate and will override any Resident I/O Point scan rate defined on these output points. Programmer timers from within the SLI which the control critical items of plant and require a staggered startup procedure.

Issue Can Inovonics wireless equipment be used with Xenta Servers? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Inovonics Frequency Agile product line which is compatible with the Xenta Server driver is being obsoleted by the manufacturer Inovonics at the end of 2011. Resolution If you have existing devices installed in the field then they should continue to work and function. New installations should explore other options for wireless sensors due to unavailability from the manufacturer. The ability to add a RS232 wireless Inovonics interface was removed from XBuilder beginning in version 5.1.8.

Issue What are System Messages and how to stop them from coming into AMT. Environment All versions of I/NET Seven Cause System Messages provide information about events occurring in the system. Resolution A message can be generated when a point changes state, goes into alarm or even when a user logs on or off to the system. There are several things that the user needs to keep in mind. The set up and programming can be seen in https://ecobuilding.schneider-electric.com/search#keyword/TAC%20INET%20Documentation%20Error%20Correction%20in%20TCON%20300%20-%20TPA-DALL-09-0001.00/tab/documents Chapter 3 System Messages.

Issue Changed sa user name as requested and unable to log in to DbCreate using that username Unable to use standard "sa" password for "sa" username Environment DbCreate I/NET Seven SQL Cause Due to new security requirements from Windows and SQL you are unable to leave the SQL admin password as the default: Username: "sa" and Password : "sa".  When installing I/NET you will be asked to provide a new more secure password.  The "sa" username cannot and should not be changed. Resolution When installing I/NET have a new username for SQL ready.  This must be something that can be recorded and available to technician when needed When prompted, enter the new password.  You will have to enter in twice to verify the text To run DbCreate us the username: "sa" and the password that you entered during installation.

Issue Downloading to a 7920 MIP and it freezes up and stops communicating. Environment All versions of I/Net Software doing Access Control. Cause The software probably got corrupted during the download and needs to be cleared out to accept the latest bin file from the host. Resolution With Power on and the board mounted on the 7920, On Pin Header J4, connect Pins 1 and 2 Together, via jumper or whatever medium available Press the Reset button

Issue Station Address conflict Error in I/NET after adding a controller Environment I/NET Cause Each Station must have a unique Station Address Resolution Check Network Configuration at the host workstation for an available Station address Using the HHC, change the station address to an open address.

Issue During Construction it may be required to use a temporary database to allow access control to function before the IP infrastructure is in place. Environment I/NET Seven Cause A temporary database has been used during construction. The end user has an existing database that the new links and doors must be added to. In some cases the temporary database may be required to be used while the building is occupied so a smooth transition between the two databases is required. Resolution Construction Phase Determine in advance the link information to be used for each new Xenta 527, and the full address for each door Determine who will access which doors within the new construction and add these individuals to new or existing groups accordingly Commission doors and add badges using the temporary database by using the available TAP on the SLI. If you use a crossover cable to connect to the Xenta 527, be sure to clear routing tables at the end of construction Ensure that each Xenta 527 has an available patch cable and Ethernet port installed Inform the IT department or installer that I/NET must have port 50069 open DO NOT leave the Xenta 527 plugged into the Ethernet port during construction If the building becomes occupied, add badges to the door using a temporary database connected via TAP If you are using multiple SLI's during the construction phase, it is important to ensure you are using only 1 access control Database.  Any other machine must have access control disabled to ensure cards are not removed from the system. If you have to add additional badges to any of the SLIs or change the temporary Database, you may need to do a station restore for the changes to take effect. Adding the New Links and Doors to the existing system Verify that the Ethernet port by each Xenta 527 is functional by using a laptop to "ping" the Primary Host workstation. The lights on the Xenta 527 may show active Ethernet communication before the new construction IP is connected to the Local network. Connect to each controller using your temporary database. Perform a station save.  If you have any issues, this will function as your restore point. Connect to the Xenta 527 and ensure that the reference Hosts and link information is correct. Connect the Xenta 527 to the Ethernet port and cycle power. At the Host PC, Select Edit>Host Computer>Network Configuration Save the new Xenta 527's, SLI's, SCUs and Doors Select Access>Tenant Add the Doors to the appropriate Tenant Select Access>Groups Give the appropriate Groups access to the correct doors Verify you have given access to all appropriate people.  You may wish to compare the System View of each door on your temporary to the System View of each door on the site database Connect to the controller Select Edit>Controller>Station Save To clear the old database you will need to take the controller to Boot. select Edit> Host computer> software Restore Load the Bin file to the appropriate controller, but hit cancel after 10K have downloaded Load the Bin file again, this time allow it to finish. Connect to the controller Select Edit>Controller>Station Restore Choose the SLI option Select Edit>Controller>Station Restore Choose the DPU option Select all DPUs and restore Once this process is completed test several badges. Repeat steps 12-21 for each SLI under this Xenta 527 Repeat this process for each Xenta 527

Issue What functions can you do in I/NET if you change the Windows users rights? Environment All versions of I/NET Seven Software Cause Changing the Windows users rights affects the way I/NET functions. Resolution   User Account I/NET Seven Operation Administrator Power User User Install I/NET Yes Yes No Remove I/NET Yes Yes No Upgrade I/NET Yes Yes No I/NET Configuration Yes Yes Yes         DBCreate Functions       Create db Yes Yes Yes Import I/NET 2X Yes Yes Yes Verify existing db Yes Yes Yes Remove existing db Yes Yes Yes Backup db Yes Yes Yes Restore db Yes No No Import Docutrend Archive Yes Yes Yes Upgrade db Yes Yes Yes         Seven Reports       View Yes Yes Yes Run Yes Yes Yes Configure Yes Yes Yes Save Yes Yes Yes Print Report Yes Yes Yes Mount Archive Yes Yes Yes View Archive Yes Yes Yes Run Archive Yes Yes Yes Print Archive Report Yes Yes Yes         Archive Configuration       Event Archive Configuration Yes Yes Yes Run Yes Yes Yes Trend Archive Configuration Yes Yes Yes Run Yes Yes Yes View Yes Yes Yes         I/O Server Configuration       Promote Filemaster Yes No No Demote Filemaster Yes No No Promote Client Yes No No Demote Client Yes No No   There are two components of security available to users of I/NET Seven: I/NET Seven passwords and Microsoft Windows user accounts. I/NET Seven passwords are specifically aimed at limiting a user’s access to features and functions within the I/NET Seven system. The restrictions imposed by I/NET Seven passwords are application-specific (i.e., they only affect the I/NET Seven system) and do not provide a replacement for domain security methods. Microsoft is very clear about the importance of limiting permissions to users in a network environment. The user account permissions that are standard in Windows 2000 and Windows XP allow full management of the computer to users with “Administrative” group membership or any group containing administrative permissions. The “Power User” group permissions allow users to install programs but restrict what these users can do to the operating system. The “User” group is the most secure because its operators cannot modify operating system settings or other users’ data. Microsoft clearly states that operators assigned to the User group may have trouble running legacy programs. This should pose no problem for I/NET users since I/NET Seven has been specifically developed to run on the Windows 2000 and XP operating system. Most functions of I/NET Seven including general system operation, AMT (alarms, messages, and transaction) processing, reporting (Seven Reports), and archiving are available to an operator assigned to the User group or any group with those permissions. However, these operators cannot install I/NET Seven or delete or upgrade its database. Seven Reports is password-protected but can be configured within I/NET Seven to allow automatic logon to operators of a Host PC. The above spreadsheet shows the functions/operations that can be performed by members of the Administrator, Power User, and User groups. For further information about Windows security, please refer to Microsoft Windows online help for more information about user accounts, permissions, and Microsoft Management Console best practices". https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc750076(v=technet.10)

Issue I/NET Seven is unable to connect to a Xenta 527 on Windows 7 Pro based computer. I/NET Configuration can not see any online NPR devices but a direct serial connection connects normally to the 527. Environment I/NET Seven rev 2.4X and above Windows 7 Pro (32-bit) Xenta 527 Cause Even though the Windows firewall was turned off, some ports were blocked by default. I/NET communicates on Port 50069. Resolution Go into Windows Firewall through Control Panel Select Advanced Security Select Inbound Rules There may be multiple instances of I/NET Seven I/O Server entries for \Inet seven\inetiosrv.exe. Likely four instances, two public UDP and TCP and two for Private UDP and TCP. Public and Private profiles need to set for "Allow." Double click any I/NET Seven I/O Server instances that are not enabled, then change the Action to "Allow the Connection" Select OK or Apply

Issue Procedure to replace EPROM when doing an upgrade. Environment All versions of I/Net software using Access Control on DPU 7910 and EPROM version of the  DPU 7920. Cause Upgrading the software and hardware on a system which work with each other. Resolution The following steps should be followed to ensure that the devices do not get damaged during the process of the upgrade: Remove power form the device Carefully remove the Eproms using the appropriate tools Replace new EPROM with correct orientation (notch on the chip) Power up the device again and hit the reset button. Verify that the transmit and receive lights are on and communications to the MCI has been re-established. Read a card and verify that the transactions are coming into AMT.

Issue Running Server/Client on a system Environment I/Net Seven version 2.13 and above. Cause Server client on a system that is running on different versions and not working. Resolution For Server/Client to work on a system, I/Net has to be installed on all the PCs and they all must be the same version as well. The following steps needs to be followed to configure this correctly: The Host PC that will be acting as the Server must have the current database. Modify the active profile in the Configuration Editor In the WorkStation Options, set this to be Standalone On the other PCs, this would be set to Remote Client An editor will come up stating the "the database will be replaced" Click on the proceed button to connect to the Server. Once completed, the client PCs would now be looking at the Server

Issue What are the effects of a connection object on the I/NET controller lan? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta 527/913/731 I/NET Cause The I/NET communication protocol has a maximum baud rate of 19,200 bps and this allows for a maximum of 10 messages a second to occur on the I/NET controller lan. This limit applies to the entire controller lan not just a single controller. Optimal performance will be at 5 or 6 messages a second on the controller lan. Resolution Any connection objects involving I/NET points need to be aware of the limits imposed by the controller lan protocol and adjust the periods of connection objects to avoid exceeding these limits. Every connection object that the source is from I/NET requires the value to be read from the I/NET controller before it can determine if the value has changed to send to the target of the connection object. If the default period of 10 seconds is used for all connection objects then only 100 points will consume 100% of the bandwidth on the I/NET controller lan to meet the demand and negatively impact the performance of the I/NET network. Instead count the number of connection objects with source values from I/NET. Divide this number of 4 to allow room for values being written to the I/NET network to determine the minimum recommended period for your connection objects to avoid overloading your I/NET controller lan. Ex: 250 points being sent from I/NET to a 3rd party system / 4 writes a second = 63 second period. This could result in some larger then expected periods and some points might be more critical then others which will require some prioritization. If of the 250 points only 15 require faster response time then they can use a lower period, but this will affect the period used for the lower priority points. It is recommended to avoid periods below 10 seconds if at all possible. Ex: 235 points at lower priority / 4 messages a second = 59 second period 59 second period for low priority points / 10 second period of high priority points = 6 polls per point * 15 points at high priority = 90 reads for high priority points. 235 points + 90 polls = 325 values read from I/NET / 4 messages a second = 82 second period for lower priority points to accommodate 15 high priority points.

Issue Is it possible to use 24VDC as power supply to the OP7? Environment OP7 power supply adapter included in package. Cause The documentation only recommends using 24VAC as power supply. Resolution Usage of 24VDC is not tested, and therefore not recommended or supported.

Issue 7771 (Modbus ICI) will not keep station address after station restore. Environment I/NET Seven 7771 (Modbus ICI) Cause The cause is the EEPROM rev in that unit. Resolution Update EEPROM to version 3.32 to work correctly in I/NET Seven.

Issue Process to use I/NET Encryption feature to encrypt an existing network or segment of network Environment I/NET Cause I/NET system contains or protects items that need addition security or separation from other I/NET networks. Resolution To encrypt the Xenta 527 and Host network   Important: ********** The Unencrypted and Encrypted UDP ports should be different from each other     (Ex. Unencrypted: 50069, Encrypted: 49152) ********** The Unencrypted UDP port for all routers and workstations should be the same (Ex. Routers: 50069, Workstations: 50069) ********** The Encrypted UDP port for all routers and workstations should be the same (Ex. Routers: 49152, Workstations: 49152) ********** The Encrypted password for all routers and workstations should be the same (Ex. Routers: Test, Workstations: Test)   Choose an unencrypted UDP port, either default 50069 or a number between 49153-65535 Set the workstation Advanced IP UDP setting to the chosen unencrypted port Shutdown I/NET, Shutdown I/O Server(make sure I/O server is shut down) <-check Task Manager to see if all I/NET services are shutdown Bring all new 527 routers online within the network Log into the 527 web interface, go to I/NET configuration profile Set 527 UDP to the chosen unencrypted port you chose in step 1, set the host reference to the workstation IP that is the filemaster/standalone Save and Restart 527, restart I/NET Filemaster/Standalone Bring up NP routers under I/O server, check if all routers in the network have appeared in the list If not all routers have appeared in the list check the unencrypted udp port of the workstation and 527 udp port match Once all routers have appeared in the online list, click on each router and modify its Advanced IP settings Check mark the Enable Encryption box, the default encryption port is 49152, make sure you leave the encryption port default or choose an encryption port that will be the same for all routers Enter a password for encryption(Ex. Test), make sure the password is the same password for each router Click OK, the router should restart with the new encrypted settings Repeat steps 10-13 on all routers within the list All routers should disappear one by one from the Online list as you enable encryption on each router and OK the settings change Under the main IO configuration screen click on Advanced IP Check mark the Enable Encryption box, the default encryption port is 49152 or choose the encryption port that corresponds to the same exact encryption port you choose for the routers Enter in the password for encryption exactly as was done for the routers Click OK, Click OK on the main screen to save the settings Shut down I/NET, Restart I/O Server(make sure I/O server is shut down) Restart I/NET Open up IO configuration once logged in Click on NP Routers The routers you have encrypted should appear back onto the Online list Troubleshoot: If the routers you have do not appear back onto the list, check each router’s web interface and make sure that the UDP port is set to the encrypted port. If the routers come back but there Name appears as numbers (Ex. 1023,1124) then what happened is the routers are encrypted but the host workstation cannot understand the encryption. To undo everything and start over uncheck encryption on the host workstation and then login to each of the router’s web interface and reset the UDP port to the default I/NET port. Make sure to restart I/O server to make changes take affect. Test the encryption by having standalone machines and other filemasters not on the same encrypted port try to pull up the routers either by NP routers in IO configuration or Host->Netcon, they should not be able to see any of the routers/host workstations that were encrypted.     To add a 527 to an existing encrypted network   Bring the router online on the chosen unencrypted port Shutdown I/NET and I/O server Modify IO configuration Uncheck enable encryption on host settings Advanced IP Make sure the unencrypted port is the same port with the router you are bringing online Shutdown I/NET and I/O server and then restart I/NET Modify the active IO configuration, under NP routers you should be able to see the new router but none of the old encrypted routers Modify the new router’s Advanced IP settings Enable encryption on the new router and assign it the default/chosen encrypted port and enter in the chosen password for encryption Click OK, the router should restart with the new encrypted settings Edit the Advanced IP of the host workstation Recheck enable encryption and reenter the default/chosen encrypted port Reenter the chosen encrypted password Click Ok to confirm settings Shutdown I/NET and I/O server then restart I/NET Modify the active IO configuration, go to NP routers All routers should appear on the list now, the existing encrypted routers on the network and the new encrypted router on the network

Issue 7798B replacement with 7798C Environment I/NET Cause The .sav file for the 7798B and the 7798C are identical.  Resolution Perform a station save on the 7798B Remove the 7798B and replace with a 7798C Save the 7798C in Netcon Select Edit>Host Computer Software Download the Software to the 7798C Connect to the controller Perform a station restore

Issue Xenta 527 showing error message "Packet no match on SeqChain type: 2" in HyperTerminal Environment I/NET HyperTerminal TelNet Xenta 527 Cause This error has been added as a means to aid in troubleshooting.  The specific Build of the Xenta 527 system program will change the meaning of this error.   In 5.1.6 the error indicates a request to the reference hosts for an updated routing table       Resolution 5.1.5 Contact the local IT department to find possible causes of corrupted IP packets You may need to use an ethernet capture device to determine the source of the corrupted packets 5.1.6 If the error is occurring only rarely it can be ignored.  You may see an increase in error traffic if there is a problem with TCP/IP communication Contact Product Support if further assistance is required

Issue DDC Control Override MR Control Override Environment I/NET MR-AHU 7718 7716 7756 7798 7793 Cause A control is needed to override the standard control for a point. Possibilities include using an ASC point for a different purpose. Resolution The most effective means to program an over-ride all logic is to use an Event Sequence containing the with Lock element. This will over-ride anything other than a point in manual control. Please see Appendix A "DCU Control Hierarchy" from TCON300 for complete Control Hierarchy.

Issue System PC crashed and there are no backup available to restore from, what can be done? Environment All versions of I/NET software. Cause There could be numerous causes for a PC to crash, like power surges, age of the PC and viruses. When this happens, if there are no backups on other media devices, then it will have to be rebuilt from scratch. Resolution To resolve this issue, if the data can be retrieved from the PC then here are a few steps that needs to be followed to get the database in tact: Go to Windows Explorer and look in C/Program Files/Microsoft SQL Server Expand that and click on the MSSQL Folder, expand that and go to Data. There are two files that needs to be retrieved, the InetDB.mdf and InetDb_log.LDF files. Copy that on to a media and place on the replacement PC which should already have I/Net installed on it. Shut I/NET, I/O Server and SQL Server down. Repeat steps 1-2, then copy the files from step 3 into the folder after renaming then current ones old. Restart MSSQL Server, I/Net and I/O Server. This should allow the database to be resynched with SQL. If this is not possible and there is no way to retrieve the data then it would have to be rebuilt from scratch.