Well, since he ditched the tools before the cops got him, all they could do was issue a warrant after I sent the detective this video. I was mostly upset about the entering of my backyard and shed (both not locked) than I was about the compressor and drill.
Had a small hiccup just now with a Broker Connection Error. Something on your end?
Anyway, as for the UI, I'm referring to iCamSource 2, so I'll post over in that beta area. iCam 2 looks just fine, and you already know about the refresh icon... So the UI for iCam is not a problem, love it.
Having a good time with this so far, six cams working great on the iPhone 4. I'll have more feedback tomorrow as I use the app during the workday, just wanted to weigh in on the easy setup.
Okay I see, that's for USB/FW/Built-In cams. Any way to reduce CPU on Ethernet/WiFi cams? My four iCam Source apps hover around 16% CPU each. Not a problem, but if there's anything I can do, it's worth a shot.
I had this error for a couple weeks. Could not figure out what it was, the network/server config had not changed but all of a sudden, I experienced intermittent behavior with Source Connection Error messages both in iCam app and in iCamWeb across multiple iPhones and computers. I finally resolved it by manually clearing out the Motion Events folders on the server. In fact, I had iCam and iCamWeb open while I was clearing out these folders and as each folder was emptied, the camera associated with that folder started working.....one after another until they all were back to normal.
Some other details: Motion Events folders are 500 MB, plenty of HD space, 4 cams total, Server is a Mac Mini running 10.5.8 Server, I'm using the latest iCam Source and iCam app, Cams are Linksys WVC54GCA.
As long as you keep it from getting wet, I've had good luck with the Linksys WVC54GCA, about $75 on eBay. It's been outside in the Texas heat (and sometimes cold) for a year, no problems.
Interesting, thanks. What if you choose No Audio as the audio input?
I believe that you will see lower CPU usage settings when connecting to a network IP camera since you aren't dealing with the video and audio capture and processing from the direct hardware itself.
Where is it you disable audio? At the camera itself?
I had one that had that IP as well, a DCS-900. I had to modify my router to allow 192.168.0.x instead of my usual 192.168.1.x, but after I set it's static IP I changed back to my regular router config all was good. I can suggest this - reset it. I remember the reset button is on the right side while the cam is pointed at you. Hold it for a few seconds and then see if it resets to that IP. Otherwise, you'll need to either guess the IP or check your DHCP log. Does any of this help?
I haven't gotten very far at all. D-Link is saying the IP addy for the cam is 192.168.0.20 we were able to access the settings page once but then nada! Now they're saying nobody can help me until Monday. HELP!
How far have you made it in the setup? These IP cams are configurable through any web browser, however, the initial setup (IP lookup) is done with a PC and some crappy proprietary software. According to the D-Link manual this camera will request a DHCP IP address (WIRED on Ethernet), so you can either guess the IP or check your router's DHCP lease table to find it's address. It will not join a wireless network on it's own. Hope this advice gets you a bit further in your setup.
I just bought four of these refurb on eBay and been very happy with them (you need Internet Explorer to set motion zones, but all the other features are cross platform)
Show Posts
