Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The functions are namely as follows:

  • DEVSUPFUN       init_record: Runs at each new record initialization. Create a new PV structure - pid_pvt or v_pvt depending on the record type. Checks if record INP is not INST_IO, prints error and exits. otherwise, it looks for the asyn parameters of the associated asyn driver by dissecting the INP field of the instantiated record, and extracting the port, the bsakey and the edef number. Once the reference is found, private pointers are stored.
  • DEVSUPFUN       get_ioint_info:  DEVSUPFUN       read; This routine is called by the ioEventScan system each time the record is added or deleted from an I/O event scan list. cmd has the value (0,1) if the record is being (added to, deleted from) an I/O event list.
  • read/write; Everytime the record is processed, the new value of the record is determined by this function. If no conversion is done, the new value is written to the val variable and 2 is returned. If conversion is done, the new value is written to rval and 0 is returned.

A graphical structure of t

Gliffy Diagram
macroIdfabbaf2e-603d-4306-8c45-4bcd13fd6754
namePointers between serviceAsynDriver and devBsss
pagePin1

At this point, the device supports exist, but are still not enabled for usage. the new device supports need to be added to the dbd file (bsaAsynDriver.dbd) using the following commands:

...