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).

Regards, Mark.

On 19 Jul 2019, at 1:10 AM, Craig Leres <leres@xse.com> wrote:

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