Re: [Emc-developers] Configuring PRU for dual Y steppers

2014-07-27 Thread Charles Steinkuehler
I do participate on this list, but since LinuxCNC currently has no support for the Xenomai real-time kernel (required to run on the BeagleBone) questions about BeagleBone specific details (like the PRU driver) are really more suited for the Machinekit list. I've also been on vacation in the mounta

Re: [Emc-developers] Sample Configs layout

2014-07-27 Thread Dewey Garrett
(16:44:05) dgarr: andypugh: one way to conform to configs structure, pickconfig, and prior (remap) examples: http://www.pastebin.ca/2826231 (16:45:30) dgarr: there is some info in configs/maintainer.txt too (16:53:15) dgarr: also you can debug and/or see pickconfig copying in a rip by using expor

[Emc-developers] Sample Configs layout

2014-07-27 Thread andy pugh
I made a remapped-T config that uses the new G43.2 to give lathe-style toolchanges. This has been incorporated into 2.6. But unfortunately it doesn't work. The config needs to find "public" remap files (nc_files/remap_lib) but also uses some common files from sim/axis I didn't put it in sim-axis

Re: [Emc-developers] Configuring PRU for dual Y steppers

2014-07-27 Thread Russel Ingram
Thanks for all of the extra information, Gene. I really appreciate it. The Xylotex board I'm talking about is actually just a DB25 interface card for the Beaglebone Black. It's not their driver board. I'm using a Gecko G540 to drive my steppers. The router itself will be a ShapeOKO2 hardware kit th

Re: [Emc-developers] Configuring PRU for dual Y steppers

2014-07-27 Thread Russel Ingram
Well, actually, Sebastian, the PRU driver (hal_pru_generic) is part of the LinuxCNC git repository. It's not in the master branch, but it is part of the code in the linuxcnc.org git repo. The reason I posted here is that, based on the archives for this mailing list, it looks like the guy who wrote

Re: [Emc-developers] possible bug in the latest 2.5.4

2014-07-27 Thread Gene Heskett
On Sunday 27 July 2014 07:43:08 andy pugh did opine And Gene did reply: > On 27 July 2014 12:36, Gene Heskett wrote: > > I've cut several metric threads using that line of code, seemed to > > have worked as the 8mm purchased nuts fit well. But you raise a > > point I may have missed, so in the int

Re: [Emc-developers] possible bug in the latest 2.5.4

2014-07-27 Thread andy pugh
On 27 July 2014 12:36, Gene Heskett wrote: > I've cut several metric threads using that line of code, seemed to have > worked as the 8mm purchased nuts fit well. But you raise a point I may > have missed, so in the interests of doing it right, how are metric threads > specified? M8 coarse is M8

Re: [Emc-developers] possible bug in the latest 2.5.4

2014-07-27 Thread Gene Heskett
On Sunday 27 July 2014 06:55:04 andy pugh did opine And Gene did reply: > On 27 July 2014 05:58, Gene Heskett wrote: > >> Does the code depend on a parameter that isn't set at program load > >> time? > > > > Well, for the G76 code, you do need quite a few parameters, but the > > only ones set at

Re: [Emc-developers] Configuring PRU for dual Y steppers

2014-07-27 Thread Gene Heskett
On Sunday 27 July 2014 01:27:48 Russel Ingram did opine And Gene did reply: > Yeah, I know I could hardwire it to work. I would rather not. > Especially since the software is capable of doing what I want, at > least with other drivers. If I can do it in software, the cabling is > much simpler. Than

Re: [Emc-developers] possible bug in the latest 2.5.4

2014-07-27 Thread andy pugh
On 27 July 2014 05:58, Gene Heskett wrote: >> Does the code depend on a parameter that isn't set at program load >> time? > Well, for the G76 code, you do need quite a few parameters, but the only > ones set at program load time are the Zstart, Zend, TPI or TPmm and the OD > of the thread. It i