Training
×

Windows + INtime Node Communication

INtime supports standard tcp/ip communication and several APIs.
Beside the full featured native INtime API, there also is an iwin32 API layer. Iwin32 is a subset of Win32 that many programmers are familiar with.
 
Win32 applications can communicate with INtime nodes using respective counterparts of the INtime APIs, global objects technology or network layers:
  • use the NTX functions to communicate with the INtime objects
  • use the iwin32x API to access iwin32 handles
  • use standard tcp/ip calls to access INtime- and D-RTOS nodes
 
Win32 applications can use INtime objects and iwin32 handles independent of where they are located. This global objects technology makes it very easy to scale a set of Windows and INtime applications from a small configuration with a single node to a large setup with many INtime nodes.
 
In the case where the Windows node needs direct access to shared memory, the Windows and INtime nodes need to share the same host. There is a transparent solution for memory copying if Windows and INtime nodes do not share the same host.