Hello everybody,
We are experencing a strange issue.
First of all we we successfully able to import both our RevPi Connect 4 and our DI Module into Codesys.
But as we tried to use these the behaviour was unexpected.
We tried to use the modules (as shown in documentation by kunbus) without any configuration in Pictory, but with no luck
See Screenshots...
We tried the official troubleshooting guide, with no luck.
The only small luck we had way after we configured the modules in Pictory, but this resulted in the end in very funny behaviour of the inputs.
The funny behaviour:
- we gave power to IN_CH2 and the IN_CH13 went to true.
- all inputs that had variables configured already in codesys went to <bad>
This happened with multiple modules and RevPi Connects.
Do you have any idea how to resolve this issue?
Any help would be very appreciated...
Funny behaviour of inputs
Hi,
Are you using 1.4.1.99 beta version of Revolution Pi Library for CODESYS?
For Connect 4 with RevPi Bullseye Image (64 bit) you need to use
CODESYS Control Linux ARM 64 bit.
There may be some incorrect device tree combination in your configured project.
I would recommend to first create a new Connect 4 Test project with DI module,
manually configure appropriate PlaceholderFilePath in /etc/CODESYSControl_User.cfg
For CODESYS Control for Linux ARM (32 bit and 64 bit) V4.10.0.0 or higher
[SysFile]
PlaceholderFilePath.1=/etc/revpi, $configrsc$
For CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 or higher
Do system restart or restart codesyscontrol as stated in release notes.
Then check if module not found (Kein Treiber gefunden) erros is shown in CODDESYS device tree and test the Digital Inputs.
Regards, Amar
Are you using 1.4.1.99 beta version of Revolution Pi Library for CODESYS?
For Connect 4 with RevPi Bullseye Image (64 bit) you need to use
CODESYS Control Linux ARM 64 bit.
There may be some incorrect device tree combination in your configured project.
I would recommend to first create a new Connect 4 Test project with DI module,
manually configure appropriate PlaceholderFilePath in /etc/CODESYSControl_User.cfg
For CODESYS Control for Linux ARM (32 bit and 64 bit) V4.10.0.0 or higher
[SysFile]
PlaceholderFilePath.1=/etc/revpi, $configrsc$
For CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 or higher
Do system restart or restart codesyscontrol as stated in release notes.
Then check if module not found (Kein Treiber gefunden) erros is shown in CODDESYS device tree and test the Digital Inputs.
Regards, Amar
KUNBUS
-
- Posts: 2
- Joined: 26 Mar 2024, 15:31
Sadly as in the documentation is stated that 64Bit is not supported we are using 32Bit.
As such the 64Bit Library won’t help us much.
Any other ideas? Also if we don’t configure the systems in Pictory the device is always shown as missing.
As such the 64Bit Library won’t help us much.
Any other ideas? Also if we don’t configure the systems in Pictory the device is always shown as missing.
Hi,
the 64 Bit library is about to be released in April. At the moment it is not officially supported, because there is no release yet.
Nicolai
the 64 Bit library is about to be released in April. At the moment it is not officially supported, because there is no release yet.
Nicolai