Diagnostics CAN development for ---- FreeEMS

[danny_ecu]

Hello,

I have joined the forum today & i am intrested to build some diagnostics services for freeEMS. I have worked on FORD project for Body Control Module it is also an electronic control unit for an CAR.

I am having some idea about vector diagnostics kernel CANDESCBASIC which i was using in an battery charger project. But ford have there own kernel for diagnostics known as VOODO. But we can build something similar to that which can be used for OBD.

But first thing for me is to unerstand FreeEMS its present s/w & tools needed for its development. Please sugest how to proceed for this ?

Once system level is clear we can procede ahead to creat the high-level design related to kernel for diagnostics of freeEMS. Once design is finalised we can built the kernel.

I am having some usefull document for HC12 which we were also using for ford vehical. I am putting it in sharing

Danny

[ToxicGumbo]

Thanks for posting that useful PowerPoint file.

Are you still interested in developing diagnostics support? FreeEMS has advanced quite a bit since your post, so this is a great time to jump in.

Edit: You might want to take a look at http://forum.diyefi.org/viewtopic.php?f=42&t=1896&hilit=can

-Jeff

[danny_ecu]

Fine i will be... But where freeEms is standing at present.
What controller & compilers you are using ?
What functionality have been implemented what is left ?
What are the future plan or radmap for freeEMS?

First i will go through these links --- long before i read it. :--
http://freeems.org/
viewtopic.php?f=54&t=1241
http://docs.freeems.org/
http://wiki.freeems.org/doku.php

//Dany

[Fred]

Read this:

viewtopic.php?f=41&t=1699

And don't bother with the old wiki.

What's implemented, in terms of features, does not matter, except to those short sighted ones without any real vision.

Fred.

[danny_ecu]

Ok fine .. i will have to go through .. your firmware structure... how your scheduler is implemented... ...

For diagnostics firmware side we need following :---
1> Diagnostics kernel to serve the request from client.
2> we can insert diagnostic related call in the scheduler for dtc checking.
3> also most important will we Transport layer protocol implementation for diagnostics .
4> I have worked to Body Control Module .. so for Engine control .. We need some document for reference PID & DTC which are commonly supported on engine control units.


First i have to understand the current implementation. Then i will proceed on above ones.

//Danny

[Fred]

This DTC, and if not, which DTC?

[danny_ecu]

yes this one..
https://en.wikipedia.org/wiki/Diagnosti ... _standards

Diagnostic Trouble Code, in the automotive industry, codes that are prescribed by SAE standards to help track problems in a vehicle detected by its on-board computer