EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024>  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024> 
<== Date ==> <== Thread ==>
Subject: RE: ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: John Dobbins <john.dobbins at cornell.edu>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 6 Jun 2024 17:40:37 +0000

Hi John,

 

This problem is mentioned in the release notes for ADSpinnaker R3-5:

 

    • There is a known problem on CentOS 9. The maximum number of driver buffers that Spinnaker will allow is 3. This is not a problem on Ubuntu 22 where a value over 200 is allowed on my system. Even with the limit of 3 I am able to stream the full 163 frame/s on a GS3-U3-23S6M camera. FLIR is aware of the issue.

I reported the problem to FLIR in February, with the last update and demonstration of the problem in the attached message.  I was promised that they would try to reproduce it, but I have not heard anything.  I sent them a reminder today.

 

  • After configuring USB-FS memory I now have the camera running.

 

Aha!  Thanks for finding that.  Did you configure it as described here?

https://areadetector.github.io/areaDetector/ADGenICam/ADGenICam.html#linux-usb-and-gige-system-settings

 

Can you tell me the command you used so I can check and update that documentation?  I want to make sure it works on CentOS 9 as well.

 

I probably neglected to do that, which is why I thought there was a bug.

 

Thanks,

Mark

 

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of John Dobbins via Tech-talk
Sent: Thursday, June 6, 2024 10:56 AM
To: tech-talk at aps.anl.gov
Subject: ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming

 

I have built, base-7.0.6,  areaDetectorR3-13 with ADSpinnaker master on Alma 9. I am using a FLIR BlackflyS 161S7M USB camera. This is large, 5320x3032 pixels.

 

The camera is detected but I get a "Not enough available memory to allocate buffers for streaming" error.

 

In ADSpinnakerConfig I have set numSPBuffer to minimum  = 10 (?)

 

# ADSpinnakerConfig(const char *portName, const char *cameraId, int numSPBuffers,

#                   size_t maxMemory, int priority, int stackSize)

ADSpinnakerConfig("SP1", 22671882, 10, 0, 0,0)

 

The host computer has 16G, 13.7 G free,

 

Ideas?

 

John Dobbins

 

Research Support Specialist

Cornell High Energy Synchrotron Source

Cornell University

 

www.chess.cornell.edu

 

 

 

 

 

[root@lnx615 iocSpinnaker]# ../../bin/linux-x86_64/spinnakerApp st.cmd.BlackflyS_161S7M

< envPaths

epicsEnvSet("IOC","iocSpinnaker")

epicsEnvSet("TOP","/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADSpinnaker/iocs/spinnakerIOC")

epicsEnvSet("ADSPINNAKER","/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADSpinnaker/iocs/spinnakerIOC/../..")

epicsEnvSet("SUPPORT","/nfs/chess/epics/det/support_flir")

epicsEnvSet("ASYN","/nfs/chess/epics/det/support_flir/asyn-R4-45")

epicsEnvSet("AREA_DETECTOR","/nfs/chess/epics/det/support_flir/areaDetector-R3-13")

epicsEnvSet("ADSUPPORT","/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADSupport")

epicsEnvSet("ADCORE","/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADCore")

epicsEnvSet("AUTOSAVE","/nfs/chess/epics/det/support_flir/autosave-R5-11")

epicsEnvSet("BUSY","/nfs/chess/epics/det/support_flir/busy-R1-7-4")

epicsEnvSet("CALC","/nfs/chess/epics/det/support_flir/calc-R3-7-5")

epicsEnvSet("SNCSEQ","/nfs/chess/epics/det/support_flir/seq-R2-2-9")

epicsEnvSet("SSCAN","/nfs/chess/epics/det/support_flir/sscan-R2-11-5")

epicsEnvSet("DEVIOCSTATS","/nfs/chess/epics/det/support_flir/iocStats-3-1-16")

epicsEnvSet("EPICS_BASE","/nfs/chess/epics/det/base-7.0.6")

epicsEnvSet("ADGENICAM","/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADGenICam")

errlogInit(20000)

dbLoadDatabase("/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADSpinnaker/iocs/spinnakerIOC/dbd/spinnakerApp.dbd")

spinnakerApp_registerRecordDeviceDriver(pdbbase)

