Brochures

SmartStruxure Architectural s Guidelines 1.3

Description
SmartStruxure Architectural s Guidelines 1.3
Categories
Published
of 6
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
  [ SmartStruxure Solution ] 1 ArchitecturalArchitectural GuidelinesGuidelines 1.31.3  The architectural guidelines are intended to outline Architectural summary important considerations that need to be taken The strategy for the recommendations provided inwhen designing a SmartStruxure solution.the following tables is to allow the system tosupport any realistic combination within the A SmartStruxure solution has few hardcodedrecommended limits without negative effect on thelimitations. Therefore, most of thetotal performance.recommendations are based on tests and softwaredesign. Table: Architecture Function Enterprise Server AutomationServer Comment Number of servers 1 32  – Number of concurrent 10 1 Enterprise Server: 2WebStation or WorkStation engineering usersconnections Automation Server: 1engineering userNumber of concurrent 5 5  – mobile connections Table: LonWorks Function Enterprise Server AutomationServer Comment Maximum number of Xenta 100  – 30 b 280/300/401 devices perserver a Maximum number of 200 LonWorks devices include64 b LonWorks devices per MNL devices and Xentaserver 100 devices Total number of Xenta 200 Xenta 4xx I/O modules64 b 280/300/401 devices and hosted by a XentaLonWorks devices per 280/300/401 device are notserver counted as LonWorksdevicesMaximum number of NVs 400 400  – on local nodeMaximum number of 5 1 One local node on theLonWorks networks Enterprise Server a) Xenta 280/300/401 needs to be of version 3.6 or higher. In version 3.8, a new feature improves the performance up to 500%when reading values in StruxureWare Building Operation.b) When using both LonWorks and BACnet MS/TP networks on the Automation Server, the network with more than 10 devicesconnected is considered to be the main network. The other network then supports up to 10 devices. The main network willsupport the number of devices specified in the table for the used protocol. For example, if the Automation Server has 64LonWorks devices connected to it, the BACnet MS/TP network can support 10 devices.      ©     2     0     1     3     S    c     h    n    e     i     d    e    r     E     l    e    c     t    r     i    c .     A     l     l    r     i    g     h     t    s    r    e    s    e    r    v    e     d . Schneider Electric | Building Business  www.schneider-electric.com/buildings03-13027-01-en June 2013  [ SmartStruxure Solution ] 2 Table: Modbus Function Enterprise Server AutomationServer Comment Maximum number of RTU 62 62 Maximum 31 devices perslave devices COM port x 2 ports = 62Enterprise Server: Requires2 serial ports to be availableMaximum number of TCP 100 100  – server devicesMaximum number of TCP 9 4  – gatewaysMaximum number of 2 2  – concurrent TCP clientconnections when acting as TCP serverMaximum number of RTU 2 2 Maximum 31 devices permasters when acting as a COM port x 2 ports = 62serial slaveEnterprise Server: Requires2 serial ports to be availableMaximum number of 2,500 2,500 Total number of objects forModbus objects per server TCP (including gateways)and serial Table: BACnet Function Enterprise Server AutomationServer Comment Maximum number of N/A BACnet MS/TP devices50 a BACnet MS/TP devices per include b3 devicesserver50 user-defined objectsMaximum number of 600 50  – BACnet/IP devices perserverMaximum number of BBMD No practical limit known No practical limit known  – per serverMaximum number of 64 64  – foreign devices per sever a) When using both LonWorks and BACnet MS/TP networks on the Automation Server, the network with more than 10 devicesconnected is considered to be the main network. The other network then supports up to 10 devices. The main network willsupport the number of devices specified in the table for the used protocol. For example, if the Automation Server has 64LonWorks devices connected to it, the BACnet MS/TP network can support 10 devices. Table: Trend logs Function Enterprise Server AutomationServer Comment Maximum number of 2,000 1,000  – internal trend logs      ©     2     0     1     3     S    c     h    n    e     i     d    e    r     E     l    e    c     t    r     i    c .     A     l     l    r     i    g     h     t    s    r    e    s    e    r    v    e     d . Schneider Electric | Building Business  www.schneider-electric.com/buildings03-13027-01-en June 2013  [ SmartStruxure Solution ] 3 Continued  Function Enterprise Server AutomationServer Comment Maximum number of 5,000 1,500  – extended trend logsMaximum number of 100,000 100,000  – records per trend logNumber of records per N/A 500 Built-in logs for all I/Oimplicit log module points; notchangeable Table: Alarms Function Enterprise Server AutomationServer Comment Maximum number of active 10,000 1,000  – alarmsMaximum number of alarms 10,000 1,000  – displayed in WorkStationMaximum number of alarms 1,000 1,000 200 for both servers if displayed in WebStation version 1.3 SP1 is notinstalled Table: Events Function Enterprise Server AutomationServer Comment Maximum number of events 200,000 10,000  – Maximum number of events 6,000 6,000  – displayed in WorkStationMaximum number of events 6,000 6,000  – displayed in WebStation Table: Variable connectors Function Enterprise Server AutomationServer Comment Maximum number of No practical limit known 500 Used when the binding hasvariable connectors no obvious direction orwhen passing databetween protocols Table: Web Services Function Enterprise Server AutomationServer Comment Maximum number of 5 5 WebServices andconnections EcoStruxure Web Services      ©     2     0     1     3     S    c     h    n    e     i     d    e    r     E     l    e    c     t    r     i    c .     A     l     l    r     i    g     h     t    s    r    e    s    e    r    v    e     d . Schneider Electric | Building Business  www.schneider-electric.com/buildings03-13027-01-en June 2013  [ SmartStruxure Solution ] 4 Continued  Function Enterprise Server AutomationServer Comment Maximum number of values No practical limit known 2,000  – consumed by the server Time to read 1000 values 1 second 3 seconds  – Due to load caused by the variable connectors, limit Design considerations the number of variable connectors according to theLoad measurements variable connectors table above. It is possible toincrease this number, but close monitoring of CPU There are two server properties that are relevant forload and memory consumption is needed.understanding the load on the Automation Server: Automation Server databaseã Memory usage (%) The Automation Server database has a limit of ã CPU usage (%)104,000 objects. This limitation is normally more The Memory usage (%) property measures the than adequate but might be restrictive if acurrent RAM memory usage. The memory usage significant number of LonWorks devices are used.should never exceed 80 %. No peaks should beseen above this limit. A trend log with thousands of records is counted asonly one object. The CPU usage (%) property measures the currentCPU load in the Automation Server. The CPUConcurrent usersusage should stay below 80 %. It is normal that theUser type definitionsCPU usage peaks at 100 % on occasion whenlower priority activities are performed. This peak ã An operator views and monitors the systemdoes not affect the overall performance.and can make changes to the system, such ascreate trend logs, alarms, schedules, users, These two properties are the key measurementand perform some object property changes.points when monitoring the load of the Automationã An engineer also makes other changes to theServer. They need to be considered at all times,system that are typically not supported byespecially when getting close to (or exceeding) theWebStation, such as create and changedefined limits. The properties can be trend logged TGML, Function Block, and Script objects;or online plotted in a standard trend chart. Thesecreate devices; import and export; and backupproperties are not available for the Enterpriseand restore.Server. The server accepts one change at a time andBackup operationsqueues up concurrent changes. Changes made byBack up the system when users are not interacting an operator are quickly handled by the server andwith the servers or the system. no noticeable delay occurs when the changesqueue up. Some of the engineering changes might Variable connectors take a longer time. Changes made during that timeare handled by the server when the engineering The system has a base philosophy where differentchange is finished.objects and properties are connected usingbindings. Bindings do not usually cause anyReferences between Automation Serverssignificant load to the system, but in some casesthe bindings need to be driven by an external object There are two main things to consider whencalled a variable connector. The user does not optimizing the Automation Server to Automationcreate variable connectors. Server communication: The system creates variable connectors either ã Minimizing the quantity of references betweenwhen there is no obvious direction of the binding the Automation Servers.(analog value to analog value, for example) or whenã Minimizing the transfer interval intensity of thepassing data between protocols (LonWorks toreferences between the Automation Servers.BACnet or LonWorks to Modbus).      ©     2     0     1     3     S    c     h    n    e     i     d    e    r     E     l    e    c     t    r     i    c .     A     l     l    r     i    g     h     t    s    r    e    s    e    r    v    e     d . Schneider Electric | Building Business  www.schneider-electric.com/buildings03-13027-01-en June 2013
Search
Tags
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks