On Thu, Jul 05, 2018 at 07:49:29PM +0100, andy pugh wrote:
>
> I have been using it that way for over a year with no problems, can I
> push the mod?
This looks like a bugfix to me, so if you're waiting for my input, I
say push away.
Chris
On 17 April 2017 at 15:48, andy pugh wrote:
> was finally prompted to try to get
> Touchy to report the current override value in the case where it was
> set from another source.
>
> I added a couple of lines around line 798 in touchy.py
>
> + self.fo_val = s.feedrate * 100
> +
On 17 April 2017 at 16:04, sam sokolik wrote:
> I think I got around it by applying the reset pulse to the encoder
> counter in hal as linuxcnc booted. (I think peter had a better solution
> but I don't remember what it was)
I think turning off the count-enable until
On the Matsuura - I found this out also (counts not resetting between
launches of linuxcnc). (the encoder counters on the 7i73)
I think I got around it by applying the reset pulse to the encoder
counter in hal as linuxcnc booted. (I think peter had a better solution
but I don't remember what
My lathe is set up with the Touchy interface. However I am not using
the touchy jog-counts input as I have 4 separate wheels for jogging X
and Z and for spindle and feed override. (I don't currently have a way
to alter maxv or to move the restart point, but I haven't felt the
need yet)
I was