On 1/16/14 09:48 , Charles Steinkuehler wrote: > 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:
Dewey can probably answer better than i can, but here's my input. > * 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? I think by_machine is for configs that correspond to specific, widely available machines, where the config can know the details of tunables like SCALE and stepgen timings. I think that's not the case for the configs you're making, i think your configs are for specific home-made machines, and you don't necessarily know the microstepping of the amps or the pitch of the leadscrews/drive-belts. If i'm right, then your configs belong in by_interface. > * 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? Different .ini files for the different pinouts. The name of the ini file should give a hint at what the pinout does. The README should explain more fully. > * 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? http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Getting_the_source_with_git TL;DR: linuxcnc installs files in $HOME/linuxcnc, so call your git clone something else, like "$HOME/linuxcnc-dev" as the docs suggest. > 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 Yes :-) > 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? This would currently be handled by the "by_interface" structure. The new configs would go next to the other mesa configs. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ 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
