Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 20:17:45 Kurt Jacobson wrote: > Gene, > I have attached my python script as a file so you won't have to repair > any line ending damage done by pasting it into the email. I am doing > this form a windoze machine though so it may not be much better off :) > > Also I changed

Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 16:16:45 Kurt Jacobson wrote: > #!/usr/bin/env python > import hal, time > import linuxcnc > > stat = linuxcnc.stat() > > h = hal.component("units") > h.newpin("prog_in", hal.HAL_BIT, hal.HAL_OUT) > h.newpin("prog_mm", hal.HAL_BIT, hal.HAL_OUT) > h.newpin("update_rate", hal

Re: [Emc-developers] view and mm/inches switching.

> > > Hi Kurt > your code looks fine. > Gstat is a super secret dev only code > Ok truth is it is used in gladevcp and GUIs for widgets that require > linuxcnc status updates. > It has no documentation - yet - I have some started somewhere... > I recently added more functions to it to help with

Re: [Emc-developers] view and mm/inches switching.

Gene, I have attached my python script as a file so you won't have to repair any line ending damage done by pasting it into the email. I am doing this form a windoze machine though so it may not be much better off :) Also I changed the default poll interval to 100ms as suggested by Chris above. H

Re: [Emc-developers] view and mm/inches switching.

From: Kurt Jacobson Sent: April 17, 2017 8:16 PM To: EMC developers Subject: Re: [Emc-developers] view and mm/inches switching. Chris, I am using the user-space Python comp pasted below to get the G20/21 state out to HAL pins. It looks somewhat similar to what

Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 19:34:02 Chris Morley wrote: > But I didn't get very far: > > pi@raspberrypi:~/linuxcnc/configs/sheldon-lathe $ halrun > halcmd: loadusr metric_status > halcmd: Traceback (most recent call last): > File "/usr/local/bin/metric_status", line 16, in > GSTAT.connect("met

Re: [Emc-developers] view and mm/inches switching.

> > But I didn't get very far: pi@raspberrypi:~/linuxcnc/configs/sheldon-lathe $ halrun halcmd: loadusr metric_status halcmd: Traceback (most recent call last): File "/usr/local/bin/metric_status", line 16, in GSTAT.connect("metric-mode-changed",mode_changed) TypeError: : unknown signal nam

Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 16:16:45 Kurt Jacobson wrote: > Chris, > > I am using the user-space Python comp pasted below to get the G20/21 > state out to HAL pins. It looks somewhat similar to what you came up > with (which makes me feel good as I am just starting to learn python > and play with LCNC

Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 14:50:41 Chris Morley wrote: > I think you are using recent master. > > If so this python program should give you what you want. > > name it metric_status and put it in your $PATH as per: > > http://linuxcnc.org/docs/devel/html/hal/halmodule.html > > Creating Userspace Pyth

Re: [Emc-developers] view and mm/inches switching.

Chris, I am using the user-space Python comp pasted below to get the G20/21 state out to HAL pins. It looks somewhat similar to what you came up with (which makes me feel good as I am just starting to learn python and play with LCNC). I sent it to Gene on Saturday, but I guess he did not like it ;

Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 14:50:41 Chris Morley wrote: > I think you are using recent master. > > If so this python program should give you what you want. > > name it metric_status and put it in your $PATH as per: > > http://linuxcnc.org/docs/devel/html/hal/halmodule.html > > Creating Userspace Pyth

Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 14:50:41 Chris Morley wrote: > I think you are using recent master. > Yes Chris, and thank you. For G20-G21, this looks promising. > If so this python program should give you what you want. > > name it metric_status and put it in your $PATH as per: > > http://linuxcnc.org

Re: [Emc-developers] view and mm/inches switching.

I think you are using recent master. If so this python program should give you what you want. name it metric_status and put it in your $PATH as per: http://linuxcnc.org/docs/devel/html/hal/halmodule.html Creating Userspace Python Components - LinuxCNC.org

Re: [Emc-developers] A tweak to Touchy?

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 after HAL has started might

Re: [Emc-developers] A tweak to Touchy?

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

Re: [Emc-developers] view and mm/inches switching.

On Monday 17 April 2017 05:09:47 Niemand Sonst wrote: > Am 15.04.2017 um 16:03 schrieb Gene Heskett: > > Greetings everybody; > > > > I think I asked about this once before, but do not recall getting an > > answer I could use, so asking again. > > > > My jog wheel code currently has no way to swit

[Emc-developers] A tweak to Touchy?

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 havi

Re: [Emc-developers] view and mm/inches switching.

Am 15.04.2017 um 16:03 schrieb Gene Heskett: > Greetings everybody; > > I think I asked about this once before, but do not recall getting an > answer I could use, so asking again. > > My jog wheel code currently has no way to switch between inches and mm's, > either for the motion stepsize, or for