Jump to content

mkkoskin

Manufacturers
  • Content Count

    123
  • Joined

  • Last visited

Posts posted by mkkoskin


  1. 2. It is not the software that detects the licenses plate, its the camera, if you need an LPR Camera or you can actually tweak up almost any IP camera to work but you need to realize that at night time you will be ONLY picking up Licenses plates and nothing else, everything will be black except for when a car passes by in a particular area so you can catch the licenses plate, thats why they call it "Licenses Plate Recognition Camera"

     

    Actually to analyze and list the license plates you do need a software, afaik , camera can capture them, but doesnt do anything with them as it recognizes them.

     

    Very nice article about LPR (by buellwinkle): http://www.networkcameracritic.com/?p=2177


  2. Hi all, im going to upgrade my exsisting coax setup which has 4 cams. I already have three i.p cams + a ptz ip i have bought. I was going to use my pc but have decided to use a nvr box instead so its always on. Im thinkning i could either use a spare pc or buy a nvr to work. Im pretty sure the cameras are all onvif i have and they range from 3mp to 5mp. Ideally id like somethign i can use upto 8 cameras on and record about a months worth of data. Im happy to fit my own hdd to something. any recommendations? budget upto £300ish with no hdd's £450 with hdd. Ideas?

     

    thanks guys

     

    I dont really know anything about budget standalone NVR's, but make sure the cameras are really ONVIF conformant if you're going for NVR that supports ONVIF but has no other support for the camera/model you have. You can search the camera model from http://www.onvif.org/FindaProduct/ProfileProducts.aspx


  3. "Basicly CBR (Constant Bitrate) will guarantee you better quality at all times, but at a higher bandwidth cost. All the systems we install, we install with CBR."

     

    Our testing disagrees with this. Also, your description is technically incorrect.

     

    CBR does not guarantee better quality. It guarantees the bit rate to be maintained. The 'quality' of CBR only comes from setting a very high bit rate to cover the worst case / most complex scenario.

     

    If you set the CBR bit rate too low, you will have poor quality. If you set the CBR bir rate too high, you will waste bandwidth / storage.

     

    VBR, by definition, does guarantee quality. It locks the quality / compression / quantization level, allowing the bitrate to fluctuate depending on the complexity of the scene.

     

    VBR is the way to go. In our testing of dozens of leading cameras, it does not have issues maintaining quality when motion increases, because the quality level is locked, it simply increases bandwidth of the stream.

     

    Thanks for the corrections. Obviously bit rate has nothing to do with the level of quality, but maintaining it, i though i made it clear with my explanation. But unlike your tests, we've had different results.

     

    On busy malls VBR does not seem to always keep up and since there is no reason to limit bandwidth, CBR worked better. So in these cases VBR did not guarantee quality, not well enough.

     

    But there are 2 settings because one works on some cases better then the other, trial and error, testing which one suits better is the way to go.


  4. I have two 10/100 switches 5 x 3mp cameras. Switches are connected in series to router. Switch A ->Switch B -> Router.

    I noticed disconnection problems because the nvr monitor shows a frozen picture for the cameras at A (meaning the connection has been stopped/disconnected). Any idea why this would happen? Average current transfer rate is just 3000kb/s for the cameras.

    Once I unplug Switch B and reconnect, the cameras work again.

     

    In earlier thread you were asking if you should get 10/100/1000 switches instead, i see you went with 10/100.

     

    Are the ports in those switches actually 100Mbps ports or is the whole switch capacity 100Mbps and each port only 10Mbps ? If this is the case, one port probably cant handle the whole other switch. Try unplugging all but 1 camera on switch A and see if the problem is still there. If the problem doesnt occur with one camera, try plugging in another.


  5.  

    On my ACTi 3MP domes I set:

     

    Encoder Type: H.264

    H.264 Profile: High Profile

    Resolution: N2048X1536

    Frame Rate: 15

    Video Bit Rate Mode: Constant Bit Rate

    Video Max Bit Rate: Unlimited

    Video Bit Rate: 6M

     

    Question: Is the video bit rate setting @ 6M overkill in your opinion? Should I lower it to 4M?

     

    I think 4Mbps should be enough for 3MP at 15fps, but really it's all about the amount of motion and lighting etc. Trial and error, you can lower it to 4Mbps and see how it handles fast motion under lowlight conditions, if there is no blur/pixelation in the stream, its sufficient.


  6. Yes it is apparent that gigabit switches would have no problems with most modest setups however my question is: Would my 6 x3mp camera operate well with just 10/100 switches? The cameras so far run at 4000kb/s.

     

     

    I have a switch in my garage to handle 3 cameras in that area and I have a 24 port desktop switch with 12 PoE ports. I have the switch in the garage with a gigabit uplink going into my gigabit 24 port switch. Both are managed, but that doesn't matter.

     

    Heck, in one install with about 16 cameras, we have several locations, each linked with 100Mbps extenders to a gigabit switch at the central location. With only 4-5 cameras per 100Mbps path, it adds up to 400Mbps on the gigabit switch, no lost frames, everything records as you would want.

     

    Probably would, but price difference between 10/100 and 10/100/1000 is so marginal it's not even worth pondering which one to get. Especially if you're going to have the switches linked (Garage -> House -> Router). This way the first switch (garage) handles load from 3 cameras and the house switch handles load from 6 cameras (garage+3cameras). It might be enough for now, but when you notice you're not getting high enough quality from camera with 4Mbps and switch to 8Mbps and grab few extra cameras, 10/100's wont cut it for long..


  7. Basicly CBR (Constant Bitrate) will guarantee you better quality at all times, but at a higher bandwidth cost. All the systems we install, we install with CBR.

     

    Example to explain it:

    You have a camera watching a door. Someone enters and rushes thru the door quickly, you would like to see who it was and get a detailed image of his/her face.

     

    Case VBR (Variable bitrate): While there is no motion, bitrate is very low, and when someone enters thru door, camera raises the bitrate to handle all motion. This might cause blurriness/pixelation in the beginning of the motion, if the motion is short enough (rushing thru door, enters and leaves camera view within second for example) image might be very blurry/pixelated and person not recognizable.

     

    Case CBR: Even when there is no motion, bitrate stays the same, when someone enters thru door, bitrate is enough to handle the motion and even if the person is visible only for a second, image is as clear as it is without motion.

     

    So if you have a very limited bandwidth, you can try to go with VBR, but there is always a chance its wont capture everything as sharp as CBR would.


  8. Thanks

    That's good to know.

    I've used only two different fisheyes. I've used Geovision which work pretty well as far as panning and presets go using their software but I haven't tried them with another vms. I've also just recently used vivotek fisheyes with the VMS we use on jobs and found them not user friendly.

    But I haven't messed with them too much.

    I haven't used any Axis cameras yet but it seems to me, they are the superior brand in most ways.

     

    What VMS are you using the fisheye with.

     

    Using it with our own developed Ksenos VMS. According to forum rules i'm not allowed to link to our page though

     

    So do I understand correctly that you are not actually dewarping the stream within Ksenos, but merely selecting the already dewarped stream via ONVIF? As I mentioned, I cannot seem to get Avigilon to do what you are doing, and what a $3 Android App (IP Cam Viewer Pro) can do.

     

    Are you planning to incorporate dewarping capability within Ksenos so that you can take a warped stream and dewarp in realtime? For example, either a live stream from the camera, or a recorded stream which can then be played back and dewarped to any view the user wishes? Mobotix does this very nicely, but it's all done inside the camera. The benefit of course is that while you are monitoring, you could be viewing a dewarped view of a single doorway, for example, but you are actually recording the full, unwarped stream, so that you can always replay to see what you might have missed while you were looking at the door. Definitely a benefit over a standard PTZ camera.

     

    We do support dewarping just the way you described it. Stream from camera is recorded as warped and can be viewed dewarped, and/or used like a PTZ camera, in live or recordings.

     

    But the reason of this post was that Axis actually does the dewarping and offers different ONVIF profiles/streams with already dewarped image. Panorama, Single view, Quad view atleast. I dont know how Avigilon handles ONVIF cameras and profiles, but if you're able to change the used profile (I think there was 6 or 7 different profiles), you should be able to see the different 'modes'.

     

    Then again atleast in our case, if only a single view stream is being recorded via ONVIF, only that view is viewable on recordings. So probably the way this should be done is record the whole warped image (via RTSP or ONVIF) and view another stream via RTSP/ONVIF for live use.


  9. I've a GoPro Hero 3+ black edition with 15fps 4K support. It is possible to get live pictures out of it via WLAN, but not via USB. And i'm pretty sure that wont work as 15fps when its still images you load from it. Sure it might do 1fps so one could see 4K image on a 4K display/tv but no 30fps, not even 15fps. The camera doesnt have enough processing power to handle streaming it that fast. Atleast not without hacks.


  10. Thanks

    That's good to know.

    I've used only two different fisheyes. I've used Geovision which work pretty well as far as panning and presets go using their software but I haven't tried them with another vms. I've also just recently used vivotek fisheyes with the VMS we use on jobs and found them not user friendly.

    But I haven't messed with them too much.

    I haven't used any Axis cameras yet but it seems to me, they are the superior brand in most ways.

     

    What VMS are you using the fisheye with.

     

    Using it with our own developed Ksenos VMS. According to forum rules i'm not allowed to link to our page though


  11. Unless you have a lot of cat5 cable laying around, i wouldnt use it. Cat5e gives you 1000mbps (gigabit ethernet) where cat5 only goes to 100mbps (fast ethernet).

    For IP-camera network, cat5 is a big no, you'll end up bottlenecking it at some point for sure. And even then cat6 isn't THAT much more expensive, so worth considering aswell, especially on longer runs.


  12. The whole purpose of this post is just to tell you what i found out while testing this camera. Maybe someone's been wondering if/how it works.

     

    While testing this Axis M3007-PV (http://www.axis.com/products/cam_m3007pv/) I noticed how awesome they've made their ONVIF on it. It's rare that cameras actually work as you'd expect, this one does.

     

    Camera being a fisheye and our VMS having a built in fisheye support, I immediately used this feature, but it is not required for this camera. They actually made PTZ/Presets work like a charm via ONVIF. And that is what surprised me.

    You can select different streams for Panoramic/Double Panoramic views and single views. Single views can be controlled via ONVIF PTZ just like any other PTZ camera, each view remembers the state it is left at.

    For actual real-time monitoring, you can use custom presets which work fast.

    Their built-in dewarping quality is good.


  13. I don't understand. Which camera do you want to read license plates on? I assume the one you have marked as Driveway and in the Youtube it clearly shows your plate number, no? Is the problem at night because that's not in that video for that camera. Clearly the other cameras can't see plates because the cars are going across the field of view, so the plate is not visible. '

     

    Or are you trying to trigger an event off the license plate number, in other words, have it send you a text when a certain plate number enters your driveway?

     

    Yes, you can change lenses on those cameras, but requires specialized tools like a thin #1 Philips head screwdriver

     

    It's your video btw


  14. Could you show a picture from camera to PC instead of camera to tablet? I think it's the app or bad resolution your galaxy tab offers, not the camera. Also, check camera settings, make sure quality is high/maxed, bitrate is high enough (atleast 4Mbps for Full HD resolution with movement).

     

    You can use VLC player on PC to grab the rtsp stream from camera, that should be as good as it gets.


  15. Code:

    nuc@nuc:~$ nmap 192.168.1.100

    Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-13 12:24 CEST

    Nmap scan report for 192.168.1.100

    Host is up (0.0010s latency).

    Not shown: 824 closed ports, 175 filtered ports

    PORT     STATE SERVICE

    7001/tcp open  afs3-callback

     

    Nmap done: 1 IP address (1 host up) scanned in 57.46 seconds

     

    Something surely is incorrect, it seems there are no http port open in the camera. Factory reset the camera and try to put it on DHCP (check the DHCP from camera network settings), the power down the camera (unplug or w/e), power it back up, wait a minute, run "arp-scan --localnet" to figure out what IP DHCP assigned for it. If you can access thru this IP, go to your router settings and make a rule so router always assigns the same IP to this same MAC address.

     

    --Just a guessing below!--

    Trying to figure out why the static ip isnt working makes me wonder if the router you're using allows static IPs at all? If it doesnt allow any traffic from static IPs for some odd security reason, then that might cause it to "lock up". It could be "protecting" the 192.168.1.* network, explains why 192.0.0.* works.


  16. No idea why the camera shows up 2 times in the arp-scan, usually thats the case only if it has 2 different IPs.

     

    Won't I have to change eth0 back to something else? I remember that I had to change it from what CBX told me with:

    nuc@nuc:~$ sudo ifconfig eth0:0 192.0.0.128

    No, this was only a temporary "virtual ip/nic".

    eth0 = your physical NIC

    eth0:0 = the first virtual ip/nic of the physical device

     

    Every setting seems to be ok now. Ping seems to go thru just fine on the second try.

    I have no idea why you cant access the camera over a browser, what does the browser say?

    What does "nmap 192.168.1.100" tell you? (you might have to install nmap, "sudo apt-get install nmap")

     

    Also what are you trying to do with this NUC+Ubuntu+Hikvision combo?

     

    Do you mean by a connection to the internet, that I could include my cam in a website? This would indeed be preferable, because it's a birdy-cam.

    Without gateway, the camera cannot connect to WAN, thus has no access/visibility to the internet, outside your LAN. If your website is in your LAN (some local webserver that is already visible from internet), you dont need gateway for camera, if not, you probably do.

     

    One last step to try is after you've set up the ip to camera (192.168.1.100) is to reboot both devices, just to make sure the virtual ip does not interfere with the setup. Then see if browser connection works.


  17. Depends on your setup, but since most cheap poe-switches are only 100Mbps switch, i'd go with 2x 4+4 (8 port of which 4 poe) and one cheap 1Gbps switch that connects PC to both camera switches.

     

    http://www.tp-link.com/en/products/details/?model=TL-SF1008P (4+4poe, costs around 40-50$, we use this model on small ip camera networks)

    http://www.newegg.com/Product/Product.aspx?Item=N82E16833181229 (5port 1Gbps switch, 30$, just an example, we've used 8port model of this one)

     

    So in total its around 110-130$ for

    - 8x 100Mbps poe slots

    - 8x 100Mbps non-poe slots

    - 5x 1Gbps slots.

     

    If the traffic from cameras is very high, make sure the Gbps switch offers 1Gbps/port, not some total..


  18. If you just want the camera installed locally, no internet access from/to it, you dont need to set the gateway for the camera at all.

     

    The first time you tried to change the ip and lost the camera so you had to reset it, was because you gave it an address from wrong subnet. Your home network is 192.168.1.* and you gave your camera 192.164.1.41.

     

    ipconfig -a does not show the default gateway, "route -n" does, look for a line that says 0.0.0.0 under Destination.

     

    Judging from what you've posted so far:

    Your PC:

    IP: 192.168.1.41

    Netmask: 255.255.255.0

    Gateway: 192.168.1.1 (Indeed, this is the router ip you used, not the broadcast address from ifconfig -a print)

     

    So camera ip settings should be for example:

    IP: 192.168.1.100

    Netmask: 255.255.255.0

    Gateway: 192.168.1.1 (this is optional, only required if you want the camera to have a connection to internet, rather than LAN only)

     

    Since you can ping the camera, you should be able to access it thru browser aswell.


  19. To explain this to op and anyone else reading this:

     

    In the beginning OP has a 192.168.1.0 network and PC in this network (probably the 192.168.1.38 IP). By default Hikvision cameras have static IP 192.0.0.64.

     

    So since (i assume) this is a small home network, there is no network management inbetween, and connecting from 192.168.1.0 network to 192.0.0.0 network is impossible.

     

    The command CBX gave makes a virtual NIC on top of the physical one, with IP 192.0.0.128, which can be used to connect to the camera at 192.0.0.64.


  20. Good to see you figured it out. Just be glad Hikvision, unlike Dahua publishes documents like this. One reason I like Hikvision better than Dahua although both make good cameras, Hikvision seems to understands our needs better.

     

    Here is a Dahua IPC HTTP API V1.00:

     

    https://mega.co.nz/#!agAxwIQK!vJH9Qurd6rixvOAVEiKpfq5q0a2uTIK159V1B9RbHEo

     

    (Link is safe, if you're not familiar with Mega, now would be a good time to get familiar with it )

×