POS
Points of sales (POS) Actions enable the exchange of accompanying meta data between POS Management Systems and G-Scopes. 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 G-View 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 G-View 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 G-Core modules. The actions FillingPumpStatus, TerminalArticleData and TerminalPaymentData are used by the module "HUTH". The module "HUTH" is a G-Core media plugin, which was developed by GEUTEBRUECK, to integrate filling station management systems of the manufacturer HUTH Elektronik Systeme GmbH into G-Scopes. 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.
Action name: InterfaceRawData (interface, time stamp, data)
Action category: notification
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.
|
Parameter |
Function |
|
|---|---|---|
|
interface |
InterfaceName |
Interface name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
data |
Data |
Interface data. |
Action name: InterfaceRawAnswer (interface, time stamp, answer)
Action category: notification
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.
|
Parameter |
Function |
|
|---|---|---|
|
interface |
InterfaceName |
Interface name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
answer |
Data |
Interface answer. |
Action name: POSStatus (POS, time stamp, status, details)
Action category: notification
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. 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. The parameter "Status" can be addressed by the POS management system with a code figure for the currently notified status.
|
Parameter |
Function |
|
|---|---|---|
|
POS |
POSName |
POS name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
status |
Status |
Status. |
|
details |
Details |
Details. |
Action name: POSData (POS, time stamp, article, price, units, price per unit, line 1, line 2, line 3, line 4, line 5)
Action category: notification
The POS Management System sends the action for each transaction carried out at a cash point 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
|
Parameter |
Function |
|
|---|---|---|
|
POS |
POSName |
POS name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
article |
Article |
Article description. |
|
price |
Price |
Price. |
|
units |
Units |
Number of units. |
|
price per unit |
PricePerUnit |
Price per unit. |
|
line 1 |
Line1 |
Line 1. |
|
line 2 |
Line2 |
Line 2. |
|
line 3 |
Line3 |
Line 3. |
|
line 4 |
Line4 |
Line 4. |
|
line 5 |
Line5 |
Line 5. |
Action name: POSDataEx (POS, time stamp, article, price, units, price per unit, line 1, line 2, line 3, line 4, line 5, user ID, username, action type, value C (32-bit), value D (32-bit), value A (64-bit), value B (64-bit), value C (64-bit), value D (64-bit))
Action category: notification
Extended POS Data action with username, action type and several fields for integer values.
|
Parameter |
Function |
|
|---|---|---|
|
POS |
POSName |
POS name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
article |
Article |
Article description. |
|
price |
Price |
Price. |
|
units |
Units |
Number of units. |
|
price per unit |
PricePerUnit |
Price per unit. |
|
line 1 |
Line1 |
Line 1. |
|
line 2 |
Line2 |
Line 2. |
|
line 3 |
Line3 |
Line 3. |
|
line 4 |
Line4 |
Line 4. |
|
line 5 |
Line5 |
Line 5. |
|
user ID |
UserID |
User ID of certain user. |
|
username |
Username |
Name of user. |
|
action type |
Actiontype |
Type of action. |
|
value C (32-bit) |
Int32FieldC |
Additional data |
|
value D (32-bit) |
Int32FieldD |
Additional data |
|
value A (64-bit) |
Int64FieldA |
64 bit value A |
|
value B (64-bit) |
Int64FieldB |
64 bit value B |
|
value C (64-bit) |
Int64FieldC |
64 bit value C |
|
value D (64-bit) |
Int64FieldD |
64 bit value D |
Action name: BarcodeData (scanner, time stamp, code)
Action category: notification
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.
|
Parameter |
Function |
|
|---|---|---|
|
scanner |
ReaderName |
Scanner name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
code |
Barcode |
Barcode. |
Action name: FillingPumpStatus (terminal, time stamp, pump no, status, amount, price, details)
Action category: notification
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.
|
Parameter |
Function |
|
|---|---|---|
|
terminal |
TerminalName |
Terminal name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
pump no |
PumpNo |
Pump no. |
|
status |
Status |
Status. |
|
amount |
Amount |
Amount. |
|
price |
Price |
Price. |
|
details |
Details |
Details. |
Action name: TerminalArticleData (terminal, time stamp, cashier station, pump no, alarm, amount, price, details)
Action category: notification
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.
|
Parameter |
Function |
|
|---|---|---|
|
terminal |
TerminalName |
Terminal name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
cashier station |
CashierStation |
Cashier station. |
|
pump no |
PumpNo |
Pump no. |
|
alarm |
AlarmStatus |
Alarm status. |
|
amount |
Amount |
Amount. |
|
price |
Price |
Price. |
|
details |
Details |
Details. |
Action name: TerminalPaymentData (terminal, time stamp, cashier station, pump no, alarm, amount, price, details)
Action category: notification
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.
|
Parameter |
Function |
|
|---|---|---|
|
terminal |
TerminalName |
Terminal name. |
|
time stamp |
TimeStamp |
Time stamp. |
|
cashier station |
CashierStation |
Cashier station. |
|
pump no |
PumpNo |
Pump no. |
|
alarm |
AlarmStatus |
Alarm status. |
|
amount |
Amount |
Amount. |
|
price |
Price |
Price. |
|
details |
Details |
Details. |
Action name: GamingMachine (machine location, calltype, amount, player ID, event date time, currency ID, Bank number)
Action category: notification
With this action information from gaming machines can be stored in database.
|
Parameter |
Function |
|
|---|---|---|
|
machine location |
MachineLocation |
Location of gaming machine. |
|
calltype |
Calltype |
Calltype of the action. |
|
amount |
Amount |
Amount (currency may be determined by currency ID). |
|
player ID |
PlayerID |
ID of the player/patron. |
|
event date time |
EventDateTime |
The local date and local time that the event occurred. |
|
currency ID |
CurrencyID |
With the currency ID the currency may be determined. |
|
Bank number |
BankNumber |
Bank number. |