search

WebsterXC / digidash

CSE442 group project that will consist of Raspberry Pi software development. Our goal is to create a plug-and-play digital dashboard and engine monitoring system.
GNU General Public License v3.0
2 stars 3 forks source link

How to control with mouse ? #69

Open engineer00127 opened 6 years ago

engineer00127 commented 6 years ago

first at all, thanks for sharing this awesome project. what i need to do if i don't have touchscreen and i want o control via mouse USB

WebsterXC commented 6 years ago

Sorry for the late reply. How are you invoking DigiDash? Is it on a Linux PC or a Raspberry Pi?

engineer00127 commented 6 years ago

thanks for responding , i am using it on Rasp Pi 3 B+ by the way, i am having problem that digidash have already connected to ELM327 adapter but it has not connecterd to the car , would you mind helping me to solve it? i don't know what to do, everytimes when i run the digidash, it connected successfully with ELM327 adapter but the gauges didn't show the real data from the engine, it didn't work ! I'm thinking the elm327 i am using such a fake one, can i use another OBDII bluetooth adapter to run the digidash? thanks a lot !

On Thu, May 31, 2018 at 11:15 PM, Will Burgin notifications@github.com wrote:

Sorry for the late reply. How are you invoking DigiDash? Is it on a Linux PC or a Raspberry Pi?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WebsterXC/digidash/issues/69#issuecomment-393587123, or mute the thread https://github.com/notifications/unsubscribe-auth/AliPeKQ1b8MUpHDD3sS6lCeMms7HuJooks5t4BcYgaJpZM4UO_sq .

WebsterXC commented 6 years ago

We had a nightmare of problems with the ELM327 adapters when we did this project. If I recall correctly, all of the group members purchased ELM327 adapters and only 2 of them functioned in the way the manual said they would.

That being said, ensure that your engine is running after installing the ELM327 adapter in the OBD-II port. Some adapters go to sleep when the engine is off, despite there being valid data on the bus. However, if the engine is on, your Raspberry Pi successfully connects to the ELM adapter, and the gauges still don't display valid data, there's probably some communications error we didn't program for.

Unfortunately the project is hard-coded to use the ELM327 protocol, so the only way to use a different OBD-II bluetooth adapter is if it supports ELM327 as well. In hindsight, ELM327 was not robust enough for our project, but by the time we realized it, it was halfway through the semester and too late to switch.

EDIT: It took some deep searching, but here's the final video we ended up making for it:

https://www.youtube.com/watch?v=gZcLh4JdHmA

engineer00127 commented 6 years ago

Thanks for letting me know your nightmare about ELM327, how frustrated that i’m facing with the same nightmare to you , moreover i am not a coder :((( I have bought 2 ELM 327 and try to run 4 project on github , there all were failed , each one will bring back to me some different error from the other one . And all off the error is about the communication i think , even i am not o coder but after day to day facing with it and fi ding solutions through the internet i can feel that ! Programs can connect with adapter but can not connect to car . That is the same result between 2 of 4 program that i had already tried , the other one connected to ecu and sent “0100” to the ecu as well, it received back the messege with 7E8 and 7E9 stand from the first location from the left of the messege, it mean the program is communicating with ecu but by some how , it connected Unsuccessfully! It also showed me the error after that : ^0x ...invalid token...and the last project that i’d tried to run could connect successfully with car and i could type the command like RPM to query data from engine. What do you think about my case ? Where exactly the problem is ? Thanksful !