1.1.3

Description of bug: Only 4 out of 14 modules can be connected to & read by OBDeleven
Android software version: 8.0, iOS 12.4.3 (identical issue across both devices)
Phone: Azpen A780, iPhone 6 (identical issue across both devices)
Dongle variant: Nextgen Pro
Car: Audi A4, 2008 3.2


The Problem: I can only connect to 4 modules (engine, headlight, ABS, and airbags). All other modules show black circle and yield a communication error when attempting to select & communicate with them.

Process of Elimination Steps Taken:

• Purchased Android 8.0 tablet to eliminate iOS as the root cause. Android behaves in the exact same way as iOS. I don't think the issue is with my iPhone.
• Scanned a friend's 12' Jetta and it read all modules successfully without drama. This suggests I might have a CAN BUS issue rather than an OBDeleven hardware/software issue.
• Measured simple voltage and resistance of my CAN BUS. Expected voltage, ground, and Ohm readings at the OBD 2 port look good. Numbers all reflect what should be an intact & functional CAN BUS
• Took the car to a professional shop and paid to have the CAN BUS tested & inspected. He was able to access all modules & communicate with my A4 without issue using his professional equipment. He gave me a computer print out from his system reflecting green status and info for 14 modules.

Conclusions:

1. Same behavior across both iOS and Android, likely not an iOS or Andriod problem. 
2. Car has been professionally confirmed to have a functioning CAN BUS network, the car is likely not the problem.
3. OBDeleven dongle & iOS device can successfully scan a 2012 Jetta but not a 2008 A4. Perhaps OBDeleven is fully capable at working with newer generation VAG networks and struggles with older generation VAG networks? Countless people have had success using OBDeleven that are the same vintage at my 08' A4. Unknown if previous generation OBDeleven is afflicted in the same way. Suggests my dongle is capable of working correctly in some situations.   
4. Is this perhaps a recent OBDeleven software bug and/or hardware defect(s) that have made their way thru the supply chain an into the hands of customers?  I have not invested time to understand if this type of issue has always existed with OBDeleven or if this is a more recent type of issue.
5. OBDeleven has been public about recent quality control and how it impacted their production & supply chain. Possible they have already fixed the quality issues and are just working to manage the percentage of customers who were impacted?   Perhaps OBDeleven is still struggling with root cause analysis and implementing corrective actions? 
6. I would hope that this is not a known fault for which a business decision was made to simply accept and not invest to correct.   As an engineer, I can envision OBDeleven technical resources want to resolve issues and it is unlikely people are choosing to turn a blind eye to a know problem.

Speaking from a position of relevant & deep product technical & business experience, effective communication is huge when facing unexpected issues in an organization. Inform your customers of what is likely the issue. OK if you don't have a solution fully sorted or if the issue is unfixable.  Either way, some honest communication goes a long way to give clarity so we can make the best choice on where to go next. Good for your customers, good for your business.


This is likely my last attempt to catch OBDeleven's attention for help. My sincere hope is that somebody from OBDeleven monitor's these boards at some frequency, will read this post and hopefully understand the point I am trying to make.  Also hope my issue and troubleshooting approach will be helpful for somebody.  If my problem is familiar to somebody on these forums, please shout it out.   I'd love to be the one making an error... would be a lot easier than crafting these detailed exhausting posts, sitting back and hoping somebody with knowledge will offer information that can help.

Hi there,

thank you for your detailed messages! 

We are investigating this exact issue and will inform you here as soon as update will be released.

This issue is already released in 1.1.4 Release Candidate and will be available this week hopefully.

---

We are also accepting requests for Release Candidates testing.

If you are experiencing issues like this and would like to contribute to the development, please contact our customer support or send a private message with these details:
- OBDeleven user email
- issue(s) you are experiencing
- vehicle(s) (make, model, year) you can test on

Description of bug: Wrong Mileage readout, App crashes occasional while switching to display fault codes
IOS software version: 1.1.3 
Phone: iPhone XR 
Car: Audi, A8L 2012 


I received the OBDeleven yesterday and checked the car.The Mileage shown in the app does not match the mileage on the car. while retrieving and checking error codes, the app mainly crashed when trying to display the air conditioning errors.
thanks 

thanks for the info. per conversion, from km to mls, the amount shown is correct. 

Im looking fwd downloading the new version.

any rough ETA on the Pro version for the IOS ? 

thanks

Please add me to your testing group.

Should we post here when testing 1.1.4 or is there another place?

My modules are now showing up. I am to scan and clear faults. I have not tried any apps yet.

2016 Passat NMS
iPhone XS Max iOS 13.3
Next gen device
1.1.4

Description of bug:

Updated firmware, now program crashes when attempting to clear control module ‘brake’ faults. All other control modules were able to be cleared.
Note: I was able to open the ‘brake’ module, it was after I clicked ‘clear faults’ when the program crashed.

IOS software version: 13.3
Phone: iPhone 8 Plus
Car:VW Golf TDI SEL 2015