Announcement

Collapse
No announcement yet.

Decoding P2K Error / Event history errors

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts


  • Decoding P2K Error / Event history errors

    Had a customer call today that their system wasn't responding. I remotely logged in and saw that it was in STOP mode. I know the facility, I built it the panel. It is not accessible by anyone without some significant work, so I know it was not a human that put it in to STOP mode.

    Copy and paste from the project report;

    Critical Error History
    E02302 Module Missing G000B01S01, 22NOV16, 00:41:29
    E02302 Module Missing G000B01S06, 17NOV16, 14:53:17
    E02302 Module Missing G000B01S07, 11NOV16, 19:02:39
    E02302 Module Missing G000B01S04, 10NOV16, 02:53:32
    E02302 Module Missing G000B01S03, 10NOV16, 02:53:32
    E02302 Module Missing G000B01S04, 08NOV16, 06:31:24

    Non-Critical Error History
    E01602 File open error IMM0FTxBeg, 23JAN18, 17:16:39
    E02101 Module IO StatusG000B01S05, 22DEC17, 21:24:36
    E02101 Module IO StatusG000B01S03, 22DEC17, 21:23:55
    E02101 Module IO StatusG000B01S03, 22DEC17, 21:21:12
    E02101 Module IO StatusG000B01S05, 22DEC17, 21:19:28
    E02101 Module IO StatusG000B01S03, 22DEC17, 21:19:25
    E02101 Module IO StatusG000B01S05, 20DEC17, 18:17:08
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:17:07
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:17:05
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:17:03
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:17:01
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:59
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:57
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:55
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:53
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:51
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:49
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:47
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:45
    E02101 Module IO StatusG000B01S03, 20DEC17, 18:16:43

    Event History
    EXTRACT G00B01S00 104.231.89.133 , 23JAN18, 17:16
    RUN G00B01S00 104.231.89.133 , 23JAN18, 17:04
    STOP G00B01S00 104.231.89.133 , 23JAN18, 17:04
    NEW PROJ G00B01S00 104.231.89.133 , 23JAN18, 17:04
    RUN G00B01S00 104.231.89.133 , 23JAN18, 17:02
    EXTRACT G00B01S00 104.231.89.133 , 23JAN18, 16:56
    EXTRACT G00B01S00 104.231.89.133 , 23JAN18, 16:55
    STOP G00B01S00 99.122.62.235 , 22JAN18, 10:15
    EXTRACT G00B01S00 99.122.62.235 , 22JAN18, 10:13
    RUN switch , 05DEC17, 20:41
    System started 1.2.2.64 , 05DEC17, 20:41
    EXTRACT G00B01S00 71.182.157.8 , 05DEC17, 17:39
    RUN switch , 27NOV17, 07:43
    System started 1.2.2.64 , 27NOV17, 07:43
    RUN switch , 12NOV17, 08:59
    System started 1.2.2.64 , 12NOV17, 08:59
    EXTRACT G00B01S00 174.227.138.172 , 24OCT17, 18:48
    COMM LOST G00B01S00 USB , 24OCT17, 18:48
    EXTRACT G00B01S00 USB , 24OCT17, 18:43
    RUN switch , 24OCT17, 18:41

    PAC Date and Time
    1/23/2018 17:16:39

    The critical errors were resolved already, it was a bad card if memory serves me. I've attempted to pull up every MST bit that I can find to see what was causing the E02101 errors, but I can't find any that are set, other than the ones that should be on (since there is a matching MST bit for any associated physical output)

    What I'm more concerned with are these;

    EXTRACT G00B01S00 104.231.89.133 , 23JAN18, 16:56
    EXTRACT G00B01S00 104.231.89.133 , 23JAN18, 16:55
    STOP G00B01S00 99.122.62.235 , 22JAN18, 10:15
    EXTRACT G00B01S00 99.122.62.235 , 22JAN18, 10:13

    There is nothing in the manual on how to decode what the "G00B01S00" string means. Tech support doesn't know either, though it's supposedly getting worked up the chain.

    Any help?


  • #2
    G00B01S00
    local Group 00
    Base 01
    Slot 00

    [EDIT] Help Topic Reference See Help topic P239 - look for Current I/O Config Error [Group|Base|Slot] entries about half way down.



    EXTRACT G00B01S00 104.231.89.133 , 23JAN18, 16:56
    A programming device (PC) at IP Address 104.... connected to the LOCAL BASE CPU -- went online and transferred the project FROM the CPU on that date/time

    EXTRACT G00B01S00 104.231.89.133 , 23JAN18, 16:55
    And another online transfer from CPU

    STOP G00B01S00 99.122.62.235 , 22JAN18, 10:15
    A programming/comms(?) device (PC) at IP Address 104.... connected to the LOCAL BASE CPU -- put the CPU into STOP mode.
    This doesn't appear to be a program transfer TO CPU
    Also, if someone had physically toggled the STOP/RUN switch, that text would have been in this list, too.

    EXTRACT G00B01S00 99.122.62.235 , 22JAN18, 10:13
    And another online transfer from CPU
    Last edited by kewakl; 01-24-2018, 05:35 AM.

    Comment

    Working...
    X