Non J1939 Diagnostics

Discuss issues and ideas you have to configuring displays with PowerVision
mthill
Posts: 2
Joined: Wed Jan 26, 2011 10:44 am

Non J1939 Diagnostics

Post by mthill » Thu Feb 03, 2011 4:38 pm

Has any attempt been made to implement non-J1939 diagnostics protocols on the PV750. In theory it seems possible and I'd like to try it but not if it's already been proven impossible due to HW or SW limitations. The engine controller I'm connecting to supports J1939 for instrumentation (which works beautifully with the 750) but does not support the DM1, DM2, etc diagnostic messages. It does support OBD-II diagnostics (over CAN).

For this use it'd be nice to implement OBD-II over CAN diagnostics (ISO15765) or KWP2000 (ISO14230). The structure of these is more complicated than a simple request to the engine ECU to send the fault codes as in J1939. A diagnostic session must be started and there are some specific message timings required. From my research, these protocols can co-exist on the same physical network as J1939/NMEA2000 without traffic conflicts.

Any thoughts?
jpurdum
Enovation Controls Development
Enovation Controls Development
Posts: 153
Joined: Mon Jun 21, 2010 11:19 am

Re: Non J1939 Diagnostics

Post by jpurdum » Sun Feb 06, 2011 5:51 am

Yes, this is possible. Technically, what would have to happen is that an application would have to be built in C/C++ to handle the protocol desired. We would either need to build this at Murphy, or you could work with us to provide you an SDK for you to implement yourself - currently that would require you to also purchase a QNX development seat.

Please contact your Murphy representative regarding either option.

john p.