Personal Data

Username:
aliazzz
Joined:
2018-09-17 16:38:21
Location:
CET

Projects

User Activity

  • Modified a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    Hi CODESYS team! It seems Podman for Raspberry Pi 3 is not detected correctly in the latest "Deploy Control SL 4.14.0.0" : Linux/ARMHFv7 unknown container technology. 1) The Communication Tab, device information section shows podman technology as DETECTED. 2) The Runtime Deployment menu message says: "unknown container architecture" 3) The pulldown window under the deployment tab doesn't show the options for ARMHF Virtual Edge SL and ARMHF Virtual Control SL. I hope you can fix this soon and keep...

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    Hi, It seems Podman for Raspberry Pi 3 is not detected in the latest "Deploy Control SL 4.14.0.0" : Linux/ARMHFv7 unknown container technology I used a RPi3 with "Cockpit", "Podman" and "Podman for Cockpit plugin" which all work fine.

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    Hi! After upgrading all my licensed runtimes to V4.14.0.0 (= RaspberryPi SL, LinuxSL and ControlWin x64 SL) I found out via the logfiles they all defaulted back into DEMO mode while all runtimes have a USB dongle inserted. So, my main question is how I can get the Dongle license detected? I use License Server 4.14.0.0 and Edge Gateway 4.14.0.0 on all platforms Any suggestions are welcome.

  • Modified a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    An interesting remark for CODESYS Support. I found this after looking through the Runtime Deploy Tool messages when I connect to an AMD64 architecture Successfully Connected to Target ( {MyIP} - AMD64 ) when I connect to an ARM64 architecture (Raspberry Pi5) Successfully Connected to Target ( {MyIP} - ) As clearly seen in the attached .png, the AMD64 target is detected, while the ARM64 target architecture is not detected (displayed). I assume that this is the reason why the pulldown menu isn't populated...

  • Modified a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    Hi, I have successfully deployed "Virtual Control SL" on a few x86/64 machines now. However, I'd now like to deploy this to a Raspberry Pi (ARM64). To do this I prepared the Raspberry Pi5 with the following prereq's; * Minimal PREEMPT Debian * Latest Bootfirmware * full SSH access via non-root account * Podman * RedHat Cockpit with CODESYS LicensServer plugin up and running However, I can't seem to resolve copying the correct (deploy) Images as they wont show up in the CODESYS IDE I have added CODESYS...

  • Modified a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    An interesting remark for CODESYS Support. I found this after looking through the Runtime Deploy Tool messages when I connect to an AMD64 architecture Successfully Connected to Target ( {MyIP} - AMD64 ) when I connect to an ARM64 architecture (Raspberry Pi5) Successfully Connected to Target ( {MyIP} - ) As clearly seen in the attached .png, the AMD64 taget is detected, while the ARM64 target architecture is not displayed which is, I assume probably the reason why the pulldown menu isn't populated...

  • Modified a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    An interesting remark for CODESYS Support. I found this after looking through the Runtime Deploy Tool messages when I connect to an AMD64 architecture Successfully Connected to Target ( {MyIP} - AMD64 ) when I connect to an ARM64 architecture (Raspberry Pi5) Successfully Connected to Target ( {MyIP} - ) As clearly seen in the attached .png, the ARM64 target architecture is not displayed which is, I assume probably the reason why the pulldown menu isn't populated correctly (?)

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    An interesting remark for CODESYS Support; I found this feedback after looking through the Runtime Deploy Tool messages when I connect to a AMD64 architecture Successfully Connected to Target ( {MyIP} - AMD64) when I connect to a ARM64 architecture (A RaspBerryPi5) Successfully Connected to Target ( {MyIP} - ) As seen in the attached .png

View All