Unknown, Unhandled and Unexpected packets in output

[frakman1]

SUMMARY
Parser seems unable to correctly parse .qmdl file.

STEPS TO REPRODUCE

1- Use qlog on embedded Linux, arm32 architecture, device with Quectel EC25A module attached via USB.
2. Transfer .qmdl file to laptop capable of running scat (python3 etc)
20240702_155824_0000.qmdl.zip
3. Use scat: scat -t qc -d ./20240702_155824_0000.qmdl
4. See errors/warnings/issues:
scat_output.txt

EXPECTED and ACTUAL RESULT
No errors or issues parsing the file

ENVIRONMENT

• OS: [Same issue observed on Mac Sonoma 14.5, Windows 10 environment]
• SCAT version: 1.3.0
• Python version: 3.12.3
• Cellular device: Quectel EC25AFA-MINIPCIE to USB board
• Baseband type: Qualcomm?
• DIAG method: [USB, serial, or baseband dump] Not sure what this means but I ran qlog on a Linux host that had the module connected via USB. Interfaces were on /dev/ttyUSB0,1,2,3. NIC was ppp0

ADDITIONAL INFORMATION
The cellular connection was solid and working fine. I think it's LTE.
This was just a test to see what I can get from the logs.

Should I use the -C option to get the most output?
Are any of these Qualcom-specific options worth using?

Qualcomm specific settings:
  --qmdl QMDL           Store log as QMDL file (Qualcomm only)
  --qsr-hash QSR_HASH   Specify QSR message hash file (usually QSRMessageHash.db), implies --msgs
  --qsr4-hash QSR4_HASH
                        Specify QSR4 message hash file (need to obtain from the device firmware), implies --msgs
  --events              Decode Events as GSMTAP logging
  --msgs                Decode Extended Message Reports and QSR Message Reports as GSMTAP logging
  --cacombos            Display raw values of UE CA combo information on 4G/5G (0xB0CD/0xB826)

[peremen]

Thanks for your report.

2024-07-03 18:45:18,388 scat.qualcommparser (parse_lte_ml1_scell_meas_response) WARNING: Unknown LTE ML1 Serving Cell Meas Serving Cell Measurement Result subpacket version 18

You can ignore this error, basically it provides the same measurements as

Radio 0: LTE SCell: EARFCN 1175, PCI  58, Measured RSRP -94.94, Measured RSSI -64.19, Measured RSRQ -16.75
Radio 0: LTE NCell: EARFCN 1175, number of cells: 2
Radio 0: └── Neighbor cell 0: PCI 424, RSRP -100.94, RSSI -70.56, RSRQ -17.00
Radio 0: └── Neighbor cell 1: PCI  39, RSRP -95.69, RSSI -70.75, RSRQ -15.69

part. Since this may cause confusion, I may end up with adjusting the output. I am also getting the same error message on one of my modems too.

2024-07-03 18:45:18,386 scat.qualcommparser (parse_lte_mac_subpkt_v1) WARNING: Unhandled LTE MAC Subpacket ID 0x03
2024-07-03 18:45:18,386 scat.qualcommparser (parse_lte_mac_subpkt_v1) WARNING: Unhandled LTE MAC Subpacket ID 0x00
2024-07-03 18:45:18,537 scat.qualcommparser (parse_lte_mac_subpkt_v1) WARNING: Unhandled LTE MAC Subpacket ID 0x04

2024-07-03 18:45:18,460 scat.qualcommparser (parse_lte_pdcp_subpkt_v1) WARNING: Unexpected PDCP Cipher Data Subpacket version 3

MAC and PDCP support is limited. My intention was getting a MAC PDU/RAR, and some PDCP SDUs, but the support was never complete.

The -C, --combine-stdout function only changes the output path (terminal or libosmocore log), and does not affect the content of output. If you need to see signaling messages and log outputs simultaneously, only then you need this option.

The --qsr-hash and --qsr4-hash option is currently not implemented, but --events and --msgs is implemented and will retrieve the DIAG event and logs. --cacombos option is intended to get the support CA combinations, and parsing the hexadecimal output requires either QCAT or UE Capability Parser. Unless you want to go deeper, these options are not needed.

[frakman1]

Thank you for your detailed response and explanation.

I am still trying to understand what I can get from the qmdl file other than occasional cell information like this:

Radio 0: LTE SCell: EARFCN 1025, PCI  58, Measured RSRP -96.25, Measured RSSI -71.75, Measured RSRQ -10.50
Radio 0: LTE RRC SCell Info: EARFCN 1025/19025, Band 2, Bandwidth 5/5 MHz, PCI 58, xTAC/xCID 2c09/b23d8c0, MCC 310, MNC 410

Are you saying that I should use the --events and --msgs flags to get more information?

I just tried that and i don't see much more information.

scat -t qc --events --msgs -d ./20240702_155824_0000.qmdl > scat_output2.log
scat_output2.log

[peremen]

These two switches will report the events and log messages through GSMTAP logging packet. I think your use case is not directly related to what these switches offer. If the QMDL file does not contain the events and logs, then they won't be included in neithger GSMTAP logging nor stdout.