To do this with a keyboard wedge device such as a Posligne 1500's card reader simply open Notepad and swipe the card. If the reader is a serial reader, we suggest using PuTTY to read the information. To do this you specify the Comm Port and the Communications settings and then when you swipe the card the data will be presented in the white box.
Rule Name: The name used for the reader/scanner
Prefix: The prefix to detect - This is the data at the start of the string used to tell GPoS which rule to follow
Suffix: The suffix to detect - this is not used and should be left as null
Length: The length of information expected (If the reader appends a CR please increase the length by 1 - this usually applies to keyboard wedge devices)
Key Types:
Code: Meaning:
0 System Key
1 PLU
2 PO
3 RA
4 Payment
5 Correction
6 Discount
8 Clerk
9 Plu Modifier
10 Macro
14 Deposit Buttons (keyoffset 1 = IN, 2 = OUT)
50 Screen Page
Key Off Set: If the key type has been set to 0: System key, then the key off set is the system key which will be used. See the system keys list for available keys
Code Portion Start: The position that the information being passed starts from.
Code Portion Length: The length of the information being passed
Amount Portion Start: If using price embedded barcodes, enter the position which the price information starts from
Amount Portion Length: The number of digits that makes up the price
Qty Portion Start: If using weight embedded barcodes, enter the position which the quantity information starts from
Qty Portion Length: The number of digits that makes up the weight
Keyboard Wedge Peripheral Type: 0 = Dallas Key, 1 = Scanner, 2 = MCR, 3 = Number Input - You need to set this option when using the reader rule for clerk functions.
Loyalty Reader Rule
Keyboard Wedge Example with Carriage Return and Line Feed Enabled :-
RecordID | Enter a Unique number here |
Rule Name | Enter a description for the rule |
Prefix | ;17502 (This prefix is a purely an example, your prefix will be on your software licence sheet) |
Suffix | (null) |
Length | 14 |
KeyType | 0 |
KeyOffset | 46 |
CodePortionStart | 2 |
CodePortionLength | 10 |
AmountPortionStart | (null) |
AmountPortionLength | (null) |
QtyPortionStart | (null) |
QtyPortionLength | (null) |
KeyboardwedgePeripheralType | (null) |
NOTE : We recommend disabling the Line Feed on the card reader - with Line Feed disabled the Length would drop 1 to 13
Price Embedded Barcode
RecordID | Enter a Unique number here |
Rule Name | Enter a description for the rule |
Prefix | 02 |
Suffix | (null) |
Length | 13 |
KeyType | 1 |
KeyOffset | 0 |
CodePortionStart | 3 |
CodePortionLength | 5 |
AmountPortionStart | 9 |
AmountPortionLength | 4 |
QtyPortionStart | (null) |
QtyPortionLength | (null) |
KeyboardwedgePeripheralType | (null) |
For further information you may find this useful http://wiki.answers.com/Q/How_does_a_price_embedded_bar_code_work
Weight Embedded Barcode
Weight embedded barcodes work as above except you would swap Amount for Quantity.
Clerk Cards
The GPoS standard prefix for a clerk card is 96969
With the clerk card the code portion is the information
RecordID | Enter a Unique number here |
Rule Name | Enter a description for the rule |
Prefix | ;96969 |
Suffix | (null) |
Length | 12 |
KeyType | 8 |
KeyOffset | 0 |
CodePortionStart | 7 |
CodePortionLength | 4 |
AmountPortionStart | (null) |
AmountPortionLength | (null) |
QtyPortionStart | (null) |
QtyPortionLength | (null) |
KeyboardwedgePeripheralType | 2 (as the above example has come from a MCR) |
You will also need need to make sure that system option 387 (Use Keyboard Wedge Peripheral Type setting when processing reader rules) is set to true