Swissbit Hardware TSE

In this article you will find information on the area of development with the Swissbit hardware TSE.

Which version of the TSE am I using (DEV/RLS)?

To determine which version you are using, you can query the Swissbit TSE properties in the service (of all connected TSEs). To make sure that you are connected to the correct TSE, there are several possibilities:

• only one TSE is connected to the system
• start the self-test of the TSE, its LED will then flashes for approx. 25sec.

To determine if the TSE is a Developer TSE, check the FirmwareType field. If the value in the FirmwareType field is "DEV", then a Developer TSE is connected.

To query the TSE properties the following possibilities are available:

Webservice

• GET /api/v1/management/germany/tse

.net implementation

using RetailForce.Fiscalisation.Implementation.Germany.Tse;

...

// static method, get all connected devices
List devices = SwissbitHardware.GetLocalSecuritySystems();

// create swissbit hardware
SwissbitHardware swissbit = devices[0].CreateInterface(Microsoft.Extensions.Logging.Abstractions.NullLogger.Instance);

// get properties
SwissbitStatus tseStatus = swissbit.TseStatus;

//firmware type
string firmwareType = tseStatus.FirmwareType;

// TseId
string tseSerial = tseStatus.TseSerial;

(Code snipped, you still have to implement the corresponding code for a successful execution (function, class))

To carry out a self-test, you can proceed as follows:

Webservice

• POST / api/v1/management/germany/tse/{tseSerial}/selfTest
  The TSE Serial can also be found in the TSE properties that you have previously retrieved.

.net implementation

using RetailForce.Fiscalisation.Implementation.Germany.Tse;

...

// static method, get all connected devices
List devices = SwissbitHardware.GetLocalSecuritySystems();

// create swissbit hardware
SwissbitHardware swissbit = devices[0].CreateInterface(Microsoft.Extensions.Logging.Abstractions.NullLogger.Instance);

// Attention: you only can run self test for further actions tse has to be initialized
swissbit.RunSelfTest();

(Code snipped, you still have to implement the corresponding code for a successful execution (function, class))

Initialisation of the TSE

The initialisation of the TSE is a complex process and is done automatically by the fiscalisation module in the method InitializeClient.

For information, the steps for the initialisation process are shown here:

• Start self-test - Result "Client not registered".
• Set AdminPuk (the initial Admin Puk must be calculated beforehand)
• Set AdminPin
• Set TimeAdminPin
• Login as Admin
• Register cash register (client)
• Start self test for this client
• Activate CTSS interface
• Initialise Tse (ATTENTION: Cannot be undone, except DEV)
• Logout
• Login as TimeAdmin
• UpdateTime
• Logout

You will find these commands all in the log file after successful initialisation.

TSE Operation

In day-to-day operation of the TSE, the fiscal system takes care of the 2 essential issues:

• After each computer start and after a certain runtime, a self-test of the TSE must be carried out.
• Nach einem bestimmten Zeitintervall ist die Zeit der TSE zu aktualisieren.

TSE Factory reset

Developer TSEs can be reset using the following command:

wormcli f: tseFactoryReset

This example requires the TSE to be connected to the computer as drive F:.

Cash register manufacturers can request the wormcli.exe from: office@retailforce.cloud.

Validity of TSE certificates

Swissbit TSE certificates are valide trhough:

• live certificates (for productive use): 5 years
• test / developer certificates (NOT for productive use!) 6 months