Re: [Emc-users] Interp problems?

[Jon Elson]

On 06/25/2017 06:51 PM, andy pugh wrote:

On 25 June 2017 at 15:21, dave  wrote:


I suspect that this is a thermal problem


Whereas I consider the idea that it is a _Computer_ thermal problem almost
inconceivable.


Yes, for a CPU to foul up ONLY the counting of one axis in 
ONE direction seems implausible.  I'm guessing possibly a 
weak encoder that is losing counts when hot.  I'd also check 
the power supply to the encoder as close to the encoder as 
it is available.


I did have a problem with my mill some years ago.  I did a 
couple things wrong on one job and didn't notice the hole 
spacing was off until the parts were used.  One error was I 
didn't spot the holes, I just drilled them with jobber's 
length drills, so all bets on accuracy would be off, 
anyway.  But, the holes were too widely spaced.  Hmmm, many 
errors in the machine would cause the holes to be too CLOSE 
together.  Then, I noticed the spindle speed display was 
fluctuating.  I started to investigate.  On my PPMC system, 
the encoder board powers the encoders through the encoder 
connector.
I saw that the encoders had about 4.0 V where it should have 
been 5.0 +/- 5% or so.  The main DC connector to the PPMC 
motherboard was making a poor contact, and the whole PPMC 
system was running on about 4.1 V!  Amazing that it even 
worked at all, as that was WAY outside the VCC spec for all 
the chips.  Once I wiggled the connector, everything 
returned to normal.


So, the error was due to one encoder losing counts, so the 
machine moved farther than it should have.  It was pretty 
repeatable, so the error did not accumulate.


Jon

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] steppers with encoders in closed loop

[Tom Easterday]

Gene,
Thanks for the response.  The machine has been running great for years on those 
values but in position mode, not in velocity mode.  I wouldn't think that any 
of the step-gen parameters would need to change when changing to velocity 
mode...?

I suspect the PID parameters I am using, DEADBAND?, MAX_OUTPUT? (not sure what 
these should be) or perhaps I have mis-wired, or not wired, an encoder or 
velocity parameter in the Hal config

-Tom

