Difference between revisions of "Q-Simulator"
(Define the car park to use) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | 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''' |
You can download it here: | You can download it here: | ||
| Line 7: | Line 7: | ||
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. | 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 | + | The token abstracts the parking ticket on paper. |
| + | |||
| + | '''Note''': the token generated by the Q-Simulator works only with parks made in ''COCHA AUTO'' car park. | ||
=== '''Before starting:''' === | === '''Before starting:''' === | ||
Ensure that: | Ensure that: | ||
| − | # | + | # Bluetooth is turned on on tablet |
# Q-Simulator is the only app using blue tooth (so check that Dashboard app and CU_Simulator app are totally turned off, not only in background) | # Q-Simulator is the only app using blue tooth (so check that Dashboard app and CU_Simulator app are totally turned off, not only in background) | ||
| Line 31: | Line 33: | ||
At this point you should see a log line in the LOG field saying: | At this point you should see a log line in the LOG field saying: | ||
Started advertising as ID-1-Entry | Started advertising as ID-1-Entry | ||
| − | + | <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>After an user successfully entered the carpark, you should see some log lines in the LOG field reporting: | |
| − | |||
| − | 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 token and the "direction", entrance or exit | ||
| Line 55: | Line 55: | ||
At this point you should see a log line in the LOG field saying: | At this point you should see a log line in the LOG field saying: | ||
Started advertising as ID-1-Entry | Started advertising as ID-1-Entry | ||
| − | + | <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''' | |
| − | After an user successfully exited the carpark, you should see some log lines in the LOG field reporting: | + | </blockquote>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 token and the "direction", entrance or exit | ||
Latest revision as of 13:35, 30 July 2021
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.
Note: the token generated by the Q-Simulator works only with parks made in COCHA AUTO car park.
Before starting:[edit | edit source]
Ensure that:
- Bluetooth is turned on on tablet
- Q-Simulator is the only app using blue tooth (so check that Dashboard app and CU_Simulator app are totally turned off, not only in background)
To simulate an entrance:[edit | edit source]
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:[edit | edit source]
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