# Use this line for a specific camera by serial number, in this case a BlackFlyS GigE

epicsEnvSet("CAMERA_ID", "22671882")

epicsEnvSet("GENICAM_DB_FILE", "/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADGenICam/db/FLIR_BFS_U3_161S7M.template")

< st.cmd.base

# Prefix for all records

epicsEnvSet("PREFIX", "13SP1:")

# The port name for the detector

epicsEnvSet("PORT",   "SP1")

# Really large queue so we can stream to disk at full camera speed

epicsEnvSet("QSIZE",  "2000")  

# The maximim image width; used for row profiles in the NDPluginStats plugin

epicsEnvSet("XSIZE",  "2048")

# The maximim image height; used for column profiles in the NDPluginStats plugin

epicsEnvSet("YSIZE",  "2048")

# The maximum number of time series points in the NDPluginStats plugin

epicsEnvSet("NCHANS", "2048")

# The maximum number of frames buffered in the NDPluginCircularBuff plugin

epicsEnvSet("CBUFFS", "500")

# The search path for database files

# This is for Windows

epicsEnvSet("EPICS_DB_INCLUDE_PATH", "/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADCore/db;/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADGenICam/db;/nfs/chess/epics/det/support_flir/areaDetector-R3-13/ADSpinnaker/iocs/spinnakerIOC/../../db")

# This is for Linux

#epicsEnvSet("EPICS_DB_INCLUDE_PATH", "$(ADCORE)/db:$(ADGENICAM)/db:$(ADSPINNAKER)/db")

# Define NELEMENTS to be enough for a 5320x3032 (color) image

epicsEnvSet("NELEMENTS", "16130240")

# ADSpinnakerConfig(const char *portName, const char *cameraId, int numSPBuffers,

#                   size_t maxMemory, int priority, int stackSize)

ADSpinnakerConfig("SP1", 22671882, 10, 0, 0,0)

2024/06/06 11:46:16.990 ADSpinnaker::connectCamera exception Spinnaker: Not enough available memory to allocate buffers for streaming. [-1016]

2024/06/06 11:46:16.990 ADSpinnaker:ADSpinnaker:  camera connection failed (3)

 

Number of cameras detected: 1

Camera 0

Device Vendor Name   (DeviceVendorName):FLIR

Device Model Name (DeviceModelName):Blackfly S BFS-U3-161S7M

Device Serial Number (DeviceSerialNumber):22671882

Device Version (DeviceVersion):2210.0.657.0

Device Type (DeviceType):USB3Vision

 

 

 

 

 

--- Begin Message ---
Subject: RE: Issue with buffer size on Linux SDK 4.0 [Incident: 240114-000083]
From: Mark Rivers <rivers at cars.uchicago.edu>
To: Teledyne FLIR Customer Support <flir at mailft.custhelp.com>
Date: Tue, 13 Feb 2024 23:52:21 +0000

Hi William,

 

I have some more information on this problem that may be useful to you.

 

I ran the BufferHandling program on a CentOS 9 system testing 2 different cameras:

 

BFS-PGE-50S5C-C

This camera works fine, I see the following output from BufferHandling:

Default Buffer Handling Mode: Oldest First

Default Buffer Count: 10

Maximum Buffer Count: 13793

Buffer count now set to: 6

 

I have attached the complete output as BufferHandling_GigE.txt

 

GS3-U3-23S6M-C

This camera does not work, I see the following output from BufferHandling:

Default Buffer Handling Mode: Oldest First

Default Buffer Count: 0

Maximum Buffer Count: 3

Error: Spinnaker: GenICam::OutOfRangeException= Value = 6 must be equal or smaller than Max = 3. : OutOfRangeException thrown in node 'StreamBufferCountManual' while calling 'StreamBufferCountManual.SetValue()' (file 'IntegerT.h', line 79) [-2002]

 

I have attached the complete output as BufferHandling_USB.txt

 

I am not sure why the 2 cameras behave differently, but perhaps it is because one is USB and the other is GigE?

 

Thanks,

Mark

 

 

 

From: Teledyne FLIR Customer Support <flir at mailft.custhelp.com>
Sent: Friday, February 9, 2024 7:16 PM
To: Mark Rivers <rivers at cars.uchicago.edu>
Subject: Issue with buffer size on Linux SDK 4.0 [Incident: 240114-000083]

 

