Re: USB or Ethernet for controller interface?
- From: "Arlet" <usenet+5@xxxxxxxxxx>
- Date: 12 Apr 2007 13:03:53 -0700
On Apr 12, 5:47 pm, "Gary" <micro-rdgr...@xxxxxxxxxxxxx> wrote:
Thank you for the feedback. Here are more details:
100Mb/s Ethernet or USB are needed for thru-put. CAN & RS232/485 have
been ruled out. Ethernet or USB data rate is needed because the
design will be transferring large amounts of buffered data. The
buffer will be large enough to handle Ethernet or USB latency and the
PC's non-deterministic nature. The PC side will be used as the human-
interface and data storage. Not for time or safety critical control.
The design will be doing basic control stuff - reading sensors &
inputs and controlling actuators. The isolation Rene mentioned is
very good feedback.
Given the choice between Ethernet and USB, I'd recommend Ethernet any
day.
Advantages of Ethernet over USB:
- electrically isolated
- optical PHY possible
- can use much longer cables
- may use already available infrastructure (data can be routed across
the internet for example)
- no special drivers required
- multiple hosts can access simultaneously
- more robust, USB hosts may give up after just 3 failures
- easier to debug and monitor traffic
- cable can be unplugged/plugged without breaking the connection
- locking plugs
.
- References:
- USB or Ethernet for controller interface?
- From: Gary
- Re: USB or Ethernet for controller interface?
- From: Paul E. Bennett
- Re: USB or Ethernet for controller interface?
- From: Gary
- USB or Ethernet for controller interface?
- Prev by Date: Re: circuit board production
- Next by Date: Re: USB or Ethernet for controller interface?
- Previous by thread: Re: USB or Ethernet for controller interface?
- Next by thread: Re: USB or Ethernet for controller interface?
- Index(es):
Relevant Pages
|