> On Jun 25, 2017, at 9:11 PM, Gene Heskett  wrote:
> 
>> On Sunday 25 June 2017 18:12:14 tom-...@bgp.nu wrote:
>> 
>> I would like to attempt to get my machine with stepper motors running
>> in velocity mode with feedback from the encoders.  Below are the
>> relevant parts of my Hal and Ini files for just the X-Axis.  I figured
>> I would do one axis at a time.  Currently nothing happens when I try
>> to jog the X axis except if I hold it long enough it gives a following
>> error.  If I try to home it, it faults with a following error.  I was
>> trying to look various parameters on Halscope, triggering off of
>> axis.0.f-error but nothing appears for any of the pins I was
>> monitoring.   Are there any obvious errors in the config below to
>> start with?
>> 
>> -Tom
>> 
>>  HAL 
>> loadrt trivkins
>> loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD
>> num_joints=[TRAJ]AXES loadrt hostmot2
>> loadrt hm2_7i43  config="firmware=hm2/7i43/SVST2_4_7I47B.BIT
>> num_encoders=3 num_pwmgens=0 num_stepgens=4" loadrt pid
>> names=pid.x,pid.y,pid.z
>> 
>> addf hm2_7i43.0.read servo-thread
>> addf motion-command-handler servo-thread
>> addf motion-controller servo-thread
>> addf pid.x.do-pid-calcsservo-thread
>> addf pid.y.do-pid-calcsservo-thread
>> addf pid.z.do-pid-calcsservo-thread
>> addf hm2_7i43.0.write servo-thread
>> 
>> 
>> #***
>> #  AXIS X
>> #***
>> # axis enable chain
>> 
>> setppid.x.Pgain[AXIS_0]P
>> setppid.x.Igain[AXIS_0]I
>> setppid.x.Dgain[AXIS_0]D
>> setppid.x.bias[AXIS_0]BIAS
>> setppid.x.FF0[AXIS_0]FF0
>> setppid.x.FF1[AXIS_0]FF1
>> setppid.x.FF2[AXIS_0]FF2
>> setppid.x.deadband[AXIS_0]DEADBAND
>> setppid.x.maxoutput[AXIS_0]MAX_OUTPUT
>> 
>> net x-index-enable <=> pid.x.index-enable
>> net x-enable => pid.x.enable
>> net x-ouput => pid.x.output
>> net x-pos-cmd => pid.x.command
>> net x-vel-fb => pid.x.feedback-deriv
>> net x-pos-fb => pid.x.feedback
>> 
>> # Step Gen signals/setup
>> setp hm2_7i43.0.stepgen.00.dirsetup[AXIS_0]DIRSETUP
>> setp hm2_7i43.0.stepgen.00.dirhold [AXIS_0]DIRHOLD
>> setp hm2_7i43.0.stepgen.00.steplen [AXIS_0]STEPLEN
>> setp hm2_7i43.0.stepgen.00.stepspace   [AXIS_0]STEPSPACE
>> setp hm2_7i43.0.stepgen.00.position-scale  [AXIS_0]SCALE
>> setp hm2_7i43.0.stepgen.00.maxaccel   [AXIS_0]STEPGEN_MAXACCEL
>> setp hm2_7i43.0.stepgen.00.maxvel   [AXIS_0]STEPGEN_MAXVEL
>> setp hm2_7i43.0.stepgen.00.step_type0
>> setp hm2_7i43.0.stepgen.00.control-type1
>> 
>> # --closed loop stepper signals--
>> net x-pos-cmd axis.0.motor-pos-cmd
>> net x-output => hm2_7i43.0.stepgen.00.velocity-cmd
>> net x-enable axis.0.amp-enable-out => hm2_7i43.0.stepgen.00.enable
>> 
>> # ---Encoder feedback signals/setup---
>> setp hm2_7i43.0.encoder.00.counter-mode 0
>> setp hm2_7i43.0.encoder.00.filter 1
>> setp hm2_7i43.0.encoder.00.index-invert 0
>> setp hm2_7i43.0.encoder.00.index-mask 0
>> setp hm2_7i43.0.encoder.00.index-mask-invert 0
>> setp hm2_7i43.0.encoder.00.scale  [AXIS_0]INPUT_SCALE
>> 
>> net x-pos-fb <= hm2_7i43.0.encoder.00.position
>> net x-vel-fb <= hm2_7i43.0.encoder.00.velocity
>> net x-pos-fb => axis.0.motor-pos-fb
>> net x-index-enable axis.0.index-enable <=>
>> hm2_7i43.0.encoder.00.index-enable net x-pos-rawcounts <=
>> hm2_7i43.0.encoder.00.rawcounts
>> 
>> # ---setup home / limit switch signals---
>> net x-home-sw =>  axis.0.home-sw-in
>> net x-neg-limit =>  axis.0.neg-lim-sw-in
>> net x-pos-limit =>  axis.0.pos-lim-sw-in
>> 
>>  end HAL 
>> 
>>  INI 
>> [EMC]
>> MACHINE = EMCO
>> DEBUG = 0
>> 
>> [DISPLAY]
>> DISPLAY = axis
>> EDITOR = gedit
>> PYVCP = custom_pyvcp.xml
>> POSITION_OFFSET = RELATIVE
>> POSITION_FEEDBACK = ACTUAL
>> MAX_FEED_OVERRIDE = 2.0
>> MAX_SPINDLE_OVERRIDE = 1.5
>> MIN_SPINDLE_OVERRIDE = 0.50
>> INTRO_GRAPHIC = linuxcnc.gif
>> INTRO_TIME = 2
>> PROGRAM_PREFIX = /home/tom/linuxcnc/nc_files
>> INCREMENTS = .1in .05in .01in .005in .001in .0005in .0001in
>> POSITION_OFFSET = RELATIVE
>> POSITION_FEEDBACK = ACTUAL
>> DEFAULT_LINEAR_VELOCITY = 0.25
>> MAX_LINEAR_VELOCITY = 1.00
>> MIN_LINEAR_VELOCITY = 0.01
>> DEFAULT_ANGULAR_VELOCITY = 0.25
>> MAX_ANGULAR_VELOCITY = 1.00
>> MIN_ANGULAR_VELOCITY = 0.01
>> GEOMETRY = xyz
>> 
>> [FILTER]
>> 

Re: [Emc-users] Interp problems?

[dave]

On 06/25/2017 04:53 PM, andy pugh wrote:

On 25 June 2017 at 21:47, dave  wrote:


