Re: Faster LIN or simpler CAN or ...? PIC16 or Cypress FX2LP or ...?
- From: R Adsett <radsett@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 18 Nov 2005 13:54:27 -0500
In article <dlkm3j$37m$1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Bill@xxxxxxxxxxxxxxx says...
> a) CAN involves me in checking each message was received once and only once.
Just design your higher level protocol so it doesn't care if the same
message is received multiple time. IE send motor speed absolutely not a
speed increment. Set a relay state rather than a toggle etc. Then you
can just forget anout the fact that a message can show up multiple times.
There are times where you have to care (mostly when abusing CAN to
send large amounts of data) but most control messages can be set up so
that it doesn't matter.
> b) We could use LIN but it seems jolly slow. Would mean a nice simple
> processor in each node with a little programming and offering some
> flexibility.
It's been a while since I looked but doesn't LIN have the same
possibility as CAN of receiving the same message multiple times?
Robert
.
- References:
- Faster LIN or simpler CAN or ...? PIC16 or Cypress FX2LP or ...?
- From: Bill Davy
- Faster LIN or simpler CAN or ...? PIC16 or Cypress FX2LP or ...?
- Prev by Date: Re: Ok, I have to join the windows world ...
- Next by Date: Re: starting embedded linux development
- Previous by thread: Re: Faster LIN or simpler CAN or ...? PIC16 or Cypress FX2LP or ...?
- Next by thread: Re: Faster LIN or simpler CAN or ...? PIC16 or Cypress FX2LP or ...?
- Index(es):
Relevant Pages
|
|