The Industrial Raspberry Pi Forum

Several days ago, I can connect to my devices via serial coms successfully. But I do not know what I changed, and there are several problems. I can not connect to my devices via serial coms, and I can not read data from IOs of MIO and DIO.
Then I piTest via SSH and found the modules are present but not configured.

pi@RevPi20726:~ $ piTest -d
Found 3 devices:

Address: 0 module type: 105 (0x69) RevPi Connect V1.0
Module is present, but NOT CONFIGURED!!!
input offset: 0 length: 6
output offset: 6 length: 5

Address: 31 module type: 96 (0x60) RevPi DIO V1.5
Module is present, but NOT CONFIGURED!!!
input offset: 11 length: 70
output offset: 81 length: 18

Address: 30 module type: 118 (0x76) RevPi MIO V1.0
Module is present, but NOT CONFIGURED!!!
input offset: 99 length: 34
output offset: 133 length: 27


Please help me with the problem, thanks.

Hello Yongchaow,

please have a look the Codesys checklist.
What do you means with "serial coms". Do you get an error message when you try to connect to the unit?

Best Regards

Ulrich Kouatang Biakoup | Technical Support

u.biakoup wrote: ↑24 Mar 2023, 11:53 Hello Yongchaow,

please have a look the Codesys checklist.
What do you means with "serial coms". Do you get an error message when you try to connect to the unit?

Best Regards

Ulrich Kouatang Biakoup | Technical Support

I have check the checklist:
1. CODESYS Control for Raspberry Pi MC SL - 4.6.0.0 : I use 4.7.0.0, I think this is not the problem because I have successed to connect to my device in this version (4.7.0.0)
2. Driver RevolutionPiBridgeV1.2.1.0 : I use V1.2.0.0. Today, I update the version to V1.2.1.0, I hope this will work.
3. I did not install CODESYS Control for Raspberry Pi MC SL - 4.4.0.0 (ID: 12071).

"serial coms" are the interfaces of serial communication. I use RS485 interface and a USB interface of Revolution Pi Connect.

u.biakoup wrote: ↑24 Mar 2023, 11:53 Hello Yongchaow,

please have a look the Codesys checklist.
What do you means with "serial coms". Do you get an error message when you try to connect to the unit?

Best Regards

Ulrich Kouatang Biakoup | Technical Support

I found a reason but not all. I solved the serial communication problem. Because these lines:
[SYScom]
Linux.Devicefile=/dev/ttyUSB
in CODESYSControl.cfg was deleted and /dev/ttyUSB0, USB1, USB2 changed to ttyUSB1, USB2,USB3. I changed them and reboot to solve the communication problem via RS485 and USB1.

But the red triangle before MIO and DIO are still exist. Should I change CODESYS Contral of Raspberry 4.7.0.0 to 4.6.0.0?

u.biakoup wrote: ↑24 Mar 2023, 11:53 Hello Yongchaow,

please have a look the Codesys checklist.
What do you means with "serial coms". Do you get an error message when you try to connect to the unit?

Best Regards

Ulrich Kouatang Biakoup | Technical Support

Hi, Ulrich
I have finish the checklist,
1. RevolutionPiBridgeV1.2.1.0
2. CODESYS Control for Raspberry Pi MC SL - 4.6.0.0
3. CODESYS Runtime V3.5.18 (V3.5 SP18 or an older version)
But the problem is still here. And I did not get an error message when I tried to connect to MIO and DIO. Could you please help me to solve the problems?

Regard,
Yongchaow

I found the reason.
In Pictory, I reconfig the RevPi connect, MIO, and DIO. I can connect them succefully. But I can not communication with my devices (Flow meter) via RS485.
Then I open /etc/CODESYSControl.cfg and Add

[SysCom]
Linux.Devicefile=/dev/ttyUSB

MIO and DIO did not work, and the serial communication via RS485 works.

So Could you please tell me how to solve the problem?

Thanks,
Yongchaow

Hi yongchaow,

Please use Revolution Pi Library for CODESYS V1.3.0.0 (ID: 4712) not RevolutionPiBridgeV1.2.1.0.
CODESYS Runtime V3.5.18 is only compatible with CODESYS Control for Raspberry Pi MC SL - 4.6.0.0 and Revolution Pi Library for CODESYS V1.3.0.0 (ID: 4712).

Please, make sure that you have the suitable setup.

Best Regards

Ulrich Kouatang Biakoup | Technical Support