Building Automation Knowledge Base

Issue Getting authentication failure when trying to set to password for "SystemReportsService" through "Building Operation WebReports Administrator" Environment Web Reports 1.6.0 RC and above Cause The Reports Agent can't check the password with the ES. This is dues to one of the three causes below: [1] The Enterprise Server path is not correct [2] The HTTP port entered for the reports agent is not correct [3] The ES is not started [4] The password entered is not correct [5] The reports agent is not started [6] The "Local System" account does not have high enough privileges to communicate out of the server Resolution [1] Enter the right ES server path e.g. using "SBO Reports Agent Config" [2] Enter the same port in HTTP in the ES Software Adminsitrator and the reports agent e.g. using "SBO Reports Agent Config" [3] Start the ES [4] Enter the correct password (you can change the defined password for the "SystemReportsService" through Workstation) Be sure to use the SystemReportsService account in the local domain of the ES [5] Start the reports agent [6] Change the report agent service to run under a local administrator account

Issue Selecting/De-selecting Image Verification in AMT Environment I/NET site Cause How does one Select/Deselect Image Verification in AMT? Resolution With the inception of Image verification in AMT, the following steps should be used for the Selection and De-Selection process: For Selection, Open AMT, Select the Edit button in the Task Bar. Select Image Verification, in this editor the user can choose what they want to be displayed on the screen when the image appears. Select the Actions button, select Auto-Image Verification and select the doors that are being used for this application. Click OK, once a user who has access to these doors reads their card, their image will appear on the screen. Following these steps can do the De-Selection process: With the Image on the screen, select the Actions Button. A Check mark will be displayed at the Auto-Image Verification. Uncheck the mark and the Image will disappear. Note: An image needs to be associated with each individual.

Issue The Mail Service in a Niagara R2 UNC station is configured correctly.  However, e-mails do not get sent to the SMTP server. Product Line TAC IA Series Environment Niagara R2 UNC station Cause The Niagara station needs to enable mail.smtp.auth in system.properties. Resolution In the station, the following lines need to be added to the system.properties file if authentication is required: mail.smtp.auth=true mail.useUTF=false Once these lines are added and the UNC is re-booted, the UNC will successfully send emails to the SMTP server.

Issue SigmaX PCID changes each time the PC is restarted, Juniper Networks Virtual Private Network (VPN) has recently been installed. Product Line Satchwell Sigma Environment Windows XP with Sigma, SigmaX and Juniper Networks VPN virtual network adapter Cause SigmaX uses the Media Access Controller (MAC) address of the first network adapter on the PC to generate the SigmaX PCID, when the VPN adapter from Juniper networks is installed it is placed by windows as the first adapter. If the ipconfig /all command is run from a command prompt it can be seen that new MAC address is assigned to the Juniper adapter each time the PC is started. A search of the Juniper Networks knowledgebase shows that it is normal behaviour and the MAC cannot be fixed Summary: Is there any way to have static MAC address for Network Connect virtual adapter? Problem or Goal: Assigning static MAC address for Network Connect virtual adapter. Solution: As of now, it is not possible to have a static MAC address for Network Connect virtual adapter. The virtual MAC for Network Connect virtual adapter will always start with 00:FF and the rest of the MAC is generated dynamically. The MAC address of the Network Connect client machine is randomly generated based on the algorithm whose result will change with system and time. Resolution SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. SigmaX uses the Media Access Controller (MAC) address of the first network adapter on the PC to generate the SigmaX PCID, when the VPN adapter from Juniper networks is installed it is placed by windows as the first adapter. Since there is no way of fixing the MAC address of the Juniper virtual network adapter the work around is to disable the adapter when SigmaX is used. There are two ways that this can be accomplished:- Disable the adapter from Windows Device Manager Note that the Juniper network Connect Virtual Adapter is a hidden device in Device Manager Right Click on My Computer and select Manage from the available options Select Device Manager from the management tree Once in Device manager select "Show Hidden Devices" from The View menu Expand the network adapters tree and right click the Juniper network Connect Virtual Adapter entry and select Disable After a short delay a red X will be shown across the icon for the adapter SigmaX will now use the next adapter to generate the PCID, note that the adapter will need to be Enabled in a similar fashion to above if a VPN connection is required at a later time. Disable the adapter via a script It is possible to disable/enable the Juniper Virtual adapter from a script, this requires that the Microsoft DevConutility be first downloaded to the PC Download the DevCon utility from http://support.microsoft.com/kb/311272 Extract DevCon.exe from the i386 folder of the zip file and place it in the root directory of the PC Create a new notepad file with the following text: cd\ devcon disable *DSNCADPT* end Save this file as DisableJuniper.bat Create a second new notepad file with the following text: cd\ devcon enable *DSNCADPT* end Save this file as EnableJuniper.bat Executing these files will control the adapter and once disabled SigmaX will now use the next adapter to generate the PCID

