On Sat, 2010-03-13 at 09:59 +0200, Alex Joni wrote:
> well, AXIS by itself should be able to run remotely. The only thing is that 
> it usually exports some HAL pins for convenience use.
> I remember adding an option to prevent that.
> from src/emc/usr_intf/axis/scripts/axis.py:
>     if os.environ.has_key("AXIS_NO_HAL"):
> 
> So you need to do this before running AXIS on the remote machine:
>     export AXIS_NO_HAL=1
> 
> Regards,
> Alex

I'm taking an uneducated guess here, HAL pins are written and read into
a shared memory area? Could a function be written to allow access to the
shared memory through Ethernet? Or expand NML to handle HALpins?

The AXIS pins are axisui.jog.N ? It seems unless someone explicitly
connects these in a .hal file these pins are not used? Currently, my jog
setup has two axis jog select sources, one for the MPG (pyvcp), the
other is the AXIS active axis buttons. The axisui.jog.N pins allow AXIS
to replace the MPG selector, so I could have one selector instead of
two? If so, this would not be an advantage if I have a physical selector
on a pendant?

-- 
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/index.html
California, USA


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to