On Mon, 2007-12-10 at 09:23 -0600, Jeff Epler wrote: > I don't know of anyone running AXIS remotely; I've never done it. > > AXIS assumes that it can create HAL pins and access (read) the var file > from the filesystem. This may be causing problems. > > Look on the terminal for any errors AXIS prints. > > Jeff
Do you mean, start AXIS from a terminal and watch the output? "axis -ini emc.ini" fails to bring up AXIS, but I am assuming this is not the proper way to do it, since the configuration selector successfully starts it. When starting the server AXIS with the configuration selector, I don't get any error messages. AXIS comes up normally, the e-stop button automatically toggles and waits. If I try to unset the e-stop button, the button is unresponsive. The file and screen features seem to work. On the client, the normal screen comes up, but the e-stop button doesn't toggle. I can select the e-stop button, but it immediately reverts to the set state. The /home/kwallace/emc2 directory including .../configs and .../nc_files are mounted from the file server on both PC's so they both see the same config files. Because the server and client .ini and .nml files need to be different, I have a different server.ini/.nml file for each client and a different client.ini/.nml file for each client. The same .var file is used in all .ini's. -- Kirk Wallace (California, USA http://www.wallacecompany.com/machine_shop/ Hardinge HNC lathe, Bridgeport mill conversion, doing XY now, Zubal lathe conversion pending) ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
