Commit 0c216831 authored by Jake Read's avatar Jake Read
Browse files

minor note updates

parent f3d63367
......@@ -2,11 +2,11 @@
**Status**
The project is ongoing. Circuit designs listed here are stable, but software across the board is undergoing a big shift: things are getting better. Currently aiming at March 1 *release* of dataflow-all-the-way-down.
The project is ongoing. Circuit designs listed here are stable, but softwares are changing.
## What it Is
The *Distributed Dataflow Machine Controllers* project (pending a decent name) is a collection of reconfigurable open hardware and software for machine-building, process development, and robotics projects.
The *Distributed Dataflow Machine Controllers* project is a collection of reconfigurable open hardware and software for machine-building, process development, and robotics projects.
It uses a Distributed Dataflow Programming Paradigm: hardware and software objects are all nodes in a graph, executing computing and physical tasks, together!
......@@ -26,6 +26,8 @@ This means that *adding and removing hardware to a system is easy, and possible.
- [SmallGantries](https://gitlab.cba.mit.edu/jakeread/smallgantries)
- [ClayStacker](https://gitlab.cba.mit.edu/jakeread/claystack)
(Most of these machines are built with parametric designs for their constituent components, that project is here: [RCT Gantries](https://gitlab.cba.mit.edu/jakeread/rctgantries)).
# The Endpoints
![endpoints](images/endpoints.jpg)
......@@ -44,7 +46,8 @@ Through the 60-pin mezzanine connector mentioned above, I connect the hardware-t
[Router](https://gitlab.cba.mit.edu/jakeread/daughterboard-router)
[Stepper](https://gitlab.cba.mit.edu/jakeread/daughterboard-stepper)
!TODO migrate doc from BLDC, DC, Ultra, and Breadboard.
!TODO migrate doc from BLDC, DC, Ultra, and Breadboard. Add AS5047 JST Conn Board.
!TODO make heating board (also current sensing big current board)
# The Computing Contexts
......@@ -53,8 +56,8 @@ Each of the computers participating in the control of these machines runs a *con
I call these 'DMCCs' - Distributed Machine Control Contexts. None are ready for use.
[Node.js DMCC](https://gitlab.cba.mit.edu/jakeread/dmcc-node)
[Browser DMCC: the IDOE, aka RuNDMC](https://gitlab.cba.mit.edu/jakeread/rndmc)
[Cuttlefish: the Browser DMCC: the IDOE](https://gitlab.cba.mit.edu/jakeread/cuttlefish)
[Nautilus: Node.js DMCC](https://gitlab.cba.mit.edu/jakeread/nautilus)
[XMEGA DMCC (forthcoming)]
# The Network
......@@ -81,17 +84,23 @@ Bytes between the Length Byte and the *Packet Header End Delimiter* define the r
## Wiring
#### Powering Boards
### Powering Distribution
The network cables don't carry any power, just four pairs of differential signals. So each board needs a power connection as well.
I have a small set of power distribution boards:
[PDBs](https://gitlab.cba.mit.edu/jakeread/pdbs)
I hook these up end-to-end to make blocks of just-the-kind of power splitter, etc, that I want.
The boards should all share a ground, but can run on different voltages of input power. Most will take 24v on two M3 screw-mounts - I use eye terminals soldered to 18ga wire to deliver power.
The router can also accept power from a USB device. If you're powering it over USB, *do not* also power it via 24v.
Last thing, don't power your supply on before you go to screw power connections onto the boards. Wire them up, and then switch on.
#### Network Cables
### Network Cables
At a bare minimum, you're going to be hooking these things up to power, and to each other (network).
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment