DashSketch 'Virtual Cockpit' for iOS - Beta Testers Wanted

[stefcio007]

I know the use will be a bit limited but do you plan on Apple Watch support?
For remote tasks and possibly single data read outs?

[HLS]

Yep its in a measuring block. I can probably find out some more info. Have a look in one of their label files (or is it the other one can't remember

FWIW on the Mk7's I think the correct boost is available just via normal CAN however there are two MAP sensors (charge pipe and inlet manifold) and I haven't had a chance to see what my elcheapo bluetooth dongle is reporting.
It will be really good it you guys can get all this sorted because really the only other option around is vagcom and its incredibly slow and clunky. Well there is another option around too but its not available to the general public

awesome work so far BTW

Thanks for the help - I'll report back today once I've had a play with the CAN sniffer and VCDS. Appreciate the kind words also!

I have a R36 and MkII Octavia vRS.
Plus a fair bit of experience with retrofits, vcds coding, RNS units etc be happy to participate in a beta and try and help realise what is looking like a great product already!

Sent from my HTC One_M8 using Tapatalk

Thanks Kamold - I'll shoot you a PM this morning. We're always very happy to get more experienced help with testing.

I know the use will be a bit limited but do you plan on Apple Watch support?
For remote tasks and possibly single data read outs?

It's on our radar, but as we focussed initially on the iPad layouts we haven't built an Apple Watch design as the Watch only pairs with an iPhone.

That said, we're building integration with the cloud service IFTTT - for those who haven't used it, it's a service that lets you link any internet connected devices with a huge number of other apps. For example, we've setup a test trigger that detects when you go over the speed limit and sends an email to a designated address, but you could configure yours to post to Facebook, send a Tweet, flash a light in your fleet manager's office etc etc.

What's relevant here is that the IFTTT app on your iPhone also gets a push notification when that event occurs, which means your Apple Watch gets the notification and vibrates on your wrist. With that setup you could configure your own notifications - so for example have the watch vibrate 200m from your next navigation turn, once for turn left and twice for turn right.

[HLS]

I had a play with VCDS this afternoon using our CANBus logger to see what's going on, and I can confirm that:

1. VCDS relies on the OBD2 protocol to determine data PIDs in OBD2 mode, so it will only read those PIDs that VW 'officially' supports. That is, no MAP boost pressure, though some vehicles (like the Beetle 1.4TSI, but not the Mk6 Golf R) do return an pressure value that we may be able to interpolate into a boost reading.

2. VCDS grabs the 'actual' boost value from the Engine module (0x740) using measuring block 0x73.3. I've logged the session and we can reproduce the communication steps and decode the protocol on our CAN test hardware. I'm not sure however if we can implement that communication session over Bluetooth using an ELM327 (ie generic OBD2 Bluetooth Adapter) - that testing will have to wait until after we wrap this first build of DashSketch.

If we can't perform that communication session over those OBD2 Adapters then we'd need a different hardware Adapter to communicate between our app and the car. We have already developed a CANBus Adapter that would do the job, but we're using it in a completely different manner.

What VCDS does to obtain data is to perform an active request-response session using the OBD2 connector. The CAN Gateway passes the requests to the correct ECU module, which returns the requested data. VCDS can sample a single measuring block about 6x per second using this method. The big advantage here is that you can plug in a VCDS cable in about 2 seconds and remove it just as quickly.

Our CANBus Adapter actually sits on the 'car' side of the CAN Gateway, tapping directly into the 3 main busses (2 in old or MOST-enabled cars). Rather than doing request-response for specific values it just watches every CAN packet sent on the busses and grabs the data we are interested in from there. This gives us much faster data rates but not every piece of data is sent across the busses on a regular basis. The disadvantage is that it's a much harder (though still completely reversible) installation process.

In any case, thanks for the hints regarding the measuring blocks - most appreciated.

[HLS]

A few updates as we get closer to the public launch of DashSketch:

•VWs built on the Mk7 platform appear to return a reasonably accurate manifold pressure value which can be interpolated into boost pressure using the local atmospheric pressure. With this method we can display 'calculated' boost on the Mk7 platform cars (including current generation Beetle).

Our testing on the Beetle (which has a VW factory Boost gauge) shows the calculated value to be almost 100% accurate, up to and including any boost spike values.



•Our latest Beta builds include our DashCam component, and enable use of the app without any vehicle connection (relying solely on the device's GPS for speed and location data). We're still looking to expand our Beta program, so if you're interested in testing a new DashCam with data logging in your car please drop us a note!

[stefcio007]

Nice to see IFTTT integration as I've used it a lot for home automation linked to my iPhone.

[HLS]

As of our latest build you can now use DashSketch to live stream vehicle data to other devices running DashSketch - which means you can setup a multi-screen digital cockpit in your car: