Difference between revisions of "Tablet configuration"
m |
|||
| Line 2: | Line 2: | ||
* Enter / exit an automatic carpark: use the [[Tablet configuration#Dashboard|Dashboard]] | * Enter / exit an automatic carpark: use the [[Tablet configuration#Dashboard|Dashboard]] | ||
| − | *Enter / exit a manually operated carpark: use the [[ | + | *Enter / exit a manually operated carpark: use the [[Q-Simulator]] |
*Charge on street: use the [[Tablet configuration#CU-Simulator|CU-Simulator]] | *Charge on street: use the [[Tablet configuration#CU-Simulator|CU-Simulator]] | ||
*Charge in a carpark (automatic or manual operated, please note that at the moment this page is written we have no automatic carparks containing charging points in Production and that the manually operated carparks represent the most of the affiliated carparks): use the [[Tablet configuration#CU-Simulator|CU-Simulator]] | *Charge in a carpark (automatic or manual operated, please note that at the moment this page is written we have no automatic carparks containing charging points in Production and that the manually operated carparks represent the most of the affiliated carparks): use the [[Tablet configuration#CU-Simulator|CU-Simulator]] | ||
| Line 15: | Line 15: | ||
This is the app for tablet to simulate entrances and exits to and from an '''automatic carpark''' | This is the app for tablet to simulate entrances and exits to and from an '''automatic carpark''' | ||
| − | https://install.appcenter.ms/orgs/quisque/apps/q-simulator/distribution_groups/public%20release | + | 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). | 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: <blockquote> | ||
| + | STOP SERVICE | ||
| + | </blockquote>Then set app fields in the following way:<blockquote> | ||
| + | ''Role = "ENTRY"'' | ||
| − | '' | + | ''Integration = "NONE"'' |
| − | = | + | ''Lane = "1"'' |
| − | |||
| − | '' | + | ''ID = "1"'' |
| − | '' | + | Press ''"START SERVICE"'' |
| + | </blockquote>At this point you should see a log line in the ''LOG'' field saying: <blockquote> | ||
| + | Started advertising as ID-1-Entry | ||
| + | </blockquote><blockquote> | ||
| + | '''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''' | ||
| + | </blockquote> | ||
| − | |||
| − | |||
| − | === CU-Simulator === | + | After an user successfully entered the carpark, you should see some log lines in the ''LOG'' field reporting:<blockquote> |
| + | the token and the "direction", entrance or exit | ||
| + | |||
| + | the user number | ||
| + | |||
| + | the mac address of the phone | ||
| + | </blockquote> | ||
| + | |||
| + | ======To simulate an exit:====== | ||
| + | If service is active press:<blockquote> | ||
| + | STOP SERVICE | ||
| + | </blockquote>Then set app fields in the following way:<blockquote> | ||
| + | ''Role = "EXIT"'' | ||
| + | |||
| + | ''Integration = "NONE"'' | ||
| + | |||
| + | ''Lane = "1"'' | ||
| + | |||
| + | ''ID = "1"'' | ||
| + | |||
| + | Press ''"START SERVICE"'' | ||
| + | </blockquote>At this point you should see a log line in the ''LOG'' field saying: <blockquote> | ||
| + | Started advertising as ID-1-Entry | ||
| + | </blockquote><blockquote> | ||
| + | '''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''' | ||
| + | </blockquote>After an user successfully exited the carpark, you should see some log lines in the ''LOG'' field reporting:<blockquote> | ||
| + | the token and the "direction", entrance or exit | ||
| + | |||
| + | the user number | ||
| + | |||
| + | the mac address of the phone | ||
| + | </blockquote> | ||
| + | |||
| + | ===CU-Simulator=== | ||
This is the app for tablet to simulate '''charges''' | This is the app for tablet to simulate '''charges''' | ||
Revision as of 10:14, 18 June 2021
An Android tablet is necessary to test the following flows:
- Enter / exit an automatic carpark: use the Dashboard
- Enter / exit a manually operated carpark: use the Q-Simulator
- Charge on street: use the CU-Simulator
- Charge in a carpark (automatic or manual operated, please note that at the moment this page is written we have no automatic carparks containing charging points in Production and that the manually operated carparks represent the most of the affiliated carparks): use the CU-Simulator
Dashboard
This is the app for tablet in use to carpark operators and allow them to register the entrances
Connect to an environment:
The app can connect to Production or to our test environments. To change this [TODO]
Q-Simulator
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
CU-Simulator
This is the app for tablet to simulate charges