Hi Jonas
Thanks for the details! I have everything up and running using the MQTT-broker. I use simple encoding and a integer to reflect the status on the UI.
BR, Anders

Hi Dirk Thanks for reply. I dug a bit deeper and now the communication is running using a MQTT broker (like your PICtory AFAIK?). The broker is initialized in NodeRed and the LogiCAL MQTT library interface is used for information transfer. However, the NodeRed publishes a string 'True'/'False' and n...

Hi It starts to get interesting... I have given up on the input pin and focus on the output pin in process variable from PICtory. The UA_SYS_start_O pin CAN actually be manipulated by Node-red.... Running piTest -r UA_SYS_start_O and setting UA_SYS_start_O high in Node-red yield different results. T...

Hi Dirk
Thanks for the input, I have proceed with Nodered, however I have run into problems.
Can you please take a look at this, I think this is something Kunbus can explain:
viewtopic.php?f=48&t=2533&p=9161#p9161
Thanks in advance!
BR, Anders

Hi again Testing the virtual input function in piTest using write to the named input pin in the virtual module confirms that the input cannot be read in logicad. piTest - w UA_SYS_start_I,1 Does not alter the value in logicad, but piTest yields a '1'. The pins in question from the export from Pictor...

Hi Added Virtual 32 bit extended module in pictory and access from Logi.Cal to Node-red works flawlesssy using node-red-contrib-revpi-nodes/revpi single input and revpi getpin. Desired values to be transferred from logical is written in the output pin section of the virtual module (using global vari...

Hi We chose to use RevolutionPi/Kunbus for our next project spring this year. In search for the required dongle to run PROCON, I got a rather arrogant answer from GTI, then I realized that Kunbus stopped the cooperation with GTI (or perhaps the other way around?)... The project is coded in Logi.cal ...