License Problems

2020-04-28
2020-04-29
  • hence.persson - 2020-04-28

    I installed and licensed a Raspberry SL yesterday. After a power off the license was lost.. (Power off by linux shutdown). I had the license files backed up so no worries.. I thought..

    Now i cant get the license to work I have tried the old way (.tar file to restore folder) and the new way (License manager -- Restore).. Cant get it to work.
    Yes I have tried deleting the cmact_licenses folder before restoring, deleted it restarted the codesys control etc.

    Even tried to remove and install the runtime again.

    Strange things

    1. In the license manager the window is empty (Se attached pictures) shouldnt there be a Runtime entry there?
    2. Strange error message when trying the option of installing the license update file.. (See picture)

    Please help.

    processor   : 0
    model name  : ARMv7 Processor rev 4 (v7l)
    BogoMIPS    : 76.80
    Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
    CPU implementer : 0x41
    CPU architecture: 7
    CPU variant : 0x0
    CPU part    : 0xd03
    CPU revision    : 4
    processor   : 1
    model name  : ARMv7 Processor rev 4 (v7l)
    BogoMIPS    : 76.80
    Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
    CPU implementer : 0x41
    CPU architecture: 7
    CPU variant : 0x0
    CPU part    : 0xd03
    CPU revision    : 4
    processor   : 2
    model name  : ARMv7 Processor rev 4 (v7l)
    BogoMIPS    : 76.80
    Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
    CPU implementer : 0x41
    CPU architecture: 7
    CPU variant : 0x0
    CPU part    : 0xd03
    CPU revision    : 4
    processor   : 3
    model name  : ARMv7 Processor rev 4 (v7l)
    BogoMIPS    : 76.80
    Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
    CPU implementer : 0x41
    CPU architecture: 7
    CPU variant : 0x0
    CPU part    : 0xd03
    CPU revision    : 4
    Hardware    : BCM2835
    Revision    : a02100
    Serial      : 00000000e2b7a316
    Model       : Raspberry Pi Compute Module 3 Plus Rev 1.0
    
    can0: flags=128<NOARP>  mtu 16
            unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    can1: flags=128<NOARP>  mtu 16
            unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
            device interrupt 170  
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.119.1  netmask 255.255.255.0  broadcast 192.168.119.255
            inet6 fe80::7335:6c91:e82f:8763  prefixlen 64  scopeid 0x20<link>
            ether 96:11:64:27:77:64  txqueuelen 1000  (Ethernet)
            RX packets 24042  bytes 6572529 (6.2 MiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 23313  bytes 3203855 (3.0 MiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
            ether 82:c1:ab:f1:d4:92  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    eth2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
            ether 8a:18:aa:00:94:7e  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 100  bytes 4992 (4.8 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 100  bytes 4992 (4.8 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    192.168.119.0   0.0.0.0         255.255.255.0   U     202    0        0 eth0
    
    Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
    ||/ Name           Version      Architecture Description
    +++-==============-============-============-=========================================
    ii  codesyscontrol 3.5.15.10    all          V3.5.15.10, Mo 16. Sep 21:05:04 CEST 2019
    
    2020-03-28T16:10:28Z, 0x0000007a, 4, 1, 0, **** ERROR: Install license file 'CMLicenseNew.WibuCmRaU' failed
    2020-03-28T16:10:28Z, 0x0000007a, 4, 1, 0, **** ERROR: CM SDK: No error occurred, Error 0.
    
     
  • eschwellinger

    eschwellinger - 2020-04-28

    Hi,
    please write to the CODESYS Store -> my question
    should work that way.

     
    • hence.persson - 2020-04-29

      Its my customer that has bought the licenses, will ask there as soon as i get the login.. But a small question..

      The customers hardware is special built using a rpi cm3 module and at the moment the hardware does not have a "real" MAC address.

      The MAC address is randomized at each start.. Could that be the problem (We do not change hardware but maybe the license uses the MAC address amongst other things to identify a specific hardware)?

      The customer has bought a range of MAC addresses now so we could set a fixed MAC address if this is the case.

       
  • eschwellinger

    eschwellinger - 2020-04-29

    Yes, for sure mac address is involved..

     

    Last edit: eschwellinger 2020-04-29

Log in to post a comment.