How can I configure pod sharing of IM10C10-1 (Pelco sarix camera) with NBRK0550 as a shared pod?

[DCIM_Support]

How can I configure pod sharing of IM10C10-1 (Pelco sarix camera) with NBRK0550 as a shared pod? I have tried it but the camera link status shows it's offline.

(CID:90899816)

[DCIM_Support]

Hi Felix,

Can you advise what FW revision is currently on the Pelco camera? From KBase FA158450 only the FW running 1.8.2 is supported on that particular Pelco camera. If the Pelco camera is running 3.x FW, it unfortunately does not work and it will show offline. If the Pelco model used an older FW version, you can try and downgrade it to FW 1.8.2. We are currently working on the issue with integrating the new Pelco FW with our Netbotz appliances. Hopefully we can resolve it soon. 

I hope this helps. 

Regards,

B

(CID:90899840)

[DCIM_Support]

Hi Breda, The Pelco camera FW is 1.8.2 but still I can't pod share it because it's offline. Regards, Felix

(CID:90899915)

[DCIM_Support]

Hi Felix,

Please make sure that you are on Botzware 4.2 or higher. The link below is for Botzware 4.4:

http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SFNBZ440

Is this Pelco camera being shared by any other Netbotz appliance? If so, can you use just one Netbotz 550 for testing? 

Are you able to access the Pelco camera independently through a web browser? 

There is a KBase FA167042 that has tips on how to add the Pelco camera to a Netbotz appliance. 

The link to the KBase is below:

http://www.apc.com/site/support/index.cfm/faq/

If you are still having issues after going through the above KBase you can also try and reformat the Netbotz device using KBase FA158175 and the Pelco camera. 

If the problem is still persisting please can you attach the appliance event log and appliance log here please? 

Regards,

Breda

(CID:90899931)

[DCIM_Support]

Hi Breda, Thank you so much, I have upgraded both the Botzware & Netbotz FW and it worked. Regards, Felix

(CID:90899934)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.