Yeah the stuff over bluetooth is useless except for show.
The lag is nothing to do with Bluetooth.
Yeah the stuff over bluetooth is useless except for show.
The lag is nothing to do with Bluetooth.
That's awesome!!! I sincerely hope you get it to work. Thank you for taking the time to work on it, and I look forward to seeing what you come up with :thumbsup:I'm looking into real world useful setups so lag is not an option. If I can come up with something, I will post everything on how I did it including all project files, animations, ...everything. If I can get this digital dash setup working, I want everyone to be able to duplicate my results.
I'm looking into real world useful setups so lag is not an option. If I can come up with something, I will post everything on how I did it including all project files, animations, ...everything. If I can get this digital dash setup working, I want everyone to be able to duplicate my results.
Sure.... but do you understand why it's not the bluetooth that cases the lag?
I remember looking at the baud rates of the 2g ECU's. They are different depending on which year but should be able to support enough to drive a tach, speedo, and a few other values real time.
This project has been on the shelf for a few months so if I'm way off, please help out. I could see a separate thread being started for this project.
also the mut-iii uses something reffered to as v.i.s. i believe... that vis receives input from teh diagnostics ports on the car and then sends info to a laptop with proprietary mitsubishi software on it.
If that's the case, then it's easy enough to just pipe all of that information into an array which will drive the animation. Any links on where that information is?
Once there is a decent pool of initial information, I think I'd like to break this off into it's own thread. I don't want to detract too much from the Apex specific stuff. This project could be implemented into other Superlite cars besides the Apex.
If the data is accessable and the bandwidth is able to support this, I plan on fronting the cost of hardware to try it out.
I'm not sure if the 2G Eclipses used CANBus but I'm doubtful.
Proprietary..... Means you're unlikely to be able to pull that same information.
The reason why newer cars like the C7 are able to do it is because they use CANBus to the cluster and is almost certainly available via the OBDII port as well.
Pre-CANBus cars use older and much slower protocols through the OBDII port so unless you have those proprietary diagnostic tools/software, you may be SOOL. I'm not sure if the 2G Eclipses used CANBus but I'm doubtful.
this is great info i think its actually what jason is talking about. and the baud rate is how fast it reads right? ecu flash is evo 8 ecu's and late plastic 2g ecu's ??I've read conflicting information on various sites but I think CANbus didn't start until evo10.
2g's are either ISO 15765 (CAN) or ISO 9141
If someone looks at their OBD2 connector - Pin 6 and 14 vs pins 7 and 15 will determine if it's CAN. (I guess manufacturers can include both protocols also)
I think its ISO9141. I also read that ecu flash increased the maximum allowable baud rate to 125000 baud. Not sure if link does something similar.
Also....Here's some work done installing an S2000 cluster...I didn't read the whole thing but I think there's some good info.
2G S2000 ap2 2006 cluster on Mitsubishi Eclipse almost done! - DSM Forums
Apologies if this is no help
this is great info i think its actually what jason is talking about. and the baud rate is how fast it reads right? ecu flash is evo 8 ecu's and late plastic 2g ecu's ??