# Looking for a way to record CAN log to file (UAVCAN GUI app) **URL:** \ **Category:** Applications & Usage\ **Created:** [February 24, 2020, 8:15am UTC](https://forum.opencyphal.org/t/looking-for-a-way-to-record-can-log-to-file-uavcan-gui-app/763 "2020-02-24T08:15:09Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![VadimZ](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/vadimz/32/434_2.png) [@VadimZ](https://forum.opencyphal.org/u/VadimZ)\ **Post date:** [February 24, 2020, 8:15am UTC](https://forum.opencyphal.org/t/looking-for-a-way-to-record-can-log-to-file-uavcan-gui-app/763/1 "2020-02-24T08:15:09Z")
Is there a way to record all received messages to a text file for later analysis, using UAVCAN GUI tool ? Ideally, in txt format as shown in bus monitor currently. ---
**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\ **Post date:** [February 25, 2020, 1:17am UTC](https://forum.opencyphal.org/t/looking-for-a-way-to-record-can-log-to-file-uavcan-gui-app/763/2 "2020-02-25T01:17:29Z")
Nope. Check these out: > [@What should our logging format be?](https://forum.opencyphal.org/t/what-should-our-logging-format-be/764): > > I long for a logging format in the specification. The requirements for a logging format: Self-describing – We want a way to persist data without needed external links to message definitions. Storage Efficient – The format must be optimized allow huge datasets to occupy reasonable amounts of file storage. Should we attempt to utilize ulog? [https://dev.px4.io/v1.9.0/en/log/ulog\_file\_format.html](https://dev.px4.io/v1.9.0/en/log/ulog_file_format.html) If not, is there a better standards to adopt? [https://github.com/UAVCAN/pyuavcan/issues/74](https://github.com/UAVCAN/pyuavcan/issues/74) Would you be interested in collaborating with us to enable this feature in PyUAVCAN, and then, by extension, in Yukon?