An EPICS areaDetector driver for cameras from FLIR (formerly Point Grey) using their Spinnaker SDK.
Home Page: https://areadetector.github.io/master/ADSpinnaker/ADSpinnaker.html
An EPICS areaDetector driver for cameras from FLIR using their Spinnaker SDK. These include GigE, 10GigE, and USB 3.0 cameras.
Beginning with R2-0 this driver derives from the ADGenICam base class.
Additional information:
Hi,
I'm using a FLIR Blackfly BFLY-PGE-50A2C-CS GigE camera with areadetector and ADSpinnaker on linux Ubuntu 18.04 and epics 7 and quite recent github versions of support modules, which mostly works fine. However, I am experiencing the following strange behavior:
Because this camera cannot set the frame rate independently of the exposure time, I have built a work around using its software trigger, with the idea to set it to software trigger and use a bo soft channel with periodic scan to write to the "TriggerSoftware" PV of the camera (I only need low frame rates for monitoring, but small exposure times). This functionality all works well, however, with the problem that whenever I have the bo record repeatedly trigger the "TriggerSoftware" PV, the memory consumption of the ioc process starts to continously increase with a rate of around 7 mByte/hour at 1s Scan interval (the rate scales with the trigger frequency, the example below has a trigger frequency of 0.5 seconds). This does not happen if I stop the scanning of the softchannel, but it is independent of whether the camera is actually triggered or not "TriggerMode=Off or On". No plugins apart from an Image plugin are loaded. When I stop the acquisition of the camera, the memory consumption drops to a baseline and stays there constant, but if I resume acquisition later, it resumes at a higher memory consumtion, as if it was running all the time:
The definition of the softchannel PV is the following:
record(bo,"$(P)trigger")
{
field(DESC,"Camera trigger")
field(VAL,1)
field(OUT,"$(P)cam1:TriggerSoftware PP MS")
field(SCAN,"1 second")
}
Is this a bug in ADSpinnaker or the Spinnaker SDK, or am I doing something silly here?
Best, Laurenz
My FLIR camera has been working well for a few week in self trigger mode "i.e. Trigger Mode=Off".
Today I tried the external trigger mode (line0) with a 50Hz TTL trigger pulses x 100 and file output turned on.
When I noticed error from IOC:
2020/08/22 19:07:01.924 ADSpinnaker::grabImage error GetImageStatus returned 9
I thought the file write must not be able to keep up with the external trigger rate.
I reverted back to internal trigger mode. The camera "Acquire Start" shows "Collecting" forever. Screen shot attached.
I restarted the computer, power cycled the camera. Problem persists.
I attached the camera to a different computer (Windows 10), using Spinview software from FLIR. It can reach good frame rate (~70 Hz Mono16). So I am confident the camera itself is still working fine.
Have you ever seen this problem before? Is there a way to clear up the error?
2020/08/22 19:07:01.924 ADSpinnaker::grabImage error GetImageStatus returned 9
issue moved from:
epics-extensions/medm#6
I am seeing ADSpinnaker IOCs fail after 1-3 days when running a USB camera at 163 frames/s.
The following is the output of procServ for 2 occurrences.
In this one the IOC completed booting on June 9 at 10:47 AM. On June 10 at 11:53 acquisition was started. 3 days later on June 13 we see a bunch of warnings that the scan tasks are running too slowly. There is then a "double free or corruption" error and the IOC crashes and automatically reboots.
Tue Jun 9 10:47:30 2020epics>
Tue Jun 9 10:47:30 2020epics> 2020/06/09 10:47:30.740 Param[BIN_X] GenICamFeature::write: node BinningHorizontal is not writable
Tue Jun 9 10:47:30 2020
Tue Jun 9 10:47:31 2020auto_settings.sav: 2874 of 2874 PV's connected
Tue Jun 9 10:47:31 2020
Tue Jun 9 10:47:32 2020epics>
Tue Jun 9 10:47:32 2020epics> 2020/06/10 11:52:47.397 ADSpinnaker::grabImage [PG1] ERROR: pData is NULL!
Wed Jun 10 11:53:02 20202020/06/10 11:53:02.024 Param[GC_FRAMERATE] GenICamFeature::write: node AcquisitionFrameRate is not writable
Wed Jun 10 11:53:02 2020
Sat Jun 13 10:31:27 2020
Sat Jun 13 10:31:27 2020dbScan warning from '.1 second' scan thread:
Sat Jun 13 10:31:27 2020 Scan processing averages 0.757 seconds (0.154 .. 1.276).
Sat Jun 13 10:31:27 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:31:27 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:32:21 2020
Sat Jun 13 10:32:21 2020dbScan warning from '.1 second' scan thread:
Sat Jun 13 10:32:21 2020 Scan processing averages 0.492 seconds (0.185 .. 0.995).
Sat Jun 13 10:32:21 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:32:21 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:32:26 2020
Sat Jun 13 10:32:26 2020dbScan warning from '.2 second' scan thread:
Sat Jun 13 10:32:26 2020 Scan processing averages 0.835 seconds (0.334 .. 1.583).
Sat Jun 13 10:32:26 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:32:26 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:32:50 2020
Sat Jun 13 10:32:50 2020dbScan warning from '.1 second' scan thread:
Sat Jun 13 10:32:50 2020 Scan processing averages 0.563 seconds (0.125 .. 0.997).
Sat Jun 13 10:32:50 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:32:50 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:32:57 2020
Sat Jun 13 10:32:57 2020dbScan warning from '.2 second' scan thread:
Sat Jun 13 10:32:57 2020 Scan processing averages 0.493 seconds (0.242 .. 0.754).
Sat Jun 13 10:32:57 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:32:57 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:33:32 2020
Sat Jun 13 10:33:32 2020dbScan warning from '.1 second' scan thread:
Sat Jun 13 10:33:32 2020 Scan processing averages 0.772 seconds (0.343 .. 1.403).
Sat Jun 13 10:33:32 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:33:32 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:33:33 2020
Sat Jun 13 10:33:33 2020dbScan warning from '.2 second' scan thread:
Sat Jun 13 10:33:33 2020 Scan processing averages 0.772 seconds (0.293 .. 1.488).
Sat Jun 13 10:33:33 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:33:33 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:34:15 2020
Sat Jun 13 10:34:15 2020dbScan warning from '.2 second' scan thread:
Sat Jun 13 10:34:15 2020 Scan processing averages 0.487 seconds (0.211 .. 0.824).
Sat Jun 13 10:34:15 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:34:15 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:34:16 2020
Sat Jun 13 10:34:16 2020dbScan warning from '.1 second' scan thread:
Sat Jun 13 10:34:16 2020 Scan processing averages 0.549 seconds (0.165 .. 0.874).
Sat Jun 13 10:34:16 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:34:16 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:34:22 2020
Sat Jun 13 10:34:22 2020dbScan warning from '.5 second' scan thread:
Sat Jun 13 10:34:22 2020 Scan processing averages 0.885 seconds (0.603 .. 1.599).
Sat Jun 13 10:34:22 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:34:22 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:34:55 2020
Sat Jun 13 10:34:55 2020dbScan warning from '.1 second' scan thread:
Sat Jun 13 10:34:55 2020 Scan processing averages 0.593 seconds (0.185 .. 1.282).
Sat Jun 13 10:34:55 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:34:55 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:35:03 2020
Sat Jun 13 10:35:03 2020dbScan warning from '.2 second' scan thread:
Sat Jun 13 10:35:03 2020 Scan processing averages 0.646 seconds (0.206 .. 1.197).
Sat Jun 13 10:35:03 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:35:03 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:35:08 2020
Sat Jun 13 10:35:08 2020dbScan warning from '.5 second' scan thread:
Sat Jun 13 10:35:08 2020 Scan processing averages 1.019 seconds (0.583 .. 1.395).
Sat Jun 13 10:35:08 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:35:08 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:35:14 2020
Sat Jun 13 10:35:14 2020dbScan warning from '.1 second' scan thread:
Sat Jun 13 10:35:14 2020 Scan processing averages 0.592 seconds (0.108 .. 1.205).
Sat Jun 13 10:35:14 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:35:14 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:35:23 2020
Sat Jun 13 10:35:23 2020dbScan warning from '.2 second' scan thread:
Sat Jun 13 10:35:23 2020 Scan processing averages 0.853 seconds (0.228 .. 1.648).
Sat Jun 13 10:35:23 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:35:23 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:35:26 2020
Sat Jun 13 10:35:26 2020dbScan warning from '.5 second' scan thread:
Sat Jun 13 10:35:26 2020 Scan processing averages 1.061 seconds (0.504 .. 1.491).
Sat Jun 13 10:35:26 2020 Over-runs have now happened 10 times in a row.
Sat Jun 13 10:35:26 2020 To fix this, move some records to a slower scan rate.
Sat Jun 13 10:35:32 2020double free or corruption (out)
Sat Jun 13 10:41:03 2020/corvette/home/epics/support/CARS/iocBoot/ioc13ida_pg1/start_epics: line 4: 16762 Aborted (core dumped) /corvette/home/epics/support/areaDetector/ADSpinnaker/iocs/spinnakerIOC/bin/linux-x86_64-centos8/spinnakerApp st.cmd
On June 16 the same scan tasks errors happened. I think the IOC may have been restarted by the user in this case, rather than crashing. But something is still going wrong.
Sat Jun 13 10:41:09 2020# These PVs are in auto_settings.req but don't have PINI=Yes
Sat Jun 13 10:41:09 2020dbpf("13IDAPG1:cam1:GC_OnBoaColProEna.PROC", "1")
Sat Jun 13 10:41:09 2020DBF_UCHAR: 1 = 0x1
Sat Jun 13 10:41:09 2020dbpf("13IDAPG1:cam1:GC_VideoMode.PROC", "1")
Sat Jun 13 10:41:09 2020DBF_UCHAR: 1 = 0x1
Sat Jun 13 10:41:09 2020dbpf("13IDAPG1:cam1:GC_DevLinThrLimit.PROC", "1")
Sat Jun 13 10:41:09 2020DBF_UCHAR: 1 = 0x1
Sat Jun 13 10:41:09 2020epics> 2020/06/13 10:41:10.025 Param[BIN_X] GenICamFeature::write: node BinningHorizontal is not writable
Sat Jun 13 10:41:10 2020
Sat Jun 13 10:41:10 2020auto_settings.sav: 2875 of 2875 PV's connected
Mon Jun 15 10:39:59 20202020/06/15 10:39:59.692 ADSpinnaker::grabImage [PG1] ERROR: pData is NULL!
Tue Jun 16 11:21:30 2020
Tue Jun 16 11:21:30 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:21:30 2020 Scan processing averages 0.536 seconds (0.316 .. 0.881).
Tue Jun 16 11:21:30 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:21:30 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:21:32 2020
Tue Jun 16 11:21:32 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:21:32 2020 Scan processing averages 0.491 seconds (0.266 .. 0.831).
Tue Jun 16 11:21:32 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:21:32 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:21:46 2020
Tue Jun 16 11:21:46 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:21:46 2020 Scan processing averages 0.650 seconds (0.272 .. 1.153).
Tue Jun 16 11:21:46 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:21:46 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:21:47 2020
Tue Jun 16 11:21:47 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:21:47 2020 Scan processing averages 0.764 seconds (0.504 .. 1.203).
Tue Jun 16 11:21:47 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:21:47 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:21:47 2020
Tue Jun 16 11:21:47 2020dbScan warning from '.5 second' scan thread:
Tue Jun 16 11:21:47 2020 Scan processing averages 0.874 seconds (0.550 .. 1.609).
Tue Jun 16 11:21:47 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:21:47 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:22:07 2020
Tue Jun 16 11:22:07 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:22:07 2020 Scan processing averages 0.530 seconds (0.148 .. 0.734).
Tue Jun 16 11:22:07 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:22:07 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:22:21 2020
Tue Jun 16 11:22:21 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:22:21 2020 Scan processing averages 0.523 seconds (0.237 .. 1.008).
Tue Jun 16 11:22:21 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:22:21 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:22:26 2020
Tue Jun 16 11:22:26 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:22:26 2020 Scan processing averages 0.600 seconds (0.233 .. 1.410).
Tue Jun 16 11:22:26 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:22:26 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:22:53 2020
Tue Jun 16 11:22:53 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:22:53 2020 Scan processing averages 1.052 seconds (0.383 .. 1.800).
Tue Jun 16 11:22:53 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:22:53 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:22:53 2020
Tue Jun 16 11:22:53 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:22:53 2020 Scan processing averages 1.090 seconds (0.317 .. 1.850).
Tue Jun 16 11:22:53 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:22:53 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:22:57 2020
Tue Jun 16 11:22:57 2020dbScan warning from '.5 second' scan thread:
Tue Jun 16 11:22:57 2020 Scan processing averages 1.359 seconds (0.529 .. 3.146).
Tue Jun 16 11:22:57 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:22:57 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:23:24 2020
Tue Jun 16 11:23:24 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:23:24 2020 Scan processing averages 0.719 seconds (0.170 .. 1.880).
Tue Jun 16 11:23:24 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:23:24 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:23:29 2020
Tue Jun 16 11:23:29 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:23:29 2020 Scan processing averages 0.778 seconds (0.345 .. 1.239).
Tue Jun 16 11:23:29 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:23:29 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:23:54 2020
Tue Jun 16 11:23:54 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:23:54 2020 Scan processing averages 0.649 seconds (0.201 .. 1.800).
Tue Jun 16 11:23:54 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:23:54 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:24:07 2020
Tue Jun 16 11:24:07 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:24:07 2020 Scan processing averages 0.544 seconds (0.215 .. 1.001).
Tue Jun 16 11:24:07 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:24:07 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:24:36 2020
Tue Jun 16 11:24:36 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:24:36 2020 Scan processing averages 1.222 seconds (0.456 .. 1.580).
Tue Jun 16 11:24:36 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:24:36 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:24:36 2020
Tue Jun 16 11:24:36 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:24:36 2020 Scan processing averages 1.274 seconds (0.150 .. 2.574).
Tue Jun 16 11:24:36 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:24:36 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:24:37 2020
Tue Jun 16 11:24:37 2020dbScan warning from '.5 second' scan thread:
Tue Jun 16 11:24:37 2020 Scan processing averages 1.424 seconds (0.717 .. 2.374).
Tue Jun 16 11:24:37 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:24:37 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:24:49 2020
Tue Jun 16 11:24:49 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:24:49 2020 Scan processing averages 0.377 seconds (0.211 .. 0.602).
Tue Jun 16 11:24:49 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:24:49 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:25:17 2020
Tue Jun 16 11:25:17 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:25:17 2020 Scan processing averages 0.940 seconds (0.437 .. 2.260).
Tue Jun 16 11:25:17 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:25:17 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:25:21 2020
Tue Jun 16 11:25:21 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:25:21 2020 Scan processing averages 0.980 seconds (0.487 .. 2.310).
Tue Jun 16 11:25:21 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:25:21 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:25:21 2020
Tue Jun 16 11:25:21 2020dbScan warning from '.5 second' scan thread:
Tue Jun 16 11:25:21 2020 Scan processing averages 1.303 seconds (0.881 .. 1.734).
Tue Jun 16 11:25:21 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:25:21 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:25:35 2020
Tue Jun 16 11:25:35 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:25:35 2020 Scan processing averages 0.972 seconds (0.373 .. 1.899).
Tue Jun 16 11:25:35 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:25:35 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:25:35 2020
Tue Jun 16 11:25:35 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:25:35 2020 Scan processing averages 1.025 seconds (0.423 .. 1.949).
Tue Jun 16 11:25:35 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:25:35 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:25:57 2020
Tue Jun 16 11:25:57 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:25:57 2020 Scan processing averages 0.752 seconds (0.304 .. 1.125).
Tue Jun 16 11:25:57 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:25:57 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:25:57 2020
Tue Jun 16 11:25:57 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:25:57 2020 Scan processing averages 0.791 seconds (0.386 .. 1.175).
Tue Jun 16 11:25:57 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:25:57 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:26:06 2020
Tue Jun 16 11:26:06 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:26:06 2020 Scan processing averages 0.396 seconds (0.194 .. 0.891).
Tue Jun 16 11:26:06 2020 Over-runs have now happened 11 times in a row.
Tue Jun 16 11:26:06 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:26:23 2020
Tue Jun 16 11:26:23 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:26:23 2020 Scan processing averages 0.614 seconds (0.193 .. 1.286).
Tue Jun 16 11:26:23 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:26:23 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:26:39 2020
Tue Jun 16 11:26:39 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:26:39 2020 Scan processing averages 0.331 seconds (0.151 .. 0.902).
Tue Jun 16 11:26:39 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:26:39 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:26:50 2020
Tue Jun 16 11:26:50 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:26:50 2020 Scan processing averages 0.351 seconds (0.140 .. 0.677).
Tue Jun 16 11:26:50 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:26:50 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:27:05 2020
Tue Jun 16 11:27:05 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:27:05 2020 Scan processing averages 0.464 seconds (0.112 .. 0.869).
Tue Jun 16 11:27:05 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:27:05 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:27:06 2020
Tue Jun 16 11:27:06 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:27:06 2020 Scan processing averages 0.456 seconds (0.314 .. 0.683).
Tue Jun 16 11:27:06 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:27:06 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:27:20 2020
Tue Jun 16 11:27:20 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:27:20 2020 Scan processing averages 0.585 seconds (0.143 .. 1.159).
Tue Jun 16 11:27:20 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:27:20 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:27:22 2020
Tue Jun 16 11:27:22 2020dbScan warning from '.5 second' scan thread:
Tue Jun 16 11:27:22 2020 Scan processing averages 0.984 seconds (0.603 .. 1.690).
Tue Jun 16 11:27:22 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:27:22 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:27:23 2020
Tue Jun 16 11:27:23 2020dbScan warning from '.2 second' scan thread:
Tue Jun 16 11:27:23 2020 Scan processing averages 0.588 seconds (0.243 .. 1.110).
Tue Jun 16 11:27:23 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:27:23 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:27:39 2020
Tue Jun 16 11:27:39 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:27:39 2020 Scan processing averages 0.303 seconds (0.101 .. 0.541).
Tue Jun 16 11:27:39 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:27:39 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:27:54 2020
Tue Jun 16 11:27:54 2020dbScan warning from '.1 second' scan thread:
Tue Jun 16 11:27:54 2020 Scan processing averages 0.414 seconds (0.100 .. 0.794).
Tue Jun 16 11:27:54 2020 Over-runs have now happened 10 times in a row.
Tue Jun 16 11:27:54 2020 To fix this, move some records to a slower scan rate.
Tue Jun 16 11:28:17 2020/corvette/home/epics/support/CARS/iocBoot/ioc13ida_pg1/start_epics: line 4: 18108 Killed /corvette/home/epics/support/areaDetector/ADSpinnaker/iocs/spinnakerIOC/bin/linux-x86_64-centos8/spinnakerApp st.cmd
Tue Jun 16 11:28:19 2020
Tue Jun 16 11:28:20 2020@@@ @@@ @@@ @@@ @@@
Tue Jun 16 11:28:20 2020@@@ Received a sigChild for process 18091. Normal exit status = 137
Tue Jun 16 11:28:20 2020@@@ Current time: Tue Jun 16 11:28:20 2020
Tue Jun 16 11:28:20 2020@@@ Child process is shutting down, a new one will be restarted shortly
Tue Jun 16 11:28:20 2020@@@ ^R or ^X restarts the child, ^Q quits the server
Tue Jun 16 11:28:20 2020@@@ Restarting child "13IDA_PG1_IOC"
Tue Jun 16 11:28:20 2020@@@ (as /corvette/home/epics/support/CARS/iocBoot/ioc13ida_pg1/start_epics)
Tue Jun 16 11:28:21 2020@@@ The PID of new child "13IDA_PG1_IOC" is: 10523
Tue Jun 16 11:28:21 2020@@@ @@@ @@@ @@@ @@@
Tue Jun 16 11:28:22 2020< envPaths
Tue Jun 16 11:28:22 2020epicsEnvSet("IOC","ioc13ida_pg1")
Tue Jun 16 11:28:22 2020epicsEnvSet("TOP","/corvette/home/epics/support/CARS")
Tue Jun 16 11:28:22 2020epicsEnvSet("SUPPORT","/corvette/home/epics/support")
The only versions available is V2.0 and V1.29 from FLIR:
https://meta.box.lenovo.com/v/link/view/a1995795ffba47dbbe45771477319cc3
Is there any plan to update the drive to work with the newer version SDK?
Would you happen to have an older version archived?
As shown in MEDM screen attached, RBV value for cam1:NumImages is minimum 2, even when when the entered value for NumImages is 1.
The behavior for ImageMode in Single and Multiple is different when NumImages=1.
The camera will acquire 1 image in Single, or 2 images in Multiple mode in this case.
Is this behavior correct?
I've been using ADAravis for my FLIR camera.
Recently, I saw ADSpinnaker has been upgraded to 3-4 (from my last attempt with 3-1).
Does the latest ADSpinnaker IOC offer performance advantage over ADAravis?
The driver sometimes crashes when acquisition is stopped. This has been observed on Windows with a USB camera in Continuous mode when setting Acquire to 0 from the OPI screen. It may happen in other circumstances as well.
ADSpinnaker R3-4 added more stream statistics like ReceivedFrameCount and ResendRequestedPacketCount. However, these parameters are not available on all cameras, e.g. USB vs GigE. When a parameter is not supported the SDK throws an exception and the driver prints an error message. This leads to a constant stream of error messages on some cameras when acquiring.
After building successfully, I tried to run the IOC (ADSpinnaker/iocs/spinnakerIOC/bin/linux-x86_64/spinnakerApp) but encounter the error of missing libGenApi_gcc11_v3_0.so. This lib file is in spinnakerSupport/os/linux-x86_64 but somehow there is no EPICS variable pointing to it. I ended up making a symlink from spinnakerSupport/os/linux-x86_64 to /usr/lib/ to run the IOC.
I think I missed something in the installation/configuration. What EPICS variable should point to the support libraries directory?
Thank you!
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.