Issue When integrating I/NET into Vista; by default I/NET alarms do not show the station name, link name, or device name (point name). Environment I/NET Seven Vista 4.5 and up Cause The settings on the $AlarmColumns object in Vista do not have the I/NET column fields checked by default. Resolution To customize the Vista alarm queue with the proper fields for I/NET alarms please follow these steps. Click on the root level TAC Vista object in the Vista tree. Right click on the $AlarmColumns object and choose properties. Check the desired boxes in the Columns fields. Note: The link name selection will display the I/NET link name that the alarm originated from. Example: Link 5 South Campus The station name field will display the I/Net station name that the alarm originated from. Example: AHU5 The device name field will display the physical point name programmed within the I/NET controller. Example: OA Damper The site field is only needed when using DLA (distributed link architecture) and will display the name of the DLA site Example: Site 1 North Campus

Issue Customers wanting to use a Barcode Reader for door access Environment Access Control site wanting to use Barcode Readers Cause Barcode Readers often are a higher  Resolution I/NET The SCU is the best you could have so that makes it easier with memory requirements and so forth. Since you have the SCU, set it up for 26-bit Wiegand (2 parity bits and 24 data bits). It would look like this: e eeeeeeee eeeeooooooooooooo o That is a 1-bit starting bit, even parity, 8-bit facility code, site number, card number, 16-bit segment, and the 1-bit ending parity (26 bits all together). That is how many data bits the reader normally takes. 26-bit Wiegand is typical and most common. The true bits are the facility code, site and card number. The beginning and end is the parity. For more information, see TCON300, beginning on page 9-59. This is the key card translations section, and may be valuable in figuring out the solution to the bar code reader. Lastly, one idea is to contact a company called RFIDeas.com. They make a bar code reader that may be a solution. If the bar code reader is outputting a card number larger than 16 digits, convert it to 26-bits of Wiegand data (it can handle up to 64-bitWiegand). If it goes over 64-bit, they have a special firmware which allows up to 254 bits of wiegand data. With the SCU, the 26-bit is the standard. Code 128 is used to barcode INET products. The Cypressworld CVX-1300 is an alternate solution for connection between the I/NET SCU and the Barcode Reader. Continuum Code 39 is used to barcode the serial number on Continuum and Pelco boards.  Most readers can auto switch between these and other code types.  

Issue IDisc Wand is no longer available from Schneider Electric Environment Any I/NET Software Program and Access Control Cause Customer cannot get the IDisc Wand from Schneider Electric Order Entry Resolution There is a third party supplier that handles a direct replacement unit. Click here for a PDF of the part number and cut sheet.

Issue Calculate the Memory usage of an MR controller Environment MR55 MR88 Any other MR that allows DDC development Cause Since the MRs have a limited memory allocation, you need to determine if you are getting close to the maximum allowed. Resolution Click here to download a zip file of an Excel spreadsheet that will help determine the memory used in the DDC system.

Issue Trying to find the IDISC Reader Part number IDISCWAND Environment I/NET IDISC Cause The model IDISCWAND tool is no longer an active product with Schneider Electric. Resolution The model IDISCWAND tool is no longer an active product with Schneider Electric. The following information describes how you can acquire the necessary components to form the IDISCWAND. The IDISCWAND is comprised of two component devices as follows - The hand held wand (602063-0002) the hand probe used to contact the IDISC buttons for reading and enrollment of the access control credential into the system. The wand requires an Adapter to allow system communications to the IDISC. The wand can be purchased from Maxim Integrated Products using the Maxim part number DS9092GT#. The second component is the RS232 communications port “Adapter” (602073-0010). The cable from the wand (shown above) plugs into the RJ11 port on the Adapter. The other end of the Adapter is a standard D-subminiature 9-pin RS232 connector. The D-sub end of the Adapter mates with the 9-pin RS232 communications port of the PC workstation (TAC I/NET Seven Host), or the RS232 port created with a USB to Serial port adapter. The Adapter can be purchased from Maxim Integrated Products using the Maxim part number DS9097U-S09#. The “#” symbol at the end of the two part numbers designates RoHS compliance and is the only version currently listed on the web site referenced below. Parts without the “#” would be functionally equivalent. The part number DS9092GT# Wand and DS9097U-S09# Adapter can be purchased from Maxim Direct at - https://www.maximintegrated.com/en.html Enter the part number in the “Price and Availability” search window to see price and lead time on the item, and place an order. View PDF document here.  

