I would like to automate the message extraction from a acquired trace file.
User: we are a module maker producer
Context: Cell modules based on different Qualcomm chip-set, like the QXC216
Tools used: EPAT V1.3.265.576
Target : extract a specific message type, we want to extract, for example TPDU exchanged from SIM and Qualcomm chip
Present situation: all actions are performed manually
Lunch EPAT
Load binary trace file
Load database file
Select some columns (PC time and message)
Search TPDU messages R and C type
Save messages found, in csv format
merge messages to create e proper finale TPDU messages with external pyhton script
convert the result with text2pcap.exe to generate a pcap for WireShark
Result is a pcap
The idea is to automate the process. Is it possible ? Is it possible to access to the EPAT .dll directly in some way
Yes, you can reduce most of the manual work, but EPAT does not publicly document any supported scripting API / SDK / “call EPAT .dll” interface, the EPAT User Guide only describes GUI operations (load log/DB, filter/search, export).
What we recommend for automation is:
In EPAT, use SigLogger → SigLog → Only Show Protocol Signalling to focus on NAS/AS signalling.
Use Ctrl+F Search/Filter; EPAT supports filtering multiple keywords using regex with |.
Export directly to PCAP via SigLog → “Export As PCAP File”.
Then fully automate the rest outside EPAT (TPDU/UIM selection + reassembly) using Python on the exported PCAP (tshark/pyshark/scapy), instead of relying on manual CSV export/merge.
If your goal is true “one-click / unattended” (open trace + load DB + filter + export), the practical option is desktop UI automation (e.g., pywinauto/AutoIt), since EPAT’s public docs don’t expose an API
Kindly reach out to me if you need any further clarification.