I will be using a mix of 4K and 2MP starlight variable focal Turret style as my main cameras to cover all the areas I want cover 24/7. The PTZ's will be used as secondary cameras that I can use to look around my property and neighborhood.
Thanks for the info. I have no problem with electronics, opening cameras, changing IP addresses or Dip switch setting. I've decided not to with a Lorex system. I'm going to put a Dahua system together. I know what cameras and NVR I'm going to be using. Once I have the exact number of cameras and types want to use I will send Andy my list and have him work up a price for the system. Several people have said that Andy give good package prices to IPCamTalk members..Just recently (within 2 weeks) bought my 4 Dahua cameras to connect with my Lorex 5k NVR from Andy. Cameras arrived quickly, exactly what ordered. Three out of the 4 recognized easily, 4th one I'm working on. I'm ignorant in these matters (not so much now after days) but I feel I'll figure it out. No networking knowledge here at all before this. IF you don't understand or fear things such as opening camera bodies, changing ip addresses etc. I'd say stick to all the same brand and US based for phone support. Just my opinion.
Sorry to bump an older thread with my first post here....
I'm another in the same boat but too late on the purchases. In anticipation however I've landed here since IP systems are a new thing for me. That being said I ended up buying TWO Lorex systems (partly based on that fact that they are Dahua and now owned by Dahua). We have a good size commercial property with two businesses and budget was a concern. The one building will be a totally new install, the other building I'm going to be replacing the older analog system. Fortunately it is all wired with Cat6 cable using baluns.
This is the setup that we ordered two of - I thought it was actually a pretty good deal since it is one of the only lower cost setups with the better NVR 2K IP Security Camera System with 16 Channel NVR and 8 HD IP Outdoor 4MP Cameras , 130FT Night Vision
With their 15% standard discount it is only $679. As far as I have been able to determine looking closely at manuals, specs, and images of the rear of both it would appear that the Lorex NR9163 NVR is identical to the Dahua NVR5216-16P-4KS2.
One thing that I'm curious on is now that Dahua has owned Lorex for a bit of time, does anyone know if they are updating firmware any more frequently or making the firmware more like standard Dahua firmware? Has anyone tried cross-flashing Dahua firmware onto Lorex branded stuff? I am going to be looking at adding additional cameras to both setups though so I'll be looking at Empire for those.
One thing that is certain, coming from semi-modern 960H analog stuff the NVR interface looks fairly familiar so that is a plus. For mobile viewing I've been using (Android phone) IP Cam Viewer Pro (by Robert Chou) for a few years and have been very happy with it. We have a Checkpoint security gateway (firewall) and I have custom ports mapped rather than using anything standard but I still worry about the seemingly terrible security on what seems to be just about all security camera systems. I'm debating on just killing the port mapping and using the Checkpoint VPN but that is just a bit more tedious and slow having to first connect to the VPN.
Anyways glad to have found this site. There appears to be an ungodly amount of excellent info and plenty of like minded helpful people! I'll be a regular on here.... that is for certain.
With respect, whilst picking a high random port does increase the level of effort required, that's an optimistic statement that may mislead, as the discovery process is often automated using a botnet collection.Rare that a generic hacker will do this as it is too time consuming.
Many script kiddies are just using tools to scan and find exposed systems... so better to just not port forward at all today. Too many malbots out there....Rare that a generic hacker will do this as it is too time consuming. They might if they are trying to hack some specific IP address for some place where they know who has that IP. ...
HI MixMan,Well - I ordered two of the SD1A203T-GN cameras from Empire (Andy). Now I get notice from Lorex that the two system packages I ordered will not ship for another week. Trying to work with Andy but wow - once I add everything in to match the Lorex kit it is coming out hundreds more.
The Lorex kit is $679 and includes
NVR NR9163 (same spec as NVR5216-16P-4KS2) thought at first it might be the 4216 but that is 200Mbps and the NR9163 is 320Mbs like the 5216.
4 LNB4173B bullets, 4 LNE4162B turrets which spec identical to the IPC-HDW1431S and the IPC-HFW1431S
Plus a bunch of (admittedly low grade) network cables.
The Lorex NVR also includes a 3TB surveillance grade hard drive (So either the Seagate one or the WD Purple one) - so about $75 value there.
Price on the NVR5216-16P-4KS2E (the newer version) is $299 plus $82 per camera and I dont think that includes a drive for the NVR.
So thoughts? Right now I can cancel Lorex and roll my own but its looking like at a LOT higher cost. At least $950 and then still need to add a hard drive! I'm wondering if I need to just wait on the Lorex stuff. When I saw I had time to cancel on Lorex I contacted Andy but I was not expecting a $270+ increase in price ordering what will be technically less (probably would not get all the cables) with less of a warranty.
I have two systems I need to get setup very soon.
Hi MixManSCOk - so an update...The Lorex NR9163 NVR. It IS a NVR5216-16P-4KS2 with Lorex custom crippled firmware on it. ..
So I fired up a TFTP server and set the environment variables in the NVR for using TFTP, copied the update.img to the TFTP folder and then ran the run up command. It took it in just fine. Now my brand new Lorex NVR is a Dahua NVR5216-16P-4KS2 with all of the proper capabilities like IVS. It also sees the two Dahua cams just fine in private mode and also sees the Lorex cams just fine too (those are still running Lorex branded firmware - I might have to try this on those too and load proper Dahua english firmware on them.
Ok - so an update. Get the lit in from Lorex and have been messing around with it some just testing things. I also have a couple of the SD1A203T cameras I ordered from Andy.
So - here is the fun bit. The Lorex NR9163 NVR. It IS a NVR5216-16P-4KS2 with Lorex custom crippled firmware on it. Somewhat disappointing as I cannot get it to connect to the Dahua SD1A cameras in private mode. It does connect to the fine via ONVIF though. The catch there of course is you have very limited control from within the NVR. Of course as mentioned, the firmware has some things stripped out like IVS. So being the adventurous type I tried loading Dahua firmware on the NVR through the web interface. Tried a few different ways and 2 different versions. None work - it errors and then the NVR reboots. So lets dig deeper then. Just to be 100% sure I looked at every square inch of the mainboard and carefully compared with a video someone made of them installing a hard drive in a Dahua NVR5216-16P-4KS2. Everything is 100% identical right down to the screen printed numbers on the board. Feeling a bit more confident I started looking at that 9 pin serial port on the back of the NVR. Well it just happens I'm an IT guy and use a Dell Precision T7910 pro workstation that has a real serial port and I have piles of serial console cables for managing different devices on my shops network. So I connect a cable up, fire up Putty and power up the NVR and get nothing. Tried a few different speeds and no go. I read in some thread that someone said on some other model that the serial port is 12v TTL - yikes! Hoping I did not fry my serial port I pulled the cover on the NVR and checked with a meter and the serial port is 3v.... so all good. So I decided to see, just to be sure.... a null modem cable. Bam - console started spitting out data on booting the NVR. After a minute or so you see a starting linux message and the console then goes dead. Before then though - you can interrupt the boot process by pressing a key.
That drops you to a Hisilicon uboot prompt. So digging some more and trying to glean some info online I figure some commands out and find that one is a manual firmware upgrade for Dahua devices, run up. Looking at the environment variables I see that run up is looking for update.img via TFTP. There are also several other run commands that can load individual parts of the firmware in the same manner. Well - went back the the firmware I downloaded and tried in the web interface and sure enough - all of the various files are in there including update.img. So I fired up a TFTP server and set the environment variables in the NVR for using TFTP, copied the update.img to the TFTP folder and then ran the run up command. It took it in just fine. Now my brand new Lorex NVR is a Dahua NVR5216-16P-4KS2 with all of the proper capabilities like IVS. It also sees the two Dahua cams just fine in private mode and also sees the Lorex cams just fine too (those are still running Lorex branded firmware - I might have to try this on those too and load proper Dahua english firmware on them.
Anyways - I'm tired and am going home. I just spent the past 3 hours on this. I have not tried to match up the two Lorex camera models that came in the kit with their Dahua counterparts yet. I think those will be trickier to convert the Dahua firmware though since they do not have a easy to get to serial port and the Lorex firmware seems to not like being upgraded to Dahua firmware in the web UI. I have not tried that on a camera though - just the NVR. If this is doable on the cameras too, particularly without having to crack each one open to solder some wires on for serial access, then I will really be stoked.
The one thing I really want to figure out though, is a way to backup the Lorex firmware FIRST. This way if there is an issue with something where I might need to send it back to Lorex under warranty I can load their firmware back on first.