On my QNAP NAS, using either the ONVIF or Generic RTSP camera selection, the camera connects OK, streams for 10-15 secs, then stops. So I've got one camera that I can use for continuous recording but no motion detection, and one that can do motion detection but only very erratic recording.ĭoes anyone know how I can squeeze the two together to make one perfect unit? Reply Deleteīubbah - have you successfully connected the H502W to your Synology SS, and does it stream steadily and reliably?
I have to believe the problem must subtly lie with the QNAP H.264 decoding - though it works AOK with the IPCC-B10.
Dericam setup with nas pro#
It streams well and reliably via VLC, ONVIF DM, its own live view - but annoyingly it only occasionally connects to SS Pro on my NAS box, using the various ONVIF flavours and even the Generic RTSP choice. It's actually a pretty good camera in terms of video quality and features.
Dericam setup with nas manual#
Despite getting updated firmware from IP Cloud Camera, and even flashing it with the AM-Q6320 firmware linked on this site, and some poking around in its internals.īased on checking out the user manual for the Dericam H502W, which shows it features a couple of motion detection actions which could be used as recording triggers on the QNAP SS Pro - an FTP action that includes specifying a destination folder (unlike that on AM-Q6320 and IPCC-B10) and an HTTP action, and the positive words here, I bought an H502w to experiment with. So - having bought an IPCC-B10 IP camera for my QNAP NAS Surveillance System and found it works very well for continuous recording under its ONVIF feature set - I haven't been able to get motion detection recording working. The HackMaster files can also be obtained from the original article: Hackmaster).Ĭlean-up.bin : Cleans up all traces of hacks (including the Hackmaster), and restores the camera in its normal state. No_hack.bin : Removes all the hacks but leave the enabler intact (i.e. Since it's only occasionaly needed, it will self-destruct on restart. The status of the SD mount is logged under /tmp.įtM.bin : Enables the unrestricted MayGion FTP daemon (login: MayGion, password: ).įtB.bin : Enables the basic FTP daemon which uses the admin login MSD.bin : Mounts the SD Card for access via FTP (e.g. Ocx.bin : Removes the ocx2.exe file from /www (saving 600KB of space), and provides an Internet access to this file instead. Check the log under /tmp to verify if the installation was successful.
Dericam setup with nas full#
It is reversible thanks to a clean-up file also provided.ībx.bin : Installs the latest full Busybox which provides a more completes set of linux commands. It is based on fw v.5.60 but will remain active after a traditional firmware update. Inject.bin : This is the "Hackmaster" module, which opens the camera to further hacking via the other files below. Each file has a specific purpose and the System Information panel will show which ones are active. The files must be first renamed as app.bin to be installed like normal application updates from the IP Camera interface. The hacks below are an extension of this simple idea. Once a terminal access is possible via telnet, the possibilities are endless: change the services loading at startup (including telnetd itself) via the file /etc_ro/rcS, use a different ftp deamon (MayGion unlimited fd, or restricted ftpd) The /app folder contains typically 3 files loaded when the camera is powered on:Ĭs.ini -> the current config file loaded by csĪ universal way to talk to the camera is to replace its cs file with another one containing a valid script, such as the following that loads the telnetd daemon:Ĭp /etc_ro/rcS /tmp/eye/app/. This post is based on the information found in macmpi's post on Before performing any firmware change, make a backup of firmware files, including the board.dat file,Īnd make yourself familiar with recovery options.
0 kommentar(er)
