Q-Simulator

From Wiquipedia
Revision as of 10:18, 18 June 2021 by Federica (talk | contribs)
Jump to navigation Jump to search

This is the app for tablet to simulate entrances and exits to and from an automatic carpark

You can download it here: https://install.appcenter.ms/orgs/quisque/apps/q-simulator/distribution_groups/public%20release

The app works in absence of connectivity, it interacts via bluetooth with the mobile phone applications, so it's not required to set an environment (production, sandbox, staging ecc).

When the user enters the parking the app on mobile phone will read the token from the Q-Simulator and when the user leaves the parking the app on mobile phone will write the token in the Q_Simulator.

The token abstracts the parking ticket on paper

Before starting:

Ensure that Q-Simulator is the only app using blue tooth (so check that Dashboard app and CU_Simulator app are totally turned off, putting them in background will not be enough)

To simulate an entrance:


If service is active press:

STOP SERVICE

Then set app fields in the following way:

Role = "ENTRY"

Integration = "NONE"

Lane = "1"

ID = "1"

Press "START SERVICE"

At this point you should see a log line in the LOG field saying:

Started advertising as ID-1-Entry

NB: Until you don't press "START SERVICE" the user can't enter the car park, so the call to action to make user enter the car park should be disabled or not visible or whatever UI/UX designed for this case

After an user successfully entered the carpark, you should see some log lines in the LOG field reporting:

the token and the "direction", entrance or exit

the user number

the mac address of the phone

To simulate an exit: If service is active press:

STOP SERVICE

Then set app fields in the following way:

Role = "EXIT"

Integration = "NONE"

Lane = "1"

ID = "1"

Press "START SERVICE"

At this point you should see a log line in the LOG field saying:

Started advertising as ID-1-Entry


NB: Like for the entrance, if you don't press "START SERVICE" the user can't exit the car park, so the call to action to make user exit the car park should be disabled or not visible or whatever UI/UX designed for this case

After an user successfully exited the carpark, you should see some log lines in the LOG field reporting:

the token and the "direction", entrance or exit

the user number

the mac address of the phone