HIKvision DS-2CD2185FWD-I-2.8mm does not record on line crossing

S

ScoobyBear

n3wb
Mar 12, 2019
22
1
Stockholm Sweden
I got problems with one of my cams, a DS-2CD2185FWD-IS. It does not trigger recording on line crossing any more. I drive "over" the line with my cars and the sensitivity settings are set to 100, so it really should trigger! Of cause the checkbox to activate it is checked. And recording scheduled is set to 24/7 on event. And it do record on intrusion, so the Event recording works.

I've test to do the settings in both the NVR (DS-7616NI-K2/16) and in the camera itself. I've also reset the camera to factory.

Also, when it do record, often there are huge delays that basically can cause me to miss what's happen all together. It capture the first frame but the it can freeze for several seconds! This problem seem to be worse in daylight. On nightvision it seem to work better, but that can just be coincidence.

I also have 4 DS-2DE3304W-DE cameras connected to the NVR and non of them have any of those problems.

First I thought that the delays could be because my old WD Black 500GB hard drive (it was a couple of years old already when I put it in the NVR) that start to fail, so I replaced it for two brand new WD Purple 1TB drives. But the problem is rather worse than better.

It's possible that the problem started when I upgraded to FW v5.6.2. I upgraded the NVR to FW v3.4.104 at the same time.
Now I've tested v5.6.3 and when that didn't work any better I've downgraded the firmware in the camera to what I think it had when I first got it, v5.5.8 (I believe). Still the same.
Now I'm thinking about downgrade the FW in the NVR (which now is on v3.4.107) too and reset it to factory settings, but that is really the last thing I can come up with.

So now I put out a question here, does anyone here has an idea?
 
I suspect the new firmware has muddled the line crossing settings and you need to recreate them. I have the same NVR and similar cameras and my line crossing works well. I suggest you stay with v3.4.107 on the NVR and v5.6.3 on the camera.
With IE11, open the webGUI of the NVR and the webGUI to the camera and check the Video settings (Configuration>Video/Audio) match. It's possible the upgrade has them at odds.
1580340912022.png
On the camera's webGUI (excuse the image), recreate the line crossing. Click Clear then set Max and Min size + detection area.

1580340394016.png
 
  • Like
Reactions: coney27
Thanks for your answer!