Image

Your support ticket has been updated, details are below.  To access your question from our support site, click here.

Please reply within 7 days to keep this ticket active.

 

Response By Email (William Gallego) (10/02/2024 02.16 AM)

Hi Mark,

 

I have an internal ticket raised regarding this issue; can you confirm a timeline on when you need this issue resolved?



Best regards,

William Gallego
Support Engineer
Teledyne FLIR

---------------------------------------
Find all your camera resources in one place at https://www.flir.com/support-center/iis/machine-vision/knowledge-base/mv-getting-started/
Create RMAs at https://www.flir.com/contact/mv-service
Create technical support tickets at https://flir.custhelp.com/app/ask
Check out our new forum to find or post your questions - https://teledynevisionsolutions.zendesk.com/hc/en-us/community/topics

Customer By CSS Email (Mark Rivers) (09/02/2024 04.04 PM)

Hi William,

 

Is there any update on this issue?

 

Thanks,

Mark

 

 

 

Response By Email (William Gallego) (23/01/2024 02.26 AM)

HI Mark,

 

I'm currently reviewing this on my end, to confirm the issue; once I have an update, i'll make sure to let you know.



Best regards,

William Gallego
Support Engineer
Teledyne FLIR

---------------------------------------
Find all your camera resources in one place at https://www.flir.com/support-center/iis/machine-vision/knowledge-base/mv-getting-started/
Create RMAs at https://www.flir.com/contact/mv-service
Create technical support tickets at https://flir.custhelp.com/app/ask
Check out our new forum to find or post your questions - https://teledynevisionsolutions.zendesk.com/hc/en-us/community/topics

Customer By CSS Email (Mark Rivers) (19/01/2024 10.42 PM)

Hi William,

 

I ran some tests on Ubuntu22 with the latest SDK, and on CentOS9 with several versions of the SDK.  I ran the BufferHandling example that comes with the SDK.

 

Here is what I found.

OS

SDK

Maximum buffer count

Ubuntu 22

4.0.0.116

204

CentOS 9

4.0.0.116

3

CentOS 9

3.1.0.79

3

CentOS 9

2.4.0.143

2172

 

So in SDK 4.0.0.116 and 3.1.0.79 the maximum buffer count is limited to 3 on CentOS 9.  In the old 2.4.0.143 it was much larger.  On that old version I changed numBuffers in BufferHandling.cpp to 6, and it ran successfully.  That shows that it was not actually limited to 3.

 

We use a lot of your cameras at the DOE National Laboratories in the US.  These almost all have standardized on Redhat or CentOS.  I really hope you can make the SDK work correctly on this OS.

 

I have attached the output of the BufferHandling program for each of the 4 tests above.

 

Thanks,

Mark

 

 

From: Mark Rivers
Sent: Friday, January 19, 2024 10:36 AM
To: Teledyne FLIR Customer Support <flir at mailft.custhelp.com>
Subject: RE: Issue with buffer size on Linux SDK 4.0 [Incident: 240114-000083]

 

Hi William,

 

  • Can you confirm what version of Linux you are testing with, and if its gone through all of its standard updates?  I'd like to reproduce the issue on my end.

I am testing on CentOS 9 Stream.  It has all the standard updates.  I understand that CentOS 9 is not officially supported, but I have been using CentOS 8 and 9 without issues before this.

 

I can also test on Ubuntu 22 if you think that would be useful.

 

Mark

 

 

From: Teledyne FLIR Customer Support <flir at mailft.custhelp.com>
Sent: Tuesday, January 16, 2024 7:22 PM
To: Mark Rivers <rivers at cars.uchicago.edu>
Subject: Issue with buffer size on Linux SDK 4.0 [Incident: 240114-000083]

 

Customer By CSS Email (Mark Rivers) (19/01/2024 05.36 PM)

Hi William,

 

  • Can you confirm what version of Linux you are testing with, and if its gone through all of its standard updates?  I'd like to reproduce the issue on my end.

I am testing on CentOS 9 Stream.  It has all the standard updates.  I understand that CentOS 9 is not officially supported, but I have been using CentOS 8 and 9 without issues before this.

 

I can also test on Ubuntu 22 if you think that would be useful.

 

Mark

 

 

