Ethernet Instrumentation drawbacks? further comments

A

Thread Starter

Achyuthan

Pls refer to my old message (http://www.control.com/1026172590/index_html). This work I was doing on my own interest and so in between when an assigned work came, I put the ideas to sleep for a week. But the numerous comments interests me, maybe many are thinking in my lines.

According to me the various drawbacks are.

1. non deterministic
2. security.
3. probality of collision and need of prioritizing the users.

As the don says, i feel this can be used for applications with such tolerance in response only. As far as I see, even wafer industry equipments have a time tolerance of 1 sec usually.
so is there any need for going for things higher than simple tcp/ip? are they worth it really?

critical applications like medical for instance should have closed loop control still.

Also minimal hardware implementations interests me, say at 10 Base ethernet.

Hope you can comment.

Achyuthan
 
By all means connect your network with 10/100BaseT Ethernet. Use full duplex 10 Mbs switches that are now relatively inexpensive, and you will not get any collisions. Unless you are programming your control system entirely in C or C++, use the Ethernet network supported by the controller supplier. For PC-based control, you should use a commercial software package such as Entivity Studio http://www.entivity.com/studio.htm or ISAgraf from Altersys/ICS http://www.altersys.com/products/isagraf.asp

Don't worry about determinism.

Dick Caro
============================================
Richard H. Caro, CEO
CMC Associates
2 Beth Circle, Acton, MA 01720
Tel: +1.978.635.9449 Mobile: +1.978.764.4728
Fax: +1.978.246.1270
E-mail: [email protected]
Web: http://www.CMC.us
============================================
 
Top