Issue Is there any information available regarding reference sites within the pharmaceutical manufacturing industries? Environment Vista 5.1.X Cause Customers will often require information about reference sites before committing to installing a new BMS or replacing an existing BMS. With the strict regulations within the pharmaceutical manufacturing industry it's important to know that our products are approved.  Resolution There are a number of references as well as other useful information on the download website at https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp.

Issue I have pneumatic actuators and want to convert to electric. Environment Pneumatic Actuators Cause Convert existing pneumatic actuators to electric. Resolution Conversions are possible for some but not all pneumatically activated valves. See the "Competitive Globe Valve Adapter Selection Guide" for all available adapters and applications.

Issue Need to confirm the correct part number to upgrade I/NET Do I need to pay for the I/NET software to upgrade the site? When can I use a SEAT license? What are the rules / definitions for using SEAT / SITE Licenses with I/NET? Product Line TAC INET Environment I/NET Software I/NET 2000 I/NET Seven to 2.4x Cause Confusion with part numbers and license restrictions within I/NET software offering.  Resolution  Ordering information is usually contained within each of I/NET's Product Announcements. These are found on The Exchange Download Center as well as on Software and Firmware compatibility matrix for older versions of the traditional product lines. When upgrading from a “minor” revision, upgrades from v2.40 are free. All you need is the new version of v2.4x software which can be downloaded at no charge from the Buildings Business Extranet website. To download TAC I/NET Seven software, refer to Downloads and Schneider Electric software, tools, documents, and tips. Upgrades from pre-2.4x versions (i.e. v2.3x and below) are paid upgrades. Standard upgrade prices are the same whether upgrading from I/NET Seven v2.31 or I/NET 2000. When upgrading, all host PCs must be upgraded to the same version.  Upgrade / New Ordering part number information can be found in How many software versions of I/NET Seven are there? For information that needs to be provided during the ordering process or if you have an issue with the Site License key refer to License or CD Key Issues. I/NET Seven Software Definitions Site Licenses SEVENHVAC SEVENMAX SEVENSEC Definition of a SITE: “A building or collection of buildings at single or multiple locations owned and operated by ONE end user, upon which I/NET is installed.” Seat License: SEVENSEAT Definition of a SEAT “A license for an additional PC at a SITE as defined above, irrespective of configuration i.e. Remote Client, Filemaster, Equalized Client etc.”

Issue I/A Series Software Compatibility with the Windows 7 Professional Operating System Product Line TAC IA Series Environment Microsoft Windows 7 Professional operating system (32-bit, 32-bit XP Mode, 64-bit XP Mode) WorkPlace Tech Tool (WPT) 5.7 and later PSI / XPSI  4.1 MNCI 4.0 MICROFLO Balance 4.0 PSOPRIF 11.6 Tree Tech 3.1 LON Flow Balance 3.0  Cause I/A Series software should only be run on tested and compatible equipment to avoid problems with software or hardware. Resolution See Product Announcement PA-00163 for detailed information on compatibility of current I/A Series Software tools and Windows 7. (Updated 3-14-12, replaces PA-00114 with PA-00163). See I/A Series (Niagara) R2 Windows Compatibility Matrix for information on the I/A Series (Niagara) R2 compatibility See WorkPlace Tech 5.8.x and 5.9.x Operating System and Microsoft Visio Compatibility for information on the I/A Series Workplace Tech compatibility

Issue I/A Series G3 version 3.8 and N4 version 4.2 Weather Service not following redirects Product Line TAC IA Series Environment I/A Series G3 3.8.x I/A Series N4 version 4.2 or older  Cause The National Weather Service (NWS) started recently redirecting from an HTTPS to an HTTP connection. Current conditions are not updated in Weather Service. The following messages appear in station output:  TRACE [15:05:30 27-Feb-18 EST][weather] Redirect to https://www.weather.gov/xml/current_obs/KBIV.xml WARNING [15:05:30 27-Feb-18 EST] [weather] Updating current conditions failed for WeatherReport javax.baja.sys.BajaException: Unable to get NWS Current Conditions feed at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:71) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) ... 12 more java.io.IOException: Redirect URL same as requested URL: www.weather.gov/xml/current_obs/KBIV.xml at com.tridium.weather.nws.FeedReader.getFeed(FeedReader.java:60) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:67) at com.tridium.weather.nws.NwsCurrentReader.getFeed(NwsCurrentReader.java:59) at com.tridium.weather.nws.NwsCurrentReader.getCurrent(NwsCurrentReader.java:84) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:630) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:275) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1602) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1135) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:166) at javax.baja.util.Worker$Processor.run(Worker.java:139) at java.lang.Thread.run(Thread.java:748) Note: The issue does not occur in I/A Series N4 version 4.3 or higher. Resolution For I/A Series G3 version 3.8 and newer, patched weather.jar modules resolve this issue. The weather module patches are available for download from the Schneider Electric Exchange as:  weather 3.8.311.1 - G3 Firmware weather 3.8.213.3 - G3 Firmware weather 3.8.112.1 - G3 Firmware weather 3.8.41.3 - G3 Firmware    To resolve the issue in Niagara 4.2 and/or versions of G3 not covered by the patches, Clear the hidden flag on the conditionsServer slot of the weather provider and change the value to w1.weather.gov.  After making this change, the current conditions will update.  The conditionsServer slot for each weather report will need to be modified if more than one is being used.  The following is a screenshot of the provider slot sheet. The Conditions Server slot is highlighted. Select Config Flags.   Config Flags dialog. Uncheck the Hidden flag and save.   View the Property Sheet for the provider and modify the Conditions Server to be w1.weather.gov

Issue I/A Series G3 schedule times can only be adjusted in half hour increments? Environment I/A Series G3 versions 3.3.22, 3.4.51, and 3.5.25 Cause Schedule module and associated user interface is not correctly processing the time setting causing the time to round to the nearest half hour increment. Resolution Note: It is recommended to upgrade to the latest maintenance build for the I/A Series G3 version being used. If this is not possible, updated schedule modules are available for download from https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp website.  

Issue What ground connections are required when wiring a voltage input? Product Line EcoStruxure Building Operation Environment AS/ AS-P Power Supply AS-B Universal Input Modules 0-10V, 0-5V sensors Cause The required connections are different for isolated and non isolated voltage inputs. Consideration of the system grounding is also required. Resolution If your input sensor is isolated it can be directly connected to the UI and RET terminals of the Universal Input module. An isolated sensor will have 4 terminals (2 power terminals G0 and G, 2 output terminals M and X) the power ground G0 is not directly connected to the output ground M terminal. However for non isolated sensors (usually 3 terminal devices) the signal terminal X will be wired to the UI input, but the sensors signal common G0 should be wired directly to the Signal Ground for the installation, not to the RET terminal of the IO Module. On every Input modules ensure that one RET terminal from the IO Module is wired directly to the Signal Ground. Full details of the required wiring and an example wiring drawing showing isolated and non-isolated voltage inputs can be found in "Wiring" section of the Hardware Reference Guide available on the Download Center or in WebHelp: Wiring.

Issue How many software versions of I/NET Seven are there? Part number License Environment I/NET Site Cause What I/NET licenses and what part number are available? Resolution Upgrade orders can be placed using the following part number: P/N: INETSEVEN24U TAC I/NET Seven Software CD TAC I/NET Seven Getting Started - TCON298 Software License Agreements TAC I/NET Seven Software Box New software orders can be placed using the following part numbers: SEVENMAXR - HVAC & Security site license, w/ CD SEVENHVACR - HVAC only site license, w/ CD SEVENSECR - Security only site license, w/ CD SEVENADDHVAC - Add HVAC, site license only SEVENADDSEC - Add Security, site license only SEVENSEATR - HVAC & Security license for 1 workstation, w/ CD, site license required SEVENSEAT3 - HVAC & Security license for 3 workstations, w/ 3 CDs, site license required SEVENSEAT5 - HVAC & Security license for 5 workstations, w/ 5 CDs, site license required SEVENMANUAL - Manual set, 3 volumes. No CD You will be provided with a CD Key only. You can download the installation files or ISO images from the Buildings Business Download Center at the link below. Search for "inet CD" or "inet iso" respectively. https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp

Issue Need information and help deciding on the correct product and part numbers. Product Line Andover Continuum Environment All current Continuum products Cause Customers do not always know how to find sales and product information on the various websites. (i.e. Catalogue, datasheets) Resolution For EMEA & Asia Pacific markets the Continuum Catalogue defines all current products and associated part numbers, see Andover Continuum Product Catalogue For the Americas information is available from the iPortal website for product selection and part numbers: http://iportal2.schneider-electric.com   Continuum datasheets are available from the Schneider Exchange Extranet link: https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp

Issue Can Microsoft Object Linking and Embedding (OLE) be used with Cyberstation? Environment Cyberstation linking to Excel using the OLE Toolkit. OLE, replacing the old DDE connections. Cause Live data is often required outside Cyberstation. Resolution The Continuum OLE Toolkit can be downloaded from The Exchange Download Center - download Continuum OLE Toolkit

Issue Some schedules stop operating correctly after Daylight Savings Time (DST) changeover.  Environment I/A Series G3, all ENS and ENC with builds 3.5.4, 3.4.53.1, 3.3.31.2, 3.2.23.1 or earlier. Cause Any station with a schedule, of any type, with an event set to occur during the "advanced" (missing) hour between 2:00 AM and 3:00 AM on the DST changeover day. The resulting miscalculation of the schedule's "Next Time" or "Next Trigger" time could cause that schedule, or even other schedules in the station, to stop working. This typically affects downstream logic in the station. In some cases it was observed that the CPU usage on an ENC went up to 100% while calculating invalid next event times. Examples A station contains a BooleanSchedule with events at 12:00 AM and then again at 2:05 AM daily. At 12 AM the schedule executes normally and attempts to calculate the next event time. On the second Sunday in March the next event time calculates to a time that does not exist due to the DST change. This causes the Java thread that executes all schedules in the station to become tied up attempting to recalculate the time. A station contains a TriggerSchedule that periodically repeats every 15 minutes, with a range passing through the DST changeover time. On the second Sunday in March the next trigger time calculates to a time that does not exist (say, 2:15 AM). Again, this causes the Java thread that executes all schedules to become tied up attempting to recalculate. Resolution The solution to this issue is to upgrade the schedule.jar file in the platform to one of the versions below, or later. Files are available from The Exchange Extranet.  Release 3.3.31.2 (Download and extract schedule-3.3.34.1) If you are using a build that is higher than the above versions then you will not be affected by this issue.

Issue Where can the FIPS fields be added to be accessed by webclient browsers? Environment Webclient FIPS Cause The question comes up asking if there is a way to add in the FIPS field to be accessed by webclient and it is not FIPS compliant Resolution Webclient is not FIPS compliant at this time. See page 15, item 8 in the Product Announcement FIPS 201 Solution   Additional Notes: In order to be FIPS compliant there is a middleware software piece that is part of the FIPS standard. The middleware company that we partnered with is called ImageWare and their product EpiBuilder integrates with Cyberstation. The integration doesn't currently run on a browser platform. If a site doesn't require FIPS then you would be able to add personnel through webclient, adding card numbers and areas, etc. Badge creation would still need to be done at a Cyberstation though since the ImageWare (EpiBuilder) application integration is used to create the badges.

Issue EcoStruxure Building Operation different types of licenses and all features Version 1.9 and older: Difference between Workstation standard and Workstation professional Product Line EcoStruxure Building Operation Environment All versions Cause Due to different features of each license, customer may get confused which license to order. Resolution See the version of the latest EcoStruxure Building Operation Part Number Summary document on the Exchange for all license part numbers.   Versions 2.0 and Newer Note: The licensing part numbers and structure has vastly changed starting in version 2.0 and newer.  See the search query below on the Exchange for more detail regarding the Scalable Pricing Policy that started in version 2.0. EcoStruxure Building Operation Scalable Pricing Information   Versions 1.9 and Older Note: There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing)  

Issue ENC is licensed for GCM but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacgcm" when attempting to access the GCM Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses   Tridium.license (Tridium 3.5 - never expires)   TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates   Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)  TAC.license (Tridium 3.6 - never expires)Certificates Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.  If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center website.  Navigate to the I/A Series G3 (ENS, ENC, etc.) Conference > SE Proprietary Drivers.  Use Workbench to import the downloaded file.

Issue Unable to key in a 'plus' sign (+) in the SMS recipient's Phone Numbers field Environment I/A Series G3 Cause The SMS recipient's phone numbers is required to be entered in international format. The international phone numbers format for sending an SMS is different for different countries. Example (using United Kingdom country code '44'): 00441403740290 or +441403740290 The following I/A Series G3 versions do not allow the 'plus' sign (+) to be entered in the SMS recipient's Phone Numbers field. I/A Series G3 version 3.4 and below I/A Series G3 3.5 versions lower than 3.5.36 I/A Series G3 3.6 versions lower than 3.6.36 Resolution Starting in build 3.5.36, 3.6.36, and 3.7 or later, a phone number may contain a ‘plus’ sign, for example: +441403740290. If you are running I/A Series G3 version 3.4 or below, you can download the updated SMS module here. If you are running a version of I/A Series G3 version 3.5 that is below version 3.5.36, upgrade to the latest version of 3.5 which is 3.5.39. If you are running a version of I/A Series G3 version 3.6 that is below version 3.6.36, upgrade to the latest version of 3.6 which is 3.6.31. These can be downloaded from https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp.

