New ethercat / probe basic control for minimonster

so its not talking to my delta vfd either... so im guessing its not the vfd side thats the issue. hmm

maybe  www.com-port-monitoring.com/ or similar?

Hmmm. that's helpful thanks. its doing... something in both directions. so maybe the issue is the spindle talker 2 software.

Any advise on another way to check functions?

So, its definitely doing something different when the drive is on vs off. So that's a start. It does show exception 1 a fair bit.


[27/10/2025 15:29:13]
Modbus Response (COM5)
Address: 1
Function: 4 (0x04) - Read Input Registers
Exception Code: 1
Checksum: 0x82c0 - OK

---

[27/10/2025 15:29:13]
Modbus Request (COM5)
Address: 1
Function: 1 (0x01) - Read Coils
Starting Address: 773
Quantity: 0
Checksum: 0x2c4f - OK

---

[27/10/2025 15:29:13]
Modbus Request (COM5)
Address: 1
Function: 1 (0x01) - Read Coils
Starting Address: 779
Quantity: 0
Checksum: 0x4d8c - OK

---

[27/10/2025 15:29:13]
Modbus Request (COM5)
Address: 1
Function: 1 (0x01) - Read Coils
Starting Address: 912
Quantity: 0
Checksum: 0x3c63 - OK

can someone walk me through the setup on linuxcnc for this? i am seeing so many conflicting and incomplete instructions and components that are no longer supported or redundant (like vfdmod).

Doesn't qualify as walk through but here are some hints. I used mb2hal.

forum.linuxcnc.org/10-advanced-configura...h100-inverter#335652

Thanks. Problem is I don't really know what to do with this.

Inching my way foreward.
Have a hal and ini for modbus now, and im getting an "out of range" error.

This happens if the drive in on or off, and im seeing no leds on the adapter. so perhaps the adapter is not enabled? Does it require a driver?

The chip on the adapter is CH340

I found a hal and ini for a parker drive and commented out errors until it made it through and booted linuxcnc and had flashing lights on tx and rx. So we now have communication. Of course its all wrong cause its for a different VFD, but the communication is actually working.

Woo.

This is proving difficult to debug. I get the same transaction error regardless of whether the drive is plugged in, however when it is plugged in, it does go into run model. So something is working. It will not however turn back off or respond to M3/m5 commands.

What should i be looking at next?