Chris, Regarding passwords, make sure you have the command line syntax correct. Here is an example:
loadusr emcrsh --connectpw=changed enablepw=changedtoo If you can log on with the default passwords and not the passwords from the command line, then there is probably a syntax error. As for overhead, the EMC call overhead should basically be identical to the TkEMC interface, as they share the same NML interface. They would differ by the relative polling rates of course. Further, the socket overhead is certainly less than the overhead of a GUI such as TkEMC. I have run as many as 8 simultaneous connections, each issuing blocks of 10-12 commands at a rate of 10 times per second, with no noticeable degradation on either the EMC or client side. I have meant to put up an example page or short tutorial on the wiki, but have not gotten around to doing it. Regards, Eric Thank you Eric Johnson and Les Newell in your replies of 16 Jan. The default setup for emcrsh works as you explained. This was using Telnet on an Mac OS X client machine to the Ubuntu/emc server machine. It would be useful if the wiki page for emcrsh had a precis of your comments added to it. I could not get emcrsh (emc Version 2.2.8) to respond to nondefault passwords, after considerable fiddling of the loadusr emcrsh line in the hal file. One more question - what sort of overhead does emcrsh place on a running emc process? There is no such thing as free parking. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
