Strange 7i76e problem when starting linuxcnc

Today I made sure that the watchdog time was higher than the base thread. And disabled all power savings in the bios, at least as far as I'm aware.
That didn't change the fact that CR1 still comes on when I start up linuxcnc.

Now according to HM2 man the wachtdog pin should be high, but that isn't the case when I look in the Hal file.

This may just be an issue with the driver (some older versions of LinuxCNC have this problem with some firmware)

This should not affect operation as long as the watchdog bit is not actually set

Hello all.
I'm just starting with LinuxCNC and the first hurdle seems to have already stumped me. I have a fresh install (linuxcnc-stretch-uspace-i386-r13) and a 7i76e card with the factory settings. Theoretically this has an ip-address of 192.168.1.121.

I have two NICs:
eth0: The WAN connection to the host computer, cnc-pc1
eth1: The connection to the 7i76e card

I tested using the command: mesaflash --device 7i76e --addr 192.168.1.121 --readhmid

After reading the relevant Forum entries, I tried a number of things:
(1)
I had a home network address space of 192.168.178.xxx (Subnet mask 255.255.255.0) and the 7i76e had the default address of 192.168.1.121 (same subnet mask). I modified the /etc/network/interfaces.d/setup file according to the hm2_eth document and forum entries. That didn't work. I also tried the 10.10.10.11 idea - no luck...

(2)
I changed my home address space to 192.168.1.xxx (same subnet). The output from the "ip a", "ip route", and system messages are attached. Still no luck.

(3)
I tried to connect the 7i76e via a network switch using DCHP (I changed the jumpers accordingly), but still no luck. I still used the same attached files. Interestingly, the Mesa card didn't even show up in my router! Odd!

(4)
I turned on the Mesa Card before and after turning the PC on. All jumpers are factory default and confirmed. The board comes up, the LEDs down their sequential start-up blicks and then everything calms down as stated in the documentation. The RJ-45 LEDs are also blinking.

Any tips and pointers would be greatly appreciated. My Unix/Linux is a bit rusty, but it's coming back again slowly!

Cheers,
Joseph

First, I would always suggest the 10.10.10.10 ip address so that you do not overlap existing NAT ranges

To select the 10.10.10.10 IP address on the 7I76E, you set W3 up and W2 down (and cycle the 7I76E power)

Then you need to set up a static IP address on the host that includes the 7I76E
in its masked range (10.10.10.100 is suggested)

You can do this is the GUI or by editing the interfaces file

Hello!

That did it, thanks!

For whatever it's worth, a few points/questions for me and those who follow:

• I did reload the system just in case. I wanted to clear out any routing tables and such.


• Using the "/etc/init.d/networking restart" command didn't work. I needed a complete reboot. I always booted the card first.


• I doesn't matter if you use 7i76e or 7i76ed with the mesaflash command line. It simply looks for 7i76e. You must include the ip address of the card as a command line argument.


• I didn't use the /etc/network/interfaces.d/setup text shown in the hm2_eth man page. As suggested by PCW, I used 10.10.10.10 in the NIC setup and 10.10.10.100 in the /etc/network/interfaces.d/setup file.
  
  Question:
  Would it have worked had I (a) left the jumpers at factory default (W2 & W3 down), (b) setup my NIC with the 192.168.1.121 ip address, and (c) used (for example) 192.168.1.100 in the setup file?


• Just in case it's also not clear to others: The NIC setup should be the ip address of the 7i76e card since you're using the bootp service or the default ip address (depending on the jumper settings). The /etc/network/interfaces.d/setup, however, should be the ip address of the host, which must be in the masked range (as per netmask) chosen for the board.
  
  As PCW suggested, setting W2=Up and W3=Down enabled the bootp service (see Wikipedia) and it worked like a champ.


• Question:
  Finally, and let me know if this outside of the scope of this thread/forum: I'm unclear why the NIC gets the ip of the 7i76e card. Since we only have a simple bootp network architecture on the 2nd NIC?
  
  What would I have done had I attached a switch on eth2 and then connected four 7i76e cards? Would each have gotten their own, for example, 10.10.10.x ip number in the NIC setup? In this case, I assume you can't use the default jumper settings and ip address of 192.168.1.121?

Kind regards from Germany,
jaf

1. The host IP address _must_ be different than the 7I76E IP address but the 7I76E
must be accessible with the given netmask. (a /24 or 255.255.255.0 netmask is
suggested) This is standard static IP address setup, not 7I76E specific.

2. The 192.168.1.121 IP address is mainly present for testing and programming the 7I76E
since this address range is very like available on local networks. This is also the reason
its _not_ a good choice for real time use and the 10.10.10.10 address should be used.

3. Bootp is not used unless you set the jumpers for bootp, and of course have a 7I76E
hardware address ==> ip address entry in your dhcpd,conf file.

4. if you have multiple 7I76E cards, you either need to program them with different IP
addresses (10.10.10.10, 10.10.10.11, 10.10,10.12, etc suggested) or set the IP addresses
with bootp