Config tool can't change the IP unless you have entered the correct password. See the 3rd icon from the right upper corner in ConfigTool for help.No, trying to set it to 192.168.x.x range. All the other cams are on the 192 range. Can get into all their web gui. This ptz I can't access. Forgot the password I gave it, but can't even get a log in on 10.x.x, so was trying to set it on the 192 so I could use configtool to reset it.
Yeah, was hoping to not have to climb a 20 foot tower and balance myself unscrewing 4 tiny screws while not dropping them... but I just did. Got back on its original .108 address. Now having trouble with ConfigTool initializing it. Go through setting new password and get "network error, maybe timed out."OK, how about doing a factory reset to give it the 192.168.1.108 address and start from there? Sometimes that is the least painful option.
Just use IE to navigate to the 108 address to initialize, you don't need the config tool.Yeah, was hoping to not have to climb a 20 foot tower and balance myself unscrewing 4 tiny screws while not dropping them... but I just did. Got back on its original .108 address. Now having trouble with ConfigTool initializing it. Go through setting new password and get "network error, maybe timed out."
One step forward, two steps back
Tried that first, comes back with nothing.Just use IE to navigate to the 108 address to initialize, you don't need the config tool.
Thanks. Got it working finally late last night. Used the Lorex NVR remote device search. It has "modify IP address" setting in it.If you want any help setting the IP let me know I can jump on via Teamviewer.
Main fps is 5-20, saw 30 for a while. Mainly staying in single digits for some reason. iframes 0.30's to 0.60'sYou need to set the FPS and iframe rate as the same. The higher the iframe the worse, especially if you use Blue Iris.
The 0.20 is the KEY, which means your iframes is 5 times the FPS. This means that any object in and and out of your field of view with 5 seconds may be completely missed in Blue Iris and other VMS. 5 seconds can be a long time in some field of view. That is how the Reolinks miss motion....
So, I set the fps to 30 and the iframes to 30 on the main and sub channel. Second sub (display) is set to 15/15 cause its fps only go to 17.Main fps is 5-20, saw 30 for a while. Mainly staying in single digits for some reason. iframes 0.30's to 0.60's
sub is pretty steady 30's, finally.
Don't know why the main isn't holding at 30 fps when its set to that in the web gui
Got the fps looking better when I turned the bit rate down 6000's. Sub is steady 30's with key of 1.
K, thanksMy settings would not work for your location and I always only use 1 Preset with a tripwire and set the tracking time to 30 seconds with a maximum 35 on Tracking Size or it starts to loose tracking.
Well just figured out how to use the trip wire. Tracked pretty good for only for 13 sec. How do you get it to record longer? Also, doesn't zoom in while its tracking. Actually, zooms out.My settings would not work for your location and I always only use 1 Preset with a tripwire and set the tracking time to 30 seconds with a maximum 35 on Tracking Size or it starts to loose tracking.
This takes trial and error. It may several tweaks to get dialed in.Well just figured out how to use the trip wire. Tracked pretty good for only for 13 sec. How do you get it to record longer? Also, doesn't zoom in while its tracking. Actually, zooms out.
Will do. What setting is for the tracking size?Make sure you use IE ( Internet Explorer ) and do any setup in the camera's Web GUI or it won't save your settings in other browsers. If it stopped tracking before your tracking time setup then I reckon you have the tracking size set to high especially how you said it zooms out. Every location is a different setup. Don't forget tracking won't be perfect all the time every time it also depends on what your FPS and Bitrate is set @ also.