Issue with buffer size on Linux SDK 4.0 [Incident: 240114-000083]

 

 

Response By Email (William Gallego) (17/01/2024 02.22 AM)

Hi Mark,

 

William here. Can you confirm what version of Linux you are testing with, and if its gone through all of its standard updates?  I'd like to reproduce the issue on my end.

Best regards,

William Gallego
Support Engineer
Teledyne FLIR

---------------------------------------
Find all your camera resources in one place at https://www.flir.com/support-center/iis/machine-vision/knowledge-base/mv-getting-started/
Create RMAs at https://www.flir.com/contact/mv-service
Create technical support tickets at https://flir.custhelp.com/app/ask
Check out our new forum to find or post your questions - https://teledynevisionsolutions.zendesk.com/hc/en-us/community/topics

Response By Email (William Gallego) (16/01/2024 02.32 AM)

Hello Mark,

 

Thank you for contacting Technical Support.

 

We have received your ticket, but unfortunately we could not respond to it today.

Your request has been accepted, and we will provide you with a solution as soon as we can.

 

Thank you,

Teledyne FLIR Machine Vision Technical Support

 


---------------------------------------
Find all your camera resources in one place at https://www.flir.com/support-center/iis/machine-vision/knowledge-base/mv-getting-started/
Create RMAs at https://www.flir.com/contact/mv-service
Create technical support tickets at https://flir.custhelp.com/app/ask
Check out our new forum to find or post your questions - https://teledynevisionsolutions.zendesk.com/hc/en-us/community/topics

Customer By CSS Email (Mark Rivers) (14/01/2024 11.01 PM)

Folks,

 

I installed the latest Spinnaker 4.0 SDK for Linux.  I am having one problem.  When I try to set the StreamBufferCountManual to any value greater than 3 I get an exception that the maximum value is 3.  I can set it to 100 on Windows in SDK 4.0, and I used to be able to set it to 100 on Linux in earlier SDK versions.  If I try to set it to 4 I get the following exception:

 

2024/01/14 15:57:26.813 ADSpinnaker::connectCamera exception Spinnaker: GenICam::OutOfRangeException= Value = 4 must be equal or smaller than Max = 3. : OutOfRangeException thrown in node 'StreamBufferCountManual' while calling 'StreamBufferCountManual.SetValue()' (file 'IntegerT.h', line 79) [-2002]

 

I have seen this error before on Windows systems with very little RAM.  However, this Linux system has 256GB of RAM, so that cannot be the problem.

 

Thanks,

Mark

 

Question Reference # 240114-000083

·  Date Created: 14/01/2024 11.01 PM

·  Date Last Updated: 10/02/2024 02.16 AM

·  Status: Response sent

[---002:005537:09481---] 

Application build date: Feb 13 2024 17:01:20

Number of cameras detected: 2


Running example for camera 0...

*** DEVICE INFORMATION ***

DeviceID : 2CDDA36EDAA7
DeviceSerialNumber : 24042151
DeviceUserID : 
DeviceVendorName : FLIR
DeviceModelName : Blackfly S BFS-PGE-50S5C
DeviceVersion : 2103.0.340.0
DeviceBootloaderVersion : Node not readable
DeviceType : GigEVision
DeviceDisplayName : FLIR
DeviceAccessStatus : OpenReadOnly
DeviceLinkSpeed : 1000
DeviceDriverVersion : none : 0.0.0.0
DeviceIsUpdater : 0
GenICamXMLLocation : Device
GenICamXMLPath : 
GUIXMLLocation : Device
GUIXMLPath : Input.xml
GevCCP : OpenAccess
GevDeviceMACAddress : 0x2cdda36edaa7
GevDeviceIPAddress : 0xa436a060
GevDeviceSubnetMask : 0xffffff00
GevDeviceGateway : 0xa436a001
GevVersionMajor : 1
GevVersionMinor : 2
GevDeviceModeIsBigEndian : 1
GevDeviceReadAndWriteTimeout : 200000
GevDeviceMaximumRetryCount : 3
GevDevicePort : 0
GevDeviceDiscoverMaximumPacketSize : Node not readable
GevDeviceMaximumPacketSize : 1440
GevDeviceIsWrongSubnet : 0
GevDeviceAutoForceIP : 0
GevDeviceForceIP : 0
GevDeviceForceIPAddress : 0
GevDeviceForceSubnetMask : 0
GevDeviceForceGateway : 0

