INtime® 3.1 Software - tenAsys
INtime® 3.1 Software - tenAsys
INtime® 3.1 Software - tenAsys
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 2: Understanding INtime software architecture<br />
Transport mechanisms<br />
With INtime software, NTX communicates between Windows and RT portions of<br />
INtime applications, whether they reside on a single PC, or on separate computers<br />
accessed via Ethernet cable:<br />
Figure 2-2. How NTX communicates with RT nodes<br />
Windows host<br />
INtime application(s)<br />
(Windows portion)<br />
<br />
NTX<br />
<br />
<br />
INtime<br />
application(s)<br />
(RT portion)<br />
RT client<br />
INtime<br />
application(s)<br />
(RT portion)<br />
RT client<br />
INtime<br />
application(s)<br />
(RT portion)<br />
RT client<br />
The Windows portion of INtime applications, located on a Windows host, makes NTX<br />
calls that communicate to RT clients.<br />
NTX determines RT client locations, detects the connection method, and determines<br />
how to communicate between Windows and RT threads.<br />
NTX uses the appropriate transport method to communicate with the RT portion of the<br />
INtime applications, located on RT clients.<br />
Transport methods available to NTX include:<br />
Transport<br />
mechanism<br />
Transport<br />
driver<br />
Description<br />
OSEM RTIF.SYS Used when the Windows host and RT client co-exist on a single PC. For details,<br />
see About the OSEM and How the RT interface driver works later in this<br />
chapter.<br />
Ethernet UDP/IP Used for Windows hosts and RT nodes connected via a local area network<br />
(LAN) cable. For details, see About remote NTX later in this chapter.<br />
19
Change language