Description

The MqttHistoryTester is used to check that the station can handle a high number of SEND_HISTORY commands and respond within a given time interval.


Implementation

  • Drag and drop the component into the a MqttConnector.
  • Set the startTimestamp and endTimestamp values. Those are the values which will be sent in the SEND_HISTORY commands.
  • Set the timeOut value.
  • Configure the LogExt.
  • Trigger the Execute action.
  • Display the Log Console Tool to have more information about the tests.
  • There are three ways to have the result of the test:
    • If the test ends before the timeout (all the commands have been sent and all the histories have been received).
    • If the test ends because of the timeout.
    • If the user triggers the "reportHistories" action.



Properties

  • Status: The status of the action, {ok} if the action was successful, {fault} if an error occurred.
  • State: The state of the execution, can be idle, pending or inProgress. 
  • Enabled: The enabled state of this component.
  • ExecutionTime: The time at which the execute action will be triggered.  
  • LastAttempt: The date of the last attempt.
  • LastSuccess: Indicates the date of the last successful attempt.
  • LastFailure: Indicates the date of the last failure.
  • FaultCause: Provides an indication of the reason if an error happened.
  • StartTimestamp: The startTimestamp value to sent in the SEND_HISTORIES action.
  • EndTimestamp: The endTimestamp value to sent in the SEND_HISTORIES action. 
  • LogExt: Btib Logger.
  • TimeOut: The time interval after which the test will be stopped.


Actions

  • Execute: Starts the test. It will take some time, as it will scan the whole station to find points with an History extension linked to the current connector.
  • Report Histories: Ends the test and updates the values. If the test was successful, the status will be ok and last success will be updated. Otherwise the status will be fault and the last failure will be updated