This shows you the differences between two versions of the page.
jvs:cigal:manual:chapter2:realtime [2011/03/31 14:49] 127.0.0.1 external edit |
jvs:cigal:manual:chapter2:realtime [2023/02/23 18:43] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | **CIGAL Reference Manual, Chapter 2 (Commands): REALTIME** | ||
- | |||
- | |||
- | ===== REALTIME -- Execute a series of i/o operations controlled by a real-time clock ===== | ||
- | **usage:** | ||
- | * **realtime rtprogram runlog mode** | ||
- | * **realtime** | ||
- | * **realtime 0** | ||
- | * **realtime - {...}** | ||
- | |||
- | The REALTIME command provides a way to execute a series of operations with precise timing. The command' | ||
- | The available operations also provide a fairly comprehensive programming environment thatincludes direct access to all of CIGAL' | ||
- | |||
- | The REALTIME command accepts the following arguments: | ||
- | |||
- | __**RTPROGRAM**__ | ||
- | |||
- | Normally, RTPROGRAM is the name of a disk file containing the list of | ||
- | operations and the times at which they are due to execute. | ||
- | reads and compiles this list into a series of internal sublists, each of | ||
- | which contains a sequence of operations to be executed in chronological | ||
- | order. The different sublists execute in parallel to provide multiple, | ||
- | independently timed control streams. | ||
- | |||
- | If REALTIME is called with no arguments, a previously suspended RT | ||
- | program is resumed (see [[jvs: | ||
- | memory. | ||
- | |||
- | If the RT_FILE argument is a - (minus sign, eg. CIGAL' | ||
- | argument placeholder), | ||
- | from the standard input (keyboard if entered interactively or current | ||
- | file if running from a macro). | ||
- | command line is encountered, | ||
- | interactively; | ||
- | execution of the operations. | ||
- | |||
- | __**RUNLOG**__ | ||
- | |||
- | This is an array or matrix variable which REALTIME will fill with a log of | ||
- | the operations it performed and the actual time at which those operations | ||
- | were executed. | ||
- | operation flags specified in the RT_FILE, as well as the value of the | ||
- | MODE argument (see below). | ||
- | long exec_time | ||
- | byte opcode | ||
- | byte eventflag | ||
- | integer | ||
- | If RUNLOG is omitted, REALTIME executes but does not record a log. | ||
- | |||
- | __**MODE**__ | ||
- | |||
- | This is a flag specifying REALTIME execution options. | ||
- | * 0 - execute RT program normally (default). | ||
- | * 1 - check for run-time errors | ||
- | * 2 - turn off taskbar explicitly during realtime (Note: sometimes taskbar acts odd when it comes back.) | ||
- | * 4 - execute RT program normally, except that after each operation has completed the amount of time the operation took is stored in the EXEC_FLAG field of the RUNLOG. | ||
- | * 10o - execute RT program and record elapsed times, but ignoring the scheduled execution times. Each operation begins as soon as the previous operation is completed. | ||
- | * 20o - single step through realtime program | ||
- | * 40o - log every real-time event (normally on flagged events) | ||
- | * 100o - test for timing conflicts | ||
- | * 2000o - Use DirectDraw for display | ||
- | |||
- | For more information on the REALTIME processor see HELP on: | ||
- | * R_PROCESSOR | ||
- | * R_SYNTAX | ||
- | * R_SUMMARY | ||
- | * R_OPS - a summary list showing the syntax of REALTIME operators | ||
- | |||
- | For more detailed information on any particular REALTIME operator ask for HELP | ||
- | for that operator (for example, "help r_repeat" | ||
- | |||
- | **See Also:**\\ | ||
- | [[jvs: | ||
- | [[jvs: | ||
- | [[jvs: | ||
- | |||
- | [[jvs: | ||
- | [[jvs: | ||
- | [[jvs: | ||
- | [[jvs: | ||