*** CONFIGURING TRIGGER ***

Trigger mode enabled...
Trigger source set to software...

*** IMAGE ACQUISITION ***

Acquisition mode set to continuous...
Pixel format set to EnumEntry_PixelFormat_Mono8
Device serial number retrieved as 24042151...
Stream Buffer Count Mode set to manual...

Default Buffer Handling Mode: Oldest First
Default Buffer Count: 10
Maximum Buffer Count: 13793
Buffer count now set to: 6

Camera will be triggered 10 times in a row, followed by 10 image retrieval attempts

Note - Buffer behaviour is different for USB3 and GigE cameras
     - USB3 cameras buffer images internally if no host buffers are available
     - Once the stream buffer is released, the USB3 camera will fill that buffer
     - GigE cameras do not buffer images
     - In TeledyneGigEVision stream mode an extra buffer will be reserved for trashing


*** Buffer Handling Mode has been set to Newest First ***

Camera triggered 10 times

Retrieving images from library until no image data is returned (errors out)
GetNextImage() #1, Frame ID: 6, Image saved at NewestFirst-24042151-1.jpg
GetNextImage() #2, Frame ID: 5, Image saved at NewestFirst-24042151-2.jpg
GetNextImage() #3, Frame ID: 4, Image saved at NewestFirst-24042151-3.jpg
GetNextImage() #4, Frame ID: 3, Image saved at NewestFirst-24042151-4.jpg
GetNextImage() #5, Frame ID: 2, Image saved at NewestFirst-24042151-5.jpg
GetNextImage() #6, Frame ID: 1, Image saved at NewestFirst-24042151-6.jpg
Error: Spinnaker: Failed waiting for EventData on NEW_BUFFER_DATA event. [-1011]


EXPECTED: error getting image # 7 with handling mode set to NewestFirst or OldestFirst in GigE Streaming


*** Buffer Handling Mode has been set to Oldest First ***

Camera triggered 10 times

Retrieving images from library until no image data is returned (errors out)
GetNextImage() #1, Frame ID: 1, Image saved at OldestFirst-24042151-1.jpg
GetNextImage() #2, Frame ID: 2, Image saved at OldestFirst-24042151-2.jpg
GetNextImage() #3, Frame ID: 3, Image saved at OldestFirst-24042151-3.jpg
GetNextImage() #4, Frame ID: 4, Image saved at OldestFirst-24042151-4.jpg
GetNextImage() #5, Frame ID: 5, Image saved at OldestFirst-24042151-5.jpg
GetNextImage() #6, Frame ID: 6, Image saved at OldestFirst-24042151-6.jpg
Error: Spinnaker: Failed waiting for EventData on NEW_BUFFER_DATA event. [-1011]


EXPECTED: error getting image # 7 with handling mode set to NewestFirst or OldestFirst in GigE Streaming


*** Buffer Handling Mode has been set to Newest Only ***

Camera triggered 10 times

Retrieving images from library until no image data is returned (errors out)
GetNextImage() #1, Frame ID: 10, Image saved at NewestOnly-24042151-1.jpg
Error: Spinnaker: Failed waiting for EventData on NEW_BUFFER_DATA event. [-1011]


EXPECTED: error occur when getting image #2 with handling mode set to NewestOnly


*** Buffer Handling Mode has been set to Oldest First Overwrite ***

Camera triggered 10 times

Retrieving images from library until no image data is returned (errors out)
GetNextImage() #1, Frame ID: 7, Image saved at OldestFirstOverwrite-24042151-1.jpg
GetNextImage() #2, Frame ID: 8, Image saved at OldestFirstOverwrite-24042151-2.jpg
GetNextImage() #3, Frame ID: 9, Image saved at OldestFirstOverwrite-24042151-3.jpg
GetNextImage() #4, Frame ID: 10, Image saved at OldestFirstOverwrite-24042151-4.jpg
Error: Spinnaker: Failed waiting for EventData on NEW_BUFFER_DATA event. [-1011]


EXPECTED: error occur when getting image #5 with handling mode set to OldestFirstOverwrite


Trigger mode disabled...

Camera 0 example complete...


