Your tool error problem may be unrelated to the encoder issue.   I'd start by 
examining the clamping mechanism and related safety switches that tell the 
control that the tool is properly locked in position.

Todd Zuercher
P. Graham Dunn Inc.
630 Henry Street
Dalton, Ohio 44618
Phone:  (330)828-2105ext. 2031

-----Original Message-----
From: Leonardo Marsaglia <ldmarsag...@gmail.com>
Sent: Wednesday, April 10, 2024 1:06 PM
To: Enhanced Machine Controller (EMC) <emc-users@lists.sourceforge.net>
Subject: Re: [Emc-users] OT: Balluff BRGE1-WSE10 encoder

[EXTERNAL EMAIL] Be sure links are safe.

Found the main issue. The terminal block in wich the turret signals were 
connected is broken. Some of them were making contact. I isolate the terminals 
and now the no indexing problem is solved.

The only problem I have left to solve is why with some tools (like tool 8 for 
example) even if the indexing and clamping is done I get the tool error.

In any case, the plan of retrofitting the lathe to LinuxCNC is still going 
because I know this control will fail eventually.

El mié, 10 abr 2024 a las 14:03, Leonardo Marsaglia (<ldmarsag...@gmail.com>)
escribió:

> From what I could find in the manual of the lathe it works in plain
> binary. Now I'm trying to measure the signals.
>
> Here's a link to the encoder manual:
> https://mp-e/
> lektronik.de%2Fwp-content%2Fuploads%2F2020%2F07%2FMP-BA-BRGE1-...-K-SA
> 12-SA13-en.pdf&data=05%7C02%7Ctoddz%40pgrahamdunn.com%7C039cb05fb3184b
> 070ade08dc5980a365%7C5758544c573f47cebee96c3e0806fb43%7C0%7C0%7C638483
> 656245382475%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=b3jfy3th9jvvEbMqu
> LHia7TpNGJWsh3i70N17ENFMh0%3D&reserved=0
>
>
>
>
> El mié, 10 abr 2024 a las 12:51, andy pugh (<bodge...@gmail.com>)
> escribió:
>
>> On Wed, 10 Apr 2024 at 15:05, Leonardo Marsaglia
>> <ldmarsag...@gmail.com>
>> wrote:
>>
>> >
>> > It seems there is a pattern, but it's a pretty weird one.
>>
>>
>> Do you know if the output is binary or gray code?  Gray code is more
>> likely.
>>
>> encoder value
>>
>> 00 = 0000 = not used?
>> 01 = 0001 = good
>> 02 = 0011 = good
>> 03 = 0010 = good
>> 04 = 0110 = bad
>> 05 = 0111 = bad
>> 06 = 0101 = bad
>> 07 = 0100 = good
>> 08 = 1100 = wierd
>> 09 = 1101 = bad
>> 10 = 1111 = bad
>>
>> I am not seeing an obvious pattern, but it is likely that tool 1 =
>> encoder 0, so.
>>
>> Pocket number
>>
>> 01 = 0000 = good
>> 02 = 0001 = good
>> 03 = 0011 = good
>> 04 = 0010 = bad
>> 05 = 0110 = bad
>> 06 = 0111 = bad
>> 07 = 0101 = good
>> 08 = 0100 = wierd
>> 09 = 1100 = bad
>> 10 = 1101 = bad
>>
>> OK, still not seeing it...
>>
>> Straight binary?
>>
>> pocket
>>
>> 01 = 0000 = good
>> 02 = 0001 = good
>> 03 = 0010 = good
>> 04 = 0011 = bad
>> 05 = 0100 = bad
>> 06 = 0110 = bad
>> 07 = 0111 = good
>> 08 = 1000 = wierd
>> 09 = 1001 = bad
>> 10 = 1011 = bad
>>
>> Hmmm.... We really need the encoder output scheme, rather than guessing.
>>
>> --
>> atp
>> "A motorcycle is a bicycle with a pandemonium attachment and is
>> designed for the especial use of mechanical geniuses, daredevils and 
>> lunatics."
>> - George Fitch, Atlanta Constitution Newspaper, 1912
>>
>> _______________________________________________
>> Emc-users mailing list
>> Emc-users@lists.sourceforge.net
>> https://lis/
>> ts.sourceforge.net%2Flists%2Flistinfo%2Femc-users&data=05%7C02%7Ctodd
>> z%40pgrahamdunn.com%7C039cb05fb3184b070ade08dc5980a365%7C5758544c573f
>> 47cebee96c3e0806fb43%7C0%7C0%7C638483656245392287%7CUnknown%7CTWFpbGZ
>> sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
>> 3D%7C0%7C%7C%7C&sdata=MRgeEAFeEsT1ZlaPr0gFywDb%2FZeQdSPNo9b32MtZ0q8%3
>> D&reserved=0
>>
>

_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to