For right now I suspect cpu temp.
Homing is manual


Are you sure that you are doing this right?

If you jog to your manual home position and re-home, does the problem go
away?

I've lost the thread 
As of this morning  cooler weather the limits violation went away.
The shift in G55 didn't disappear every loop through a pocket shifted 
about 1 cm.
Current tack is to replace the X encoder and see if that fixes things. 
Time will tell.

It might be a couple of days before I get things settled again.
Keep poking, we'll get this sorted yet.

Dave

Rehome, exit Tk... , etc, do a total shutdown and boot, no joy.
















--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] steppers with encoders in closed loop

[Gene Heskett]

On Sunday 25 June 2017 18:12:14 tom-...@bgp.nu wrote:

> I would like to attempt to get my machine with stepper motors running
> in velocity mode with feedback from the encoders.  Below are the
> relevant parts of my Hal and Ini files for just the X-Axis.  I figured
> I would do one axis at a time.  Currently nothing happens when I try
> to jog the X axis except if I hold it long enough it gives a following
> error.  If I try to home it, it faults with a following error.  I was
> trying to look various parameters on Halscope, triggering off of
> axis.0.f-error but nothing appears for any of the pins I was
> monitoring.   Are there any obvious errors in the config below to
> start with?
>
> -Tom
>
>  HAL 
> loadrt trivkins
> loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD
> num_joints=[TRAJ]AXES loadrt hostmot2
> loadrt hm2_7i43  config="firmware=hm2/7i43/SVST2_4_7I47B.BIT
> num_encoders=3 num_pwmgens=0 num_stepgens=4" loadrt pid
> names=pid.x,pid.y,pid.z
>
> addf hm2_7i43.0.read servo-thread
> addf motion-command-handler servo-thread
> addf motion-controller servo-thread
> addf pid.x.do-pid-calcs   servo-thread
> addf pid.y.do-pid-calcs   servo-thread
> addf pid.z.do-pid-calcs   servo-thread
> addf hm2_7i43.0.write servo-thread
>
>
> #***
> #  AXIS X
> #***
> # axis enable chain
>
> setp  pid.x.Pgain [AXIS_0]P
> setp  pid.x.Igain [AXIS_0]I
> setp  pid.x.Dgain [AXIS_0]D
> setp  pid.x.bias  [AXIS_0]BIAS
> setp  pid.x.FF0   [AXIS_0]FF0
> setp  pid.x.FF1   [AXIS_0]FF1
> setp  pid.x.FF2   [AXIS_0]FF2
> setp  pid.x.deadband  [AXIS_0]DEADBAND
> setp  pid.x.maxoutput [AXIS_0]MAX_OUTPUT
>
> net x-index-enable <=> pid.x.index-enable
> net x-enable => pid.x.enable
> net x-ouput => pid.x.output
> net x-pos-cmd => pid.x.command
> net x-vel-fb => pid.x.feedback-deriv
> net x-pos-fb => pid.x.feedback
>
> # Step Gen signals/setup
> setp hm2_7i43.0.stepgen.00.dirsetup[AXIS_0]DIRSETUP
> setp hm2_7i43.0.stepgen.00.dirhold [AXIS_0]DIRHOLD
> setp hm2_7i43.0.stepgen.00.steplen [AXIS_0]STEPLEN
> setp hm2_7i43.0.stepgen.00.stepspace   [AXIS_0]STEPSPACE
> setp hm2_7i43.0.stepgen.00.position-scale  [AXIS_0]SCALE
> setp hm2_7i43.0.stepgen.00.maxaccel  [AXIS_0]STEPGEN_MAXACCEL
> setp hm2_7i43.0.stepgen.00.maxvel[AXIS_0]STEPGEN_MAXVEL
> setp hm2_7i43.0.stepgen.00.step_type  0
> setp hm2_7i43.0.stepgen.00.control-type   1
>
> # --closed loop stepper signals--
> net x-pos-cmd axis.0.motor-pos-cmd
> net x-output => hm2_7i43.0.stepgen.00.velocity-cmd
> net x-enable axis.0.amp-enable-out => hm2_7i43.0.stepgen.00.enable
>
> # ---Encoder feedback signals/setup---
> setp hm2_7i43.0.encoder.00.counter-mode 0
> setp hm2_7i43.0.encoder.00.filter 1
> setp hm2_7i43.0.encoder.00.index-invert 0
> setp hm2_7i43.0.encoder.00.index-mask 0
> setp hm2_7i43.0.encoder.00.index-mask-invert 0
> setp hm2_7i43.0.encoder.00.scale  [AXIS_0]INPUT_SCALE
>
> net x-pos-fb <= hm2_7i43.0.encoder.00.position
> net x-vel-fb <= hm2_7i43.0.encoder.00.velocity
> net x-pos-fb => axis.0.motor-pos-fb
> net x-index-enable axis.0.index-enable <=>
> hm2_7i43.0.encoder.00.index-enable net x-pos-rawcounts <=
> hm2_7i43.0.encoder.00.rawcounts
>
> # ---setup home / limit switch signals---
> net x-home-sw =>  axis.0.home-sw-in
> net x-neg-limit =>  axis.0.neg-lim-sw-in
> net x-pos-limit =>  axis.0.pos-lim-sw-in
>
>  end HAL 
>
>  INI 
> [EMC]
> MACHINE = EMCO
> DEBUG = 0
>
> [DISPLAY]
> DISPLAY = axis
> EDITOR = gedit
> PYVCP = custom_pyvcp.xml
> POSITION_OFFSET = RELATIVE
> POSITION_FEEDBACK = ACTUAL
> MAX_FEED_OVERRIDE = 2.0
> MAX_SPINDLE_OVERRIDE = 1.5
> MIN_SPINDLE_OVERRIDE = 0.50
> INTRO_GRAPHIC = linuxcnc.gif
> INTRO_TIME = 2
> PROGRAM_PREFIX = /home/tom/linuxcnc/nc_files
> INCREMENTS = .1in .05in .01in .005in .001in .0005in .0001in
> POSITION_OFFSET = RELATIVE
> POSITION_FEEDBACK = ACTUAL
> DEFAULT_LINEAR_VELOCITY = 0.25
> MAX_LINEAR_VELOCITY = 1.00
> MIN_LINEAR_VELOCITY = 0.01
> DEFAULT_ANGULAR_VELOCITY = 0.25
> MAX_ANGULAR_VELOCITY = 1.00
> MIN_ANGULAR_VELOCITY = 0.01
> GEOMETRY = xyz
>
> [FILTER]
> PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
> PROGRAM_EXTENSION = .py Python Script
> png = image-to-gcode
> gif = image-to-gcode
> jpg = image-to-gcode
> py = python
>
> [TASK]
> TASK = milltask
> CYCLE_TIME = 0.010
>
> [RS274NGC]
> PARAMETER_FILE = emc.var
>
> [EMCMOT]
> EMCMOT = motmod
> COMM_TIMEOUT = 1.0
> COMM_WAIT = 0.010
> #BASE_PERIOD = 5
> SERVO_PERIOD = 100
>
> # [HOSTMOT2]
> # This is for info only - config line is in the .hal file
> # DRIVER0=hm2_7i43
> # BOARD0=7i43
> # CONFIG0="firmware=hm2/7i43/SVST2_4_7I47B.BIT num_encoders=3
> num_pwmgens=0 num_stepgens=4"
>
> [HAL]
> HALUI = halui
> HALFILE = EMCO-CL.hal
> HALFILE = 

