Mesa 7i96s / Network no longer working

Hi all

I was happily using my 7i96s with LinuxCNC on my Mill. This week i powered on the machine and LinuxCNC was not able to connect. Ping 10.10.10.10 also got no response. So i picked a new 2m Lan Cable and connected the Laptop to the Mesa Card  (thought the cable from the cabinet might be damaged) - no Change I removed all connectors from the Mesa except the Power, still no change. I put the Mesa card on my bench, inspection did not show any damage. The Link Led is on, traffic led blinking from time to time. I did set the jumper W4/W5 down/down for 192.168.1.121 fallback ip (changed my laptop ip also ofc ), still no luck.
I did set the jumpers up/down for bootp and connected it to my router - it got stuck with red led on boot and no device did show in dhcp or the switch arp table.
The card was all the time inside a cabinet and there was no change to any electronics or firmware. I replaced the card with the one from my lathe - worked like a charm.

So the question: There is a firmware "7i96s_16m_fallback.bin", should i try to flash this on the card (the electronic guys at work have jtag equipment) ? 
From the manual :  "Note that the card IP address is fixed at 192.168.1.121 when the IP select jumpers are in the UP,UP setting. If this fails, the 7I96Ss EEPROM must be re-programmed via the JTAG connector or (faster) JTAG FPGA load followed by Ethernet EEPROM update"

Anyone has done this before and could give me some hints please ? Thanks

-
schnellmued
 

If you get the link LED (Yellow) on the RJ45, its not likely a firmware issue
but rather an Ethernet issue.

If you ping the card, do the green LEDs on the 7I96S count up?
 

On the PC, what does
ip a
in a terminal return?

>>If you get the link LED (Yellow) on the RJ45, its not likely a firmware issue
>>but rather an Ethernet issue.
>>If you ping the card, do the green LEDs on the 7I96S count up?

no, the green LED stay off.

If i connect to the other card in my lathe and ping it the green LED start to blink

-
schnellmued

tommylight wrote:

On the PC, what does
ip a
in a terminal return?

 

---

xx@lxcnc-l540:~$ ip a
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: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 3c:97:0e:d3:69:0e brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute enp0s25
       valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5c:51:4f:8c:69:69 brd ff:ff:ff:ff:ff:ff
    inet 192.168.37.146/24 brd 192.168.37.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 863940sec preferred_lft 863940sec

---

enp0s25 is the nic connected directly to the mesa card, wlp2s0 wifi to my home router

-
schnellmued
 

Sounds like something has gone wrong with the Ethernet section of the 7I96S card.
It should be repaired/replaced under warranty, Contact Mesa or your dealer for instructions

That looks OK.
Did you use the Network Manager to set up the network?
If yes, you need to check the "use this connection for local ..... " not sure what exactly it says as i am on the phone.
That is for wired network only, IPV4 settings.
You also have a wireless network and if that connects before the Lan, it will send all trafic through wifi, if the above is not set for wired network.

tommylight wrote:

That looks OK.
Did you use the Network Manager to set up the network?
If yes, you need to check the "use this connection for local ..... " not sure what exactly it says as i am on the phone.
That is for wired network only, IPV4 settings.
You also have a wireless network and if that connects before the Lan, it will send all trafic through wifi, if the above is not set for wired network.
 

I think i used networkmanger, but iam also able to set the ip with ifconfig 
The Ip Stack will notice 10.10.10.10 is on the same subnet  as 10.10.10.2/24, so it will allways send packets for 10.10.10.0/24 to that interface. (unless statics routes exist)  It also worked for like >1 year in this config and it still works for the lathe mesa with the same ip as the "broken" one. I also tried some other Laptop, with no luck

-
schnellmued

 

PCW wrote:

Sounds like something has gone wrong with the Ethernet section of the 7I96S card.
It should be repaired/replaced under warranty, Contact Mesa or your dealer for instructions
 

Ok, i fear that too. But i will hook it to this Jtag debugger thingy at work, just for curiosity

Will post if i got some insights ..-
schnellmued

Ok, this is getting weird ... Yesterday i mounted the mesa card from the lathe into the mill, all worked fine... made parts for like 3+ hours .. Today i power up the mill again and the second mesa card network is also no longer working I dont understand, there was zero change to the electronics, since decenmber last year or sometime around.. (added 3d-probe)
The only power coming to the mesa card is 5v from a step down converter (24v->5v) which goes into the vc+/gnd and +5 to the input common.. all outputs go to a relay board. China spindle to pwm 0-10v . Xyz-axis Stepper drivers are on a seperate 48v psu, A-axis Stepper is on the 24v psu

This setup was working for ~1 year... Is there any chance some voltage spike (iam no electronics guy ) could kill only the ethernet ?

-
schnellmued