Mach3 -> Camtronics -> Parallel P Replacement

Threading is all I have done with this before. Super happy about the potential I have with this 7i76e card!

This is the ethernet adapter info.

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

The ping was direct between the network port on the PC and the 7i76e.

Being a little concerned, I pulled the cat-5 -> parallel plug to cat-5 connector I made and ran a ping.

Looks the same.

Thank you for letting me know to have this on my radar.

Yeah, the Realtek driver doesn't have that option so I'm not sure what's going on with the random ping times.

Here's what I get:
peter@pcw-HP-EliteDesk-800-G1-USDT:~/bitfiles$ ping 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.208 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.130 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.130 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.130 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.133 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.132 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.129 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.129 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.129 ms
64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.130 ms
64 bytes from 10.10.10.10: icmp_seq=11 ttl=64 time=0.130 ms
64 bytes from 10.10.10.10: icmp_seq=12 ttl=64 time=0.130 ms
64 bytes from 10.10.10.10: icmp_seq=13 ttl=64 time=0.129 ms
64 bytes from 10.10.10.10: icmp_seq=14 ttl=64 time=0.129 ms
64 bytes from 10.10.10.10: icmp_seq=15 ttl=64 time=0.130 ms
64 bytes from 10.10.10.10: icmp_seq=16 ttl=64 time=0.142 ms
^C
--- 10.10.10.10 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 15356ms
rtt min/avg/max/mdev = 0.129/0.135/0.208/0.022 ms

(The first response is slower because the host needs to do a ARP transaction )

I'll keep on the hunt regarding this ping time.

There was another thread you replied to with a Realtek having similar ping response.

I checked the BIOS on this ZBOXNANO-AD12 PC and its as up to date as possible. Version 2K131128.

root@cnc:~# dmesg | egrep -a "ZOTAC"
[ 0.000000] DMI: ZOTAC ZBOXNANO-AD12/ZBOXNANO-AD12, BIOS A261P020 11/28/2013

What made you think you had to build Linuxcnc from source ?

The whole point of the images was to enable a quick and easy setup to get going.

Unless of course you wanted a version other than 2.8

bbsr_5a wrote: hi we got a external user that has quite a Good if not the best follow throu
gnipsel.com/linuxcnc/uspace/debian9-emc.html

look here

as you are new to the Linux system why dident you go for the almost redy to run Version on DVD Debian
just insertt the DVD and go ahed cabeling ans configurating

The forum supplied Mint images have the same functionality as the official Debian ones.
The Mint ones are setup for qtvcp out of the box.
Some little extras are all the HTML docs available offline via the cnc menu, desktop shortcuts to the forums and the linuxcnc GitHub page and lastly a desktop shortcut to a script that installs the dependencies to build linuxcnc. The desktop shortcut to the read me even has a reference to JT’s page regarding rebuilding linuxcnc.
If stable packages become available for qtpyvcp they’d go in as well.

This would be the reason.

Compiling from source is typically straight forward and is the least of my concern.