New Eagle Conversion
13 Feb 2017 00:37 - 13 Feb 2017 01:12 #87892
by lakeweb
Replied by lakeweb on topic New Eagle Conversion
I've tested the encoder inputs and they work fine. This encoder interfaces just like the glass on the table.
I'm watchdog timing out and still not sure how to set that up. But now I'd like to move the machine and see the servo voltages before I take this back to the shop and really move the machine.
I've got a volt meter on pin 2 and 3 of TB5. ( ENA0+, GND ), but it looks like all I'm getting is a floating pin. I have run the code and expect to see voltage to drive the servo. Yes, I know I will get a joint following error if I don't get the encoder to fake it out, but I'd like to know if I'm on the right track.
I'm watchdog timing out and still not sure how to set that up. But now I'd like to move the machine and see the servo voltages before I take this back to the shop and really move the machine.
I've got a volt meter on pin 2 and 3 of TB5. ( ENA0+, GND ), but it looks like all I'm getting is a floating pin. I have run the code and expect to see voltage to drive the servo. Yes, I know I will get a joint following error if I don't get the encoder to fake it out, but I'd like to know if I'm on the right track.
Please Log in or Create an account to join the conversation.
14 Feb 2017 02:55 #87937
by lakeweb
Replied by lakeweb on topic New Eagle Conversion
Hi Tom,
Thanks. The servo amp set had just one 24 volts to sink that would power it up, at least, the best that I could find while tracing wires while the amp was on the bench. So I used an e stop to break that sink.
At first my hand was so ready to slap that thing. I got side tracked for a lot of the day but the servos are up and running! I'll have to use a dial indicator to be sure the glass is 5um, but a measuring tape say it is so. I still have a lot to learn and do. I can't move faster than 5 ipm without a joint error. And I'll have to trim the zero because there is about a 2 second pulse as the servo bounces off the encoder. It does run smooth while moving. I need to spend an uninterrupted day out there to dress wires and get the limits and M stuff hooked up.
Best, Dan.
Thanks. The servo amp set had just one 24 volts to sink that would power it up, at least, the best that I could find while tracing wires while the amp was on the bench. So I used an e stop to break that sink.
At first my hand was so ready to slap that thing. I got side tracked for a lot of the day but the servos are up and running! I'll have to use a dial indicator to be sure the glass is 5um, but a measuring tape say it is so. I still have a lot to learn and do. I can't move faster than 5 ipm without a joint error. And I'll have to trim the zero because there is about a 2 second pulse as the servo bounces off the encoder. It does run smooth while moving. I need to spend an uninterrupted day out there to dress wires and get the limits and M stuff hooked up.
Best, Dan.
Please Log in or Create an account to join the conversation.
16 Feb 2017 21:16 - 16 Feb 2017 21:18 #88074
by lakeweb
Replied by lakeweb on topic New Eagle Conversion
Hi Peter,
Thanks. By searching on 'axis.0.pos-lim-sw-in' I found some stuff. And it seems that this thing is wired with double pole lines such that:
net lim_out_x <= hm2_[HOSTMOT2](BOARD).0.7i77.0.0.input-00-not
net lim_out_x => axis.0.pos-lim-sw-in axis.1.pos-lim-sw-in axis.2.pos-lim-sw-in
Does what I need. the other two lines are also hooked to the switches and without further digging I'll assume that is how you figure which switch actually got hit.
But where do the likes of 'axis.0.pos-lim-sw-in' get described for what they actually do? I've only found it in examples.
When I tuned up before I did not let the table get to full speed and settle. Now with the max rate turned down, I get:
The error just keeps building and I'll eventually trip a joint follow. I'm not sure how this gets fixed. And you can see the drift and corrections before the move. I am trying to be sure it is not some kind of ground loop on my side. BIAS has no effect and when linuxcnc is not powered, there is no drift.
Also, when at 1m per division does this translate to .001 inches?
Thanks. By searching on 'axis.0.pos-lim-sw-in' I found some stuff. And it seems that this thing is wired with double pole lines such that:
net lim_out_x <= hm2_[HOSTMOT2](BOARD).0.7i77.0.0.input-00-not
net lim_out_x => axis.0.pos-lim-sw-in axis.1.pos-lim-sw-in axis.2.pos-lim-sw-in
Does what I need. the other two lines are also hooked to the switches and without further digging I'll assume that is how you figure which switch actually got hit.
But where do the likes of 'axis.0.pos-lim-sw-in' get described for what they actually do? I've only found it in examples.
When I tuned up before I did not let the table get to full speed and settle. Now with the max rate turned down, I get:
The error just keeps building and I'll eventually trip a joint follow. I'm not sure how this gets fixed. And you can see the drift and corrections before the move. I am trying to be sure it is not some kind of ground loop on my side. BIAS has no effect and when linuxcnc is not powered, there is no drift.
Also, when at 1m per division does this translate to .001 inches?
Please Log in or Create an account to join the conversation.
Moderators: cncbasher
Time to create page: 0.103 seconds