Jon wrote- > Given all the required overhead to read and write multiple > packets, it is already pretty close to chewing up a whole > millisecond, and there's no way it could handle even 5 KHz > servo update rate. So, I really don't think CAN is a good > candidate.
I agree. The thread started because of concern about the parport going away on newer machines, and how to replace it. I have not seen any computers with a CAN interface built in, which would defeat the whole purpose. We could consider USB, but that has problems as well and met with resistance upthread. Ethernet is relatively easy, affordable and available, and as Jon mentioned before is isolated. With regard to trying to daisy-chain ethernet, I would not advise it. Ethernet is highly standardized, and doing anything to break that would lead to worlds of problems. Since we are talking about a machine controller here and not a remote server the 100 meter distance limitation will not be a problem. Javid ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