Re: [Emc-users] Interp problems?

[andy pugh]

On 25 June 2017 at 15:21, dave  wrote:

> I suspect that this is a thermal problem


Whereas I consider the idea that it is a _Computer_ thermal problem almost
inconceivable.


-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
for the especial use of mechanical geniuses, daredevils and lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[andy pugh]

On 25 June 2017 at 21:47, dave  wrote:

> For right now I suspect cpu temp.
> Homing is manual
>

Are you sure that you are doing this right?

If you jog to your manual home position and re-home, does the problem go
away?

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
for the especial use of mechanical geniuses, daredevils and lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

[Emc-users] steppers with encoders in closed loop

[tom-emc]

I would like to attempt to get my machine with stepper motors running in 
velocity mode with feedback from the encoders.  Below are the relevant parts of 
my Hal and Ini files for just the X-Axis.  I figured I would do one axis at a 
time.  Currently nothing happens when I try to jog the X axis except if I hold 
it long enough it gives a following error.  If I try to home it, it faults with 
a following error.  I was trying to look various parameters on Halscope, 
triggering off of axis.0.f-error but nothing appears for any of the pins I was 
monitoring.   Are there any obvious errors in the config below to start with?

-Tom

 HAL 
loadrt trivkins
loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD 
num_joints=[TRAJ]AXES
loadrt hostmot2
loadrt hm2_7i43  config="firmware=hm2/7i43/SVST2_4_7I47B.BIT num_encoders=3 
num_pwmgens=0 num_stepgens=4"
loadrt pid names=pid.x,pid.y,pid.z

