Running a Wide & Narrow FOV device on the same host

BrianBourn

Hello All,

I'm trying to run both a wide angle and standard FOV device off the same host, is there a way programatically to figure out which is which within the DeviceInfo? Maybe the SerialNumber runs or something. It's for a fleet we're building so I cant just hard code serial numbers. Any help is appreciated.

jakaskerl

Hi BrianBourn
device.readCalibration2().getEepromData().productName will give you the full name of the device. Then you can check whether its W or standard (NFOV).

Thanks,
Jaka

BrianBourn

jakaskerl Awesome thanks for the help!!

BrianBourn

jakaskerl Ok running into a small problem:

Traceback (most recent call last):

File "/Users/bbourn/dev/i8labs/pythonProject/eeprom_text.py", line 5, in <module>

print(device.readCalibration2().getEepromData().productName)

depthai.EepromError: No or invalid EEPROM configuration flashed, error: EEPROM_NOT_AVAILABLE

for reference I'm using OAK-1 and an OAK-1 W

jakaskerl

Hi @BrianBourn
Line 5, I'll assume you have not booted the device (with dai.Device() as device). You have to boot the device first before you are able to access the eeprom.

Thanks,
Jaka

AmunTimilsina

Is there a way to know this info without booting up the device, maybe through: dai.Device.getAllAvailableDevices()

jakaskerl

Hi @AmunTimilsina
OAK devices do not expose this information unless a host it connected to it. You could map the MXID to a dictionary of FF and AF to know beforehand, but you would need to do this for every single device.

Why would you need that info? Perhaps the Camera node would help..

Thansks,
Jaka

AmunTimilsina

Hi @jakaskerl

I've set up a configuration to specify whether I prefer using the narrow or wide camera. I aim to streamline the boot-up process by initializing only the necessary camera based on this configuration parameter. For instance, if I specify "narrow" in my configuration, I intend solely for the narrow camera to boot up, eliminating the need to start both and then decide which one to utilize. This optimization is geared towards minimizing unnecessary overhead.

jakaskerl

Hi @AmunTimilsina
You can't know that without first booting the camera which defeats the whole purpose.. As I said before, the easiest option would be to map each device beforehand (could even write a script that does that).

Thanks,
Jaka

AmunTimilsina

That clears things out. Thanks.