RE: AreaDetector Driver for device that sends back 3 synchronized frames

["Pearson, Matthew via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Evan,

 

I assume you’d be handling/saving each array separately? If so, one way to handle this is to use different Asyn addresses for the output NDArray callbacks. So you would have a single driver that gets the 3 images, and then output the RGB image NDArray on addr=0, the IR image NDArray on addr=1 and the depth image NDArrray on addr=2. Each NDArray type would use a different dims[] size and datatype. Then you can have 3 separate plugin chains to handle the NDArray processing, with the 1^st plugin in each chain listening to a different Asyn address.

 

Cheers,

Matt

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Daykin, Evan via Tech-talk
Sent: Monday, June 9, 2025 4:08 PM
To: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] AreaDetector Driver for device that sends back 3 synchronized frames

 

Hi, I am looking to create an AD Driver for Microsoft Kinect v2. The open-source device driver libfreenect2, uses a Synchronized multi-frame listener that awaits the receipt of an RGB image (1920x1080x3 int), an IR image (512x424 float), and

Hi,

 

I am looking to create an AD Driver for Microsoft Kinect v2. The open-source device driver libfreenect2, uses a Synchronized multi-frame listener that awaits the receipt of an RGB image (1920x1080x3 int), an IR image (512x424 float), and a depth image (512x424 float). I would like suggestions for the best way to handle this. My first thought is to have three separate ‘sub’-detector drivers and dole out each frame from the main driver according to its type. Are there any existing device support modules that do something similar?

 

Thanks!

-Evan