R.Alves Posted January 30, 2008 Report Share Posted January 30, 2008 Would be great to count with a package like the IMAQ package but for use with IP cameras, where all the process of capturing the video information of the communication protocol would not be an issue to the user. Quote Link to comment
Rolf Kalbermatter Posted January 30, 2008 Report Share Posted January 30, 2008 QUOTE(R.Alves @ Jan 29 2008, 02:37 PM) Would be great to count with a package like the IMAQ package but for use with IP cameras, where all the process of capturing the video information of the communication protocol would not be an issue to the user. Well, nice idea but there is a problem with that. There is nothing like a single IP camera communication protocol that I'm aware of. If a camera has the possibility to be controlled over IP directly it is sometimes RSTP or a proprietary protocol, that you can access through an Active X control only, and whose protocol is not normally documented or it contains an embedded web server that can be accessed through a web browser. For the proprietary protocol through ActiveX, you would have to integrate it through use of the Active X functionality in LabVIEW and this will be of course camera specific, and the second you could access trough the HTTP VIs that are part of the Internet Toolkit and of course are camera specific too, since the web server structure is also different on each camera type and sometimes varies between versions of the same camera too. RSTP is not very common and only really allows control of the camera itself, but is not the streaming protocol itself. If the camera supports it you can request with the DESCRIBE command an url from which you can retrieve the current image, which will be usually an FTP or HTTP url, and that can be handled with the Internet Toolkit. But considering the NON-standardization among IP cameras such a Toolkit will never be able to support more than a few specific cameras, so it will be hard to justify creating something like that unless you happen to have a specific application, and that means often that one develops them for a specific project and therefore can't just put it up for free download because of right of ownership. There is of course also GigE, which is a standard and I think NI is supporting that already. Rolf Kalbermatter Quote Link to comment
Neville D Posted January 31, 2008 Report Share Posted January 31, 2008 QUOTE(rolfk @ Jan 29 2008, 01:27 PM) There is of course also GigE, which is a standard and I think NI is supporting that already.Rolf Kalbermatter For windows only, not yet for LV-RT. It has been on their "to-do" list for more than a year now. Neville. Quote Link to comment
Rolf Kalbermatter Posted February 1, 2008 Report Share Posted February 1, 2008 QUOTE(Neville D @ Jan 30 2008, 03:49 PM) For windows only, not yet for LV-RT. It has been on their "to-do" list for more than a year now.Neville. Which RT system has a GigE interface? Without it won't work anyhow. Rolf Kalbermatter Quote Link to comment
robijn Posted February 1, 2008 Report Share Posted February 1, 2008 GigE is the way to go. I guess it wont be long before there is an RT system with a compatible interface. Joris Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.