Axis 2.9.0~pre: jogging moves the tool cone, but not the steppers

I don't think its a LinuxCNC build issue or many more people
would be affected. As I said before I would more suspect
dropped packets which may be a hardware/network driver/OS issue

Here is the complete log of 7I96S setup packets captured
with tcpdump. You should get the same results (other than the host name)
Note that everything up to line 911 is setup, that is, the periodic:

host  --> 7I96S Read Request
7i96S  --> host Read Data
host --> 7I96S Write data

triplets start at  line 911

 

You've yet to explain why it works with pncconf and not with axis. I don't think you can. In principle, both send/receive information with the 7i96s card via the same mechanism, i.e., via halcmd. In the case of pncconf, everything works as expected. This suggests that your hypothesis about the problem being hard/network driver/OS can't be right. In the axis case, nothing is getting out to the 7i96s card. That's because halcmd isn't receiving anything to send. That's been proven with the evidence that I've put here.

However, just for grins and giggles, let me try to the tcpdump approach. Unfortunately, I've never used it, nor can I decode what the packets mean. So, would you please give me some more details about how I should use it and how I might interpret the packets?

Thanks.

If there is a communication issue it may be sensitive to timing or packet size
and this is completely different between pncconf and LinucCNC

In the axis case, nothing is getting out to the 7i96s card. That's because halcmd isn't receiving anything to send

Not true, the periodic data writes and reads must be working or you would get an
immediate following error if you command  a move.

What I am suggesting is that during initial parsing of the hal file and sending this
setup information to the 7I96S something has gone wrong, which may in fact be
dropped packets, a symptom of a hardware/OS or Ethernet driver issue
 
The fact that I can run LinuxCNC 2.9 on a 7I96S successfully with your hal file
suggest this is not LinuxCNC related but rather something very specific about
your setup (which points to hardware or network/OS issues)

The tcpdump command is

sudo tcpdump -i [your Etherent device] -x dump.txt

(lauch this before you start linuxCNC and immediately exit linuxCNC once it starts)

Sorry, the correct tcpdump command is:

sudo tcpdump -i [your Etherent device] -x > dump.txt

Nevermind. I think I figured it out myself.Attached are a couple of tcpdumps, one for pncconf, the other for axis. Tell me what you think. There is no evidence in either case that the network link is failing.

Well, I tried to attach a zip file, but it's too big.  They will be too big when I split them as well.  Please give me some direction about the best way to get them to you.  The unzipped sizes are 66MB and 43MB for pncconf and axis respectively.

Maybe the best approach is to edit out something, but I'm clueless as to what.  Would the binary version of these files work for you?

You should edit the files down to about 1000 lines each
nothing interesting happens beyond that

OK, attached are the trimmed tcpdump files. Let me know what you find.

Meanwhile, it is my understanding that the handling of the packets communicated between the computer and the I/O card are handled by halcmd (or some lower level software), not by axis as such. Is this not so?

I'm not entirely sure, but I think the python-based GUIs use the "linuxcnc" python module to communicate with the core LinuxCNC components. Source in src/emc/usr_intf/axis/extensions/emcmodule.cc .

Also, there were no files attached to your latest post.

I'm not sure what happened, but it may be that the files had an extension of .log which doesn't seem to be on the list of acceptable types.  So, now they are attached as a .zip file.