addf hm2_7i43.0.read servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf pid.x.do-pid-calcs servo-thread
addf pid.y.do-pid-calcs servo-thread
addf pid.z.do-pid-calcs servo-thread
addf hm2_7i43.0.write servo-thread


#***
#  AXIS X
#***
# axis enable chain

setppid.x.Pgain [AXIS_0]P
setppid.x.Igain [AXIS_0]I
setppid.x.Dgain [AXIS_0]D
setppid.x.bias  [AXIS_0]BIAS
setppid.x.FF0   [AXIS_0]FF0
setppid.x.FF1   [AXIS_0]FF1
setppid.x.FF2   [AXIS_0]FF2
setppid.x.deadband  [AXIS_0]DEADBAND
setppid.x.maxoutput [AXIS_0]MAX_OUTPUT

net x-index-enable <=> pid.x.index-enable
net x-enable => pid.x.enable
net x-ouput => pid.x.output
net x-pos-cmd => pid.x.command
net x-vel-fb => pid.x.feedback-deriv
net x-pos-fb => pid.x.feedback

# Step Gen signals/setup
setp hm2_7i43.0.stepgen.00.dirsetup[AXIS_0]DIRSETUP
setp hm2_7i43.0.stepgen.00.dirhold [AXIS_0]DIRHOLD
setp hm2_7i43.0.stepgen.00.steplen [AXIS_0]STEPLEN
setp hm2_7i43.0.stepgen.00.stepspace   [AXIS_0]STEPSPACE
setp hm2_7i43.0.stepgen.00.position-scale  [AXIS_0]SCALE
setp hm2_7i43.0.stepgen.00.maxaccel[AXIS_0]STEPGEN_MAXACCEL
setp hm2_7i43.0.stepgen.00.maxvel  [AXIS_0]STEPGEN_MAXVEL
setp hm2_7i43.0.stepgen.00.step_type0
setp hm2_7i43.0.stepgen.00.control-type 1

# --closed loop stepper signals--
net x-pos-cmd axis.0.motor-pos-cmd
net x-output => hm2_7i43.0.stepgen.00.velocity-cmd
net x-enable axis.0.amp-enable-out => hm2_7i43.0.stepgen.00.enable

# ---Encoder feedback signals/setup---
setp hm2_7i43.0.encoder.00.counter-mode 0
setp hm2_7i43.0.encoder.00.filter 1
setp hm2_7i43.0.encoder.00.index-invert 0
setp hm2_7i43.0.encoder.00.index-mask 0
setp hm2_7i43.0.encoder.00.index-mask-invert 0
setp hm2_7i43.0.encoder.00.scale  [AXIS_0]INPUT_SCALE

net x-pos-fb <= hm2_7i43.0.encoder.00.position
net x-vel-fb <= hm2_7i43.0.encoder.00.velocity
net x-pos-fb => axis.0.motor-pos-fb
net x-index-enable axis.0.index-enable <=> hm2_7i43.0.encoder.00.index-enable
net x-pos-rawcounts <= hm2_7i43.0.encoder.00.rawcounts

# ---setup home / limit switch signals---
net x-home-sw =>  axis.0.home-sw-in
net x-neg-limit =>  axis.0.neg-lim-sw-in
net x-pos-limit =>  axis.0.pos-lim-sw-in

 end HAL 

 INI 
[EMC]
MACHINE = EMCO
DEBUG = 0

