Advanced Search

Hi Andy,

thanks a lot for your response. I will try it and buy the recommended MESA Board.

Yes, you are right, the tacho signal can be connected directly to the DC motor amplifier. I have only one amplifier for the 3 axes. So I can run them only in sequence.

I hope, I will find out how to interpret the inputs (TTL ?) from the Heidenhain EXEs.

Is there any chance to get connected to the LinuxCNC developer in Münster?

Best regards

Hartwig

Firehunter wrote:

Thanks for the replies. I guess updating Linux and LinuxCNC is the only option left.
 

Note that I don't actually expect that to fix this issue. 

Can you attach your HAL files(s)?

github.com/LinuxCNC/linuxcnc/commit/9783...cfdb5ea02cd0336145e6

I don't normally recommend PyVCP as it is not very flexible, but in this case it is probably a good choice.

linuxcnc.org/docs/stable/html/gui/pyvcp.html

The example panel in section 4.1 is very close, you would just swap the bar for a slider, and connect to stepgen.4.velocity-cmd instead of the spindle speed.

its easier if you use the threads we have stickied at the top.
unless the chip is a good clone, we dont support the GD line of clones. the lowcost hardware that will be the least trouble are the ones listed on the docs

You _probably_ don't need to take the tachos to LinuxCNC.

Typically the tachos connect only to the servo drives to feed back velocity, and the analogue voltage input from the controller sends a velocity command based on position feedback from the glass scales.

The Leinien FM1 looks like a lovely little thing.

An all-in-one solution from Mesa would be: store.mesanet.com/index.php?route=produc...id=397&search=analog
But there might be cheaper options (for example 6i24 + 7i33TA) but the 7i97T ethernet option will work with just about any supported computer, including the Raspberry Pi.

Other options exist. EtherCAT, Pico PPMC for example.

One of the LinuxCNC developers lives in Münster, I think.