> > On 30 October 2016 at 14:47, Jim Craig <[email protected]> wrote:
> >> Since the current functionality reads a running configuration, I would
> >> like to be able to read the .ini file that is currently loaded to get
> >> access to the .hal files that make up the current running configuration.
> > I would actually suggest that the tool should start by asking for a
> > single HAL file, or the INI file for the config to be examined.
> I plan on adding separate methods to load from an ini or a HAL file 
> directly without a running configuration. However I also plan on working 
> from a running configuration.

I think you use "loadrt" and ask for hardware capabilities. Then suitable 
symbols are added or generated which may be used for configuration.

> The reason I keep coming back to working from a running configuration is 
> that it provides a better way to access pins of some components. For 
> instance a postgui.hal file may have many pins that cannot be determined 
> unless the linuxcnc GUI is running. The same issues have been raised 
> about the Pico Systems configurations and the Mesa configurations. While 
> it may be possible to access the components and pins by loading and 
> unloading each component the postgui.hal file pins are not possible to 
> access without a running configuration and the GUI being operational.

You might be right with this, it might not be possible to determine hardware 
without a running configuration. The posgui.hal file however may or may not 
reflect the hardware, it could be outdated.

> Does this seem reasonable or is there another way around this?
> 
> Is there any way to determine what the current .ini file is for the 
> running configuration?

The *.ini file stor constants which may accessed from the *.hal file, I think 
it would be possible to run without this but named constant in separate file 
make sense. The *.hal file is used to components, add threads and in particular 
connect things.

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to