Building Automation Knowledge Base

Issue When a user logs on to Workstation and accesses the hyperlink, the website is displayed without prompt for login credentials Product Line EcoStruxure Building Operation Environment Building Operation Workstation Microsoft Internet Explorer Cause EcoStruxure Building Operation software uses Microsoft Internet Explorer to present web pages. How the page logs on is an IE function and not a function of EBO Workstation Resolution  Log off from the web site before logging off from Workstation  Configure Internet Explorer to delete browsing history on exit Go to Internet Explorer settings and then the Internet Options On the General tab, under the Browsing history, enable the checkbox for 'Delete browsing history on exit' (computer restart may be required)

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 for assistance. Issue When you attempt to save a Menta application in Workstation you will get an "Invalid Data" Error. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Menta Editor Cause Some public variable in the Menta application has had Initial bindings added that conflict with the EBO bindings. Resolution Remove the Initial bindings from the variables in the Menta application and use EBO bindings. To find these Initial bindings follow these steps, Edit the Menta device with the issue From the File Menu "export" the Menta application to a known location on the PC and save it as a MTA file. Browse to this MTA file you exported and open this file with the Menta Editor From the File menu select "Save as" option. Give the file a name and in the Save as Type select FDB (*.AUT) Using Note Pad++ edit the AUT file you just created. Search the AUT file for the label "InitialBindings" [see Figure1 below] Make a note of the objects with Initial bindings so the initial bindings can be deleted from the Menta file. In Workstation edit the Menta device and remove the initial bindings from the objects found in step 7 and change the name of the object noting the original name down. Save the Menta application to the server. In Workstation edit the same Menta device and rename the object back to the noted name in step 8. Save the Menta application.

Issue Following an upgrade to V1.5 from V1.4 the AS goes off/ online. Environment Automation Server AS Enterprise Server ES V1.50 and above. Cause Following an upgrade to V1.5 from V1.4 the AS goes off/ online caused by an incorrect setting of the Default Priority Level. Resolution This issue only occurs if the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. So before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher. If the system has been upgraded with the incorrect values, then:  If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher. If after upgrading a multiserver configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: 1. Apply the hot fix #1.5.0.4301; available from Product Support Services 2. Fix the multi-server (by detaching/re-attaching the servers) 3. Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" has a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected, this also applies even if the hot fix is installed. The effects of not setting the Default above the Force Priority level are: 1. If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SBO servers and those in 3rd party BACnet devices. 2. If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid. Note: The Default and Force Priority Level are located/ defined in the Green "System" folder, "Interface Manager", "BACnet" for each Server.

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 @TriggeredTimeStamp does not always report the last time an object transitioned to an off-normal state. Environment Alarms Substitution Codes Event Notifications. Cause Both the Normal and the Reset alarm states represent conditions where the alarmed object has assumed an acceptable value and is not in alarm Reset = The object has returned to a normal state but the return to normal notification has not been acknowledged. Normal = The object has returned to a normal state and the return to normal notification has been acknowledged. The TriggeredTimeStamp value is updated only when the object transitions from a Reset Alarm State to an Alarm Alarm state. The TriggeredTimeStamp value is not updated when the object transitions from an Alarm Alarm State to a Reset Alarm state. If an object goes into alarm and that alarm event is never again acknowleged, the Triggered Time Stamp will continue to reflect that initial alarm transition time regardless of how many times the object goes into and out of an alarm state. Resolution In order to get the Triggered Time Stamp to update, the notification must be acknowleged so that the alarm can return to a Normal state (rather than Alarm State = Reset) before it transitions to Alarm. 

Issue Unable to find data sheet for TAC M500 actuator Environment TAC M500 actuator Cause No data sheets are to be found on the Extranet Resolution The data sheet for TAC M500 actuator can be found here

