EtherCAT License Error Issue

Runtime 🇬🇧
arj3090
2019-09-12
2019-09-12

  • arj3090 - 2019-09-12

    I am seeing a problem with EtherCAT license error that only occurs when using 3.5.15.10

    If I revert back to 3.5.15.0 , the problem goes away. See attached picture. In the picture all of my EtherCAT devices show the orange circle. Sometime part of the devices will be green and the others orange.

    IMG: V31510Issue.png

     

  • arj3090 - 2019-09-12

    After further testing, this does occur in 3.5.15.0 after rebooting the device. This could be related to installing RT PREEMPT patched kernel. I will test more and report back.

     

  • eschwellinger

    eschwellinger - 2019-09-12

    Hi,
    no.. nothing to do wit rt_preempt.
    -> Check the plc logger.

    BR
    Edwin

     

  • arj3090 - 2019-09-12

    The only pattern so far is connected to the RT PREEMPT patch. I tried 3 different Codesys run-time versions and they all have the issue. I have 2 devices, 1 with RT PREEMPT patch and 1 without. It only happens on the 1 with the PREEMPT patch. Patch version:

    Linux 4.19.59-rt23-v7+

    If I remove the run-time, then install again. The problem is not there until the unit is rebooted.

    I checked the log and I don't see anything abnormal:

    2019-09-12T08:23:29Z, 0x00001005, 1, 0, 0, Networkadapter opened
2019-09-12T08:23:29Z, 0x00001005, 1, 0, 0, Preparation successfull
2019-09-12T08:23:30Z, 0x00001005, 1, 0, 0, Read slave informations
2019-09-12T08:23:36Z, 0x00001005, 1, 0, 0, Set physical addresses
2019-09-12T08:23:36Z, 0x00001005, 1, 0, 0, All slaves init mode
2019-09-12T08:23:36Z, 0x00001005, 1, 0, 0, prepare slaves
2019-09-12T08:23:36Z, 0x00001005, 1, 0, 0, All slaves pre-operational
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, Configure distributed clock settings
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, Synchronize Slaves
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, Set safe operational
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1002 Index: 16#1C12 SubIndex: 0 Data: 16#00 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1002 Index: 16#1C13 SubIndex: 0 Data: 16#00 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1003 Index: 16#1C12 SubIndex: 0 Data: 16#00 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1003 Index: 16#1C13 SubIndex: 0 Data: 16#00 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1003 Index: 16#1C13 SubIndex: 1 Data: 16#1A00 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1003 Index: 16#1C13 SubIndex: 2 Data: 16#1A01 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1003 Index: 16#1C13 SubIndex: 3 Data: 16#1A02 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1003 Index: 16#1C13 SubIndex: 4 Data: 16#1A03 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1003 Index: 16#1C13 SubIndex: 0 Data: 16#04 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1004 Index: 16#1C12 SubIndex: 0 Data: 16#00 Result: 16#00
2019-09-12T08:23:37Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1004 Index: 16#1C13 SubIndex: 0 Data: 16#00 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1002 Index: 16#1C13 SubIndex: 1 Data: 16#1A00 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1004 Index: 16#1C13 SubIndex: 1 Data: 16#1A00 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1004 Index: 16#1C13 SubIndex: 2 Data: 16#1A02 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1004 Index: 16#1C13 SubIndex: 3 Data: 16#1A04 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1004 Index: 16#1C13 SubIndex: 4 Data: 16#1A06 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1004 Index: 16#1C13 SubIndex: 0 Data: 16#04 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1002 Index: 16#1C13 SubIndex: 2 Data: 16#1A01 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1002 Index: 16#1C13 SubIndex: 3 Data: 16#1A02 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1002 Index: 16#1C13 SubIndex: 4 Data: 16#1A03 Result: 16#00
2019-09-12T08:23:38Z, 0x00001005, 1, 0, 0, SDO write ok: Address: 1002 Index: 16#1C13 SubIndex: 0 Data: 16#04 Result: 16#00
2019-09-12T08:23:39Z, 0x00001005, 1, 0, 0, All slaves safe-operational
2019-09-12T08:23:39Z, 0x00001005, 1, 0, 0, Set operational mode
2019-09-12T08:23:39Z, 0x00001005, 1, 0, 0, All slaves operational
2019-09-12T08:23:39Z, 0x00001005, 1, 0, 0, Startup finished: All slaves in operational !
2019-09-12T08:23:57Z, 0x00000007, 1, 0, 6, Network interface: <ipaddress>169.254.149.138</ipaddress>, subnetmask <subnetmask>255.255.0.0</subnetmask>
2019-09-12T08:23:57Z, 0x00000018, 1, 0, 4, Network interface <interface>ether 4</interface> at router <instance>4</instance> registered
2019-09-12T08:23:57Z, 0x00000018, 1, 0, 1, Setting router <instance>4</instance> address to <address>(0000:958a)</address>
2019-09-12T08:24:45Z, 0x00000001, 1, 0, 0, runtime licensed
     

  • arj3090 - 2019-09-12

    This seems to be a problem with one of my devices. I installed the RT PREEMPT patch on the other device and it does not have the problem.

     

Log in to post a comment.