On 11/23/2016 5:45 PM, Mike Ross wrote:
> I think I've identified the location of the problem, I just need some hints 
> on 
> how to get over it.
> 
> Watching the component pins I can see the position_cmd change when I issue an 
> M6 
> Tx command, but there is no stepper activity.
> 
> It seems to me that the problem is related to this being done on a BBB with 
> PRU ...
> The original toolchanger hal file has:
> net apos-cmd toolchanger.position.cmd => stepgen.3.position-cmd
> 
> I thought all I needed to do was update that to hpg.stepgen.03.position-cmd 
> and 
> all would be good but the Xylotex.hal file I'm editing doesn't have a 
> hpg.stepgen.03.position-cmd
> 
> So the question is what am I supposed to link to?  There are a few I can try 
> but 
> its a bit painful doing it trial and error.
> help here is appreciated.

I'm not sure what Xylotex.hal file you started with, but the example
configuration has entries for 4 axis (and the cape can support more
using the IDC header):

https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Xylotex/Xylotex.hal#L227-L279

You need to make sure you are loading the hal_pru_generic driver with
the appropriate number specified for num_stepgens:

https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Xylotex/Xylotex.ini#L3

...otherwise, you just need to tie whatever position command you are
using for your tool changer to the hal_pru_generic stepgen driver to
create the step/dir signals.

-- 
Charles Steinkuehler
[email protected]

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to