ArduCAM Mini 2MP Plus not working with Arduino Nano

I am trying to connect an ArduCAM Mini 2MP Plus to my Arduino Nano. I have used the camera module with my Arduino Uno, so I know that camera works. However, it does not work with my Nano. When I use the ArduCAM_host app included with the ArduCAM library and click the open button, it gives the message "com is open", but it is also supposed
to confirm the SPI interface.

I have been following this video to operate the camera. The instructions worked for my Uno, but not my Nano.
Does anyone have experience with using the ArduCam on with a Nano?

Edit:
The message I should recieve on the host app is:
Com is open!
ArduCAM Start!
SPI Interace OK.
OV2640 detected.

As far as I can tell, OV2640 refers to the camera model, the ArduCAM Mini 2MP Plus.

So something is keeping the COM port open. I'm not familiar with the "ArduCAM_host app" but one application that can keep the port open is the serial monitor (or any other terminal application); close it if that is the case.

Thank you for your reply.
Unfortunately that did not fix the issue. I included more information about the app message in an edit to my post.

Unfortunately your original message did not indicate that "COM port open" was the expected message.

The main difference (that I think might be relevant) between the Uno and the Nano is the 5V voltage regulator. Which brings the question how you are powering your setup? If there is external power supplied to Vin, the regulator might not be able to handle the current requirements of the ArduCam. If you're using only USB, this does not apply.

Hello,
I am using USB to power the setup.

In that case, I do not know.

I modify the rate ( 115200 instead of 921600 ) and it runs .

image

Hello,
That worked. The serial monitor now shows that it is communicating. I am now getting an SPI error:
image_2023-02-13_175857230
I am not sure what's causing it. Anyone have an idea?

hello,
I was also facing the issue while working with the Arducam and was also not able to solve issue. But when I tried it on second day that error did not pop up, I didn't do anything different but the only difference that I think of is, first time when I tried it many applications were working in the background and on the next day this was first thing that I did after starting my system, so I guess you can try completely restarting your system.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.