Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@RocketSurgeon because high-density GPIO networks at client. Too much noise for Wifi to be a thing.
(They're planning on having 3-4 RPis per node, 3 to 4 nodes per network, all in one huge box [like that one IBM machine that was on Jeopardy.] Mass split-job computing on a budget, as I'm told.)
not too big a deal to make whole networks act like a single client, just have one in each node with a GPIO splitter be the node master. -
@Fast-Nop if I knew I wouldn't be taking the one-off job, would I?
These guys were studying for a Java exam...from PRINTED OUT PHONE PICTURES OF CODE ON THEIR SCREENS
Hmm. In the cooking section you say...
I've gotta create a bidirectional communication protocol to link 2-3 RPis over GPIO. I have between 4-5 pins for TX and 45 for RX, so each directional bus is that wide.
Even better, I have to assume 4 bit bus length unless told otherwise, since 4 to 6 pins on the GPIO are usually used for serial/UART, COM and/or 1-pin communications (for use to get a console, not to throw data down.)
The best part?
Needs to be a Python library.
i wanna die
rant
kill me
serial
raspberry pi
gpio
4 bits is enough for all of us...?