InduSoft SCADA Best Practices

2,280 views

Published on

InduSoft SCADA Best Practices

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,280
On SlideShare
0
From Embeds
0
Number of Embeds
268
Actions
Shares
0
Downloads
82
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

InduSoft SCADA Best Practices

  1. 1. InduSoft Web Studio 7.0+SP1<br />Best Practices<br />
  2. 2. Best Practices<br />When designing a new project<br />Tags Database<br />Graphic Interface<br /> General<br />Performance optimization<br /> Troubleshooting<br />When deploying the project<br />
  3. 3. When designing a project<br />Application Resolution<br />Platform and License<br />Review Project Settings (Viewer, Communication, Web)<br />Touch-screen settings (cursor, focus, vk, right-click, object size)<br />Translation (objects size)<br />Communication (every state or last state)<br />
  4. 4. Tags Database<br />Arrays<br />Classes<br />Tag Fields (->Hi, ->HiLimit, ->Quality, ->TimeStamp, etc)<br />Tag names (use objective names - avoid long names)<br />Avoid retentive values/parameters for a large number of tags<br />Tag Integration<br />Tag description<br />
  5. 5. Graphic Interface<br />Screen groups<br />Re-use screens (array tags, indirect tags, or mnemonics)<br />Share background pictures when applicable<br />Linked Symbols<br />$Ext() function to text used in external dialogs, such as MsgBox or InputBox.<br />
  6. 6. General<br />Avoid spaces and special characters in file names (e.g.: screen names)<br />Add comments to scripts and worksheets<br />History Life Time<br /> Avoid calling modal dialogs on the Server (MsgBox, InputBox, $RDFileN, etc) when using Thin Clients.<br /> Avoid hard-coded paths. Use $GetAppPath().<br />
  7. 7. General<br /> Avoid repeated scripts – Global Procedures. <br />Use ‘$region:<BlockName> to organize procedures in the Global Procedures dialog<br />When applicable, use ‘On Error Resume Next’ and ‘On Error Goto 0’ in scripts<br />Make sure that when using $DBCursorOpen() or $DBCursorOpenSQL(), call $DBCursorClose() to avoid memory leaking.<br />
  8. 8. General<br />When using the Recipe task, enable the XML format.<br />When using Thin Clients, enable the SSL option, as well as the Web Tunneling Gateway.<br />
  9. 9. Performance optimization<br />Sequential addresses in the driver sheet<br />Consider the options “Screen” or “Auto” in the Main Driver Sheet and OPC Client worksheets.<br />Adjust the “Send Period” for communication with Thin Clients<br />Trend decimation and Database Gateway<br /> Avoid large picture objects and fill effects in low-end HMIs (Windows Embedded CE).<br />
  10. 10. Troubleshooting<br /> Output window (Log Options, and Log Tags)<br />Database Spy<br />Cross-Reference<br />$Trace() function<br />
  11. 11. When deploying the project<br />Clear Database Spy<br />Disable LogWin “save to disk” option<br />Remove “test” files (HST, Alarm, WebDump)<br />Remove unused tags from the project<br />Quality Feedback (unexpected errors)<br />Run “Verify” command<br /> Create a backup<br />
  12. 12. Questions ?<br />
  13. 13. Contact InduSoft Today<br />Email<br />(US) info@indusoft.com<br />(Brazil) info@indusoft.com.br<br />(Germany) info@indusoft-germany.de<br />Supportsupport@indusoft.com<br />Web site<br />(English) www.indusoft.com<br />(Portuguese) www.indusoft.com.br<br />(German) www.indusoft-germany.de<br />Phone (512) 349-0334 (US)<br />+55-11-3293-9139 (Brazil)<br />+49 (0) 6227-732510 (Germany)<br />Toll-Free877-INDUSOFT (877-463-8763)<br />Fax (512) 349-0375<br />USA<br />Brazil<br />Germany<br />

×