Issue Does Port Based Network Access Control Ethernet 802.1x apply to Continuum controllers? Product Line Andover Continuum Environment Continuum Ethernet Controllers Cyberstation Cause A question that may be asked by Customers IT Departments Resolution No, the 802.1x protocol is not applicable to controllers, it is a Port based Network Access Control (PBNAC) that is used by Routers and computers. It is related to the Operating system user accounts and policies so is above and outside the scope of Continuum. Not all devices support 802.1X authentication. Examples include some network printers, Ethernet-based electronics like environmental sensors, cameras, and wireless phones. For those devices to be used in a protected network environment, alternative mechanisms must be provided to authenticate them. One option would be to disable 802.1X on that port, but that leaves that port unprotected and open for abuse. Another, slightly more reliable option is to use the MAB option. When MAB is configured on a port, that port will first try to check if the connected device is 802.1X compliant, and if no reaction is received from the connected device, it will try to authenticate with the AAA server using the connected device's MAC address as username and password. The network administrator then must make provisions on the RADIUS server to authenticate those MAC-addresses, either by adding them as regular users, or implementing additional logic to resolve them in a network inventory database. Many managed Ethernet switches offer options for this. Network Security is an available option add on for IP level controllers. Please refer to IPSEC and Network Security on Controllers for more information. Another potential option would be to secure the controllers on a separate VLAN.

Issue Performing a firmware upgrade on a reader expander module via the SP-C's web page will fail with the message: "Error - The module failed to restart in boot mode" Firmware update failure Product Line EcoStruxure Security Expert Environment SP-C, SP-RDM2, SP-MRDM2. Cause Cause 1 There was an intermittent communications fault hindering the update process. Cause 2 There are Smart Card Readers connected to the reader expander module, which are set to RS485 communication. This appears to be causing RS485 communication issues between the SP-C and the reader expander which is hindering the firmware upgrade process. Resolution For Cause 1 Run the module upgrade process again. For Cause 2 Physically remove all connected RS485 Smart Card Readers from the reader expander module being upgraded. Run the module upgrade process again. Once the reader expander firmware has been successfully upgraded, reconnect all Readers.

Issue Analog consumer values referencing the temperature of a SmartX Sensor shows in metric units when setup to display imperial units. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Building Operation Multi-Purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller Building Operation IP-IO Building Operation SmartX Sensor Cause SmartX Sensor is configured in the device as metric measurements (SI System). Setting Fahrenheit in Display of SmartX Sensor does not convert the values from metric to imperial. Consumer values are configured to use the object being referenced and do not convert measurements. Unit conversion is done within the binding and not the device itself. Resolution There are two workarounds: Option 1: Create an analog value and then bind to consumer value Step 1: Create an Analog Value. Setup unit settings to (°F) and Save.  Step 2: Bind Analog Value to temperature from SmartX Sensor and Save Step 3: In the created Consumer Value, bind the Analog Value to the input binding reference and setup unit settings to (°F) and Save   Option 2: Bind to Consumer Value directly and keep the value in metric Step 1: In the created Consumer Value, bind the SmartX Sensor temperature to the input binding reference Step 2: Setup unit settings as configured in the object (°C) and Save.

Issue Need to know Electromagnetic Compatibility for Power Supply PS-24V Environment AS PS-24v Cause Electromagnetic Compatibility Resolution Please have a look at the attached document for Electromagnetic Compatibility test report  --Report--

Issue Utilize the RS-232 port to send text out to a third party device such as CCTV Product Line TAC INET Environment I/NET Seven Cause Integration Assistance Resolution This V-Doc describes the way text output can be set up in I/NET to be sent out to third party hardware such as CCTV through the RS-232 port. The port that will be used for this application cannot be one that is already being used by the serial port section, A/C reader port, or printer port in the peripheral section of the configuration profile.   For the guide of integration with Pelco analog matrix, refer to How to integrate I/NET with Pelco Analog Matrix.

Issue Global and indirect points are very useful and are usually a mandatory part of most application programs. It is seen that in the event of a LAN failure or any failure of the indirect point being updated, the indirect point will be flagged as "Old Data." When this occurs any process using the indirect point as a variable, say, calculation extension, event extension will freeze at the last status/value before the old data on the indirect point was detected. Even though other parameters are still valid, the calculation and the event extensions will remain frozen, and some occasion remain in this state even when the old data is cleared from the source. Any subsequent process that uses the calculation or event definition will also be frozen. Any PID DDC Modules, Floating DDC Modules and 2 Position DDC Modules that uses the indirect point that has been flagged as "old data" will force those DDC modules to "Fail Safe" mode. Product Line TAC INET Environment ALL I/NET Software and controller LAN (CLAN) based controllers Cause LAN failure or any failure of the indirect point being updated. Resolution There are various tools available within I/NET to filter "old data" from subsequent control processes.  These include: Filtering by Calculation AVG operator function (including point types AI, DI and DO) Filtering by Direct Digital Control (DDC) Modules using either the Relay or HiLo modules Click Here to download a document which details these methods. For further details and recommendations when using Global and Indirect points, refer to the following I/NET Global and Indirect Points Overview and Recommendations.

Issue When reloading a controller or deleting objects from Continuum, an error "Distribution Server MFC application stopped" appears. It looks like an MFC compatibility issue, but is not. After creating a new database and logging on to Continuum, the problem does not exist. Environment Continuum 1.94 Windows 7 Cause Some database issue may cause the distribution server MFC application to crash. This is only one issue encountered. There may be other unknown reasons that could cause this problem also. Resolution Export the original database to a dump file Create a  new database and make Continuum work. Create a network in the new system and give the same name as the original database to the network Import the dump file into the new system, and reload all the controller in the system.

Issue Satchwell AR Series 1 or AR Series 2 Rotary Actuator requires replacement Environment Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Satchwell ARE ARM & ARX Series 1 and Series 2 Rotary Actuators Cause Obsolescence of Satchwell AR Series 1 or AR Series 2 Rotary Actuators Resolution Replace Satchwell AR Series 1 or AR Series 2 Rotary Actuators with appropriate S-E MD Series Rotary Actuators and wire as follows: Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies ARE ARE Series 1 & 2 Wire Colour BLUE  =  MD10A-24 or MD20A-24 Wire Number 2 ARE Series 1 & 2 Wire Colour RED  =  MD10A-24 or MD20A-24  Wire Number 3 ARE Series 1 & 2 Wire Colour BLACK  =  MD10A-24 or MD20A-24  Wire Number 1 ARE Series 2        Wire Colour WHITE  =  MD10A-24 or MD20A-24  Wire Number 5  ARX ARX Series 1 & 2 Wire Colour RED  =  MD10B-24 or MD20B-24 Wire Number 3 ARX Series 1 & 2 Wire Colour BLUE  =  MD10B-24 or MD20B-24  Wire Number 2 ARX Series 1 & 2 Wire Colour BLACK =  MD10B-24 or MD20B-24  Wire Number 1  ARM – UP TO MARCH 2006 ARM Series 1 & 2 Wire Colour RED  =  MD10B-230 or MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLUE  =  MD10B-230 or MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLACK  =  MD10B-23 or MD20B-230 Wire Number 1  ARM – SINCE MARCH 2006 ARM Series 1 & 2 Wire Colour BROWN  =  MD10B-230 or MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLACK  =  MD10B-230 or MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLUE  =  MD10B-230 or MD20B-230 Wire Number 1  Note: Should the Satchwell AR Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the S-E MD Actuator as follows: MD – S1  One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch  AR COMMON Wire Colour ORANGE  =  MD-S1 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S1 N/O contact Wire Number S3      AR N/C contact Wire Colour WHITE  =  MD-S1 N/C contact Wire Number S2  MD – S2  Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches  AR COMMON Wire Colour ORANGE  =  MD-S2 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S2 N/C contact Wire Number S2  AR COMMON Wire Colour BLACK  =  MD-S2 COMMON Wire Number S4 AR N/O contact Wire Colour RED  =  MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Colour BLUE  =  MD-S2 N/C contact Wire Number S5   Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE ARE Series 1 & 2 Wire Colour BLUE  =  MD20A-24 Wire Number 2 ARE Series 1 & 2 Wire Colour RED  =  MD20A-24 Wire Number 3 ARE Series 1 & 2 Wire Colour BLACK  =  MD20A-24 Wire Number 1 ARE Series 2        Wire Colour WHITE  =  MD20A-24 Wire Number 5  ARX ARX Series 1 & 2 Wire Colour RED  =  MD20B-24 Wire Number 3 ARX Series 1 & 2 Wire Colour BLUE  =  MD20B-24 Wire Number 2 ARX Series 1 & 2 Wire Colour BLACK =  MD20B-24 Wire Number 1  ARM – UP TO MARCH 2006 ARM Series 1 & 2 Wire Colour RED  =  MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLUE  =  MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLACK  =  MD20B-230 Wire Number 1  ARM – SINCE MARCH 2006 ARM Series 1 & 2 Wire Colour BROWN  =  MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLACK  =  MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLUE  =  MD20B-230 Wire Number 1  Note: Should the Satchwell AR Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the S-E MD Actuator as follows: MD – S1  One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch  AR COMMON Wire Colour ORANGE  =  MD-S1 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S1 N/C contact Wire Number S2  MD – S2  Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches  AR COMMON Wire Colour ORANGE  =  MD-S2 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S2 N/C contact Wire Number S2  AR COMMON Wire Colour BLACK  =  MD-S2 COMMON Wire Number S4 AR N/O contact Wire Colour RED  =  MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Colour BLUE  =  MD-S2 N/C contact Wire Number S5

Issue How is the mac address (ethernet id) of the Continuum master controllers calculated? Product Line Andover Continuum Environment bCX CX9200 CX9400 CX9900 CX9600 CX9702 CX9680 ACX5720 ACX5740 Cause Mac address must be unique. Resolution The controller mac address is assigned at the factory. The first three numbers (0:40:11) are fixed and represent the manufacturer, the next three numbers ar5e the unit's serial number converted to hex. Example: Manufacturer = 0:40:11 SN = 557746 which converted to hex = 882b2 Mac address = Manufacturer + SN ~ 0:40:11:8:82:b2   Windows calculator has a programmer mode that can be used to convert from decimal to hex.

Issue When closing Continuum 1.9x SU (SQL 2005 Express engine on a stand alone workstation),  it shows MFC error message of ACCDataServices and the Windows Event Log shows AlmUtil.dll error message. Environment Continuum SU 1.82 and higher version. Cause There are 3 Windows Schedule Tasks which are created during the DBInitialization->Creation of the Continuum SU workstation. Some possible causes are: If these Schedule Tasks are missing The Windows Schedule Tasks cannot be executed due to that fact that the current login userID is different than the one setup for the Schedule Tasks The password is not correct Resolution Manually create these 3 Schedule Tasks in the SU Cyberstation Alternatively: Uninstall SQL engine, Continuum Reboot the Workstation Reinstall Continuum SU, create a new DB from DB Initialization. Verify these 3 Schedule Tasks are created as below: CS_Distn CS_hrly CS_Minute

Issue Alarms about BACnet devices with duplicate names These are not required on the site Product Line EcoStruxure Building Operation Environment Third Party BACnet Devices Building Operation Enterprise Server Cause In EBO, BACnet device name uniqueness enforcement has been removed but an alarm is sent regardless to alert of the problem. Resolution Disable the alarm if it is not require in the alarm view. This is achieved by right clicking on the alarm in the Alarm Pane and 'Disable Alarm'

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are required.

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 Deleting reports built in Reports Builder using Building Operation WebReports Environment SmartStruxure Building Operation running Reports Server and Microsoft Report Builder Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Reports built using SQL interface such as Microsoft Report Builder cannot be deleted using the Manage Reports in Building Operation WebReports Resolution Building reports on the SQL side must be deleted on the SQL side.   From the first screenshot below, you can see that when using WebReports, in the Manage Reports tab, custom reports which are made are considered System Reports and the Delete button is grayed out.  Here I have created Top Alarms Test 1 report, which has been selected. Using SQL Server Management Studio, I penetrate to the tb.ReportGroups and see the isSystemOwned is True for the report Top Alarms Test 1 The isSystemOwned is changed to False for the selected report(s) Top Alarms Test 1 Viewing WebReports, in the Manage Reports tab, the Top Alarms Test 1 report is selected and the Delete option is available.

Issue Selection and installation of a pulsed output module. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, TAC Vista Environment Heat Meter Multical 602 Pulsed output module No pulses Cause Installed card does not give output pulses. Resolution Selection of the output card. The Schneider Electric part number is MAPULSETOPC and this is the equivalent to Kamstrup part number 602-0C This card will provide 2 pulse outputs for energy and volume, CE and CV respectively. Normally, energy (CE) is connected to 16-17 and volume (CV) to 18-19, but other combinations can be selected via the PC program METERTOOL, also used to select pulse duration 32 or 100 ms. The MAPULSETOPC is actually a top module, which means that it is fitted into the top piece of the MC602 calculator, basically the inside LCD cover. This is released by pressing downwards in the middle of the plastic piece on the left, and at the same time pushing the top module towards the left.

Issue Will public signals in TAC Xenta show up in Echelon Lonmaker? Will AI, DI, AO, DO, PVR, PVI, PVB blocks show up in Echelon Lonmaker?  Product Line TAC Vista Environment TAC Menta LonMaker or NL220 Xenta 30x, 401, 28x Cause Public signal are proprietary and can only be viewed from Schneider Electric products such as TAC Vista Workstation or EcoStruxure Building Operation. Resolution The answer to both questions is no. Only SNVTs are displayed in Echelon Lonmaker, and the SNVTs have to be added in TAC Menta and then downloaded to the TAC Xenta devices.

Issue Commission and Download command from Vista Workstation on a controller/network beneath a Xenta 911 communication port results in "Error: Failed to connect to TAC Xenta 911 - Invalid User/Password" Product Line TAC Vista Environment Vista Classic Network Communication Port - Xenta 911 Xenta 511/911 Cause Vista port properties has User name and Password stored.  If the user name or password are changed in the controller, these changes must be made to the Vista server settings as well. Resolution Obtain the most current user name and password for the Xenta hardware device If the password is not known and cannot be obtained, a temporary password can be assigned.  Please see Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost. Right-click on the Xenta 911 communication port and select Properties Enter the new user name and password under TCP/IP settings Attempt the Commission and Download command again.

