Advanced Search

Das hier wäre meine Version mit dem geklautem Code aus dem Forum:



########################################
# 7i73/7i75 hal connections for the MPG#
# von Norbert Schechner kopiert #
########################################

# Here the mpg counts are connected
net jog-wheel-counts joint.0.jog-counts <= hm2_7i796s.0.7i73.0.0.enc0.count
net jog-wheel-counts joint.1.jog-counts
net jog-wheel-counts joint.2.jog-counts
net jog-wheel-counts axis.x.jog-counts
net jog-wheel-counts axis.y.jog-counts
net jog-wheel-counts axis.z.jog-counts

# we need a mux component to select the step increments
loadrt mux2 names=jog-mode-sel
addf jog-mode-sel servo-thread

net jog-scale-out jog-mode-sel.in0 <= gmoccapy.jog.jog-increment
# my default on continious jogging is 0,05 mm / count
setp jog-mode-sel.in1 0.050

# need to get the jog mode
# Mode 0 all steps will be done, Mode 1 joint will stop as soon as you stop spinning the mpg
net jog-vel-mode gmoccapy.jog.jog-inc-0 <= jog-mode-sel.sel <= hm2_7i796s.0.gpio.041.in
net jog-vel-mode joint.0.jog-vel-mode
net jog-vel-mode joint.1.jog-vel-mode
net jog-vel-mode joint.2.jog-vel-mode
net jog-vel-mode axis.x.jog-vel-mode
net jog-vel-mode axis.y.jog-vel-mode
net jog-vel-mode axis.z.jog-vel-mode

# already connected cont_joging on jog vel mode selection
# here we connect the physical buttons to select the jog increment
# net jog_cont gmoccapy.jog.jog-inc-0 <= hm2_7i76e.0.7i73.0.1.input-07
net jog_1000 gmoccapy.jog.jog-inc-1 <= hm2_7i796s.0.gpio.042.in
net jog_0100 gmoccapy.jog.jog-inc-2 <= hm2_7i796s.0.gpio.044.in
net jog_0010 gmoccapy.jog.jog-inc-3 <= hm2_7i796s.0.gpio.046.in
# net jog_0001 gmoccapy.jog.jog-inc-4 <= hm2_7i796s.0.gpio.041.in

# This is to change between jog modes 0 and 1
net jog_scale-out joint.0.jog-scale <= jog-mode-sel.out
net jog_scale-out joint.1.jog-scale
net jog_scale-out joint.2.jog-scale
net jog_scale-out axis.x.jog-scale
net jog_scale-out axis.y.jog-scale
net jog_scale-out axis.z.jog-scale

# this is to enable the selected joint / axis
net jog-x-enable joint.0.jog-enable <= hm2_7i796s.0.gpio.034.in
net jog-x-enable axis.x.jog-enable
net jog-y-enable joint.1.jog-enable <= hm2_7i796s.0.gpio.036.in
net jog-y-enable axis.y.jog-enable
net jog-z-enable joint.2.jog-enable <= hm2_7i796s.0.gpio.038.in
net jog-z-enable axis.z.jog-enable

# Buttons START PAUSE STOP mit Gmoccapy

net Button_Start gmoccapy.h-button.button-2 <= hm2_7i796s.0.gpio.035.in
net Button_Pause gmoccapy.h-button.button-4 <= hm2_7i796s.0.gpio.037.in
net Button_Stop gmoccapy.h-button.button-3 <= hm2_7i796s.0.gpio.039.in

See also Mesa 7i96S and 7i76E and 7i95 and many other combos, but for a start 7i96S is the easiest to wire and quite cheap.

Itś all good now. Thanks

1. USB-LAN adapters should not be used on production machines, USB has inherent latency issues
2. from your explanation it seems like interference issues, so is the machine and PC properly grounded?

Hello,
I get the error mentioned when a milling operation has run to completion or when I stop an operation with the stop button.
I have attached some pictures. My Mesa card is connected to a USB-LAN adapter.
Thank you very much for your help.

I just switched MESA connection from the USB-LAN adapter to the intern LAN adapter and the error is gone... the reason i didn´t take the intern LAN was my post monthś ago forum.linuxcnc.org/9-installing-linuxcnc...to-connect-to-github but now it also works.

ok, I made the sink configuration for output01 with setp now within custom.hal:
hm2_7i76e.0.7i76.0.0.output_source 0xFFFD
setp hm2_7i76e.0.7i76.0.0.output_sink 0x0002
-> works as expected, thanks a lot

Apologies for reviving this old topic but found a mistake on the diagram that may generate a lot of frustation to anyone trying to use it.

Pin AI3 is missing, so all other digital input pins from so on are displaced 1 position.

Unfortunatelly even if moderators delete the link in both  #98901  and  #112565  on the forum, the diagram is still appearing as one of the first searchs on search engines. Not sure if OP has a way to change the picture on his cloudfront account.
 

Aahh shoot! I was hoping to avoid resoldering my DIY pullup resistor board. But thank you for the explanation.

The 7I76EU inputs have a threshold of 60% of VFIELD when going positive and 40% of VFIELD when going negative.
This means with 24V VFIELD, a voltage below 9.6V is read as low and a voltage above 14.4V is read as high.
This  is called hysteresis, and is deliberate behaviour for noise immunity. With a 10 K pullup you end up just in the middle
of this input threshold range, You need a stiffer pullup resistor (say 2.2K) so that you have a valid input to the 7I76EU.

I am pretty sure that you are correct, at least in the part about the inputs being reversed between the two boards.
But it is my understanding that this is why the pull-up resistor is needed, so that the input at idle is 12v and then when activated goes to 0. So to get the correct logic in linuxcnc I use the xxx-not input signal.

But I don't understand why the hal state doesn't change after the first trigger, even though I can see the voltage change on the input pin.

Wait until  someone else confirms but I think your issue is that the  Mach3 board senses on the negative side and the 7i76e senses on the positive side. In other words on the 7i76e, you need to switch the input to +24 volts not GND

Read page 24 of the Mesa manual.

Hi,

I am trying to convert my DMC2 Mini from the chinese Mach3 board it came with, to LinuxCNC via a Mesa 7i76eu. And I have most of it working by now But I am having an issue with two simple inputs.

I have two probes, a hight pug and a xy probe, that basically just connects to GND when triggered. They are connected to the mesa with a 10kOhm pull up resistor. This is what I am seeing when I power the machine on:
- The input pin on the Mesa card reads 12v and the input is as expected high/true in hal show
- I then trigger the probe and the input pin now reads 0v, and the input is low/false in hal show
- After I "release" the probe the input pin returns to 12v, BUT the input remains low/false in hal show

Any ideas why the input in hal doesnt return to high when the pin reads 12v with a multimeter
Field power is 24v, and all voltage readings are done between field GND and the input pin.

Thanks in advance

net joint.X.amp-fault-in hm2_7i76e.0.7i76.0.0.input-16-not
etc...

Do U replace this section
# HLFB is true when enabled *and* following
net hlfb_x  hm2_7i76e.0.7i76.0.0.input-16-not 
net hlfb_y  hm2_7i76e.0.7i76.0.0.input-17-not
net hlfb_y2 hm2_7i76e.0.7i76.0.0.input-18-not
net hlfb_z  hm2_7i76e.0.7i76.0.0.input-19-not
net hlfb-a  hm2_7i76e.0.7i76.0.0.input-20-not

With net joint.X.amp-fault-in whatever_input_pin

? Thanks 

Just as a general thought, no GUI configurator can fully support the 7I76EU
(or any other hardware) , though I think MesaCT does support the output options.

In all but the simplest cases, some hand editing of hal/ini files is likely to be needed
and considerable hal customization will be needed for functions like tool changers,
spindle orientation, jogging options etc etc.