Issue Understanding how the NPR functions in a corporate WAN / LAN environment NPR network Issues What information can we provide to IT (MIS) departments that will explain what the NPR is doing on their network. Product Line TAC INET Environment I/NET Seven Series 2000 NetPlus Router (NPR) Cause This advisory discusses the interaction of a Series 2000 NetPlus Router (NPR) with a corporate LAN/WAN. It is intended to alleviate any concerns MIS personnel may have regarding Ethernet network loading or LAN/WAN security.  Resolution For information on the Series 2000 NetPlus Router (NPR) when used on a corporate LAN / WAN refer to the attached Customer Advisory CA-2004-01.  This advisory includes more detailed information of the following topics: The NetPlus Router and Dial Security Protocols Packet Routing TCP/IP Communication Network exposure I/NET Ethernet Network Loading Network Utilization The NetPlus Router and Network Configurations Network Configuration for Proxy ARP:

Issue When connecting the RoamIO-2 service tool directly to a standalone BACnet b3 controller which is not connected to the MSTP network yet, the RoamIO-2 does not show the b3 controller on the screen. Environment RoamIO-2 Continuum SmartStruxure BACnet b3 controller Cause By default, the View option of the ROAMIO2 Bacnet Service Tool is set to view "By Network".  Resolution Connect the RoamIO2 service tool directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries. Click the green icon to connect. Now, it will show the b3 controller in the service tool.

Issue A laptop has USB ports, but does not have serial ports. Can I/NET run using USB ports? Product Line TAC INET Environment Windows XP Windows Vista Windows 7 Cause Most new computers do not provide the “Old Style” serial ports, they now have USB ports instead. Resolution A lot of Schneider Electric have been using the KEYSPAN USB to Serial Adapter. The Part Number is KEYSPAN – USA – 19HS. Click here for a data sheet. This product can be seen by going to https://www.tripplite.com/ Please note that there are other products that are equally as good

Issue After downloading application and parameters to a TAC Xenta from TAC Vista, get an error message "OUT OF MEMORY (RAM)" When trying to edit a Xenta trend in TAC Vista Workstation get an error message "Could not save the object: OUT OF MEMORY (RAM)" Product Line TAC Vista Environment TAC Vista Workstation TAC Menta Cause The error message means that a trend log definition exceeds the capacity on the TAC Xenta unit. Resolution In Menta: Select the "Option" menu, and click on "Trend Logs". In the Select Trend Log dialog box, double click on the trend log that need to be edited. In the "Trend Log Definition" window, under "Signal" section: Increase the "Log Interval" time Decrease the "Log Space" time In TAC Vista Workstation: Right click on the Xenta log that needs to be edited. Select "Properties". Under the "Signal" Tab: Increase the "Log interval" time. Decrease the "Log space" time.

Issue Running Windows XP, Service Pack 2 and I/NET Seven Configuration Instructions Product Line TAC INET Environment I/NET Site running XP Cause Windows XP Service Pack 2, it will be necessary to configure the Firewall feature which is on by default in the Service Pack Resolution Please see the following link to configure XP to allow I/NET Seven file equalization to function properly. XP SP2 Configuration and InetSeven.doc

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. Issue Dependencies for Vista Server running as a service Product Line TAC Vista Environment Vista Server Cause The Vista server can run into issues if it starts up before other services. Resolution Ensure that Vista Server does not start up before Aladdin Privilege Server by making some changes to the registry. Select the start menu, select run, and type “regedt32”. Once the program opens you should browse to the following path: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TACOS\ The key named DependOnService should by default contain the value RPCSS. To add a dependency to this service just modify the value of the key and add the name of the service you wish to start before this one. In the case of Aladdin Privilege Server just add the text “Privilege Win32 Server” to the registry key. Close the registry editor and the dependency will be visible in the services properties window for TACOS. Note: If you need Vista to start late in the boot cycle but you do not have a specific service dependency, as explained above, then choose one of the services which startup last as the data value for the value "Depends on Service". Services commonly selected are Spooler and Messenger.

