PicoScope 7 Automotive
Available for Windows, Mac, and Linux, the next evolution of our diagnostic scope software is now available.
I don't think that is such a big limitation.FioranoCars wrote: Yes, sadly due to "gaps" between buffers, this is not suitable to listen and follow a "conversation", any data missed would be a failure, and render the analysis void. As a quick and dirty, is my CAN signal valid, it's great.
That may be true, I don't know for sure, never got my hands on that to prove otherwise, but I can't understand why they are slow for this.FioranoCars wrote: The ELM327 is according to "superior" sources too slow for this sort of task and other has limitations, not sure what, but that's the word, and I'll not double check others work, as hardware is relatively cheap anyway.
The Arduino (faster than most Pi's especially in terms of I/O operations) is also thought to be a bit slow if you get into complex stuff, and the recommendation for serious playing is the Intel® Galileo Gen 2 board, which is sort of compatible with the Arduino sketches, but has access to Visual Studio as well, so no doubt much more powerful, though still single core, single thread architecture. I'll probably hold off the Intel board as it's about 10x the cost, and I have a few spare Arduino floating.
I can only say good luck with that.FioranoCars wrote: Also the Application Layer stuff (message structures, contents) and initialisation, although right now I'm planning on listening only, sooner or later it'll crop up as to why the initialistions failed, so understanding the wake up stuff is pretty important too.
Projects using something other than data that you can't get with the standard OBDII protocol I believe are really rare, and very limited in function.FioranoCars wrote: Also anything (docs or sites) dealing with Arduino and OBD, there are quite a few, many with little recent activity, so if you stuble over something, please pop it my way! Ideally not projects to make a dashboard or fuel economy meter, as they are not really too relevant, but heck, I'm happy to filter!
I believe Wireshark type software only makes sense if we are talking of a higher level protocol like TCP/IP, and you could get "metadata" from the overhead of the protocol.FioranoCars wrote: Finally, any links to software for analysis of CAN/Data packets. I use Wireshark for TCPIP stuff, and could just write the data into a format that program can read, which I might do anyway to give the output an opensource universal viewer, but if there is anything (commercial or Free/Opensource) that is dedicated to OBD/CAN packets, then please let me know, this is probably the critical part of the jigsaw ... raw data is one thing, the analysis of THOUSANDS of message per minute is the value! Bear in mind some captures could be 10-60minutes long (LandRover vehicle shutdown is 45mins), road tests for intermittent faults ...
Please keep us informed with your progress, and I'm very curious to see your approach to this.FioranoCars wrote: Will try and prototype something in next 4-5 weeks, let you know how it goes, but I want to let the theory soak in before I go blowing up any ECU's !