On 15 Jul 2019, at 18:52, Craig Leres <leres@xse.com> wrote:

I don't know anything about VW network buses but with GM there are usually two buses (OBD-II up through 2014 anyway). All models have a high speed can on pins 14 and 6 of the diagnostic connector. Newer models have a low speed, single wire can bus on pin 1. Older use J1850/Class 2 PWM on pin 2. The high speed bus has mostly engine, brake and related. Doors, hvac, infotainment are on the low speed bus. Single wire can and J1850 appear to be unique to GM.

I would start by figuring out where the other buses are in your new car.

Yeah, I know some metrics seem to be carried over the classic CAN bus (battery level is often tagged "Hybrid Battery Pack something” because of hybrids in the line), Pin 1 is activated to +12 on ignition, and K-Line is pulled down eventually by diagnostic tools to trigger “gateway” accessing, but well, still in early discovery. There is lots of business going around OBD dongles for diagnostics that allow some configuration of various organs of the car (Coding / Long Coding / Adaptations, they have a broad new vocabulary to learn), I probably won’t get active help because of fear of competition (heck, à 100€ device that does it all, without licensing or credit purchase, that’s fresh!) But well, worst case, I’ll reverse engineer the whole thing, since I’m moving to a new place with an enormous and electrified garage ;-) but that’ll be for autumn. We’ll get there, I wan’t this to work !

Craig

On 15 Jul 2019, at 19:28, Michael Balzer <dexter@expeedo.de> wrote:

Julien,

hope you got that e-UP at a reasonable price, they were pretty far overpriced on introduction. But they seem to be very efficient, so good choice.

9600€ second hand 2014 64000km, perfect shape, all (few) wearable parts replaced, that’s 3 to 4000€ less than the usual second hand price in France, though the double-batteried new versions (also arriving via Seat and Skoda) is probably gonna bump down the second hand market on pre 2019 models. A friend, IT engineer at VW France, told me to give it a shot and ask for a battery swap, they haven’t answered *shrug*, but well, 150km is more than enough for me And damn, the little bug packs a punch, I can trigger traction control a tad too easily, lots of fun, and comfort compared to the Twizy, in all honesty :) Anyways, that’s me digressing.

Your CRTD log only shows OBD2 requests, and there seem to be four devices answering to them.

As Craig wrote, the process data may be on another bus, and the bus you're on now only does request/response communication.

Next would be to check for more CAN buses and to check out more OBD2 requests targeted at those four devices.

Yeah, all I saw was eventually pulling down K-Line to trigger some diag modes, though, with an OBDEleven dongle, I could play with the dashboard dials with the car fully on, so I don’t know at which point triggering that generates or opens more traffic or not without having to stall the car. I might end up opening it up to see which pins are used by elimination. I don’t believe from the little I read that CAN1 is used at all, but again, lots of the content I find are for older birds… or get my hands on a screw on OBD plug to poke around… The road will be long, but I will certainly not be satisfied by the embedded CarNet service (gotta see how that thing is connected! That’s an idea) The Twizy was simple in a sense ;-)

Regards, Michael

Am 15.07.19 um 16:43 schrieb Julien “JaXX” Banchet:

...

Hi everyone, and happy summer to all !

So, sold my Twizy a month ago, the OVMSv3.1 has left with it, got a VW e-UP! a little bit before and received a v3.2 last week. Threw away a few microSDs but got a CRTD log this afternoon.

While I have the weird impression 1335 lines and 55kB ( https://pastebin.com/FAZqnzie ) for a 30 minute drive back from work seems very short, I tried reading it in SavvyQT but it “salvages” only the first 35 lines. (30 minutes kinda full left aside the wipers, ignition off, on, launch, lights, windows, reversing, and even blinkers that Parisians try to avoid using for some odd reason, so yeah, 1335 lines, that’s not even a frame per second, something is missing)

No DBC found on the interwebz for volkswagen’s AA/12 platform, so I’m in for making a first probably ? That is if the sole CANBus connected got anything worthy (OBDII vehicle module used)

I have understood VAG cars are a bit different in a way, I wouldn’t be surprised accessing VW busses need a bit of help :)

Anybody around with a bit of knowledge with these cars ?

Best,

JaXX./. _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

On 2019-07-16 16:47, Mark Webb-Johnson wrote:

One comment:

The new format CRTD produced by OVMS includes bus# prefix. So the records look like ‘1R11’ or ‘2R11’ (for bus #1 and bus #2, respectively). SavvyCAN currently supports only the old format ‘R11’ CRTD. If you want to load these into SavvyCAN, you will need to modify the CRTD log file.

There is currently experimental support for SavvyCAN server mode in the latest bleeding edge OVMS:

OVMS# can log start tcpserver gvret-b :23

Then put in the wifi IP address of the OVMS into the SavvyCAN server connection, and you should start to see live data from OVMS. This is experimental, and still a work-in-progress, but basic functionality is working.

This is really cool! I found it pretty easy to crash the savvycan app itself and some random gm dbc files I can across didn't seem to decode any of my frames but this looks very powerful. Craig

On 2019-07-18 20:58, Mark Webb-Johnson wrote:

I’m liking this so much I setup a build environment for SavvyCAN. The QT stuff is enormous and seems to require an account with them, but once you’ve gotten over the QT hurdle, SavvyCAN itself builds relatively cleanly for me on OSX 10.14.5.

My github repo is here:

https://github.com/markwj/SavvyCAN

I’ve made changes there to support the latest CRTD format, as documented here:

https://docs.openvehicles.com/en/latest/crtd/

And also sent a pull request to get these incorporated into the main codebase. The changes are minimal.

I too have seen some crashes. I suspect it is related to high speed / volume of logs, at it seems to occur for me after running against a live car for a while. It doesn’t seem to crash when running under the debugger (which makes things trickier to catch).

Earlier I took a run at a FreeBSD port and I got something close to building pretty quickly. I already build wireshark and it needs a lot of the qt5 modules so they were mostly already available before I started. A little more work just now and I have an (untested) binary. I have zero experience debugging under windows but if it crashes on FreeBSD I will have a better time trying to fix it. Craig