Boost4VR4
12-24-2012, 03:54 AM
Ok here's the story:
I took a look at duke3k's setup with his custom controller to control and run self-test diagnostics on his existing ECS struts. I am taking it a step further, but I am also simplifying things quite a bit.
First, I will outline what the scope of the project is going to be:
ECS Servo motor control will be done with an Arduino Mega 2560.
The same Self Test abilities will be available similarly like duke3k's setup, except it will be software based.
The front end software will be compatible with Windows distributions to start, then I plan to expand it for use with Centrafuse, a CarPC software front-end.
Other functionality:
G-Force readings based on X/Y axis on an accelerometer
Dampening force readings based on Y axis on accelerometers on all of the struts
Future functionality:
integration with OBD1/OBD2 readings and displaying that data in addition
The Arduino boards are very easy to program and require very little memory. They are rudimentary and have a very large community for coding. I chose the arduino because I wanted a common programming language platform and I also wanted an easy to use programming method.
The accomplishments so far:
I have written the code for the ECS Self-Test on the arduino board, the next step is to gather user input via serial for setting values in rotational degrees. I am working with a 180 degree servo at the moment, however it will not require any additional coding when I switch over to the ECS servos, as I will only need to provide the "safe" values in degrees for the strut adjustments. I also do not have an accelerometer at the moment, but I will need to calculate the raw values of the accelerometer data to provide a meaningful data statistic for the user to see (forces in Gs). Once I come up with all of the solutions to the problem, I will then be able to build the front-end program to send and receive data to the arduino board via USB serial and dedicated serial channels.
I will keep you guys posted on the progress. So far, it has been positive, other than accidentally swapping positive and negative wires and frying the bluetooth interface I just bought today!
Stay posted!
I took a look at duke3k's setup with his custom controller to control and run self-test diagnostics on his existing ECS struts. I am taking it a step further, but I am also simplifying things quite a bit.
First, I will outline what the scope of the project is going to be:
ECS Servo motor control will be done with an Arduino Mega 2560.
The same Self Test abilities will be available similarly like duke3k's setup, except it will be software based.
The front end software will be compatible with Windows distributions to start, then I plan to expand it for use with Centrafuse, a CarPC software front-end.
Other functionality:
G-Force readings based on X/Y axis on an accelerometer
Dampening force readings based on Y axis on accelerometers on all of the struts
Future functionality:
integration with OBD1/OBD2 readings and displaying that data in addition
The Arduino boards are very easy to program and require very little memory. They are rudimentary and have a very large community for coding. I chose the arduino because I wanted a common programming language platform and I also wanted an easy to use programming method.
The accomplishments so far:
I have written the code for the ECS Self-Test on the arduino board, the next step is to gather user input via serial for setting values in rotational degrees. I am working with a 180 degree servo at the moment, however it will not require any additional coding when I switch over to the ECS servos, as I will only need to provide the "safe" values in degrees for the strut adjustments. I also do not have an accelerometer at the moment, but I will need to calculate the raw values of the accelerometer data to provide a meaningful data statistic for the user to see (forces in Gs). Once I come up with all of the solutions to the problem, I will then be able to build the front-end program to send and receive data to the arduino board via USB serial and dedicated serial channels.
I will keep you guys posted on the progress. So far, it has been positive, other than accidentally swapping positive and negative wires and frying the bluetooth interface I just bought today!
Stay posted!