Hurco Hawk 5M Retrofit w/ existing motors

More
8 years 6 months ago #108838 by biqut2
Here it is. I save it as GTKBuilder format, I read somewhere that the other files format is depreciated and its recommend to just not use it. That is unless I got that backwards. As a side note, I just stumbled across gmoccapy. Actually I don't know how I missed it on the list of included UIs, Its almost exactly what I was wanting in the first place. I may just experiment with adding extra pages/tabs to it for probing and my toolbox cycles.

File Attachment:

File Name: test.glade
File Size:7.35 KB

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

More
8 years 6 months ago #109003 by biqut2
Well, I've got the mesa cards, set the jumpers and flashed with the 7i77x2 firmware, applied 24vcd for field voltage, tested the cards via cli. I've been determining all of the pinouts and relative connections on the servo drive and motors. I've read a few other threads on here as well as some I found via google. I can see where I need to hook up encoder a and b and then the differential output on the 7i77. I'm not sure what to do with the tach signal from the motor, z encoder or brake. Does LinuxCNC make use of these out of the box or does it require me to do a lot of extra work to implement?

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

More
8 years 6 months ago - 8 years 6 months ago #109005 by PCW
Typically LinuxCNC does not deal with the tachometer outputs, as these are normally
connected to the motor drives for velocity feedback.

The Z encoder signal is the encoders index channel and connects to the 7I77 index input

If the motors have mechanical brakes you will first need to find how these are driven.
Brakes are often take considerable current so its not likely they can be driver directly by
7I77 outputs.

The hal side of brake control is often somewhat involved because you must typically
release the brakes about 100 ms before you enable the drives to avoid getting a drive fault.
Last edit: 8 years 6 months ago by PCW.

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

More
8 years 6 months ago #109008 by biqut2
In that case, then I won't worry about the brakes, at least not at this point. Just want to get operational first. For what its worth when I first opened the electrical cabinet on this machine the tach wire going from the x motor to the x drive was cut and zip tied to the other wires next to it. It was obvious that some had deliberately done this. I may be completely wrong but this led me to believe the tach feedback wasn't 100% required. So my connections would be as follows:

- Servo Pins -
Signal - Pin - Connection
Va1 - A - 7i77 qa0
Va1 - B - 7i77 qa0
Va2 - C - 7i77 qb0
Va2 - D - 7i77 qb0
Va0 - E - 7i77 idx0
Va0 - F - 7i77 idx0
Motor Earth - G - Ground/Earth
+5V - H - 5vdc power supply positive
0V - I - 5vdc power supply negative
B+ - J - brake unconnected
B- - K - brake unconnected
Shield - L - connected to cable shielding
T2- - M - tach unconnected
A2- - N - servo drive negative
T1+ - O - tach unconnected
A1+ - P - servo drive positive

- Servo Drive -
aout0 from the 7i77 and the gnd pin will connect to the drives diff sig in pins to provide the +-10vdc

If I hook all of this up I should be able to start the PID tuning process correct?

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

More
8 years 6 months ago - 8 years 6 months ago #109009 by PCW
The original drive --> motor cabling should connect the tachometer to the drives
If the drives were setup for velocity mode (which is very likely) they _require_
tachometer feedback or they will not be controllable.

Also note that you should absolutely expect runaways (and running into hard stop and breaking things or hurting peole)
and so, its much safer to do initial tests with the motors disconnected from the linear axis.

The first thing you should get working on the servo drives is the enable logic
(so LinuxCNC can enable/disable the drives) This is a safety issue.

Regarding brakes, typically the motor will be locked unless the brake is powered
so if you do actually have brakes on the motors, the shafts will be locked with power off
(often brakes are only used on the Z axis to avoid coasting into the table when power is off)
Last edit: 8 years 6 months ago by PCW.
The following user(s) said Thank You: biqut2

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

More
8 years 6 months ago - 8 years 6 months ago #109010 by biqut2
Tha makes sense about the way the brakes are applied. I can confirm that with the power disconnected I can rotate each of the motors by hand, including the Z. The machine has belt reduction on all three motors too. I fully expected the runaways, I've got the motors off the machine and strapped down on the bench for testing. the drives are bolted onto a frame that included the DC power supply. It has the 3 drives with a connector on each for the diff signal, tach signal, and limit switch inputs. There is also power connection to each of the servos, Pins N and P. There is a single 24vdc controlled relay on the frame of the unit that interrupts the 115vac coming into the power supply. It appears as though this want meant to enable/disable the drives. After looking through the documentation I was sent from servo dynamics it does show that each of the drives has a pin to enable/disable it externally, however, it's not being used. I'm not sure If I should deviate from the "stock" wiring and connect these pins to an estop circuit or just rely on the relay that already there being controlled by the estop circuit.

Edit: the machine has a pneumatically actuated mechanical brake on the Z.
Last edit: 8 years 6 months ago by biqut2. Reason: addition information

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

Time to create page: 0.361 seconds
Powered by Kunena Forum