apopleptic
Members-
Content Count
9 -
Joined
-
Last visited
Community Reputation
0 Neutral-
apopleptic started following Super Mini NVR Configuration problem
-
Super Mini NVR Configuration problem
apopleptic replied to yacinemi's topic in Digital Video Recorders
Hey, Thanks for the help, I was able to get the vmeye working on the phone by reading your post. do you know if it is possible to remotely view the NVR on a computer browser? Thanks in advance. -
" title="Applause" /> Thanks so much for posting this. I had not been able to locate the onvif one and had asked after is a few times. Fingers crossed it works for me.
-
Strange to see that you and jovanardi loose the ONVIF protocol. I have all previous left when I add a new one? Perhaps it was the order that I did it? Have you added all of the protocols? or just the I12? It is strange if you didn't loose the option. My option Onvif also disappeared. I would love to add it back since I have two cameras that are no longer showing up at all, but no one seems to know how.
-
I don't know about streaming one channel from the NVR to VLC since that is like a stream of a stream and it sounds ____ to me, but depending on your camera, they broadcast an RTSP stream or two. One of my cameras uses rtsp://192.168.1.11/0 for the main and rtsp://192.168.1.11/1 for the secondary stream and another uses rtsp://192.168.1.21/live0.264 and rtsp://192.168.1.21/live1.264 respectively. Load Onvif Device Manager onto your computer, see if your camera is listed and then select the link for live video in the program. At the bottom of the screen it should show you the RTSP link you would need to input into VLC. If your camera isn't listed, then IDK.
-
You must find the files and then load them as updates either through the web interface, or on a USB attached to the unit. I have never found a list of them all, only the few that were referenced on here. Mostly from Russian websites selling versions of this system.
-
Okay, new unit, starting from scratch. managed to update the firmware and it's showing V4.0[20150124] now. I added i8, i9, i12, i13 and i18 (onvif is no longer listed) and now have several cameras that allow me to set the motion detection as i9 or i12, but also several others that do not show at all in the search. I added a few with RTSP but even with that they do not show up on the monitor connected right to the DVR and certainly no motion detection. What other protocols should I load to try and get these cameras working? and why is there never an attachment on the email that the NVR sends no matter what options are checked? and why can't I make it record all the time, but mark where it is motion detected? It doesn't seem to work that way. I also have two cameras that will not do DHCP. When I try they just both keep reverting too 192.168.1.168 and causing IP collisions. They are the ones that right now I can connect to with RTSP but only if I manually set the IP on the cameras and unselect DHCP. If I try setting the DHCP server to hand out any other IP addresses to the cameras and set them to dhcp, they will both reset to 192.168.1.168 even though the DHCP will say different addresses. They do have different MAC addresses, so I don't think that is it. If I do not set anything on the DHCP server and set both cameras to DHCP the router will show only one of the cameras as 192.168.1.168 (whichever was plugged in first) and not notice the other one at all. but the web interface will flash from one to the other randomly.
-
Yo Frank, that is what we define "completely bricked" in factory. It happens when the updated file is not correctly written onto NVR flash, maybe USB plugged out too soon, maybe power is not stable at that time. but if it happened then NVR can only be returned to factory to refresh program with the machines in factory. I believe the time stamp in your NVR stopped moving? Frank, you might not be as stuck as it seems. When I was in this state I was able to update the firmware by formatting a hard drive fat16 and putting the update files on it and connecting it with eSATA. I was then able to connect with telnet and update the machine. After this the USB is still dead so I could not configure the NVR but I was able to log in through Internet Explorer on a computer and connect the cameras. I can record on the eSATA drive with all 4 cameras, but with HDMI connected to a TV only 2 cameras are displaying and I am unable to use the mouse to configure the device (since the USB has power but is not working with any devices.) To me that means it's not "completely bricked" and it seems almost 100% that it is just a messed up line of code missing somewhere and nothing you would need to do with a machine in your factory. Mike, Can you please be a little more detailed about what you would actually do if you got one of these back "completely bricked" units at the factory? I feel like it is just not loading the USB driver at all, but I'm not great at linux so I'm still trying to figure that out.
-
I was able to add the i9 and i12 protocols and register the cameras with them. The USB ports are still not working though. Formatted drive, blank drive, usb thumb drive and mouse all light up and indicate they are getting enough power but the nvr acts as if nothing is connected. Through the hdmi and vga two cameras still do not show even though in IE they do.
-
I purchased one of these 8ch mini NVRs from China and had some issues. I was hoping that a firmware update might help with the motion detection and masking issues, as well as hopefully allowing me to attach snapshots to the emails. While attempting to update it with the utility, I managed to brick the unit. I attempted to use the USB recovery method, which went through and indicated it had completed, but after the reboot I still just got a black screen, and the USB was no longer booting. After many attempts, I logged in with telnet and was unable to mount the USB device. tried another USB and also nothing. I then formatted a HDD fat16 and copied the update (restore) files from the telnet instructions and connected the drive with eSATA and was able to use the telnet instructions to complete the restoration process. Reboot and I was able to connect to the NVR through IE and get into configuration. I was then able to update the device to the latest firmware (20150124), load 4 cameras (still no motion detection or anything) and see video through internet explorer for all 4 cameras. Only things I noticed as different with the new firmware is that one camera is now showing up as ONVIF when it was previously I9, and the MAC address changed which resulted in a new IP instead of the static IP that was previously handed out. When I connect the NVR with HDMI to my monitor however, the USB is still not working. If I connect the mouse, the light comes on but I cannot move the cursor or click. And I only get display from cameras 2 & 3. If I try to connect the drive as USB instead of eSATA it no longer registers as having the drive attached. Thoughts?