Issue Processor % Loading and LAN % Loading; What do these mean and how can they impact my system. Processor % Loading -  This field displays the Controller processor (CPU) percent loading (0–100%). This number is an indication of how busy the controller is.  LAN % Loading - This shows the percentage of controller LAN communication attributable to this controller only. It is not the total control LAN loading figure. Product Line TAC INET Environment ALL I/NET Controllers (Controller LAN (CLAN) based) Cause A greater understanding of the values seen at each controller can greatly assist in having a more efficient I/NET network. Resolution The controller Processor % loading and LAN % loading are available from each controllers' configuration/status editor. You must be connected to the controller in order to use this editor. This information can also be obtained using the hand-held console, Code 3 (CPU %), and Code 4 (LAN %). These fields are display only. You cannot make changes. However, you can make changes to the database and observe the relative loading statistics after. The readings should be taken with all graphic pages and DCU controller point summaries closed. Processor % Loading This field displays the Controller processor (CPU) percent loading (0–100%).  This number is an indication of how busy the controller is.  If this number is 100, control actions may be lost or delayed. You should not let this reading go above 80%.  If kept to below 80% then if the processor peaks for some reason, it has 20% to peak in without locking up for a number of processor machine states. The conditions that affect the processor loading are as follows: Resident Point scan interval.  All resident points are processed by the firmware.  If you find that the processor loading is high, then edit all the AOs and DOs that do not have a calculation extension and adjusting the scan intervals to 255 seconds.  In heavily populated controllers this will bring down the processor % loading somewhat. Calculated Point frequency.  All resident points with a calculation extension will have their calculation processed at the scan interval of the target point.  If you find that the processor loading is high, then, on the calculation extensions that perform less important tasks, you may edit the target point’s scan intervals to a larger figure. Event Initiated Sequences.  A number of sequences that are in a loop, that is to say, running sequences with a skip back to themselves causing the sequence to run continuously, will cause the processor % loading to rise.  Edit and modify to create a more efficient database.  Ensure that a minimum of 1-second delay is implemented between each action within a sequence.  Do not leave all actions at the default value of zero.   DDC Module Sample Interval.  All DDC modules are processed at their respective sample interval.  If you find that the processor loading is high, then, on the DDC modules that perform less important tasks, you may edit the DDC module’s sample rates to a larger figure. Global or Indirect Traffic.  Naturally, large quantities of global and or indirect traffic to and from the controller will cause the processor % loading to rise.  See the next section “LAN % Loading” for more details. Graphic Pages and or Controller Point Summaries.  Graphic pages and or controller summaries with large quantities of points requesting information/data (solicited messages) from a controller will cause the processor % loading to rise.  This also includes the number of pages open either on the one host or multiple hosts.  You have a number of choices here; you could increase the host’s “Monitor Refresh Interval” to minimize the solicited traffic or you could rationalize the graphic pages to a more efficient use of points. Alarm or Messages.  Large quantities of alarm or message traffic (unsolicited messages) from the controller will cause the processor % loading to rise.  You will have to identify the cause.  Be aware just taking out the matching message masks from the host or from the point will not inhibit the message from transmitting to the LAN, the Resident Point’s Message and or Alarm priority must be set to “None”. SEVENTRENDS Data Uploads.  Large quantities of SEVENTRENDS data (unsolicited messages) being uploaded to the LAN from the controller will cause the processor % loading to rise.  You will have to identify the origin and alter the “Cell Sample Counts” and or the “Sample Control Interval” to relieve the condition.  Be aware just taking out the Host SEVENTRENDS Cell mask or the point’s Trend Sample SEVENTRENDS Distribution Mask will not inhibit the data from transmitting to the LAN, the SEVENTRENDS Distribution Priority must be set to “None”.  LAN % Loading This shows the percentage of controller LAN communication attributable to this controller only.  It is not the total control LAN loading figure.  Treat the control LAN as a 100% resource.  If this controller has a LAN percent loading of 23%, then the control LAN has only 77% of resources left to service the other controllers on the control LAN. Another way to look at it is, in the above example, out of every 100 token passes on the control LAN this controller has used the token 23 times. The best scenario is to have the lowest figure possible, e.g. 0%.  Just imagine a control LAN with 25 controllers connected, each controller with a ‘LAN % loading’ of 5 %.  The LAN is flooded and will cause messages to be lost and or buffered, graphic pages will not update as expected and the system will dramatically slow down. The empirical rule is as follows: The ‘LAN % loading’ is allowed to rise to a figure above 0%, but within 20 seconds, it must go back to 0%. The conditions that affect the ‘LAN % loading’ are as follows: LAN Reconfigures.  Every time a LAN reconfigures all global points in every controller on that control LAN transmit their values on to the LAN, and all indirect points request, at their scan interval, an update from their associated global points.  On an unstable control LAN, this could contribute heavily to a controller’s ‘LAN % loading’. Global Point Traffic.  Large quantities of global point traffic from the controller will cause the ‘LAN % loading’ to rise.  The conditions that affect the frequency of global traffic are: Global point’s “Broadcast Change Counts”.  Remember that multiplying the analog point’s conversion coefficient’s ‘m’ value with the broadcast change count value will be the resolution of the analog value to be exceeded to cause a broadcast onto the LAN. Just imagine a globalized analog point with a ‘m’ value of .05 and a Broadcast Change Counts set at 1.  Then this sensor will globalize its value every time the value exceeds 0.05 creating globalized traffic. The faulty sensor being globalized.  The sensor’s value being unstable to the extent that the point’s value changes exceed the “Broadcast Change Counts”, in extreme cases creating globalized traffic. Controller’s Power Line Frequency, HHC function [Ctrl 92], not set correctly.  This is for setting a notch filter to filter out power supply noise being imposed over the sensor’s input signal thereby helping to eliminate the sensor’s value appearing to fluctuate.  These fluctuations could send a global sensor’s value change to exceed the “Broadcast Change Counts” in extreme cases creating globalized traffic. Pulsed Input (PI) points.  The PI points “Scans between Broadcast” incorrectly assigned. Beware: a PI point with a “Scan Interval” of 1 second and a “Scans between Broadcast” set at 1 second will cause the controllers ‘LAN % loading’ to rise by 10% and stay there, even though the PI point’s value may not have changed. Indirect Point Traffic.  Large quantities of indirect point traffic from the controller will cause the ‘LAN % loading’ to rise.  The conditions that affect the frequency of indirect point traffic are: LAN Reconfigures.  Every time a LAN reconfigures all indirect points, at their scan interval, request an update from their associated global points.  On an unstable control LAN, this could contribute heavily to a controller’s ‘LAN % loading’. Indirect Point scan intervals set incorrectly.  If an indirect point does not see a change in its state/value from the global point after 2 scan intervals then the indirect point will request an update from its associated global point to be reported at the indirect point’s 3 rd scan.  With global points that are reasonably static, i.e. not altering a lot e.g. status points, etc., the associated indirect points will carry out their requests for updates.  Therefore the indirect points scan intervals should be staggered system-wide, not just controller-wide.  If all the indirect points have the same scan interval they could conceivably request at the same time and queue and hang onto the control LAN’s token. Graphic Pages and or Controller Point Summaries.  Graphic pages and or controller summaries with large quantities of points requesting information/data (solicited messages) from a controller will cause the ‘LAN % loading’ to rise.  This also includes the number of pages open either on the one host or multiple hosts.  You have a number of choices here; you could increase the host’s “Monitor Refresh Interval” to minimize the solicited traffic or you could rationalize the graphic pages to a more efficient use of points. Alarm or Messages.  Large quantities of alarm or message traffic (unsolicited messages) from the controller will cause the ‘LAN % loading’ to rise.  You will have to identify the cause.  Be aware just taking out the matching message masks from the host or from the point will not inhibit the message from transmitting to the LAN, the Resident Point’s Message and or Alarm priority must be set to “None”. SEVENTRENDS Data Uploads.  Large quantities of SEVENTRENDS data (unsolicited messages) being uploaded to the LAN from the controller will cause the ‘LAN % loading’ to rise.  You will have to identify the origin and alter the “Cell sample counts” and or the “Sample Control Interval” to relieve the condition.  Be aware just taking out the Host SEVENTRENDS Cell mask or the point’s Trend Sample SEVENTRENDS Distribution Mask will not inhibit the data from transmitting to the LAN, the SEVENTRENDS Distribution Priority must be set to “None”.  

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

Issue Will a certain badge printer, signature pad or capture device work with Continuum? Product Line Andover Continuum Environment CyberStation Cause Certain badge printers. signature pad and cameras that have been tested and approved by ImageWare are supported. Resolution Note: ImageWare is a third party add on for Continuum, all support on compatibility questions should be directed to ImageWare at the following ImageWare Support Link. Please check the EPISuite compatible hardware list to verify whether a badge printer, signature or capture device has been tested by ImageWare. See also current device driver download page. Update as of August 2015 direct from ImageWare Systems EPI Builder Updates NEW QR Code barcode plug-in ImageWare has recently built a plug-in that provides the ability to create QR Code barcodes within EPI 6.x Designer. If you are interested in testing out this update, please let me know and I will provide you with a link for download. Camera Hardware Compatibility List: Canon cameras EOS Rebel XS, EOS Rebel T3, EOS Rebel T5 and EOS Rebel T5i Tested on Windows 7 (32-bit & 64-bit) and Windows 8.1 (64-bit) Requires IWS custom software plug-in to provide direct control and image capture from the client workstation to the camera. Plug-in is licensed and sold per client workstation. Videology cameras 1.3 MP USB Color Box Camera Tested on Windows 7 (32-bit) Camera can be used out of the box with its TWAIN driver (TWAIN data source SFT-10011 REV2.1.18). No additional IWS software plug-in is needed. 5 MP USB 2.0 Camera with Synchronized Flash and Auto Focus (24C708AF) Tested on Windows 7 (32-bit & 64-bit) Test PENDING for Windows 8.1 Camera can be used out of the box with its TWAIN driver (TWAIN driver version 2.1.22). No additional IWS software plug-in is needed. Sony camera (PENDING IWS custom plug-in release) EVI-D70 Pan/Tilt/Zoom Color NTSC Video Camera Tested on Windows 7 (32-bit & 64-bit) and Windows 8.1 (64-bit) IWS custom software plug-in provides direct control and image capture from the client workstation to the camera. Plug-in is licensed and sold per client workstation. Camera requires the dPict Aexeon LT video capture card hardware to be installed within the client workstation. Webcams EPI Builder works with most Webcams with compatible TWAIN drivers. IWS has worked with both the Logitech HD Pro Webcam C910 and C920 camera models. Most webcams can be used out of the box with its TWAIN driver. No additional IWS software plug-in is needed. Signature Pad Hardware Compatibility List: ePad-Ink Signature Pad VP9805 Tested on Windows 7 (32-bit and 64-bit) and 8.1 (64-bit) Requires IWS custom software plug-in to provide direct control and image capture from the client workstation to the device. Plug-in is licensed and sold per client workstation. Topaz SigPlus Signature Pad -L-460-HSB, T-LBK460-HSB-R and T-S571-HSB Tested on Windows 7 (32-bit and 64-bit) Requires IWS custom software plug-in to provide direct control and image capture from the client workstation to the device. Plug-in is licensed and sold per client workstation. NOTES EPI Builder typically supports the generic TWAIN driver, as well as Video For Windows (VFW). Furthermore, EPI also indirectly supports the WIA drivers, which Windows ports internally to the TWAIN driver. Each device manufacturer will provide drivers of some or all of these types with an implementation of their own specific functions. WIA is supported under certain circumstances. In each case the functions that will be present depend on the Manufacturer's implementation of these drivers. If you would like to internally evaluate any IWS EPI capture plug-in, please let me know and I will supply you with a 30 day evaluation license. Printer Hardware Compatibility List: Below are some of the current printers which we have received in house for testing.  Datacard SR300 Tested on Windows 7 Tested Mag encoder Digital Identification EDIsecure DCP360+ Tested on Windows 7 Fargo DTC 4500e Tested on Windows 7 and 8.1 Tested Mag encoder Fargo HDP 5000 Tested on Windows 7 Tested Mag encoder Magicard Rio Pro Duo Tested on Windows 7 and 8.1 Tested Mag encoder Matica Technologies XID 8300 Tested on Windows 7 Tested Mag encoder NiSCA PR-C101 Tested on Windows 7 Tested Mag encoder Zebra ZXP Series 7 Tested on Windows 8.1 (Windows 7 testing is pending) Tested Mag encoder Zebra ZXP Series 8 Tested on Windows 7 and 8.1 Tested Mag encoder IDP SMART-50L M N Tested on Windows 7 and 8.1 Tested Mag encoder POINTMAN USA  Test PENDING for October 2015 NOTE: We have tested other printers on Windows XP and they may be supported in Windows 7 and 8.1 depending on the available drivers. Also, other printer make/models are being used with the EPI software, but we only list printers that we've received in house for testing. If you are interested in having IWS test a specific make/model printer, please let us know and we will try to work with you and the manufacturer to obtain a demo printer in house to run through compatibility testing.