Hello.
From my experience with such a solution, it is already 4 years 24/7 without crashing the "recorder".
The only thing you need to do every now and then is to vacuum the whole thing. It is helpful to set the alarm in bios to some 60 ° C of the CPU. Sam then lets know when the time is right for cleaning.
The computer works in the minimum configuration, i.e. Mobo + CPU + RAM + PSU + 2xEthernet (1x100Mb / s 1x1Gb / s) + HDD in the plural. There is nothing more in this PC.
It would be good if the motherboard of such a computer would allow the PC to start automatically after a power failure (I have and works).
Processor - depends on the format in which the colleague will download the image from IP cameras. I use MJPEG and this has minimal CPU requirements. One Core Dual Core @ 1.8GHz is enough to support 8 IP cameras.
The PC has access to the home network, because it makes me still behind the NAS + some other useful additions coming from owning the PC as a recorder / servers.
The second ethernet interface creates a completely separate LAN from the home network, only for the purpose of operating the cameras. Lan1 and Lan2 can not see each other directly - for some reason, despite the deviation of upnp / dyndns in cameras, they have been reported somewhere on the web somewhere. As a reward, I isolated it completely from the Internet.
As for the software, I personally use go1984. Expensive party if you have a company. For the home user "not necessarily". It has the aforementioned possibilities - including a phone app, motion detection, a web server on any port, users + a permitting system, a client application, etc.
The whole planted on the Vista V2 SP2 x86 behind the wardrobe and behind the restrictive firewall, without a monitor. Why and why a monitor. I administer after RDP.
Why vista? Well, XP had a tendency to cut his legs through logical badsectors. This problem does not occur on Vista, and it has been stable for 4 years and has a defragmentation schedule. Sufficient proof that I would have nothing to complain about. Only required to disable the newer version of the samba in cmd, because sometimes it was hanging up to share disks, and when trying to access from XP, things were unexplained.
I also combined linux, but emulation under wine is a waste of computing power once, and two is linux software for IP cameras was quite poor. I admit that I did not drill the Linux theme for more than one day in practice, so I do not rule out the existence of some useful software.
issues
The biggest problem when connecting cameras with 2.4GHz wi-fi is a large difference in camera distance. I think about the case when one is close to the AP and the other one is 200m away. In spite of good, directional anthology, there were mass collisions of packets in the ether. Those from the close camera were passing, while the distant camera was often drowned out and thus did not agree with the AP.
It helped setting the ack timeout parameter from the hand. I came to this quite by accident, because at night somehow the cameras could work properly. So I watched what changed, that they did not cooperate.
Another thing - crappy routers put in the role of AP like to hang up as they get a steady stream from several sources.
The wired installation works most steadily. I do not have any problems with her. Of course, apart from atmospheric discharges. For this, use shielded cables on long sections (50m +) and ground them properly.
Otherwise, after each major storm, the cameras, AP and switches are manually reset. And for unloading directly into the NN network, there are no strong ones. You need to spend a penny after a storm or disconnect everything before the storm.
Another surprise that can happen is trivially that they can swell electrolytes or oxidize unleaded tin
I use a solution of alcohol and rosin on the whole PCB without oxidation for the oxidizing tin in the cameras. It solves this problem for years and until I was surprised myself, what conditions can be tolerated by an outdoor indoor camera mounted under the roof without prejudice
Comments
- If I was to re-register my device in this technology today, I would look for a microcomputer with i5u with a lot of USB or SATA ports working under Vista or 7GB with 2GB RAM. I would not want to, because this freak lives on my own life and wastes electricity to execute commands that the user did not order. Linux? Why not, it is not so scary and it is very flexible. Only is there any sensible software on the ropes?
- As for HDD, it is worth checking the distribution of sectors on the disk before the purchase of a note, or the logic of the disk does not somehow cheat the SATA / ATA controller in terms of their physical distribution. It depends largely on whether the HDD will live 15 years of continuous work or 2 and will crash with a bang.
- In the role of overhead lines, the overhead cables of the tepsy 3 pairs are great - just like they used to go after the poles. They have a screen, 2 pairs for transmission and one for power supply.
Check out Zoneminder.
