On Sunday 29 March 2020 09:40:38 andy pugh wrote:
> On Sun, 29 Mar 2020 at 08:15, Gene Heskett
wrote:
> > > And there is no need to add a tiny move to M66.
> >
> > Somebody should fix the docs, it say it needs a move to activate it.
>
> No it doesn't. That is for M67 (and the requirement can be
On Sun, 29 Mar 2020 at 08:15, Gene Heskett wrote:
> > And there is no need to add a tiny move to M66.
>
> Somebody should fix the docs, it say it needs a move to activate it.
No it doesn't. That is for M67 (and the requirement can be avoided by using M68)
On Saturday 28 March 2020 23:03:59 andy pugh wrote:
> On Sun, 29 Mar 2020 at 03:08, Gene Heskett
wrote:
> > Is the analog-in-00 and and analog-out-00 two separate circuits
> > independent of each other?
>
> Yes.
>
That will help clarify my thinking, a bunch. So I can use 00 for
independent
On Sun, 29 Mar 2020 at 03:08, Gene Heskett wrote:
> Is the analog-in-00 and and analog-out-00 two separate circuits independent of
> each other?
Yes.
And there is no need to add a tiny move to M66.
M67 takes effect on the next move, but that's for output, not input.
M66 ENN transfers the
On Saturday 28 March 2020 15:51:02 Gene Heskett wrote:
> On Saturday 28 March 2020 13:55:28 andy pugh wrote:
> > On Sat, 28 Mar 2020 at 17:50, Gene Heskett wrote:
> > > mornings git pull so it might not be page 812 any more. Is now on
> > > page 814 according to evince:
> > >
> > Section 14.15
On Saturday 28 March 2020 13:55:28 andy pugh wrote:
> On Sat, 28 Mar 2020 at 17:50, Gene Heskett wrote:
> > mornings git pull so it might not be page 812 any more. Is now on
> > page 814 according to evince:
> >
> > 14.15.6.6
>
> Section 14.15 is "14.15 Creating Userspace Python Components"
>
>
On Sat, 28 Mar 2020 at 17:50, Gene Heskett wrote:
> mornings git pull so it might not be page 812 any more. Is now on page
> 814 according to evince:
>
> 14.15.6.6
Section 14.15 is "14.15 Creating Userspace Python Components"
So, this is a Python function for use in custom userspace
On Saturday 28 March 2020 10:01:51 andy pugh wrote:
> On Sat, 28 Mar 2020 at 13:45, Gene Heskett
wrote:
> > > Where did you find that format? Is it in the docs somewhere?
> >
> > page 812, /usr/share/doc/linuxcnc/Documentation.pdf
>
> The 2.7 docs don't even have a page 812, and in 2.9 and 2.8
On Sat, 28 Mar 2020 at 13:45, Gene Heskett wrote:
> > Where did you find that format? Is it in the docs somewhere?
>
> page 812, /usr/share/doc/linuxcnc/Documentation.pdf
The 2.7 docs don't even have a page 812, and in 2.9 and 2.8 that page
is discussing kinematics.
Searching the PDF for the
On Saturday 28 March 2020 07:16:49 andy pugh wrote:
> On Sat, 28 Mar 2020 at 07:45, Gene Heskett
wrote:
> > Now, the actual line from the gcode which should be good
> > #<_Z_dist>=hal.get_value("ovrtrvl-scaler-mux.out")
>
> Where did you find that format? Is it in the docs somewhere?
page 812,
On Sat, 28 Mar 2020 at 07:45, Gene Heskett wrote:
> Now, the actual line from the gcode which should be good
> #<_Z_dist>=hal.get_value("ovrtrvl-scaler-mux.out")
Where did you find that format? Is it in the docs somewhere?
If so, can you say which file and which page?
You seem to be trying to
On Friday 27 March 2020 16:04:21 Gene Heskett wrote:
> 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.
> > > >
> > > >
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
> > >
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
Fine!
Il giorno ven 27 mar 2020 alle ore 12:23 Gene Heskett
ha scritto:
> 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
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
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 value type thing
Whether it is linked and what type of pin it is is going to
Greetings all;
I have some code in my Sheldon's hal file that accepts a value from
gcode, #<_tpmm> or #<_tpi> that twiddles that value shipped across
motion and then shows me via a pyvcp text box, the numerical distance
value of the overshoot from inertia between the initiance of the reverse
18 matches
Mail list logo
