Configuration
Setup Tool
The easiest way to configure the device is via the Setup Tool. Follow the instructions in the Setup Tool.
Manually
To edit the configuration of the device, connect it via USB to your computer. In the connected drive you will find a file named "app_config.txt". Open this file with a text editor.
The configuration file is divided into sections.
Every section starts with [Section].
buttonmapping
In the section buttonmapping you can configure
the function of each button.
The possible values that can be set are:
| Value | Function |
|---|---|
| 0 | No Function |
| 1 | Program a transponder |
| 2 | Verify a transponder |
| 3 | Read transponder/barcode |
| 4 | Lock a transponder |
| 5 | Read transponder/barcode raw |
For each button you can now assign one of the values mentioned above.
| Option | Button |
|---|---|
| trigger_one | T1 |
| trigger_two | T2 |
| function_one | F1 |
| function_two | F2 |
bluetooth
reconnect_to_last_device
With this option the automatic bluetooth connection can be controlled.
If the value is set to 1,
the device will try to connect to the last connected device.
If the value is set to 0,
the connection must be established manually from the PC.
write
allow_short_epc_schemes_only
With this option the size of the allowed EPC schema can be defined.
| Value | Function |
|---|---|
| 0 | All schemes are allowed |
| 1 | Only small EPC schemes are allowed (e.g. only SGTIN-96, but not SGTIN-198) |
sgtin_filter_value
With this option the filter value can be specified for the SGTIN EPC schemes.
This filter value is used, when a transponder is programmed using an SGTIN EPC scheme.
Default value is 0.
Allowed values are from 0 to 7.
grai_filter_value
With this option the filter value can be specified for the GRAI EPC schemes.
This filter value is used, when a transponder is programmed using an GRAI EPC scheme.
Default value is 0.
Allowed values are from 0 to 7.
giai_filter_value
With this option the filter value can be specified for the GIAI EPC schemes.
This filter value is used, when a transponder is programmed using an GIAI EPC scheme.
Default value is 0.
Allowed values are from 0 to 7.
verify
failure_signal
This option is used to define the feedback signal if the verification fails due to a mismatch between barcode and transponder.
| Value | Function |
|---|---|
| 0 | Single Beep |
| 1 | 6 Beeps (high/low) |
lock
type
There different types of locking mechanisms.
This can be set via type parameter in the configuration.
Default is 0.
| Value | Lock type |
|---|---|
| 0 | Permanent (not reversible) |
| 1 | Random Password (can be written again with the randomly generated password) |
See documentation of the locking procedure for more details.
hid
date_time_format
With this setting the date format can be defined which is used when data is sent to a PC via HID. Wildcards can be used to define the format.
data_format
With this setting the format in which the data is sent to a PC can be defined. The format can be defined differently for every button.
| Option | Button |
|---|---|
| data_format_trigger_one | T1 |
| data_format_trigger_two | T2 |
| data_format_function_one | F1 |
| data_format_function_two | F2 |
To define the format, placeholders can be used.
| Wildcard | Output |
|---|---|
| {TAB} | TAB keypress |
| {ENTER} | ENTER keypress |
| %t | Timestamp in the format as defined in hid_date_time_format |
| %F | The function that was executed ("read", "write", "verify", "lock"). |
| %H | EPC as hexadecimal string (when reading an RFID transponder), barcode string (when scanning a barcode) |
| %I | When using the verify function, it prints the EPC in hex format of the transponder that was verified. |
| %S | All GS1 application identifiers and their values in the format "(xx)yyyy(xxxx)yyyy". |
| %U | When using the verify function, it prints all GS1 application identifiers of the transponder that was verified. |
| %{XXXX} | The value of the GS1 application identifier "XXXX". |
| %{nXXXX} | The key and value of the GS1 application identifier "`XXXX". |
| %{(nXXXX} | The key (in brackets) and the value of the GS1 application identifier "`XXXX". |
| %% | Percentage-Sign |
Following are examples for different formats with the given data.
- AI 01: 1111
- AI 21: 2222
| Format | Output |
|---|---|
| %{01} | 1111 |
| %{n01} | 011111 |
| %{(n01} | (01)1111 |
| %{(n01}{TAB}%{(n21} | (01)1111 [TAB] (21)2222 |
| %t %{01}{ENTER} | 2024.04.14 12:22:01 1111 [ENTER] |
| %S | (01)1111(21)2222 |
journal
date_time_format
With this setting the date format can be defined which is used in the journal. Wildcards can be used to define the format.
Additional Information
Wildcards Dateformat
| Wildcard | Description |
|---|---|
| %y, %Y | Year |
| %m | Month (without leading 0) |
| %M | Month (with leading 0 if needed) |
| %d | Day (without leading 0) |
| %D | Day (with leading 0 if needed) |
| %h | Hour (without leading 0) |
| %H | Hour (with leading 0 if needed) |
| %n | Minute (without leading 0) |
| %N | Minute (with leading 0 if needed) |
| %s | Second (without leading 0) |
| %S | Second (with leading 0 if needed) |