Revpibridge error :error code 8453
Posted: 06 Jan 2025, 11:12
I'm writing to get technical support for a problem I'm experiencing.
I am using a Revpi Connect+ (Computer module 3) in which I recently installed your most recent Revpi Bullseye armhf image (32bits) as shown in one of the attached image. The Revpi is physically connected to two DIO modules with the appropriate connectors (pibridge left and pibridge end).
Then I created a project with the latest version of CODESYS V3.5 SP20 Patch 4 in which I deployed the packages necessary to deploy CODESYS Control (Codesys Control for Linux ARM SL , CODESYS Edge Gateway for Linux) and also your library Revolutionpibridge V 2.0.0
All these steps went smoothly but when I load my project the pibridgeleft and pibridgeright components are in error in the component tree. In the logs I get this error: ‘Errorcode 8453: No valid RevPi Base device found in codesys device tree Connection’. I suspected a configuration conflict with Pictory but the error doesn't seem to be coming from there, especially as your latest package versions are supposed to have solved this problem.
The attached images illustrate the situation, and I remain at your disposal should you require any further information.
I am using a Revpi Connect+ (Computer module 3) in which I recently installed your most recent Revpi Bullseye armhf image (32bits) as shown in one of the attached image. The Revpi is physically connected to two DIO modules with the appropriate connectors (pibridge left and pibridge end).
Then I created a project with the latest version of CODESYS V3.5 SP20 Patch 4 in which I deployed the packages necessary to deploy CODESYS Control (Codesys Control for Linux ARM SL , CODESYS Edge Gateway for Linux) and also your library Revolutionpibridge V 2.0.0
All these steps went smoothly but when I load my project the pibridgeleft and pibridgeright components are in error in the component tree. In the logs I get this error: ‘Errorcode 8453: No valid RevPi Base device found in codesys device tree Connection’. I suspected a configuration conflict with Pictory but the error doesn't seem to be coming from there, especially as your latest package versions are supposed to have solved this problem.
The attached images illustrate the situation, and I remain at your disposal should you require any further information.