Content
# #nino-well — 2025-07-07
**06:04 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751893488212419):** if the pi is online i should be able to access the PLC as well
**06:05 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751893502770539):** without a PC
**16:38 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931498496949):** @Kevin is it a productivity PLC? or click?
**16:38 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751931517997449):** productivity
**16:38 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931522018289):** oh fancy
**16:38 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931522634959):** ok
**16:38 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751931531935949):** just the 1000 though
**16:39 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931552080689):** any idea what the PI's ip addres is?
**16:39 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751931554568619):** I saw that it is a MQTT client
**16:39 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931573047799):** oh?
**16:39 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931577228409):** interesting.
**16:40 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751931615182459):** still would be nice to have the Pi if it gives us remote access to the PLC
**16:40 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751931624550639):** if it turns out we don't need it for MQTT
**16:40 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931648004559):** i still like the node-red software on the pi.. i can also do the signl4 alarming if we need. not sure if we could do that from the PLC
**16:41 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751931664503069):** good. I like it
**16:44 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751931858121219):** i dont see the pi in the list.. did you give it a static IP? maybe its stuck on the other subnet
**16:47 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932032495399):** yeah, might need your help when you have time to get the PI on the right network
**16:47 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932049447419):** we could probably leave it on DHCP
**16:47 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932059156449):** let me disconnect the eth and reboot
**16:50 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932239882669):** done.
**16:52 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932348519519):** ok. so.
**16:52 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932359852059):** i can connect to it over the VPN, but this PC that you have setup with productivity cant talk to it?
**16:53 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932427726219):** right because the plc and pc are on a different router. We can connect the Pi to the wireless on that router if you want, then they will be equal, but I'm guessing you will have to make a change in your vpn, otherwise it should be working with eth plugged in?
**16:54 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932456902139):** it just needs internet access.. so if dhcp gives it a good address the VPN should work
**16:55 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932500158679):** there must be some conflict
**16:55 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932516830869):** ok let me look around.. now that i can connect to SSH
**16:55 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932520585609):** standby
**16:56 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932573407019):**
![[F095D5WV0UQ_image_from_ios.jpg]]
**16:56 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932581653149):** Dashboard came back to life
**16:57 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932661505699):** ok can you also plug it into the ethernet port on the new router
**16:57 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932675313699):** maybe the wifi will keep it on the internet and i can see what address it picks up on eth
**16:58 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932703488949):** Done
**16:58 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932733797019):** yeah that shuts me down for some reason
**16:59 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932743353289):** thinking
**16:59 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932758585979):** Can you ssh from the pc?
**16:59 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932775531199):** no. i dont know what IP it gets.. and when i scan i dont see it in the subnet
**16:59 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932792881429):** Ssh to autosyspi
**17:01 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932881089949):** i can ping it from the PC.. it gets an ipv6 address
**17:02 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932937606149):** Thought i shut off ipv6 in the Pi
**17:02 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751932949807569):** Guess it didn't stick
**17:02 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932973884639):**
![[F0954FKPSN5_image.png]]
**17:03 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751932982132209):** i should be able to ssh with this.. let me see what i can do
**17:03 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751933019599059):** I was able to ssh to it using the hostname autosyspi
**17:04 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933048268929):** yeah that works.. but it resolves to that ipv6 address.. and not sure why the vpn isnt getting internet access
**17:05 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933122331639):** eth0 has an ip of 192.168.1.10 which i thin is on the other network.. weird.
**17:06 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751933167336899):** Is eth0 the wireless?
**17:06 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933171423479):** DHCP is enabled on the new router?
**17:06 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933174260909):** no wlan0 is wifi
**17:06 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933194361369):** it has 192.168.1.14
**17:07 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751933232999859):** I may have disabled dhcp
**17:07 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751933270306089):** But the PC is on automatic?
**17:08 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751933302613049):** Maybe dhcp is off for the eth port on the Pi
**17:11 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933499424559):** ok.. well.. now eth0 picked up a 10.0.0 address
**17:11 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933506863889):** and everything is good.
**17:11 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751933514184799):** not sure if theres a problem or not.
**17:24 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751934244945189):** ok.. beautiful.. i have routing all set up so i can get online with the PLC remotely
**17:24 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751934271052309):** let me have the pi read a tag over modbus tcp and push it up to the dashboard
**17:24 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751934284800219):** Super exciting!
**17:25 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751934308294769):** it is! this is pretty cool little setup
**17:53 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751936039687149):**
![[F094T7EU9HA_image_from_ios.jpg]]
**17:54 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751936078156659):**
![[F095DAQ2LN4_image.png]]
**17:54 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751936094538409):** PLC has a float value of 123.45 pi is grabbing it and publishing it to mqtt
**17:55 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751936107073829):** the mobile dashboard app reading it in and displaying it
**17:57 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751936229146669):** really digging this.. its clean. simple. not a lot of moving parts. i like it
**17:57 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751936256174409):** no vpn.. nothing needs to be hosted.. no router rules, not port forwarding..
**18:13 [Kevin](https://slack.com/archives/C094GTB7ACS/p1751937220331079):** Sweet!
**18:14 [Mason Radke](https://slack.com/archives/C094GTB7ACS/p1751937272193079):** What’s the next steps here?