Advanced Search

Been reading this for while, I think you need to reassess what you think you know compared to what you actually know.
Usually the stepper drivers are pretty hardy, the ones I have in my mill are about 15 years old and haven't missed a beat.
I've never heard of anyone having to make modifications.
Some of the early TB6600 drivers weren't as reliable as they should have been, no experience with them myself but many reports of them being that way.
So just settle down, do things the recommended way and don't try to modify things that don't require modification. And if you still insist of doing board level mods consult the data sheets for the components that will be affected. I'm sure this would have resolved the issue of "no flyback diodes".

Yes, I am using GMOCCAPY UI, but I have just checked QTDragon_HD, and it looks really cool! I might be tempted to make a switch at some point. I am completely new to LinuxCNC, got it all up and running last week after pulling my hair out after experiencing multiple bugs with Mach3 and EC300(digital dream) controller. I have to say I am super happy, LinuxCNC is soooooo much better than Mach3.

switched to the second one which i thought was the wifi.. now it says link up. still no slaves though

Master0
Phase: Idle
Active: no
Slaves: 0
Ethernet devices:
Main: 60:36:dd:54:7b:49 (attached)
Link: UP
Tx frames: 488
Tx bytes: 29280
Rx frames: 0
Rx bytes: 0
Tx errors: 0
Tx frame rate [1/s]: 124 34 6
Tx rate [KByte/s]: 7.3 2.0 0.4
Rx frame rate [1/s]: 0 0 0
Rx rate [KByte/s]: 0.0 0.0 0.0
Common:
Tx frames: 488
Tx bytes: 29280
Rx frames: 0
Rx bytes: 0
Lost frames: 488
Tx frame rate [1/s]: 124 34 6
Tx rate [KByte/s]: 7.3 2.0 0.4
Rx frame rate [1/s]: 0 0 0
Rx rate [KByte/s]: 0.0 0.0 0.0
Loss rate [1/s]: 124 34 6
Frame loss [%]: 100.0 100.0 100.0
Distributed clocks:
Reference clock: None
DC reference time: 0
Application time: 0
2000-01-01 00:00:00.000000000

network ip/mac


1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:3e:1b:ba brd ff:ff:ff:ff:ff:ff
altname enp0s25
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 60:36:dd:54:7b:49 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.194/24 brd 192.168.2.255 scope global dynamic noprefixroute wlp2s0
valid_lft 257328sec preferred_lft 257328sec
inet6 fe80::6236:ddff:fe54:7b49/64 scope link noprefixroute
valid_lft forever preferred_lft forever

only one network port on this machine plus the wifi for the internet.
I *think* im using the right one. haha. I dont see how i cant be.

dmesg spits out 10000 things. last one mentions lan at 100base though

Mac address and generic driver.
Two network interfaces and you picked the wrong one? Has never happened to anyone...
Ethercat master prints in /var/log/messages. Have a look there or at the end of the huge output of "sudo dmesg" for signs of why it won't use the network interface