[DISPLAY]
DISPLAY = axis
EDITOR = gedit
PYVCP = custom_pyvcp.xml
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
MAX_FEED_OVERRIDE = 2.0
MAX_SPINDLE_OVERRIDE = 1.5
MIN_SPINDLE_OVERRIDE = 0.50
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 2
PROGRAM_PREFIX = /home/tom/linuxcnc/nc_files
INCREMENTS = .1in .05in .01in .005in .001in .0005in .0001in
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
DEFAULT_LINEAR_VELOCITY = 0.25
MAX_LINEAR_VELOCITY = 1.00
MIN_LINEAR_VELOCITY = 0.01
DEFAULT_ANGULAR_VELOCITY = 0.25
MAX_ANGULAR_VELOCITY = 1.00
MIN_ANGULAR_VELOCITY = 0.01
GEOMETRY = xyz

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
PARAMETER_FILE = emc.var

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
#BASE_PERIOD = 5
SERVO_PERIOD = 100

# [HOSTMOT2]
# This is for info only - config line is in the .hal file
# DRIVER0=hm2_7i43 
# BOARD0=7i43
# CONFIG0="firmware=hm2/7i43/SVST2_4_7I47B.BIT num_encoders=3 num_pwmgens=0 
num_stepgens=4" 

[HAL]
HALUI = halui
HALFILE = EMCO-CL.hal
HALFILE = custom.hal
POSTGUI_HALFILE = custom_postgui.hal

[HALUI]
MDI_COMMAND = G53 G0 X0 Y0 Z0
MDI_COMMAND = o call

[TRAJ]
AXES = 3
COORDINATES = X Y Z
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_VELOCITY = 0.5
MAX_LINEAR_VELOCITY = 2
DEFAULT_ANGULAR_VELOCITY = 0.25
MAX_ANGULAR_VELOCITY = 1.0

[EMCIO]
EMCIO = io

[Emc-users] more advice needed

[Gene Heskett]

Greetings all;

I just about have my g33wrapper.ngc working again, but I see several 
problems because I used fixed values for some of the variables, derived 
by successive approximations.  Not good for versatility should I want to 
carve some of Andy's threads. :)

I want it to be universal, but I am not there yet.

Those I need to sort, but first I need to fix in my mind things like 
which edge of the threading tool should be doing the cutting, leading 
edge always or trailing edge always?

Trailing edge seems to work but did seem to cause a medium frequency 
judder as the cut got deeper. This I think may be in the spindle 
bearings & I need to remove a thou worth of shim in the front bearing as 
its running 10F cooler than the rear ATM after 10 minutes at around 1600 
rpm.

Worst case rise is about 35F over room. I am told that is expected from 
bronze bearings. And I'd imagine some of it is not metal to metal drag, 
but oil viscosity in that thin a film. So the 10W non-detergent may get 
replaced by 5w-20 synthetic.

It sure works wonders in the small yard engines and standby generators 
about the place, allowing them to be started by pull string on the first 
pull in zero F weather.

The oil consumption has also been cut by very noticeable amounts, that 
12.5hp in my rider is burning very little compared to the fixed 20w with 
5w30 in it, and it starts instantly even in snowplow weather. On the 20w 
I'd be adding a pint about every other time I mowed. On the 5w30, in 2 
years, I still have half the makeup quart I bought left. 

Is there any reason I should not use modern oils in this lathe?

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)
Genes Web page 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[dave]

On 06/25/2017 12:34 PM, Jon Elson wrote:

On 06/25/2017 12:44 PM, dave wrote:





Multiple problems:
Having cooled off the  shop a bit the limits violation seems to have 
gone away for now. We'll see
what later in the day brings. BTW the limit violations were 
consistent between axis and tklinuxcnc.


