ASi is more important than DeviceNet.
We have our reasons :)
> And the Intel 82527 is the oldest CAN chip on the market,
> even not anymorre available at Intel.
That's not a problem in this case.
> Are you going to use one of the established Linux CAN drivers for it?
>
Possibly. There is a CAN driver now for J1939 that's adequate.
>
> Regards
> Heinz-J�rgen oertel
>
--
Les Cargill
Reply by ●February 17, 20132013-02-17
On Thu, 07 Feb 2013 21:15:26 -0600, Les Cargill
<lcargill99@comcast.com> wrote:
>Who's good? Target is Linux 2.6.x with plenty of RS485 UARTS and Intel
>82527 CAN controllers.
The Intel 82527 is quite usable for simple peer-to-peer CAN bus
applications as well as CanOpen/DeviceNet slaves.
Since you are referring to Linux 2.6, I guess you are planning to use
CanOpen master / DeviceNet scanner, for that, SJA1000 from Philips in
Pelican mode would be a much more appropriate alternative.
While in the old days, ordinary RS485 tri-state drivers were used for
CAN bus communication, but what does RS485 and UART have to do in this
context ?
Reply by ●February 17, 20132013-02-17
Les Cargill wrote:
> Who's good? Target is Linux 2.6.x with plenty of RS485 UARTS and Intel
> 82527 CAN controllers.
>
http://www.can-wiki.info/doku.php?id=can_higher_layer_protocols:devicenet
Just for my interest.
Who is implementing DeviceNet these days, in 2013?
And the Intel 82527 is the oldest CAN chip on the market,
even not anymorre available at Intel.
Are you going to use one of the established Linux CAN drivers for it?
Regards
Heinz-J�rgen oertel
Reply by Les Cargill●February 7, 20132013-02-07
Who's good? Target is Linux 2.6.x with plenty of RS485 UARTS and Intel
82527 CAN controllers.
--
Les Cargill