Digital output is not working.

[hartingwada]

Dear KUNBUS

Our VIP Car manifactures has a below trouble now.
Please teach us solution.

System: Revpi Connect+ 8G + DIO
App: Codesys V.3.5.16.1
Trouble: Digital output is not working.

We refered following site and check IO.
viewtopic.php?t=1979
RevPiLib CodesysV3.5 SP16-Beta-Test version.zip
(64.5 KiB) Downloaded 143 times
It is OK for only Codesys monitor, actual Digital output is not working.
In this meaning, Digital input is OK for display and actual hardware, but Digital output is not working actual hardware.
We mistake to correct working only Codesys Display.
You can check actual output! And teach us solution.

Best Regards,
Jo Wada

[dirk]

Der Jo Wanda, you need an update of the RevPiLib which is not yet officialy released.
I'll contact you via PM.

[hartingwada]

Dear Dirk

Thank you very much for your help.
I heard from our PM that it's working now.

Can I ask 1 more question?
When would the it be official release?
If there are any information about it I want to share.

Best Regards,
Jo Wada

[dirk]

Dear Jo Wanda I got the information that it will be ready by the next week.

[Jk#312]

Hi Dirk,

We have a question about the revpi lib package.
We wanted to test the outputs of our program but when we used putty we could activate the outputs and it works.
But when we use codesys the outputs won't activate they give 0 V.

In a comment above the new package would be available next week. But when we download it is still the same package.
When would the new package available for download?

Yours sincerely,

Jeroen

[Amar]

Please use the latest available versions:
Revolution Pi Library for CODESYS V1.3.0.0
https://revolutionpi.com/tutorials/downloads/

CODESYS Control for Raspberry Pi 4.8.0.0
https://store.codesys.com/en/codesys-co ... mc-sl.html

CODESYS V3.5 SP19
https://store.codesys.com/codesys.html

Release Note

CODESYS V3.5 SP19 includes a bug fix. CDS-81506: CODESYS Control SysFile
system file access vulnerability.ForceIecFilePath is activated by default, due to which file access from IEC is now restricted to the configured paths only (file sandbox).

For more details, see Advisory 2023-01, which is available on the CODESYS website:

https://customers.codesys.com/index.php ... &download=

Release notes for CODESYS V3.5 SP19
https://www.codesys.com/fileadmin/data/ ... 35190.html

In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is required in order to create a config.rsc file based on devices configured in the CODESYS application project. The CODESYS project using the KUNBUS RevolutionPiBridge IO library creates a configuration file /etc/revpi/config.rsc, which is basically the PiCtory file /var/www/revpi/pictory/projects/_config.rsc.

Customers using Revolution Pi CODESYS devices will therefore have to manually configure PlaceholderFilePath in /etc/CODESYSControl_User.cfg as mentioned below.

Code: Select all

[SysFile]
PlaceholderFilePath.1=/etc/revpi, $configrsc$

Restart CODESYS Control in order to load the new changes from /etc/CODESYSControl_User.cfg.
Alternatively, you could reboot the device, and the changes will be automatically loaded from the user configuration file at the start of CODESYS Control.

Code: Select all

sudo service codesyscontrol restart

Troubleshpoting tips for DIO Output:

1) After running the CODESYS application program check if DIO module is found and listed with command
piTest -d

DIO troubleshooting.png (10.13 KiB) Viewed 5866 times

2) Update the DIO firmware to the latest version (V1.5 as of now)
https://revolutionpi.com/tutorials/imag ... re-update/

3) If DIO module is still not found, then check the piBridge connection.
Check the status LEDs of DIO
https://revolutionpi.com/tutorials/over ... dio-di-do/

Regards
Amar