# Library "WagoAppPLCInfos\_FR.FbSystemInfo"

**URL:** <https://www.wago.community/t/bibliotheque-wagoappplcinfos-fr-fbsysteminfo/2702>\
**Category:** CODESYS\
**Created:** [April 29, 2026, 1:50pm UTC](https://www.wago.community/t/bibliotheque-wagoappplcinfos-fr-fbsysteminfo/2702 "2026-04-29T13:50:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![saouali](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@saouali](https://www.wago.community/u/saouali)\
**Post date:** [April 29, 2026, 1:50pm UTC](https://www.wago.community/t/bibliotheque-wagoappplcinfos-fr-fbsysteminfo/2702/1 "2026-04-29T13:50:24Z")

</div>

Hello,

I have a question regarding the “WagoAppPLCInfos\_FR.FbSystemInfo” library in CoDeSys V3.5 SP21 PATCH 3. I am able to add this library and retrieve the PLC information.

However, for CoDeSys V3.5 SP19 PATCH 7, even after adding this library, I encounter library errors. Is there a solution or another library compatible with SP19 PATCH 7 to retrieve this information (firmware version, PLC model, K-bus error code)?

Thank you in advance for your help.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/7/7eb53f4de31a73701f5a0296c82e8ea679e9e063.png)

Best regards,

---

<div class="post-metadata">

**Author:** ![WagoDamRud](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagodamrud/32/258_2.png) [@WagoDamRud](https://www.wago.community/u/WagoDamRud)\
**Post date:** [May 5, 2026, 9:18am UTC](https://www.wago.community/t/bibliotheque-wagoappplcinfos-fr-fbsysteminfo/2702/2 "2026-05-05T09:18:17Z")

</div>

Can you paste information from Messages window?

---

<div class="post-metadata">

**Author:** ![saouali](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@saouali](https://www.wago.community/u/saouali)\
**Post date:** [May 18, 2026, 11:35am UTC](https://www.wago.community/t/bibliotheque-wagoappplcinfos-fr-fbsysteminfo/2702/3 "2026-05-18T11:35:13Z")

</div>

Hello, thank you for the response: Ultimately, the problem was my working environment, so the issue is resolved.
