Convert from Anilam Crusader M to EMC 2

More
08 Jan 2013 00:14 #28452 by BigJohnT
If we put a sticky about machine conversions with links do you think it would help?

John

Please Log in or Create an account to join the conversation.

More
08 Jan 2013 00:22 #28453 by cmorley

If we put a sticky about machine conversions with links do you think it would help?

John


Sorry to hijack the thread a bit...

Yes John a very good idea - but lock it and you decide which conversion write-ups are high quality enough to be there.
We could use a couple more high quality write-ups like that. I think the fact they wrote it when the had little EMC2 experience helps.
I think any of our developers or power users would tend to forget to make the little mistakes,,, :)

Chris M

Please Log in or Create an account to join the conversation.

More
08 Jan 2013 02:36 #28469 by ryankracht

Ahh yes the red one. This is definitely square wave TTL output. I have some of these. I just can't remember the resolution.
IIRC the color is a clue of the resolution (red orange and green I have)

While TTL output means it's easy to connect to, it also means you can't improve the resolution - aside from replacing them.

Chris M


Chris, the info I found shows that this is a 10 micron (.0004") encoder. From reading through other threads, it sounds like some have had difficulty tuning EMC with this "coarse" of an encoder. I do like the fact that it is measuring true position, and thus reducing the impact of backlash somewhat. Any advice regarding the likelihood of success with this resolution?

Ryan

Please Log in or Create an account to join the conversation.

More
08 Jan 2013 04:30 #28472 by cmorley
Well I don't have a lot of practical experience. I did some testing with a linear encoder only but it was a much higher resolution.
It was a heidenhain analog sine wave output that could be interpolated ( 5 fold in my case )

From what I have read a rough rule of thumb is minimum 5 times finer then what resolution you want.
Bottom line is You have it so try it. You always add encoders to the motor or ball screw later.
Hopefully you have very minimal backlash. Backlash will be more of a problem with the linear encoder then the resolution I think.

Other with more experience will surely advise you soon....

Chris M

Please Log in or Create an account to join the conversation.

More
08 Jan 2013 04:54 #28475 by andypugh

From what I have read a rough rule of thumb is minimum 5 times finer then what resolution you want.

Do the motors have tachometers?
The LinuxCNC PID component has in input from a separately-derived velocity pin. It ought to be possible to drive that via an analogue-to-digital stage.
The 7i77 has the option to use some pins as low-resolution analogue inputs.
You might have to do something excessively cunning such as derive high-speed data from encoder count delta and low-speed velocity data from tachs and A to D, with HAL arbitrating the switchover. (simple addition it probably fine, with the scales correctly set)

Please Log in or Create an account to join the conversation.

More
08 Jan 2013 04:57 #28476 by ryankracht

From what I have read a rough rule of thumb is minimum 5 times finer then what resolution you want.

Do the motors have tachometers?)


Yes

Please Log in or Create an account to join the conversation.

More
08 Jan 2013 18:16 #28492 by Rick G

I do like the fact that it is measuring true position, and thus reducing the impact of backlash somewhat


Good point, however it was my understanding that using linear scales with an axis that does have too much backlash would make the servo tunning difficult, which was the reason to add encoders.
Perhaps Andy is onto something with the tach signal.

Rick G

Please Log in or Create an account to join the conversation.

More
09 Jan 2013 07:09 #28503 by ryankracht

The 5i25 / 7i77 combo might work better for that conversion now, though the 5i23 / 7i33 setup used there is still good and potentially more adaptable.
(I have a 5i23 in my milling machine, and I am using a wierd mix of hardware, resolvers, encoders, smart-serial)


Guys, I will address this question to the Mesa guys, unless you have this information readily available, but why is 5i23 / 7i33 more adaptable?

Why the 5i25 / 7i77 if I will never use 6 axis, why not 5i25 / 7i33?

Please Log in or Create an account to join the conversation.

More
09 Jan 2013 07:44 #28505 by andypugh

Guys, I will address this question to the Mesa guys, unless you have this information readily available, but why is 5i23 / 7i33 more adaptable?

PCW is the Mesa guy. I just write some of the drivers.
Because the 5i23 has more pins, you can attach more stuff, and a bigger variety.
There are resolver boards and brushed/brushless/stepper motor boards that connect directly to the 5i23 style FPGA cards.

Why the 5i25 / 7i77 if I will never use 6 axis, why not 5i25 / 7i33?

You can't connect a 7i33 to the 5i25. The 5i25 has a 25-pin D-sub connector, and the 7i33 has a 50-pin box header.
(actually, with the right adaptor cable it could probably be made to work, but would need special firmware).

Please Log in or Create an account to join the conversation.

More
09 Jan 2013 23:52 #28520 by ryankracht

The 7i77 has the option to use some pins as low-resolution analogue inputs.


Ok. Does the 7i33 have that option as well?

or am I better off using a 3rd board dedicated to A/D for a high resolution conversion?

The 5i25 / 7i77 combo might work better for that conversion now, though the 5i23 / 7i33 setup used there is still good and potentially more adaptable.


My thoughts are that the 5i25/7i77 seems like it meets my requirements to bring in my glass scales (encoders) and output the +/-10V back to the drives, Andy references that the 7i77 will give me the ability to bring in the tachs as well, so I am not sure what other flexibility I would need. Any other thoughts on why I should still consider the 5i23 / 7i33?

Please Log in or Create an account to join the conversation.

Moderators: cncbasher
Time to create page: 0.095 seconds
Powered by Kunena Forum