Cameraguy
Known around here
- Feb 15, 2017
- 1,502
- 1,159
Yes, when using autotracking to trigger BI (as per pinko), motion triggering in the 59225 automatically re-enables after my daily reboot (as per jaycanter).
Not fully understood, but when moving in front of the camera for a long time, the file size/time in the camera's SD card exceeds the PTZ/intelligence/autotrack duration setting (60s). I have the Event/IVS setting at 10s. Also, the record in BI misses the first 6s and is split into several separate events.
Oh and although BI finds PullPointSubscrtiption in the camera's list of features, it is not automatically selected as per the help file. (not a big deal)
Pic below.. i get a good tracking id say 9/10 times. Dont know if its my setup, luck, just the location of camera or all three.
If you set the ivs instrusion boxes right this camera kicks assThanks, you apparently just hold your mouth right while setting it up.
Plus it is partly location, as in most case's you don't have any thing between the camera and the target.
Thanks for the feedback looney2ns but two things :-Turn off the daily reboot, that's just a time where Murphy can rear his ugly head.
Using BI for motion detect will by far do a better job then anything from the camera.
If you need any help with ivs setup let us knowThanks for the feedback looney2ns but two things :-
1. I’ve mentioned previously that I have a hell of a problem with spiders’ webs with IR reflections at night and the ptz restart when the camera boots keeps them away.
2. I’ve had a problem with intruders who usually run at night causing blurred faces and am hopeful that auto tracking will help a lot. The frame rate may be a factor but I record continuously with several cameras per BI system so to extend the time before overwriting, I can only use a low frame rate to maximise the number of bits per frame.
PS. the 59225 I’m testing now is one of the cameras I bought from Andy nearly a year ago but didn’t get used and so just now updated the firmware and installed it at home to try out the benefits of auto tracking.
OK thanks Cameraguy. The query I have is are you able to provide me with a definition of the ‘Auto Track/Duration’ function under the PTZ menu that differentiates it from the ‘Alarm Track/Track Time’ function under the IVS menu please?If you need any help with ivs setup let us know
track time box in its seems to do nothing.. that is one of my only issues with this camera.. Example: A car pulls in, stops at the mail boxes. Before the car begins to move again, even though it's only a few secs thales camera wants to return to the designated ivs preset.. I would love to increase that time by even 5 seconds.. as for the tracking under ptz ive never tried it.. not sure if it does anything.. I could mess with it over this weekendOK thanks Cameraguy. The query I have is are you able to provide me with a definition of the ‘Auto Track/Duration’ function under the PTZ menu that differentiates it from the ‘Alarm Track/Track Time’ function under the IVS menu please?
Also, I have wondered specifically how the movement is tracked, bearing in mind the unlike using IVS without auto tracking, both the green/red motion sense rectangles and blue/red trigger boundaries are suppressed at the instant a trigger occurs - presumably because the blue trigger positions are no longer valid when the PTZ is exercised.
Might be a few days before I can load these up but I noticed that when I manually reboot camera it always goes forward 10 hrs so actual time is 12:30pm it will reboot and new time will be 10:30pm only way I can set it to reboot with correct time is to set time zone to -5hr then it boots up to correct time very strange. Oh and I am normally on eastern time zone, new York time in usaHello dabossc7, please find the files attached. This FW is PAL but will work in your system just the same. But I have my doubts that any FW version will solve your problem. I would be tempted to swap the cameras over (if possible) and see if the problem follows the camera. I also think that regular reboots are a good thing.
Please post back if/when you use the files so then I can hopefully delete them and not clog up the forum's server.
Ok just downloaded both but im a little hesitant to try I though I read some where on forum that you cannot go back to earlier f/w may brick camera anyone know for sure. If ok to do then thank you kindly for files.Hello dabossc7, please find the files attached. This FW is PAL but will work in your system just the same. But I have my doubts that any FW version will solve your problem. I would be tempted to swap the cameras over (if possible) and see if the problem follows the camera. I also think that regular reboots are a good thing.
Please post back if/when you use the files so then I can hopefully delete them and not clog up the forum's server.
I’m on GMT here in the UK but surely your time zone actually is GMT - 5hrs ie 5hrs earlier than GMT[/QUOTE
Solved 1 sd59925 has older fw that time is set to +5 in gui and it always had correct time when rebooted so I copied all settings when I did factory reset for the newer fw in the other sd59925 so when this camera was rebooted it changed to the correct time the +5 as I set it which is Pakistan time so my older fw camera is the one that the time setting is wrong, I feel so dumb. your comment about me being in -5 time zone had me thinking yea I'm behind England so I googled just for sure.I’m on GMT here in the UK but surely your time zone actually is GMT - 5hrs ie 5hrs earlier than GMT
Mega - thanks for the heads up - the firmware update also works on the PTZ1A225U-IRA.So anyone using either of these firmwares on this cam? Any problems to report?
[NTSC]DH_SD-Eos_MultiLang_NP_Stream3_V2.623.0000000.13.R.181205
[PAL]DH_SD-Eos_MultiLang_PN_Stream3_V2.623.0000000.13.R.181205
I'd try it but I'm pretty happy with mine firmware now.. keep us posted.. thanks !!Both cameras I loaded the firmware onto have been stable all day and the http admin interface is still running on both (a rarity these days!)
I still haven't reset the settings just yet and I've noticed that the auto tracking seems to make use of the zoom more when following objects here than the previous firmware I was running from 2017 - I'd be intrigued to hear if anyone else sees the same behaviour. The auto tracking still goes bonkers at times but in general I'm happy so far - thanks again for the heads up @looney2ns