Overview
This guide explains RobustOS RCMS, firmware and ping-detection configuration on a Robustel device when stock managers, end customers and monitoring teams share responsibility for deployment. It covers the sequence for onboarding to RCMS, applying firmware and enabling connectivity monitoring. The key takeaway is that roles and handoffs must be defined before devices are upgraded or transferred between stakeholders.
This guide outlines the complete process for configuring and upgrading cellular gateway devices across three stakeholder companies:
- Device Holder (Stock Manager & Main Player)
- Customers (End Users)
- Monitoring Company (RCMS Server Operator)
| Task | Device Holder | Customer | Monitoring Company | Notes |
|---|
| Device Registration | | | | |
| Backend Database Registration | - | - | ✓ | Required before deployment |
| RCMS Platform Registration | - | - | ✓ | Via batch import |
| Firmware Management | | | | |
| Update via RCMS | - | - | ✓ | Remote update capability |
| Update via Web UI | ✓ | ✓ | ✓ | Local/remote access needed |
| Update via USB | ✓ | ✓ | - | Physical access required |
| RCMS Configuration | | | | |
| Enable via SMS | ✓ | - | ✓ | Any stakeholder with device number |
| Enable via Web UI | ✓ | ✓ | ✓ | Local/remote access needed |
| Enable via Config File | ✓ | ✓ | ✓ | Profile deployment |
| Ping Detection | | | | |
| Enable via Web UI | ✓ | ✓ | ✓ | Local/remote access needed |
| Enable via Config File | ✓ | ✓ | ✓ | Profile deployment |
| Monitoring & Verification | | | | |
| Connection Monitoring | ✓ | - | ✓ | System Debug |
| RCMS Status Check | ✓ | - | ✓ | System Debug/RCMS Status
|
Success Criteria
A properly configured device must meet all these conditions:
1. Network Connection:
- Connected to custom APN network
- Stable cellular connection
2. RCMS Status:
- Device registered and visible in RCMS platform
- Active connection to RCMS server
3. Stability Verification:
- Ping detection operational and reporting
- Consistent network connectivity monitoring
Prerequisites
Initial Steps
1. Monitoring Company Prerequisites:
- All devices pre-registered in backend database with IMEI and SN. Refer to the backend documentation
- Devices registered in frontend of RCMS platform with IMEI and SN via BATCH IMPORT
2. Device Delivery State:
- Ideally: Devices delivered with latest firmware
- Ideally: RCMS on the device is enabled, Ping Detection is enabled
Goal 1: Firmware Update to the latest one
There are 3 ways to update the device to the latest FW:
- Update Firmware via RCMS - Monitoring company should do it
- Local / Remote Web UI Update - Stock manager / End Customer / Monitoring company should do it
- Update via USB - Stock manager / End customer should do it
Goal 2: RCMS Enable
Available configuration methods, any stakeholder company can do it with either local or remote access to the device:
- Enable RCMS via SMS
- Enable RCMS via Web UI
- Enable RCMS via Config/Profile File
Goal 3: Ping Detection
Available configuration methods, any stakeholder company can do it with either local or remote access to the device:
- Enable Ping Detection via Web UI
- Enable Ping Detection via Config/Profile XML File
Verification & Troubleshooting
Status Checks
Each configuration aspect has its own status page:
- PIN code status verification. Under System > Debug or Interface > Cellular > Status
- Ping detection status monitoring. Under System > Debug
- RCMS connection status. Under System > Debug or Services > RCMS > Status
Configuration Order
- Goals can be achieved in any order
- Multiple configurations can be applied simultaneously
- Each feature can be configured independently
Conclusion
To complete RobustOS RCMS, firmware and ping-detection configuration on Robustel device, verify that the device runs the approved firmware, appears online in RCMS and reports the expected ping-detection status. This creates a repeatable commissioning process across the involved organizations.