September-10th-2020, 01:53 PM
(This post was last modified: September-10th-2020, 02:07 PM by Armin@netPI.)
Sure it is possible.
Here is how I would do it:
1. I would use the netX-programming example container from here https://registry.hub.docker.com/r/hilsch...-examples/
2. I would run the PROFINET example directly to check if it is running
3. I would change the default input/output data size of the PN example from 4 bytes inputs and 10 bytes output to 256bytes input and output to have more data
4. I would modfiy the the example to send the data instead of printing it on the screen to the local Docker internal IP network in InfluxDB (database) API based TCP/IP format and to a second container hosting the InfluxDB database.
5. I would start a second container InfluxDB (time series database) with the SSD USB drive mounted into this container and a mount point. The influxDB is configured to write its database data to this mount point and hence the SSD drive finally
6. Since InfluxDB container has a web server, you can watch the data also in historical order or you can call it from anywhere in the world if your netPI has internet contact.
The best thing is, if you do not want to let run the InfluxDB database on the netPI you could host it on a Windows Machine for example. In your example you have just to change the destination IP where the TCP/IP telegrams are sent to.
Thx
Armin
Here is how I would do it:
1. I would use the netX-programming example container from here https://registry.hub.docker.com/r/hilsch...-examples/
2. I would run the PROFINET example directly to check if it is running
3. I would change the default input/output data size of the PN example from 4 bytes inputs and 10 bytes output to 256bytes input and output to have more data
4. I would modfiy the the example to send the data instead of printing it on the screen to the local Docker internal IP network in InfluxDB (database) API based TCP/IP format and to a second container hosting the InfluxDB database.
5. I would start a second container InfluxDB (time series database) with the SSD USB drive mounted into this container and a mount point. The influxDB is configured to write its database data to this mount point and hence the SSD drive finally
6. Since InfluxDB container has a web server, you can watch the data also in historical order or you can call it from anywhere in the world if your netPI has internet contact.
The best thing is, if you do not want to let run the InfluxDB database on the netPI you could host it on a Windows Machine for example. In your example you have just to change the destination IP where the TCP/IP telegrams are sent to.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)