Issue Understanding DbCreate Utility Product Line TAC INET Environment DbCreate Cause Various Database errors Resolution The DbCreate utility provides you with the basic tools you'll need to create and remove an I/NET SQL database. After creating an empty database, you can use DbCreate to import data from a previously installed I/NET 2000 version 2.x system in order to upgrade to I/NET Seven. Note: In most cases, you will probably use DbCreate's graphical user interface (GUI) in order to interactively perform tasks. However, you also have the option of performing DbCreate tasks silently from a command line. For information about using the command line, refer to Using DbCreate from the Command Line. Ref; Online Help "Using DbCreate". Use DbCreate to perform any of the following tasks: Create an empty database To create a new SQL database.doc Import I/NET 2.x data Importing I/NET 2000.doc Import a Docutrend archive Importing a Docutrend Archive.doc Verify the existing SQL database Verifying the Existing SQL Database.doc Remove an existing I/NET SQL database Removing an Existing I/NET Db.doc Backup an SQL database Backup an SQL Database.doc Restore an SQL database Restore an SQL Database.doc Upgrading the database Upgrading the database.doc Recording a Log File When you activate () the Record logfile, DbCreate will record a log file. The path and filename may be specified. If no path is specified, the file is created in the current directory. Also, if the path specified is invalid, the current directory is used. There are two levels of logging: normal and verbose. By default only significant events are logged. When the –V (verbose) flag is set, other informational events are also logged. Monitoring Progress Once an operation has started, its progress can be monitored in the lower half of the DbCreate dialog. Side-by-side progress bars show the overall progress of the operation (left progress bar) and of the individual task being performed (right progress bar). A scrollable text area keeps a list of actions that are being performed. The text includes the result of each action performed. If you have chosen to import I/NET 2000 2.x data, the Start button changes to Abort, and all other controls are disabled. Pressing Abort will attempt to stop the operation in progress. In this case, the database will contain only partial data from the I/NET 2000 system that was being imported.

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.

