I am reviewing the new configuration setup for 2.6 and trying to modify
the BeagleBone ARM configurations to follow suit but I have a few questions:

* How do I determine if a configuration should go into by_machine or
by_interface, or am I to somehow create symlinks so it shows up in both?

* Most of my configurations will use the same interface, but may have
different pinouts.  For example, the same 3D printer machine could be
controlled by virtual identical *.ini and *.hal files, with only a small
*.hal file snippet changed to reflect the use of different I/O pins by
various hardware (ie: BeBoPr board, BeBoPr+ or generic CNC board, K9
board, etc).  What is the recommended procedure for reflecting this in
the configuration structure?

* On the BeagleBone images I create, the linuxcnc git working copy is in
~/linuxcnc, but it appears the config picker is wanting to drop files
into ~/linuxcnc.  Is there a suggested location for the linuxcnc build tree?

It seems like perhaps the following would work better:

  ~/linuxcnc          Empty (or missing) directory as shipped

  ~/linuxcnc-dev      LinuxCNC git clone & build directory for RIP

  ~/linuxcnc-dev/
      configs/
        by_machine/
          mendel/                Configuration for mendel 3D printer
            mendel_BeBoPr.ini      using BeBoPr pinout
            mendel_BeBoPr+.ini     using BeBoPr+ pinout
            mendel_K9.ini          using K9 pinout

          rostock/               Configuration for rostock 3D printer
            rostock_BeBoPr.ini     using BeBoPr pinout
            rostock_BeBoPr+.ini    using BeBoPr+ pinout
            rostock_K9.ini         using K9 pinout

Does this seem reasonable?  IMHO, it seems OK as-is, but what happens
when someone wants to provide a similar configuration for something
driven by a mesa card on an x86 instead of a BeagleBone?  How is that
indicated in the config file structure so the config selector presents
something coherent to the user?

-- 
Charles Steinkuehler
char...@steinkuehler.net

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to