-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in the image processing loop #54
Comments
@mkaivs, you are using an outdated code. Try pulling newest version. Also GST_DEBUG=2,pylonsrc:6 environment variable helps understanding errors |
@mrstecklo, Thanks, I'm installing the newest code now. I will report back. |
Any updates on this @mkaivs ? I am having same issue |
I didn't write this section of code, but have some guesses. It could be that there were missing packets due to network/system overloading, generating an incomplete buffer. To help identify this, I would add to that error statement the value of the grab result. If it's due to incomplete buffers, an element property could be added to ignore a certain number of incomplete buffers, or possibly fill in missing data from the previous frame. Do either of you have a way to reliably recreate this error condition? |
Thanks for the reply @joshdoe. Actually, I don't know if it is reproducible but I am getting this error when running this simple pipeline on Adlink Neon Vision Camera which has a basler acA2500-14uc USB3 camera connected to Jetson TX2 board. |
Hi @MhdKAT, have you applied the recommendations in the installation readme in the pylon for Arm64 package? e.g. Increase usbfs memory, increase transfer size in camera. If not you generate a very high rate of smaller transfers, which could overload the host controller and can result in issues you observe |
Thank you @thiesmoeller I checked that usbfs was increased as in the installation recommandations' readme. |
@MhdKAT, every parameter that is displayed active in Pylon Viewer will be saved in PFS file. You can open PFS with text editor if you are unsure. |
Thank you @mrstecklo but I don't think it's there . Here is my PFS file : |
@MhdKAT. Try adjusting Transfer Size a bit in Pylon Viewer. Probably some defaults are not exported to PFS. When property is represented in PFS it can be manually edited with text editor |
It is not in the camera node map, but in the streamgrabber nodemap. It is a config param of the grab enginem In pseudo code: cam.StreamgrabberNodemap.MaxTransferSize = 4 * 1024 * 1024 |
I added the feature in my fork ... ( https://github.com/thiesmoeller/gst-plugins-vision/tree/feature/gst-pylonsrc_add_usb3_maxtransfersize )
|
I have a pipeline that ran for hours before this error occurred.
I looked into the source code and the error originated from this function:
I'm not sure what this error means and how to start fixing it. Please give me some explanation and pointers to help me deal with this error.
The text was updated successfully, but these errors were encountered: