Looks like it works like intended and that there was an oversight on my part.
I looked at the source code of the web interface page with the java script functions, and the input field and the range test function for "sn1_md_delay" has a maximum of 999 seconds. After changing the source to allow a range up to 99999, I managed to set the delay to 3600 seconds (1 hour) and it seems to work.
It would be nice if this field and the value range test of the variable "sn1_md_delay" could be changed to allow for more than a maximum of 999 seconds. Maybe 99999 would be more appropriate? Could this be done in the next software update?
Below is a change to the snapshot1.html file. As a workaround, If you add in this file to each path (e.g. src="/cgi-bin/....") the full url of your camera ("e.g. src="http://your-camera-ip/cgin-bin/..."), you can even try this out as a local copy on your workstation. You might have to log-in first with your browser if you have authentification enabled.
Line 28 to 30:
if (checkNumRange(f.sn1_md_delay, 99999, parseInt(f.sn1_md_postnum.value) + 1, "Delay seconds must from " +
(parseInt(f.sn1_md_postnum.value) + 1) + " to 99999.\n" +
"Next event must be detected after sending all the images which are triggered by last event."))
Line 245:
<input type=text name="sn1_md_delay" size=6 maxlength=5 value=3>
Thanks,
Chris