J
James Ingraham
>ping to my local router:
>64 bytes from sx (192.168.1.1):
>icmp_seq=1 ttl=64 time=0.424 ms
Okay. 150 I/O isn't much more data than a ping. And ping uses TCP, which means that ping did a connect and a close within 424µs. With UDP and all 150 points on one device, I'd say that you just proved Ethernet is almost twice as fast as the application needs.
>If such high sampling rates are necessary, stick to I/O cards directly plugged into PCI.
I essentially agree with this point. Grabbing stuff out of dual-port RAM on a PCI card is going to be about as fast as you can get. If I needed to guarantee I'd get the application done, I'd do it this way. However, if placing the I/O on Ethernet gives some real advantages, and I've got some time to play around with possible solutions, I'm pretty sure I could make this application work.
-James Ingraham
Sage Automation, Inc.
>64 bytes from sx (192.168.1.1):
>icmp_seq=1 ttl=64 time=0.424 ms
Okay. 150 I/O isn't much more data than a ping. And ping uses TCP, which means that ping did a connect and a close within 424µs. With UDP and all 150 points on one device, I'd say that you just proved Ethernet is almost twice as fast as the application needs.
>If such high sampling rates are necessary, stick to I/O cards directly plugged into PCI.
I essentially agree with this point. Grabbing stuff out of dual-port RAM on a PCI card is going to be about as fast as you can get. If I needed to guarantee I'd get the application done, I'd do it this way. However, if placing the I/O on Ethernet gives some real advantages, and I've got some time to play around with possible solutions, I'm pretty sure I could make this application work.
-James Ingraham
Sage Automation, Inc.