Le 12/10/2010 15:20, IOhannes m zmoelnig a écrit :
On 2010-09-30 15:10, cyrille henry wrote:
ok, thanks for all the answer.
i'm sorry, i was so exited to have it compiled, that i miss the end of
the readme.
so, i'll not ask how to open a camera, since i now have read it till the
end!
sending :
device GigEVision::0030530f8e64 did not work, but :
device GigEVision:default:0030530f8e64 did work.
so, i now have an image.
well, i would be better if i had a lens on this camera ;-)
anyway, i noticed that some images are not correct.
in attachment, you can find 2 examples of bad images...
hmm, no that i have this camera, this get's even stranger...
i cannot reproduce the bad images, however:
- it's only b/w (well, i guess that's the cam)
yes, i think this cam is B/W
- framerate is pretty bad (afaict, its about 10fps :-(, but that might
be related to something else)
outch!
it's a 120fps cam...
- latency is worse than expected (see attached feedback image)
yes, this is not really usable...
however, all images captured are fine.
ok, strange.
note however, that i experimented a little bit with the pylon SDK before
trying with HALCON. maybe this put the cam into a more appropriate mode...
(eventually i'll write an pylon backend, it seems to be available
without having to pay a license, though it's somehow hard to get your
hands on as well)
cool
thanks
Cyrille
fgamsdr
IOhannes
_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev
_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev
