Privatteer

Took a gamble and tried a NVR that has gone into a reboot cycle during camera setup. Seller has ignored requests for firmware/reset to factory default procedure. Chipset seems to be a HI3520 DRQCV200 CR4131503. Board claims to be a HI3520D_v2.2.5. Tried a recovery file I found via a thread from http://www.urcctvstore.com/Download.html# just to see if it would detect it but did not work. Anyone recognize the unit?

Its been a long time since i worked on one but if I remember right the fans on the DS2 are a 3 wire type. If the motherboard does not see the correct rpm it shuts down.

Urcctv N6100-8EL. I've got 2 Hikvision camera working as wanted with motion detect. However I also brought two ACTi cameras thinking they would be better quality (not) and I can't get the N6100 to register motion from either. Acti-D55 and D72A. Motion is registered at camera and I've currently got it set to trigger url command 1,2,3 in events. Other options include: HTTP CGI 1 or 2 message SMP server HTTP server Any one tried this combination before and got it to work?

Well, short story Ebay seller "Amistic" is one to avoid. Refused to supply firmware files. Has employed every delaying tactic possible for refund process. Currently not accepting returned item.

I tried a new/different harddrive first no change. At this point I have not loaded any firmware. I have only tried the usb boot loader, with no firmware file added to usb, to get to the stage of loading firmware and it was not detected.

I could be getting confused with another system but I'm pretty sure I configured an audio alarm on motion detection in Exacq pretty recently. Under event actions? Perhaps that was the Bosch DVR, I work on so many. I'm positive the camera did flash red on the map on motion detection. If you have the standard vivotek day cameras there is no night mode. Just a brightness setting. If they are day/night you might need to log into the actual camera webserver to set the threshold probably.

Reboot the machine into admin mode and use the cmd prompt to ping the camera address's. "connection faulty" usually means the Dibos cant talk to the camera via the network. I suspect they will not respond as there is a network issue. If they do respond try opening IE when in the admin mode and logging into the camera via the browser. Connection faulty will also come up if you have a wireless link or similar choke point and are trying to send data faster than it can handle.

With 20w a camera I can understand going with a separate power supply a lot of switches are only rated for 15w per port. Beside even after buying the extra cable it can be cheaper than a POE switch sometimes. 24vAC over 70m(225f) is going to have a volt drop of around 1.6v if you use 24/02 fig8. Most AC transformers sit a volt or 2 higher than their rating so with a 24v transformer you will be fine. 12vdc has a lot smaller tolerance and you would be too low at the far end unless you went for bigger cable.

I found the actual configuration of Exacq easy if your used to working with digital video recorders. Arranged logically and clear descriptions. More trouble on some of the individual cameras as it took some playing to get the right settings for day/night etc. As I brought the server from the dealer it was already installed with windows/exaq and some default user accounts setup.

