Michael, A quick preface before addressing your individual points. Emcrsh basically just ported the functionality of emcsh to a telnet type interface. IOW, the tk/tcl interface was replaced by a socket interface. So in most cases the reason it does what it does and separates the commands out the way that it does is because that was the way it was done in emcsh.
>> I finally got it working! Thanks Eric. Emcrsh is really quite neat. << Great, that interface had two primary objectives. 1> Make the simplest possible network interface 2> Use a standard protocol independent of the particular version of EMC running. >>A couple of observations though - 1. I checked the source code for emcrsh and it hard codes the relative path "../../nc_files". I think this doesn't make sense since it precludes absolute paths and creates confusion by implementing relative paths and hardcoded directories. I would either leave the path off or allow it to be a parameter to emcrsh. Also the path is different from the path specified in the .hal file. << I don't remember if I added that, or if that was how it was done in emcsh at the time I ported the code. I can add a command line parameter to allow specifying the path to use for the g-code files. >> 2. When a file is finally opened the telnet session gets an ACK but the Axis screen doesn't refresh. The filename on the title bar changes but the code and the image in the path window doesn't update. This certainly doesn't give you the warm fuzzy feeling that the right thing is going to happen when you hit run! << As Les already pointed out, they are separate entities and can at times compete with each other. Another thing you will find is that operator and error messages will get snagged by the first one in and missed by the other application. Usually Axis will get it first because it typically has a faster update rate. That was among the reasons I suggested using TkEMC to get it going. TkEMC and emcrsh use fundamentally the same interface, and in fact share some common code (shcom.cc), so they get along much better. >> 3. Perhaps it is because my print out of the help text split task_plan_init onto two pages but I wouldn't have guessed that I needed to set task_plan_init before opening a file. I think this may have been the reason that my previous attempts at moving nc_files around and trying to open my test didn't work. Since I'm not sure how you can open a file without calling task_plan_init maybe open should call it automatically. << I had completely forgotten about that until I dumped a log file to see the exact commands I send when doing an "open". The reason it is not called automatically is because that is the way it was done in emcsh. Which does not mean that we can't change it. >> 4. Occasionally when emc initializes it doesn't allow connections through port 5007. I'm not sure how to reproduce this but it happens about 1 in 5 times. << I have seen that too, but have not been ablt to isolate the cause. Whether it is in the shutdown code of emcrsh or something about how EMC shuts down in general. Regards, Eric ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