Unfortunately it doesn't seem to help much. I redid the config last night and changed the settings, but it still won't work to my satisfaction.
When I came home earlier today it didn't trigger when I drove my car over the line (B->A)!!
I did an experiment tonight and disabled the intrusion detection, leaving only the line crossing detection and went out to trigger it. First walk it didn't trigger A -> B but it did trigger on B -> A.
Second try it trigger on both ways. So it does work, but very randomly it seems!
Sensitivity is set to 70. No Min or Max is set (can't be set in my NVR, only in the camera).

I've just noticed one thing though about the freeze image and skipping several seconds of video. That seems to be only on the playback via the app or web-GUI. I just download some clips from the NVR and played it on my computer and there was no freeze and no missing seconds. But instead there was a ghosting effect were there was movement during the first seconds. Not sure what that tell us...

I know I've read that some Hik-models have performance problem and have trouble to handle several different type of triggers at the same time. Can it be the case on this camera model?
 
Something I noticed which may apply and appeared to be a firmware glitch....

Open two separate browser windows - 1 for the NVR and 1 for the camera itself then look at your line crossing in both. Confirm that A and B are the same on both the NVR and camera pages. I found on mine that A and B were opposite in the NVR webpage to what they were in the camera (I forget which of the two matched the local monitor output). After a bit of messing about I found that when you rotate the line, once you go passed a certain orientation - the A&B were flipping sides. As the NVR webpage/Camera webpage/local monitor output didn't match the line crossing behaviour reversed.
 
Thanks for your input.
I've compare the settings and they are identical.

I wondering if the angle of the line together with the fact that the ground slopes slightly towards the camera makes it hard for the camera to determine if the line is being crossed. But then again, it has worked before.

Tonight I downgraded the FW in the NVR. It now runs on v3.4.101 which is possibly the same version it came with. We'll see if that makes any difference.
Someday I will try to switch place between two cameras and see if the problem follow the camera or if it could be something with the cable, even if I hold that very unlikely. And maybe I should try to switch Ethernet-ports on the NVR. But that also is highly unlikely to do any difference.
 
You mentioned playback skipping on event earlier in this thread. Two things to check - first ensure main stream normal and main stream event are set the same with regard to FPS and bitrate. Second if your recording on a 24/7 ensure that in storage > schedule > advanced that the pre alarm for each camera is set to 0 seconds rather than its default of 5 seconds. Pre alarm buffering is not needed if you’re recording on a schedule and can cause skipping/missing recording on event trigger.

For the line crossing not working I’d first clear it and disable it in the NVR, then redraw it/re enable it. The NVR GUI is reading/displaying the settings from the attached camera (programmed via the NVR in the earlier firmware) Since the NVR firmware has been updated, it’s not inconceivable that although the NVR is displaying the setting correctly it’s perhaos not acting on it. If that doesn’t work I’d log on to the cameras web page http://nvripaddress:6500cameranumber and go to maintenance to default the camera. Once back online - reprogram it via the NVR. I’m sure this will sort it - I’ve had similar glitches over the years after updates.
 
I only record on event, not continuously.
It's might be a bit to early to say but I haven't seen any skipping/stumbling videos since I downgraded the NVR. That is kind of good.
One thing worth mentioning is that it only seemed to happen in daylight. I don't think I ever seen it stumbling when the night vision is on.

Line Crossing: I've tried to do factory reset several time and I've tested to do the settings in the camera only (removing all rules in the NVR) and in the NVR only. No difference.
I tried to downgrade the camera yesterday but it refused to. I selected the file and the progress bar come up. But then nothing.
 
A few things I want to add more as just general info:

- I’ve found on multiple occasions the NVR GUI does not accurately report settings from cameras. Dial into camera directly and it’s correct. Newer and older firmware alike

- K series NVRs do have a version 4 firmware that is available if you wanted to try it. Same new modern GUI as found on the higher end I series units

- with IP cameras in general all of the processing is done on the Camera itself and not so much the NVR. The NVR is merely recording based on triggers sent from the camera firmware. With that being said it does take 2 to tango, so isolating the failure to either the trigger or the recording command is important and it looks like you’ve already made some headway with that.

When in Doubt, factory reset the camera. I’ve had peculiar issues come up over a series of firmware changes that only clearing the settings resolved. It may not fix your issue but it’s worth a shot.
 
CoreyX64 said:
A few things I want to add more as just general info:

- I’ve found on multiple occasions the NVR GUI does not accurately report settings from cameras. Dial into camera directly and it’s correct. Newer and older firmware alike

Program the setting in the NVR and it sets it in the camera and the info will match in both. Program it on the camera and the NVR will continue to show the previous setting unless you reboot the NVR. On the odd occasion I have known the camera to remain unaltered following a setting change in the NVR but it’s rare.

- K series NVRs do have a version 4 firmware that is available if you wanted to try it. Same new modern GUI as found on the higher end I series units

It doesn’t work very well and freezes - I assume that this is because the I series is a higher performance model. The version 4 firmware for the K series (4.21.005) was removed from the Hikvision UK portal on Jan 21st. While you could use the version in the I series folder in the portal - 4.21.005 has been removed from there also.

- with IP cameras in general all of the processing is done on the Camera itself and not so much the NVR. The NVR is merely recording based on triggers sent from the camera firmware. With that being said it does take 2 to tango, so isolating the failure to either the trigger or the recording command is important and it looks like you’ve already made some headway with that.

When in Doubt, factory reset the camera. I’ve had peculiar issues come up over a series of firmware changes that only clearing the settings resolved. It may not fix your issue but it’s worth a shot.

Agreed - a factory reset following a firmware upgrade is a good idea
Click to expand...
 
Interesting info CoreyX64.
Where can I find FW 4? I didn't see it in Hiks Portal.

I've done several factory reset from the web GUI without any improvements. Last night I removed the cover from the camera and pressed the physical reset button on it. I'm not sure if that made any difference.
It tends to work a lot better if I only have the line-crossing detection. I tried to deactivate intrusion detection and I don't think it missed anything. But I've activated the intrusion detection again (but in a smaller area than before) and tonight it missed when I came home with my car!!! Later to night I walked over the line and it detect it...
I would gladly live with only line-crossing detection if it wasn't that it only support ONE rule! The same comes for Intrusion detection, only one area allowed.

OffTopic: Interesting fact is that when I downgraded the NVR I got back the ability to call PTZ presents from the Android App. I've been missing that feature the last couple of months! I actually thought it was the app so I downgraded it and got a kind of hidden menu in a older version. But now, after fw downgrade in the NVR, I have a visible present menu again.
 
V4 firmware removed on Jan 21st as I’ve annotated the previous reply. I’m guessing it’s because it didn’t perform very well in the lower spec’d machine. I found it would freeze when switching between normal and smart playback. You can however use V4 firmware that’s for the I series so long as it’s a K2 8 channel or above. This was confirmed by Hikvision supplier DVS here in the UK. I had I series 4.22.005 on my K series. If you do later decide to downgrade from V4 to V3 it does work but it will default and deactivate the NVR requiring you to reprogram from scratch.
 
Last edited:
Doesn't all downgrade require to start from scratch? I had to do that when I downgraded to v3.4.101. So that is not an issue.
I'll might give v4 a try some day next week. Mine has 16 channels so that should work then.
 
John Williamson said:
V4 firmware removed on Jan 21st as I’ve annotated the previous reply. I’m guessing it’s because it didn’t perform very well in the lower spec’d machine. I found it would freeze when switching between normal and smart playback. You can however use V4 firmware that’s for the I series so long as it’s a K2 8 channel or above. This was confirmed by Hikvision supplier DVS here in the UK. I had I series 4.22.005 on my K series. If you do later decide to downgrade from V4 to V3 it does work but it will default and deactivate the NVR requiring you to reprogram from scratch.
Click to expand...

Sorry, didn’t scroll up high enough!

V4 K series had different file sizes, hashes, and time stamps from those on I series. They are not identical firmware. With that being said, K series is less powerful and cheaper than I series, which likely explains why it took them so long to release V4 and then ended up rescinding it. I didn’t know they pulled it until you mentioned. I have several K series units running it without issue. But they’re using basic 4MP cameras, nothing higher or more intense smart or analytic wise.


Sent from my iPad using Tapatalk
 
Hikvision didn’t permit downgrading last time I checked. It’s been a few years but that’s not surprising. If there are 4 settings in you config, 3 can’t use them so it’s procedural to clear them out.
 
CoreyX64 said:
Sorry, didn’t scroll up high enough!

V4 K series had different file sizes, hashes, and time stamps from those on I series. They are not identical firmware. With that being said, K series is less powerful and cheaper than I series, which likely explains why it took them so long to release V4 and then ended up rescinding it. I didn’t know they pulled it until you mentioned. I have several K series units running it without issue. But they’re using basic 4MP cameras, nothing higher or more intense smart or analytic wise.


Sent from my iPad using Tapatalk
Click to expand...

I too would have thought the versions were different. It was in the comments of one of DVS’s YouTube videos that people were asking “how have you got Version 4 on K series” that they alluded your could simply use the I series firmware on 8 channel or above K2 units. At that point in time V4 was not available in the K series folder on either the UK or EU portal - that came weeks later.

I swapped out my 8 channel K for a 16 channel I series a few days ago.
 
@ScoobyBear - please post screen captures from the webGUI of your DS-2CD2185FWD-IS:
Configuration>Video/Audio>Video for the Main Stream settings
Configuration>Image>Display Settings with the Backlight Settings fields expanded
Configuration>Image>Display Settings with the Image Enhancement fields expanded
This will help narrow the issue down regarding the image freeze and skipping on the playback and also with the ghosting on the downloaded clips.
 
John Williamson said:
I too would have thought the versions were different. It was in the comments of one of DVS’s YouTube videos that people were asking “how have you got Version 4 on K series” that they alluded your could simply use the I series firmware on 8 channel or above K2 units. At that point in time V4 was not available in the K series folder on either the UK or EU portal - that came weeks later.

I swapped out my 8 channel K for a 16 channel I series a few days ago.
Click to expand...

Interesting. I don’t risk it because I don’t want to accidentally brick a unit but generally each firmware has a 3 digit model code with which you can use to verify compatibility. A Q4 unit for example has a board ID of K74. I2 and K2 both have board IDs of K51, hence why people saw the firmware as crossable. I don’t know the physical hardware differences of the K and I series boards outside of their marketed specs, but the fact that 2 alleged identical firmwares with same board ID and version had different dates and file sizes was concerning to me.
 
CoreyX64 said:
Interesting. I don’t risk it because I don’t want to accidentally brick a unit but generally each firmware has a 3 digit model code with which you can use to verify compatibility. A Q4 unit for example has a board ID of K74. I2 and K2 both have board IDs of K51, hence why people saw the firmware as crossable. I don’t know the physical hardware differences of the K and I series boards outside of their marketed specs, but the fact that 2 alleged identical firmwares with same board ID and version had different dates and file sizes was concerning to me.
Click to expand...

I switched mine back and forth between the two firmwares several times without issue - I trust information from DVS to be correct. There's very little difference physically between the models in appearance - I was a bit underwhelmed when I swapped mine! Physically identical externally apart from the additional BNC video output on the I. The boards inside on the I are also similar, the I had a couple of extra chips that are missing on the K but that could be as my replacement was 16 channel rather than the previous 8.
 
This is still an issue for me. The line crossing detection works much better now when I have redone the line from a vertical to horizontal line, but there is a greater risk that intruders won't trigger it because they won't cross it...

The issue with skipping frames is back and possibly worse than ever. Yesterday I upgraded the camera FW to v5.6.4 and today the skipping isn't just in the first seconds anymore but randomly in the video... If I download the video to my computer and using Media Player Classic there is no skipping but distortion/ghosting instead. If I use HikVisions VSPlayer I see skipping but no distortion.

I found this tread with basically the same problem.

Hikvision Image Problem and Skipping during playback

Hey guys I have a new nvr DS-7608NI-E2/8P with 2 cameras DS-2CD2342WD-I My recording settings are 1080p with full frame rate and quality to highest and h264+ enabled. Also its set to record motion detect only Anywyay I've noticed that if I play back the camera in the garage and for example it...
ipcamtalk.com ipcamtalk.com
But no solution...

Now I've tried to reduce the resolution to 3072x1728, Quality to Medium (from High) and H.264 (from H.265). I'll see if that makes any difference but I actually think it will end up with me having to replace the camera to ensure I don't miss something important. My other 4 cams are much more reliable.
 
You must log in or register to reply here.
Top Bottom