dj92
11-29-2013, 05:18 PM
Hi there,
some days ago, I've completed my LCD gauge using a GLCD, an Arduino pro mini, a generic ELM OBD adapter (with BT) and a bluetooth master which connects to the adapter's BT module :)
Overall cost was far less than 50€.
http://files.brauchmer.net/imghost/up/small_fbd15818f9bd03d9d246cefa82e850cc.jpg (http://files.brauchmer.net/imghost/up/fbd15818f9bd03d9d246cefa82e850cc.jpg)
http://files.brauchmer.net/imghost/up/small_c7eed6540f087453c86c6f34cf9d9758.jpg (http://files.brauchmer.net/imghost/up/c7eed6540f087453c86c6f34cf9d9758.jpg)
Sadly the green has the usual yellowish tint in reality unlike in the pictures.
1st world problems :laugh:
When I turn on IGN, the bluetooth module looks for the adapter's and establishes a connection.
http://files.brauchmer.net/imghost/up/small_39db6f71e8b5f34f941d8abf3c6f2b86.jpg (http://files.brauchmer.net/imghost/up/39db6f71e8b5f34f941d8abf3c6f2b86.jpg)
Then, the arduino sees a wired-like connection to the ELM where it sends queries to.
If it gets an answer, the "init"-loop is quit and the usual operation begins:
http://files.brauchmer.net/imghost/up/small_c0db275280374ec838911f76ef0c211c.jpg (http://files.brauchmer.net/imghost/up/c0db275280374ec838911f76ef0c211c.jpg)
And when I start the engine:
http://files.brauchmer.net/imghost/up/small_2379cfa7fce9571820f12740e2361f16.jpg (http://files.brauchmer.net/imghost/up/2379cfa7fce9571820f12740e2361f16.jpg)
Attention, it really reads "C[oo]L[a]NT" at 2 o' clock :biggrin:
I've decided against adding more values because of the rather small display area and the fact that the ELM-clone runs just at 4MHz and is rather slow because of that.
By now, the responsiveness is acceptable.
The values are aligned at te left end, so they don't woggle too much if they change between values (e.g. the RPM).
For the next generation, I've got already a module with a PIC32 @80MHz in the drawer that I'm going to hook up to the CAN directly.
Because I'm not limited to OBD requests, I can passively get parameters flying around on the bus - including a (IMHO) quite accurate value for the injected fuel amount.
Upon request, I can post the rather ugly (but working fine) code, the schematics are so easy I haven't made a plan.
some days ago, I've completed my LCD gauge using a GLCD, an Arduino pro mini, a generic ELM OBD adapter (with BT) and a bluetooth master which connects to the adapter's BT module :)
Overall cost was far less than 50€.
http://files.brauchmer.net/imghost/up/small_fbd15818f9bd03d9d246cefa82e850cc.jpg (http://files.brauchmer.net/imghost/up/fbd15818f9bd03d9d246cefa82e850cc.jpg)
http://files.brauchmer.net/imghost/up/small_c7eed6540f087453c86c6f34cf9d9758.jpg (http://files.brauchmer.net/imghost/up/c7eed6540f087453c86c6f34cf9d9758.jpg)
Sadly the green has the usual yellowish tint in reality unlike in the pictures.
1st world problems :laugh:
When I turn on IGN, the bluetooth module looks for the adapter's and establishes a connection.
http://files.brauchmer.net/imghost/up/small_39db6f71e8b5f34f941d8abf3c6f2b86.jpg (http://files.brauchmer.net/imghost/up/39db6f71e8b5f34f941d8abf3c6f2b86.jpg)
Then, the arduino sees a wired-like connection to the ELM where it sends queries to.
If it gets an answer, the "init"-loop is quit and the usual operation begins:
http://files.brauchmer.net/imghost/up/small_c0db275280374ec838911f76ef0c211c.jpg (http://files.brauchmer.net/imghost/up/c0db275280374ec838911f76ef0c211c.jpg)
And when I start the engine:
http://files.brauchmer.net/imghost/up/small_2379cfa7fce9571820f12740e2361f16.jpg (http://files.brauchmer.net/imghost/up/2379cfa7fce9571820f12740e2361f16.jpg)
Attention, it really reads "C[oo]L[a]NT" at 2 o' clock :biggrin:
I've decided against adding more values because of the rather small display area and the fact that the ELM-clone runs just at 4MHz and is rather slow because of that.
By now, the responsiveness is acceptable.
The values are aligned at te left end, so they don't woggle too much if they change between values (e.g. the RPM).
For the next generation, I've got already a module with a PIC32 @80MHz in the drawer that I'm going to hook up to the CAN directly.
Because I'm not limited to OBD requests, I can passively get parameters flying around on the bus - including a (IMHO) quite accurate value for the injected fuel amount.
Upon request, I can post the rather ugly (but working fine) code, the schematics are so easy I haven't made a plan.