Robust PC-RPI IOT Platform

Hi Jay,

I'm not sure of the requirement, your question is framed in an unusual way where you're mentioning some programming languages and command lines, but the end goal is missing to help answer it well.

1. My Goal in detail

        (e.g. climb a mountain next year)

2. What things I'm trying to solve

         (e.g. establish how high I am)

3. What constraints I have

         (e.g. cost, software experience, hardware experience)

4. What hardware, tools and software I'm using

         (e.g. part number, link to the tools and software)

5. Diagram or sketch to show the scenario, and what I've attempted

Although it is a guess, possibly a couple of things worth reading up on, maybe they may or may not end up being part of a solution, but are useful to know about anyway, are:

(1) SSH

With SSH, it's possible to send commands from one machine to another, and have them execute and return the displayed result. For more information on this, see  Accessing and Controlling the Pi

(2) HTTP

HTTP can be used by programmers to send something like a web link from one machine to another, and have the remote side pull information out of that, perform an action, and then send back the results. HTTP can often be tested by using a web browser, and typing something like http://192.168.0.10/mycommandsystem?command=clearscreen;reportbackwhencomplete=true

At the remote end, code that is continuously running and listening for such a request (known as web server software) will decipher that line, and do whatever actions it needs to (based on what the software programmer intends) and then send a response back. For more information on this type of scheme, there's a nice tutorial to work through here: https://projects.raspberrypi.org/en/projects/python-web-server-with-flask

Both of the above methods work in a similar way in that they rely on a network protocol, and IP addressing. This works because any device on your home network (you mention WiFi, but it won't matter if it is via WiFi or Ethernet, it will work the same way) have an IP address, and SSH and HTTP work on top of that network, transmitting and receiving information in a client and server machine relationship that comes about when you run server software on the remote machine (SSH is by default running on the Pi once enabled, and the HTTP server can be coded as indicated in the web link above) and when you use client software that makes use of SSH, or HTTP, or when you write your own custom programs that make use of a protocol that the server understands.

Based on this information, it might get you closer to defining what you're looking for, or (hopefully) it may be the answer.

Hi Jay,

I'm not sure of the requirement, your question is framed in an unusual way where you're mentioning some programming languages and command lines, but the end goal is missing to help answer it well.

1. My Goal in detail

        (e.g. climb a mountain next year)

2. What things I'm trying to solve

         (e.g. establish how high I am)

3. What constraints I have

         (e.g. cost, software experience, hardware experience)

4. What hardware, tools and software I'm using

         (e.g. part number, link to the tools and software)

5. Diagram or sketch to show the scenario, and what I've attempted

Although it is a guess, possibly a couple of things worth reading up on, maybe they may or may not end up being part of a solution, but are useful to know about anyway, are:

(1) SSH

With SSH, it's possible to send commands from one machine to another, and have them execute and return the displayed result. For more information on this, see  Accessing and Controlling the Pi

(2) HTTP

HTTP can be used by programmers to send something like a web link from one machine to another, and have the remote side pull information out of that, perform an action, and then send back the results. HTTP can often be tested by using a web browser, and typing something like http://192.168.0.10/mycommandsystem?command=clearscreen;reportbackwhencomplete=true

At the remote end, code that is continuously running and listening for such a request (known as web server software) will decipher that line, and do whatever actions it needs to (based on what the software programmer intends) and then send a response back. For more information on this type of scheme, there's a nice tutorial to work through here: https://projects.raspberrypi.org/en/projects/python-web-server-with-flask

Both of the above methods work in a similar way in that they rely on a network protocol, and IP addressing. This works because any device on your home network (you mention WiFi, but it won't matter if it is via WiFi or Ethernet, it will work the same way) have an IP address, and SSH and HTTP work on top of that network, transmitting and receiving information in a client and server machine relationship that comes about when you run server software on the remote machine (SSH is by default running on the Pi once enabled, and the HTTP server can be coded as indicated in the web link above) and when you use client software that makes use of SSH, or HTTP, or when you write your own custom programs that make use of a protocol that the server understands.

Based on this information, it might get you closer to defining what you're looking for, or (hopefully) it may be the answer.