Recent content by yorkie

Just tried the web GUI and it seems to be normal... except that when I tried to export the device parameters (as a download file) that triggered a reboot. When it had fully rebooted I tried again and got the same result. Also, the system time is an hour ahead despite me having DST turned off...

At the moment I've not logged in to see the web GUI, but the local UI seems to be as expected. EDIT navigating in the browser to the Web GUI and it does bring up a login screen, though I have not gone any further on that as yet __ As for "actually working", it still seems to have a fairly...

Doing the firmware transfer has gone through but it still does the reboot loop. At one point it shows a prompt for a list of the system commands, and these are what comes up: Enter 'help' for a list of DVR/NVR system commands. # psh open !!! ----------<1> tar all res ---------- cpu_name...

Doing a system restart from having erased the environment variables is still causing a reboot loop... but with a boat load more feedback through the terminal software to the point where there is a considerable lag. Also, the screen resolution still changes from 1024x768 to 1920x1080 during boot...

Yesterday I put in a replacement capacitor, at the same value as all the ones around it (bit of a guesstimate there, but worth a crack) - and I also noticed that the connection for the capacitor also included a link through from the topside of the motherboard to the underside and yet part of the...

I've only just seen your reply, so I'll have a look at this either during the daytime or on sunday. I've had the motherboard out though, as I was going to go over it with a magnifying lens to see if there was a cracked solder joint or similar.... and it looks as if somebody has been at this...

well thanks for helping up to this point anyway. If it had been doing this loop right from the outset then it would have been easier to write it off, but because it had originally started up and got to the grid screen (complete with a password reset) it's annoying for it to now be pretty much...

Turns out I had made a note of the firmware when I first got the NVR - 4.61.020.... I have tried flashing that version back onto the NVR, it went through OK but still got the same reboot loop. I have then tried flashing firmware 4.61.025 onto it... again, the update went through fine but it is...

It has gone straight to an update action. This program will upgrade software. ******************************************************* * ATTENTION!! PLEASE READ THIS NOTICE CAREFULLY! * * Don't reset machine,or anything that interrupt it. * * The upgrade process must finish in 10 minutes...

Right well I just had a sudden DING moment and tried a little alteration.... I have opened up the NVR case and unplugged the 5-pin lead that goes from the inside of the Serial port, turned it roud, and plugged it in the other way; then I have the USB-Serial converter plugged in directly without...

I have the Null Modem Cable and the USB-to-Serial (CH340) converter all plugged in to the NVR. Windows device manager shows the CH340 as plugged into COM5 (I changed it to a USB directly on the motherboard). Open PuTTY, input the required settings under the "session" tab with the 'Serial' box...

Right well I've given it a try with the current cable and got nowhere. Windows Device Manager shows the cable as working properly under "Ports (COM & LPT)" with it's proper name "USB-SERIAL CH340" and shows it being on COM4. Started PUTTY and set that to serial and with the required...

It's a CH340 type cable, if that means anything... hardware ID details being "VID_1A86&PID7523&REV_0254".... just been hunting for drivers to get it working. I believe it's most likey a standard cable not a null modem one - if you're thinking the same thing then I'll order a null modem cable...

I ordered one so that the 9-pin end would be the right gender to fit into the NVR.... I suppose I can connect it up and see if any data comes through, if not then I'll get a null modem cable too

Right I see, so kinda similar to a LAN crossover cable, but with a few extras. The USB-RS232 converter I got didn't say specifically that it acts as a null modem, but the listing mentions "Support automatic handshake protocol" though I suspect that's a variation of plug and play.