Section 1 Pair RPCM to Readers via KLM

Download the newest version of the KLM app from the App Store or Google Play Store.

Log in to KLM and select “Pair RPCM” from the service menu.	Tap “Pair with Reader” in the pop-up window and select “Scan QR Code.”

Scan the QR code of the reader to be paired, then click the “Scan” button to continue to scan the QR code of RPCM.	Scan the QR code of RPCM, then select the socket of RPCM and click the “Start Pairing” button. 1) If the machine is connected to the “A” port of the socket, you must select “A” on KLM, otherwise the remote starting process will fail. 2) If you are configuring a 240V RPCM, there will be no pop-up window for selecting the socket.

After successfully pairing the reader, you can continue to pair the second reader.

Section 2 Remote Start

Users can issue a remote command at the server’s side to have RPCM power cycle the reader by following the instructions below.

This feature is not applicable to RPCM with modem at the present stage.
Remote Power Cycle is also applied to the AVU (VC) Touch Kiosk via remote command “Remote Power Cycle” as well.

To issue remote command for RPCM, “Remote Command” should be added as a permission for vendor admin(s) when creating/editing the roles at the Universal Server platform.

If a vendor staff wishes to issue the remote command, he/she should be granted the permission “Remote Power Cycle” at vendor portal > User management >Staff management. Once you’ve selected a role for the vendor staff, you can click on the “See Permissions” button to check the role’s permissions to ensure “Remote Command” has been added.

With the permissions added, you can check and issue the remote command at the location’s room view level.

Log in to Washboard Vendor Portal -> Location Management -> View location -> Rooms -> Room View. In this page, you will see the machines available in this location.

If there exist two socket icons () next to the machine name, it means the dual-socket RPCM 120V has been installed for the machine. If there is only one socket icon (), it indicates that the single-socket RPCM 240V has been used for the machine.

Then you can click on “Remote Command” to send the remote power cycle command. Select the action as “Remote Power Cycle,” select “Issue Command Time” as “currently,” tick the machine paired with RPCM, then click “Submit.”

Click “Apply” to confirm remote command.

Please wait up to 10 minutes for the process to start.
You can monitor the remote starting process on Washboard. Once the remote command is dispatched, the status will show as “Waiting to process remote power cycle.” Upon completion of the process, refreshing the Washboard page will update the status to “Remote power cycle successful.”

Section 3 RPCM Auto Power Cycle Reader Workflow

RPCM will be able to bring an unresponsive reader back to work automatically by adhering the workflow below without any manual intervention:

# 1 If RPCM cannot connect to the reader and has missed the heartbeat for the first time, then RPCM will try to connect once per second within a span of 20 seconds, up to a maximum of 20 times.

# 2 If RPCM still cannot connect to the reader by running # 1 flow twice consecutively, then RPCM will power cycle the reader. The reader will be brought back to working condition.

After the power cycle, if RPCM still fails to connect to the reader by running # 1 flow twice consecutively, then RPCM will NOT power cycle the reader until:

a. The RPCM is paired with another new reader, or

b. RPCM is able to connect to the reader again during the heartbeats in the end.

If the heartbeat between RPCM and VXT reader proves to be abnormal, RPCM will double confirm based on the configuration. If it fails, RPCM will power cycle the whole machine.

# 3 If RPCM detects a sound heartbeat update from the reader, it will record the power cycle event and upload the event directly to the KioCentral server, which indicates that it has successfully brought the reader back to work.

If RPCM fails to detect any heartbeat update from reader, it still records and uploads the power cycle event to the KioCentral for future retrieval.

Section 4 Reboot and Factory Reset

You can use KLM app to proceed with reboot and factory reset for RPCM.

Reboot: Service -> Reboot. Scan the QR code or enter machine number and prompt successful.
Factory Reset: Service -> Factory Reset. Scan the QR code and prompt successful.

Section 5 Check Activity Audit Log 

Remote power cycle events are recorded and presented in Activity Audit Log at the vendor portal, which includes manual and auto power cycle operations. You can use the filters (date range, activities, and keyword) on the left bar to search for the target power cycle activities.  

Each log includes the activity date, user’s full name, Email address, and company’s name along with an activity detail, where the activity detail column keeps track of the critical information that sticks to the formats: 

1) For Manual Power Cycle   

[Manual Power Cycle: LocationName RoomName Machine ### - Reader S/N] 

“Machine ###” indicates the machine number. 

2) For Auto Power Cycle 

[Auto Power Cycle: LocationName RoomName Machine ### - status] 

“status” indicates the reader’s state after the power cycle, which may include three scenarios: 

If it is auto power cycle, status will be labeled as “System.”

If RPCM can connect to the reader, status will be labeled as “RESTORED.”

If RPCM can’t connect to the reader, status will be labeled as “UNSUCCESSFUL.”

3) For RPCM supporting reader

[location name] [room name] [Machine #] [Modem: SN] [Reason: RPCM Wi-Fi signal strength test failed/Modem Cellular signal strength test failed/Edge Linux box test failed/General Network Connection test failed].

Note: The “Reason” may vary depending on the actual power cycle results, including:

a. RPCM Wi-Fi signal strength test failed;

b. Modem Cellular signal strength test failed;

c. Edge Linux box test failed;

d. General Network Connection test failed.