Advanced Search

Probably about a 90% chance that replacing U22 will fix the issue.

But the issue  likely re-occur if a breakout is not  added and the same drives/wiring are used.

The direct FPGA outputs on P2 are not really designed for field wiring which may have large EMI coupled
from drives, VFDs etc

The question is whether the drives can do preset velocity with no commutation.

So does this mean that the BLDC module doesn't output commutation before/during the startup indexing procedure? If commutation outputs are suppressed before index pulse is found I may have a problem. I was thinking that it could output them, even if they were off by a little, and hopefully it wouldn't jostle the motor around too much. 

The voltage is about 4V only on one contact of the three connected axes, on the others it is about 1.2V / 1.6V
What are my chances of restoring functionality by replacing the U22?

I'll see if I can find a better power supply

As I mentioned before, If you ever see CR7 illuminated it means power failure.
Power failure on a 7I96S means the 3.3V supply has dropped below about 3V.
This in turn means that the 5V power has dropped below about 4V (even for a few ms)

 

Did you check a DIR pin with a voltmeter? (when jogging both directions)
A voltage reading would be the most helpful for debugging

Another way to check for U22 damage is to measure the voltage
across C111 (on left side of U22) It should be close to 4V
If much lower it indicate that U22 has been damaged.


P2 is the only way to add step/dir outputs to a 7I97/7I97T

 

Thst is possible I suppose. I am using a charging block and a modified usb cable to provide power. its measuring 5.1 volts but I can't figure out how many amps.

I tried connecting a simple stepper motor. There is no rotor movement at all. Most likely, the problem remains in the board itself. Since the board has already worked before and I understand how it should function, the issue is not in the software part. The question is very important for me — is it possible to connect the extension boards you suggested not through the Mesa board’s P2 expansion port, but through its TB4? Because most likely, any extension board connected through the faulty P2 port will produce the same result.

In the Pncconf wizard? yes I changed it to 10.10.10.10
ip a returns
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 90:b1:1c:8d:36:5f brd ff:ff:ff:ff:ff:ff
altname enp0s25
altname enx90b11c8d365f
inet 10.10.10.11/8 brd 10.255.255.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::147c:8a67:beeb:e22a/64 scope link noprefixroute
valid_lft forever preferred_lft forever

What does
ip a
in a terminal return?
Also, did you set the IP to 10.10.10.10 in the wizard? By default it is at 192.168.1.121

if you get CR7 (/DONE) illuminated at any time after initial power on,
you likely have a marginal 5V supply. (CR7 is only illuminated during a
power on reset)

let me start by saying Hi and I am very new to linux and linuxcnc.
I've been trying to 2 days to get mesa mesa 7i96s to connect to linuxcnc. 
I am running debian 13 Xfce and I have kernel-vers -v: #1 SMP PREEMPT_RT Debian 6.12.48-1 (2025-09-20)
I have wired connection 1 Ipv4 set to manual and address set to 10.10.10.11 (routes set to use this connection only for resources on its network)
On the 7i96s I have the jumper set for eeprom. 
I can ping the card at 10.10.10.10 and it appears to respond (yellow power led and green users leds lit)

but when I to launch my config file I get red led's on cr6 and cr7
and linuxcnc shuts down and gives this debugging 

Note: Using POSIX realtime
hm2_eth: rtapi_app_main: Resource temporarily unavailable (-11)
./7i96s.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./7i96s.hal:9: /usr/bin/rtapi_app exited without becoming ready
./7i96s.hal:9: insmod for hm2_eth failed, returned -1
1868
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

I am not sure what I am missing...
 

All i have left is 5 of Voron 2.4R2 and a single Creality CR-5 PRO, so none have multi material support, and i am in no rush to modify any, but yes i have seen that and it is easy to do when the bottom is flat even on single extruder machines.
I never needed multi color, either, but yes sometimes i wish i had already modified one of the Voron's, maybe someday when i get old ... hmm older...

I was just wondering when the RP2040 version of Remora might be updated to use the new Remora-core code?  I'm working on designing a new board using an RP2354.  It won't be ready for awhile yet but with winter coming I should have some more time to work on it.

C|

I think that the problem is with your fancy logic for converting the unidirectional spindle sensor into a directional one.

I am not sure that the logic will work as you hope, as the encoder won't change direction the instant that the motor direction reverses, it takes some time to reverse a spindle. (if you always stop it first, them it's probably fine).

You only need a bidirectional encoder on a lathe for rigid tapping, do you anticipate doing that?

It's probably easier to add an extra opto sensor. It just needs to be N + 1/4 further round the disc than the A sensor, using the same holes. (not N + 1/2, I have made that mistake...)

You mentioned that the index didn't seem to be working? Possibly a confusion about which channel it is on?Is it GPIO 14 or 8 ?