January-2nd-2020, 03:20 PM
(This post was last modified: January-2nd-2020, 03:20 PM by Armin@netPI.)
Hello Carsten,
I want to first mention at this stage that this forum was made for the device name NIOT-E-NPI3-51-EN-RE or called "netPI" as marketing name.
I agree that both devices NIOT-E-NPI3-51-EN-RE and NIOT-E-TPI51-EN-RE look similar, but they come indeed with different software preloaded.
The device NIOT-E-NPI3-51-EN-RE just has Docker preinstalled and you can add software to it as containers only whereas NIOT-E-TPI51-EN-RE (your device) comes with Docker AND Node-RED preinstalled. So with Node-RED you have a software ready-to-use to realize different kind of software connectivity.
Since this forum is made for netPI only and handles all questions around "Docker and Containers" preferable I can just give limited support for your device (which of course includes Docker also) but Node-RED as main software. Support for your device can be received through hotline@hilscher.com.
A word to the NPIX-RS485 module. First of all make sure you have a RS-485 module of #REV2. There is a bar code on the module and in the lower right corner of it there shoul be the value 2. This module or #REV2 just needs the pin BCM_TX_EN (GPIO 17) set to high = 1 to be enabled and then works in auto direction control for transmitting and receiving frames. The NPIX-RS485 is connected to the "mini" UART of the Raspberry CPU working in your device. This UART has some restrictions in term of UART functionality. These limitations are all writting the NPIX manual located here https://www.netiot.com/netpi/industrial-raspberry-pi-3/ in the download section. So you should check if the RS485 module in conjunction with the Mitsubishi PLC will work or not based on this UART restrictions.
As next a word to Node-RED as preinstalled software. This software has some nodes preinstalled which enables the communication over Modbus RTU and a lot more. I search on Google for "Computer Link" protocol and found some links, but what I did not find was any Node-RED function and support for this type of protocol. So I have doubts it will run with the PLC directly. So your fall-back as you said is "Modbus" which is supported by Node-RED.
The preinstalled Node-RED also includes the OPC UA nodes https://flows.nodered.org/node/node-red-contrib-opcua. If you read details on this page you see that it supports OPC UA server functionality as well. So if you get the Modbus Nodes connected to talk to the Mitsubishi PLC you could pass the data to the OPC UA server and from there it can be read out by any client.
The cool thing with Node-RED is that before receiving the NIOT-E-TPI51... device is that you can install Node-RED on Windows already and play with it immediately to get familiar with it. Here is a link how to do it: http://www.brainboxes.com/faq/items/inst...windows-pc
If you have more questions don't hesitate to ask
Armin
I want to first mention at this stage that this forum was made for the device name NIOT-E-NPI3-51-EN-RE or called "netPI" as marketing name.
I agree that both devices NIOT-E-NPI3-51-EN-RE and NIOT-E-TPI51-EN-RE look similar, but they come indeed with different software preloaded.
The device NIOT-E-NPI3-51-EN-RE just has Docker preinstalled and you can add software to it as containers only whereas NIOT-E-TPI51-EN-RE (your device) comes with Docker AND Node-RED preinstalled. So with Node-RED you have a software ready-to-use to realize different kind of software connectivity.
Since this forum is made for netPI only and handles all questions around "Docker and Containers" preferable I can just give limited support for your device (which of course includes Docker also) but Node-RED as main software. Support for your device can be received through hotline@hilscher.com.
A word to the NPIX-RS485 module. First of all make sure you have a RS-485 module of #REV2. There is a bar code on the module and in the lower right corner of it there shoul be the value 2. This module or #REV2 just needs the pin BCM_TX_EN (GPIO 17) set to high = 1 to be enabled and then works in auto direction control for transmitting and receiving frames. The NPIX-RS485 is connected to the "mini" UART of the Raspberry CPU working in your device. This UART has some restrictions in term of UART functionality. These limitations are all writting the NPIX manual located here https://www.netiot.com/netpi/industrial-raspberry-pi-3/ in the download section. So you should check if the RS485 module in conjunction with the Mitsubishi PLC will work or not based on this UART restrictions.
As next a word to Node-RED as preinstalled software. This software has some nodes preinstalled which enables the communication over Modbus RTU and a lot more. I search on Google for "Computer Link" protocol and found some links, but what I did not find was any Node-RED function and support for this type of protocol. So I have doubts it will run with the PLC directly. So your fall-back as you said is "Modbus" which is supported by Node-RED.
The preinstalled Node-RED also includes the OPC UA nodes https://flows.nodered.org/node/node-red-contrib-opcua. If you read details on this page you see that it supports OPC UA server functionality as well. So if you get the Modbus Nodes connected to talk to the Mitsubishi PLC you could pass the data to the OPC UA server and from there it can be read out by any client.
The cool thing with Node-RED is that before receiving the NIOT-E-TPI51... device is that you can install Node-RED on Windows already and play with it immediately to get familiar with it. Here is a link how to do it: http://www.brainboxes.com/faq/items/inst...windows-pc
If you have more questions don't hesitate to ask
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