Right, I found the client log file. Not were I was expecting it. 8/4/10 is when I received it. This message seems to correspond to times its crashed. 8/13/2010 10:36:33 AM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 7/29/2010 6:07:15 PM LogPI Warning Starting Log Manager 4.2.4.22317. 7/29/2010 6:07:15 PM StreamPI Warning User manager migrated legacy user account data. 7/29/2010 6:07:15 PM StreamPI Error Error loading license key - failed to locate file (err 2). 7/29/2010 6:07:15 PM StreamPI Error Failed to load any license key on startup. System unlicensed. 7/29/2010 6:07:15 PM EvtLogPI Warning missing log records, current[0] oldest[1] 7/29/2010 6:07:15 PM ExportPI Warning Failed to load configuration. Using default configuration. 7/29/2010 6:07:15 PM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 7/29/2010 6:07:15 PM NotifyPI Warning Either no configuration or an improper configuration was found, continuing with empty configuration. 7/29/2010 6:08:31 PM StreamPI Warning Successfully updated license key. 7/29/2010 11:10:34 PM ArecontPI Error Device(172.16.1.14): Channel 1 stream socket timeout (10 secs). 7/30/2010 1:40:37 AM ArecontPI Error Device(172.16.1.10): Stream socket timeout (10 secs). 7/30/2010 2:01:19 AM ArecontPI Error Device(172.16.1.10): Stream socket timeout (10 secs). 7/30/2010 3:21:52 AM ArecontPI Error Device(172.16.1.11): Channel 1 stream socket timeout (10 secs). 7/30/2010 10:49:59 AM LogPI Warning Stopping Log Manager. 7/30/2010 10:51:09 AM LogPI Warning Starting Log Manager 4.2.4.22317. 7/30/2010 10:51:09 AM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 7/30/2010 10:52:21 AM LogPI Warning Stopping Log Manager. 8/4/2010 10:45:19 AM LogPI Warning Starting Log Manager 4.2.4.22317. 8/4/2010 10:45:20 AM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 8/4/2010 10:45:28 AM Core Warning system time changed by 5 seconds 8/4/2010 8:49:23 AM StreamPI Warning Updated system time zone to (GMT+08:00) Perth. 8/4/2010 8:51:10 AM IPCamDetectPI Warning Rescan requested while another scan in progress. 8/4/2010 10:03:03 AM ArecontPI Error Device(10.0.2.15): Stream socket timeout (10 secs). 8/4/2010 10:03:36 AM ArecontPI Error Device(10.0.2.15): Stream socket timeout (10 secs). 8/4/2010 12:16:34 PM ArecontPI Error Device(10.0.2.13): Stream socket timeout (10 secs). 8/4/2010 12:52:32 PM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/4/2010 12:57:05 PM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/4/2010 4:32:02 PM ArecontPI Error Device(10.0.2.13): Stream socket timeout (10 secs). 8/4/2010 4:32:07 PM LogPI Warning Stopping Log Manager. 8/9/2010 8:35:45 AM LogPI Warning Starting Log Manager 4.2.4.22317. 8/9/2010 8:35:45 AM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 8/9/2010 8:35:55 AM Core Warning system time changed by 3 seconds 8/9/2010 8:36:10 AM ArecontPI Error Device(10.0.2.14): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/10/2010 1:44:21 PM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/10/2010 1:45:53 PM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/10/2010 2:07:27 PM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/10/2010 2:10:27 PM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/10/2010 2:12:31 PM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNABORTED. 8/10/2010 2:15:48 PM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/10/2010 2:53:14 PM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/10/2010 2:53:23 PM LogPI Warning Stopping Log Manager. 8/10/2010 2:57:28 PM LogPI Warning Starting Log Manager 4.2.4.22317. 8/10/2010 2:57:28 PM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 8/10/2010 2:57:38 PM ArecontPI Error Device(10.0.2.14): Stream socket timeout (10 secs). 8/10/2010 2:57:38 PM ArecontPI Error Device(10.0.2.13): Stream socket timeout (10 secs). 8/10/2010 2:57:49 PM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/10/2010 3:03:09 PM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/10/2010 3:08:30 PM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/10/2010 3:13:51 PM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/10/2010 3:17:06 PM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/10/2010 3:17:16 PM LogPI Warning Stopping Log Manager. 8/10/2010 3:18:46 PM LogPI Warning Starting Log Manager 4.2.4.22317. 8/10/2010 3:18:46 PM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 8/10/2010 3:23:15 PM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 8/10/2010 3:29:10 PM LogPI Warning Stopping Log Manager. 8/10/2010 3:30:35 PM LogPI Warning Starting Log Manager 4.2.4.22317. 8/10/2010 3:30:36 PM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 8/10/2010 3:40:28 PM StreamPI Warning Client 127.0.0.1 disconnected due to key exchange timeout. 8/11/2010 1:57:01 PM StreamPI Warning Client 127.0.0.1 disconnected due to key exchange timeout. 8/13/2010 9:32:34 AM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/13/2010 9:34:45 AM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/13/2010 9:45:43 AM IQeyePI Error Input(Input 1): Resetting max downsample factor to 4. 8/13/2010 10:33:34 AM ArecontPI Error Device(10.0.2.15): Config socket connect error (10060) - GET /getreg?page=3&reg=122 HTTP/. Delaying reconnect. 8/13/2010 10:34:57 AM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET. 8/13/2010 10:35:06 AM LogPI Warning Stopping Log Manager. 8/13/2010 10:36:33 AM LogPI Warning Starting Log Manager 4.2.4.22317. 8/13/2010 10:36:33 AM ExportPI Error Error in executing media test (size query) for status refresh (error 255). 8/13/2010 10:36:33 AM IQeyePI Error Input(Runway Camera ): Resetting max downsample factor to 4. 8/13/2010 10:36:43 AM Core Warning system time changed by 3 seconds 8/16/2010 9:12:41 AM StreamPI Warning Client 127.0.0.1 disconnected due to read failure - WSAECONNRESET.

Recently decided to do a 6 camera site with Exacq after playing around with the software on a single cam license. Requested desktop version of the server and ended up with the 2RU server but never mind. The issue I am having is the client on the server (V4.2.322315) edvrclient.exe is intermittently crashing. Say after 6-12 hours. Only have 3 cameras on it currently as still waiting on the rest of the gear. 2 arecont, 1 IQ700 3MP set to motion detect/15FPS. Did have the Map enabled with a JPeg of site, just deleted that. Not made any changes to how OS has been setup. After sending 2 DOA cameras back I'm not getting too far with the supplier so was hoping someone might have a suggestion.

Of course, its on the office bench.

