Skip to content
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

Retrieve data chunk from image client #15

Open
Wanru-He opened this issue Jul 3, 2020 · 4 comments
Open

Retrieve data chunk from image client #15

Wanru-He opened this issue Jul 3, 2020 · 4 comments

Comments

@Wanru-He
Copy link

Wanru-He commented Jul 3, 2020

Hi, I am working on the O3D303 camera and I hope to take pictures and analyse the data chunk on a separate python script. Is there a way to retrieve a specific image data chunk (lets say z image) from PCIC image client after a trigger is issued (to force take photos from the camera)? I am able to do this manually from the windows vision application, but I cant find a way to achieve this using this library. Thank you.

@lola-masson
Copy link
Member

Hi @Wanru-He, sorry for the (long) delay, it appears that this issue got lost. Anything we can help you with at the moment?

@diegosalomone
Copy link

Hey, I have a similar setup where a physical trigger activates the camera and I want to have the image generated via Python. I can't find a way to do it. Can any of you help?
If I setup the TriggerMode to 1 (continuous) I can see images being generated on the python script. But with 3,4,5 (physical triggers) the python script never receives and image.

@cfreundl
Copy link
Member

@diegosalomone Did you try the image_grabber.py script in the examples folder already? This one should be able to receive the images for any trigger type.

In case the script is not working: do you see the results if you connect to the camera with the Vision Assistant and execute a hardware trigger?

@diegosalomone
Copy link

Yeah, I tried. Thanks for the suggestion. Also, while exploring the inputs/outputs we can see the TriggerMode parameter (from the docs 1: free run, 2: process interface, 3: positive edge, 4: negative edge, 5: positive and negative edge).

My issue was more on the physical world, sorry. Apparently our proximity switch was too low so didn't trigger the capture. This is now fixed and working with TriggerMode=3.

Thanks @cfreundl . Btw, if anyone wants, the official docs: https://www.ifm.com/mounting/706397UK.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants