Device Information
- Model: FMC920
- Firmware Version: 0.3.29.00 Rev:21
- Network Operator: Claro
- Region: Peru
Problem Description
I’m experiencing a GSM reconnection issue with my FMC920 after extended periods without network coverage during travel through remote areas.
Expected Behavior vs Actual Behavior
First trip (Working as expected):
- Device sending data normally
- Lost signal in remote area
- Device continued storing data locally
- Upon returning to coverage area, device reconnected automatically
- All buffered data was transmitted successfully
Second trip (Problem occurred):
- Device sending data normally
- Lost signal in the same remote area
- Device continued storing data locally
- Upon returning to coverage area with good signal strength, device failed to reconnect
- Device remained disconnected for 5 hours despite being in good coverage zone
- After 5 hours, device finally reconnected and sent all buffered data
Current Status Information
Recent getInfo output:
RTC:2025/6/11 20:49 Init:2025/5/23 14:21 UpTime:1661893s PWR:SoftReset RST:2 GPS:3 SAT:13 TTFF:7 TTLF:34 NOGPS:0:0 SR:40616 FG:7 FL:0 SMS:35 REC:0 MD:0 DB:0
Questions
- Is there a specific configuration parameter that controls reconnection attempts frequency after extended disconnection periods?
- Are there timeout settings that might cause the device to “give up” trying to reconnect after a certain period?
- What parameters should I check/modify to ensure more aggressive reconnection attempts when returning to coverage areas?
- Is this behavior related to network operator restrictions or device-side configuration?
What I’ve Already Tried
- Previous testing: Device was tested in controlled environments with intentional disconnections and reconnections - worked normally
- Connection/reconnection tests: Prior tests showed normal reconnection behavior when simulating network loss
- Current status: Device is now sending data correctly and functioning normally
Important Notes
- No logs available: This issue occurred during real-world operation in remote areas, so detailed logs are not available
- Data integrity: All data collected during the 5-hour disconnection period was successfully transmitted once reconnection occurred
- Inconsistent behavior: The same route and coverage conditions that worked fine on the first trip caused the extended reconnection delay on the second trip
Additional Information Needed
- Which specific parameters should I review in my current configuration?
- Are there any logs I can check to understand why the reconnection failed?
- Should I consider adjusting any GSM/GPRS related timeouts?
Any guidance would be greatly appreciated. This issue is critical for our fleet tracking operations in remote areas.
Tags: FMC920, GSM, Reconnection, Coverage, Remote Areas, Configuration
