Gene,
See below for ip route and solution.
> From: Gene Heskett [mailto:[email protected]]
> > > I'm stuck. What's the next step to get this working again?
> > >
> > > Thanks
> > > John
>
> What does "ip route" say?
>
Here's the result of the ip route but notice it's showing wlan0 so that's
perfectly alright.
default via 192.168.0.2 dev wlan0 proto dhcp src 192.168.0.97 metric 303
192.168.0.0/24 dev wlan0 proto dhcp scope link src 192.168.0.97 metric 303
The WiFi is working with the system. Neither the HAL file (with 192.168.1.121)
nor the jumpers on the MESA have been changed.
$
loadrt hostmot2
loadrt hm2_eth board_ip="192.168.1.121" config=" num_encoders=0 num_pwmgens=1 n$
setp hm2_7i92.0.watchdog.timeout_ns 5000000
The only thing that happened over the last week was the hardwired Ethernet
because at night, here in our neighbourhood, everyone starts watching movies on
their WiFi based cable modems and ability to reach across the house from the
WiFi router to the office becomes problematic. So to do the apt-get
update/upgrade etc to the OS it was more reliable to swap out the mesa for a
wired connection.
My Pi2 with Octopi to the 3D printer also had to be connected with wired
because it became too unreliable. At the moment it's too difficult to move the
WiFi Ethernet Router into the center of the house.
And then it hit me. Instead of suspecting samba I should have set the eth0 ip
on the Pi4 to be 192.168.1.1.
Did that, cycled power to the MESA, lights did the same blinky thing and then
kept doing blinky patterns. And now the Pi4 reports that it's connected and
when running LinuxCNC works.
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 509121 bytes 48873834 (46.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1018296 bytes 93686274 (89.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And none of the rest of my wiring on the bench has been disturbed because the
MIST/COOLANT ON/OFF buttons again switch on relays on a CANopen module
connected via a Lawicel CANUSB.
The Pi4 now is wearing a MCP2515 CAN HAT so next step is to try using SocketCAN
to access it instead of the CANUSB dongle although for the standard PC running
the mill it will have to be the CANUSB.
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
