varascope

I think your information source is jumbled. 9p006 is the Aptina MT9P006 The TI 368 is the TMS320DM368 which is the Digital Media Processor As far as Sony vs Aptina that is relevant to the model. Sony released the ISX006 series which as a more Apples to Apples comparison I prefer the ISX006 because of the speed tag capability and up to 120fps but if you don't need the super speed then Aptina is the best price.

Have you experienced overages? If so how bad was the bill?

Usually it is an On/Off operation. Cameras with OSD may have intensity settings and thresholds depending on manufacturer. Those without OSD or dip switches are primarily on/off. If you cracked one open, you might find a pot that adjusts intensity.

What third party? 99% of DVR do what your asking. Just need to clarify further of what your doing.

It comes down to focal distance. A 480tvl camera properly placed can identify a face at 10' or less. So 2.1 for longer distances gives you X clarity on zoom. The X is the part that has a more in depth formula. 1. If you were watching the local kids in the neighborhood and new who they are then 40% focal length may be enough 2. If it is for identifying an unknown person 80% focal length. The FBI recommends 110%. 3. A camera placed farther away but with a better zoom maybe better than a camera placed closer but too high. You see this from the amateurs that install most convenient store systems. The police end up with more top of the hat than a face. There is more but you get the general idea Now this is typical recommendations for focal length based on lens zoom. Since IP cameras is mostly fixed length lens, although there are exceptions, the formula then applies to the zoom ratio. I know most poeple are asking the difference between 2.1 vs 3 because of cost differences but each situation is different. If you place one to catch people walking to the door then 2.1 or even 1.3 is more than enough. But if your talking about the house the end of the driveway 3MP maybe more suited. It also depends on the image sensor make and model. Night time requirements also are a factor. For example a 3MP Mobotix looks terrible at night but the new 5MP is significantly better. In any setup, define your objectives first in order of importance then that will narrow down your selection of the right camera.

Is it wrong to think that was awesome? Worse has happened on Jackass !

What are you looking to have done?

The greens are the worst. Performance is super slow and side by side with a Red it is a night and day difference. The best drives used for Enterprise systems have been SAS drives with an Areca Raid Controller configured for RAID 6 or RAID 10. Just waiting for the Ultraviolet drives to come out. 1.2 Petabytes of storage with Intels MPU blazing fast transfer rate.....uhh..uhh.uhh more power!

@khalid Can you start a new thread? Your subject does not match the topic being discussed here. Also for your post to be answered correctly and fast, you should be more descriptive. Provide Model # of DVR, configuration, 3G EVO Model Number and TP wireless model #. Photos are a plus.

Have you tried their Mega Red?

@Docer What is your sensor size on each? what is your lens size on each?

It will work fine. With the Red Series, it is not so much the speed it is spinning but the 6Gbs SATA rate and the firmware that tells it how to record. As an example the SV35 drives record sequentially vs randomly. I actually prefer the Red over the SV35 because after the Thailand flood issue, the drives don't seem the same and the warranty was shortened. The way the DVR/NVR records also effects performance. We have 2 versions of our software where 1 records 1 file per camera in 256M chunks. The second records all cameras to one file in 256M chunks (changeable). The 1 file system shows a dramatic performance increase.

Drinking usually does it for me. Do you see an advanced menu with storage or drive management? Do you see where to Format drive? She will find out sooner or later so not sure erasing the drive will help.

Are your referring to: how the IR filter works with the IR lighting? This is the sensitivity to the IR light range 800-1200nm (nanometers) Images appear different depending on the range and the sensor. Or are you referring to how the IR turns on?

Yes for the entire account setup. Has anyone come across an IP camera that "pushes" vs pulls? There was some chatter about it but didn't see a final economical solution. The only one was over $2k but it could bond up to 5 air cards or OSPF the traffic. @thewireguys What is the damage for overage fees? Had any customers drop their jaw when the bill arrived?

It is called a magnetic ground loop sensor. It creates a magnetic field and when the field is "warped" it activates a relay. Same tech used for intersections in the USA. Those strange squares you see in the lanes when your first or second in line at a light. They also use for scheduled control so the most popular direction stays green all night long after 11pm and will not change until you roll over it from the perpendicular direction. Maybe a little expensive to delpoy. Second option is the $5 hose with a bolt plug on one end and a pressure switch. The vehicle runs over it, blows a puff of air against a diaphragm switch completing a circuit. Either can be converted to wireless notification. Third option is a better motion detector that discerns small animals vs vehicles but..... the deer maybe enough to set it off. PM me if you need help on setup of either.

