.."Heeey! @matze is back!"..
Hello, Matthias,
hope you are doing well in this craziness. With plenty of time available for coding now, we have finally started to work on the new control software. If you are online, could you guide me through the structure of libpco? I understood from Tomas that you had added some code on top of collection of very low-lovel functions which you got from PCO like, what, ten years ago (?) I used libpco+libuca to connect to Dimax and 4000 which we have too at BMIT, but our workhorse camera is PCO Edge CLHs with the optic-fiber interface on the 5th generation of Marathon frame-grabber. PCO now has SDK which I got from them and CLHS (opt fiber) camera has a separate set of headers, includes, and libraries. SDK also contains functions compatible with old cameras. I discussed plan of actions with Tomas and he suggested that I should try to compile libpco with new SDK and try it first with Dimax/4000. With this being done one can try to compile a separate library, e.g. libpcoclhs to have an interface between libuca and pco-clhs camera. Since I'm not professional it will probably take me days of work to reverse-engineer original libpco and compare it with functions in new SDK. I though that if you could have a look and compare new SDK, which includes already some higher-level functions to work with individual frames and streams, with your libpco functions which you had added on top of old PCO SDK, that could give me a good start. Or, if you do not have much time/interest in this anymore, could you enumerate what was missing in the old libpco which you had to implement yourself to make interface between libuca and the frame-grabber. In any case any help/thoughts/comments from you side will be very much appreciated.
Stay safe and best regards,
Sergei.
Best regards,
Sergei.
.."Heeey! @matze is back!"..
Hello, Matthias,
hope you are doing well in this craziness. With plenty of time available for coding now, we have finally started to work on the new control software. If you are online, could you guide me through the structure of libpco? I understood from Tomas that you had added some code on top of collection of very low-lovel functions which you got from PCO like, what, ten years ago (?) I used libpco+libuca to connect to Dimax and 4000 which we have too at BMIT, but our workhorse camera is PCO Edge CLHs with the optic-fiber interface on the 5th generation of Marathon frame-grabber. PCO now has SDK which I got from them and CLHS (opt fiber) camera has a separate set of headers, includes, and libraries. SDK also contains functions compatible with old cameras. I discussed plan of actions with Tomas and he suggested that I should try to compile libpco with new SDK and try it first with Dimax/4000. With this being done one can try to compile a separate library, e.g. libpcoclhs to have an interface between libuca and pco-clhs camera. Since I'm not professional it will probably take me days of work to reverse-engineer original libpco and compare it with functions in new SDK. I though that if you could have a look and compare new SDK, which includes already some higher-level functions to work with individual frames and streams, with your libpco functions which you had added on top of old PCO SDK, that could give me a good start. Or, if you do not have much time/interest in this anymore, could you enumerate what was missing in the old libpco which you had to implement yourself to make interface between libuca and the frame-grabber. In any case any help/thoughts/comments from you side will be very much appreciated.
Stay safe and best regards,
Sergei.
Best regards,
Sergei.