Issue Minimizing network traffic when sharing data between Continuum Infinity controllers Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Accessing a remote point’s attribute other than value is a point to point operation that generates extra traffic. Resolution Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller; this is in some ways similar to BACnet COV. When the value of a remote point is referenced in a PE program the system takes care of making sure the owner of the point sends the value to the subscriber(s) via the Import/Export system ONLY when the value changes. Consider the following PE program line… MyNum1 = RemoteCX\Num1 If a looping PE program sits on the line above no extra traffic is generated as the PE program gets the value of RemoteCX\Num1 from its local Import/Export table, information only goes on the wire when RemoteCX\Num1 changes value. The only problem here is that the Import/Export system ONLY works for the VALUE attribute, any other attribute requested from a remote object results in a point to point message on the network to obtain the requested attribute value. Consider the following PE program line in a CX controller we will call LocalCX NyNum1 = RemoteCX\Num1 size If a looping PE program sits on the line above a number of point to point messages would go on the wire every time the line executes. If there are many requests for attributes on remote objects a degrading in communications could take place. One way to avoid degrading communications as explained above is expose the value of the attribute in question by placing it in the value of a numeric object. Example: In RemoteCX create a numeric point (Num1Size) to hold the size of Num1 and use a PE program to set Num1Size Then the program in LocalCX will look like this… NyNum1 = RemoteCX\Num1Size Since the program is now going after the value attribute of Num1Size the import/export system will be used instead of point to point.

Issue Deleting a point from an MNB controller in StruxureWare Building Operation results in the following error Environment StruxureWare Building Operation: All versions up to and including 1.5.x I/A Series Micronet BACnet Controller Cause StruxureWare Building Operation does not support the deletion of points in the Application Folder of a MNB device.  Resolution To delete a point, disconnect the MNB controller from the network. Once StruxureWare Building Operation server is unable to communicate with the MNB device, it will allow the deletion of the point in the Application folder. Take note that even though the point has been deleted from the AS Application folder, the point still exist in the MNB controller.

Issue Trying to use OPRIF to make a few programming changes to a MicroSmart controller. OPRIF is installed on a SIGNAL computer (Windows 98). With SIGNAL disabled, OPRIF is able to start and handshake with the COM port. However the Auto Answer feature is enabled by default and begins an endless loop of trying to synchronize with the modem. The looping effect prevents a proper connection to the DMS to do programming changes. How can the Auto Answer be disabled on startup of OPRIF? Product Line TAC IA Series Environment OPRIF or Operator Interface version 11.4 and higher Cause Initialization file was modified by default Resolution The readme.txt file in the DMS folder explains how to prevent Auto Answer from being enabled on startup of OPRIF. Click here to view the entire readme file. Below is the excerpt on how to disable Auto Answer: Changes to the command strings used for modem-initialization and control The default modem init-string "AT C1 E1 V1 S0=1 S7=51" has been changed. It is now "AT&C1&D2E1V1". If you or your modem don't like this string, you can now override the default. Using NOTEPAD or EDIT, create a file called MODEM.INI in the DMS directory. This file should contain a single line of ASCII, which will be your customized initialization string. The line must begin with the letters "AT", and must not contain the letters "DT". Other than this one restriction, your modem-init string can contain whatever commands your modem requires. Two separate default strings have been defined for turning auto-answer ON and OFF. These may be overridden by creating files with the appropriate names in the DMS directory. To specify a customized string to force your modem to STOP auto-answering, use NOTEPAD or EDIT to create file a called ANSWEROF.INI in the DMS directory. By default, this file would contain the single ASCII line "ATS0=0". If your modem requires a disconnect command, you could instead write a line that reads "ATH ATS0=0". The default autoanswer ON string "ATS0=1", instructs the modem to answer on the first ring. To answer on the third ring, use NOTEPAD or EDIT to create a file called ANSWERON.INI in the DMS directory. It should contain the single ASCII line "ATS0=3". SUMMARY: Description Default String Filename Comment Modem Initialize AT&C1&D2E1V1 \DMS\MODEM.INI Modified in 11.4 Auto-answer On ATS0=1 \DMS\ANSWERON.INI New in 11.4 Auto-answer Off ATS0=0 \DMS\ANSWEROF.INI New in 11.4

Issue "No license for LonWorks communication" error when using a non LE dongle. Product Line TAC Vista Environment Non LE dongle (LE= Limited Edition which has no Webstation or multiserver functionality) Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause One would normally expect this error message when trying to run Webstation server with a Vista LE license. If the system is not using a Vista LE dongle/license, but the error "No license for LonWorks communication" appears, then the problem may be in the Privilege Server service.   Resolution Shut down Vista Server and Workstation. Right click on My Computer and select Manage. Expand Services and Applications. Click on Services. Find the service Privilege Win32 Server. Right click on the service and select Stop. Right click on the service once more and select Start. Restart Vista Server and Workstation and verify that the error went away. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Adding entries to the Web.config file during installation. Environment WebClient installation. Cause Unclear instructions in webClient Planning and Installations Guide. Resolution When modifying the Web.config file located in: C:\\Program files\Continuum\DNWACServerFactory Add the following lines before the close Configuration tag <system.webServer> <security> <requestFiltering allowDoubleEscaping=”True”/> </security> </system.webServer> </configuration>

Issue Alarm colors in Workstation Product Line EcoStruxure Building Operation Environment  Building Operation Workstation Cause The default color for active alarms is white font with a red background. Some customers may want this to be in a different color.  Resolution In Building Operation Workstation System tree, go to Alarm Control Panel > Alarm Styles.  From here, the font type, font color and background color of acknowledged, active, disabled, fault or reset alarm states can be changed.  Refer to: Styling the Alarm States in the Alarms Pane and Alarm Views   Also available from EcoStruxure Building Operation 1.9 and above is Alarm Decoration. This allows overriding an alarm configuration for a specific alarm or group of alarms and applying an alarm decoration rule.  An alarm decoration rule is similar to a filter and allows changing other properties in addition to the font type, font color and background color.

Issue How is a subnet defined? Environment Refer to "TCP/IP Network Administration" by Craig Hunt, O’Reilly & Associates, Inc. Cause Sectioning network communication by subnets. Resolution A subnet is defined by applying a bit mask (subnet mask) to the IP address. If a bit is on in the mask, that equivalent bit in the address is interpreted as a network bit. If a bit in the mask is off, the bit belongs to the host part of the address. The subnet is only known locally.

Issue Number of individuals that a controller can have based on the firmware revision. Adding individuals to a system that has more than 24,000 users and is not working. Product Line TAC INET Environment I/NET Seven DPU 7910 DPU 7920 with or without 48K MIP Card SCU1284 Cause Although TAC I/NET supports up to 32,000 individuals per tenant, the model type and revision date of a tenant’s door controllers will ultimately determine how many individuals will be supported Resolution I/NET Supports up to 32,000 individuals per tenant based on the model type and revision date of the tenant's door controllers determines how many individuals it will support. The following table shows the capacity of the various door controllers. Firmware Revision Door Controller Maximum Number of Individuals Maximum number per Tenant 2.1X and earlier DPU 7910, DPU 7920 Up to 24,000 per door 24,000 2.2X to 3.23 DPU 7910, DPU 7920 w/o 48K MIP Up to 48,000 per controller. 24,000 DPU 7920 with 48K MIP, SCU 1284 Up to 48,000 per door 1 3.24 and later DPU 7920 with 48K MIP, SCU 1284 Up to 64,000 per door 1 32,000 1 Typically, the total number of individuals for a selected door cannot exceed 32,000. However, if one of the two doors controlled by a DPU is not being used (that is, no individuals are assigned to the door), you can assign up to 64,000 individuals to the door that is being used. This also requires the use of more than one tenant since no single tenant can have more than 32,000 individuals.

Issue ES is connected to a remote server via EWS; when loading a graphic in a web browser or workstation, the values take a long time to read. (a few minutes.) It makes no difference what the settings for polling are configured for. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Every time the graphic is brought up, the ES needs to subscribe to all values from the external EWS server, this is the cause of the delay. Resolution Workaround Solution: Maintaining Active Subscriptions The recommended workaround solution involves maintaining active subscriptions. This can be achieved through the following methods: Persistent Graphic Display: Always keep the graphic displayed on a client. This is crucial as the subscriptions are terminated when the graphic object is closed. By keeping the graphic open, the subscriptions remain active. Watch View Creation: Create a watch view that includes the values displayed in the graphic. This ensures that the values are constantly monitored and updated. As long as a client subscribes to these values, the update process will be expedited when the graphic is launched. This is because the subscriptions remain active, and the values do not need to be re-initialized. However, if there are no active subscriptions to the values, all values must be set up each time the graphic is opened. This can potentially slow down the process. Therefore, maintaining active subscriptions is highly recommended for efficient operation.

Issue Workstation displays power in Btu/s when VA is required. Product Line EcoStruxure Building Operation Environment Workstation Cause The units displayed in Workstation are based on the Regional and Language Options settings in Windows Control Panel as talked about in Metric vs. English (Imperial) Operating System. Resolution The Unit Conversion Exception tool can be used as a solution for this issue. This is located in the Domain portion of Workstation's Control Panel. For more information on the Unit Conversion Exception see Unit Conversion Exceptions feature or the Online help located here. In the situation where VA has been set as the power unit but Btu/s is still displayed, the unit conversion shown below will resolve the issue. Note: If your desired value units have a prefix, then this needs to be done in the Unit Conversion Exception as well (kVA). Note: WebStation (as of v1.3 SP1) does not use the Windows OS setting because the AS does not currently have localization - it uses only the International System of Units (SI) - not the Imperial or US units.

Issue Configuring Special Day Schedules. Product Line TAC INET Environment I/NET Site with schedules Cause What are the steps to make sure the Special Days works correctly Resolution Special Days are handled a little differently in Access control. The steps to make sure the Special Days work correctly is discussed in the attached white paper, Special Days Setup I7.doc.

Issue Are multiple Enterprise Servers in same system/site supported with Building Operation?  Product Line  EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central  Cause Large sites or customers may request a multi-tiered configuration to support multiple Enterprise Servers. Resolution A three tier server support containing multiple Enterprise Servers are not supported until Building Operation 2.0 and above.  The top tier of this EcoStruxure BMS been the Enterprise Central.  Refer to the following online help topic for further information: EcoStruxure BMS Server Hierarchy   

Issue Does TreeTech version 3.1 & 3.2 support all block types in all types of GCMs and LCMs? Product Line TAC IA Series Environment TreeTech version 3.1 or 3.2 GCM-84xxx GCM-86xxx SIM-xxxxx LNC GIM-2100 LCM-8xxxx Cause Block types supported are not listed in the Tree-Tech Engineering Guide document, F-26640 Resolution The following table lists the sub-devices supported by TreeTech 3.1 or 3.2 for each Network 8000 device type. GCM (rev 4.x & 5.x) ASDGCM (rev 4.x & 5.x) GIM-2100 / SIM-GCM (All rev)  LCM (rev 4.x)  LCM (rev 4.x)  MICROZONE-II  LCM (rev. 5.x)  LCM (rev 5.x)  PEM    MICROZONE-II  LIM    PEM      LIM   The following table lists the block types supported by each device family.  GCM 4.X ASD-GCM 4.X GCM 5.X ASD-GCM 5.X GIM-2100 SIM-GCM LCM 4.X/5.X AI AIPLC ALARM AO AOPLC APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DIPLC DO DOPLC DPT EDL EMS ENTHL FLOW HILO HOLI LIMIT LOGIC LOOP MATH MOMEN MTR MZHP1 MZONE MZRT1 MZSAT MZST1 OSS POLL PULSE PWM RAMP RESET RLCM RNET SEQ SGCM SLECT SNET SYS TOTAL TREND TSTAT VVBOX WEEK   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LIM LIMIT LOGIC LOOP MATH MOMEN MTR OSS PEM1 POLL PWM RAMP RESET RLCM RNET SEQ SGCM SGRP SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WEEK ZONE2   AI AIPLC ALARM AO AOPLC APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DIPLC DO DOPLC DPT EDL EMS ENTHL FLOW HILO HOLI LABEL LIMIT LOGIC LOOP MATH MOMEN MTR MZHP1 MZONE MZRT1 MZSAT MZST1 NIM NSCHD OSS POLL PULSE PWM RAMP RESET RLCM RNET SEQ SGCM SLECT SNET SYS TOTAL TREND TSTAT VVBOX WEEK   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LABEL LIM LIMIT LOGIC LOOP MATH MN MNFLO MOMEN MTR NIM NSCHD OSS PEM1 POLL PWM RAMP RESET RLCM RNET SEQ SGCM SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WEEK Z2HSC Z2SCH ZONE2   ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LIM LIMIT LOGIC LOOP MATH MOMEN MTR OSS PEM1 POLL PWM RAMP RAV21 RDS21 RDV21 RESET RNET SEQ SGRP2 SLECT SNET SYS TOTAL TREND TSTAT WAV21 WDV21 WEEK ZONE2   ALARM AO APT BTUH CALEN CNTR1 CNTR2 COS CURVE DAILY DCC DEGDA DELAY DO DPT EDL EMS ENTHL FLO2 FLOW HILO HOLI LABEL LIM LIMIT LLLB1 LOGIC LOOP LWC1 MATH MN MNFLO MOMEN MTR NIM NSCHD OPM1 OSS PEM1 POLL PWM RAMP RECP1 RESET RMA1 RNET ROOF1 SEQ SGRP2 SIM SLECT SNET SYS TOTAL TREND TSTAT UNTV1 WEEK WMA1 WSHP1 Z2HSC Z2SCH ZONE2 AI ALARM AO APT BTUH CALEN COS CURVE DAILY DCC DEGDA DELAY DI DO DPT EDL EMS ENTHL FLOW HILO HOLI LABEL LIMIT LOGIC LOOP MATH MOMEN MTR NSCHD OSS POLL PULSE PWM RAMP RESET RGCM SEQ SLCM SLECT SYS TOTAL TREND TSTAT WEEK   NOTE 1: Refer to the table at the beginning of chapter 4 of the GCM/LCM Programmer's Manual, F-23120, for more information on what object types are supported in specific versions or types of controllers. NOTE 2: The block types listed for the "GIM-2100 / SIM-GCM:" encompass the blocks supported by all the devices of the group.  You will be able to create any block type listed however, an error will be displayed when you attempt to download an unsupported block type into a specific controller in the GIM-2100 / SIM-GCM family.  Please refer to the controller manual (LNC, SIM-York, SIM-Trane, SIM-CCN, SIM-MTech or GIM-2100) for information on the block types supported by that controller type. The following ASD device blocks are supported by TreeTech. MICROZONE II PEM LIM AO DO EMS HOLI LOOP OSS RESET RGRP SCHED SEQ UI UTIL WINDO AO AS AT AV DI DO EMS LOOP RESET RGRP SEQ UTIL WINDO EMSA EMSD HOLI OVI RGRP RO SCHED UTIL WINDA WINDD  

Issue After an OGC graphic is upgraded to TGML, some images or components are no longer in the desired location on the page. Some images may shift location on the page depending on how TGML performs certain tasks during the conversion. Product Line TAC Vista Environment TGML Graphics Editor OGC Graphics Editor Vista Cause When an OGC graphic is converted to TGML, it is possible for the position of an image to be converted incorrectly. The x,y axis of an image in OGC is relative to the origin on the page (The uppermost top, left corner on the page being 0,0). However, if you have used the Symbols feature in OGC, TGML may group this symbol as a during the conversion. This places the 0,0 axis position at the uppermost top, left corner of the component and not the page. This creates unwanted separation as the x.y position relative to the component moves the image to an undesired location on the graphics page. Resolution Open the new TGML file in the graphics editor Locate the component that has been moved in the object tree Change the top and left position to 0,0 on all s associated with that component. TGML may have created several groups for one OGC symbol and the image under each group will need to change. NOTE: It may be possible to use the find/replace function in the source code to replace all of the unwanted positions at once. You will need to be careful that this number is not being used anywhere else in your code before you save these changes. You may remove necessary code if this number has multiple functions.

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 Customers at times need to be able to batch print badges Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause There's a need to know how the EpiBuilder, EpiSuite and GuardDraw batch mechanism works to utilize the batch printing feature Resolution To Batch print: Open a personnel object and select Make/Edit badge and then from within the Make/Edit badge window select File>Batch Print Cards You cannot select specific cardholder numbers to batch print like 101-110, you have to start with 1 and select a range from there. 1-10 which will print 10 card holder records that are marked as not printed by EpiSuite. EpiSuite indexes its cards for batch printing.  The Index number that Episuite uses does not match our card number.  As an example say you have 10 cards with card numbers 1-10 and you send cards 1-5 as a batch to the printer.  When you want to print the next 5 cards, Episuite does not see them as cards 6-10 but as cards 1-5 again.  This is due to EpiSuite own indexing scheme. If a card has already been marked as printed it won’t show up in the batch.  The order is determined by the index in the database.  Most likely the order in which the cards were created. To print a card again: Bring up the cardholder in Make/Edit badge> Tools> Set Card Unprinted ImageWare solution: Imageware offers a product called Guard Card/GuardTool as an add-on module. It can use the Microsoft Access for EPI Database by importing the data from the ContinuumDB. The personnel requiring updated badges are in this db and then this tool can be used to setup a batch print specifying a template. EPI software would then match personnel to one of the 4 templates and batch print them.  Note: Product Support has not used Guard Card/Guard Tool and does not support it. Contact ImageWare with any questions http://www.iwsinc.com/