Once more, thank you Schufti!
I registeres for the foscam software but I have no clue which one to pick for my camera. What is the difference to the other firmwares? Can you recommend it?
I will drop celem a PM as well.
Sorry for asking so much and thanks
Graham
P.S.
Found a web UI that runs with my cam. Seems like everything works but I cannot move my cam using the buttons on the web UI. Just the button in the middle works where the cam does a ful circle.
Please make sure your camera will support loading one of these Foscam MJPEG camera firmware versions. The table below should help you isolate what firmware versions MIGHT be compatible for your camera. If your camera cannot support using a Foscam MJPEG firmware version. Then you could wipe out important memory areas in your camera. You still might be able to recover your camera after doing so, by using a serial interface.
On the label for each camera. There will be a VNT or FR followed by the wireless Mac Address of the wireless daughterboard in the camera:
VNT wireless daughterboards only support 802.11 b,g
FR wireless daughterboards support 802.11 b,g,n
Example System firmware map to Foscam MJPEG camera models by wireless daughter boards:
PT = Pan/Tilt
Type FR WiFi module Type VNT WiFi module
------------------- --------------------
Indoor PT cameras romfs_cmos_11_37_2_51 romfs_cmos_11_22_2_51
Indoor fixed cameras romfs_cmos_11_35_2_51 romfs_cmos_11_25_2_51
Outdoor waterproof cameras romfs_cmos_11_35_2_51 romfs_cmos_11_25_2_51
Outdoor PT cameras romfs_cmos_11_37_2_51 Never use VNT WiFi module
Note: The linux.zip file for each System firmware release. Example x.x.x.51, is common to ALL MJPEG camera models. The romfs file is unique to camera model type ("Indoor PT, Indoor Fixed, Outdoor 'fixed', Outdoor PT") and wireless daughter board in that camera model type.
I have ALL the firmware versions for ALL Foscam camera models. MJPEG, Old H.264 and currently being sold H.264 models. Including the linux.zip and romfs for ALL Foscam MJPEG camera models. Which can be used for serial interface recovery.
So worse case you could do a serial interface upgrade for the camera. IF it's compatible with Foscam MJPEG camera model firmware. The TTL Serial Interface needs to support 3V DC and can be a USB serial interface, like the one shown below. They can be found for under $2.00 U.S. ("Including shipping") on places like ebay.

All Foscam MJPEG camera models have a serial connector labeled J2. See below, for pin layouts and locations for Foscam MJPEG Outdoor ("Example 1") and Indoor ("Example 2") camera models. The pins RXD,TXD,GND are the same for both:


If you can still see your camera in the IP Camera Tool. Then you can simply reference the above table first two sets of firmware version numbers and download that firmware, from the Foscam firmware download page:
IP Camera Tool Download:
http://foscam.us/downloads/IPCamera.exeFoscam Firmware Downloads:
http://www.foscam.com/down3.aspxThen you can use the IP Camera Tool to install firmware normally, without the need to use serial interface recovery methods. By simply selecting the camera shown in the IP Camera Tool and then right-clicking on it and then choosing the upgrade firmware option.
You can first install only the system firmware before installing the Web UI firmware and use the below to verify that you can access the camera, prior to installing the Web UI via the IP Camera Tool:
Please do NOT use any leading http:// or www. when entering your camera and port information after you click on the link belowSimply enter: IPAddressForCamera:PorForCamera or DDNSForCamera:PortForCamera
http://www.saveontelephonebills.com/camera/YourCameraBIV25.htmThe above can be very helpful. Because it does not depend on any Web UI being in the camera. Since whatever Web UI firmware is currently in the camera, if any, may no longer match the system firmware, that's now in the camera. The above gives you a clean method to make sure that the system firmware now in the camera, is in fact functioning as it should be. Before taking any more time installing Web UI firmware, that won't work anyway, if the above fails. Allowing you to potentially install a different system firmware, if needed, first.
If your camera is accessible using the above. You can now use the IP Camera Tool to also install the Web UI firmware now, so that you can access the Standard Camera Interface by using the Cameras IP Address or DDNS and port for the camera from a browser.
The same method above, can be used when recovering a camera using the serial interface, prior to installing a matching Web UI firmware using the IP Camera Tool to do so, for the system firmware you used for the cameras serial recovery.
Don