September-22nd-2022, 08:02 AM
(This post was last modified: September-22nd-2022, 08:12 AM by Armin@netPI.)
Hello Sandip,
this forum is a platform for all customers to help out in all cases they have trouble with device configuration, or device communication issues, or need answers on simple questions they need an instant answer for. Then the rest of the forum readers can participate in case they have the same issue and can learn from it.
The platform is not made for making an overall consultancy for a specific customer usually a sales team is responsible for. These questions have to be forwarded and discussed with your responsible Hilscher sales colleague at headquarter if you can't answer them.
Here is what I can contribute
1. With netFIELD there is no container any more available to read/write S7 data. We did that once with Node-RED at times we call our solution netIOT. But meanwhile we changed to netFIELD which offers some Hilscher containers only, while customers have to deploy a standard and public Node-RED container of the community. So we are no longer responsible for a public Node-RED with netFIELD
2. Do not understand this question. Hilscher supports an OPC UA Client and Server container under netFIELD. Do you mean these containers?
3. A netFIELD device only is not able to read PLC/DCS data. It needs software doing so. So which software do you mean to read data from PLC?
4. No. Under netFIELD Hilscher is transparent to any software running on our device except those that is developed by Hilscher. Node-RED does not come from Hilscher, so its responsibility lies in the community.
5. Node-RED is not our software. So it is not our responsibility.
6. Once again. Node-RED is not our software. Under netFIELD we tell customers they can load any container to netFIELD devices. If customers want to use Node-RED, they can load the container from here https://hub.docker.com/r/nodered/node-red
7. This has to be negotiated with your sales representative at Hilscher HQ
8. Once again under netFIELD a device is transparent to any softzware. So the decision if a netFIELD device sends data to MS Azure or Google Cloud or Amazon AWS cloud is made by the end customer depending on the container he deploys on the device
9. The feature data retention right now is not available. So if a netFIELD device sends data to netFIELD Cloud using the socalled platform connector container, then this data is nowhere stored.
10. Yes sure. You can disable the SSH service in the Web-UI of a netFIELD device
11. No this is not possible. With the latest version of our edge gateway netFIELD Connect, we are supporting secure boot. So each device gets a signed OS that fits to the devices serial number. So each OS and its keys is slightly different per device. So there can never ne a single .iso file. OS updates are provided here ehttps://kb.hilscher.com/display/NO/netFIELD+OS+-+Core+system+software+and+runtimes+making+devices+netFIELD+Cloud+managable
12. Service is offered by Hilscher HQ from 9 AM to 5 PM only.
13. Once again. A netFIELD Device without any software does not store any data. Since customer an deploy their own software based on containers they can store it as long as they want with their own software
14. All Hilscher offered containers under netFIELD are written in the modern way to make all data available on an MQTT broker. A broker has the advantage to distribute all published data to any connected MQTT client. So to extend this basic setup by a "debug function" is quite easy. You could add your own software to netFIELD device which works as an MQTT client and subscribes to all data that is held in the MQTT broker. So then it will receive all data and hence can be debugged. Or customer installs an MQTT client on his Windows machine for example and connects to the MQTT broker in the device. Then this windows client also receives all data in the device
15. Once again. A netFIELD device is 100% transparent to the software running inside by using container techniques. So the customer decides whether or not a device support AI or Edge computing based on his demands
16. Customer decides on his software by himself. So defining API is a matter of the customer's software, not of Hilscher.
this forum is a platform for all customers to help out in all cases they have trouble with device configuration, or device communication issues, or need answers on simple questions they need an instant answer for. Then the rest of the forum readers can participate in case they have the same issue and can learn from it.
The platform is not made for making an overall consultancy for a specific customer usually a sales team is responsible for. These questions have to be forwarded and discussed with your responsible Hilscher sales colleague at headquarter if you can't answer them.
Here is what I can contribute
1. With netFIELD there is no container any more available to read/write S7 data. We did that once with Node-RED at times we call our solution netIOT. But meanwhile we changed to netFIELD which offers some Hilscher containers only, while customers have to deploy a standard and public Node-RED container of the community. So we are no longer responsible for a public Node-RED with netFIELD
2. Do not understand this question. Hilscher supports an OPC UA Client and Server container under netFIELD. Do you mean these containers?
3. A netFIELD device only is not able to read PLC/DCS data. It needs software doing so. So which software do you mean to read data from PLC?
4. No. Under netFIELD Hilscher is transparent to any software running on our device except those that is developed by Hilscher. Node-RED does not come from Hilscher, so its responsibility lies in the community.
5. Node-RED is not our software. So it is not our responsibility.
6. Once again. Node-RED is not our software. Under netFIELD we tell customers they can load any container to netFIELD devices. If customers want to use Node-RED, they can load the container from here https://hub.docker.com/r/nodered/node-red
7. This has to be negotiated with your sales representative at Hilscher HQ
8. Once again under netFIELD a device is transparent to any softzware. So the decision if a netFIELD device sends data to MS Azure or Google Cloud or Amazon AWS cloud is made by the end customer depending on the container he deploys on the device
9. The feature data retention right now is not available. So if a netFIELD device sends data to netFIELD Cloud using the socalled platform connector container, then this data is nowhere stored.
10. Yes sure. You can disable the SSH service in the Web-UI of a netFIELD device
11. No this is not possible. With the latest version of our edge gateway netFIELD Connect, we are supporting secure boot. So each device gets a signed OS that fits to the devices serial number. So each OS and its keys is slightly different per device. So there can never ne a single .iso file. OS updates are provided here ehttps://kb.hilscher.com/display/NO/netFIELD+OS+-+Core+system+software+and+runtimes+making+devices+netFIELD+Cloud+managable
12. Service is offered by Hilscher HQ from 9 AM to 5 PM only.
13. Once again. A netFIELD Device without any software does not store any data. Since customer an deploy their own software based on containers they can store it as long as they want with their own software
14. All Hilscher offered containers under netFIELD are written in the modern way to make all data available on an MQTT broker. A broker has the advantage to distribute all published data to any connected MQTT client. So to extend this basic setup by a "debug function" is quite easy. You could add your own software to netFIELD device which works as an MQTT client and subscribes to all data that is held in the MQTT broker. So then it will receive all data and hence can be debugged. Or customer installs an MQTT client on his Windows machine for example and connects to the MQTT broker in the device. Then this windows client also receives all data in the device
15. Once again. A netFIELD device is 100% transparent to the software running inside by using container techniques. So the customer decides whether or not a device support AI or Edge computing based on his demands
16. Customer decides on his software by himself. So defining API is a matter of the customer's software, not of Hilscher.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
