Safety Considerations Guide, Tricon v9.0 - Tuv-fs.com
Safety Considerations Guide, Tricon v9.0 - Tuv-fs.com Safety Considerations Guide, Tricon v9.0 - Tuv-fs.com
52 Important TriStation CommandsUpload and VerifyBefore you make changes to a project in TriStation, you should run the Upload andVerify command to verify that the project in TriStation matches the project runningin the controller. (The Upload and Verify command is on the Commands menu onthe Control Panel in TriStation.) This command compares the current projectrunning in the controller to a record of the last downloaded project. To use theUpload and Verify command, you must be able to connect your application to thecontroller using the Connect command on the Control panel in TriStation.For more information on the Upload and Verify command, see the TriStation 1131Developer's Guide.Compare to Last DownloadAfter you have run the Upload and Verify command, make the desired changes tothe project. Use the Compare to Last Download command to verify that thechanges to the project are only the intended changes. (The Compare to LastDownload command is on the Commands menu of the Configuration editor inTriStation.) To test the changes, use the Emulator Control Panel in TriStation.Tricon Safety Considerations Guide
Setting Scan Time 53Setting Scan TimeSetting appropriate scan time for the project is essential to avoid impropercontroller behavior. When changing a project running in an on-line system, specialprecautions should be exercised to avoid scan time overruns, which could result inunexpected controller behavior.Scan TimeScan time is the interval required for evaluations (in other words, scans) of anapplication as it executes in the controller. The time it actually takes to do anevaluation may be less than the requested scan time. To prevent scan-timeoverruns, a scan time must be set that includes sufficient time for all executableelements in an application—including print statements, conditional statements,and future download changes.Use the Scan Time parameter in the TriStation Configuration editor to suggest thedesired scan time before downloading an application. Upon downloading, thecontroller determines the minimum and maximum allowable scan times for yourapplication and uses your suggested scan time if it falls within the acceptablelimits. The default scan time is 200 milliseconds. The maximum allowable scantime is 500 milliseconds and the minimum allowable scan time is 25 milliseconds.Requested Scan Time is a system parameter that is set using the Configurationeditor.Actual scan time is the actual time of the last scan. Actual scan time is always equalto or greater than the requested scan time.Scan SurplusScan surplus is the scan time remaining after application elements have beenexecuted. Scan Surplus must be positive—if it is negative, the Scan Timeparameter must be adjusted using the Set Scan Time command on the ControlPanel to set the surplus value to greater than or equal to zero. The Scan Timeparameter in the TriStation Configuration editor applies only when you do aDownload All.Chapter 4Application Development
- Page 17 and 18: CHAPTER 1Safety ConceptsThis chapte
- Page 19 and 20: Safety Overview 3Protection LayersT
- Page 21 and 22: Hazard and Risk Analysis 5Hazard an
- Page 23 and 24: Hazard and Risk Analysis 7Completio
- Page 25 and 26: Hazard and Risk Analysis 9Equation
- Page 27 and 28: Hazard and Risk Analysis 11Flowchar
- Page 29 and 30: Hazard and Risk Analysis 13Some key
- Page 31 and 32: Safety Standards 15Safety Standards
- Page 33 and 34: Safety Standards 17Application-Spec
- Page 35 and 36: CHAPTER 2Application GuidelinesThis
- Page 37 and 38: General Guidelines 21• Under cert
- Page 39 and 40: Guidelines for Tricon Controllers 2
- Page 41 and 42: Guidelines for Tricon Controllers 2
- Page 43 and 44: Guidelines for Tricon Controllers 2
- Page 45 and 46: Guidelines for Tricon Controllers 2
- Page 47 and 48: Guidelines for Tricon Controllers 3
- Page 49 and 50: Guidelines for Tricon Controllers 3
- Page 51 and 52: Guidelines for Tricon Controllers 3
- Page 53 and 54: CHAPTER 3Fault ManagementThis chapt
- Page 55 and 56: System Diagnostics 39System Diagnos
- Page 57 and 58: Operating Modes 41Operating ModesEa
- Page 59 and 60: Module Diagnostics 43Module Diagnos
- Page 61 and 62: Module Diagnostics 45Relay Output M
- Page 63 and 64: Module Diagnostics 47System Attribu
- Page 65 and 66: CHAPTER 4Application DevelopmentThi
- Page 67: Important TriStation Commands 51Imp
- Page 71 and 72: Sample Safety-Shutdown Programs 55S
- Page 73 and 74: Sample Safety-Shutdown Programs 57I
- Page 75 and 76: Sample Safety-Shutdown Programs 59A
- Page 77 and 78: Sample Safety-Shutdown Programs 61P
- Page 79 and 80: Sample Safety-Shutdown Programs 63O
- Page 81 and 82: Sample Safety-Shutdown Programs 65D
- Page 83 and 84: Sample Safety-Shutdown Programs 67P
- Page 85 and 86: APPENDIX APeer-to-Peer Communicatio
- Page 87 and 88: Data Transfer Time 71ParameterTS =S
- Page 89 and 90: Examples of Peer-to-Peer Applicatio
- Page 91 and 92: TR_CRITICAL_IO Function Block 75TR_
- Page 93 and 94: TR_CRITICAL_IO Function Block 77Par
- Page 95 and 96: TR_CRITICAL_IO Function Block 79Str
- Page 97 and 98: TR_CRITICAL_IO Function Block 81CO
- Page 99 and 100: TR_SHUTDOWN Function Block 83Parame
- Page 101 and 102: TR_SHUTDOWN Function Block 85Relate
- Page 103 and 104: TR_SHUTDOWN Function Block 87* Exam
- Page 105 and 106: TR_SHUTDOWN Function Block 89TIMER_
- Page 107 and 108: TR_VOTE_MODE Function Block 91Param
- Page 109 and 110: TR_VOTE_MODE Function Block 93Appen
- Page 111 and 112: APPENDIX BShutdown Function BlocksT
- Page 113 and 114: TR_CRITICAL_IO Function Block 974 R
- Page 115 and 116: TR_CRITICAL_IO Function Block 99Rel
- Page 117 and 118: TR_CRITICAL_IO Function Block 101*
52 Important TriStation CommandsUpload and VerifyBefore you make changes to a project in TriStation, you should run the Upload andVerify <strong>com</strong>mand to verify that the project in TriStation matches the project runningin the controller. (The Upload and Verify <strong>com</strong>mand is on the Commands menu onthe Control Panel in TriStation.) This <strong>com</strong>mand <strong>com</strong>pares the current projectrunning in the controller to a record of the last downloaded project. To use theUpload and Verify <strong>com</strong>mand, you must be able to connect your application to thecontroller using the Connect <strong>com</strong>mand on the Control panel in TriStation.For more information on the Upload and Verify <strong>com</strong>mand, see the TriStation 1131Developer's <strong>Guide</strong>.Compare to Last DownloadAfter you have run the Upload and Verify <strong>com</strong>mand, make the desired changes tothe project. Use the Compare to Last Download <strong>com</strong>mand to verify that thechanges to the project are only the intended changes. (The Compare to LastDownload <strong>com</strong>mand is on the Commands menu of the Configuration editor inTriStation.) To test the changes, use the Emulator Control Panel in TriStation.<strong>Tricon</strong> <strong>Safety</strong> <strong>Considerations</strong> <strong>Guide</strong>
Change language