On Thu, 2012-02-09 at 11:36 -0600, Jon Elson wrote:
... snip
> Yes, if the docs don't adequately describe how this system of putting
> settings in the
> .ini file and then having HAL code in a HAL file that reads them and
> makes the
> settings to the HAL component, then it does need to be put in
John Thornton wrote:
> I have to disagree with this, you can have unlimited INI options if
> you call them from your HAL file and as we all know this only confuses
> new users when they see a snippet in the manual and assume that it is
> used by LinuxCNC in some way other than how it is used to
I have to disagree with this, you can have unlimited INI options if you
call them from your HAL file and as we all know this only confuses new
users when they see a snippet in the manual and assume that it is used
by LinuxCNC in some way other than how it is used to bring all the
settings to on
On 8 Feb 2012, at 20:14, Jon Elson wrote:
>>
> I think it may be uncommon for servo systems. Most servo systems use
> PID, and the
> PID and FFx parameters are loaded from the .ini file. Also, INPUT_SCALE,
> OUTPUT_SCALE, following error settings, axis limits of travel, etc.
> normally all
andy pugh wrote:
> On 8 February 2012 10:16, Chris Morley wrote:
>
>
>> But most (all?) configs use substitution to apply the INI settings to HAL
>> components.
>>
>
> My own HAL files typically make no reference to the INI file at all. I
> don't know how common that is.
>
I think it ma
:
>
> > But most (all?) configs use substitution to apply the INI settings to HAL
> > components.
>
> My own HAL files typically make no reference to the INI file at all. I
> don't know how common that is.
>
> --
> atp
It's common.
look at the sample configs, stepconf and pncconf configs.
On 8 February 2012 10:16, Chris Morley wrote:
> But most (all?) configs use substitution to apply the INI settings to HAL
> components.
My own HAL files typically make no reference to the INI file at all. I
don't know how common that is.
--
atp
The idea that there is no such thing as objective
> On 8 February 2012 03:27, Chris Morley wrote:
> > While they are specific to these drivers, they are still INI options and
> > belong in the INI section.
> > There are lots of INI option that are specific to certain components.
>
> I don't really understand this statement. As far as I know no
On 8 February 2012 03:27, Chris Morley wrote:
> While they are specific to these drivers, they are still INI options and
> belong in the INI section.
> There are lots of INI option that are specific to certain components.
I don't really understand this statement. As far as I know no HAL
hardware
While they are specific to these drivers, they are still INI options and belong
in the INI section.
There are lots of INI option that are specific to certain components.
I think we just need to note that very few boards utilize it.
output_offset was in PNCconf for a long time until I figured out
Do those drivers read the output_offset from the INI file? If it is
driver specific it belongs in the driver chapter.
John
On 2/6/2012 5:36 PM, Chris Morley wrote:
I've been meaning to bring this up ...
output_offset found in the INI section under servo needs some
clarification.
Not all c
I've been meaning to bring this up ...
output_offset found in the INI section under servo needs some clarification.
Not all components / boards use this feature.
For instance hostmot2 has no provision for output_offset on it's pwmgen.
In fact it seems only servo to go and motenc honors this s
12 matches
Mail list logo
