How to Deploy

Section 1 Upgrade RPCM for Readers to RPCM for Modem

If you have purchased an RPCM that supports readers, you can adopt one of the two approaches below to convert the RPCM supporting readers to RPCM supporting modem, which will be more of a cost-friendly option to fully utilize this product.

^{Upgrade via KLM app (iOS version)}

^{Two upgrades are required for this approach: upgrade the RPCM (supporting reader) to a transitional version and upgrade the transitional version to RPCM (supporting modem).}

^{Both upgrades should be done on the KLM app but differ in the reference number and version number.}

Step 1 Upgrade RPCM (supporting reader) to a transitional version

1. You can open KLM app and tap the navigation menu. Select “Service” -> “Update Reader” -> “TMS Update.”	2. Tap “Enter Reference.”

3. Select “Firmware Update” in the pop-up “Select Mode” window. Tap “OK.”	4. Enter the reference number in the pop-up window. Please contact KioSoft support for this information.

5. Then scan QR Code on the RPCM.	6. You can wait for a few minutes to complete the whole upgrading process. To confirm the RPCM has been upgraded to a mid version successfully, you can go to KLM and tap “Get Reader Info” to check the new version number (0500.000.001.000).

_{Step 2 Upgrade the transitional version to RPCM (supporting modem)}

1. You can open the KLM app and tap the navigation menu. Select “Service” -> “Update Reader” -> “TMS Update.”	2. Tap “Enter Reference.”

3. Select “Firmware Update” in the pop-up “Select Mode” window. Tap “OK.”	4. Enter the reference number in the pop-up window. Please contact KioSoft support for this information.

5. Then scan the QR Code on the RPCM.	6. Wait for a few minutes to complete the whole upgrading process. To confirm the RPCM has been upgraded to a mid version successfully, you can go to KLM and tap “Get Reader Info” to check the new version number (4200.000.000.008).

Section 2 Pair RPCM to Modem via KLM

Pair RPCM to Modems via KLM

Log in to KLM and select “Pair RPCM” from the service menu.	Then two radio options will appear “Pair with Reader” and “Pair with Modem.” Tick “Pair with Modem.”

After that, it will prompt to confirm the location.	Then you should select a room (If there is no room under the location, it will directly jump to the next step).

Then you can scan the QR code on RPCM.	After scanning the QR code on RPCM, you can enter the “Machine Number” and “Machine ID” of RPCM. Click on “Next.”

Afterwards, you should enter the modem SSID (default value is set as techtrex), which is a mandatory field.	Then click on “Submit” button. You can refer to the prompt’s description as below to become aware of the possible pairing result. 1) If KLM prompts “Paired Successfully,” it indicates that the RPCM has been paired with modem already. 2) If KLM prompts "Oops! Failed to Pair.” it indicates that the RPCM failed to pair with the modem. You should re-try again.

Get Reader Info

Having paired RPCM with modem successfully, you can acquire the complete pairing info. You can tap Service -> Get Reader Info through the KLM app. After scanning the QR code or entering the machine number, you can view the detailed information of the modem, including version number, Bluetooth name, Bluetooth firmware version, etc.

Section 3 Remote Start

Remote Commands via vendor portal are not applicable to RPCM with modem at present satge.

Section 4 RPCM Reboots Modem Workflow

After pairing the RPCM via KLM successfully, the RPCM will adhere to the workflow as below to reboot modem:

Step 1: The RPCM will start the Wi-Fi connection with the SSID entered in the KLM app.

If the Wi-Fi connection fails, RPCM will retry. The retry times (“Connect Wi-Fi retry times” set in NMS) has been configured in NMS ahead of time. If the connection is still not working, the RPCM will check if the modem has been rebooted within the hours that is configured in NMS (“Power Cycle Modem interval” set in NMS):

Scenario #1: If the modem has never been rebooted within the set hours, the RPCM will power cycle the modem. The action time along with the power cycle event would be uploaded into log.

Scenario #2: If the modem has been rebooted within the set hours, the RPCM will start to wait for the configured minutes (“Retry interval” set in NMS) to begin the testing for another time round.

If the Wi-Fi connection turns out successful, the RPCM will call the modem API to get modem’s SN.

Step 2: The RPCM will start to check the network status based on the checking rule configured in NMS (RPCM Modem Double confirm).

If the network fails to work, the modem will perform auto power cycle based on the configuration.

Step 3: If all the testing items are approved, the RPCM will start the testing after 5 minutes for another time around.

If there occur any failed test items:

If the double-confirm parameters have been selected, the RPCM will wait for 1 retry interval and double check once (just in case the modem switches the network). If it still failed, the RPCM needs to check if the modem has been rebooted within the set hours.
If the double-confirm parameters haven’t been selected, the RPCM needs to check if the modem has been rebooted within the set hours.

Step 3: If the RPCM has never been rebooted within the set hours, RPCM will power cycle the modem and record the action time and upload the power cycle event in the log. After the reboot command is sent, the RPCM will be in waiting mode for 5 minutes and then connect the modem Wi-Fi (go to Step 1).

Step 4: If RPCM is rebooted within the set hours, RPCM will start the next round of testing after the set minutes (go to Step 3).

Note: Users should connect and insert the modem into the 2 sockets of RPCM so that when RPCM needs to power cycle the modem, both sockets would be dead.

Section 5 Reboot and Factory Reset

You can use the 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 6 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: 

For RPCM supporting modem

[location name] [room name] [Modem: SN] [Reason:### ### ###]

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

a. RPCM connect Wi-Fi failed;

b. RPCM Wi-Fi signal strength test failed;

c. Modem Cellular signal strength test failed;

d. Edge Linux box test failed;

e. General Network Connection test failed.