Running example for camera 1...

*** DEVICE INFORMATION ***

DeviceID : USB\VID_1E10&SRL_010BC788
DeviceSerialNumber : 17549192
DeviceUserID : 
DeviceVendorName : Point Grey Research
DeviceModelName : Grasshopper3 GS3-U3-23S6M
DeviceVersion : FW:v2.30.3.00 FPGA:v2.02
DeviceBootloaderVersion : Node not readable
DeviceType : USB3Vision
DeviceDisplayName : Point Grey Research
DeviceAccessStatus : OpenReadWrite
DeviceDriverVersion : Unknown : 0.0.0.0
DeviceIsUpdater : 0
DeviceInstanceId : USB\VID_1E10&SRL_010BC788
DeviceLocation : 
DeviceCurrentSpeed : SuperSpeed
DeviceU3VProtocol : 1
DevicePortId : 
GenICamXMLLocation : Device
GenICamXMLPath : 
GUIXMLLocation : Device
GUIXMLPath : Input.xml

*** CONFIGURING TRIGGER ***

Trigger mode enabled...
Trigger source set to software...

*** IMAGE ACQUISITION ***

Acquisition mode set to continuous...
Pixel format set to EnumEntry_PixelFormat_Mono8
Device serial number retrieved as 17549192...
Stream Buffer Count Mode set to manual...

Default Buffer Handling Mode: Oldest First
Default Buffer Count: 0
Maximum Buffer Count: 3
Error: Spinnaker: GenICam::OutOfRangeException= Value = 6 must be equal or smaller than Max = 3. : OutOfRangeException thrown in node 'StreamBufferCountManual' while calling 'StreamBufferCountManual.SetValue()' (file 'IntegerT.h', line 79) [-2002]


Trigger mode disabled...

Camera 1 example complete...


Done! Press any key to exit...

Application build date: Feb 13 2024 17:01:20

Number of cameras detected: 1


Running example for camera 0...

*** DEVICE INFORMATION ***

DeviceID : USB\VID_1E10&SRL_010BC788
DeviceSerialNumber : 17549192
DeviceUserID : 
DeviceVendorName : Point Grey Research
DeviceModelName : Grasshopper3 GS3-U3-23S6M
DeviceVersion : FW:v2.30.3.00 FPGA:v2.02
DeviceBootloaderVersion : Node not readable
DeviceType : USB3Vision
DeviceDisplayName : Point Grey Research
DeviceAccessStatus : OpenReadWrite
DeviceDriverVersion : Unknown : 0.0.0.0
DeviceIsUpdater : 0
DeviceInstanceId : USB\VID_1E10&SRL_010BC788
DeviceLocation : 
DeviceCurrentSpeed : SuperSpeed
DeviceU3VProtocol : 1
DevicePortId : 
GenICamXMLLocation : Device
GenICamXMLPath : 
GUIXMLLocation : Device
GUIXMLPath : Input.xml

*** CONFIGURING TRIGGER ***

Trigger mode enabled...
Trigger source set to software...

*** IMAGE ACQUISITION ***

Acquisition mode set to continuous...
Pixel format set to EnumEntry_PixelFormat_Mono8
Device serial number retrieved as 17549192...
Stream Buffer Count Mode set to manual...

Default Buffer Handling Mode: Oldest First
Default Buffer Count: 0
Maximum Buffer Count: 3
Error: Spinnaker: GenICam::OutOfRangeException= Value = 6 must be equal or smaller than Max = 3. : OutOfRangeException thrown in node 'StreamBufferCountManual' while calling 'StreamBufferCountManual.SetValue()' (file 'IntegerT.h', line 79) [-2002]


Trigger mode disabled...

Camera 0 example complete...


Done! Press any key to exit...

--- End Message ---
Replies:
Re: ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming John Dobbins via Tech-talk
References:
ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming John Dobbins via Tech-talk
Navigate by Date:
Prev: Re: ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming John Dobbins via Tech-talk
Next: Re: ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming John Dobbins via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024> 
Navigate by Thread:
Prev: Re: ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming John Dobbins via Tech-talk
Next: Re: ADSpinnaker, BlackfkyS 161S7M Not enough available memory to allocate buffers for streaming John Dobbins via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024> 
ANJ, 09 Jun 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·