Advanced Search

While you wait for PCW to confirm when the 8i20 might be in stock:
You can use other drives to drive motors and still use the existing resolvers, but no idea what exactly would work for you, probably any "voltage mode" drive, and maybe "torque mode" will also work, but you should wait for someone else to chime in and confirm any of this.
I am sure LinuxCNC will work with any setup, not sure about cheap drives plastering all possible options on the label and later finding out they do only step/dir or only +-10V...although some +-10V should work if they do not explicitly require having a tacho attached.
This would mean using a Mesa 7i97T together with 7i49.
In the meantime some more info might help narrow things down, like motor voltage/current/power, resolver type/make/model (very important as i have resolvers that do not work with 7i49, yes i am unlucky as heck), brakes, tacho maybe, etc.

By providing detailed technical specifications for your servo amplifier and motor, you’ll significantly improve your chances of receiving an accurate answer.

Yes, the networking part, we were misled badly and chased our tails by having the laptop wired to the console while the network required for file transfers was at the back of the main electronics cabinet! That is 6 hours i will never get back! I kept wondering why W2K has an IP set and the Mazak software has another IP set...now i know.
So now it can be used properly with the laptop, but i would still like to be able to use it without the laptop attached since i already figured out how to copy stuff to it, so i will report the exact model when they get back from Germany in a few days.
Thank you very much for everything.

Is there a repository that currently is complete and works? I have been trying to get an installation working since March with no luck at all. I continually get errors about various components (LCEC, Boost, meson, etc) I have been able to get an "install" using the repository on this thread but it seems to lack full connection to the before mentioned components

Did you solve your problems with this machine?

Thank you, but I have already changed the plasmac component and got the result I wanted. I added a few lines:
   self.extJogXplusPin = self.h.newpin('ext_jog_x_plus', hal.HAL_BIT, hal.HAL_IN)
   self.extJogXminusPin = self.h.newpin('ext_jog_x_minus', hal.HAL_BIT, hal.HAL_IN)
   self.extJogYplusPin = self.h.newpin('ext_jog_y_plus', hal.HAL_BIT, hal.HAL_IN)
   self.extJogYminusPin = self.h.newpin('ext_jog_y_minus', hal.HAL_BIT, hal.HAL_IN)
   self.extJogZplusPin = self.h.newpin('ext_jog_z_plus', hal.HAL_BIT, hal.HAL_IN)
   self.extJogZminusPin = self.h.newpin('ext_jog_z_minus', hal.HAL_BIT, hal.HAL_IN)

   self.extJogXplusPin.value_changed.connect(lambda v: self.gui_button_jog(1 if v else 0, 'x', 1))
   self.extJogXminusPin.value_changed.connect(lambda v: self.gui_button_jog(1 if v else 0, 'x', -1))
   self.extJogYplusPin.value_changed.connect(lambda v: self.gui_button_jog(1 if v else 0, 'y', 1))
   self.extJogYminusPin.value_changed.connect(lambda v: self.gui_button_jog(1 if v else 0, 'y', -1))
   self.extJogZplusPin.value_changed.connect(lambda v: self.gui_button_jog(1 if v else 0, 'z', 1))
   self.extJogZminusPin.value_changed.connect(lambda v: self.gui_button_jog(1 if v else 0, 'z', -1))
It works great. 

At work we have a robot with a dead servo drive. The manufacturer is still around, and says that the original drives aren't available by any means. As far as I can tell, the motors are ordinary 3 phase brushless servos, but with resolvers. I can't find any industrial servo drives or systems that use resolvers. A few manufacturers list drives that can take input from a resolver, but of course they all say "call for quote" before I can get any information on the device.

I'm aware of the Mesa 7I49 resolver interface board, and the 8I20 PWM amplifier (which is out of stock). Are there any other industrial servo amplifiers that work like the 8I20?

This is a professional application: I am not going to screw around designing boards, nor will I consider hobby-grade hardware. I'd like the next person who needs to work on this machine to be able to do so.

Hi ...after finally getting a micro switch wired up for limit switch,,,light shows on/off on mesa7ip6s board,..hal meter shows working... but when I run axis and hit switch held in my hand....no change....keeps moving. been at his all day...I usually like to figure things out myself but now I am weary...grateful for some help if possible.

Thanks,

Rick

Put my PCB together! It works! Very happy to have moved on from breadboard to something more reliable!

"Key Error" means that the system is looking in the object returned by getWcsOffsets() call for an item that doesn't exist.

It looks like, for whatever reason, the getActiveWcsIndex() call is returning -1. There isn't a -1-th WCS, so it returns an error message.

This looks like qtPyVcp isn't handling the case when the apparent WCs is zero properly.

github.com/kcjengr/qtpyvcp/blob/main/src...c_datasource.py#L194

I think you should raise this as a bug:
. github.com/kcjengr/qtpyvcp/issues

Try this HAL component to map key events to HAL pins:

linuxcnc.org/docs/stable/html/man/man1/hal_input.1.html

Examples:
wiki.linuxcnc.org/cgi-bin/wiki.pl?Simple_Remote_Pendant

Perfekt! Danke
Funktioniert wie gewünscht.

For reference, my PCI motherboard (I have forgotten what it is, but that doesn't matter) in which I was using a Mesa 5i23 PCI card died.
I tried a PCIe to PCI adaptor in a DN2800MT motherboard running Debian Wheezy and it didn't work.

But when I tried an Asrock N100DC motherboard and Debian Bookworm it worked fine.

One of these (though the link will be dead in another 5 years)
www.amazon.co.uk/dp/B0CHM91KJB