# Using Nuc with USB

**URL:** <https://forum.core-electronics.com.au/t/using-nuc-with-usb/19918>\
**Category:** Core Electronics\
**Created:** [10 May 2024 05:03 UTC](https://forum.core-electronics.com.au/t/using-nuc-with-usb/19918 "2024-05-10T05:03:02Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Pixmusix](https://yyz2.discourse-cdn.com/flex028/user_avatar/forum.core-electronics.com.au/pixmusix/32/9719_2.png) [@Pixmusix](https://forum.core-electronics.com.au/u/Pixmusix)\
**Post date:** [12 May 2024 08:48 UTC](https://forum.core-electronics.com.au/t/using-nuc-with-usb/19918/12 "2024-05-12T08:48:26Z")

</div>

> [@Vx2124](#):
>
> In a typical software engineering scenario, I’d look at sockets, async messaging (pub/sub or mqtt) or API style (eg. python fastapi) using wifi / ethernet cable with a hub. I’m comfortable handling the security around any of this.

### 1

Raspberry Pis 3-5 are essentially tiny 4 core computers so a network solution would be fine 🙂.  
Depending on what kind of data you want to send it might be the best approach.  
It might be overkill for controlling motors.

### 2

Another search term you could explore is _interrupts_.  
For example,

_Agent A_ and _Agent B_ share a “BUS” which contains 1 byte of data (which is usually enough 😛 ).

_Agent A_ leaves a message in the BUS for agent B.

If _Agent A_ wants to talk to _Angent B_ then A would send a HIGH signal to one of B’s GPIO pins which triggers a HARDWARE interupt.

_Agent B_ stops what it’s doing and reads whatever _Agent A_ put on the BUS.

### 3

I haven’t personally replicated this but @James46717 is a respected regular here.

> [@Pi Pico W to Pico W - Simple Communications](https://forum.core-electronics.com.au/t/pi-pico-w-to-pico-w-simple-communications/16188):
>
> Following success with my latest project. Main aim being to develop a simple way of getting two Pico W’s to communicate, thought I would share the Python code I developed. One Pico W sets itself up as a WiFi Access Point and listens for a connection from the other Pico W. The other Pico W connects to the Access Point, collects data and sends it. The Access Point responds with ‘success’ if data is received ok. The code here is the basic for the communications, whatever is done with the data …

### 4

Some search terms for light weight requirements are “UART” and “Serial”

---

_[View the full topic](https://forum.core-electronics.com.au/t/using-nuc-with-usb/19918)._