I have a Planet ICA-350 IP camera. I have been successful at setting the camera up with Vitamin D. However, after being connected to the camera for about 5 seconds or so Vitamin D says that it is trying to connect to the camera and is never able to connect to it again.
I am able to maintain a connection to the camera via web browser and via another brand of surveillance software. Is it possible vitamin d timeouts are too short?
Jim
PS it would be good to have a time limited trial version for your pro version. If I get this camera to work I would want to connect an additional 4 cameras. I like how Vitamin D works but am unsure how it would perform with the 5 cameras active.
Problems maintaining connection to ip camera
Moderator: Staff
3 posts
• Page 1 of 1
-
jayoungh - Posts: 2
- Joined: Wed Nov 17, 2010 5:10 pm
Re: Problems maintaining connection to ip camera
I performed the universal Microsoft fix (rebooted the computer) and it seems to be working properly now. Do you have a linux version? 
-
ryan - Posts: 1015
- Joined: Wed Aug 25, 2010 2:52 pm
- Location: Palo Alto, California
Re: Problems maintaining connection to ip camera
Hi Jayoungh,
Glad a reboot fixed things for you! We don't have a linux version, as much as I'd like to say that we do. It takes far more time supporting two OSs and their variants than I imagined it would, the thought of adding X numer of linux distros makes my head hurt a bit thinking about it... I'm not sure if anybody has tried running the windows build under WINE, you could always give that a shot?
Thanks for the suggestion about pro trial periods. It would be nice, and maybe we can implement it some day. Unfortunately such systems tend to be easily exploitable. That's one of the reasons we opted to simply have an unlimited use free version.
With regard to estimating pro requirements, a baseline measurement from a processor-utilization standpoint would be to open task manager and look for the Vitamin D Agent process using the highest CPU %. This should be the camera process. For instance, on my VDV machine each camera at VGA tends to take about 5%, it can run a large number of cameras with plenty of room to spare for other purposes. Obviously the more cameras you have, the more disk space you'll probably want for storing video as well.
Let us know if you have any other questions, or would like more guidance about the pro version.
Glad a reboot fixed things for you! We don't have a linux version, as much as I'd like to say that we do. It takes far more time supporting two OSs and their variants than I imagined it would, the thought of adding X numer of linux distros makes my head hurt a bit thinking about it... I'm not sure if anybody has tried running the windows build under WINE, you could always give that a shot?
Thanks for the suggestion about pro trial periods. It would be nice, and maybe we can implement it some day. Unfortunately such systems tend to be easily exploitable. That's one of the reasons we opted to simply have an unlimited use free version.
With regard to estimating pro requirements, a baseline measurement from a processor-utilization standpoint would be to open task manager and look for the Vitamin D Agent process using the highest CPU %. This should be the camera process. For instance, on my VDV machine each camera at VGA tends to take about 5%, it can run a large number of cameras with plenty of room to spare for other purposes. Obviously the more cameras you have, the more disk space you'll probably want for storing video as well.
Let us know if you have any other questions, or would like more guidance about the pro version.
Learn more about Sighthound Video in our support pages - Reference Guide | All Articles
Are you a developer? Check out our cloud APIs - Demo | Docs
Are you a developer? Check out our cloud APIs - Demo | Docs