## ## ## # ## ####### ##### ## ##
_______ ( ____ \ | ( \/ | (_____ (_____ ) ) | /\____) | \_______)
_ ( ) | | | | _ | |_( ) (____/'
____ | _ \ | |_) | | _ < | |_) | |____/
## ## ## ## ## ## ## ## #####
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: I have done the simple traction control module, well, PCB for now, based on ATmega128. It has 4x20 LCD incorporated, 2 UARTs, SPI, 7 0.5A outputs, 7 analog inputs, digital inputs/outputs, etc.. The primary goal is calculating wheel's speed, and putting the information to the VEMS. The secondary goal is calculating 0-60-100mph, 100-200kmph, 0-200-400-1000m, average consumption, trip times, etc... http://memimage.cardomain.com/ride_images/1/2822/1741/7053370276_large.jpg http://slike.hr/vidi/tcm0.gif ---- Question: AIM protocol on VEMS doesn't have all the information. Can the AIM protocol be expanded for this information (injector time, etc)? ---- Nice job you have done and think a lot of people could use the idea. I think if we should make a daughter board it should have several functions not only traction control. The avr 128 has a lot of IO and we could them fore other functions like launce, als and so on The commutation must be Can so we can send and resave information’s between the two boards also Can is the future if we some day should tray to control cars newer then 2000 I have no idea haw difficult it is to make the code but worth to consider Tnx Peter Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.