5.4.0 LPR Fuzzy Reader

Steps to enable matchFirstCandidate aka "fuzzy reader"

1. Log in with Admin user account

2. Navigate to "localhost:5001/gql

3. Clear notes on left-hand side table, and enter the following then press play:

query LprCameras {
  lprCameraConfigs {
    cameraType
    configKey
    debug
    deviceType
    lastLoad
    loadOutLocationKey
    lprCameraUrl
    lprFieldToMatch
    matchFirstCandidite
    name
    socketKeepAlive
    startupOption
  }
}

You will get results like the following:

// Some code

This provides the camera's configuration in the right-hand side table:

Pasted results:

  "data": {
    "lprCameraConfigs": [
      {
        "cameraType": "AXIS",
        "configKey": "4cfddb99-1026-4cbe-8e27-14ad5c1de739",
        "debug": true,
        "deviceType": "LPR_CAMERA",
        "lastLoad": null,
        "loadOutLocationKey": 3841,
        "lprCameraUrl": "http://post",
        "lprFieldToMatch": "LICENSE_NUM",
        "matchFirstCandidite": false,
        "name": "Return AXIS LPR",
        "socketKeepAlive": false,
        "startupOption": "START_AT_STARTUP"
      }
    ]
  }
}

1. The configuration can be copy-pasted into the mutation to enable matchFirst like the following:

mutation UpdateLprCamera {
  updateLprCamera(
    input: {
      inputtype: {
        cameraType: AXIS,
        configKey: "4cfddb99-1026-4cbe-8e27-14ad5c1de739",
        lastLoad: null,
        loadOutLocationKey: 3841,
        lprCameraUrl: "http://post",
        lprFieldToMatch: LICENSE_NUM,
        matchFirstCandidite: true,
        name: "Return AXIS LPR",
        socketKeepAlive: false,
        startupOption: START_AT_STARTUP
      }
    }
  ) {
    configLprCamera {
      cameraType
      configKey
      debug
      deviceType
      lastLoad
      loadOutLocationKey
      lprCameraUrl
      lprFieldToMatch
      matchFirstCandidite
      name
      socketKeepAlive
      startupOption
    }
    errors {
      ... on TacServerError {
        code
        errorSource
        itemId
        message
        serverMessage
      }
    }
  }
}

NOTE: You will need to remove the quotations around some of the results from the configuration you copy-paste into the mutation for it to run successfully.

1. Ensure you have changed matchFirstCandidate from false to true, and then press play.

The corresponding results in the right-hand table should reflect that matchFirstCandidate now shows as "true", but if you want to take extra caution you can run the config query again.