INtimeÂ® 3.1 Software - tenAsys

More documents

Recommendations

Info

INtime <strong>3.1</strong> <strong>Software</strong> interface, then data manipulation and data storage can be given a lower relative priority. A hypothetical system Note • You can use the Windows Performance Monitor to observe CPU usage by Windows and INtime software’s RT kernel. For more information, see Performance monitor in Chapter 10, INtime application development. • You can dedicate 100% of one processor to INtime on a multi-core computer without negatively affecting Windows performance. This hypothetical INtime application monitors and controls dialysis. The application consists of three main hardware components: Figure 5-1. The hardware of the dialysis application system A bedside unit is located by each bed. Each unit runs INtime software, which performs these functions: - Measures the toxins in the blood as it enters the unit - Adjusts the rate of dialysis - Removes toxins from the blood - Generates the bedside display for bedside personnel - Accepts commands from the bedside personnel - Sends information to the MCU (Master Control Unit) The MCU, a PC with a screen and keyboard, runs INtime software. The MCU enables one person to monitor and control the entire system. It performs these functions: - Accepts commands from the MCU keyboard - Accepts messages from the bedside units (toxicity levels, bedside commands, emergency signals) - Creates the display for the MCU screen A LAN connects the bedside units to the MCU. The next sections describe how various INtime software features are used in the hypothetical system. 58
Chapter 5: Designing RT applications Interrupt and event processing Multi-tasking Interrupts and internal events occur at the bedside units: bedside personnel enter commands asynchronously and the system computes toxicity levels at regular intervals. Toxicity levels, measured as the blood enters the bedside unit, are not subject to abrupt change. The machine slowly removes toxins while the patient's body, more slowly, puts toxins back in. The result is a steadily declining toxicity level. The bedside units must monitor toxicity levels regularly, but not too frequently. For instance, the bedside units could compute the toxicity levels once every 10 seconds, using a clock for timing. The measurement thread would measure and compute the toxicity, put the information in a mailbox for the MCU, and suspend itself for 10 seconds. Command interrupts from the bedside unit occur when a medical operator types a command and presses Enter. Interrupts from command entries occur at random times. The interrupt handler signals the interrupt thread. The interrupt thread performs any required processing and waits for the next interrupt. Processing commands from the bedside units: Each time a medical operator types a command and presses Enter, the bedside unit receives an interrupt signal from the terminal. The bedside unit stops executing the current instruction and begins to execute an interrupt handler. 1. The interrupt handler accumulates the characters in a buffer and puts them in memory. The interrupt handler signals the interrupt thread for bedside commands. 2. The interrupt thread gets the contents of the memory where the handler put the command. It parses the command and does the required processing. 3. The thread puts the command information, along with the number of the bedside unit, into a message. 4. The thread sends the message to the predetermined mailbox for the MCU. 5. The interrupt thread waits for the next interrupt. The system returns to its normal priority-based, preemptive scheduling. Threads in the application run using preemptive, priority-based scheduling. This allows the more important threads, such as those that control the dialysis rate, to preempt lower-priority threads, such as those that update displays. New capabilities can be added to the system by simply adding new threads. 59
Page 1 and 2:
U S E R ’ S M A N U A L INtime ®
Page 3 and 4:
Before you begin This guide describ
Page 5 and 6:
Before you begin Glossary Notationa
Page 7 and 8:
Before you begin • Within source
Page 9 and 10:
Contents Part I Chapter 1 Chapter 2
Page 11 and 12:
Contents Part II Chapter 6 Chapter
Page 13 and 14:
Contents Part III Appendix A Append
Page 15 and 16:
Contents NTX DLLs..................
Page 17 and 18:
I Introducing INtime software This
Page 19 and 20:
1 Overview INtime software extends
Page 21 and 22:
Chapter 1: Overview Considerations
Page 23 and 24: Chapter 1: Overview Developing an I
Page 25 and 26: Chapter 1: Overview INtime software
Page 27 and 28: Chapter 1: Overview • INtime Grap
Page 29 and 30: Chapter 1: Overview • Remote conf
Page 31 and 32: 2 Understanding INtime software arc
Page 33 and 34: Chapter 2: Understanding INtime sof
Page 45 and 46: 3 About INtime software’s RT kern
Page 47 and 48: Chapter 3: About INtime software’
Page 55 and 56: 4 About RT programming This chapter
Page 57 and 58: Chapter 4: About RT programming Pre
Page 59 and 60: Chapter 4: About RT programming whe
Page 61 and 62: Chapter 4: About RT programming Fig
Page 63 and 64: Chapter 4: About RT programming Syn
Page 65 and 66: Chapter 4: About RT programming The
Page 67 and 68: Chapter 4: About RT programming Exc
Page 69 and 70: Chapter 4: About RT programming Str
Page 71 and 72: 5 Designing RT applications This ch
Page 73: Chapter 5: Designing RT application
Page 77 and 78: II Using INtime software This part
Page 79 and 80: 6 Installation This chapter explain
Page 81 and 82: Chapter 6: Installation 5. Select o
Page 83 and 84: 7 Configuration INtime software pro
Page 85 and 86: Chapter 7: Configuration Tab Local
Page 87 and 88: Chapter 7: Configuration Configurin
Page 89 and 90: Chapter 7: Configuration Setting th
Page 91 and 92: 8 Preparing an RT node This chapter
Page 93 and 94: Chapter 8: Preparing an RT node Bui
Page 95 and 96: Chapter 8: Preparing an RT node 4.
Page 97 and 98: Chapter 8: Preparing an RT node Fir
Page 99 and 100: 9 Operation This chapter describes
Page 101 and 102: Chapter 9: Operation • INtime too
Page 103 and 104: 10 INtime application development T
Page 105 and 106: Chapter 10: INtime application deve
Page 125 and 126:
III Appendices The appendices inclu
Page 127 and 128:
A INtime software system calls This
Page 129 and 130:
Appendix A: INtime software system
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
B The iwin32 subsystem This appendi
Page 159 and 160:
Appendix B: The iwin32 subsystem A
Page 161 and 162:
Appendix B: The iwin32 subsystem Mu
Page 163 and 164:
Appendix B: The iwin32 subsystem Sh
Page 165 and 166:
Appendix B: The iwin32 subsystem Us
Page 167 and 168:
Appendix B: The iwin32 subsystem Pr
Page 169 and 170:
C INtime directory structure This a
Page 171 and 172:
D INtime software components This a
Page 173 and 174:
Appendix D: INtime software compone
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
E Visual Studio .NET debugging for
Page 191 and 192:
Appendix E: Visual Studio .NET debu
Page 193 and 194:
F Adding INtime software to an XP E
Page 195 and 196:
G Troubleshooting This appendix lis
Page 197 and 198:
Appendix G: Troubleshooting Table G
Page 199 and 200:
Appendix G: Troubleshooting Table G
Page 201 and 202:
Glossary application loader asynchr
Page 203 and 204:
Glossary memory area memory pool me
Page 205 and 206:
Index A B C D E F G H I J K L M N O
Page 207 and 208:
A B C D E F G H I J K L M N O P Q R
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
show all

INtimeÂ® 3.1 Software - tenAsys

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?