Ok this should be a simple fix now that information is confirmed and you are in fact double routing. 1. In the Modem under LAN or DHCP server, is it on? If not make sure it is. 2. In your WRT54G turn DHCP off under LAN 3. The plug from your modem is most likely going into the single port labeled WAN. Unplug that and plug into 1 of the 4 ports on the LAN side. 4. The DVR has a set static IP? If not make sure it is. 5. In the modem set port forwarding to point to the DVR at 192.168.0.101 Note the third octet is "0" You will have to change the DVR from your original post. So to confirm 192.168.0.X is your network 1=Modem (Also a router) 2=Wireless(Was a router, now just an access point) 101=DVR. DHCP "ON" for modem , off for wireless router. The modem will issue all addresses no matter which device connect via DHCP. Wireless only provides authentication to the network. Now for device lingo made easy. Your modem is what is referred to as a Layer 1/Layer 2 device. This means it provides the physical connection (Phone line/DSL) and the network card it uses. It is also a Layer 3 device which means it is a router (directs traffic). Router is the function not so much how it looks. For home use they combine to make it easy. The most common misinformation is a modem has 1 port and routers have many. Buried in the fine print is the fact that your WRT54G is a router/switch/wireless gateway with a firewall built in. High end routers at data centers typically have 1 for WAN and 1 for LAN and anything else is consider optional modules. They are then plugged into dedicated firewalls and/or switches, if those features are not built in already. Your network that start with 192.168.x.x are considered non-public routable IP addresses and used for inside network or private network. So originally your IP chicken address WAN >>> NAT (Network Address Translation) with port forwarding was taking the outside address and telling it to forward to .101 Which it shouldn't even allow it at you wanted to point to 1.101. The traffic would hit a brick wall (the WRT54G firewall/router) WHICH had the 192.168.0.2 address. Since that is not a true routable address and the DVR was plugged into the inside network of the WRT54G, port forwarding wouldn't work. What you have after this change is a Modem/Router/DHCP server plugged into your WRT54G Wireless AP with a 4 port switch. Notice router is not in the description since you should not have any cable plugged into the WAN port. For reference you could double the routing and port forwarding or in the modem disable firewall or tell it that 192.168.0.2 is a DMZ. This will work BUT is not considered best practice and due to how the headers in the packet are assembled and read by each router, may cause issues. There is a lot more to it, but I will not go into it here. For testing purposes, you internal PC should have a 192.168.0.X address Open command prompt Ping 192.168.0.1 (Modem) Ping 192.168.0.2 (Wireless) Ping 192.168.0.101 (DVR) If you get a response on all you should be good to go. Please advise if everything is working now.

Do you have an adapter to plug PC speakers into the DVR? Are you getting any line noise, static etc? Can you play a radio on load at one of the microphone sources? Then log on the camera direct through the browser, do you hear audio there?

My bad. I was off on the model #. The correct one is the HD 7790. Problem with remembering numbers. "Oh it's Valentines day?...' Egg on the face aside. The reason for the second card, even though it draws more power, is to offload from the processor and transfer to it's own GPU. Regardless of opinion, just for testing purposes, try any card you may have laying around. The processor you are using has an integrated GPU. Have you tried obtaining the GPU drivers from Intel to make sure you have the latest one? The last system you built with NVR, what were the specs? Same I7 processor? I would suggest doing an inventory print for side by side compare to dot your i's and croos your t's. Maybe something will jump off the page. Try this link http://www.intel.com/support/graphics/detect.htm

@Boogieman Your right on that one. I think I am mis-quoting the model number. I am going to have to check on that one when I get to the office tomorrow. Thanks for the spot.

The rating of the relay and voltage drop are both a factor. 24 volts over 18/2 as long as the drop is within the tolerance of the relay, you should have an issue That distance should still have 15 volts. 9 volt drop. On 12v your looking at 3 which should be enough to trigger standard relays. Using 22awg twisted pair on 12v you will not have anything at that distance. On 24vac you will have 3.2v with 22awg. What is the relay model?

Not that you didn't but I didn't see in the post, did you turn audio ON in the camera? In the Speco: Is audio setup correctly? Select this option to set an audio channel to output. (Channel 1 through 4, Audio Mute)

It appears ou have a dual routing issue. The modem does not appears to be just a straight modem but a router too. To clear things up: 1. Go to IP chicken. What is your address in there? 2. Go to the modem and under status or setup you should see that same address for outside/WAN 3. In the modem what is your LAN/Internal address? Is it 192.168.1.1? What is the mask? 255.255.255.0 ? 4. is DHCP turned on? Now go to the Router WRT4G: 1. Under status or setup under outside/WAN what is the IP Address? <----Important 2. What is your LAN/Internal address? What is the mask? The network cable attached to the DVR is plugged into which? I assume your using the WRT45G primarily because it has wireless?

You should be using 24v with a relay that operates between 6-40 volt range. Here is a connection diagram.

I was hoping for a jumper pin that creates a reset. Anything like that on the board? While running short the jumper or move the jumper plug.