Quoth Chris Morley.....
>
>> From: Andy Pugh
>> On 2 October 2013 18:26, Russell Brown <russ...@lls.lls.com> wrote:
>> 
>> >         loadrt abs names=
>> >         loadrt lowpass names=
>> 
>> This is a stepfconf bug. I can't recall what prompts it. I thought it
>> was fixed. (it tries to load a bunch of components with blank names,
>> and then their pin names collide)
>
>Pncconf bug -but is probably fixed. what version was this made with?

It's PNCconf Beta 1 (linuxcnc 2.5.3, lucid)

(the system was built from the ISO on the linuxcnc website)

FWIW, I just did a:

git clone git://git.linuxcnc.org/git/linuxcnc.git linuxcnc-dev

config,make,source scripts/rip-environment and then ran bin/pncconf.

That also identifies itself as Beta 1 Version although the linuxcnc it
built is 2.6.0~pre

>> > http://ruffle.me.uk/cnc/Mesa_Mill.ini
>> > http://ruffle.me.uk/cnc/Mesa_Mill.hal
>> 
>> The INI file Z axis max velocity in the INI is a lot higher than the
>> stepgen max velocity in the HAL file.
>
>I'm sure that was hand edited.

Yes the velocities in the INI file have been hand edited while I was
mucking around (the comments in the file show the various
values/problems).  I must admit that I didn't notice the absolute values
in the HAL file...  I just changed the INI file as I had with the
vanilla parallel port setup and as the docs suggest was normal practise
after generating the initial config.

>> Also, the HAL file is not actually looking in the INI file for the
>> stepgen maxaccel, so ini file settings are not having any effect.

FWIW, they do effect the AXIS UI by limiting the max jog speeds.

>> (Which version of PNCconf is this? It is making a lot of mistakes). If
>> you look in the HAL file both stepgen accel and velocity are absolute
>> values rather than being sucked out of the INI file.
>
>That is the way it was meant to be.
>PNCconf has no stepgen_max entries.
>If they are there - they are hand edited.

Ummmm....  maybe I misunderstood what you just said but PNCconf does
generate MAX_VELOCITY and MAX_ACCELERATION in the INI file for each
axis.

PNCconf also, as Andy rightly observed, puts
hm2_5i25.0.stepgen.XX.maxaccel and hm2_5i25.0.stepgen.XX.maxvel in the
HAL file as absolute values (albeit different to the values in the INI
file; see below).

(I just did fresh test configuration run with PNCconf to confirm the
above).

This is what lead to my confusion as I was changing the values in the
INI file but, I guess, the values in the HAL file were causing the
following errors (the numbers stack up anyway as the HAL file had a
Z-maxvel of 17.7 and X-maxvel of 39.8; these pretty much match up with
the tripping point of the following errors for each axis).

So I tried changing my 'real' HAL file like so:

setp   hm2_5i25.0.stepgen.00.maxaccel        [AXIS_0]MAX_ACCELERATION
setp   hm2_5i25.0.stepgen.00.maxvel          [AXIS_0]MAX_VELOCITY

for each axis.  Bzzzzzzzzzzzt Nope that wasn't good and made things
worse (X would only go to < 586 mm/min without following errors).

So I then changed the absolute values in the HAL and INI to match (used
round numbers) and tried jogging.  That generated following errors when
I stopped the jog (took my finger off the mouse button in continuous
mode).

Hmmmm....  back to my test config, I reran PNCconf and set max speed to
4000 mm/min and the three axis to:

X       800 Stepper Scale, 3000 mm/min Velocity, 350 mm/sec2 Acceleration
Y       800 Stepper Scale, 3100 mm/min Velocity, 400 mm/sec2 Acceleration
Z       400 Stepper Scale, 3200 mm/min Velocity, 450 mm/sec2 Acceleration

This puts the following in the INI file:

X     MAX_VELOCITY = 50.0            MAX_ACCELERATION = 350.0
Y     MAX_VELOCITY = 51.6666666667   MAX_ACCELERATION = 400.0
Z     MAX_VELOCITY = 53.3333333333   MAX_ACCELERATION = 450.0

and in the HAL file:

setp   hm2_5i25.0.stepgen.00.maxaccel         437.5
setp   hm2_5i25.0.stepgen.00.maxvel           62.5

setp   hm2_5i25.0.stepgen.01.maxaccel         500.0
setp   hm2_5i25.0.stepgen.01.maxvel           64.6

setp   hm2_5i25.0.stepgen.02.maxaccel         562.5
setp   hm2_5i25.0.stepgen.02.maxvel           66.7

...and I can jog at full speed on each axis without following errors.

So.  Why are the absolute values in the INI different to the ones in the
HAL file?  There's obviously some magic going on here :-)

...and how is one meant to tweak velocities/acceleration in 
a configuration generated by PNCconf?  (perhaps a comment in the PNCconf
generated INI file would stop someone else falling into the same hole).

-- 
 Regards,
     Russell
 --------------------------------------------------------------------
| Russell Brown          | MAIL: russ...@lls.com PHONE: 01780 471800 |
| Lady Lodge Systems     | WWW Work: http://www.lls.com              |
| Peterborough, England  | WWW Play: http://www.ruffle.me.uk         |
 --------------------------------------------------------------------

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to