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 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.

Issue Unable to install I/NET Seven after downloading software from Buildings Business Extranet. Gets error "unable to open, file is corrupt" when using WINzip Environment Windows XP Windows Vista Windows 7 Windows Server 2003 WinZip Inet 2.30 or below WinRAR   Cause Software was created in a number of parts which all parts needed to be downloaded before unpacking was attempted. WinZip is not a valid software to unpack the Inet install files downloaded from the Buildings Business Extranet. (now ecobuildings) Resolution Downloading all parts of the I/NET software from the Buildings Business Extranet Make sure all files are in the same folder. You will need to use WinRAR to unzip the files Download from here http://filehippo.com/download_winrar_32/ You must unzip the files before trying to run the install, if you open part 1 of the files this will automatically unzip all parts of the software, once all files have been unzips the install will work NOTE: This was an issue with Inet software versions 2.30 and below, all new version can be downloaded and unzipped without issue from the ecobuildings website.

Issue Lan Tap Overflow message received in AMT Environment All versions of I/NET Software Cause The message capacity of a LAN Tap has been exceeded and they are now being FI/FO (First In, First Out) mode, meaning that the first message that came in will be the first one that goes out. When this happens, the LAN Tap Overflow message is displayed in AMT. Resolution To resolve this issue, verify the following: Open up AMT and look at the Messages and see if there are any controller that having issues Verify that address and correspond that with the Host or Link Tap that it is coming from. Rectify the issue, whether it is communications or power and the error should go away.

Issue Unable to communicate to a Hand-Held Console (HHC) on Windows 7 Product Line TAC INET Environment Windows 7 HHC Cause Com Port settings not working with the HHC Resolution To resolve this issue, change the following port setting that is used to communicate to the HHC. DCB is set for Even Parity Flow Control is disabled Stop bits is 2 Baud Rate is 1200

Issue Leakage voltage on relays Environment I/Net Seven versions using SCU 1284's. Cause There is a small leakage current through the integrated MOV transient suppressor across the NC and NO contacts on the four relays that are used to control the door locks. Resolution If the relay is connected to a very high impedance (electronic) device input where it is falsely detecting as a relay ON condition, there are two things that can be done: 1. Place a 10,000 Ohm resistor on the device input to ground (or relay output to ground) 2. Move to one of the other unsuppressed relays ( relay 3, 4, 7 or 😎

Issue Is IPv6 supported with I/Net and SE Vista Controllers? Environment NPR2000 Xenta 527-NPR, 527, 731, 913 Cause IPv6 with I/NET and Vista Controllers Resolution  I/NET and Vista Controllers DO NOT support IPv6

Issue Using Access Initiated Control to trigger an event sequence Environment I/NET Seven 7798 Cause Custom door applications sometimes require several steps to be initiated on a reader entry Resolution Create in Internal DO point (Point1) where 0 = off and 1 = ON, The scan interval should be shorted than the expected time between 2 card reads at the door. Add a Calculation to point1 that sets it equal to 0. [C0 where C0=0] Add an event extension to the point that triggers your desired event sequence on the specified state of ON Create an AIC that starts point1 on a reader Entry Create your event sequence with the desired programming. The effect should be that a reader entry causes Point1 to turn on triggering the event sequence

Issue  Temporary groups can't get a PM time, only AM Environment I/NET Cause The time are using US settings AM/PM on for example a European PC Windows don't use AM/PM Resolution Enter Control Panel and choose Regional and Language Settings On first tab click Customize Choose tab "Time"  Set AM and PM symbol to AM and PM Click OK Restart I/NET IO server and try again.

Issue AMT message "Time-sync failed" Environment I/NET Seven AMT Cause The Time-sync failed message indicates that an attempt to sync time with a DCU has failed. Resolution Time synchronization is a function of DCU Synchronization. This is only intended for use with direct-connect, TCP/IP or AD/AA communication. If your site is using Integrated Dial or NPR Dial connection, this explains the alarm and must be deactivated. To View the systems DCU synchronization settings. Log into I/NET and select Edit>Host Computer>Network functions. From there you can select a link via a dropdown menu view the "Sync" setting for each controller. If Sync is enable on any controller that are offline or no longer exist, disable synchronization (and any other Host function)  If time sync is not desired, it can be disable which will also remove the alarm. If time DCU synchronization is desired, This is likely an indication of a communication failure. Determine if this has occurred on an entire Controller LAN or just a single controller. Use this as a starting point and work towards the PC looking for communication errors.  

Issue Even though Windows Server 2008 R2 is exclusively a 64-bit operating system, 32-bit applications are supported by enabling the WoW64 optional feature. NOTE: These are general instructions for utilizing the WoW64 function. Not all Schneider Software will be able to run in an emulated environment. If uncertain, please check with Product Support Services to ensure proper installation. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows Server 2008 R2 WoW64 feature. All 64bit OS Cause If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. WoW64 option in in undesired state. Resolution If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. The WoW64 execution layer is an optional component that is installed by default on R2 releases. You can save resources by removing the feature if you are not going to be running 32-bit applications on your Server Core install. Install the WoW64 Execution Layer using the following command: dism /online /enable-feature /featurename:ServerCore-WOW64 If your solution has a .NET 32-bit dependency, then also invoke the following sequence: dism /online /enable-feature /featurename:NetFx2-ServerCore dism /online /enable-feature /featurename:NetFx2-ServerCore-WOW64 Note: In Windows Server 2008 R2 RC1, WoW64 is enabled by default. If you don't want WoW64 enabled, just disable the feature as follows:  dism /online /disable-feature /featurename:ServerCore-WOW64

Issue Generating a Xbuilder project results in the error message "The size of the generated project is xxxx KB, which exceeds the maximum size 8192 KB". Environment Xbuilder 5.x.x Cause The generated project size exceeds the maximum limit due to the following reasons: The project contents made up of graphic pages, inserted networks (LON, I/NET, etc), large images (BMP, GIF, etc), or imported files in the UserTargetImage directory cause the project to exceed the limit. The option "Send Project backup file to target device" is checked and this causes pushes the project size over the limit. Resolution Generate the Xbuilder project to see how far above the limit the project currently is. Open the Project\Settings and uncheck the "Send Project backup file to target device" and regenerate the project to see the difference in file size. If the size difference is significant then check for large files in the project directory that should not be sent to the device such as project or device documentation files such as PDFs. Remove these files from the Xbuilder project directory and generate the project again.  Search the Xbuilder project directory for the largest size files such as graphic pages and try to find way to reduce the size by converting background image formats that will result in smaller file sizes. Example convert BMP file to PNG or JPG format.