Create the documentation on how to bring the Freenove robot to life

[mcolinj]

1. Assemble the robot drivetrain and attach the raspberry pi. Include any assembly advice and pointers to the documenation. Also how to get to the documentation.

2. Equip your driverstation. (how to install all of the required software on the driverstation)

3. How to bring up the robot.
   Cabling for monitor/keyboard, connecting to wifi, etc...
   What options have to be set in raspi-config (related SPI, I2C busses, for example)
   Reboot.

4. How to find your robot. how to find the robot on the network. (many possible, many should be explained)

5. How to start the robot running and the driverstation running.

6. How to update the robot software

[numerator]

The documentation lives here: https://docs.google.com/document/d/13n1QN8vziR7Z6QPZxJy76q95Cz_2N0AkUMWgDU8ddN0/edit?usp=sharing

Still a living document as people encounter new problems, so keeping this issue open for now.

[EmilyRobotics]

Should we move this to the Readme?

[numerator]

Maybe leave it on Google for now until everyone has gotten through the instructions. Easier for group editing and commenting on Google (esp. while people don't know GitHub). We can pickle it and put it into the README once we're sure it's stable.

[EmilyRobotics]

I meant we could close the issue and put the link to the instructions in the readme

[numerator]

Ah. Then yes. That would work!

…

On Tue, Dec 1, 2020 at 10:44 PM Eli ***@***.***> wrote: I meant we could close the issue and put the link to the instructions in the readme — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPBFVKHTXPA2YRPEAAAQSLSSWZZNANCNFSM4T6VABOQ> .

-- ||\\//|| \\//\\// ||\\|| | Mark W. Newman | Professor | School of Information & Department of EECS | University of Michigan | http://mwnewman.people.si.umich.edu | bookable office hours <https://calendar.google.com/calendar/selfsched?sstoken=UUxSUElmaGxtR0gwfGRlZmF1bHR8OGM5ZTU5NGE0MWFhYzBiNmQ0NzExMzc3Y2NjNjEwMmY>

[numerator]

Just realized though: the document is currently world-writable. Perhaps should be changed to allow comments but not editing. I'll do that.

…

On Tue, Dec 1, 2020 at 10:54 PM Mark Newman ***@***.***> wrote: Ah. Then yes. That would work! On Tue, Dec 1, 2020 at 10:44 PM Eli ***@***.***> wrote: > I meant we could close the issue and put the link to the instructions in > the readme > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#36 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAPBFVKHTXPA2YRPEAAAQSLSSWZZNANCNFSM4T6VABOQ> > . > -- ||\\//|| \\//\\// ||\\|| | Mark W. Newman | Professor | School of Information & Department of EECS | University of Michigan | http://mwnewman.people.si.umich.edu | bookable office hours <https://calendar.google.com/calendar/selfsched?sstoken=UUxSUElmaGxtR0gwfGRlZmF1bHR8OGM5ZTU5NGE0MWFhYzBiNmQ0NzExMzc3Y2NjNjEwMmY>

-- ||\\//|| \\//\\// ||\\|| | Mark W. Newman | Professor | School of Information & Department of EECS | University of Michigan | http://mwnewman.people.si.umich.edu | bookable office hours <https://calendar.google.com/calendar/selfsched?sstoken=UUxSUElmaGxtR0gwfGRlZmF1bHR8OGM5ZTU5NGE0MWFhYzBiNmQ0NzExMzc3Y2NjNjEwMmY>

[numerator]

Fixed.