Issue Printer Use with Emergin Software Emergin Software worked fine until I/NET 2000 was upgraded to I/NET Seven. Now the printer starts to print the Events and Alarms vertically instead of horizontally. Environment Emergin Software I/NET Seven upgraded from I/NET 2000 Cause Upgrade process requires that the COM port be added back again following the upgrade. Resolution Remove the COM Port from the Device Manager Reboot the PC so that it rediscovers it or re-adds it back again Restart I/NET Generate an Alarm and verify that it works correctly. If for some reason this does not work: Verify that you have the latest Emergin Build that is compatible with I/NET Seven, then try it again. You would have to go to the Emergin Website to get this information at www.emergin.com.

Issue I/NET to DVR interface communications port Environment TCP/IP Cause A firewall may prevent communication between a PC and the DVR Resolution Integral DVR communicates on port 18772.

Issue What is the proper way to enter data in ID Works and print a badge? Product Line OTHER, TAC INET Environment ID Works I/NET Seven Cause Enter data properly to avoid losing data or having to redo personnel entry. Resolution Log into the ID Works Program Default user name is lowercase admin Default password is lowercase 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. Typically, select the “Trusted Connection” option. This is a view of the Sample project that is on the I/NET Seven CD under the "Support" file folder on the CD. Next fill in all the information listed on the Production Form including taking the photo. Now that you have filled in all the info and took the picture, it is time to print the badge. On the Bottom ICON Task Bar, the second ICON in going from left to right is the "Print ICON." Before you actually print the badge, make sure the Blank cards that are in the printer magazine are the correct ones. Once you verify that the correct blanks are in the printer, and then depress the Printer ICON with the mouse. 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. Now that you still have the information in the Production Form on the Screen, DO NOT choose the RED X on the Top ICON Task Bar to clear the page. If by accident you do choose the RED X, you will get the following pop up window. DO NOT CHOOSE the YES BUTTON, if you do, you WILL DELETE ALL THE INFORMATION AND PHOTO you just entered in the I/NET Seven System and the ID Works system. If you find yourself in this situation, you NEED TO CHOOSE the NO BUTTON, doing this choice WILL NOT DESTROY ANY DATA. In order to refresh the project, go to the Top Task Bar and choose the "FILE" option. In the drop down list choose the "Close Project" option. Then select a new Project for the next badge, this process will open a new clean Production Form to fill out.

Issue Inovonics Wireless Interface problem Environment FA7403 Cause Inovonics provides an interface to access wireless temperature sensors. The FA7403 receiver can be used to interface with Xenta equipment or Continuum equipment, however these interfaces use different protocols. Resolution The Xenta equipment requires a hexadecimal protocol which corresponds to the FA7403 receiver. The Continuum equipment requires an ASCII protocol which corresponds to the FA7403-ASC receiver. If you have the wrong receiver for the equipment you are trying to interface with then contact the Product Support Group for steps to reconfigure this device.  

Issue How to program a BioScrypt V-Pass-2 (Biometric) Reader in I/NET Seven. Product Line Other, TAC INET Environment I/NET Seven BioScrypt V-PASS (MV1200) Cause Assistance with configuring the BioScrypt V-PASS reader with I/NET Seven Access Control. Resolution Biometric Reader Setup Using the Bioscrypt V-pass-2 Reader The reader is: Bioscrypt V-Pass FingerPrint Reader VPASS-2 Note: The Programming software to load fingerprints on the PC comes with the reader. For the actual wiring and programming of this reader see the linked "BioScryptSetup.PDF" BioScript Setup Wiring (pigtail) Wiegand 1 - Wiegand Out Data 0 3 - Wiegand Out Data 1 6 - Wiegand GND Power using separate 24V DC Power Supply 11 - Pwr GND 13 - Pwr IN 15 - Earth Ground BioScrypt V-Pass Reader Wiegand Setup Install BioScrypt Software (VeriAdmin) on PC and setup to communicate with reader. Go to Configure > Unit Parameters Click on Wiegand Tab Check Predefined Format Pick "Standard 26 bit" Under On Success Check Alt Site Code & Enter Arbitrary Value (usually 3 digits) RECORD VALUE this is the Site Code Under Wiegand I/O Check Enable Input Check Enable Output Select Always Output (regardless of Input Source) Enroll Individual in VeriAdmin Enroll Individual RECORD ID – this is Individual Number NOTES: The index number is to assigned to ID number to record each individual finger (0-9 is for all 10 fingerprints). I/NET will only be sent the ID number in the Wiegand String. Schedule does not matter. You have selected Always Output (regardless of Input Source). One will do all the door scheduling in I/NET. Enroll Individual in I/NET Create new Tenant called “BioReaders” If site is using Wiegand Card and NOT Large Numbers (Dipswitch 7 OFF) Enter Site Code (recorded from above) as the Tenant ID When enrolling the individual in the new tenant, use the ID recorded from above as the Individual Number and Decimal Card Number.   If site is using Wiegand Cards and Large Numbers (Dipswitch 7 ON) or if using Idiscs (set Dipswitch 7 ON for only DPUs with BioScrypt, even if they have Idisc also) Leave default Tenant Code. Use 26BHEXCAL.xls and enter Site Code and Individual ID recorded from above and it will generate the HEX Card Number. When enrolling the individual, enter the Hex Card Number as generated. I/NET Door Configuration Make sure door is setup as Wiegand 26 Configuration as Implemented DPU 7920 Door 08 was setup as BioScrypt V-Pass MV1200 Door 09 was setup for Idisc Door Lock was wired to both relays in series (so both had to be energized to unlock the door). Door 08 (BioScrypt) was given a schedule of 24/7 and assigned to all individuals in new tenant. Door 09 (Idisc) had the original schedule assigned to site personnel. This schedule is the one that will deny access according to schedule. Other Configurations This can be used as a single reader for the door (with schedules in I/NET) or as implemented above with any combination of reader compatible with I/NET.

Issue Every time the computer reboots, LMGRD errors are shown at startup.   LMGRD encountered a problem and needed to close. lmgrd.exe - Application Error The instruction at "0x0012e854" referenced memory at "0xffffff91". The memory could not be "written". Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista Server 5.0 FlexNet Licensing Remote Alarm Manager Sigma BAS2800+ Micronet Errors Cause There is a known issue with the new license server from Flexnet. The LMGRD.exe is actually crashing during shut down of the PC. Resolution This is nothing dangerous. What happens is that when you turn off the PC, something is happening with the license server during the shutdown phase. Since LMGRD runs as service, it can not display this error message during this shut down. The error message is shown the next time the PC is started. It will not affect anything since the error messages is queued from the last shutdown sequence, NOT during the startup. We think it has something to do with having a license server installed and not using only an entitlement license. In some situations, placing a customer license file from any project into the license folder along with the monthly demo license stops the LMGRD error. The license server may read the customer license, note that it is invalid, then use the monthly license. Flexnet is looking into this issue. Look for a fix in upcoming versions. On Sigma, BAS2800+, and Micronet systems where Remote Alarm Manager is installed, the TAC license server can be uninstalled as it is not used.

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter Will not work with a Dell E6400 laptop Environment PCMCIA slot Cause Dell E6400 Chipset Resolution Go to the Dell website and upgrade your laptops chipset to the latest version from the dell drivers and downloads section. The file download is a self extracting file, follow the instruction provided and when you re-boot your computer your LonTalk PCC-1 PCMCIA Network Adapter should be fully functional. For further information see TPA-SACH-10-0008.00 - LON PCC-10 PCMCIA Card with Dell E6400 Laptop

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

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

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

