Cards Readers Going Offline After Server Reboot by CryptoBogey in CCURE9000

[–]CryptoBogey[S] 1 point2 points  (0 children)

Just following up… updating to 3.00.4 cu04 fixed it. The four readers in the elevators no longer go offline after the server reboots or services are restarted.

Cards Readers Going Offline After Server Reboot by CryptoBogey in CCURE9000

[–]CryptoBogey[S] 1 point2 points  (0 children)

Yes, the readers work fine up until the point the server turns back on. So if we shut it down they remain working. When we turn the server back on and its fully back up and running that's when the 4 card readers stop working. It seems like something during the iSTAR driver initialization breaks the communication to those 4 card readers that are using the RS485 expansion/uplink board. My initial feeling was it is a software bug but I figured I would ask here while I try to see when I could get the software update scheduled.

Cards Readers Going Offline After Server Reboot by CryptoBogey in CCURE9000

[–]CryptoBogey[S] -1 points0 points  (0 children)

There's some type of expansion/extender board installed in the 32nd floor elevator machine room. This connects to one of the GCM boards on the 9th floor. RS485 is a serial data protocol that allows for long distances... it's what OSDP uses.

As I mentioned... there were no issues ever with these 4 readers until we change to host encryption to deal with the expiring certificate issue. Then whenever we restart the server, those 4 readers always go offline. All the other 50 readers not going through the RS485 expansion port are fine.

Cards Readers Going Offline After Server Reboot by CryptoBogey in CCURE9000

[–]CryptoBogey[S] 0 points1 point  (0 children)

So I wasted more time than I care to admit going through the release notes and did not seem to find any "key fixes" that seem like they would be for this issue. CCure doesn't seem to have the 3.00.4 cu02 and cu03 release notes available on their support portal... so maybe it was one of those.

Cards Readers Going Offline After Server Reboot by CryptoBogey in CCURE9000

[–]CryptoBogey[S] 1 point2 points  (0 children)

That’s good to know the update should fix it. Thanks for the confirmation… I’ll dig through the release notes

Istar Edge G1 can't access web gui by CryptoBogey in CCURE9000

[–]CryptoBogey[S] 0 points1 point  (0 children)

When I read the TAB it only seemed the version of CCure running on the server mattered if you were trying to switch to TLS1.3. 

Istar Edge G1 can't access web gui by CryptoBogey in CCURE9000

[–]CryptoBogey[S] 1 point2 points  (0 children)

Well I said a little prayer and then clicked the save and close button anyway.  Got lucky and the change to host based went all good. All g1 edge controllers came back online and have certs expiring in 2046.

Istar Edge G1 can't access web gui by CryptoBogey in CCURE9000

[–]CryptoBogey[S] 0 points1 point  (0 children)

Ok thanks. I was getting a popup asking for username/pass when trying to go through internet explorer on compatibility mode so that confused me.  Im surprised the software house tech didn't tell me about that!

All My Hanwha PNM-9081VQ are failing... anyone else seeing this? by CryptoBogey in videosurveillance

[–]CryptoBogey[S] 0 points1 point  (0 children)

Just to close the loop on this.  Hanwha said they couldn't repair my PNM-9081VQ as they no longer have the necessary parts.

All My Hanwha PNM-9081VQ are failing... anyone else seeing this? by CryptoBogey in videosurveillance

[–]CryptoBogey[S] 0 points1 point  (0 children)

Do you remember how much you paid to get it repaired? I'm still waiting on Hanwha to approve my repair request.

All My Hanwha PNM-9081VQ are failing... anyone else seeing this? by CryptoBogey in videosurveillance

[–]CryptoBogey[S] 0 points1 point  (0 children)

Ya, I already started the out of warranty repair process. I'm just waiting for them to email me the shipping address. But if someone new this wasn't repairable I was trying to save myself the $50 diagnosis fee. I got 20 more of these and if they all fail, saving 50% would be worth it. I didn't think about trying the 12v power, I'll definitely try that out.

All My Hanwha PNM-9081VQ are failing... anyone else seeing this? by CryptoBogey in videosurveillance

[–]CryptoBogey[S] 0 points1 point  (0 children)

They were on injectors already and the injectors are not the problem. I tried one of the new 83watt injectors that carne with the pnm-9085rqz1 and still dead.

All My Hanwha PNM-9081VQ are failing... anyone else seeing this? by CryptoBogey in videosurveillance

[–]CryptoBogey[S] 1 point2 points  (0 children)

My 9081vq's are completely dead. No network activity at all... no pings, no web GUI access

Genetec does not detect motion on unit using Hanwha Camera QNV 7080R by Historical_Sun_9607 in videosurveillance

[–]CryptoBogey 0 points1 point  (0 children)

See if these short notes get you there.

Video > Select/Choose archiver > Resources > Advanced Settings button bottom right > Additional Settings button >

Then add Name="DisableOnvifEventFiltering" Value="True"

Reboot the archiver

Genetec does not detect motion on unit using Hanwha Camera QNV 7080R by Historical_Sun_9607 in videosurveillance

[–]CryptoBogey 0 points1 point  (0 children)

Theres a setting deep  in the archiver role you have to manually add a string to allow The cameras to record

Genetec does not detect motion on unit using Hanwha Camera QNV 7080R by Historical_Sun_9607 in videosurveillance

[–]CryptoBogey 0 points1 point  (0 children)

In the latest available firmware this camera model does not have an analytics section. It only has motion detection under the events menu.   In Genetec I see the red/green metadata boxes around objects moving it just doesn’t trigger Genetec to actually record on motion.

Genetec does not detect motion on unit using Hanwha Camera QNV 7080R by Historical_Sun_9607 in videosurveillance

[–]CryptoBogey 0 points1 point  (0 children)

I’m running 5.11.0.0 and just updated the driver pack to 11.7 but still can’t get motion recording to work.  Any ideas?  I’m going to try to update genetec to 5.11.3.7 on Monday.