Multiple passes thru a small routine show progressive x offset with 
each iteration. :-(
Dial indicator on X is clean in one direction but not the other which 
usually indicates a broken
coupler to the encoder. I'll have to tear into the housing to verify 
that. Shift is about a cm for
each pass of a pocketing routine. Same shift pattern as another 
routine to inlet a tang on a stock.


Well, could be a marginal encoder that is reporting more counts in one 
direction than the other.
That COULD be affected by heat.  Or, the encoder counter could be 
missing counts.


Jon

I've unmounted the encoder and the coupling was not broken so that 
leaves connections/cabling or
a failed encoder.  This is the first summer with this cpu. The old Duron 
1200 would go on strike when

the shop got too warm.
Much more to verify .

Dave
-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[dave]

On 06/25/2017 12:32 PM, Jon Elson wrote:

On 06/25/2017 09:21 AM, dave wrote:



.warning:  gcode exceeds machine limits. I classically set my 
limits at -.2 ..18, -.2, ..9 and 0 ... -3.
Moving to -9 ... 9, -4 ... 4  for x and y and it still gave me the 
same error message.  and yes I shutdown linuxcnc and restarted 
homing on the center of the bed.


I can't POSSIBLY see how temperature could affect soft limits, which 
is what your message describes.  The only way this could happen is 
computer malfunction or homing to a different spot than was intended 
for home.



For right now I suspect cpu temp.
Homing is manual and I know rather well where each axis is when I home.
Lots of things to look at...

Dave
-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[Jon Elson]

On 06/25/2017 09:21 AM, dave wrote:



.warning:  gcode exceeds machine limits. I classically 
set my limits at -.2 ..18, -.2, ..9 and 0 ... -3.
Moving to -9 ... 9, -4 ... 4  for x and y and it still 
gave me the same error message.  and yes I shutdown 
linuxcnc and restarted homing on the center of the bed.


I can't POSSIBLY see how temperature could affect soft 
limits, which is what your message describes.  The only way 
this could happen is computer malfunction or homing to a 
different spot than was intended for home.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[Jon Elson]

On 06/25/2017 12:44 PM, dave wrote:





Multiple problems:
Having cooled off the  shop a bit the limits violation 
seems to have gone away for now. We'll see
what later in the day brings. BTW the limit violations 
were consistent between axis and tklinuxcnc.


Multiple passes thru a small routine show progressive x 
offset with each iteration. :-(
Dial indicator on X is clean in one direction but not the 
other which usually indicates a broken
coupler to the encoder. I'll have to tear into the housing 
to verify that. Shift is about a cm for
each pass of a pocketing routine. Same shift pattern as 
another routine to inlet a tang on a stock.


Well, could be a marginal encoder that is reporting more 
counts in one direction than the other.
That COULD be affected by heat.  Or, the encoder counter 
could be missing counts.


Jon

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[Jon Elson]

On 06/24/2017 06:20 PM, dave wrote:



Thanks Jon,
Tried that earlier in the day and didn't get anything.
Just tried it again and what to my wondering eyes ... 
axis. :-)
Still struggling with the interface but it seems to be 
giving me the same errors as tk.
I can't quite figure out how I can be in the middle of the 
bed  with a small part and still

get limit violations.
These are soft limit errors, or limit switch tripped 
errors?  Soft limit errors will manifest when you try to jog 
past them, the machine will just stop with no explanation.  
A limit switched tripped will raise a red warning message on 
the screen.
If you are getting limit switch tripped conditions, then you 
may have a problem with flaky wiring, or insufficient 
pull-up or whatever on the digital inputs.  If soft limits, 
then you need to check that homing is working right, and 
that the right numbers have been given for MIN_LIMIT and 
MAX_LIMIT for each axis.
I suspect it is heat. The heat sink was maybe 120 F. 
Before I go too much farther

I will rig a fan.

If you are getting FOLLOWING error limits, then the axis is 
not following the commanded position accurately.


Jon

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[dave]

On 06/25/2017 07:21 AM, dave wrote:



On 06/25/2017 02:55 AM, andy pugh wrote:

On 25 June 2017 at 00:20, dave  wrote:

can't quite figure out how I can be in the middle of the bed  
with a

small part and still
get limit violations


Is this actual limit-switch trips. or warnings that the G-code exceeds
machine limits?

The first is probably electrical noise. I seem to always end up with a
software low-pass on those signals, just because false-trips are so
annoying and a couple of mS delay in responding to a limit switch isn't
that critical.

If it is the second, then you might need to have a look at your 
coordinate

system offsets.
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?CoordinateSystems#So_if_you_re_lost_what_should_you_do 




.warning:  gcode exceeds machine limits. I classically set my 
limits at -.2 ..18, -.2, ..9 and 0 ... -3.
Moving to -9 ... 9, -4 ... 4  for x and y and it still gave me the 
same error message.  and yes I shutdown linuxcnc and restarted 
homing on the center of the bed.


I suspect that this is a thermal problem ... small fan blowing across 
the mb. Next step is to rig a
 so-called 'whisper' fan off an 11/40. Can you believe they have a 
100,000 hrs on them.

Temp is 55 this morn so I'm blowing cool air into the shop. :-)

One issue at a time...

Tnx

Dave

Multiple problems:
Having cooled off the  shop a bit the limits violation seems to have 
gone away for now. We'll see
what later in the day brings. BTW the limit violations were consistent 
between axis and tklinuxcnc.


Multiple passes thru a small routine show progressive x offset with each 
iteration. :-(
Dial indicator on X is clean in one direction but not the other which 
usually indicates a broken
coupler to the encoder. I'll have to tear into the housing to verify 
that. Shift is about a cm for
each pass of a pocketing routine. Same shift pattern as another routine 
to inlet a tang on a stock.


Bird walking a bit  my Z axis encoder is driven off a small timing 
pulley that couples the
encoder to the servo drive belt. ~100K counts/in. I'm thinking the same 
thing could be used

for the X and eliminate the coupler and make access easier.

Stay tuned we'll sort this out yet with help.

Dave

-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[jeremy youngs]

All machine move offs should be in the negative direction. I.e. I believe
you have your scales backwards. There was an illustration pinned in the
forum about this

On Jun 25, 2017 9:28 AM, "dave"  wrote:

>
>
> On 06/25/2017 02:55 AM, andy pugh wrote:
>
>> On 25 June 2017 at 00:20, dave  wrote:
>>
>> can't quite figure out how I can be in the middle of the bed  with a
>>> small part and still
>>> get limit violations
>>>
>>> Is this actual limit-switch trips. or warnings that the G-code exceeds
>> machine limits?
>>
>> The first is probably electrical noise. I seem to always end up with a
>> software low-pass on those signals, just because false-trips are so
>> annoying and a couple of mS delay in responding to a limit switch isn't
>> that critical.
>>
>> If it is the second, then you might need to have a look at your coordinate
>> system offsets.
>> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?CoordinateSystems#S
>> o_if_you_re_lost_what_should_you_do
>>
>>
>> .warning:  gcode exceeds machine limits. I classically set my limits
> at -.2 ..18, -.2, ..9 and 0 ... -3.
> Moving to -9 ... 9, -4 ... 4  for x and y and it still gave me the same
> error message.  and yes I shutdown linuxcnc and restarted homing on the
> center of the bed.
>
> I suspect that this is a thermal problem ... small fan blowing across the
> mb. Next step is to rig a
>  so-called 'whisper' fan off an 11/40. Can you believe they have a 100,000
> hrs on them.
> Temp is 55 this morn so I'm blowing cool air into the shop. :-)
>
> One issue at a time...
>
> Tnx
>
> Dave
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[dave]

On 06/25/2017 02:55 AM, andy pugh wrote:

On 25 June 2017 at 00:20, dave  wrote:


can't quite figure out how I can be in the middle of the bed  with a
small part and still
get limit violations


Is this actual limit-switch trips. or warnings that the G-code exceeds
machine limits?

The first is probably electrical noise. I seem to always end up with a
software low-pass on those signals, just because false-trips are so
annoying and a couple of mS delay in responding to a limit switch isn't
that critical.

If it is the second, then you might need to have a look at your coordinate
system offsets.
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?CoordinateSystems#So_if_you_re_lost_what_should_you_do


.warning:  gcode exceeds machine limits. I classically set my limits 
at -.2 ..18, -.2, ..9 and 0 ... -3.
Moving to -9 ... 9, -4 ... 4  for x and y and it still gave me the same 
error message.  and yes I shutdown linuxcnc and restarted homing on 
the center of the bed.


I suspect that this is a thermal problem ... small fan blowing across 
the mb. Next step is to rig a
 so-called 'whisper' fan off an 11/40. Can you believe they have a 
100,000 hrs on them.

Temp is 55 this morn so I'm blowing cool air into the shop. :-)

One issue at a time...

Tnx

Dave


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Interp problems?

[andy pugh]

On 25 June 2017 at 00:20, dave  wrote:

> can't quite figure out how I can be in the middle of the bed  with a
> small part and still
> get limit violations
>

Is this actual limit-switch trips. or warnings that the G-code exceeds
machine limits?

The first is probably electrical noise. I seem to always end up with a
software low-pass on those signals, just because false-trips are so
annoying and a couple of mS delay in responding to a limit switch isn't
that critical.

If it is the second, then you might need to have a look at your coordinate
system offsets.
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?CoordinateSystems#So_if_you_re_lost_what_should_you_do


-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is designed
for the especial use of mechanical geniuses, daredevils and lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users