Closed rebeccasc closed 3 months ago
Since I don't have a Calibir GX at hand the following remarks are somewhat shots in the dark 1) Some of the other Spinnaker based cameras allow for a UserSet to be loaded. Have a look for instance at the Blackfly S camera configs and the launch file for loading e.g. UserSet0. The procedure would be to save UserSet0 from within SpinView, then loading UserSet0 when launch the ROS2 driver. 2) This line from the log is concerning. No idea what it means and what triggers it.
[camera_driver_node-1] terminate called after throwing an instance of 'Spinnaker::Exception'
[camera_driver_node-1] what(): Spinnaker: Unable to set StreamBufferCountMax due to failure to determine image size or payload size. [-1009]
3) I'm confused as to why the driver didn't log more error messages. The lines below seem to have invalid spaces (between Transport and Layer), and between TransportLayerControl etc. Why are there no error messages? This should never work.
[camera_driver_node-1] [INFO] [1723818030.189867363] [XXXXXXXX]: setting TransportLayer Control/GevSCPSPacketSize to: 1500
[camera_driver_node-1] [INFO] [1723818030.191231802] [XXXXXXXX]: setting Transport Layer Control/GevSCCFGExtendedChunkData_to: 1
4) Since this is a GigE camera, you may want to use Jumbo packets (5000 instead of 1500), also make sure your network card MTU is set to 5000. But this should not be a problem since SpinView also operates at 1500 MTU, right?
5) Again in the log it says:
[camera_driver_node-1] [INFO] [1723818030.187767911] [XXXXXXXX]: setting AcquisitionControl/continuousTransfer Mode to: Off
It seems to me that the capitalization and spacing is wrong (should be ContinuousTransferMode), and if anything should be set to "On" rather than off.
Where those strange inconsistencies introduced when editing the log file to obscure the serial number?
@berndpfrommer thanks a lot for the fast reply!
Actually, the spacing is some weird copy and paste error.
Setting ContinuousTransferMode
to On
solved the problem. Thank you very much for your help! :)
Is this behavior also observed when using SpinVIew? No
Describe the bug I want to use the ROS flir camera driver with my Calibir GX GigE camera. I added a configuration file, as described here. When I try to run the camera via the ROS launch script I get a
[WARNING]: acquisition timeout, restarting!
. However, the camera works fine (without the warning) when it was used with SpinView right before. That means it works properly with SpinView and if I disconnect from SpinView and start running the ROS driver afterwards, everything works fine. However, if I then disconnect the camera from the power supply and reconnect it and then try to restart the ROS driver, I get the acquisition error again. It seems that SpinView sets some important camera parameters that I do not set in the launch file. I have gone through all the parameters in SpinView and cannot find the missing ones.Useful logging output
System details