Double event entry in event recorder when event text contains a variable text via placeholder {0}

[Tardigrade]

We are using Event Recorder App V1.5.5 on a machine. I noticed that whenever I set an event with text that contains a place holder {0} and clear the event in the next step.  I always get minimal 2 entrys in the event recorder. I also tried waiting 2 seconds between set and clear event but i still get minimal 2 event in the event recorder. The only way to prevent it, is to remove the place holder {0} then everything works fine, but I need that place holder for the variable data. Is there some way to prevent this double entry and use the place holder?

[nexidator]

This looks really weird, but actually I am quite sure there is no general problem with event texts using {0}.

• What version of the EventRecorder Service (= Runtime) are you using?
• Can you post the source code of the step where you set the event?

(Alternatively, you can contact our helpdesk so we can give you directions how you can send us your project for analysing the behavior.)

[Tardigrade]

Event runtime version seems to be V 1.5.5.4

The even recorder app seems to be V1.5.5

step N246:

// Info Message with current holder nr: if holder was changes
IF ( YZAxis.Unit.OutCmd.HolderNo = _holderNoMemory )
THEN
  _retVal := OK;
ELSE
  IF (_eventPlc = 0)
  THEN
    _eventPlc := SetEvent(OpconEventClass.INFO, INFO_HOLDER_NR, INT_TO_STRING(YZAxis.Unit.OutCmd.HolderNo), Lock:= FALSE);
    _holderNoMemory := YZAxis.Unit.OutCmd.HolderNo;
    _retVal := OpconSetTimeout(_waitTimeEvent,_waitTimer);
  ELSE
    _retVal := RUNNING;
  END_IF
END_IF

step N247:

// Clear holder Nr info message
IF (_eventPlc <> 0)
THEN
  IF ( OpconCheckTimeout(_waitTimer) = OK )
  THEN
    ClearEvent(OpconEventClass.INFO, _eventPlc);
    _eventPlc := 0;
    _retVal := OK;
  ELSE
    _retVal := RUNNING;
  END_IF
ELSE
  _retVal := OK;
END_IF

[nexidator]

Thanks for posting your code. As expected, it doesn't look like it can be the reason for the duplicate entry. (I am not sure if  "ELSE _retVal:=RUNNING" in the first step makes much sense, but I don't see how it could run into this line anyway.)

One thing I forget to ask: Does the event appear twice in the HMI as well? I guess not, and otherwise this must really be a problem of the EventRecorder service.

Can you try if it helps to update to the latest version of the EventRecorder service (V1.5.9)? I have seen in the change history that some bugs have been fixed since the version you are using.

[Tardigrade]

I Installed the new version of eventrecorder service V1.5.9.1 and event recorder app V1.5.7.7 , export, deployed including std. but the result stays the same.

On the HMI I only see one Message.