From: Tom Evans <tom_usenet@optusnet.com.au>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
henrique ricardo figueira <henrislip@gmail.com>,
linux-can@vger.kernel.org
Subject: Re: Questions about using multiple sockets
Date: Mon, 7 Sep 2020 23:07:00 +1000 [thread overview]
Message-ID: <18093198-d04c-e07e-9a92-306f9d0afbb7@optusnet.com.au> (raw)
In-Reply-To: <20200907123356.GA15060@x1.vandijck-laurijssen.be>
On 7/9/20 10:33 pm, Kurt Van Dijck wrote:
>>
>> The 'problem' seems to be already introduced by that specific ECU ;-)
>
> In my experience, it's hard to use 29bit CAN id's mixed with J1939.
> But the 11bit CAN id range is free to use without any conflict with
> j1939.
> I've seen some uses of this 11bit id's.
Just as long as all other devices on the bus are perfect and fully tested, and don't do what was in
one of the links I sent previously:
https://electronics.stackexchange.com/questions/467932/is-it-possible-to-use-j1939-and-canopen-on-the-same-bus
Certain CAN nodes don't distinguish between 11 or 29 bit
internally.
There are a lot of CAN devices out there that work well enough in the limited environment they've
been tested in. But add anything else to the bus and change the traffic or addresses in use and you
might find they can't handle that. They might be demonstrably buggy, but it will still be your
fault. Especially if they throw a DTC and don't work until the vehicle gets back to the dealer to
clear it. BeenThereDoneThat.
Tom
prev parent reply other threads:[~2020-09-07 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAD1tVCN7-T=FHNQEz3Bp-0Kt3H6M1RokyUuw=e9sTLdXNWB=DQ@mail.gmail.com>
2020-09-03 5:47 ` Questions about using multiple sockets Oleksij Rempel
2020-09-05 6:47 ` Tom Evans
2020-09-07 6:55 ` Oliver Hartkopp
2020-09-07 12:33 ` Kurt Van Dijck
2020-09-07 13:07 ` Tom Evans [this message]
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=18093198-d04c-e07e-9a92-306f9d0afbb7@optusnet.com.au \
--to=tom_usenet@optusnet.com.au \
--cc=henrislip@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).