Try increasing your HTTP_TIMEOUT value under Options -> Network.
After setting the HTTP_TIMEOUT to 5000 on my system, neither one of my two wireless ip cameras have gone offline since.
Remote cameras disconnects frequently
thanks for answering.
did you have the very same problem?
I want to understand this, if after 2500 ms the server does not receive an answer by the camera, it assumes that the camera is disconnected and then it does not try to reconnect again?
another thing, i recently noticed that some monitors suddenly begins to generate events very very fast. and timeline shows the events as if they had started years ago
did you have the very same problem?
I want to understand this, if after 2500 ms the server does not receive an answer by the camera, it assumes that the camera is disconnected and then it does not try to reconnect again?
another thing, i recently noticed that some monitors suddenly begins to generate events very very fast. and timeline shows the events as if they had started years ago
- knight-of-ni
- Posts: 2406
- Joined: Thu Oct 18, 2007 1:55 pm
- Location: Shiloh, IL
All I'm saying is that the your symptoms appear to be similar. Because other problems can cause thees kind of symptoms, I cannot say for certain that we both have/had the exact sample problem. I recommend you simply try my suggestion and then let us know whether or not it fixes your problem (it can't hurt).
Your issue with the time-line getting messed up with events generated from 1969 is just another symptom of the same problem.... this seems to be a side affect when a camera unexpectedly goes offline. Arguments of whether or not this could be called a bug aside, one could program a filter to delete these erroneous events (that's what I did).
Hope this helps.
Your issue with the time-line getting messed up with events generated from 1969 is just another symptom of the same problem.... this seems to be a side affect when a camera unexpectedly goes offline. Arguments of whether or not this could be called a bug aside, one could program a filter to delete these erroneous events (that's what I did).
Hope this helps.