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.


On Tuesday, November 22, 2016 at 7:30:03 AM UTC, Schooner wrote:
>
>
>
> On 22/11/2016 03:11, Mike Ross wrote:
>
> Thanks, 
> I was able to compile the attached file once I created a posix folder 
> (there is an issue open about comp on xenomai) and I was able to copy it 
> over to the xenomai folder.
>
> I've managed to get Axis to run now but don't get a response from my 
> stepper when I issue a M6 Tx command.  I'll need to troubleshoot a bit 
> further and see what I've messed up, progres will be slow over the next few 
> days....
>
> The place to start is with the Machine Configuration dialog open and 
> watching the component pins
>
> When you issue a m6tX command you should be able to watch the iocontrol 
> pins as well and see the command processed
>
> good luck
>
>
> Mike
>
> On Monday, November 21, 2016 at 10:48:42 AM UTC, Schooner wrote: 
>>
>>
>> On 21/11/16 07:55, schoo...@btinternet.com wrote:
>>
>>
>> On 21/11/16 01:16, Mike Ross wrote:
>>
>> Schooner - Thanks for the pointer - I had missed that I needed to install 
>> the component. 
>>
>> I had to add the machinekit-dev packages to be able to run the comp 
>> --install toolchanger.comp
>>
>> Now when I run that I get the following errors:
>>
>> toolchanger.c:55:5: error: unknown type name 'bool'
>>        bool bEven;
>>        ^
>> toolchanger.c57:5:  error: unknown type name 'bool'
>>        bool bToggle;                       
>>        ^
>> toolchanger.c63:5:  error: unknown type name 'bool'
>>        bool bWarn;                       
>>        ^
>> toolchanger.c69:5:  error: unknown type name 'bool'
>>        bool fjog;                       
>>        ^
>> toolchanger.c71:5:  error: unknown type name 'bool'
>>        bool bjog;                       
>>        ^
>> I see that this is your original contribution - many thanks.  I hope I 
>> can get it working without being too much of a pain.
>>
>>
>> Yes I wrote this *many* years ago for Linuxcnc.  I still use it on the 
>> Boxford 240 lathe I wrote it for with Machinekit however, no reason to 
>> change what works.
>>
>> The bool issue is probably due to some changes in types introduced a 
>> while back, it can be got over simply by either defining bool, true, false 
>> etc or
>> using hal_bit_t
>> I think I defined them in instcomp to allow bool to be used in the main 
>> function, could just do the same to comp.
>>
>> I will look at it later and post an amended version which compiles with 
>> the current Machinekit.
>>
>>
>> I have changed the component to use hal_bit_t instead of bool.  
>> The #defines for true and false are already implemented in comp.
>>
>> I have also changed the other variables whilst I was at it.
>>
>> Params will become deprecated before too long in favour of i/o pins, 
>> since the only point of a param, was that you used not to be
>> able to create a pin with an initial default value, but now you can.
>>
>> Other variables should really be hal_typed, int should be either 
>> hal_s32_t or hal_u32_t depending upon the requirement, as an integer size 
>> can vary.
>> Likewise float should really be hal_float_t, which in fact is double, so 
>> that assignments are always correct
>>
>> This compiles for me so hopefully will get you going and you can fine 
>> tune the move values required between tools
>>
>> regards
>>
>>
>> -- 
> 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 machinekit+...@googlegroups.com <javascript:>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to