- Joined
- Feb 25, 2014
- Messages
- 2,780
- Reaction score
- 4,490
- Location
- Cincinnati, OH
- VCDS Serial number
- C?ID=25607
More thoughts after some weekend play time.
New UDS control modules: It's hard to find what I want in the sheer volume of data available. I'm used to ME7 cars and I kind of know where the interesting MVBs are. The ECU in my loaner 2013 Turbo Beetle appears to offer up nearly 1,000 separate data items. It takes a good while to set things up on VCDS Mobile just due to the volume and the browser interface. VCDS Desktop is faster to navigate, but the list is only partially alphabetized with no search available.
I'd love to see some default presets made available for common troubleshooting scenarios. Some random examples:
VCDS Cloud stuff: Any interaction I have with Cloud functions is really rocky. I had written this off to my home wireless range issue, but I spent some time today working via AT&T LTE tethering on my smartphone and I wasn't having much more luck. I do eventually get through, but I often have to try things several times. My laptop was on the same tethered BSSID so I could play with VCDS Desktop, and it had good connectivity. All three devices were in the same car. The server ping function under Options->Self Test seemed consistently okay. Do you know of any server-side reason I'd have trouble this weekend?
I'm wondering if I have issues with tangled-up device registration records. I had to try registering the unit a few times today, and I thought I had gotten it successfully registered already a couple weeks ago. The provenance of my particular HEX-NET unit is a little unusual, as Uwe or Andy will know. It had definitely seen some cars before I received it. Before I start doing real network-layer digging, I thought I'd ask if there's any other explanation.
The vcds-cloud.com website currently uses a self-signed TLS certificate. That creates kind of a speed-bump when we're handed off between HEX-NET and Cloud functions, especially when we're on a new device. I'm guessing that will change before HEX-NET comes out of Beta though.
Jason
New UDS control modules: It's hard to find what I want in the sheer volume of data available. I'm used to ME7 cars and I kind of know where the interesting MVBs are. The ECU in my loaner 2013 Turbo Beetle appears to offer up nearly 1,000 separate data items. It takes a good while to set things up on VCDS Mobile just due to the volume and the browser interface. VCDS Desktop is faster to navigate, but the list is only partially alphabetized with no search available.
I'd love to see some default presets made available for common troubleshooting scenarios. Some random examples:
- Troubleshooting misfires: Select all individual cylinder misfire counters
- Troubleshooting A/F ratios: Select mass air-flow specified and actual, all fuel trim data (turns out to be widely scattered now!), etc
- Troubleshooting transmission slippage: Select current gear, engine RPM, transmission input RPM (TC slip), transmission output RPM, etc
VCDS Cloud stuff: Any interaction I have with Cloud functions is really rocky. I had written this off to my home wireless range issue, but I spent some time today working via AT&T LTE tethering on my smartphone and I wasn't having much more luck. I do eventually get through, but I often have to try things several times. My laptop was on the same tethered BSSID so I could play with VCDS Desktop, and it had good connectivity. All three devices were in the same car. The server ping function under Options->Self Test seemed consistently okay. Do you know of any server-side reason I'd have trouble this weekend?
I'm wondering if I have issues with tangled-up device registration records. I had to try registering the unit a few times today, and I thought I had gotten it successfully registered already a couple weeks ago. The provenance of my particular HEX-NET unit is a little unusual, as Uwe or Andy will know. It had definitely seen some cars before I received it. Before I start doing real network-layer digging, I thought I'd ask if there's any other explanation.
The vcds-cloud.com website currently uses a self-signed TLS certificate. That creates kind of a speed-bump when we're handed off between HEX-NET and Cloud functions, especially when we're on a new device. I'm guessing that will change before HEX-NET comes out of Beta though.
Jason