indusoft scada best practices

13
InduSoft.com [email protected] InduSoft Web Studio 7.0+SP1 Best Practices

Upload: marcia-gadbois

Post on 28-Jan-2015

181 views

Category:

Technology


7 download

DESCRIPTION

InduSoft SCADA Best Practices

TRANSCRIPT

Page 1: InduSoft SCADA Best Practices

InduSoft.com [email protected]

InduSoft Web Studio 7.0+SP1

Best Practices

Page 2: InduSoft SCADA Best Practices

InduSoft.com [email protected]

Best Practices

When designing a new

project

Tags Database

Graphic Interface

General

Performance optimization

Troubleshooting

When deploying the project

Page 3: InduSoft SCADA Best Practices

InduSoft.com [email protected]

When designing a project

Application Resolution

Platform and License

Review Project Settings (Viewer, Communication,

Web)

Touch-screen settings (cursor, focus, vk, right-

click, object size)

Translation (objects size)

Communication (every state or last state)

Page 4: InduSoft SCADA Best Practices

InduSoft.com [email protected]

Tags Database

Arrays

Classes

Tag Fields (->Hi, ->HiLimit, ->Quality, ->TimeStamp, etc)

Tag names (use objective names - avoid long names)

Avoid retentive values/parameters for a large number of

tags

Tag Integration

Tag description

Page 5: InduSoft SCADA Best Practices

InduSoft.com [email protected]

Graphic Interface

Screen groups

Re-use screens (array tags, indirect tags, or

mnemonics)

Share background pictures when applicable

Linked Symbols

$Ext() function to text used in external dialogs, such

as MsgBox or InputBox.

Page 6: InduSoft SCADA Best Practices

InduSoft.com [email protected]

General

Avoid spaces and special characters in file names

(e.g.: screen names)

Add comments to scripts and worksheets

History Life Time

Avoid calling modal dialogs on the Server (MsgBox,

InputBox, $RDFileN, etc) when using Thin Clients.

Avoid hard-coded paths. Use $GetAppPath().

Page 7: InduSoft SCADA Best Practices

InduSoft.com [email protected]

General

Avoid repeated scripts – Global Procedures.

Use ‘$region:<BlockName> to organize procedures

in the Global Procedures dialog

When applicable, use ‘On Error Resume Next’ and

‘On Error Goto 0’ in scripts

Make sure that when using $DBCursorOpen() or

$DBCursorOpenSQL(), call $DBCursorClose() to avoid

memory leaking.

Page 8: InduSoft SCADA Best Practices

InduSoft.com [email protected]

General

When using the Recipe task, enable the XML

format.

When using Thin Clients, enable the SSL option, as

well as the Web Tunneling Gateway.

Page 9: InduSoft SCADA Best Practices

InduSoft.com [email protected]

Performance optimization

Sequential addresses in the driver sheet

Consider the options “Screen” or “Auto” in the

Main Driver Sheet and OPC Client worksheets.

Adjust the “Send Period” for communication with

Thin Clients

Trend decimation and Database Gateway

Avoid large picture objects and fill effects in low-

end HMIs (Windows Embedded CE).

Page 10: InduSoft SCADA Best Practices

InduSoft.com [email protected]

Troubleshooting

Output window (Log Options, and Log Tags)

Database Spy

Cross-Reference

$Trace() function

Page 11: InduSoft SCADA Best Practices

InduSoft.com [email protected]

When deploying the project

Clear Database Spy

Disable LogWin “save to disk” option

Remove “test” files (\HST, \Alarm, \Web\Dump)

Remove unused tags from the project

Quality Feedback (unexpected errors)

Run “Verify” command

Create a backup

Page 12: InduSoft SCADA Best Practices

InduSoft.com [email protected]

Questions ?

Page 13: InduSoft SCADA Best Practices

InduSoft.com [email protected]

Email(US) [email protected](Brazil) [email protected](Germany) [email protected]

Support [email protected] site

(English) www.indusoft.com(Portuguese) www.indusoft.com.br(German) www.indusoft-germany.de

Phone (512) 349-0334 (US) +55-11-3293-9139 (Brazil) +49 (0) 6227-732510 (Germany)

Toll-Free 877-INDUSOFT (877-463-8763) Fax (512) 349-0375

Contact InduSoft Today

Germany

USA

Brazil