PFC100 SL symbol configuration, var access problem

somlioy
2023-03-08
2023-03-08
  • somlioy - 2023-03-08

    Hi

    I'm having problem accessing published variables from a PFC100 Symbol Configuration on a Exor JMobile HMI.
    The PFC100 is running FW19, device description version 4.7.0.0. Using compiler 3.5.18.40.

    I'm noticing the following in the PLC log when the HMI is trying to get data. This is repeating at every reconnection from the HMI.

    CmpDevice: Session not available anymore!
    CmpSrv: Invalid session ID. No other session on this channel, close it.
    

    The HMI is opening a channel, but this is closing and repoening repeatedly.

    CmpChannelServer channel information:
    Maximum 4 channels (at timestamp 262674)
       Channel 0: OPEN     PROCESSING  AddrPeer FA31.0A0A.0A01.0337, ChannelId 18756, ComBufferSize 95768, LastRxTime 262674, LastTxTime 262662
       Channel 1: OPEN     PROCESSING  AddrPeer 01D3, ChannelId 60525, ComBufferSize 32768, LastRxTime 262059, LastTxTime 262266
       Channel 2: FREE     
       Channel 3: FREE   
    

    This is from the HMI log where you can see there's an timeout. The HMI is able to connect to the PLC, because if the PLC ethernet physically disconnected or PLC is offline, the error changes to "Can't connect socket";

    <14>Mar  8 20:01:08 0.0.0.0  idal[0x53a]: BaseProtocol: [prot1,CDS3,0] read datagram [Application/PLC_PRG/xBool] failed - Error: timeout on answer
    

    I've tried the same PLC program on a PFC200 with the new FW23 from Wago running codesys 3.5, and the HMI works correctly there.

    Is there anything I'm missing with the PFC100 SL container?

     
  • somlioy - 2023-03-08

    I just noticed in the audit log the following error message on each retry from HMI:
    CmpDevice: System, Device login from 01D3 failed.

    So I guess it has something to do with user management?

     
  • somlioy - 2023-03-08

    I just noticed in the audit log the following error message on each retry from HMI:
    CmpDevice: System, Device login from 01D3 failed.

    So I guess it has something to do with user management?

     

Log in to post a comment.