Issue Where can I find the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets? Product Line TAC IA Series Environment WorkPlace Tech Tool software I/A Series MNB BACnet family of controllers I/A Series MNL LON family of controllers Cause There is no single online source for the all the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets. Resolution All documentation related to the WorkPlace Tech Tool (WPT, WPCT & WPFB) and related controller documents are installed to your computer when you install the WorkPlace Tech Tool software. At the time of release, the current version of each software manual, hardware installation manual (LON & BACnet), specification data sheet (LON, BACnet & Software) and the software release notes document is built into the software installation program. These documents are all accessible under the \WorkPlace Tech\Help folder on any computer where the WorkPlace Tech Tool software is installed. All documentation can be displayed from the list displayed by the WorkPlace Tech Help menu. This was done to insure that all WorkPlace Tech Tool users would have access to the version of all documents related to that specific release of the software. Since these documents are included in the installation package for any version of the WorkPlace Tech Tool software, you can download the latest WorkPlace Tech Tool installation file from The Exchange Download Center to get the complete set of documents. These documents are also available individually from the 'Publication Zone', accessible from the 'Links' menu on iPortal (https://iportal2.schneider-electric.com).

Issue Where are the DUI expander objects for the MNB-300 and MNB-1000 controllers in Workplace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech version 5.1 through 5.9.4 I/A Series WorkPlace Tech version 5.10.0 till current Cause The standard stencils do not include an object for Momentary SS or a DUI multiplexer.  Resolution The I/A Series BACnet controllers do not currently support the DUI object directly within the MNB-300 or MNB-1000. An application performing the same basic function was created and factory tested. This application was created as a custom object named "DUI_App". For support of these objects in Workplace Tech 5.1 until 5.9.4, log into The Exchange Download Center and download the file Application Objects_rev1.zip. There is also a detailed DUI_Application_Documentation_rev1.pdf that describes the operation of the "DUI_App". For support of these objects in Workplace Tech 5.10.0 until further notice, log into The Exchange Download Center and download the file Application Objects_rev2.zip. There is also a detailed DUI_Application_Documentation_rev2.pdf that describes the operation of the "DUI_App". Note: VAV box controllers do not have DUI expander objects available. See TB06-02 for additional details.

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://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp Internal note: In bFO the Care Team to which PSS will De-Escalate case is the NAM_BLD_COE_ADV Care Team.

Issue How to change the CX level controllers message count to improve I2 Infinet communications. Throttling adjustments using accinfoframe1 and accinfoframe2. Product Line Andover Continuum Environment accinfoframe, accinfoframes, acc info frame Continuum Cyberstation CX 9680 Infinet I2 bus Cause Improve I2 communications on the infinet bus. Changing the CX level controller's message count on the Infinet bus to improve alarm delivery and exported data times when heavy polling is occurring. Resolution TPA-BOST-00-0004.00 describes several fixes, including one that improves field bus with heavy traffic. One of the fixes speeds up graphics and field bus reloads. With the latest version of the firmware the ability to throttle the number of messages during token passing has been added. This will allow a variable to adjust an Infinet bus based on the amount of traffic a particular bus is experiencing. With the latest firmware versions 2.100028, 2.000030 for the Netcontroller 9680 there are variables that can be used to adjust the number of messages per token pass. This is very similar to the MaxInfoFrames setting on Bacnet the devices; we'll call them “accinfoframe” for this document and examples. The value can be adjusted for values of 1-128. Since the TPA was issued, the value is defaulted to 128 and if no accinfoframe variable is created the default value is 128. In order to have the ability to adjust the number of messages in the supported controllers, an infinity numeric needs to be created in the CX/BCX. The name of the variable has to be correctly spelled but is case insensitive. The names are accinfoframe1 and accinfoframe2. Accinfoframe1 will be the setting for comm1 one and accinfoframe2 will control the setting for comm2. When configuring accinfoframe1 or accinfoframe2, make sure to select the SetPoint and back up the flash on your controller, so that you retain the settings in case of power failure. Example of when to use throttling: There will be instances where the accinfoframe variables will need to be throttled. For instance, lets theorize a site “ChillerPlant” and the ChillerPlantCX(9680) has 100 infinet controllers located on Comm1. In our scenario we have 3 workstations each running a graphic polling 2 points(200 points) from each Infinet controller and we are running listviews of infinitynumerics on 8 of the Infinets controllers or perhaps hundreds of points that are being collected for extended logging. As one might think, communications would begin to slow down when polling for values on approx 600 points not to mention the point to point communications of the listviews and extended logs. With all of this traffic, the CX will dominate the network token. Since it can do 128 messages when it receives the token and it receives the token between every Infinet, the token round time can go into minutes. This means that the Infinet controllers can take minutes to deliver alarms and exported data. Another potential scenario is if one selected 4 Infinet controllers to reload, the bus may very well be overloaded at this time and may be receiving errors on the reloads in the distribution window. One of the error messages that could be expected is “Unable to reload object CarlNet\My_9680\My_I2_814\Num_1. An invalid response was received from a remote service request.” In this example we could create a infinity numeric on the CX named accinfoframe1(for Comm1) and start to reduce the number of messages CX would generate before passing the token. On the other extreme, if the ACCInfoFrame setting is set too low, such as to 1 as in the earlier versions of Netcontroller II firmware, this extreme traffic could cause such issues as extreme slowness of graphics and listview updates, Extended logging not being capable of retrieving the required data at the required intervals, and possibly the Infinet controllers randomly appearing to be offline to the system. In the example above the question is “What value should the accinfoframe1 be set to?” The answer entirely depends on how much traffic is on the Infinet bus. How many extended logs, how many listviews, how many graphics, alarms and Plain English programs are creating traffic on the bus? The quick way out here would be set the accinfoframe1 to a value of 1. We know for a fact that this would slow the bus down, and you might want to increase the number to 5. As mentioned this is all dependent on the amount of traffic on the Infinet bus. Or we could take a more in depth approach and find out what the token round time is on the bus and adjust our accinfoframe1 based on token round time. We could create the following points. TOKEN ROUND TIMER PROGRAM InfinityNumeric MaxTokenItem InfinityNumeric MaxTokenRound InfinityNumeric TokenRoundTime Logsize:100 Logtype: LogMaximum InfinityProgram TokenRoundCalc InfinityDateTime LastDateExport Program code: Initialise: LastDateExport = PointMapsTests\Infinity2\i2_851\Date Goto DoTokenRoundCalc DoTokenRoundCalc: If LastDateExport <> PointMapsTests\Infinity2\i2_851\Date then TokenRoundTime = (PointMapsTests\Infinity2\i2_851\Date - LastDateExport) – 1 LastDateExport = PointMapsTests\Infinity2\i2_851\Date Endif MaxTokenRound = maximum(TokenRoundTime) MaxTokenItem = maxitem(TokenRoundTime) E: If TS >= 5 then Goto Initialise The program and points above created in the CX will allow the token round time to be captured and one could essentially get very creative and change the accinfoframe value dynamically through Plain English programming. For these examples we just want to find out the token round time and manually adjust the accinfoframe1 variable to avoid any reload errors. The TokenRoundTime, MaxTokenRound and MaxTokenItem numerics can be added to a watch window or a graphic to visually monitor the TokenRoundTime. If you see that your TokenRoundTime is 5, 10 15 seconds, this is an indication you need to reduce the accinfoframe1 value. As a rule of thumb a TokenRoundTime of less then 2 seconds is acceptable, while keeping the TokenRoundTime below 0.7 seconds is ideal.

Issue Cannot interface to the GE Lighting Control Panel PSLP Object nviPattern and nvoPatternFb with G3 lonGe-3.8.37.  Network variables nviPattern, nvoPatternFb, and nciChannelCfg are missing from the proxy points within the object definition. Environment I/A Series G3 - 3.8.37 Cause Network variables nviPattern, nvoPatternFb, and nciChannelCfg are based upon manufacturer types (GEPatternType and GEChType) and are not properly defined in the lonGe 3.8.37 module. The pslp object within the lonGe module generates warnings when added. WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nviPattern WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nvoPatternFb WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_0 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_1 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_2 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_3 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_4 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_5 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_6 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_7 Resolution Upgrade to lonGe-3.8.38.1.   The updated module is available for download from the Schneider Electric Download Center. https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp