Common use of Exception Handlers Clause in Contracts

Exception Handlers. The USBTMC driver attempts to take correct action when it detects that the device has been unplugged or become unresponsive. The effectiveness of this depends somewhat on the level of support provided by the underlying operating system so it is good practice to also specify the following StreamDevice global exception handlers: The drvAsynFTDIPort driver supports devices connected via FTDI adapters. FTDI ports are configured with the drvAsynFTDIPortConfigure and asynSetOption commands: drvAsynFTDIPortConfigure("portName",vendor,product,baudrate,latency,priority,noAutoConnect,noPro asynSetOption("portName",addr,"key","value") where the arguments are: • portName - The portName that is registered with asyn. • vendor - The USB vendor number associated with the FTDI device. • product - The USB product number associated with the FTDI device. • baudrate - The baudrate to be used with the FTDI device. • latency - The latency timer after which non-full FTDI buffers are sent. • priority - Priority at which the asyn I/O thread will run. If this is zero or missing,then epicsThreadPriorityMedium is used. • noAutoConnect - Zero or missing indicates that portThread should automatically connect. Non-zero if explicit connect command must be issued. • noProcessEos If 0 then asynInterposeEosConfig is called specifying both processEosIn and processEosOut. • mode: 0 = UART; 1 = FTDI initialized in binary SPI mode. USB TMC (Test and Measurement Class) driver 81 The setEos and getEos methods have no effect and return asynError. The read method blocks until at least one character has been received or until a timeout occurs. The read method transfers as many characters as possible, limited by the specified count. asynInterposeEos can be used to support EOS. The following table summarizes the drvAsynFTDIPort driver asynSetOption keys and values. Reasonable defaults are used at first. baud 50 75 000 000 000 200 300 600 1200 2400 9600 ... Any numeric value. Check chip datasheet for actual supported baud rates. bits 8 7 parity none even odd mark space stop 1 1.5 2 break off on flow rts_cts dtr_dsr xon_xoff Values can be OR'ed together, e.g., rts_cts|dtr_dsr The FTDI SPI interface was developed for control of evaluation board, EVAL-AD9915, via Adafruit FT232H. During initial SPI learning it is sufficient to short circuit, (loop-back), FTDI D1(MOSI) - D2(MISO) pins and read back written values. (Note the SPI is synchronous interface, not asynchronous.) AD9915 provides basic control for RF amplitude and phase. In order to use the Adafruit as USB - SPI converter for EVAL-AD9915 the following pins need to be connected: Adafruit FT232H EVAL-AD9915 connections D0 (SPI Clock, SK) SCLK-BUF D1 (Data Out, MOSI) SDIO D2 (Data In, MISO) SDO D3 (Chip Select, CS) CSB D4 IOUPDATE-BUF D5 SYNC_IO D6 RESET

Exception Handlers. The USBTMC driver attempts to take correct action when it detects that the device has been unplugged or become unresponsive. The effectiveness of this depends somewhat on the level of support provided by the underlying operating system so it is good practice to also specify the following StreamDevice global exception handlers: The drvAsynFTDIPort driver supports devices connected via FTDI adapters. FTDI ports are configured with the drvAsynFTDIPortConfigure and asynSetOption commands: drvAsynFTDIPortConfigure("portName",vendor,product,baudrate,latency,priority,noAutoConnect,noPro asynSetOption("portName",addr,"key","value") where the arguments are: • portName - The portName that is registered with asyn. • vendor - The USB vendor number associated with the FTDI device. • product - The USB product number associated with the FTDI device. • baudrate - The baudrate to be used with the FTDI device. • latency - The latency timer after which non-full FTDI buffers are sent. • priority - Priority at which the asyn I/O thread will run. If this is zero or missing,then epicsThreadPriorityMedium is used. • noAutoConnect - Zero or missing indicates that portThread should automatically connect. Non-zero if explicit connect command must be issued. • noProcessEos If 0 then asynInterposeEosConfig is called specifying both processEosIn and processEosOut. • mode: 0 = UART; 1 = FTDI initialized in binary SPI mode. USB TMC (Test and Measurement Class) driver 81 The setEos and getEos methods have no effect and return asynError. The read method blocks until at least one character has been received or until a timeout occurs. The read method transfers as many characters as possible, limited by the specified count. asynInterposeEos can be used to support EOS. The following table summarizes the drvAsynFTDIPort driver asynSetOption keys and values. Reasonable defaults are used at first. baud 50 75 000 000 000 200 300 600 1200 2400 9600 ... Any numeric value. Check chip datasheet for actual supported baud rates. bits 8 7 parity none even odd mark space USB TMC (Test and Measurement Class) driver 81 stop 1 1.5 2 break off on flow rts_cts dtr_dsr xon_xoff Values can be OR'ed together, e.g., rts_cts|dtr_dsr The FTDI SPI interface was developed for control of evaluation board, EVAL-AD9915, via Adafruit FT232H. During initial SPI learning it is sufficient to short circuit, (loop-back), FTDI D1(MOSI) - D2(MISO) pins and read back written values. (Note the SPI is synchronous interface, not asynchronous.) AD9915 provides basic control for RF amplitude and phase. In order to use the Adafruit as USB - SPI converter for EVAL-AD9915 the following pins need to be connected: Adafruit FT232H EVAL-AD9915 connections D0 (SPI Clock, SK) SCLK-BUF D1 (Data Out, MOSI) SDIO D2 (Data In, MISO) SDO D3 (Chip Select, CS) CSB D4 IOUPDATE-BUF D5 SYNC_IO D6 RESET

Exception Handlers. The USBTMC driver attempts to take correct action when it detects that the device has been unplugged or become unresponsive. The effectiveness of this depends somewhat on the level of support provided by the USB TMC (Test and Measurement Class) driver 81 underlying operating system so it is good practice to also specify the following StreamDevice global exception handlers: The drvAsynFTDIPort driver supports devices connected via FTDI adapters. FTDI ports are configured with the drvAsynFTDIPortConfigure and asynSetOption commands: drvAsynFTDIPortConfigure("portName",vendor,product,baudrate,latency,priority,noAutoConnect,noPro noProcessEos asynSetOption("portName",addr,"key","value") where the arguments are: • portName - The portName that is registered with asyn. • vendor - The USB vendor number associated with the FTDI device. • product - The USB product number associated with the FTDI device. • baudrate - The baudrate to be used with the FTDI device. • latency - The latency timer after which non-full FTDI buffers are sent. • priority - Priority at which the asyn I/O thread will run. If this is zero or missing,then epicsThreadPriorityMedium is used. • noAutoConnect - Zero or missing indicates that portThread should automatically connect. Non-zero if explicit connect command must be issued. • noProcessEos If 0 then asynInterposeEosConfig is called specifying both processEosIn and processEosOut. • mode: 0 = UART; 1 = FTDI initialized in binary SPI mode. USB TMC (Test and Measurement Class) driver 81 The setEos and getEos methods have no effect and return asynError. The read method blocks until at least one character has been received or until a timeout occurs. The read method transfers as many characters as possible, limited by the specified count. asynInterposeEos can be used to support EOS. The following table summarizes the drvAsynFTDIPort driver asynSetOption keys and values. Reasonable defaults are used at first. baud 50 75 000 000 000 200 300 600 1200 2400 9600 ... Any numeric value. Check chip datasheet for actual supported baud rates. bits 8 7 parity none even odd mark space stop 1 1.5 2 break off on flow rts_cts dtr_dsr xon_xoff Values can be OR'ed together, e.g., rts_cts|dtr_dsr The FTDI SPI interface was developed for control of evaluation board, EVAL-AD9915, via Adafruit FT232H. During initial SPI learning it is sufficient to short circuit, (loop-back), FTDI D1(MOSI) - D2(MISO) pins and read back written values. (Note the SPI is synchronous interface, not asynchronous.) 82 FTDI Port AD9915 provides basic control for RF amplitude and phase. In order to use the Adafruit as USB - SPI converter for EVAL-AD9915 the following pins need to be connected: Adafruit FT232H EVAL-AD9915 connections D0 (SPI Clock, SK) SCLK-BUF D1 (Data Out, MOSI) SDIO D2 (Data In, MISO) SDO D3 (Chip Select, CS) CSB D4 IOUPDATE-BUF D5 SYNC_IO D6 RESET

Exception Handlers. The USBTMC driver attempts to take correct action when it detects that the device has been unplugged or become unresponsive. The effectiveness of this depends somewhat on the level of support provided by the underlying operating system so it is good practice to also specify the following StreamDevice global exception handlers: The drvAsynFTDIPort driver supports devices connected via FTDI adapters. FTDI ports are configured with the drvAsynFTDIPortConfigure and asynSetOption commands: drvAsynFTDIPortConfigure("portName",vendor,product,baudrate,latency,priority,noAutoConnect,noPro asynSetOption("portName",addr,"key","value") where the arguments are: • portName - The portName that is registered with asyn. • vendor - The USB vendor number associated with the FTDI device. • product - The USB product number associated with the FTDI device. • baudrate - The baudrate to be used with the FTDI device. • latency - The latency timer after which non-full FTDI buffers are sent. • priority - Priority at which the asyn I/O thread will run. If this is zero or missing,then epicsThreadPriorityMedium is used. • noAutoConnect - Zero or missing indicates that portThread should automatically connect. Non-zero if explicit connect command must be issued. • noProcessEos If 0 then asynInterposeEosConfig is called specifying both processEosIn and processEosOut. • mode: 0 = UART; 1 = FTDI initialized in binary SPI mode. USB TMC (Test and Measurement Class) driver 81 The setEos and getEos methods have no effect and return asynError. The read method blocks until at least one character has been received or until a timeout occurs. The read method transfers as many characters as possible, limited by the specified count. asynInterposeEos can be used to support EOS. The following table summarizes the drvAsynFTDIPort driver asynSetOption keys and values. Reasonable defaults are used at first. baud 50 75 000 000 000 200 300 600 1200 2400 9600 ... Any numeric value. Check chip datasheet for actual supported baud rates. bits 8 7 parity none even odd mark space stop 1 1.5 2 USB TMC (Test and Measurement Class) driver 81 break off on flow rts_cts dtr_dsr xon_xoff Values can be OR'ed together, e.g., rts_cts|dtr_dsr The FTDI SPI interface was developed • Driver for control Prologix LAN/GPIB adapter 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 evaluation boardwriting an asyn port driver, EVAL-AD9915because it takes care of all of the tasks like registering the port, via Adafruit FT232H. During initial SPI learning it registering the interfaces, and calling interrupt clients. It is sufficient to short circuit, (loop-back), FTDI D1(MOSI) - D2(MISO) pins and read back written valuesdocumented separately in asynPortDriver.html. (Note the SPI is synchronous interface, not asynchronous.) AD9915 provides basic control for RF amplitude and phase. In order to If clients need asynchronous operation then they can use the Adafruit as USB - SPI converter for EVAL-AD9915 the following pins need to be connected: Adafruit FT232H EVAL-AD9915 connections D0 (SPI Clock, SK) SCLK-BUF D1 (Data Out, MOSI) SDIO D2 (Data In, MISO) SDO D3 (Chip Select, CS) CSB D4 IOUPDATE-BUF D5 SYNC_IO D6 RESETnormal C interface with pasynManager->queueRequest. It is documented separately in asynPortClient.html.

Exception Handlers. The USBTMC driver attempts to take correct action when it detects that the device has been unplugged or become unresponsive. The effectiveness of this depends somewhat on the level of support provided by the underlying operating system so it is good practice to also specify the following StreamDevice global exception handlers: The drvAsynFTDIPort driver supports devices connected via FTDI adapters. FTDI ports are configured with the drvAsynFTDIPortConfigure and asynSetOption commands: drvAsynFTDIPortConfigure("portName",vendor,product,baudrate,latency,priority,noAutoConnect,noPro noProcessEos asynSetOption("portName",addr,"key","value") where the arguments are: • portName - The portName that is registered with asyn. • vendor - The USB vendor number associated with the FTDI device. • product - The USB product number associated with the FTDI device. • baudrate - The baudrate to be used with the FTDI device. • latency - The latency timer after which non-full FTDI buffers are sent. • priority - Priority at which the asyn I/O thread will run. If this is zero or missing,then epicsThreadPriorityMedium is used. • noAutoConnect - Zero or missing indicates that portThread should automatically connect. Non-zero if explicit connect command must be issued. • noProcessEos If 0 then asynInterposeEosConfig is called specifying both processEosIn and processEosOut. • mode: 0 = UART; 1 = FTDI initialized in binary SPI mode. USB TMC (Test and Measurement Class) driver 81 The setEos and getEos methods have no effect and return asynError. The read method blocks until at least one character has been received or until a timeout occurs. The read method transfers as many characters as possible, limited by the specified count. asynInterposeEos can be used to support EOS. The following table summarizes the drvAsynFTDIPort driver asynSetOption keys and values. Reasonable defaults are used at first. baud 50 75 000 000 000 200 300 600 1200 2400 9600 ... Any numeric value. Check chip datasheet for actual supported baud rates. bits 8 7 parity none even odd mark space stop 1 1.5 2 80 USB TMC (Test and Measurement Class) driver break off on flow rts_cts dtr_dsr xon_xoff Values can be OR'ed together, e.g., rts_cts|dtr_dsr The FTDI SPI interface was developed • Driver for control Prologix LAN/GPIB adapter 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 evaluation boardwriting an asyn port driver, EVAL-AD9915because it takes care of all of the tasks like registering the port, via Adafruit FT232H. During initial SPI learning it registering the interfaces, and calling interrupt clients. It is sufficient to short circuit, (loop-back), FTDI D1(MOSI) - D2(MISO) pins and read back written valuesdocumented separately in asynPortDriver.html. (Note the SPI is synchronous interface, not asynchronous.) AD9915 provides basic control for RF amplitude and phase. In order to If clients need asynchronous operation then they can use the Adafruit as USB - SPI converter for EVAL-AD9915 the following pins need to be connected: Adafruit FT232H EVAL-AD9915 connections D0 (SPI Clock, SK) SCLK-BUF D1 (Data Out, MOSI) SDIO D2 (Data In, MISO) SDO D3 (Chip Select, CS) CSB D4 IOUPDATE-BUF D5 SYNC_IO D6 RESETnormal C interface with pasynManager->queueRequest. It is documented separately in asynPortClient.html.