Issue Direct Connect Xenta 527-NPR or 527 Web Server through I/NET Environment I/NET site Cause Direct Connect a Xenta 527-NPR or 527 Web Server through I/NET Resolution Are you using a Xenta 527-NPR or 527 Web Server and want to direct connect to it through I/NET and not having any luck? There are a couple of things that you need to set up in the unit for serial communication to I/NET through Port A (RS 232). The Xenta 527 NPR is set at factory default (RS232 Port A). The following steps should get you through this: Start I/Net and create a profile for the NPR (Net Plus Router) in I/O Server, then make this active. Verify that you have the correct cable to hook up from the serial port of the PC to Port A (RS 232) on the unit. (L1: RJ45 to RJ45 part # 0-073-0817). Connect them together. At this time you will need to start X Builder, if you don’t have it already, then you need to download it from the Exchange Extranet. The path is TAC Vista > Engineering Tools > TAC XBuilder > TAC XBuilder 1.5 (or latest revision). Download this to the PC. Start XBuilder through Programs > TAC > TAC Tool > XBuilder. Once started, select File\ New Project\(Project Name)\Location (default)\Project Template (select 527 Project), call it 527 NPR or whatever makes sense to you. At the settings Editor, just hit the OK button. Once the Editor comes up, in the Network frame, expand the TAC_Xenta_527. Right Click on the RS232-485A selection, click on Add then select I/NET. If you click on the TAC_Xenta_527, you will see all the settings that you have originally set up through Hyper Terminal or you can put those in at this time. Now select the Generate Icon or press F10 to generate the file. In the bottom of your project you would see a message that says Xbuilder – 0 error(s), 0 warning (s). This indicates that your project is now complete without errors. Now select the Rocket Ship Icon or press F11 to transfer the file to the unit. Once completed, restart or cycle power on the 527. Go to I/Net\Edit\Host Computer\Network Configuration and your 527 will show up in the Link Summary. At this time you can save the link, penetrate it and save the controllers etc. the old fashioned way. At this time you should be able to work on your system through a direct connect on a Xenta 527 NPR/Webserver unit.

Issue TAC Vista and Peripheral Software Installation Outline Product Line TAC Vista Environment Microsoft Windows 2000/XP (Microsoft) LonMaker (Echelon) Microsoft Visio PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI Adobe Acrobat  LNS  lmw31.exe lmw313U1.exe LNS3SP8.EXE LNSSP8U1.EXE HASP device driver h4_hinstall hdd32.exe Privilege Licenser 2.01 Aladdin Privilege Administrator 2.01 taclicense201.exe taclicense202.exe .NET Framework 1.1 TACVistaConfig1.2.0 .NET Framework 1.1 SP1 Microsoft SQL Server (MSDE)2000 SP4 MSXML 4.0 MDAC 2.8 Vista Server IV WorkStation TAC ToolPack 4.X   Cause The correct installation procedure for Vista IV and necessary peripheral software. Resolution Below is an outline that can be followed to install Vista in the proper order. Each "*" denotes a software package followed by the associated files/programs that are included. Depending on your specific application, some of the software may not be needed. For example, a Vista Classic network will not need LonMaker. Call Tech Support if you have any questions concerning the software needed for your application. *Microsoft Windows 2000/XP (Microsoft) *LonMaker (Echelon CD) LNS Utilities: Microsoft Visio, PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI (only if using an Echelon LNS interface), Adobe Acrobat (if you don't already have it) *Update LonMaker to 3.13 and LNS to 3.08.05 (TAC Extranet) lmw31.exe, lmw313U1.exe, LNS3SP8.EXE, LNSSP8U1.EXE *HASP device driver utility (TAC Extranet) h4_hinstall - MUST Execute from a Command Prompt! or... hdd32.exe if using Windows Server 2003 *Privilege Licenser 2.01 - "taclicense201.exe" or 2.02 - "Privilege Windows XP crash hotfix" (TAC Extranet) *.NET Framework 1.1 (Microsoft) *TACVistaConfig1.2.0 (TAC Extranet) .NET Framework 1.1 SP1, Microsoft SQL Server (MSDE)2000 SP4, MSXML 4.0, MDAC 2.8 (Reboot) At this point you could be prompted to choose which type of Licensing to be used. Select which option is best for you, the Site License (Order Entry Department), 30 Day Demo (TAC Extranet), or Engineering dongle. This will write the appropriate license files to the Privilege License Server. *Vista Server 4.X with WorkStation (TAC Extranet) (Reboot) *TAC ToolPack 4.X (TAC Extranet) If you encounter any errors during the installation process, be sure to make a note of specific errors received so Technical Support can better troubleshoot your issue. A simple way to record errors are to capture a "screenshot" (Ctrl+PrintScnr). The screenshot can then be pasted (Ctrl+V) into Paint a text editor like wordpad for later reference. Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue Time Zone Database shows +0 for all time zones when the platform date is in 2016. IA Series G3 version 3.6.407 IA Series G3 version 3.7.108 IA Series G3 version 3.8.41 Product Line TAC IA Series Environment IA Series G3 versions 3.6.407, 3.7.108, and 3.8.41 Cause This error appears when listing the contents of the Niagara Time Zone database where the Time Zone Database shows +0 for all time zones when the platform date is in 2016.  The issue is related to an error within the 3.8.41 baja and hx modules and only affects the display within the Platform view only.  The actual behavior and operation of the Time Zone remains accurate.  Prior IA Series G3 versions (e.g. 3.8.38, 3.7.106, and 3.6.406) or earlier will not exhibit this issue. Resolution Download and upgrade the baja and hx modules available in the latest consolidated patch files. baja 3.6.407.3 (or higher) and hx 3.6.407.1 (or higher) baja 3.7.108.3 (or higher) and hx 3.7.108.1 (or higher) baja 3.8.41.2 (or higher) and hx 3.8.41.1 (or higher) The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area (reference Latest consolidated patch files for I/A Series G3 maintenance builds with details).  Download and install the appropriate patch for the version.

Issue Problems receiving emails from Xenta 511/527 Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause Some email servers have been found to filter UTF-7 character encoding as spam. The Xenta products require this encoding to support Swedish characters, but this can be configured by manually editing some files. Resolution Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device Cycle power The device will now use UTF-8 character encoding which is more commonly used in the United States. For more troubleshooting tips, see Troubleshooting sending emails from a Xenta Server.

Issue What amount of memory is used for DPU Resident Individuals in the DPU\SCU controller? Product Line TAC I/NET Environment I/NET Seven - Access control DPU7910A, DPU7920, DPU7920 w/DPU48K, and SCU1284 Cause Need to understand the memory allocation and implications of using DPU Resident settings with both the DPU or SCU hardware devices. Resolution To set the Individual as DPU Resident the DPU Res. checkbox needs to be checked in the Individuals editor as shown below (red box) shown below.     In the table below from TCON300 05/17 Chapter 9-14 shows the memory allocation for a 7910A DPU or DPU7920   If you have a selection of between 6000 to 12000 Resident User Individuals (i.e. set as DPU Resident) in the system you can ONLY have between 3262 to 2887 Cached users respectively stored within a properly communicating system.  If the DPU is offline to the Sub LAN Interface (SLI) these cached users will be reduced as the requirement for the DPU storage capacity will need to store 'offline' messages as shown under the "Messages" column.     In the table below from TCON300 05/17 Chapter 9-15  shows the memory allocation for a SCU1284 DPU or DPU7920 w/DPU48K   If you have a selection of between 6000 to 12000 Resident Users Individuals (i.e. set as DPU Resident) in the system you can have the full quota of 48,000 Cache Users respectively stored within a properly communicating system.  Unlike the DPU7910 or 7920 if the DPU is offline to the Sub LAN Interface (SLI) there is no change to these cached users and there is more 'offline' message storage as shown under the "Messages" column. For further information on DPU Caching and memory management read from Chapter 9-11 in TCON300-05/17

Issue What should be considered when analyzing the performance of a Modbus TCP/IP implementation? Environment Modbus TCP/IP implementation Cause Check the performance level of Modbus TCP/IP implementation for possible improvement. Resolution Determining if a Netcontroller will handle the load of a specific Modbus TCP/IP implementation must take into account many different factors. A lot depends upon the 3rd party device, the network utilization of the IP network, the number of devices/points being polled and the speed/polling rate of the devices on the RS485 network. The Modbus TCP/IP xdriver behaves as a client and polls for information in a round robin basis. The more data it has to poll the longer it will take. The organization of the Modbus Addresses is also important. For example: If 12 registers are at consecutive address locations i.e. 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, then 1 data packet is required to retrieve all this information. If only a few registers are at consecutive locations i.e. 1, 2, 3, 8, 21, 22, 23, 30, 40, 65, 66, 67 then 6 data packets are required to retrieve this information. If the registers are all in separate locations i.e. 1, 5, 10, 20, 30, 40, 50, 60, 70, 80 then 10 data packets, one for each address is required. The third example would take 10 times longer than the 1st to poll the address information. If address locations in the 3rd party device cannot be altered then it may be more efficient to create additional xdriver points to effectively 'fill the gaps' so as to reduce the number of data packets. It is recommended to carry out a bench test with the devices in order to analyze the configuration. This would allow for adjustments of the requests or adding additional hardware to poll the amount of required information. Field Example: Using a Modbus TCP/IP xdriver to poll a number of Powerlogic metering devices. Considering 30 EGX's/ECC's involved, plus two Powerlink 3000 panels, using 33 IP addresses. Each EGX/ECC has from 10-20 Modbus devices attached on the RS485 side. Each metering device will be polled for about 12 registers. In this example, we would be polling about 4000-5000 register points via Modbus TCP/IP with a NetController2. In this particular scenario, it was determined that 2 Netcontroller IIs would be needed to handle the amount of polling required at the expected performance level.