P4 Software
/
activoHQ English
ActivoHQ RFID (the activoHQ mobile app) is the Android app used on the floor to count Assets with an RFID reader and to run actions on an asset without going back to a computer.
With it your team can: start or resume a count session, read the Assets' RFID tags - watching live how many are Found, Missing and Unexpected - submit the reads, reconcile and review the variance; plus check out, check in and dispose of an asset from the handheld itself.
If the connection drops, the check out, check in and dispose actions are saved on the device and sync themselves once the signal is back. Counting (opening sessions, submitting reads, reconciling) does need a connection.
It is available in English and Spanish and connects to the same inventory as the web application.
| Requirement | Detail |
|---|---|
| Device | An Android handheld; for RFID reading, a Zebra device with an integrated reader or a sled (for example MC3300R, MC3390R or a TC with RFID). |
| Account | A user account of type Administrator in your organization's activoHQ. |
| Tenant (subdomain) | Your organization's identifier, the same one you use in the web address (for example acme in acme.activohq.cloud). |
| Connection | Needed to sign in and to count (open sessions, submit reads, reconcile and close). Only the check out, check in and dispose actions can be done offline; they are queued and synced later. |
Without an RFID reader, the app runs in mock mode for training and testing: the count screen shows the notice MOCK RFID - no hardware reads, and the reads do not come from real hardware.
Once in, you see Count sessions, with the company's sessions and their status. From there you can:
An indicator shows how many actions are waiting to sync; tap it to open the Sync Queue.
Reads you have not submitted are not kept if you leave the count screen; submit them before leaving. Submit reads and Reconcile become active once at least one new tag has been read during the current visit to the screen.
Variance shows the result per asset: Found, Missing, Moved and Unexpected. When the count looks right, tap Close session. Closing the session means it can no longer accept reads.
The same information is available in the web application, under Audit > Count sessions and in the RFID Audit Variance report.
Only the Check Out, Check In and Dispose actions work offline. If there is no connection when you run one of them, the app answers Saved - will sync when back online. and queues it. Counting (sessions, reads, reconciling and closing) requires a connection.
In the Sync Queue you see each pending action with its type (Check Out, Check In, Dispose), its date, its status (Pending, Synced, Failed) and the last error if there was one. Pending actions are sent automatically once the connection is back, in the order they were recorded. An action rejected by the server is left as Failed for a human to review: fix the cause and tap Retry.
Under Reader Settings you can set:
| Option | What it is for |
|---|---|
| Connection | The reader type: Integrated device, Bluetooth sled or USB. |
| Scan for readers | Detects the available readers. |
| Mapped reader (name / prefix) | Pins a specific reader; left blank, the first one found is used. |
| Power | The antenna's power, as a percentage. Less power cuts down reads of Assets in adjacent rooms. |
| Reader ID (stamped on reads) | The identifier written into each read, useful when several handhelds count at once. |
| Beep & vibrate on each tag | Audible and tactile confirmation of each read. |
| Test connection | Checks that the reader responds. |
| Language | English or Spanish. |
Save with Save. An open count session can be resumed after leaving the app (reads already submitted stay on the server).
| Symptom | Likely cause | Resolution |
|---|---|---|
| You cannot sign in. | The tenant, username or password is wrong, there is no connection, or the account is not of type Administrator (a message appears). | Check the company identifier (the same one as the subdomain), your connection, and that the account is of type Administrator. |
| MOCK RFID - no hardware reads appears. | The app is in mock mode, or no reader is connected. | Use the build installed for the Zebra handheld and check the connection under Reader Settings. |
| No readers are detected. | The wrong connection type, or missing Bluetooth permissions. | Choose the right Connection, accept the permissions Android asks for, and tap Scan for readers. |
| Assets in another room are being read. | The antenna power is too high. | Reduce Power in the reader Settings. |
| Many Assets show as Unexpected. | The tags read do not match the EPC recorded on any asset in the register. | Record or correct the EPCs on each asset's record. |
| An action is stuck at Failed. | The server rejected the operation (the asset was already checked in by someone else, for example). | Review the error message, fix the situation and tap Retry. |
| The pending indicator does not go down. | There is no connection, or there are actions in Failed status. | Check the connection and review the Sync Queue. |
Was this page helpful?