I think I'm confusing you guys. We have a machine running LinuxCNC realese 2.5.1 and using the "touchy" GUI. There have been added features added to "touchy" that we really want to have. However I can't just throw something on a machine that I have not tested. I have LinuxCNC setup as simulator that I use before I try it on a machine. That way i can limit my problems before I shut a machine that is working down. The problem I was questing was in the linuxcnc simulator version. I prefer gscreen over touchy for a GUI and it works in simulator and realtime version. On this machine I have a structure that is listed this way home/linuxcnc, home/linuxcnc-dev, home/linuxcnc-master. On my simulator I have home/linuxcnc-simulator and touchy won't run there. The "touchy.ini" file that is in the sim directory asks for the /linuxcnc/ncfiles and if you correct that it asks for linuxcnc/rtlib so it is wrong in my opinion. It should be removed from there or fixed.
Thanks, Shannon Watson swat...@mpm1.com Phone: (316) 945-1227 MPM Inc. 2100 S West Street Wichita, KS 67213 > Date: Wed, 10 Jul 2013 09:05:16 -0600 > From: Sebastian Kuzminsky <s...@highlab.com> > Subject: Re: [Emc-users] Touchy update? (Chris Radek) > To: "Enhanced Machine Controller (EMC)" > <emc-users@lists.sourceforge.net> > Message-ID: <51dd782c.1070...@highlab.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 7/10/13 07:56 , Shannon Watson wrote: >> Operating this way ties me down to only one directory. I want to have a >> production directory that is current release and stable version. That >> directory is linuxcnc. I want updates and currently untested (by me) items >> to be run in its own directory so that there is no interference with the >> machine that makes money for our company. Can this be done? > > I'm not sure if you're talking about different directories for different > versions of LinuxCNC or different directories for different kinds of > gcode files. I think you mean different kinds of gcode files, because > that's what the error message you posted complained about. > > If so, then the good news is that there is no such limit: you can have > gcode files in many directories. I often use one directory per project. > You can have one directory for completed, proven gcode files and > another directory for experimental gcode files under development if > that's what you like. > > The error you posted is informing you that the path you told your gui to > look for gcode files in does not exist. You should create that > directory (or point your gui at some other directory), then create a > "stable" and "experimental" subdirectories under that directory, and you > should be good to go. (If i understand what you're trying to do.) > > > -- > Sebastian Kuzminsky > > > > ------------------------------ ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
