user45920: So what I'm trying to do is use the ArduCAM OV2640 (2MP Mini) to take a timelapse. Of course the first thing I have to do it to get it to take a picture and write it to an SD card. The thing is, the camera works fine by itself, however when I hook up the SD card something happens where the SPI no longer works (I have a general understanding of how SPI works -- not a highly technical understanding though). 
So my main question is if it's possible for a device using SPI to 'use up' the entire SPI bus so that other peripheral devices can't interact with the microcontroller?
And if so, is there any software or way to visualize this? Like something that monitors the SPI bus?
And as for how to actually fix the problem, would it be practical to use a shield with a built in SD card module? Or use a logic gate to determine which device to allow access?
I really don't have the greatest understanding of this, so any help would be appreciated. 
EDIT:
I'm using this camera module with this sd card module. As for my wireup, the camera follows as below: 
The common pins between the SD card module and camera are VCC,GND,MISO (pin 12) , MOSI (pin 11), and SCK (pin 13). I have an individual CS pin for each.

user33608: In this case, I don't think that a device is "using SPI to 'use up' the entire SPI bus so that other peripheral devices can't interact with the microcontroller". I think that your problem probably lies with how your SD card is connecting via the SPI bus.
The problem is that a lot of Serial Peripheral Interface (SPI) devices, particularly the cheaper ones, don't properly put the MISO pin into high-impedance when SS is pulled high.
I had almost exactly this situation with one of my projects. I eventually resolved it by placing a tri-state buffer in the MISO line for each of the SPI devices.
In that case, I used a 74HC125 (4-channel tri-state buffer).
This is the page on Better SPI Bus Design in 3 steps that finally got me on the right track. I think the explanations are reasonably clear (at least compared with many other sites I found!).

45920: <p>So what I'm trying to do is use the ArduCAM OV2640 (2MP Mini) to take a timelapse. Of course the first thing I have to do it to get it to take a picture and write it to an SD card. The thing is, the camera works fine by itself, however when I hook up the SD card something happens where the SPI no longer works (I have a general understanding of how SPI works -- not a highly technical understanding though). </p>

<p>So my main question is if it's possible for a device using SPI to 'use up' the entire SPI bus so that other peripheral devices can't interact with the microcontroller?</p>

<p>And if so, is there any software or way to visualize this? Like something that monitors the SPI bus?</p>

<p>And as for how to actually fix the problem, would it be practical to use a shield with a built in SD card module? Or use a logic gate to determine which device to allow access?</p>

<p>I really don't have the greatest understanding of this, so any help would be appreciated. </p>

<p>EDIT:</p>

<p>I'm using <a href="https://rads.stackoverflow.com/amzn/click/B012UXNDOY" rel="nofollow noreferrer">this camera module</a> with <a href="https://rads.stackoverflow.com/amzn/click/B01IPCAP72" rel="nofollow noreferrer">this sd card module</a>. As for my wireup, the camera follows as below: <a href="https://i.stack.imgur.com/c8qC7.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/c8qC7.jpg" alt="Camera Schematic"></a></p>

<p>The common pins between the SD card module and camera are VCC,GND,MISO (pin 12) , MOSI (pin 11), and SCK (pin 13). I have an individual CS pin for each.</p>
 33608: <p>In this case, I don't think that a device is "<em>using SPI to 'use up' the entire SPI bus so that other peripheral devices can't interact with the microcontroller</em>". I think that your problem probably lies with how your SD card is connecting via the SPI bus.</p>

<p>The problem is that a lot of Serial Peripheral Interface (SPI) devices, particularly the cheaper ones, don't properly put the MISO pin into high-impedance when SS is pulled high.</p>

<p>I had almost exactly this situation with one of my projects. I eventually resolved it by placing a tri-state buffer in the MISO line for each of the SPI devices.</p>

<p>In that case, I used a <a href="https://assets.nexperia.com/documents/data-sheet/74HC_HCT125.pdf" rel="nofollow noreferrer">74HC125</a> (4-channel tri-state buffer).</p>

<p>This is the page on <a href="https://www.dorkbotpdx.org/blog/paul/better_spi_bus_design_in_3_steps" rel="nofollow noreferrer">Better SPI Bus Design in 3 steps</a> that finally got me on the right track. I think the explanations are reasonably clear (at least compared with many other sites I found!).</p>
