# Modify v0 UAVCAN GUI Tool for v1?

**URL:** <https://forum.opencyphal.org/t/modify-v0-uavcan-gui-tool-for-v1/1089>\
**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:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JacobCrabill](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/jacobcrabill/32/746_2.png) [@JacobCrabill](https://forum.opencyphal.org/u/JacobCrabill)\
**Post date:** [January 26, 2021, 6:16pm UTC](https://forum.opencyphal.org/t/modify-v0-uavcan-gui-tool-for-v1/1089/1 "2021-01-26T18:16:19Z")

</div>

I know that the new application, Yukon, has in the works for the past year and is supposed to have lots of nice new features, but having a more bare-bones solution in place (that is a step above a CLI) would be extremely useful for most system-setup use cases. Basically, what would cover most of my needs is:

1. Ability to see a list of all active nodes on the bus
2. Ability to fetch all parameters from a node and view them in a table
3. Ability to modify and “save” (send) parameters back to a node
4. Bonus: The Bus Monitor, with its handy message decoding
5. Bonus: The Jupyter-style interface

That’s really it. Yakut works, but trying to setup a large system with it sounds quite painful.

Thoughts? I haven’t really looked into the details of the UAVCAN GUI Tool; how difficult would this be to strip it down to just a simple register interface?

---

<div class="post-metadata">

**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")

</div>

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?