With an additional license, MxHub offers a transaction interface that allows to receive and display metadata via TCP-IP or serial interface.
It is not relevant which “device” or “software” sends the metadata, what is important is that it is sent to the MxHub via TCP-IP or serial interface.
In this example, the Vaxtor MakeModelColor Recognition App sends its detected metadata to the Transactions interface of the MxHub.
The following data is transmitted in this example.
- Date
- Time of day
- License Plate
- Country code
- Make
- Model
- Color
- Class
How to configure the Vaxtor app for this purpose is briefly described in the following section
Configure the TCP IP Notification in the Vaxtor App
→ Setup-Menu → Certified App Settings → Vaxtor ALPR MMCR
Reporting → TCP Server
- Enable this Interface
- Fill in the Port on which the TCP Notification should be send to
- Template: Fill in the “Text” which should be send, you can use Vaxtor specific variables"
Click Set → Close
When the Vaxtor MMCR App will recognize a license plate the TCP Notification will be send to Port: 30000
1. Create a Transaction Source in ManagementClient
→ ManagementClient → Transact → Transaction sources
Right click : Add source…
Name: “Fill in a name for the Trasnaction Source”
Connector: “Select the right Connector”
Host name: “Enter here the source of the transaction data from which they will arrive”
Port number: “Enter here the port number on which the transaction data will arrive”
Click Next
Click: New
Name: “Enter a name for the Transaction Definition”
Encoding: “Select the right Encoding for your date source”
Click on "Start collecting data"
Now you must send some metadata to the transaction interface.
In this example some License plates where detected.
You can see this in the raw data field.
If the metadata arrives, it is still unformatted and must be formatted.
Here you can format this as you like.
Now you need to Add filters.
You can select the following filters:
Substitute:“Here you can have certain values replaced”
Break line: “Applies a line break”
Omit:“Here you can have certain values removed”
Based on the display, the MxHub expects at least one line break after a certain character.
In this case, an “@” character was also sent; if this appears, it will be removed and a line break will be performed.
Also a start pattern must be set, so that the transaction interface knows when the metadata starts.
With stop pattern you can also decide when the metadata ends.
After the line break has been set and the start pattern as well, you can see how the metadata is displayed
Click OK
You can now select a camera whcih shows a rellated video alongside the transaction. You can also choose several camera.
Click on Add and select your camera
Click Next
The Transaction Source is now configured and ready for transaction metadata
You can now set Events for specific Match Types of the incoming metadata.
→ ManagementClient → Transact → Transaction definitions
Select your Transaction definition which you have created before.
Click on "Events"
You can decide between 3 Match Types:
- Use exact match: “The search identifies strings that contain exactly what you have entered in the Start pattern and Stop pattern fields”
- Use wildcards:"The search identifies strings that contain what you have entered in the Start pattern and Stop pattern fields in combination with a wild card symbol (*, #, ?)
- matches any number of characters. For example, if you have entered “Start transaction”, the search identifies strings that contain “Start transaction”.
#matches exactly 1 digit. For example, if you have entered “# watermelon”, the search identifies strings that contain, for example, “1 watermelon”.
? matches exactly 1 character. For example, you may use the search expression “Start transaction” to identify strings that contain “Start transaction”"
- Use regular expression:“Use this match type to identify strings that contain specific notation methods or conventions, for example a date format or credit card number. For more information, see the Microsoft website (https://docs.microsoft.com/dotnet/standard/base-types/regular-expression-language-quick-reference/)”
This event can be used for a Rule for exampe.
You can find this Event now in the eventlist of a Rule:
2. Adding a transaction source in MxHub
Create a view in MxHub.
Here, the Transactions source needs a “place” in a view to be able to see the data live.
Click on Setup
Drag an Drop the Transact into the Place in which it should be displayed.
Select your configured Transaction Source.
After the Transaction Source received some Metadata, they will be displayed in the view:
Here you can see a short Clip of how it looks:
You can also view the transaction data in the “Transact” tab.
When you create a Rule for Recording when an Transaction Events triggers, you can see the recording in the Transact Tab.
