Replies: 3 comments
-
Hello, for json files : 1238 if i change it with for exemple projname = proj[0:18].upper() though i don't know the impact, so i will wait for an answer here before trying with my car. |
Beta Was this translation helpful? Give feedback.
-
transformed into an issue, closing |
Beta Was this translation helpful? Give feedback.
-
This in general does not talk about vgate in readme and/or any other wiki, we do not take your accessories into account. If they work better, but that is no reason to issue issues on material that has never been mentioned and/or tested by the development team. If you find an error with an extra accessory and are able to resolve it, you can propose this in readme along with the PR (pull request) that allows it. Cordially |
Beta Was this translation helpful? Give feedback.
-
Hello,
car : renault megane 2 phase 2 ( french ) , OS : debian 12 , python : 3.12.2 , OBD2 : vgate vlinker MC+, ddt4all : 3.0.2 ( git clone )
i already noticed that before in demo mode , but if i filter the ECU i want to scan by car model ( like X84 or X84Ph2 ) the scan only lauch for trigrams , per say : X84 will work while X84Ph2 not, i tried different models in demo mode, and it was the same (dummy data only shows with trigrams ).
Though i noticed , my car ecus ( some ) shows up with a X84 scan because they can be included in multiples project as i could verify in the ecu/db.json
Is this the intended behavior ?
On the side since i found an OBD2 interface which seems to work ( so far ) i'd like to share the info here on github , but there doesn't seem to be any page acting as a database of compatible interfaces ( including where it was bought at what price and the result of elm benchmark for exemple )
Would be nice to do that... ( and maybe would have saved me a lot of time against chinese crap )
Beta Was this translation helpful? Give feedback.
All reactions