Destination Host Unreachable

I have a 7i96s.
I have moved the pins w4 down w5 up as per the instructions to use EEPROM (The as shipped default EEPROM IP address is 10.10.10.10.)
I have followed senpai tommy's guide  forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards
and when I ping :
ping 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
From 10.10.10.11 icmp_seq=1 Destination Host Unreachable
From 10.10.10.11 icmp_seq=2 Destination Host Unreachable

I noticed that everyone else fixed their problem by moving the pins but I've already done that. I checked the cable and it works.

SOLVED by not using virtual box but booting from a USB. Apparently, you can't use VB

 

You can not control machines from virtual box.
You should have mentioned that first.

Your network looks correctly setup, at first glance. Do the ethernet port LEDs blink in time with the pings?

Does your computer have multiple network interfaces (what does 'ip addr' say)? Is your Mesa EEPROM IP set to something other than 10.10.10.10? Perhaps try the 192.168.1.121 setting instead? (Use computer IP e.g. 192.168.1.120, netmask 255.255.255.0.)

I see so using virtual box in the first place was my doom. I should Just go with a normal linux installation?

xlordofpainx wrote:

I see so using virtual box in the first place was my doom. I should Just go with a normal linux installation?

Yes and no !
Yes, no virtual box.
And no, for testing you do not need to install anything, just burn the image to a USB stick and boot from it.
It does not mess the existing installation, and you can control machines with it.
So boot from USB, set up the network, make a config using PncConf, test the machine with Mesa, and after you get it working DO NOT forget to save the config to another USB or to internal hard drive. It will not save configs while it is in Live mode or booted from USB.

I see. Okay. . Wow I would have kept trying for hours. Thanks a lot. I will try this first thing tomorrow

I did what you asked and success. But the internet stopped. Now my next problem is the motor does not spin.
I have a nema 34 with encoder strapped to servo stepper drive. What would be the first debug step? I checked the phases, the encoder wires, mesa pins and followed the pncconfig tutorial. 

The most common reasons for no motion on step/dir drives are

1. Wiring
I suggest single ended wiring for step motor drives so
PUL+ ==> 7I96S +5V
PUL- ==> 7I96S STEP-
DIR+ ==> 7I96S +5V
DIR- ==> 7I96S DIR-

2. Too short step times
(double manufacturers minimum step times to start)

3. Communication issues. watchdog faults
(fix realtime issues on host)

I had not even pressed post, such a great community. I will troubleshoot these and post back the results. Thanks.

First, before wiring it to mesa board
Power the drive with encoder wired, try to spin the shaft with your hand, it should not move, so get some pliers and try to spin it, it should move but go back when you release it.
If it does not do that, search the web for encoder wiring, it is usually wrong in the manuals for some of those drives.