How many communication busses at once on an Arduino UNO?

I haven't been able to find an answer and maybe there isn't one.

How many communication busses can you configure an Arduino UNO to use at one time?

The parts I would like to work with are using a variety of busses. The DS18B20 uses the one-wire bus, the MicroSD card use SPI, and the LCD, RTC, DAC and ADC are on I2C. As far as I can tell the pinouts are mutually exclusive.

Will there be a problem with the libraries conflicting on a resource that I don't know about yet? Or am I all good?

Are there any communication busses that are known to conflict?

adwsystems:
Will there be a problem with the libraries conflicting on a resource that I don't know about yet? Or am I all good?

Are there any communication busses that are known to conflict?

No, and no. What you propose is normal. The One-wire pin is nominated by you, usually pin 3. The busses are standardised and, if you want to use them as a bus, just don't use them for anything else, e.g. the CS pin for something on the SPI bus.

Just checking.

Oh yeah, I also will be running the serial port too. So up to four busses.

Eventually I would like this project to transmit to a receiver for remote display. I don't know what protocol the input for the as-yet-unknown module will require.

adwsystems:
Oh yeah, I also will be running the serial port too. So up to four busses.

Serial port is not a bus, but the same applies.

I don't know what protocol the input for the as-yet-unknown module will require.

Well I don't suppose anybody else will, either, but the above will still apply, and what you propose is still normal. You may have some problems with the details, but the principles of what you propose are simpler than you think.

I might point out two little traps.

The variety of duties in your project means that you may run out of memory before you run out of pins. While I have said that what you propose is normal, a Mega is a better proposition for datalogging.

Using bluetooth, which you may want for external display, doesn't put any extra imposition on Arduino's resources over those you probably already use for the serial monitor, i.e. there is nothing special about it.

Why do you say a Mega is better for data logging?

My plan is to use an SD card to hold the data.

because of the variety of duties, all which require code to operate them. By all means use an SD card to store data, but you still need somewhere to park the code that operates the SD - and the display, and the clock, and the sensors, and something else that you haven't thought about, but surely will think about next week.