Jump to content

mkkoskin

Manufacturers
  • Content Count

    123
  • Joined

  • Last visited

Everything posted by mkkoskin

  1. mkkoskin

    can't find ip cam on network

    http://www.hikvision.com/en/us/support_more.asp?id=174 You might have to change your computer IP to same network to configure camera, to set DHCP on before you see it in your router settings.
  2. mkkoskin

    poe or power supply

    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
  3. You could use any camera and external I/O unit with a relay to cut/uncut the power. I've not heard of a camera that has any wake-on -support. We have used Moxa ioLogik E12xx models (Ethernet DI/O). I have only used it thru our VMS, but it has a nice web-ui aswell. And there are probably tens or hundreds of other just like those, with varying pricerange.
  4. 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
  5. mkkoskin

    CBR vs VBR

    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.
  6. mkkoskin

    switch blackout?

    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.
  7. mkkoskin

    CBR vs VBR

    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.
  8. mkkoskin

    two switch questions

    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..
  9. mkkoskin

    CBR vs VBR

    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.
  10. 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.
  11. Old thread about similiar problem that might be of help: viewtopic.php?f=19&t=39160&hilit=image+green
  12. 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.
  13. Using it with our own developed Ksenos VMS. According to forum rules i'm not allowed to link to our page though
  14. mkkoskin

    Installation using CAT5

    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.
  15. Is it connected to PoE? Maybe not enough power for the camera + ir lights?
  16. I've never used Netgear switches, but I know TP-Link TL-SF1008P 10/100Mbps switch (http://www.amazon.com/TP-LINK-TL-SF1008P-100Mbps-8-Port-802-3af/dp/B003CFATT2) is reliable as we've used them in our systems a lot. With 3 cameras, you should be ok with just the 100Mbps ports, unless you go overkill 35Mbps bitrate per camera
  17. 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.
  18. Ok next thing to try is factory reset once more, assign ip 192.168.1.100 to camera and 192.168.1.101 to nuc, then disconnect your nuc and the camera from the network and connect the camera straight to the nuc. See if it works then. That eliminates the router from between atleast.
  19. 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.
  20. No idea why the camera shows up 2 times in the arp-scan, usually thats the case only if it has 2 different IPs. 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? 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.
  21. 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..
  22. 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.
  23. 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.
  24. 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 )
×