On Friday 27 March 2020 14:39:39 Gene Heskett wrote:

> On Friday 27 March 2020 07:20:33 Gene Heskett wrote:
> > On Friday 27 March 2020 02:53:03 theman whosoldtheworld wrote:
> > > Hi
> > >
> > > They are read only.
> > >
> > > The FEATURES=12 or whatever gives you access to the values, but
> > > you cannot change them, that would be the Holy Grail.
> > >
> > > If the pin can be written to, you can do it from a user M code
> > >
> > > halcmd setp <pinname> value type thing
> > >
> > > Whether it is linked and what type of pin it is is going to
> > > determine if it can be written
> > >
> > > regards
> > >
> > > (by ArcHye ....  with AndyPugh some years ago teach me about thse)
> > >
> > > plus on g code     #<_hal[pinname]>

Apparently has been modified, see snip below from page 812 of the current 
docs, I finally found it with zero help from the index.

> > Great minds, I just thought of adding a module, putting it in the
> > correct place in the addf order & feeding it from hal but using its
> > output in the gcode. That syntax '#<_hal[pinname]>' may be the key
> > to the backwards path I need to actually make it work.
> >
Nope.

> > And a debug statement is all it will take to prove its working.  But
> > that also means the loading of the module will have to be moved out
> > of the postgui.hal to the initial loadrt's and addf's so that the
> > modules output exists at the hal scan time, else the error is that
> > the pin doesn't exist. I can sort that I think as geany's copy/paste
> > is I think, global.  I think I may have already done that as
> > postgui.hal is all 'net' statements:

> > net         showdist1       <= scale-ovrtrvl.out => ovrtrvl-scaler-mux.in1
> > net display-mode    <= units.G21 => ovrtrvl-scaler-mux.sel
> > setp        scale-ovrtrvl.gain 25.400000
> > # here, use a scale and a mux2 to select the scale.in for inches, or
> > the scale.out
> > # for a mm's conversion.

> > So in the gcode:
> > #<_z_depth> = [#<_hole_depth> - #<_hal[ovrtrvl-scaler-mux.out]>]

And on page 812, I find this example:
value = hal.get_value("iocontrol.0.emc-enable-in")
So I'll use that syntax just for S&G.
Then I noted the dblquotes around the hal-pinname, but now it is an unk 
where a unary could be.  Gonna take more figuring I think.

Thanks again.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>


_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to