Hi folks, I am new to this forum, but over a decade in security camera systems.
Long ago I would setup GeoVision system hardware for DVRs.
Today's system I have a issue with is all NVRs on POE+ switches, and multiple brand cameras hooked up.
I am running about 20 cameras....
I have had Bi for almost a year, and v4 was running great. But I was looking forward to the v5 upgrade with a few more features. I made the change and all was good.
This system is my main PC, so it was only supposed to stay on here a temporarily. Its a i7 6550K or something like that. with 32gb ram a nVidia GeForce GTX 970.
Win10 had some updates last week, and all is AOK. Then I see that Bi has a update, so I proceed, and in the update it needs Visual C++ So that failed. and now I cant even launch Bi!
Because the above system is my main work PC, I had just purchased a almost new i7 8700/16gb Ram/with the onboard 630 intel graphics chip. I was on this site that had cpu and camera ratings and speeds that helped me select the PC.
So I installed Bi with the new update on this new fresh win10Pro system, and this time, the VisualC++ install was mandated and installed with no issues.
Bi is also up and looks like is running...BUT
Now the cameras are active for a few seconds then go out.A ctive and out! All hardwired with shielded Cat6
You can not see that you are PTZ or zooming, but it does move and works. But it doesn't record much anything as its not on long enough to detect motion as they are too intermittently in and out.
I am pretty confused at this point. HELP would be MUCH appreciated. I am NOT going to be using the first system I mention above,
but I think it maybe helpful to others, so I explained the situation. BUT I need this second(new i7 8700), likely less complex issue resolved.
WHY are the cameras going in and out? I rebooted router, and switches, and rebooted cameras...
Maybe its a setting to tell Bi about what graphics chip is to be used?(I checked and they are Intel, though there is a 2nd intel option). Maybe something with network? Although all else looks to run fine.
Long ago I would setup GeoVision system hardware for DVRs.
Today's system I have a issue with is all NVRs on POE+ switches, and multiple brand cameras hooked up.
I am running about 20 cameras....
I have had Bi for almost a year, and v4 was running great. But I was looking forward to the v5 upgrade with a few more features. I made the change and all was good.
This system is my main PC, so it was only supposed to stay on here a temporarily. Its a i7 6550K or something like that. with 32gb ram a nVidia GeForce GTX 970.
Win10 had some updates last week, and all is AOK. Then I see that Bi has a update, so I proceed, and in the update it needs Visual C++ So that failed. and now I cant even launch Bi!
Because the above system is my main work PC, I had just purchased a almost new i7 8700/16gb Ram/with the onboard 630 intel graphics chip. I was on this site that had cpu and camera ratings and speeds that helped me select the PC.
So I installed Bi with the new update on this new fresh win10Pro system, and this time, the VisualC++ install was mandated and installed with no issues.
Bi is also up and looks like is running...BUT
Now the cameras are active for a few seconds then go out.A ctive and out! All hardwired with shielded Cat6
You can not see that you are PTZ or zooming, but it does move and works. But it doesn't record much anything as its not on long enough to detect motion as they are too intermittently in and out.
I am pretty confused at this point. HELP would be MUCH appreciated. I am NOT going to be using the first system I mention above,
but I think it maybe helpful to others, so I explained the situation. BUT I need this second(new i7 8700), likely less complex issue resolved.
WHY are the cameras going in and out? I rebooted router, and switches, and rebooted cameras...
Maybe its a setting to tell Bi about what graphics chip is to be used?(I checked and they are Intel, though there is a 2nd intel option). Maybe something with network? Although all else looks to run fine.
Last edited:
