Bostomatic 400-2 Retrofit

1. What does "ip a" report? Dropped connections are not normal

2. If you connected a high current capable power supply to a 7I83 backwards
its likely you shorted the reverse protection diode. Depending on the current
capabilities of the supply this may be the only damaged component

1. Here is it "ip a" report A, with the link working B, after it drops.
A:
bosto400@BostoCNC:~$ 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
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 34:17:eb:c5:b0:83 brd ff:ff:ff:ff:ff:ff
inet 192.168.90.105/24 brd 192.168.90.255 scope global dynamic noprefixroute eno1
valid_lft 86145sec preferred_lft 86145sec
inet6 fe80::135a:b283:9604:a8bb/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 68:05:ca:e8:4c:4e brd ff:ff:ff:ff:ff:ff
inet 10.10.10.2/8 brd 10.255.255.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::6a05:caff:fee8:4c4e/64 scope link
valid_lft forever preferred_lft forever

B:
bosto400@BostoCNC:~$ 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
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 34:17:eb:c5:b0:83 brd ff:ff:ff:ff:ff:ff
inet 192.168.90.105/24 brd 192.168.90.255 scope global dynamic noprefixroute eno1
valid_lft 85728sec preferred_lft 85728sec
inet6 fe80::135a:b283:9604:a8bb/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 68:05:ca:e8:4c:4e brd ff:ff:ff:ff:ff:ff

I did notice that the sub net was wierd (10.10.10.2/8 brd 10.255.255.255 ) so I changed the /9 to /24 and I get 10.10.10.2/24 brd 10.10.10.255 now, which I believe is correct.

2. I'm fairly sure I shorted the diode, what component # is the diode so I can test it.? I checked resistance across the v in terminals and both directions measured 0.
Is this something that is fixable? Send it in or can I do it?

1. How did you set the static IP address? I have see Wicd break existing connections like this
(how can the host lose its IP address in "B"? this should no happen even if the link is down)

2. The diode is CR1, a MRA4007

Diodes: I measure .1 Ohms both directions on the Diode, If I remember correctly that means its bad... good thing their not expensive!

I initially had trouble with the nm-tray so I loaded gnome network manager and did the initial settings in there. I uninstalled nm-tray
After I noticed the network dropping I switched out the cable, then the NIC, then reloaded nm-tray & xterm (that fixed the original issue i was having) , and uninstalled gnome network manager.
Something may have gotten messed up thru this process, should I delete the connection and start over?

Diodes are fixed and the 7I83 cards seem to be working, there are 3 of the 4 leds on and I can see the corresponding pins. Yea!
However I am still having the dropping issues. I finally got a half file that didn't throw errors on start up, and within a minute linuxcnc says it lost connection to the 7I94 card. So as a last resort I saved all of the important files and did a fresh install of linuxcnc. Installed the needed software etc and got the same results. I even switched which NIC the 7I94 was connected to with the same results. I'm using a store bought network cable so I don't think that's the issue. I think I have tested every option for failure and I'm down to the 7I94 board itself. Anyone have anyideas?

Could it be the flash file that I loaded? I used the files from this thread.
forum.linuxcnc.org/27-driver-boards/4282...sa-7i94-7i89?start=0

It's not likely firmware related since all firmware uses the same Ethernet code
This is still suspicious:

1. Here is it "ip a" report A, with the link working B, after it drops.
A:
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 68:05:ca:e8:4c:4e brd ff:ff:ff:ff:ff:ff
inet 10.10.10.2/8 brd 10.255.255.255 scope global noprefixroute enp4s0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Valid static IP address on host

3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 68:05:ca:e8:4c:4e brd ff:ff:ff:ff:ff:ff
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What happened to the static IP address?

This is not something the 7I94 can do

Even if the link is lost, I would expect something like:
A valid link:

2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether ec:b1:d7:6c:a2:da brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 10.10.10.100/8 brd 10.255.255.255 scope global eno1
       valid_lft forever preferred_lft forever

B cable unplugged:
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether ec:b1:d7:6c:a2:da brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 10.10.10.100/8 brd 10.255.255.255 scope global eno1
       valid_lft forever preferred_lft forever

One reason for dropping a connection is too many timed out packets
What is your servo thread rate and what are the various tmax values?
(and CPU clock speed since tmax numbers are in CPU clock cycles)

halcmd show param *.tmax

(when linuxCNC is running)




 

Here are the results of halcmd show param *.tmax

bosto400@Bosto400-linuxcnc:~$ halcmd show param *tmax
Parameters:
Owner Type Dir Value Name
32 s32 RW 3272 abs.spindle.tmax
38 s32 RW 38928 classicladder.0.refresh.tmax
41 s32 RW 11700 foincr.tmax
26 s32 RW 0 hm2_7i94.0.read-request.tmax
26 s32 RW 2792544 hm2_7i94.0.read.tmax
26 s32 RW 80492 hm2_7i94.0.write.tmax
41 s32 RW 8100 jogincr.tmax
35 s32 RW 4580 lowpass.spindle.tmax
19 s32 RW 12272 motion-command-handler.tmax
19 s32 RW 57824 motion-controller.tmax
29 s32 RW 6732 pid.a.do-pid-calcs.tmax
29 s32 RW 10872 pid.s.do-pid-calcs.tmax
29 s32 RW 14656 pid.x.do-pid-calcs.tmax
29 s32 RW 10872 pid.y.do-pid-calcs.tmax
29 s32 RW 5988 pid.z.do-pid-calcs.tmax
20 s32 RW 2862940 servo-thread.tmax
41 s32 RW 6388 soincr.tmax

Here is the fresh ip a before and after the connection drops see pics attached for error msgs.  It dosen't seem like its dropping compleatly, like it has a loose wire....  The 7I94 is on the eno1(onboard) NIC now originally I had it on the brand new enp4s0 (intel card).
Before:
bosto400@Bosto400-linuxcnc:~$ 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
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 34:17:eb:c5:b0:83 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/8 brd 10.255.255.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::18d7:d22d:45d1:1bd/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 68:05:ca:e8:4c:4e brd ff:ff:ff:ff:ff:ff
    inet 192.168.90.101/24 brd 192.168.90.255 scope global dynamic noprefixroute enp4s0
       valid_lft 67692sec preferred_lft 67692sec
    inet6 fe80::6a05:caff:fee8:4c4e/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

After:
bosto400@Bosto400-linuxcnc:~$ 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
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 34:17:eb:c5:b0:83 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::18d7:d22d:45d1:1bd/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 68:05:ca:e8:4c:4e brd ff:ff:ff:ff:ff:ff
    inet 192.168.90.101/24 brd 192.168.90.255 scope global dynamic noprefixroute enp4s0
       valid_lft 67307sec preferred_lft 67307sec
    inet6 fe80::6a05:caff:fee8:4c4e/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

 

26 s32 RW 2792544 hm2_7i94.0.read.tmax

Is likely way too long (this is in CPU clock cycles)
I also have never seen "error finishing write" or "error queuing read"

Can you post your hal and ini files?

If you have Intel MACs, have you disabled IRQ coalescing
as described in the hm2_eth manual page?

Have you watched the 7I94 Link and status LEDs when running?
do you lose the link or is there possibly a power issue?