Common use of Additional Drivers Clause in Contracts

Additional Drivers. The drivers noted above are included as part of the ASYN distribution. Additional drivers are available, including: • Driver for Prologix LAN/GPIB adapter asynPortDriver C++ base class A C++ base class called asynPortDriver is available. This is a base class from which real asyn port drivers can be derived. It greatly simplifies the job of writing an asyn port driver, because it takes care of all of the tasks like registering the port, registering the interfaces, and calling interrupt clients. It is documented separately in asynPortDriver.html. asynPortClient C++ classes asynPortClient is a set of C++ classes that are designed to simplify the task of writing a client that directly communicates with an asyn port driver, without running an EPICS IOC. They handle the details of connecting to the driver, finding the required interfaces, etc. They only uses the synchronous interfaces, so all calls are blocking. If clients need asynchronous operation then they can use the normal C interface with pasynManager->queueRequest. It is documented separately in asynPortClient.html.

Appears in 4 contracts

Samples: epics-modules.github.io, epics-modules.github.io, epics-modules.github.io

AutoNDA by SimpleDocs

Additional Drivers. The drivers noted above are included as part of the ASYN distribution. Additional drivers are available, including: Additional Drivers 83 • Driver for Prologix LAN/GPIB adapter asynPortDriver C++ base class A C++ base class called asynPortDriver is available. This is a base class from which real asyn port drivers can be derived. It greatly simplifies the job of writing an asyn port driver, because it takes care of all of the tasks like registering the port, registering the interfaces, and calling interrupt clients. It is documented separately in asynPortDriver.html. asynPortClient C++ classes asynPortClient is a set of C++ classes that are designed to simplify the task of writing a client that directly communicates with an asyn port driver, without running an EPICS IOC. They handle the details of connecting to the driver, finding the required interfaces, etc. They only uses the synchronous interfaces, so all calls are blocking. If clients need asynchronous operation then they can use the normal C interface with pasynManager->queueRequest. It is documented separately in asynPortClient.html.

Appears in 1 contract

Samples: epics-modules.github.io

AutoNDA by SimpleDocs
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!