Post by axberry on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
when is the releaseof the 4.2.0.0
Last updated: 6 days ago

Post by dmb-fan on Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Post)}
Installing SP17 on an old Win10 PC is working. Are there companys out there who can handle installing software on windows ? Siemens: No Dell: No CoDeSys: No
Last updated: 5 days ago

Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Thread)}
Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
Last updated: 5 days ago

Post by dmb-fan on Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Post)}
I had runnig this already. Then I updated to SP22 patch3. After that I got always this error: ===== Project importieren: XXXXnameYYYYYY ===== *[FATALER FEHLER] Fehler beim Import des Projekts: Ausnahmefehler des Servers. * [FATAL ERROR] Error importing the project: Server exception. (Exception to HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) I delete the version and installed again. Same. I uninstalled all CoDeSys on the PC and installed the old SP22 patch2 new. Same error by opening old projects. Immediatly, not by converting. Convert V3.5.17 was always installed. What is happening or what can I do?
Last updated: 5 days ago

Post by dmb-fan on Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Post)}
I try Sandbox. Now I get messages like "Converter is on the blacklist for this version". Online help says nothing about a too high version for the converter. How I can find out the allowed version? Or is this only for sandboxes? what a jungle !
Last updated: 5 days ago

Post by dmb-fan on Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Post)}
Oldest possible Sandbox is not working (Converter blacklistet) Install of SP17 sucessfull. But Same error. And now?
Last updated: 5 days ago

Post by dmb-fan on Attemp Convert old V2.3 projects : Error HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) ^{CODESYS Forge talk (Post)}
EDIT: All 32 Bit Version
Last updated: 5 days ago

Login problem with FileTransfer on Raspberry Pi 5 ^{CODESYS Forge talk (Thread)}
Login problem with FileTransfer on Raspberry Pi 5
Last updated: 1 day ago

Engineering 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Discussions about the CODESYS Development System, IEC programming, CODESYS Professional Developer Edition
Last updated: 1 day ago

Post by jasonhogan on Login problem with FileTransfer on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
That’s a classic CODESYS quirk. As soon as you enable AllowFileTransferServices=1, the web server locks down and demands authentication for everything, including WebVisu sessions. Since you're on a Raspberry Pi / Linux, trying to make the built-in CODESYS web server do both secure file handling and unauthenticated kiosk visu is usually a losing battle. A couple of ways to get around this: The cleaner route (separate the jobs): Turn AllowFileTransferServices back off in the config so your kiosk WebVisu opens freely without any login prompts. Then, handle the file download outside of CODESYS — just run a dead-simple Nginx/lighttpd file server or a tiny Python script on the Pi pointed at your export folder (/var/opt/codesys/...). That way your PLC security stays intact, and the kiosk screen just works. If you really want it through CODESYS: Check your Device -> Users and Groups in the IDE. Make sure the Everyone / Anonymous user group actually has explicit view permissions checked for the Visualization. Sometimes when file services are toggled, anonymous users lose the default visu-read rights and get booted straight to the login dialog. URL / Browser trick for kiosk: If the Pi is just opening a local browser on startup, you can sometimes pass the basic credentials in the browser launch script or use a small reverse proxy on localhost to inject the headers automatically so you don't see the popup. Honestly, running a lightweight HTTP/FTP endpoint on Linux (option 1) is by far the least headache.
Last updated: 1 day ago

Sort by relevance or date