Issue Using the LANMON 3 tool with a 78010 TAP with a MIP01 board attached Environment I/NET Controller LAN 78010 TAP with a MIP01 Board Cause The EPROM is an obsolete item and therefore is not available anymore. Because of this, the 78010 with a MIP01 board must be used instead. The modified special 7810.bin (LANMON binary) is intentionally set to not retained in memory through a power cycle. Once the LANMON binary is installed into a MIP, there is no longer any way to communicate with it as a "downloadable device". Power cycling is the only way to bring the MIP back to the boot state. So basically you have to leave the 'DIP SW' the way the Mip Document states. Because if you power down the 7810 TAP to change the 'DIP SW' per the TCON 310-0305, you will lose the program in the TAP. Resolution List of material that will be used for the LANMON 3 operations. Click here to download a .zip file containing all of the necessary executables, bin files, and manuals. The Custom 7810.BIN file (Modified Printer Tap BIN) The LANMON 3 Master Program “EXE” file (LanMon 300.exe) TCON 310-0305 PDF Manual for the LANMON program. A black 78010 TAP or a base mounted 78010 TAP, with it’s associated Power Transformer A Memory Interface Processor (MIP01) Board Cable – CBL071 (606105-0035) – TAP to 9 pin (Female) Serial You might have to provide a USB to 9 pin (Male) Serial Adapter Setup Process If the 78010 TAP (either the “Black” or Base-mount unit) has never had a MIP01 installed before, some items on the Motherboard must be removed prior to installing the New MIP01 board. Remove power from the base unit. For those units that do not have a power switch, remove the power connector. Remove the base unit parts as shown in Table 3 below. Orient the MIP01 with the negative end of the battery (unmarked end) pointing upward (toward the notched end of the white outline of the base unit processor). Insert the MIP01 into the processor socket. Note, the MIP01 must be set up as a “Printer TAP”. The Steps to set this up are as follows: With the power OFF of the unit set all the DIP switches (1 to 😎 to the UP position. Cycle the power ON then cycle the power OFF Then set up the "Printer TAP" using the DIP switch settings defined below: Once this is unit set up with DIP switch setting below, it will work as a LANMON 3 Unit. Please note that the LanMon TAP does occupy a node on the CLAN. So this unit requires an address that is not already used in the System. The Address range is 0 to 62 (63 is not a valid address) DIP Switch settings: Switch 1 -- DN Switch 2 – DN Switch 3 -- DN Switch 4 -- DN Switch 5 -- DN Switch 6 – UP = Tap Address 32 Switch 7 – DN = 19200 baud CLAN (Choose one or the other) Switch 7 – UP = 9600 baud CLAN Switch 8 -- DN   The first 6 DIP switches are used for the addressing of this TAP on the CLAN. In my example above, my unit is set to address of 32 (SW# 6 is up) Switch  1 – UP = 1 Switch 2 – Up = 2 Switch 3 – UP = 4 Switch 4 – Up = 8 Switch 5 – UP = 16 Switch 6 – Up = 32   Go into the following I/NET Editor – Edit > Host Computer > Network Configuration. Make sure the “Lanmon 3 TAP” is saved.   A special BIN file must be loaded into the MIP01 board. There are several steps in doing this process. Go to the following location and Rename the existing file from 7810.bin to 7810.org. Then copy the special 7810.bin that is the “LanMon 3” BIN   Go into the following editor and do software restore to the LANMON TAP: Edit > Host Computer > Software Restore   During the software download to the LANMON TAP, an error message will appear at the end of the download that says, "Software not loaded." This is expected. Click "OK" on the message.   The LANMON 3 program may be started now. The file to use is the LanMon 300.exe file. Double click this file and that will start the LANMON program. Please note the comments in the capture below. The chosen Com port will be the port the CBL071 is connected to on the PC. The Output TXT file will be located in the same directory where the LANMON program (LanMon 300.exe) is stored on the hard drive. The Capture code should be set to this format -- B E1 M N O And "Enter stroke" now will start the LANMON program. Please note the TAP LED pattern in the LANMON mode is as follows: Port “A” the Red LED only flashes. Port “B” the Green LED only flashes The modified special 7810.bin (LANMON binary) is intentionally set to not retained in memory through a power cycle. Once the LANMON binary is installed into a MIP, there is no longer any way to communicate with it as a "downloadable device". Power cycling is the only way to bring the MIP back to the boot state. Leave the 'DIP SW' the way the Mip Document states. If the 7810 TAP is powered down to change the 'DIP SW' per the TCON 310-0305, it will lose the program in the TAP.

Issue Some issues which this article covers are: What rules or recommendations should be used with Indirect and Global Points? Why might a global point not change? Attempting to alter a global AO/DO points' value/state, by "Point Control" without "Manual Mode" being used, and the change does not take place. (Referred to as Global Output Retentive Feedback.) What scan rates should be used for global / indirect points? Product Line TAC INET Environment I/NET Software Cause Often within a system, a point's status or value within one controller has to be shared or used in other controllers connected to the system. An example could be an outside air temperature sensor connected to a controller. The value of the outside air temperature in that controller can be transmitted across the I/NET network to be used in algorithms in the other controllers. The I/NET software and firmware provides the mechanism to transmit and receive point data system wide. The outside air temperature point in this example would be called a "global point." The receiving points within the other controllers that reference and thereby mimic the global point's temperature value are called "indirect points." Resolution Each controller is capable of a total of 128 global and indirect points. Global points are used to share information from one controller to another. If a point is not a global point, the state or value of that point is available only to other points in the same controller. If a point is specified as global, you may use it to control an indirect point in another controller. Any internal or external point may be designated as a global point. When a point is defined as global, a corresponding indirect point must be set up in the additional controller(s) to receive the global point's data. The global point must be designated with the appropriate globalisation level. There are four (4) different levels of globalisation, as shown below: Local: This point provides information only to this controller. A global setting of "Local" indicates that this point is not a global point. LAN: This point may provide information to an indirect point in any device connected to this controller LAN. Link: This point may provide information to an indirect point in any device connected to this controller's Host LAN. This setting WILL NOT send global data across links headed by NetPlus Routers. System: This point may provide information to an indirect point in any device connected to the I/NET system including ETHERNET. This setting WILL send global data across links headed by NetPlus Routers. Global points "broadcast" or send their state/value to corresponding indirect points. The frequency of the broadcast depends on the point type. All global point types broadcast under the following conditions: The controller has been restarted, either by a power restore, the controller's red reset button has been pushed or the database, DCU0000.sav file, has been "Restored." A global point has been changed from "Automatic" to "Manual" or from "Manual" to "Automatic." This does not apply to the Test Mode. A global point changing to or recovering from the "old data" state due to either a communications failure, or an analogue input point falling outside or re-entering its sensor limits (defined within the 'Resident Points' editor). Global analogue points (AI, AO, GI, GO) broadcast whenever their value changes through a range greater than the specified "Broadcast change counts" parameter (defined within the 'Resident Points' editor). Global discrete points (DI, DA, DO, DM, DC) broadcast whenever their state changes. Global pulsed input points (PI) broadcast whenever their "Scans between broadcasts" parameter is exceeded (defined within the 'Resident Points' editor). When requested to by the associated indirect point. Indirect points "receive" their state/value from their corresponding global points. Indirect points must reside in a different controller from the global point, and they act as receptors for the value or status information broadcast from the global point. When entering an indirect point, you must specify the name or address of the associated global point. The frequency of the update from the global points depends on the following. Their associated global point broadcasting its status or value. In addition, an indirect point can request an update, at the indirect points scan rate, from their associated global point. This happens when: The indirect point is first entered. When the indirect point's controller is restored or reset (power restore, station restore or the red reset button is pressed). Whenever the local control LAN reconfigures. Whenever an AO or DO indirect point is put into "Manual Mode" or back into "Automatic Mode." When the indirect point has not seen a status/value change from its associated global point within 2 times the indirect point's scan interval it request an update from its associated global point. It then reports the update on its third scan interval. If the indirect point is unable to be updated from its global point (i.e. no communications) then the indirect point will report its last valid updated value/state and will flag the value/state as "Old Data." Direction of Point Data's Flow INPUT POINTS (AI, GI, DI and DA): The data flow is from the global input point broadcasting to the associated indirect point only. The flow is "one way" only, that is to say, if the associated indirect point should alter the state or value is not broadcast to their corresponding global point. GLOBAL INPUT --------------> LAN -------------> INDIRECT INPUT OUTPUT POINTS (AO, GO and DO): All output points (both global and indirect) broadcast their state or value changes to the other associated point(s). The flow is "two way," that is to say, a change to either the global or the associated indirect point will change their opposing point's value accordingly. GLOBAL OUTPUT <--------------> LAN <----------------> INDIRECT OUTPUT Click Here to view some recommendations / rules for Global and Indirect Points as well to view this complete article as one document.

Issue Transformer for I/NET Controllers Environment XFMR1, XFMR2, XFMR3, XFMR4, XFMR5, XFMR6, XFMR7, XFMR8, XFMR9, XFMR10, XFMR11 IRB8, IRB8HC Relay boards 7700, 7740, 7741 DCUs 7750, 7760, 78XX, 72XX UCs, 7716 7718, 7780, DPU3100, DPU7910A, DPU7920 78XX TAPs 7780 DLCU 7728 I/SITE I/O Cause The following table describes each transformer, the primary power required, the secondary power supplied by the transformer and the products each transformer model supports. Some of these transformers have two secondary outputs and these are shown in the table. Resolution Download the attached PDF document here. Model Number Description Comments XFMR1 Transformer, 120Vac Primary, 20Vac @ 3.4A Secondary IRB8, IRB8HC Relay boards XFMR2 Transformer, 120Vac Primary, 10Vac @ 3.6A and 36Vac @ 0.7A Secondaries 7700, 7740 7741 DCUs XFMR3 Transformer, 240Vac Primary, 10Vac @ 3.6A and 36Vac @ 0.7A Secondaries 7700, 7740, 7741 DCUs XFMR4 Transformer, 120Vac Primary, 13.5Vac @ 2A and 24Vac @ 2A Secondaries 13.5Vac for baseplate mounted 7750, 7760, 78XX. 24Vac for 72XX UCs, 7716 XFMR5 Transformer, 240Vac Primary, 13.5Vac @ 2A and 24Vac @ 2A Secondaries 13.5Vac for baseplate mounted 7750, 7760, 78XX. 24Vac for 72XX UCs, 7716 XFMR6 Transformer, 120Vac Primary, 24Vac @ 2.4A Secondary 72XXUC, 7716, 7718, 7780, DPU3100, DPU7910A, DPU7920 XFMR7 Transformer, 240Vac Primary, 24Vac @ 2.4A Secondary 72XXUC, 7716, 7718, DPU3100, DPU7910A, DPU7920 XFMR8 Transformer, 120Vac Primary (plug-in), 13.5Vac Secondary (DIN connector) 7750, 7760, 78XX TAPs XFMR9 Transformer, 277Vac Primary, 24Vac @ 2.4Vac Secondary 7780 DLCU XFMR10 Transformer, 120Vac Primary, Dual 24Vac @ 2A Secondaries 7728 I/SITE I/O XFMR11 Transformer, 240Vac Primary, Dual 24Vac @ 2A Secondaries 7728 I/SITE I/O

Issue Operating Systems and SQL Supported in I/NET Seven 2.40, 2.40A, and 2.41 Environment Windows Server 2003 w/ SP1 Windows XP Professional w/ SP3 Windows Vista Enterprise w/ SP1 Windows 7 Professional 32-bit SQL Server 2000 Desktop Engine(MSDE 2000) SP4 SQL Server 2000 Standard SQL Server 2000 Enterprise SQL Server 2005 Express SP3 SQL Server 2005 Standard SP3 SQL Server 2005 Enterprise SP3 SQL Server 2008 Express (32-bit) SQL Server 2008 Standard (32-bit) Cause Issues may arrive if the I/NET software and SQL Server versions do not follow the below guidelines. Resolution  Click here to download this document in PDF format.     Operating Systems     Windows Server 2003 w/ SP1  Windows XP Professional w/ SP3  Windows Vista Enterprise w/ SP1  Windows 7 Professional 32-bit  SQL Server  SQL Server 2000 Desktop Engine (MSDE2000) SP4   Yes   Yes       SQL Server 2000 Standard   Yes         SQL Server 2000 Enterprise   Yes         SQL Server 2005 Express SP3   Yes   Yes   Yes   Yes   SQL Server 2005 Standard SP3   Yes   Yes   Yes   Yes   SQL Server 2005 Enterprise SP3   Yes         SQL Server 2008 Express (32-bit)         Yes   SQL Server 2008 Standard (32-bit)         Yes  General Notes: Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, or 2008. It is strongly recommended that you defragment the PC's hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. The use of Microsoft SQL Server 2005 Standard or Enterprise edition, or any edition of Microsoft SQL Server 2008 will require that the PC have at least 2 GB of RAM. Microsoft SQL Server 2005/2008 Express Edition cannot be used on a TAC I/NET Seven filemaster.

Issue PageGate allows for network paging or network wide SMS messaging from any combination of the following modules: web, email, commandline/ascii, serial, TAP-in and (GUI) windows workstations. SMS or text messages can be sent to alphanumeric pagers, numeric pagers, cell phones, PIMs, billboards or pcmcia pager cards. For capturing and paging I/NET Seven alarms and messages the “Get Serial” module from PageGate is used. Environment I/NET Seven PageGate Cause Network paging or network wide SMS messaging required. Resolution Click here to download this document as a PDF Configuring I/NET to send a message Open up the IO Server. Choose your configuration profile. Maybe direct connect. Click Modify. Under Peripherals, change Text Output Port to a COM port that is not being used, COM3 for example. I/NET will most probably be using COM1. See screen cap below. Set Baud Rate to 9600. Click OK to close out the Configuration Profile Screen. Restart I/NET and I/O Server for changes to take affect. Open up Alarms, Messages, & Transactions. Go to the Edit drop down menu and select Text Library. Here you will need to know the address for the point that you want to generate a message for when it goes into alarm. Choose add to enter point address and desired text message. As you can see above you can enter any text message you want. I/NET is now configured to send a text message to PageGate. Hardware Connections for PageGate-I/NET interface Three Com Ports are required to send the message from I/NET to PageGate Server. One for the I/NET port, a second for the Text Output Port so AMT can send the message, and the third COM port for PageGate to catch the message. Physically connect the Text Output Port to the PageGate COM port that will be catching the message. See Illustration below. Note:   If you run out of COM ports you can go to Radio Shack and purchase a USB to serial cable. It comes with the software to create another COM port. Be aware that it is not plug in play. The software/PC will refer to that USB port as your new COM port. In other words, if you take the USB plug out and insert it into another USB port you will have to repeat the installation to create another new COM port and it will have a different number then you will have to go back into  I/NET or PageGate to point to the right COM port. I found this out because my customer decide he wanted to move his USB cables around and then PageGate quit working. Configuring PageGate PageGate consists of PageGate server, PageGate Admin, & PageGate Monitor. From now on I will refer to PageGate as PG. PG Server is an e-mail server and will create an e-mail domain such as inet@villadematel.com. PG Server can be ran as a Windows NT application so the customer does not have to worry about starting PG when he boots his machine up. PG Monitor will show I/NET generate the alarm, PG catches that alarm, and PG Server e-mails the message out. It is not necessary to run PG monitor unless you are setting up the software or trouble shooting a problem. Follow these steps to assist you in setting up PG to send your message to a cell phone or pager. Go to http://www.notepage.net/ to download the trial version.  Install the software and then open up PG Admin to begin configuration. The PG software file system is organized in a tree structure. Open up Settings under, Program, and PageGate. From this point on reference tree structure on screen caps to navigate through PG. Under settings choose Run PG as an application and check the box next to scheduler, GetSerial and Dialer 1. Remember to go back and change to NT service once you get customer set up. Set the capture serial port for PG, baud rate, parity, data bits, stop bits, handshaking, & init string as you see below. These are the settings that I/NET uses when it transmits a message out the Text Output Port. Go to the GetSerial drop down to Record and enter the Start Pattern and End Pattern you see below. This tells PG how to determine what the message is. Under Recipient choose static recipient and give whatever name you want. The person or group that will be receiving the message. Now name your Static Sender. The application (In our case I/NET) that is sending the message.  Select Message and choose Dynamic Message since our text alarms from I/NET will be different most of the time. Put START offset at 6 so PG will know when our message starts and –4 so it will know when the message ends. 6 being the length of “START “ plus a space and –4 being a space plus the length of “END”. We have now configured PG Get Serial to capture the I/NET message. Connectors. PG will always require at least 1 dialer running and if you are sending a message on the internet you will need to set up the Global settings as well. Under SMTP create a Local Domain. When your customer receives a message it will be from “static.sender.name@localdomain.com”. For example Villa De Matel receives a text message from inet@villadematel.com. Then enter your customers DNS server addresses. You only need one but enter both if you have them. Obtain from their IT department or internet provider. Dialer set up. Even though we are not dialing with a modem PG uses a dialer to send all messages. Serial Port in this case is for an external dedicated modem. Just make sure you have Dialer 1 running (See step 4). Carrier creation. Here we create the cell phone/pager provider that our customer will be using to receive messages and pages. In my customers case it was T-Mobile. To do this, right click on carrier and select Add. Select the drop down box under protocol and select SMTP or the appropriate protocol you need. TAP, GSM, SNPP, etc. Recipient creation. Here we enter the contact data for the individual’s cell phone, pager, fax number, e-mail address, etc. Fill in name of recipient and check the box for enabled service. It is possible to send messages to multiple devices such as an e-mail and text message at the same time. Just check the service you are using but remember you need a dialer for each service. Refer to cell phone provider for e-mail address format. For T-Mobile it was phone number@tmomail.net. Also check the box for Alpha and Drop non-printable characters. Group creation. You can create a Group and PG will send messages to every recipient in that group for the appropriate enabled service. Right click on group and select add. Check box to enable appropriate service. Select recipients you want to add and move them across into your new group. Select apply and PG will now send messages to all recipients in that group. This write up is intended to be a general guide in setting up PageGate for your customer. Most likely your customer’s setting will differ from the settings in this write up. To download the software here is the link to the website: http://www.notepage.net/ Once you get the trial software working you have about 10 days to pay for it because the trial version will shut the scheduler down every so often until you pay for the software. Good luck!

Issue The modbus RTU communication from the ICP 7188 and the Caterpillar SCM module stops communicating after the genset hand off auto switch has been placed not in auto. Environment ICP 7188 Modbus RTU Caterpillar SCM Module Cause When the Caterpillar genset hand of auto switch is placed not in auto for monthly genset tests or to manually run the generator the SCM module on the generator senses this state change and sends a "wait" command on the modbus network that the ICP 7188's modbus driver can not handle. Resolution There are two resolutions to this problem depending on what version of the modbus driver running in the ICP 7188. If the modbus driver dated 2-16-2001 is being used in the ICP, the only resolution will be to power cycle the ICP after the genset has been placed in "not in auto". This will re-initiate the communication on the modbus network. This modbus driver version does not have the capabilities to handle the 'wait" message from the SCM module. Upgrade to the final modbus build for the ICP 7188 dated 3-4-2005. This driver has the ability to receive the "wait" command from the SCM module on the modbus network. To upgrade the ICP 7188 to the final modbus build, simply place the ICP7040.exe, SP7040.def, and SP7040.exe files from the attached.zip file in the linkterm directory, and redownload the ICP.   NOTE: The ICP7188 is no longer officially supported by Schneider Electric as the gateway device for I/Net integration efforts. The Xenta 913 is the official replacement for the ICP 7188 when doing third party integration to an I/Net system.

Issue IAS stands for Intrusion Alarm System. If stopped in "Initializing" then follow these steps. Normally if using the bin file from I/NET version 2.21, the display will show correctly. The bin file for version 2.30 and above may have to complete the step to get past the initializing screen. Intrusion Alarm System (IAS) also referred to as the OP5 or Remote Arming Terminal RAT Environment I/NET Seven with a 7798C and Intrusion Alarm System I/NET version 2.21 and above. I/NET version 2.16 and bellow do not support the OP5 Terminal. Cause Configuration Settings and database download. Normally if using the bin file from I/NET version 2.21, the display will show correctly. The bin file for version 2.30 and above may have to complete the step to get past the initializing screen. Resolution After a software download from I/NET Seven 2.30 to current, the OP5 is always in Initializing Mode.  Hot to correct this? In the MCU Configuration Editor, the type has to be DPU The device has to be saved in Network Configuration If these two are true, it will pass the initialization part of initializing mode. Here are the steps in order to get the OP5 terminal to setup at my desk:  Set the OP5 as link 29 Backup the existing database. If DCU password is requested, it is 4444 Backup existing database. Copy the Database from CD\support\IAS Templates\8_Zones to local hard drive Copy the SAV file from CD\support\IAS Templates\8_Zones to local hard drive in the Sav folder of I/Net. Be sure to rename DCUxxxx.sav Restore database you just copied from CD Go into Network Configuration and delete link 94 Go into Network Configuration and save the link penetrating down all levels Do a station restore from the SAV file you copied to the 7798 and renamed from CD. I recommend SLI then DPU, in that order. Go into Edit, Controller, MCU Configuration and make OP5 29 link DPU Go to Edit -  Controller - Intrusion Alarm System Add point OP5 - 2 (This one is configured to link 29), Choose one or all if so desired. Click OK twice. The led light in the upper left corner on the OP5 will be lit now. Make a station restore and the OP5 keypad appears. Go into pull down menu for Access Add Door to Tenant Add Door Schedule for all three groups Go into MCU Config and check OP5 is on Link 29, and set for DPU If OP5 is still ‘Initializing’ then change MCU Config Link 29 to Internal, exit Go into MCU Config and change Link 29 to DPU My OP5 works using I/Net 2.40, Xenta 527, 7798C, OP5. I have the OP5 link as 29. Please alter the instructions to fit your link number. Step 6 refers to the link 94, which is part of the database here, you can delete since it is not relevant to your location. Here is a pdf with an example of the setup of a typical OP5. Another paper written on the steps they performed using the OP5 is found Here.

Issue Review of Windows event log, product event logs, or error windows during operation provides an error code number that is unreadable. Environment Microsoft Windows Cause Microsoft uses a standard list of error codes which programs can access. The display of these errors is typically in a decimal or hexadecimal format. Resolution Use the Windows Error Codes spreadsheet which allows the user to enter the code as either Hexadecimal or Decimal format and provide the text description for the error code. Use the error code description to further diagnose the problems being experienced. Guidance on whether a code is Hexadecimal or Decimal: 0x00000001 - Hexadecimal -214000000 - Decimal

Issue I/NET uses a different "large number" hexadecimal format to represent individual cards.  To convert to a Continuum system, these must be decoded into Facility Codes and Card Numbers. Product Line Andover Continuum, TAC INET Environment I/NET Seven Security converted to Continuum Cause Different representations of individuals in the two systems. Resolution Download the "ZIP" file here conversion Excel spreadsheet. Press the "Clear Values" button to zero out the inputs. Select the correct format between the four options: 26-Bit Wiegand 32-Bit Wiegand Format (CSI) 35-Bit Wiegand Format 37-Bit Wiegand Format Enter the hexadecimal value and the Facility Code and Card Number will populate automatically.

Issue Is a Vista license necessary for I/NET Host tool features or is the I/NET CD key sufficient? What is the difference in the I/NET Integrated and I/NET Security licenses? Environment Vista Server I/NET Host Tool Cause The I/NET Host tool requires a Vista license file to run. Certain editors and features in the I/NET Host Tool are common to both the Integrated and Security license. Some features are specific to the Integrated or Security license. To have all of the features purchase of both licenses is necessary. AMT is not included with the I/NET host tool product as Vista is expected to handle alarms messages and transactions Common Features System features Change password Connect/Disconnect Logon/Logoff Quit Work offline Host features Host configuration editor Host password editor Host phone numbers editor Host software restore editor Netcon function editor Network configuration editor System view Tap features Host, link, and site tap configuration Site tap remote configuration Site tap save/restore Controller features 7720 configuration editor Action messages summary Alarm extension editor Calculation editor Control description editor Conversion coefficient editor DCU configuration editor DCU save editor DCU restore editor DCU password editor DPU configuration editor Engineering units editor Event extension editor Event sequences summary I1/I2 state parameters editor Lighting circuits editor Lighting zones editor LCD page definition editor Lookup table editor MCU configuration editor MR configuration editor Resident point editor Special days editor State descriptions editor Time schedule extension editor Trend extension editor Trend plot view dialog Summaries Configuration summary Controller summary Disabled points summary Off-normal points summary Reporting features SevenReports (operates in view-only mode if no I/NET CD key is installed) I/NET Integrated only Controller features Consumption extension editor DDC modules summary Demand control extension editor MR DDC summary Override billing equipment mapping editor Override billing extension editor Override billing parameter editor Runtime extension editor Temperature control extension editor Unitary control configuration editor Unitary control extension editor I/NET Security only Controller access features Elevator extension editor DCU AIC editor Door extension editor Personnel schedules SCU parameters editor Host access features Access control options editor Access control wizard AIC editor Door extension editor Groups editor Individuals editor Key translation editor Personnel schedules Pin generation dialog Recycle bin SCU editor Tenant editor User search Summaries Door tenant summary Resolution Purchase of an I/NET Host Tool license is necessary for the integration with Vista Workstation to function. Use the feature list to determine if only one license or both licenses are required by the customer. Attached is the PA for all the required software Here

Issue How to install and use I/NET with SQL located on a separate PC Environment I/NET 2.40 and above Full SQL Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause The SQL database may be located on a separate server for IT, security, or backup requirements. Resolution Please see attached "RemoteServerandRCwithIO" Install full SQL on a PC and take a note of the IP address. Make sure the following criteria are met: The server must be on the Ethernet. Provide SQL services. Allow authorized clients to connect, and have an I/NET database. Setup I/NET on the Host PC as a Remote client and redirect it to the PC with SQL installed, IO server must be running on 1 of the remote clients (This Client will be in charge of updating AMT, Trends, Network Functions)

Issue Displayed temperature on the ETR is offset from the actual temperature reading of the controller. Environment ETR Thermostat Cause Factory calibration is offset from actual temperature. Resolution Click here to download the Installation and Operating Instructions Temperature Display Adjustments Temperature display may be adjusted by adjusting the ZERO or OFFSET Potentiometer (P2) as shown on the diagram.  Adjust P2 until the LCD Display reading, matches your controllers temperature reading if necessary. Note that all LCD Displays, are factory calibrated using an NIST Certified Glass Thermometer.

Issue Error Message pop up reading: Station Conflict - [Link: 95] Station 00 at site 61 - Xenta527 conflicts with site 63 - xenta737-97. Station Conflict - [Link: 1000] Station 00 at site 03 - Host 3 conflicts with site 90 - Host 9. Product Line TAC INET Environment I/NET Cause Station conflicts occur when multiple devices share the same address. This is always the cause, but Identifying the possible addresses can be confusing. Host Address - The I/NET Configuration unique identifier for each host workstation.  1-250 Link address - The system segment in question. Contains multiple Stations and in DLA multiple sites. 0-99 It is generally advised that you do not use Link 0. The Link will typically define an NPR or Xenta 527. Such as the Link 4 Xenta 527 functions as the bridge between TCP/IP and the Link 4 Controller LAN segment. Site Address - Only used in DLA architecture.(1-63) 0 is only used in non-DLA NPR devices. The site allows for multiple Controller LAN segments to use the same Link address. This changes the description of a Xenta 527-NPR from Link 6, to Link 6 Site 1 and allows Link 6 Site 2, Site 3 and so on. In DLA architecture, the NPR devices will typically all use the same Station Address.  If link 6 Site 1 uses Station 0, Link 6 Site 2 may also use Station 0. Station Address - This is the unique identifier for addresses on a physical controller LAN wire.  You may use 0-63, but one must be reserved for the NPR device. Station level controllers are typically referred to in messaging by a 4 digit address.  Link 4 station 12 may be shorted to 0412.  All controllers in an I/NET system must have a unique for digit label of LLSS. The only exception to this is the NPR device as it function as a gateway and can have a site address to make it unique.  Controller LAN level controller do not show a site label. Resolution Change the address on one of the offending controllers In DLA situations, you can only duplicate the Station address used by the Xenta 527 If a 913 is used on the Controller LAN, it must also have a unique station ID Ensure all Host workstations have unique host ID's Ensure all devices in a DLA architecture have unique Link/Station combinations.  There cannot be 2 Link 4 Station 3s, even if they both have a unique site number.

Issue Filtering Alarms in StruxureWare Building Operation to show only I/NET alarms Product Line EcoStruxure Building Operation, TAC INET Environment I/NET integrated to StruxureWare Building Operation version 1.9 and older Cause Users may wish to only view alarms from the I/NET system Resolution Filter for All I/NET Alarms: Create an alarm View Click on the Filter Object Add a condition to Filter by Type Select the Type 'INET Alarm Record' Click OK Filter for I/NET Alarms from a Specific Link Create an alarm View Click on the Filter Object Add a condition to Filter by Source Type */INET Interface/LL where LL is the link number of the desired link. Note: If the INET interface on your server is not the default name, the name must match yours exactly. Click OK

Issue The Windows power save is interrupting system operation, i.e if you have a graphic open on a Workstation which is talking to another PC and the mouse has been inactive for some time, when you move the mouse it takes some time to update the graphics Environment Windows ES Continuum Inet Vista SmartStruxure SmartStruxure Lite SBO Cause This is caused by the Windows OS going into a power save mode, this will normally close down the CPU, Network adapter, graphics card etc Resolution   PC is going into a power save mode, Go into, "Control panel", make sure view is "Small icons", then click "Power Options" in here you will have a number of option, set this to "High performance" then "change plan settings" make sure all are set to Never or high performance, when you have done this, goto "Network and Internet" then "Change adapter settings", right click on your network adapter and goto "properties" then click "Configure" then "Power Management" make sure that the power save settings are off, this will stop the network from going to sleep.   This will need to be done on the ES, Workstation PC, Continuum Workstation, SQL server, etc This should then stop you having the delay as the PC wakes up