Ewon : Flexy
Ewon : Cosy
IN THIS ARTICLE
This article is divided in two sections as the debug logs are different in Cosy131/Flexy and in Cosy+.
Enabling debug logs for Cosy131/Flexy
The Cosy131/Flexy modem implementation is based on AT commands and PPP layers to enable the 3/4G connection. The AT commands are used to configure and launch the modem connection. The PPP protocol is used to configure and establish the IP connection (3/4G).
The menu displayed below only exists in Ewon Flexy, even if the debug options also exist in Cosy131.
About the Cosy131, the support team has developed a custom Cosy131 webpage that regroups all the debug parameters needed to enable the debug logs : https://tools.ewonsupport.biz/CustomPages/ > Modem Troubleshooting page.
- Enable AT commands log
Go to Setup > System > Main > Debug and set the "Debug PPP Port" as well as the "Debug AT Port" options to "HEX and ASCII on RX/TX".
All the AT commands communication will be recorded into your real time logs
- Enable PPP Log
To record the PPP logs you must go to Setup > System > Main > PPP Dump :
- Check the options Log Incoming call & Log outgoing call
- Type a log size of 100000
- Check the option Append log.
The logs will then be recorded at the next cellular connection. You can force this reconnection by clicking "Disconnect" in the Internet connection settings (Setup > System > Communication > Internet connection > Main Setup).
To download the PPP logs, you can download the log file from Diagnostic > Files transfer menu > dump.ppp. This file can be opened using the software Wireshark.
The AT logs and the PPP logs are included into Ewon Backup files, when the option "include support files" is selected.
Enabling debug logs for Cosy+
For the Cosy+, the Modem implementation is no more done using AT commands and PPP protocol but using a standard component called ModemManager, that talks to the modem chip in QMI protocol.
There are two kind of modem logs in the Cosy+ : The logs showing the communication between the firmware and ModemManager component and the logs showing the communication between ModemManager and the modem itself.
- Enabling logs between the firmware and ModemManager
- Set the SYSTEM Config Parameter "ModemManagerZeroMQLog" to the analog value : 262137
- Simulate the problem
- Check the ZeroMQ messages in the real time logs (This log is therefore included into the Ewon Backup (including support files).
- Enabling the logs between ModemManager and the Modem chip. (QMI logs)
- Set the SYSTEM Config Parameter "ModemLoglevel2" to the string value "debug"
- Simulate the problem
- Download the Modem manager logs using the link http://<ewonIPaddress>/rcgi.bin/ParamForm?AST_Param=$dtML$fnLogText.txt
- You gonna get a txt file full of verbose logs. This log file is NOT included into the Ewon Backup file.