Bouriquet59 a écrit :
Bonjour à tous,
Je viens de commander 2 caméras FI8910W que je vais recevoir prochainement.
Je suis actuellement sous windows phone et j'ai vu qu'il n'existait pas spécialement d'appli pour visualiser et commander sa caméra. Du coup je me suis dit pourquoi pas faire une appli convivial et surtout gratuite.
J'aurais cependant besoin d'un coup de main. J'ai vu en première page des commandes pour bouger la caméra, pour activer la surveillance etc.. mais je n'ai pas vu comment récupérer le retour de celle-ci pour savoir si elle est bien en surveillance par exemple.
Ou plus simple auriez-vous une doc qui regroupe toutes les commandes de la caméra possible ?
Mon objectif serait de faire une appli pour windows phone et plus tard pour windows 8, sachant que les deux OS sont très proches.
Merci d'avance pour votre coup de main.
Michael
|
You are very welcome. I am including as much information as possible in this response. So that as needed. Others can use it as a reference. You and/or others can link back to this response directly by using this:
http://forum.hardware.fr/hfr/Hardw [...] tm#t737225
Hello.
There are two methods to interface to these IP Cameras. One is a high level interface, using .cgi commands. The other is a low level interface using http data packets. Here is information and examples. With Live Demos for the high level interfaces as well as a pre-compiled binary for Windows based systems showing the use of the low level interface. Including documentation for both interface levels as well.
Please see this free Interface which includes Live Demos, that work with any Internet browser capable device from Computers to Tablets and Phones to TVs:
http://foscam.us/forum/free-generi [...] tml#p10970
Here is another free Interface which is Windows based, that can monitor as many as 10 IP Cameras at the same time and record video with audio on IP camera alarms. Please note. Normally, only video is recorded on alarms. This also allows you to define the length/time of the video as well as the resolution and FPS ("Frames Per Second" ) rate of the video. Normally alarm recordings, are always 60 seconds long:
http://foscam.us/forum/free-mjpeg- [...] tml#p15874
Here is the documentation for the high level .cgi SDK for these IP Camera models:
http://foscam.us/forum/download/file.php?id=402
Here is the documentation and a full c++ project, including source code, for the low level interface, with a low level pre-compiled binary .exe for Windows example:
http://foscam.us/forum/sample-code [...] tml#p24770
It's also possible to customize the UI ("User Interface" ) that the IP Camera uses, as well as host and store other web pages inside the IP Cameras firmware. Basically using the IP Camera as a self-contained, tiny web server, by storing custom web pages in the IP Camera itself. Please look toward the bottom of the page this link goes to, for more information, on how to go about doing that:
http://www.openipcam.com/forum/ind [...] 473.0.html[url]
The IP Camera has limited memory. So you could not use the IP Camera as a full blown web server. However, you can use the IP Camera as a small mini web server and include custom web pages, in the actual IP Cameras Web UI firmware and/or modify and customize, the standard IP Camera interface, that comes with the IP Camera.
Here is an example of modifying the IP Cameras Web UI firmware, where a custom web page was added. This web page is stored in the IP Cameras memory and was added to the IP Cameras normal Web UI firmware. The normal Web UI of the standard IP Camera interface still works as normal. This is simply another web page that was added to the Web UI firmware.
Now the IP Camera can be used for public access, limited access or private access, to host and supply this web page, directly from the IP Camera. Without any need to use the standard IP Camera interface, that comes with the IP Camera or have a website or web hosting service to store this custom web page. This example is using the free Interface of the first link in this post, with custom configuration options, the Interface supports. It could prompt for logon vs. auto-logon, which is one of the configuration options in the free Interface:
http://cam18372.topipcam.org:90/Ne [...] erator.htm
The above link is hosted and served directly from the IP Camera itself using the DDNS of the IP Camera and name of the custom web page and it can be used and accessed by any Internet browser capable device. From Computers to Tablets and Phones to TVs.
If your ISP IP Address does not change often, you could also simply use your ISP IP Address and the port for the IP Camera and the name of the custom web page with no need to use any DDNS for the IP Camera.
Example: http://68.187.157.136:90/NewWorkingDemoOperator.htm
One could use the links above for private use or in any Email correspondence or on social media sites to say things like "Hey..Take a look at my IP Camera here!" without any need to have a website to host the link above. You could also delete the User Id or change the password in the IP Cameras configuration being used in the link above, to disable the link above, from working, as needed. So it can be turned off/on enabled/disabled easily.
You can also use this internally within your local network. Even if you do not allow remote access from the Internet to your IP Camera by simply accessing the local IP Address and port for your IP Camera and the name of the custom web page. Example:
http://192.168.1.10:90/NewWorkingDemoOperator.htm |
Again, you could also have configured this custom web page to prompt for logon vs. auto-logon as it does. So that anyone who uses the link above, would still need to know a valid IP Camera User Id and the password for that IP Camera User Id. This would also allow you to change the User Id or the password, from time to time and only those knowing the new User Id or password ("Even if many others had the link above, from the past" ). Would not be able to access the IP Camera, using the link above, without knowing the new User Id or new password.
In fact. Even with using the auto-logon option in the above link. If I were to delete the User Id or change the password in the IP Cameras configuration, which is being used in the link above. The same web page, being used in the link above, would now prompt for logon. So there are easy ways to go from auto-logon to prompt for logon without changing/modifying the actual web page the IP Camera is using or installing a new custom Web UI firmware for the IP Camera.
Of course you could also create and store custom web pages in the IP Camera, that have nothing to do with the IP Camera. "About Me" web pages with pictures and background images, other web pages with links to your social media sites, another web page of your resume and so on. Use your imagination.
As you can see there are many options to create custom interfaces for these IP Cameras and access those custom interfaces. I tried to cover all possibilities here. So that you and others can pick the ones that fit your needs.
Without trying to bore anyone to tears. There is one important factor when creating interfaces for these IP Cameras that needs to be considered. These IP Cameras only support ("Four" ) formally logged in concurrent connections. Once this limit is reached, all other requests for formally logged in connections WILL be refused or denied, by the IP Camera.
Formally logged in connections include: Copies of the standard IP Camera interface that comes with the IP Camera that are logged in, Video Streams directly to the IP Camera that are active, applications that use the low level interface to the IP Camera, as well as many, if not most, 3rd party applications.
You can emulate this limit, by trying to exceed the limit by using any combination of the above. Example, try using five different browser windows to logon to the IP Camera, at the same time. Using the standard IP Camera interface that comes with the IP Camera. The fifth logon, will be refused or denied. This is important to know as a IP Camera owner. Because you can be running so many things at the same time for a IP Camera, that you can LOCK yourself out of accessing that IP Camera, until or unless a connection is released.
This also becomes extremely important if you want your IP Camera to be viewed from a website for public access. Because done wrong, it will only allow and support, four website visitors to access your IP Camera, at one moment of time, denying all other visitors access to your IP Camera. Worse, once four website visitors are viewing your IP Camera, you the IP Camera owner, will not be able to access your IP Camera, until one of those four website visitors stops viewing your IP Camera.
The Interfaces that I create ("Including the example custom web page stored in the IP Camera itself and the free Interface example" ). Use short-term connections. Leaving all four of your formally logged in connections available for use, by other interfaces. So this limit of ("Four" ) concurrent formally logged in connections does not apply to my Interfaces. The limit of concurrent connections for my interfaces, shown here, is ("Eighty" ) concurrent connections. It's actually higher than eighty, since this number is short-term connection in flight ("Outstanding requests that have not yet received a response. Which are concurrently in progress" ). This is by design, whereas many if not most, 3rd party developers, are using the formally concurrently logged in connections.
You can also emulate this. Simply by opening more than four browser windows using my Interfaces, to the same IP Camera. Your connections to the IP Camera, once they exceed four, will not be denied or refused, as is normally the case, when using other interfaces to your IP Camera.
IMHO. If you are going to create an interface to these IP Cameras and not allow the interface to be used by ALL Internet browser capable devices. It's somewhat like going to medical school to end up specializing as a foot doctor, who only works with big toes, on left feet only. While you may get patients that use your services. Most likely not as many as other foot doctors that work with anything that has to do with feet!
No disrespect to foot doctors intended. Point being, the second you start specializing and confining who your audience is for your IP Camera interface, based on what Operating System and/or device, they use or can use your IP Camera interface on. You limit the possible uses of your interface to a much smaller group than the entirety of all IP Camera owners who use these IP Cameras. This maybe important if you intend to charge for your IP Camera interface as well. Most of the large computer manufactures, have learned this lesson the hard way, as tablets and other mobile devices have increased in sales. Their sales have decreased, because they did not keep their eye on the ball.
This is easy for me to say. Since my primary goal was/is to provide free interfaces for all IP Camera owners of these IP Camera models. Which I have created interfaces for. I did and continue to do this because I saw many frustrated IP Camera owners who were needing to purchase special applications for each device they used to access their IP Cameras and/or wanted to for private use or to allow limited or public access to their IP Cameras, that would work with all Internet browser capable devices, at no cost. Not limiting that access to four at a time, or locking the IP Camera owner out of their own IP Cameras, when that limit is reached. So, this is just my opinion based on those complaints and observations.
Don
Message édité par theuberoverlord le 06-06-2013 à 19:13:24
---------------
CV - About Me: Français English Conseils et exemples gratuits pour vos Camera IP Live IP Cam Demos
FORUM HardWare.fr
) :
, une idée de mon souci ?