Advanced Search

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.

Thank you. I'll learn. And ask there if don't catch something.

Thank you very much MaHa!

This worked. Initially with (debug,#5230) I got -0.012195. After G10 L2 P1 R0 it was reset to 0. Perfect. So there was a rotation active? Maybe a leftover from when I probed rotation of a workpiece?

PDI = that parallel communication mode? Noone uses it. Everyone uses SPI.
The last few lines in the xml file should look similar to this. The first "80" means spi, then there
is polarity and other settings. Read out the eeprom from the board and verify that is says "80" in the first byte.
I have had my fair share of problems with SPI so I think you again should verify that you can get past the ESC_init() function.
Use the debugger and verify that you read 0x87654321 from LAN9252 on line 445 in the figure
 
You may need to power cycle the LAN9252, it only reads eeprom after power down.
 

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.

I managed to get spi working but I might have an issue with the eeprom. Apparently I'm stuck in PDI mode and lan9252 is not communicating through spi

I asked Grok:
the official linuxcnc Ethercat driver at github.com/linuxcnc-ethercat/linuxcnc-ethercat does not currently support EoE (Ethernet over Ethercat) drives such as the SV660N drive. Can you suggest modifications to the code to enable EoE support?
And he gave a very comprehensive answer.

Its far to comprehsensive to share on the forum due to formatting but I saved hos answer to markdown and converted to pdf which is attached

 

Sorry to bust you AI bubble but

1. where is  eoe_running defined?
2. where is *arg used?
3. the for statement seems invalid.

I find Grok lies less than ChatGPT but still gives me wrong code sometimes.
 

I spent some time with ChatGpt and I'm of course super skeptical to those tools.
Chatgpt says the likely reason for EoE drives to hang is that the EoE mailbox isn't serviced/emptied.
Yes, it isn't. Maybe one can try that, it doesn't have to be more advanced. A code snippet that does that
There is that ecrt_master_send kworm talked about. It's about principles at this point.
I would need a slave with EoE. I don't have that. Maybe maybe I can make one, there
is an example in SOES with lwip. Or anyone know of a not too pricey servo drive with EoE?

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

Verify that the slave has the entered PDOs with "ethercat -p 2 pdos"
Check syslog for any messages, last lines of "sudo dmesg"
If that doesn't give anything, add debug messages "ethercat debug 1"
 restart ethercat master, start linuxcnc and check syslog again for any helpful output.

In MDI:  (debug,#5230)  to see if there is a rotation around Z. To reset   G10 L2 P1 R0

I think the problem is that the joints are supposed to have numbers, not letters.

Like 

joint.0.amp-fault-in

I just realized you haven't created a signal name, just linked two pins.  Because your joint.(lettter).amp-fault-in pin doesn't actually exist, LCNC is creating a SIGNAL named joint.(letter).amp-fault-in.

That's why you aren't getting an error at startup.

Try this

net x-fault joint.0.amp-fault-in hm2_7i96s.0.inm.00.input-1-not

and so on for the others.
 

Thanks so much! I used to know that, but totally forgot it this project. For once I started a project without first reading the mesa manual from cover to cover... my error has come to light.