14893e62a5
This MVP release provides a complete full-stack solution for managing action mappings in Geutebruck's GeViScope and GeViSoft video surveillance systems. ## Features ### Flutter Web Application (Port 8081) - Modern, responsive UI for managing action mappings - Action picker dialog with full parameter configuration - Support for both GSC (GeViScope) and G-Core server actions - Consistent UI for input and output actions with edit/delete capabilities - Real-time action mapping creation, editing, and deletion - Server categorization (GSC: prefix for GeViScope, G-Core: prefix for G-Core servers) ### FastAPI REST Backend (Port 8000) - RESTful API for action mapping CRUD operations - Action template service with comprehensive action catalog (247 actions) - Server management (G-Core and GeViScope servers) - Configuration tree reading and writing - JWT authentication with role-based access control - PostgreSQL database integration ### C# SDK Bridge (gRPC, Port 50051) - Native integration with GeViSoft SDK (GeViProcAPINET_4_0.dll) - Action mapping creation with correct binary format - Support for GSC and G-Core action types - Proper Camera parameter inclusion in action strings (fixes CrossSwitch bug) - Action ID lookup table with server-specific action IDs - Configuration reading/writing via SetupClient ## Bug Fixes - **CrossSwitch Bug**: GSC and G-Core actions now correctly display camera/PTZ head parameters in GeViSet - Action strings now include Camera parameter: `@ PanLeft (Comment: "", Camera: 101028)` - Proper filter flags and VideoInput=0 for action mappings - Correct action ID assignment (4198 for GSC, 9294 for G-Core PanLeft) ## Technical Stack - **Frontend**: Flutter Web, Dart, Dio HTTP client - **Backend**: Python FastAPI, PostgreSQL, Redis - **SDK Bridge**: C# .NET 8.0, gRPC, GeViSoft SDK - **Authentication**: JWT tokens - **Configuration**: GeViSoft .set files (binary format) ## Credentials - GeViSoft/GeViScope: username=sysadmin, password=masterkey - Default admin: username=admin, password=admin123 ## Deployment All services run on localhost: - Flutter Web: http://localhost:8081 - FastAPI: http://localhost:8000 - SDK Bridge gRPC: localhost:50051 - GeViServer: localhost (default port) Generated with Claude Code (https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
533 lines
32 KiB
HTML
533 lines
32 KiB
HTML
<!DOCTYPE html>
|
|
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" lang="en" xml:lang="en" data-mc-search-type="Stem" data-mc-help-system-file-name="index.xml" data-mc-path-to-help-system="../../" data-mc-target-type="WebHelp2" data-mc-runtime-file-type="Topic" data-mc-preload-images="false" data-mc-in-preview-mode="false" data-mc-toc-path="GeViScope SDK|Action documentation">
|
|
<!-- saved from url=(0014)about:internet -->
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>POS</title>
|
|
<link href="../Resources/TableStyles/TABLE.css" rel="stylesheet" />
|
|
<link href="../../Skins/Default/Stylesheets/TextEffects.css" rel="stylesheet" />
|
|
<link href="../../Skins/Default/Stylesheets/Topic.css" rel="stylesheet" />
|
|
<link href="../Resources/Stylesheets/Styles.css" rel="stylesheet" />
|
|
<script src="../../Resources/Scripts/jquery.min.js">
|
|
</script>
|
|
<script src="../../Resources/Scripts/plugins.min.js">
|
|
</script>
|
|
<script src="../../Resources/Scripts/require.min.js">
|
|
</script>
|
|
<script src="../../Resources/Scripts/require.config.js">
|
|
</script>
|
|
<script src="../../Resources/Scripts/MadCapAll.js">
|
|
</script>
|
|
</head>
|
|
<body>
|
|
<div class="MCBreadcrumbsBox_0"><span class="MCBreadcrumbsPrefix">| </span><a class="MCBreadcrumbsLink" href="../Titel.htm">GeViScope SDK</a><span class="MCBreadcrumbsDivider"> > </span><a class="MCBreadcrumbsLink" href="../300_Action documentation.htm">Action documentation</a><span class="MCBreadcrumbsDivider"> > </span><span class="MCBreadcrumbs">POS</span>
|
|
</div>
|
|
<h1>POS</h1>
|
|
<p>Points of sales (POS) Actions enable the exchange of accompanying meta data between POS Management Systems and GeViScope/re_porter. With these actions payment processes can be documented consistently by video. The use of these actions for start and re-start of event recordings leads to the output of accompanying meta data in live video in GSCView as well as in the storage of those in the video data base. The video sequences recorded via POS Actions can easily be retrieved in GscView using the accompanying meta data und special data filter dialogs (optional) Besides the actions POSStatus and POSData for the general integration into POS Management Systems there are also POS actions which belong to special GeViScope drivers. The actions FillingPumpStatus, TerminalArticleData and TerminalPaymentData are used by the driver "HUTH". The driver "HUTH" is a GeViScope Media Plugin, which was developed by GEUTEBRÜCK, to integrate filling station management systems of the manufacturer HUTH Elektronik Systeme GmbH into GeViScope/re_porter. The driver is compatible to HUTH Video Interface T400/T450/Maxi/mini V1.2. The actions InterfaceRawData and InterfaceRawAnswer are also used by the driver "HUTH". But they only serve for debugging and fault analysis purpose. They can also be used in general for any link that the concerned action supports - respectively uses these actions. The action BarcodeData serves as a general integration of barcode scanners.</p>
|
|
<h2><a name="Barcode"></a>Barcode data</h2>
|
|
<p>Action name:BarcodeData(ReaderName, TimeStamp, Barcode)
|
|
|
|
</p>
|
|
<p>Action category: notification
|
|
|
|
</p>
|
|
<p>The POS Management System (or any other system like barcode scanner or similar) sends the action as soon as a barcode was read.
|
|
|
|
Via the parameter "ReaderName" the affected barcode scanner will be identified.
|
|
|
|
The further parameter will be filled with video meta data by the POS Management System.
|
|
|
|
</p>
|
|
<p> </p>
|
|
<table style="margin-left: 0;margin-right: auto;caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 349px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">scanner </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">ReaderName
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Alphanumerical identification of the barcode scanner </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Time stamp.
|
|
</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">code </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Barcode </td>
|
|
<td class="BodyD-Column1-Body1">Alphanumerical field for recording the scanned barcode. </td>
|
|
</tr>
|
|
</table>
|
|
<h2><a name="Filling"></a>Filling pump status</h2>
|
|
<p>Action name:FillingPumpStatus(TerminalName, TimeStamp, PumpNo, Status, Amount, Price, Details)
|
|
|
|
Action category: notification
|
|
|
|
</p>
|
|
<p>The "HUTH" driver sends the action for each status change of one filling pump.
|
|
|
|
Via the parameter "TerminalName" the concerned device will be identified. The "HUTH" driver is principally able to build up several connections to different Huth devices. The driver sends the alphanumerical value defined in his setup as "Interface name".
|
|
|
|
The further parameter will be filled with video meta data by the driver.
|
|
|
|
</p>
|
|
<p> </p>
|
|
<table style="caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');margin-left: 0;margin-right: auto;" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 349px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">Terminal </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">TerminalName
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Identifies the affected device. The "HUTH" driver is principally able to build up several connections to different Huth devices. The driver sends the alphanumerical value defined in his setup as "Interface name". </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Time Stamp, when the status change was detected by the Huth-System </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">pump no </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">PumpNo </td>
|
|
<td class="BodyD-Column1-Body1">Number of the filling pump </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">status</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Status</td>
|
|
<td class="BodyD-Column1-Body2">New status of the filling pump <br />Filling started = Huth-device status "taken off before filling"
|
|
<br />Filling stopped = Huth-device status "put back on end of filling" <br />Pump released = Huth-device status "disconnect after filling" <br />Amount message = sum - respectively amount notice of the filling pump
|
|
</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">amount</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Amount</td>
|
|
<td class="BodyD-Column1-Body1">Amount of the booking (optional)</td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">price</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Price</td>
|
|
<td class="BodyD-Column1-Body2">Sum of the booking (optional)</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">details</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Details</td>
|
|
<td class="BodyD-Column1-Body1">Free text (optional)</td>
|
|
</tr>
|
|
</table>
|
|
<h2><a name="Interfac"></a>Interface raw answer</h2>
|
|
<p>Action name:InterfaceRawAnswer(InterfaceName, TimeStamp, Data)
|
|
|
|
</p>
|
|
<p>Action category: notification
|
|
|
|
</p>
|
|
<p>This action is used by the "HUTH" driver. ". It serves only as a debug service and can also be used in general for any integration that supports or uses this action.
|
|
|
|
The "HUTH" driver sends the action for each telegram it has sent to the end device.
|
|
|
|
The affected end device will be identified by the parameter "TerminalName". The "HUTH" driver can always build up numerous connections to different Huth devices. The driver then sends the alphanumerical value defined in its setup as "Interface name"
|
|
|
|
The further parameter will be filled with video meta data by the driver.
|
|
|
|
</p>
|
|
<p> </p>
|
|
<table style="margin-left: 0;margin-right: auto;caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 350px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">interface </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">InterfaceName </td>
|
|
<td class="BodyD-Column1-Body1">Identifies the affected end device. The "HUTH" driver is principally able to build up several connections to different Huth devices. The driver sends the alphanumerical value defined in his setup as "Interface name". </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">TimeStamp when the telegram was received from the Huth system. </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">answer </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Data </td>
|
|
<td class="BodyD-Column1-Body1">The sent telegram in raw format. </td>
|
|
</tr>
|
|
</table>
|
|
<p> </p>
|
|
<h2><a name="Interfac2"></a>Interface raw data
|
|
</h2>
|
|
<p>Action name:InterfaceRawData(InterfaceName, TimeStamp, Data)
|
|
|
|
</p>
|
|
<p>Action category: notification
|
|
|
|
</p>
|
|
<p>This action is used by the driver "HUTH". It serves only as a debug service and can also be used in general for any integration that supports or uses this action.
|
|
|
|
The "HUTH" driver sends the action for each telegram it has received from the end device.
|
|
|
|
The affected end device will be identified by the parameter "TerminalName". The "HUTH" driver can always build up numerous connections to different Huth devices. The driver then sends the alphanumerical value defined in its setup as "Interface name"
|
|
|
|
The further parameter will be filled with video meta data by the driver. </p>
|
|
<p> </p>
|
|
<table style="margin-left: 0;margin-right: auto;caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 350px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">interface </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">InterfaceName </td>
|
|
<td class="BodyD-Column1-Body1">Identifies the affected end device. The "HUTH" driver is principally able to build up several connections to different Huth devices. The driver sends the alphanumerical value defined in his setup as "Interface name". </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">TimeStamp when the telegram was received from the Huth system. </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">data </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Data </td>
|
|
<td class="BodyD-Column1-Body1">The received telegram in raw format. </td>
|
|
</tr>
|
|
</table>
|
|
<h2><a name="POS"></a>POS data</h2>
|
|
<p>Action name:POSData(POSName, TimeStamp, Article, Price, Units, PricePerUnit, Line1, Line2, Line3, Line4, Line5)</p>
|
|
<p>Action category: logical</p>
|
|
<p>The POS Management System sends the action for each transaction carried out at a cash point</p>
|
|
<p>Via the parameter "POS"the affected cash point will be identified. The further parameter will be filled with video meta data by the POS Management System</p>
|
|
<p> </p>
|
|
<table style="margin-left: 0;margin-right: auto;caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 350px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">POS
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">POSName
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Alphanumerical identification of the cash point </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Time Stamp, when the action was send from the POS management system </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">article
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Article
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Identification of the booked article (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">price
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Price
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Amount (single price multiplied with number of articles) of transaction (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">units
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Units
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Amount of articles of the transaction (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">price per unit
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">PricePerUnit
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Single article price of the transaction (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">line 1
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Line1
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Alphanumerical fields /sections for storing of additional information concerning the transaction or for storing information which have been printed out on the sales slip (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">line 2
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Line2
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Alphanumerical fields /sections for storing of additional information concerning the transaction or for storing information which have been printed out on the sales slip (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">line 3
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Line3
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Alphanumerical fields /sections for storing of additional information concerning the transaction or for storing information which have been printed out on the sales slip (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">line 4
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Line4
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Alphanumerical fields /sections for storing of additional information concerning the transaction or for storing information which have been printed out on the sales slip (optional) </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">line 5
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Line5
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Alphanumerical fields /sections for storing of additional information concerning the transaction or for storing information which have been printed out on the sales slip (optional) </td>
|
|
</tr>
|
|
</table>
|
|
<h2><a name="POS2"></a>POS status</h2>
|
|
<p>Action name:POSStatus(POSName, TimeStamp, Status, Details)</p>
|
|
<p>Action category: logical</p>
|
|
<p>The POS management system sends the action as soon as the cash point is opened or closed or as soon as a cancellation will be made at a cash point.</p>
|
|
<p>Via the parameter "POS" the concerned cash point will be identified. The further parameter will be filled with video meta data from the POS management system.</p>
|
|
<p>The parameter "Status" can be addressed by the POS management system with a code figure for the currently notified status.</p>
|
|
<p> </p>
|
|
<table style="margin-left: 0;margin-right: auto;caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 350px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">POS
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">POSName
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Alphanumerical identification of cash point </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Time Stamp, when the action was sent from the POS management system</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">status
|
|
</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Status
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Identification figure for the currently notified status </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">details
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Details
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Additional alphanumerical information from POS management system (optional) </td>
|
|
</tr>
|
|
</table>
|
|
<h2><a name="Terminal"></a>Terminal article data</h2>
|
|
<p>Action name:TerminalArticleData(TerminalName, TimeStamp, CashierStation, PumpNo, AlarmStatus, Amount, Price, Details)
|
|
|
|
</p>
|
|
<p>Action category: notification
|
|
</p>
|
|
<p>The "Huth" driver sends the actions for each product-group-booking.
|
|
|
|
Via the parameter "TerminalName" the affected device will be identified. The "HUTH" driver is principally able to build up several connections to different Huth devices . The driver sends the alphanumerical value defined in his setup as "Interface name".
|
|
|
|
The further parameter will be filled with video meta data via the driver.
|
|
|
|
</p>
|
|
<p> </p>
|
|
<table style="caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');margin-left: 0;margin-right: auto;" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 349px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">Terminal </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">TerminalName
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Identifies the affected device. The "HUTH" driver is principally able to build up several connections to different Huth devices. The driver sends the alphanumerical value defined in his setup as "Interface name". </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Time Stamp, when the status change was detected by the Huth-System </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">cashier station</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">CashierStation</td>
|
|
<td class="BodyD-Column1-Body1">Number of the cash point where the booking is carried out</td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">pump no</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">PumpNo</td>
|
|
<td class="BodyD-Column1-Body2">Number of the filling point</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">alarm</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">AlarmStatus</td>
|
|
<td class="BodyD-Column1-Body1">Status of Alarm-Flags
|
|
<br />Yes = Alarm-Flag was set by the Huth system
|
|
<br />No = Alarm-Flag not set
|
|
|
|
</td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">amount</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Amount</td>
|
|
<td class="BodyD-Column1-Body2">Amount of the booking (optional)</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">price</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Price</td>
|
|
<td class="BodyD-Column1-Body1">Sum of the booking (optional)</td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">details</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Details</td>
|
|
<td class="BodyD-Column1-Body2">Free text (optional)</td>
|
|
</tr>
|
|
</table>
|
|
<h2><a name="Terminal2"></a>Terminal payment data</h2>
|
|
<p>Action name:TerminalPaymentData(TerminalName, TimeStamp, CashierStation, PumpNo, AlarmStatus, Amount, Price, Details)
|
|
|
|
</p>
|
|
<p>Action category: notification
|
|
|
|
</p>
|
|
<p>The "HUTH" driver sends the action for each termination of a booking with the used method of payment.
|
|
|
|
Via the parameter "TerminalName" the affected device will be identified. The "HUTH" driver is principally able to build up several connections to different Huth devices. The driver sends the alphanumerical value defined in his setup as "Interface name".
|
|
|
|
The further parameter will be filled with video meta data via the driver.
|
|
|
|
</p>
|
|
<p> </p>
|
|
<table style="caption-side: top;mc-table-style: url('../Resources/TableStyles/TABLE.css');margin-left: 0;margin-right: auto;" class="TableStyle-Rows" cellspacing="0">
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 100px;" class="Column-Column1" />
|
|
<col style="width: 349px;" class="Column-Column1" />
|
|
<thead>
|
|
<tr class="Head-Header1">
|
|
<th class="HeadE-Column1-Header1" colspan="2">Parameter
|
|
</th>
|
|
<th class="HeadD-Column1-Header1">Function
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">Terminal </td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">TerminalName
|
|
</td>
|
|
<td class="BodyD-Column1-Body1">Identifies the affected device. The "HUTH" driver is principally able to build up several connections to different Huth devices. The driver sends the alphanumerical value defined in his setup as "Interface name". </td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">time stamp
|
|
</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">TimeStamp
|
|
</td>
|
|
<td class="BodyD-Column1-Body2">Time Stamp, when the status change was detected by the Huth-System </td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">cashier station</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">CashierStation</td>
|
|
<td class="BodyD-Column1-Body1">Number of the cash point where the booking is carried out with the used payment method</td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">pump no</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">PumpNo</td>
|
|
<td class="BodyD-Column1-Body2">Number of the filling point (optional)</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">alarm</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">AlarmStatus</td>
|
|
<td class="BodyD-Column1-Body1">Status of Alarm-Flags
|
|
<br />Yes = Alarm-Flag was set by the Huth system
|
|
<br />No = Alarm-Flag not set
|
|
|
|
</td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">amount</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Amount</td>
|
|
<td class="BodyD-Column1-Body2">Amount of the booking (optional)</td>
|
|
</tr>
|
|
<tr class="Body-Body1">
|
|
<td class="BodyE-Column1-Body1">price</td>
|
|
<td class="BodyE-Column1-Body1" style="font-style: italic;">Price</td>
|
|
<td class="BodyD-Column1-Body1">Sum of the booking (optional)</td>
|
|
</tr>
|
|
<tr class="Body-Body2">
|
|
<td class="BodyE-Column1-Body2">details</td>
|
|
<td class="BodyE-Column1-Body2" style="font-style: italic;">Details</td>
|
|
<td class="BodyD-Column1-Body2">Free text (optional)</td>
|
|
</tr>
|
|
</table>
|
|
<p> </p>
|
|
<p> </p>
|
|
<p> </p>
|
|
<p> </p>
|
|
</body>
|
|
</html> |