OV9281 MIPI Camer a Module with RPI3 problem

1.Which seller did you purchase the product(s) from?
I tried reboot and deinstalled and reinstalled
2.The Model number of the product(s) you have purchased?
Arducam OV9281 MIPI 1MP Monochrome Global Shutter Camera
3.Which Platform are you using the product(s) on?
Raspberry PI 3B+
4.Which instruction are you following?
https://www.arducam.com/docs/cameras-for-raspberry-pi/mipi-camera-modules/camera-userland-driver-sdk-and-examples/
5.Has your product ever worked properly?
works with yavta example as described
6.What problems are you experiencing?
But after installing the SDK and running $ ./arducamstill -t 0 -m 1 -awb 1 -ae 1

the response is:

Open camera…
Hardware platform: a020d3
Found sensor ov9281 at address 60
mode: 0, width: 1280, height: 800, pixelformat: GREY, desc: (null)
mode: 1, width: 1280, height: 720, pixelformat: GREY, desc: (null)
mode: 2, width: 640, height: 400, pixelformat: GREY, desc: (null)
mode: 3, width: 320, height: 200, pixelformat: GREY, desc: (null)
mode: 4, width: 160, height: 100, pixelformat: GREY, desc: (null)
mode: 5, width: 1280, height: 800, pixelformat: GREY, desc: Used for ov9281 2lans raw8
mode: 6, width: 1280, height: 800, pixelformat: Y10P, desc: Used for ov9281 2lans raw10
mode: 7, width: 2560, height: 800, pixelformat: Y10P, desc: Used for synchronized stereo camera HAT 1280x8002
mode: 8, width: 2560, height: 720, pixelformat: Y10P, desc: Used for synchronized stereo camera HAT 2560x720
2
mode: 9, width: 1280, height: 400, pixelformat: Y10P, desc: Used for synchronized stereo camera HAT 640x4802
mode: 10, width: 640, height: 200, pixelformat: Y10P, desc: Used for synchronized stereo camera HAT 320x200
2
mode: 11, width: 320, height: 100, pixelformat: Y10P, desc: Used for synchronized stereo camera HAT 160x1002
mode: 12, width: 2560, height: 800, pixelformat: GREY, desc: ov9281 1lane raw8 1280x800
2 for synchronized stereo camera HAT
mode: 13, width: 1280, height: 800, pixelformat: GREY, desc: Used for ov9281 1lane raw8 1280x800 external trigger mode
mode: 14, width: 1280, height: 720, pixelformat: GREY, desc: Used for ov9281 1lane raw8 1280x720 external trigger mode
mode: 15, width: 640, height: 400, pixelformat: GREY, desc: Used for ov9281 1lane raw8 640x400 external trigger mode
mode: 16, width: 320, height: 200, pixelformat: GREY, desc: Used for ov9281 1lane raw8 320x200 external trigger mode
mode: 17, width: 1280, height: 800, pixelformat: GREY, desc: Used for ov9281 2lanes raw8 1280x800 external trigger mode
mode: 18, width: 1280, height: 800, pixelformat: Y10P, desc: Used for ov9281 2lanes raw10 1280x800 external trigger mode
mode: 19, width: 1280, height: 720, pixelformat: GREY, desc: Used for ov9281 2lanes raw8 1280x720 external trigger mode
mode: 20, width: 640, height: 400, pixelformat: GREY, desc: Used for ov9281 2lanes raw8 640x400 external trigger mode
mode: 21, width: 320, height: 200, pixelformat: GREY, desc: Used for ov9281 2lanes raw8 320x200 external trigger mode
index: 0, CID: 0x00980914, desc: V4L2_CID_HFLIP, min: 0, max: 1, default: 0, current: 0
index: 1, CID: 0x00980915, desc: V4L2_CID_VFLIP, min: 0, max: 1, default: 0, current: 0
index: 2, CID: 0x00980911, desc: V4L2_CID_EXPOSURE, min: 0, max: 65535, default: 681, current: 32
index: 3, CID: 0x00980913, desc: V4L2_CID_GAIN, min: 0, max: 15, default: 1, current: 8
index: 4, CID: 0x00981901, desc: V4L2_CID_ARDUCAM_EXT_TRI, min: 0, max: 1, default: 0, current: 0

and it does not list the current mode framerate .etc

If I run the same command once more (after exiting with ^C) the response is :

[email protected]:~/MIPI_Camera/RPI $ ./arducamstill -t 0 -m 1 -awb 1 -ae 1
Open camera…
Found sensor ov9281 at address 60

and the program stalls. All other example programs show the same behavior.

Any help is much appreciated.
7.What attempts at troubleshooting have you already made?

8.How would you like us to help you?
yes

Hello,

Don’t worry and I will try my best to help. Using MIPI_Camera driver, you should open the /boot/config.txt file and comment “dtoverlay = ov9281” then reboot. Both the two driver can’t work together.

Let me know if you need more help.

Thanks a lot!

I am able to run the c-based example codes now. However, there still seems to be a problem with the python code:

it looks as if the v4l2 library does not support python 3? Is this correct? The capture.py example runs under python 2 but not under python3?

Thanks again,

 

Hello,

Great to hear you have run the C code normal. Yes, about the pyth0n code, you are right, it seems the v4l2 python library is used for python2 instead of python3.