Deploy LicenseServer for Linux SL

jonasz
2025-11-14
2025-11-21
  • jonasz - 2025-11-14

    Hello, I'm asking for help with installing the license server for Linux SL 4.18.0.0.
    When I try to install it, I get a message that the WIBUCodeMeter package is missing.
    I checked the package manager tab to see if the package is installed, and it is - Codemeter 8.40.7120.501.
    I've checked the CodeMeter Runtime on the target machine, and everything seems to be working fine.
    One thing caught my eye: the Device Architecture tab says "None"
    Please help me solve this problem.

     
  • jonasz - 2025-11-14

    So here's how:
    I manually installed the following packages:
    codemeter-lite_8.30.6885.501_amd64.deb
    codesyslicenseserver_licenseserver_4.18.0.0_all.deb
    codesyswbmbase_wbmbase_4.18.0.0_all.deb
    codesyswbmlicensing_wbmlicensing_4.18.0.0_all.deb
    Of course, the license server appeared immediately.
    Trying to install it again using Install in the Deploy tab, the same error appears. Of course, the information that such a server is already installed is also there.

    Configuring PLC, S_PLC, EDGE, and SAFE_TIMER_PROVIDER went smoothly, and basically everything works.

    I wrote a simple program for S_PLC.
    I'm loading the programs into PLC and S_PLC. When loading the program into S_PLC, a message appears stating that there is no connection to the S_PLC controller.

    Timeout error.

    Restart the controller, attempt to load, and see the above.

    After changing the cycle time for S_PLC to 50ms, the problem no longer occurs.

    My question, besides the difficulty of installation for a new user, is what causes the cycle time for S_PLC to be so long, and how can I fix it?

     
  • jonasz - 2025-11-17

    After carefully studying the documentation, I have a question: is a second hardware-independent time source required for the correct operation of the VirtualSafety system?

     
  • eschwellinger

    eschwellinger - 2025-11-17

    yes it is and it need to realtime capable with a preempt_rt patched kernel.

     
  • eschwellinger

    eschwellinger - 2025-11-17

    yes it is and it need to be realtime capable with a preempt_rt patched kernel.

     
    πŸ‘
    1

    Last edit: eschwellinger 2025-11-17
  • jonasz - 2025-11-17

    The machine I'm currently using (Celeron J1900) already has the Kernel RT patch.
    I checked the performance according to the documentation. After running CyclicTest for 4 cores, the value for each core is around 6-7.
    I went through the entire process according to the documentation (I envy the TaskMonitor results in the documentation).

    The documentation states:
    "CODESYS Virtual Safe Time Provider
    The CODESYS Virtual Safe Time Provider is a standard interface that the user can use to transfer a second and external time base to the CODESYS Virtual Safe Control.

    The implementation is done as a client, which must run on another system with an independent time base."

    How do I implement this?
    I've been struggling for two weeks now - I'm too old to give up.

     
  • eschwellinger

    eschwellinger - 2025-11-18

    Hi,
    just use the deploytool to deploy the Timeprovider on this external device:
    An set the IP of you SafeControl PLC

     
    πŸ‘
    1

    Last edit: eschwellinger 2025-11-18
  • jonasz - 2025-11-18

    Hello,

    Basically, everything is clear to me.
    There's still the issue of a TimeProvider for an external device.
    This may be a stupid question, but I can't find this package.
    And of course, the question is, can the RPi machine be an external provider?
    Has anyone tested such a solution?

     
  • eschwellinger

    eschwellinger - 2025-11-18

    for the package you net to install 32bit support(to have the native timprovider availble to deploy)
    sudo apt-get install libc6:i386
    Then native Safeplc and native Safetimeprovider should be available to install.

    Raspi yes - but there is no official package available till now and you need have a rt_preemt patched kernel on the Pi, then it works like charm

     
    πŸ‘
    1

    Last edit: eschwellinger 2025-11-18
  • jonasz - 2025-11-18

    Thank you for the information and support - I need to think this through again.

     
  • jonasz - 2025-11-19

    Good morning,

    I'm digging into this topic because I'm curious about resolving my problem in a test environment.
    In my previous message, I asked about the CODESYS Safe Timeprovider SL package (4.18.0.0), which I saw in the illustration.
    I noticed that it runs as a service.
    I am asking about this because from the perspective of an "ordinary" user, this service provides easier access to the settings of the time provider's operating parameters.
    The basic time provider configuration is outlined at https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_virtual_safe_time_provider.html.

    Why my questions?
    They stem from my specific case, which is experiencing timeout issues.
    I know that my environment is currently only a test environment.
    I'm assuming a real-world scenario in which I won't be able to achieve a better result with my configuration, and I will ultimately need to increase the time provider's cycle time. By running the time provider service, I can easily influence the time provider's operation and thus eliminate the problem. I know, I know, safety systems are not life-enhancing extras.

     
  • eschwellinger

    eschwellinger - 2025-11-20

    As I see from your logs I think the Timeprovider is not accurate enough in your case.
    Things to check - at the moment you run it on the same device? (for tesing purpose ok)
    I would set 127.0.0.0 as IP and set it not really to Core 0 ( many other stuff is there)

     
    πŸ‘
    1
  • jonasz - 2025-11-21

    Thank you for your response. Is there documentation for the commands?
    I spent a lot of time trying to figure this out.
    I have a potato computer at home, so I'll have to test this later.

     

Log in to post a comment.