Issue Error when running the Checklic license utility: "InitCrypkey Error -103: NETWORK: REPLY FROM NETWORK DRIVER IS BAD" "InitCrypkey Error -102: NETWORK: NETWORK DRIVER APPEARS TO NOT BE SERVING THIS DIRECTORY" Product Line Other, TAC Vista Environment LNS 3.0 LNS Turbo Edition (Ver 3.2) LonMaker 3.0 LonMaker 3.1 LonMaker Turbo (Ver 3.2) Vista Cause A problem has occurred with the LonMaker licensing. Resolution There are two procedures for fixing this problem. Try Procedure 1 first, and if the license still has the same problem, try Procedure 2. Internet access may be required for Procedure 2 to in order to download the setupex.exe and cks.exe programs and request a replacement license. Procedure 1: Confirm that the Windows Crypkey License service is started. To confirm, click Start > Control Panel > Administrative Tools > Services. Verify the Crypkey License status is Started. Also verify that the startup type is Automatic. If not, right-click the name and then click Start. Double-click the name to enter the properties dialog and change the startup type to Automatic. Close the Service window.   Confirm the Crypkey NetworkX driver is started by running C:\Program Files\Common Files\Microsoft Shared\MSInfo\Msinfo32.exe. Expand System Summary > Software Environment > System Drivers in the category tree in the left pane, then locate NetworkX in the right pane. Confirm that the State is Running and the Status is OK. Close the System Information window. If you cannot find these software components, uninstall the Echelon Software product, reboot, and reinstall the product. Antivirus and Internet security software can interfere with the proper installation of the software. Disable such software before you re-install the Echelon software product. At this point, if you are still unable to run your LonMaker or LNS application because of a License Access error message and if the Checklic license utility still reports a -102 or -103 error, follow the steps in Procedure 2. Procedure 2: Check to see if two files exist in the C:\Windows\LNS Licenses folder. setupex.exe cks.exe The LNS Licenses folder is hidden; if you do not see it, open the Windows Explorer Tools menu, click Folder Options, and in the View tab, select Show Hidden Files and Folders and clear Hide Protected Operating System Files (Recommended). If you don't see these files, download them from Echelon and extract them to the C:\Windows\LNS Licenses folder. Open a Windows command prompt by clicking Start > Run and typing in cmd (or command for Windows 98). Type the following command to change your working directory: cd "\Windows\LNS Licenses" Type the following command: setupex /U Reboot the computer. Repeat steps 3 and 4, and then type the following command: setupex Reboot the computer. Open a Windows command prompt and enter "checklic lonmaker.vsl" for the LonMaker Tool or "checklic nsseng.exe" for other LNS tools and applications. If no errors appear, then the LNS application should start. Exit now. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening/creating network. If the -4/-1 error remains, use the license wizard to request replacement credits. If the InitCrypkey Error -102/-103 error is shown, delete the following files under C:\Windows\LNS Licenses (do not delete other files from the LNS Licenses folder): For the LonMaker tool: LonMaker.rst LonMaker.ent LonMaker.key LonMaker.41s For an LNS tool or application other than the LonMaker tool: nsseng.rst nsseng.ent nsseng.key nsseng.41s Delete esnecil.ind in the C:\windows\system32 folder. Reboot the computer. Run the Checklic license utility again. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening or creating a network. If the -4/-1 error remains, use the license wizard to request replacement credits. Once the license is fixed, download and install the LNS Licensing Update 2006.

