From: John Whitmore <arigead@gmail.com>
To: Rama kiran kumar Indrakanti <ramakirankumar.i@hcl.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: CAN Bus Cable
Date: Mon, 13 Jul 2015 20:28:03 +0100 [thread overview]
Message-ID: <20150713192802.GF25291@bamboo.electronicsoup> (raw)
In-Reply-To: <FF0E019DD74E2349AE9109F955A784D00EFC8194@chn-hclt-mbs06.HCLT.CORP.HCL.IN>
On Mon, Jul 13, 2015 at 11:15:08AM +0000, Rama kiran kumar Indrakanti wrote:
> From: linux-can-owner@vger.kernel.org [mailto:linux-can-owner@vger.kernel.org] On Behalf Of John Whitmore
> Sent: Monday, July 13, 2015 4:38 PM
> To: linux-can@vger.kernel.org
> Subject: CAN Bus Cable
>
> >OK it's not Linux-can specific, although I am using RPi's on the BUS but I can't think of anywhere better to ask this question. Possibly a lack of imagination on my part.
>
> >I'm working on a project on a tractor and am looking for cable to use. I'd like to use a four core cable with two thin wires for the serial CAN Data and then two thicker wires for 12V Power. That is a hard thing to >communicate to Google so if somebody had any ideas I'd be really grateful
>
> Is this the J1939 connector you are talking about.
No it's the actual copper cable I'm looking for. I'm creating my own CAN Bus
network. Maybe if I searched for a cable using the SAE or ISO standard number
that would be the way to go.
>
> John
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> ::DISCLAIMER::
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
> (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior written consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses and other defects.
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
next prev parent reply other threads:[~2015-07-13 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 11:08 CAN Bus Cable John Whitmore
2015-07-13 11:15 ` Rama kiran kumar Indrakanti
2015-07-13 19:28 ` John Whitmore [this message]
2015-07-14 17:16 ` Armin Burchardt
2015-07-13 21:12 ` Max S.
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=20150713192802.GF25291@bamboo.electronicsoup \
--to=arigead@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=ramakirankumar.i@hcl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.