Hi,
I have found a lot of info
like this in the tech doc I have
"
Using the Jaguar Land Rover approved diagnostic
equipment, check datalogger signal – Vehicle Speed (0xDD09)
Ensure that vehicle speed is transmitted and updated
correctly. Clear the DTCs and retest. If fault persist using
the Jaguar Land Rover Approved Diagnostic Equipment,
reconfigure the door module with the latest level software.
Clear the DTCs and retest
"
What do you think I can do
with the info "0xDD09" ? a PID ?
Presumably. Try it. As it's a 16 bit PID, you'll probably need poll
type 22, so that would be:
obdii can1 request broadcast 22dd09
The communications networks available on the
vehicle are shown below:
- High Speed (HS) CAN chassis systems bus
- HS CAN body systems bus
- HS CAN Human Machine Interface (HMI) systems bus
- HS CAN power mode zero systems bus
- Flexray
- Local Interconnect Network (LIN)
- Private bus
That's a log of networks. You probably won't be able to access all
of them at the ODB port.
- the copen scan does not do
anything
If it doesn't _do_ anything, you didn't do it right. If it doesn't
_find_ anything, you don't have CANopen nodes, so can concentrate on
OBD/UDS.
- the "obdii
can1 request broadcast 0100", (and 0120,
0140, 0160, 0180...) returned a 32 bits that I can decode to
identify which PID is supported, but only one ECU (7df)
answered to the broadcast. I guess there is many other, but
they don't respond to the broadcast.
7DF isn't an ECU, it's the broadcast address. You currently need to
enable the CAN logger to see the origin address. It's normal only
one device responds to broadcasts. You need to find the other
devices by scanning for them.
I don't understand why the "re
obdii scan start 1 7df 0 20" does not give
me an anser for the identifyed PID of the previous
"broadcast" command .
Because you need to specify the RX ID range you're expecting, the
PID scanner doesn't set that automatically. In this case, you'd do:
re
obdii scan start 1 7df 0 20 -r7e8-7ef
…or…
re
obdii scan start 1 7df 0 20 -r600-7ff
…to check for responses outside the standard.
In the broadcast command, when we send "0100",
the first byte seems to be a "mode", and the second the PID,
is it correct ? (as described in the vehicle.h).
I still don't see how I can have a full list of
ECU ID, and a full list of PID for each ECU. Maybe that is
why retro engineering is complex,
That is correct, and you get a full list by scanning.
I don't also understand the impact of selecting
a vehicle in the web session. Since my Jaguar is not
supported yet, I select the OBDII car , but if I select the
nissan leaf, I can see more data, which does not make sense,
unless we ned to "wake up" some ECU in order to pull some
info. Is the OVMS device masking some data in the bus? how
can I see everything on the bus ?
Selecting a vehicle activates the special CAN & OBD handling
that is implemented for that vehicle already. Since your car isn't
supported, you should select the empty vehicle (code NONE). The OBD
vehicle polls some standard PIDs, which can interfere with RE scans.
You can see everything on the bus with the CAN logging &
monitoring & streaming commands. See the documentation links I
gave you in my first post.
Regards,
Michael
Thanks for your help.
I will definitively take a look at your new
page.
Didier
Didier,
Am 31.12.20 um 10:47 schrieb Michael Balzer:
> Most OBD2 devices won't respond to
broadcasts though. To identify
> them, you need to send a test request to
all CAN IDs in your assumed
> ID range. The scan tools for this are
below "re obdii scan":
I've just added a first UI for that scanner:
https://docs.openvehicles.com/en/latest/plugin/repidscan/README.html
Feedback is welcome.
Regards,
Michael
--
Michael Balzer * Helkenberger Weg 9 *
D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989
26
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev
--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26