Welcome to the Tumanako Wiki
The Tumanako Project is an Open Source development effort to produce Open Source hardware and software to drive and recharge electric vehicles. Tumanako is Māori for hope & togetherness.
All Tumanako source code is licensed under LGPL3. Design documents, schematics or any other artifact that is not source code is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License. To view a copy of this licence, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California 94105, USA.
Please join our development mailing list: http://lists.sourceforge.net/lists/listinfo/tumanako-devel
Chat on the #tumanako channel on the freenode IRC server.
If you are interested in helping out please send an email to the mailing list to introduce yourself. We are particularly interested in hearing from developers with C, C++ and Java experience. Electrical engineers and embedded developers are also welcome.
Please see https://sourceforge.net/p/tumanako/_list/git for a list of git repositories.
The Tumanako EVD5 Battery Management system is a modular BMS capable of monitoring and balancing Lithium Ion cells. Each board monitors 5 cells and a central control computer controls the battery charger. Communication between nodes is via an RS485 bus. This BMS specifically measures bypassed current.
For more information please visit the Tumanako EVD5 Battery Management page.
The Tumanako Inverter is based around the STM32. It is power stage agnostic and so far has been tested to support Semikron SKiiP/SKAI modules and Powerex. If you want to get involved in development of the Tumanako Inverter, this link will give you everything you need to get started: Inverter Development - Getting Started
The Inverter project consists of at least the following components:
- Physical Design
- Casing IP65(?)
- Wiring Loom (throtle, on/off, contactor engage, forward/reverse).
The Dashboard is an Android based application which will run on a mobile phone or tablet hardware platform.
- Electrical Design
- Software (PIC10F220 Assembler)
The SolarNetwork is an Open Source software platform compatible with an increasingly large list of common "of the shelf" hardware components (e.g. grid tied inverters and load control switches) for distributed generation, monitoring and various demand side response applications.
- V2G Extensions
- User interface (specify charge mode and next vehicle use time)
- External Grid API (power company software control)
- Charger interface
- CAN (Vehicle and BMS interface?)
- Take this advice: http://jacobian.org/writing/great-documentation
- Project Logo test drive, how does it feel?: (Tumanako logo designed by Michael Stewart).
- Connect http://tumanako.net to this wiki (partially done, can we make the wiki appear in the http://tumanako.net domain?
- Make the wiki names more restful, so http://sourceforge.net/apps/mediawiki/tumanako/index.php?title=Main_Page becomes http://tumanako.net/wiki/Main_Page. See http://sourceforge.net/community/forum/topic.php?id=5201&replies=1#post-10987
- Put a feed of blog posts, wiki changes, mailing list posts and SVN commits on the front page so the project doesn't look so dead. Use pipes to combine:
- Sourceforge project page feed of the commits and stuff
- wiki change feed
- blog feed
- There doesn't seem to be a feed for the mailing list, http://mailbucket.org/ looks to be dead or dying, we can't apply patches to sourceforge's hosted mailman, and a "supported" feature is some way away so hosting http://taint.org/mmrss/ is our only option?
- Stop the wiki and blog from demanding credentials if you follow an https link while not logged in
- Make the wiki work first time when you do enter your credentials after following an https link (currently you see a blue line on a white page, if you refresh, it works)
- Make the blog enter absolute urls to locally hosted media in the RSS feed -- some RSS readers don't like relative references so you don't see any pictures. To work around this we have to modify the html version of the post to use absolute urls which is painful and has it's own problems. Explanation at the W3C feed reader (which complains about other parts of the feed but not this issue?) Fix here