Codesys Control for Raspberry MC stops without error...

2022-07-29
2022-09-03
  • w.romiguieres - 2022-07-29

    Hello,

    I wanted to use my RPI as a Profinet Master, so I just purchased and installed "CODESYS Control for Raspberry Pi MC SL" and load my Codesys project into it.

    It works, but sometimes (after 1 to 3 hours) the PLC stops by itself without error in the log file (only "CODESYS Control shutdown...").

    Here is the latest log after a crash (/tmp/codesyscontrol.log):

    2022-07-29T08:58:36Z, 0x00000001, 1, 0, 34, CODESYS Control ready
    2022-07-29T08:58:36Z, 0x00000001, 1, 0, 0, runtime licensed
    2022-07-29T08:58:38Z, 0x000010a2, 1, 33554432, 0, Station 'infranordrv': Connecting...
    2022-07-29T08:58:38Z, 0x000010a2, 1, 33554432, 0, Station 'infranordrv': Received Connect Confirmation
    2022-07-29T08:58:38Z, 0x000010a2, 1, 33554432, 0, Station 'infranordrv': Received Prm-End Confirmation
    2022-07-29T08:58:38Z, 0x000010a2, 1, 33554432, 0, Station 'infranordrv': Received Application-Ready Indication
    2022-07-29T08:58:38Z, 0x000010a2, 1, 33554432, 0, Station 'infranordrv': Data Exchange
    2022-07-29T08:58:38Z, 0x000010a2, 1, 50331648, 0, Station 'infranordrv': Connected
    2022-07-29T09:28:36Z, 0x0000100d, 1, 0, 0, Demo mode expired.
    2022-07-29T09:28:36Z, 0x0000100d, 4, 0, 0, **** ERROR: Demo mode for IO-Link expired. Feature stopped!
    2022-07-29T09:28:36Z, 0x0000100d, 4, 0, 0, **** ERROR: License for IO-Link not installed.
    2022-07-29T10:33:16Z, 0x00000001, 1, 0, 35, CODESYS Control shutdown...
    2022-07-29T10:33:17Z, 0x00000114, 2, 1, 0, !!!! Warning: SysTaskJoin [CMCommCycleTask]: error Connection timed out
    2022-07-29T10:33:17Z, 0x00000124, 1, 0, 0, Provider 'AlarmManager' (version 0x3051200) unregisterd at the OPC UA server.
    2022-07-29T10:33:17Z, 0x00000114, 2, 1, 0, !!!! Warning: SysTaskExit [Profinet_CommunicationTask]: lostcycles: [4204037]
    2022-07-29T10:33:17Z, 0x000010a2, 1, 16777216, 1, Reset Configuration
    2022-07-29T10:33:20Z, 0x00000124, 1, 0, 0, Provider 'AddressSpaceFragment Provider' (version 0x3051200) unregisterd at the OPC UA server.
    2022-07-29T10:33:20Z, 0x00000124, 1, 0, 0, Provider 'OPC UA for IEC-61131-3' (version 0x3051200) unregisterd at the OPC UA server.
    2022-07-29T10:33:20Z, 0x00000018, 1, 0, 5, Network interface <interface>BlkDrvTcp</interface> unregistered
    2022-07-29T10:33:20Z, 0x00000124, 1, 0, 0, Provider 'CODESYS_DefaultProvider' (version 0x3051200) unregisterd at the OPC UA server.
    2022-07-29T10:33:20Z, 0x00000124, 1, 0, 0, ********************** Server OPC UA stopped! *************************
    2022-07-29T10:33:20Z, 0x00000018, 1, 0, 5, Network interface <interface>ether 1</interface> unregistered
    2022-07-29T10:33:20Z, 0x00000018, 1, 0, 5, Network interface <interface>ether 2</interface> unregistered
    2022-07-29T10:33:20Z, 0x00000018, 1, 0, 5, Network interface <interface>ether 3</interface> unregistered
    

    Could you help me please? It is very (very!) annoying and I haven't found a solution for a few weeks...

    I use CODESYS Control for Raspberry Pi MC SL v4.5.0.0 and CODESYS Edge Gateway for Linux v4.5.0.0 too.

    Thanks!

    W.ROMIGUIERES
    INFRANOR SAS

     
  • pruwetbe - 2022-09-03

    hello,
    i have similar problem these last week. i am running a older version of rpi MC ( 4.0.0.0) on powerIO H1M100.
    in my case, i even have no message recorded at all, new messages are logged only when a reboot is triggered.
    i also have OPC UA communication with another rpi where i run nodered . i monitor the status of the communication to inform me when the system stop working sending a notification by telegram...
    the app was running for month without major trouble.
    i did only minor changes in the last week. i still wondering what could cause such stop.
    the load of my cpu is very low

     
  • pruwetbe - 2022-09-03

    hello,
    i have similar problem these last week. i am running a older version of rpi MC ( 4.0.0.0) on powerIO H1M100.
    in my case, i even have no message recorded at all, new messages are logged only when a reboot is triggered.
    i also have OPC UA communication with another rpi where i run nodered . i monitor the status of the communication to inform me when the system stop working sending a notification by telegram...
    the app was running for month without major trouble.
    i did only minor changes in the last week. i still wondering what could cause such stop.
    the load of my cpu is very low

     

Log in to post a comment.