Yet Another Cyphal Textual User Interface

Applications & Usage
1

I’m making a simple TUI for Cyphal which is a little different than yakut monitor and I wanted to gather some suggestions beyond what I was already going to do:

  • Subscriptions
    • Heartbeats
    • Time Sync (as backup master / peer)
    • diagnostic Records (writes to log)
    • portlist
  • Publishes
    • Time Sync (when master)
  • Clients
    • GetInfo
    • Transport Statistics

I’m using textual the Python framework to render the UI elements in the terminal itself, enabling remote viewing over ssh without forwarding traffic.

The initial demo has a space for Cyphal/UDP + CAN + Serial all together. Are we still at a point with pycyphal that it can’t operate all 3 transports at once?

2

Neat.

A few months back we discussed the idea of dropping the application layer in Cyphal v1.1 completely. Per that proposal, which originated from me but IIRC @scottdixon seemed at least somewhat aligned with, we will have just two standard types: the heartbeat and a generic CRUD input/output service on raw bytes. The v1.0 types will stay as a legacy (them being in the old uavcan namespace is a good reminder of their status).

Given that, I think that maybe there is value in replacing special-case pub/sub/clients with generic ones that work on any type?