I have only played with a 1 camera self installed copy of the software on pc before so yes I am new to Exacq. I may have missed it but I could not find any program logs in the client interface or directory when I looked. Yes I was logged in as the admin user. The only log files I located were stored in the server directory under /logs. I'll have another look on Monday as I will have a bit more time. I've left the machine running over the weekend to see if it occurs again. Installer, I have done IP cameras, networking etc. ie indigo/bosch/axis/vivotek right to the old stuff like Maxpro 1000 programming. Had no issues getting the cameras connected, web server started, map loaded, motion only recording etc. 1st DOA camera would not power up and was missing the sensor dust cover when I opened box, 2nd had random green/yellow squares over the picture that a default and firmware upgrade did not fix. Tested its lens on another camera. I requested "IPS-2000-DT", and was told suppliers part number for it was "XN64S-02000S" and received "IPS-2000-R2". I missed the 2RU in the description in their quote so partly my fault but changing part numbers around makes it easy for stuff ups. Edit: As supplied the client auto starts on the server. Its only a small 6 camera site with 1 monitor. Btw its a 4000km trip to do training so a little beyond budget.

I asked for http://www.exacq.com/products/desktop_ip_server.html Received http://www.exacq.com/products/2u_ip_rackmountserver.html Not critical but the desktop model would have suited the location better. Server only shows the client connecting/disconnecting. Cant find any logs for the actual client... "It must be my fault they tested it before sending" Just like the 2 DOA cameras.

http://www.veracityglobal.com/products/ethernet-over-coax/highwire-poe.aspx Used a couple of these. Simple, and gains you a POE connection for the camera. Pros: Can work out cheaper than pulling new cable, especially in difficult buildings. Can go with a cheaper non POE switch. Longer cable distance than standard Ethernet possible. Cons: Extra item to fail Need space in camera housing, or somewhere you can get to for the extra box at camera end. Existing or new 12/24v power supply needed

I'm not sure if any one else is selling Exacq yet in Aus but when I was looking into it I came across a company called Zoneaps. I ended up with a login for several days for their office exacq server, the client and a few other documents that helped.

Mozilla Firefox (another free browser) might work had good success when newer versions on IE wont load a embeded web page. Just make sure you click yes when you connect to the DVR and it tries to load the java files. I assume your using Sightboss until they release an update you probably wont be able to get the installer to run. .

I would be bit cautious using any wireless system that transmits in 802.11g for security, especially for an airport. Just a little bit to easy to get a receiver for 2.4GHz gear plus the interference issues. I've used Airmux-200's http://www.airmux.com/products/airmux_200.htm in some pretty harsh environments in North Australia and found them reliable. Available in 5.4 and 5.8GHz. Motorola make a good product in their PTP300 to PTP600 range but its 4 times the cost of Airmux. I only use it for jobs needing guaranteed uptime. One thing to be aware of is 5.4Ghz in many places has a weather radar band/channel right in the middle. If your in one of the regions that does you need to be able to lock those channels out.

Other option depending on why you want the axis would be to leave the DS2 in, and connect the axis encoder to its loop through terminals. Then you would still use the current PTZ keyboard to control those cameras. Not sure about the DS2 keyboard, but most are rs232/485 and you could connect it to an IP encoder to get to to where the axis control center is.

Take a look at Megapixels posts here. http://www.cctvforum.com/about11322-0-asc-75.html http://www.cctvforum.com/about11322-0-asc-105.html The Bosch one is only 36x (122mm) great camera but 1km max for anything other than a general view. Il'd be saying 2000mm like ZMtech, used similar (think Avenir brand) to the one he linked to in a Pelco PTZ enclosure before but wind vibration was a ***. http://www.pelco.com/products/default.aspx?id=178 This was the PTZ unit we used, had 20KG counter weights and an custom housing to fit the lens and we still had issues with anything over 12knotts wind. Height is also a consideration at that distance as need to be 20-25m above sea level to stop horizon obscuring. All depends on how close you want to be able to zoom to as well, see a container ship at 8km or see a person on the deck is a big difference.

Most digital video recorders support IP access either via software or a web browser. The better quality ones all have loop through terminals as well. Depending on why you want to go IP why not get a hybrid similar to below. http://www.exacq.com/products/2u_hybrid_server.html There is plenty of other brands can use as well.

Might be their history motion detect function. Can load recorded footage and see where the camera thought it has seen motion.

Done a couple on that sort of towers, analogue cameras. Pay attention to the earthing and not had a problem. Just started using the Bosch I500's so its too early to tell long term stuff.. However they seem to be built well, and getting a lot less image shake when mounted in areas that are windy compared to a pelco spectra unit on the same light pole. Worse problem I have had is getting their propriety codec to install properly so I could view the mpeg4 stream on laptop. Xp machine is fine but the vista one is still a no go.

http://www.cctvforum.com/about16453-0-asc-0.html Thread on it not that long ago.

Its a once in a blue moon event that a camera I have backfocused in the workshop has exactly the right amount of zoom at installation. But then again I'm a perfectionist that hates cameras looking at meters of worthless wall/ceiling. Generally is practical and quicker for the apprentice to do the focusing and me to sit in the control room/nearest ethernet switch on 2-way. When its not I use a standard 50V dc POE injector running off a 12v dc buck/boost converter and a cross over cable. Bit bulky but works.