# Modify v0 UAVCAN GUI Tool for v1? **URL:** \ **Category:** PyCyphal\ **Created:** [January 26, 2021, 6:16pm UTC](https://forum.opencyphal.org/t/modify-v0-uavcan-gui-tool-for-v1/1089 "2021-01-26T18:16:19Z")\ **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 2, 2021, 2:52am UTC](https://forum.opencyphal.org/t/modify-v0-uavcan-gui-tool-for-v1/1089/2 "2021-03-02T02:52:42Z")
Hi Jacob! Sorry it took me forever to get back to this but I was knee-deep in PyUAVCAN. I think trying to revive the old GUI Tool would not be the best use of our resources. Instead, I recommend refocusing on Yukon, which has been relatively forgotten for the past few months but it seems to be accelerating again: > [@Yukon Take Three](https://forum.opencyphal.org/t/yukon-take-three/1139): > > A few months back I said that I am slowly working on a Yukon-related proposal. A [recent post](https://github.com/UAVCAN/yukon/issues/14#issuecomment-785655158) by @bbworld1 on GitHub made me realize that I better make my snail work slightly more visible to enable collaboration. Here we go: At this very moment, there is virtually nothing you could run and poke at (aside from a [silly demo script that doesn’t do much interesting](https://github.com/pavel-kirienko/yukon/blob/8269112d5e11d8b49c194bda20a9b908d0ca58ce/test.orc.yaml)), but I am turtle working on putting all the core blocks in place to make that possible. Once the groundwork around the DCS and th… If there is any chance to secure a bit of engineering help from your side, we could drive Yukon to a minimally-usable state in a relatively short amount of time. Do you think you or any of your colleagues who are experienced with Python could join? --- _[View the full topic](https://forum.opencyphal.org/t/modify-v0-uavcan-gui-tool-for-v1/1089)._