Hi Amar, Thanks, that helped with the Modbus TCP setup which now works. The last step is to get Modbus RTU up and running. I have a temperature sensor on my slave device, and I know it can be read from pictory. I've updated the CODESYSControl.cfg with [SysCom] Linux.Devicefile=/dev/ttyUSB I have NOT...

Thanks Dirk.

Are you able to help me please?

Excellent! - thanks, that's working now. I can turn the lights on/off. I understand the basics of the offset now. Moving on to Modbus I have now added a Modbus TCP module to communicate with a Teltonika 955 router and a Modbus RTU module to communicate with a Carel EVD Evolution driver. piTest promp...

Hi Amar,

So I think I have understood that the "offset" is specifying the location of the individual modules - am I right?

I managed to set up your image test, but I still cannot turn the LEDs on and off.

What am I doing wrong?

Thanks,
Nikolai

Hi Amar,

That's great I'll try it out .

In the meantime, are you able to explain what the "offset" means? Is it an offset in time? I don't understand the purpose?

Thanks,
Nikolai

Hello, I'm trying to set up a Connect+ with Modbus and the AIO and DIO module. I haven't purchased the modules yet, as I want to test the feasibility of running CODESYS on the RevPI. I followed this guide to flash the CODESYS runtime to the RevPi: https://revolution.kunbus.com/tutorials/software/rev...

When will CODESYS be supported?

Just to confirm IX agent works well on the RevPI

Hi All, I'm am currently looking for a highly scalable mobile controls and telematics solution for a commercial product. I like the look of the Rev PI, and I've been in touch with the IXON Cloud's support who mentioned that their IX agent could be installed directly on the rev PI. Does anyone have e...