Re: [Emc-developers] Fwd: Help with Hal programming

2016-01-15 Thread TJoseph Powderly
and to use hal without linuxcnc... assuming you have a RIP ( run-in-place build of linuxcnc ) somewhere open a terminal, cd pathtoyourRIP . scripts/linuxcnc-environment scripts/halrun -I -f /apthtoyourcustomhalfile/yourcustomhalfile it is very important to have the '.' in the 2nd line my hal

Re: [Emc-developers] Fwd: Help with Hal programming

2016-01-15 Thread TJoseph Powderly
i think if i am 'in' the directory that contains the scripts folder ( done by 'cd pathtoyourRIP' ) then i can identify the script with just 'scripts/blah' not true? isnt '.'(meaning 'from here') the default for execution path? tomp On 01/15/2016 03:23 AM, John Thornton wrote: > it's > >

Re: [Emc-developers] Fwd: Help with Hal programming

2016-01-15 Thread TJoseph Powderly
John its likely good practice to use ./ , not to assume (old joke) so you are right heres example of the oscillator reading files for data gui and mcodes using bash and python https://videobin.org/+86p/azg.html On 01/15/2016 03:23 AM, John Thornton wrote: > it's > > . ./scripts/rip-environment

Re: [Emc-developers] Fwd: Help with Hal programming

2016-01-15 Thread John Thornton
it's . ./scripts/rip-environment On 1/15/2016 5:04 AM, TJoseph Powderly wrote: > and to use hal without linuxcnc... > > assuming you have a RIP ( run-in-place build of linuxcnc ) somewhere > > open a terminal, > > cd pathtoyourRIP > . scripts/linuxcnc-environment > scripts/halrun -I -f

Re: [Emc-developers] Fwd: Help with Hal programming

2016-01-15 Thread andy pugh
On 15 January 2016 at 10:49, TJoseph Powderly wrote: > I have made oscillators with hal I have only just noticed that this is what he was doing. http://linuxcnc.org/docs/2.7/html/man/man9/siggen.9.html -- atp If you can't fix it, you don't own it.

[Emc-developers] Fwd: Help with Hal programming

2016-01-13 Thread Anupama
> > >> >> >> Dear all, >> >> I am working towards developing a script for rectangular pulse generator ( >> variable data cycle)which is a user defined real time component.I am having >> some conceptual doubts about the work flow in the Hal environment. >> 1) I have defined the logic inside