Page History

...

• serviceAsynDriver: Class constructor,  

• serviceAsynDriver

• writeInt32

• writeOctet

• updatePVA

• initPVA

• addBldChannelName

• MonitorStatus

• bsssCallback

• bldCallback

getServiceType

• Gets root Path from CPSW, creates the <Service>Yaml structure(s) provided by the timing/bsa package, and register callbacks

• SetupAsynParams: Creates all ASYN parameters the translate to PVs
• SetRate: set all EDEF rate related configurations (deprecated in BSSS)
• SetDest: set all EDEF destination related configurations
• SetChannelSevr: method to set the channel severity private variable
• GetChannelSevr method to get the channel severity private variable

• writeInt32: Asyn write 32 bit function used for passing PV values to firmware

• writeOctet: Asyn write array function used currently only with BLD multicast address

• updatePVA: Deletes the old PVA and calls initPVA again

• initPVA: Instantiates the BLD payload PVAccess. IT described the content of the BLD packet

• addBldChannelName: adds a name to a BLD channel. This replaces the channel key <bsakey> in BLD

• MonitorStatus: method that reads status variables from the firmware and updates PVs

• bsssCallback: BSSS built-in callback function

• bldCallback: BLD built-in callback function

• getServiceType: Return private variable serviceType

  
  

The BLD packet structure coming from the ATCA FPGA and the ones sent out to the BLD clients are described in these slides. The packet structure coming from the firmware contain a packet header, followed by the event's enabled channel data and finally by the severity mask. The firmware may send other event data appended as many times as necessary.

The BSSS firmware packet structure however are not described anywhere.