Hello CVB team,
Hope you are doing well.
Since more than one year now, I use the stack 3 to take pictures on our main vision products. It use two AT (mostly C5 SCT) cameras that reconstruct huge carts to control components on it.
We set up the AT to take fixed size images with a maximum of profile (5400). We also open all Ethernet board parameters like Jumbo packets to there maximum. We set also the scsp packet size to it’s maximum.
With the stack two, no problem at all. When we use stack 3 we can see this :
when we should have this :
We also understand that when this happen, we got verry small pikes (in red in the image) contrary to the huge pikes that we have normally (in green) with the task manager :
When we switched from stack 2 to stack 3 or the inverse, no parameters are changed.
The stack 3 used a composite image to get data. Both camera are on the same Ethernet board, without any other element on it.
We suspect that either we get a improper network settings or a problem with stack 3 like bad uses or missing a parameters that need to set up ? Or have you any ideas ?
Hi @AxelDosSantosDoAlto,
With our experience of the new GenTL stack (3rd Gen stack) I expect no difference in performance or stability.
The first image clearly shows lost packets, which you also should see when checking for corrupt frames or Incomplete frames. if you want to do it programmatically.
I strongly suspect a setting which is different in these two setups. And the one which is set from CVB is the PacketSize. So this would be the first thing to check. Has the packet size the expected value?
There is a difference how the packet size can be changed during the startup of the VIN-Stack and the GenTL-Stack.
With the VIN-Stack and loading the GenICam.vin file, you use the setting from the INI-File. Mostly configured over the GenICam Browser.
If you use the GenTL-Stack you have to set the feature programmatically. e.g. directly via the “GevSCPSPacketSize” feature.
p.s.
Please check if you are allowed to post these images publicly. If not, you should delete them.
Hello @Sebastian
Thanks for your quick answer.
As I wrote on my message, we do set up the scps packet size at is maximum like this, directly after connection to the device and get the nodes we need :
m_node_scpsp_packet_size->SetValue(8192);
Unless we need to do it at another point, normally we are ok on this.
Yes, this should work. Additionally you can check for errors and if the value was set correctly.
@Sebastian
We already put this value on our code. And we have the problem.
We will check the value for each packet we will received.
How can we check for errors ?
What I meant with checking for errors in my last post was using try/catch if something goes wrong during access to the node or value of the node.
