That would be something to try.. Maybe mesaflash doesn't know how to handle the 192.168.1.1 ip address? Set the pie to something else like 192.168.1.10
On Fri, Jun 11, 2021 at 11:25 AM Mark Wendt <wendt.m...@gmail.com> wrote: > On Fri, Jun 11, 2021 at 12:09 PM John Dammeyer <jo...@autoartisans.com> > wrote: > > > Sam, > > Here's the ifconfig output generated from putty running on my WIN-7 > > workstation via remote desktop from my WIN-10 ZBook. Ethernet cable from > > Pi4 to 7i92 is 2' long. > > > > And with or without LinuxCNC running this is what I get: > > pi@linuxcnc:~ $ cd mesaflash > > pi@linuxcnc:~/mesaflash $ sudo ./mesaflash --device 7i92 --readhmid > > lbp16_access.send_packet: Operation not permitted > > Aborted > > > > John > > > > pi@linuxcnc:~ $ ifconfig > > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255 > > ether dc:a6:32:1e:30:f1 txqueuelen 1000 (Ethernet) > > RX packets 29442387 bytes 2826463726 (2.6 GiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 58886151 bytes 1122489823 (1.0 GiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 > > inet 127.0.0.1 netmask 255.0.0.0 > > inet6 ::1 prefixlen 128 scopeid 0x10<host> > > loop txqueuelen 1000 (Local Loopback) > > RX packets 595 bytes 40144 (39.2 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 595 bytes 40144 (39.2 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > > inet 192.168.0.97 netmask 255.255.255.0 broadcast 192.168.0.255 > > inet6 fe80::9d66:1b85:f539:da50 prefixlen 64 scopeid 0x20<link> > > ether dc:a6:32:1e:30:f2 txqueuelen 1000 (Ethernet) > > RX packets 11119 bytes 3535970 (3.3 MiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 3108 bytes 415864 (406.1 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > pi@linuxcnc:~ $ > > > > Do you have any other network devices on the 192.168.1.x network? The > 192.168.1.1 address is usually reserved for routers in that subnet. > > Mark > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
