I have a proof of concept working with right now with emcrsh running on a simulated emc inside a virtual machine, but I'm not that happy with the performance of sending thousands of telnet messages back and forth across the network. The latency of checking if the previous command has finished adds a lot of time to the entire job.
Right now I have an SMT pick and place machine controlled by a windows machine right now with a dedicated microcontroller on the X Y and Z axis, with a serial cable coming back from each axis to 3 serial ports on the windows machine. I'm investigating the possibility of replacing the microcontrollers with a dedicated EMC machine to handle all of the motion control but leaving the windows software intact with only slight modifications to have it talk to EMC instead of the individual microcontrollers. My last test using emcrsh had the job take almost twice as long as the current setup probably because of the TCPIP latency of checking if the previous MDI commands had finished using emcrsh (I modified emcrsh to use TCP_NODELAY which helped, but it's still not that fast). I'm hoping a serial link between the windows box and the EMC box will cut the latency down to almost zero. I never though of using NML from a windows machine to talk directly to EMC. But looking at it now, I think I will have the same latency problems since the messages still have to travel between the machines using TCPIP. Does that sound like I understand how NML would work correctly? Thanks! Alex Joni wrote: > You can also do that using emcrsh > it's a telnet like interface > and you can also connect using NML directly to emc2 from a windows machine > (granted it involves writing and compiling some software ;) > > Regards, > Alex > > > -------------------------------------------------- > From: "Flying Electron" <[email protected]> > Sent: Thursday, December 31, 2009 2:22 AM > To: "Enhanced Machine Controller (EMC)" <[email protected]> > Subject: Re: [Emc-users] Building and using emcsh > > >> Thanks! >> >> That totally worked on my 2.4.0 pre system. Tested it by getting estop >> to turn on and off from an interactive tclsh. I'm planning on piping >> the input and output of the tclsh through a serial port connected to a >> windows machine so the windows machine can issue MDI commands to the >> linux EMC box. >> >> >> >> Jeff Epler wrote: >> >>> emcsh is no longer built. The emc-specific extensions to tcl are now in >>> the loadable library emc.so. >>> >>> Instead, use regular tclsh or wish, and near the top >>> # Load the emc.tcl file, which defines variables for various useful >>> paths >>> source [file join [file dirname [info script]] emc.tcl] >>> eval emc_init $argv >>> (the above snipped from tcl/tkemc.tcl) >>> >>> The way this 'source' line finds the location of emc.tcl is appropriate >>> for run-in-place systems where the script is in bin/ or scripts/; or for >>> run-installed systems where the script is in $prefix/bin/. If your >>> setup is different, then you may need to do something else. >>> >>> Jeff >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Emc-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/emc-users >>> >>> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Emc-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/emc-users >> > > > > >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 9.0.722 / Virus Database: 270.14.123/2594 - Release Date: >> 12/30/09 09:27:00 >> >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
