You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Registering will also remove advertisements. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
I'm an engineer at DrewTech and work on the Mongoose cable. It depends completely upon the software you're using.
Most ECUs artifically limit the Mode 1-9 OBD responses to max 30/sec. If you're using DMRs or rapid packet modes, you can expect 150-200 frames per second on most GM and Ford controllers. Since Mongoose supports full bandwidth it will give the highest rates supported by your software. I'm programming on a plug-in library right now that'll allow highspeed datalogging in any/all software.
I've got an ELM5 and could run a comparison benchmark if necessary. The serial pipe is going to saturate pretty quickly.
Mongoose seems to be my reader of choice from the research I am doing. I am looking for something that will return 1-2 bits of data as often as possible. Probably something like 10+ samples a second. So mongoose seems like a good choice. FYI, I will be using the Asian/Euro module for mongoose.
Do you have any program samples/API Docs or naything of that nature to aid me for when I start developing my app? The app will most likly be written in C#, but any/all example will be greatly appreciated.
The formal SAE J2534 API specification is available straight from the SAE for around $50. I've written an overview (http://www.drewtech.com/support/j2534/) that may be helpful in the meantime. Sample code is available upon request for both C and C#.