From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Patrick Menschel <menschel.p@posteo.de>,
Marvin Ludersdorfer <marvin.ludersdorfer@dintec.solutions>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Andre Naujoks <nautsch2@gmail.com>
Subject: Re: Problem receiving > 8 byte UDS response when using istpsend
Date: Tue, 22 Nov 2022 13:52:38 +0100 [thread overview]
Message-ID: <96a4de81-882b-cd88-ae7a-ca3b7c3b432f@hartkopp.net> (raw)
In-Reply-To: <40200c08-552e-e6b3-c5c7-f5ee8a4b839c@posteo.de>
On 21.11.22 17:45, Patrick Menschel wrote:
> Am 21.11.22 um 17:11 schrieb Andre Naujoks:
>> Am 21.11.22 um 13:08 schrieb Marvin Ludersdorfer:
>>>
>>> In another terminal, I run echo 22 F1 95 | isotpsend -s 00000680 -d
>>> 00000780 can0 -p 0x00
>
> Typical error,
>
> exchange -s and -d
>
> isotprecv works the other way around.
>
:-D Yes. Trapped into this myself some times.
Btw. @Marvin are you really sure with the given values for the CAN IDs?
The help text says:
Usage: isotpsend [options] <CAN interface>
Options:
-s <can_id> (source can_id. Use 8 digits for extended IDs)
-d <can_id> (destination can_id. Use 8 digits for extended IDs)
So your IDs 00000680 and 00000780 are 29 bit CAN identifiers!
Is this intentionally?
Some people mix up the nominal values with the 11/29-bit IDs and think
every CAN ID below 0x800 is a 11 bit CAN ID.
Regards,
Oliver
next prev parent reply other threads:[~2022-11-22 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FR2P281MB165556E4F729AC3CDB50F6F69F0A9@FR2P281MB1655.DEUP281.PROD.OUTLOOK.COM>
2022-11-21 12:08 ` AW: Problem receiving > 8 byte UDS response when using istpsend Marvin Ludersdorfer
2022-11-21 16:11 ` Andre Naujoks
2022-11-21 16:45 ` Patrick Menschel
2022-11-22 12:52 ` Oliver Hartkopp [this message]
2022-11-22 16:24 ` Marvin Ludersdorfer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96a4de81-882b-cd88-ae7a-ca3b7c3b432f@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=marvin.ludersdorfer@dintec.solutions \
--cc=menschel.p@posteo.de \
--cc=nautsch2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).