diff --git a/README.md b/README.md index 3b0e6ffdd9fd6af585883309488b7b21fca0c93b..50ca9617f1bd39e5a8137f3812bee518d705f8cf 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ TinyNets is stateless, resilient multipath message passing for networked control systems. -See a longer report on the work (for 6.829) [here](https://gitlab.cba.mit.edu/jakeread/tinynets/blob/master/document/6-829_project-jr_dk_ns_pw_Tiny_Nets_finalReport.pdf). +See a longer report on the work (for 6.829) [here](https://gitlab.cba.mit.edu/jakeread/tinynets/raw/master/document/6-829_project-jr_dk_ns_pw_Tiny_Nets_finalReport.pdf). ## Networked Control Systems (NCS) @@ -30,17 +30,17 @@ TinyNet routers maintain a port forwarding table and update one-another on their We show that TinyNets recovers fairly well from the loss of nodes: - + In addition, we developed TinyNets to run on small microcontrollers, that can simulatenously be used to do 'other stuff' - i.e. motor control, sensor reading, etc. - + - + On the hardware we tested (a 300MHz embedded uc) we record a packet processing time<sup>3</sup> of about 37us. - + With a bitrate of about ~2MBPS we do a total per-hop time of ~ 100us. This means that between two nodes we can run a 10kHz control loop.