# Param getset for string types fails to be read by UAVCAN GUI tool **URL:** \ **Category:** Libcanard\ **Created:** [March 5, 2020, 4:34am UTC](https://forum.opencyphal.org/t/param-getset-for-string-types-fails-to-be-read-by-uavcan-gui-tool/772 "2020-03-05T04:34:09Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [March 5, 2020, 5:28pm UTC](https://forum.opencyphal.org/t/param-getset-for-string-types-fails-to-be-read-by-uavcan-gui-tool/772/2 "2020-03-05T17:28:59Z")
This is probably caused by the known bug in PyUAVCAN v0: [https://github.com/UAVCAN/pyuavcan/issues/32](https://github.com/UAVCAN/pyuavcan/issues/32) We do not have any resources committed to fixing that because v1 is the focus of the current development. Have you considered migrating to v1? Libcanard v1 is already usable: > [@Libcanard for UAVCAN/CAN v1 is released](https://forum.opencyphal.org/t/libcanard-for-uavcan-can-v1-is-released/774): > > Libcanard v0.100, implementing UAVCAN/CAN v1, is now available: Key features: Full test coverage and static analysis. Partial compliance with automatically enforceable MISRA C rules (compliance report not available). Detailed time complexity and memory requirement models for the benefit of real-time high-integrity applications. Purely reactive API without the need for background servicing. Support for CAN FD. Support for redundant transports. Compatibility with 8/16/32/64-bit platforms. The… --- _[View the full topic](https://forum.opencyphal.org/t/param-getset-for-string-types-fails-to-be-read-by-uavcan-gui-tool/772)._