Issue The device is applicationless, or is not associated with a program record. (Subsystem:  NS, #5) The target device does not have a valid application loaded. To correct this problem, right-click on the device and select the "Load" option. Then, if necessary, repeat this operation. The device was discovered to be applicationless, or not associated with a program. If you encounter this error, load the application into the device. For host-based nodes, ensure that the host application is running Product Line Other, TAC Vista Environment LNS LonMaker Vista NL220 Cause Interrupting a download can cause the download to fail and render the controller applicationless.  Also, a corrupt Menta file can sometimes successfully download, but cause the controller to go into an applicationless state. Resolution An application must be downloaded through Menta while directly connected to the controller through the RS-232 serial port.  A blank Menta file with just one PVR is sufficient to restore an application to the controller and allow it to be downloaded; however, downloading the actual Menta file is better because it can expose parsing errors in the Menta file that need to be fixed before downloading it through the System Plug-in again. In some cases, an attempt to direct download can not establish communications to the controller and "timeout". In this event, download a new .mot file to the system using the Download Wizard. Instructions are located in Instructions on how to download an .MOT file into a Xenta Programmable controller. If the Download Wizard  is not able to establish communications with the device, the program should first be cleared using a Xenta Hardware Reset Tool. You can make one by following the instructions located in Xenta Controller Will Not Download / How to Clear the Xenta Application. If the Xenta firmware is older than 3.61, the method to clear the Xenta application is to power cycle the controller 10 consecutive times.

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 Is one access vendors card with Wiegand 26 bit output the same as another vendors Wiegand 26 bit output? Environment Continuum 1.xx Access Control Cause Replacing access card reader. Resolution When replacing access readers follow the manufacturer’s installation instructions for that particular reader. Wiegand 26 bit output type is a standard so that output will be the same.

Issue Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes to the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   To use these files in XBuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template.  

Issue Temperature inputs not reading the correct values Environment Cyberstation IOUs Controller Cause Bad input Bad controller Bad sensor Resolution Replace sensor with a 10k ohm resistor.  Temperature input should read roughly 77°F or 25°C.  If it does then the problem is with the sensor.  If it does not then the problem is either with the input board or that particular input itself.

Issue Cannot communicate to third party devices using the MODBus TCP XDriver or MODBus RTU XDriver. Environment CyberStation ACX5740 XDriver MODBus TCP Cause The MODBus TCP configuration point was not created Resolution Create the MODbus TCP configuration point following the guidelines in section 5.1.3 of the MODBus TCP guide

Issue Continuum Add-On Software products and support contacts Environment Continuum Continuum Reports Suite Continuum Archiver/Archivers Continuum Elevator Control Continuum Bioscrypt Integration Video Monitor For Third Party Video Systems Continuum Guard Tour Center of Excellence (COE) Cause Continuum Add-On Software products and support contacts information. Resolution Please forward Continuum Add-on Software support requests to COE.Support@buildings.schneider-electric.com The Reports Suite software can be downloaded here: https://ecobuilding.schneider-electric.com/search?documentUUID=e040ce9b-7114-4cbc-b9cc-bcde73a6d64e&title=Continuum%20Reports%20for%20CyberStation%20v1.81%20and%20v1.82%20Add-on%20Software Internal note: In bFO the Care Team to which PSS will De-Escalate case is the NAM_BLD_COE_ADV Care Team.

Issue Bacnet 3rd party controller will not respond to Find New Bacnet Devices (Who-Is/I-Am), so will not come online to Continuum Environment Bacnet MSTP Continuum Cause Some 3rd party bacnet devices can be setup as master or slave. If the bacnet 3rd party bacnet device is setup as a slave device, it will not respond to the mstp token, therefore will not respond to the Who-Is broadcast and will not be able to communicate on the mstp network. The BACnet MS/TP protocol does not allow a slave only device to respond to a "Who-Is" broadcast. Resolution Check 3rd party device documentation or contact 3rd party device vendor for Master/Slave settings and configure for Master to communicate on a MSTP network. Slave only devices cannot come online and will require a 3rd party interface to convert to a protocol that can be directly supported by Continuum.   Examples of BACnet MSTP Slaves that are known not to respond to a Continuum Who-Is request and so not come online are: - The Babel Buster 485XM from Control Solutions Inc is BTL listed as a BACnet Slave device , their PICs statement can be seen Here. - Wilo pumps Interface Modules: IF-Modul BACnet & IF-Modul Stratos BACnet, their PICs statement can be seen Here. Additional Note In SmartStruxure a "slave only" MSTP device can ba manually created. 

Issue What are the default passwords for a IAC Touchscreen Environment Satchnet IAC controllers Cause Access level Resolution Read only: -      1234 Read/Write: -   4321 Super User: -    1024 ACK Alarm: -  2513 It is worth noting that these passwords can be changed when programming. If you connect to the Touchscreen using VisiSat software you can identify the passwords under the properties of the Touchscreen.