Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap and missing features #3

Open
8 of 25 tasks
MrKevinWeiss opened this issue Jun 14, 2023 · 1 comment
Open
8 of 25 tasks

Roadmap and missing features #3

MrKevinWeiss opened this issue Jun 14, 2023 · 1 comment
Assignees
Labels
tracking Tracking a large amount of issues

Comments

@MrKevinWeiss
Copy link
Contributor

MrKevinWeiss commented Jun 14, 2023

A number of planned features...

  • Add optional power control
    • Check if power control available for which boards
    • Turn all ports on by default whenever checking connection
    • Turn all unused off commissioned nodes by default once the action is complete
    • flags to prevent power options
    • Generic command to turn on all ports or specific nodes
    • Caching usb locations
  • cleanup exception handling
  • remove all or one board
  • allow user boards that will not get overwritten
  • Nice readme with some gifs of usage (added in 07e7a50)
  • Add a CLI way and example get the port live based off UID to handle reconnecting within tmux session (Added a while ago)
  • Improve getting started
  • Add a session or exec timeout that will abort if the call takes too long
  • Add tests that go through the cli (14642b3)
  • Have a way to check who is locking the board (Log which user is blocking)
  • Document server setup and permission requirements
  • Add inet-nm-check to show a table will what is available/used/missing/feature_matched
  • customize commands and envs in config file
  • Add uid to check selection
  • Time being used (logging system)
  • Capture more than com ports (debugger, generic connection, modbus?, power)
  • Distribution to other CPUs (host name, maybe just ssh connection?)
  • Recently used or tied to a session so it can be reused
  • grouping of devices (for example a board, programmer, power profiler)
@MrKevinWeiss MrKevinWeiss added the tracking Tracking a large amount of issues label Jun 14, 2023
@MrKevinWeiss MrKevinWeiss self-assigned this Jun 14, 2023
@MrKevinWeiss
Copy link
Contributor Author

Some things that should be done before having actual users:

  • power control
  • versioned configs
  • remove CLI settable config files
  • move some caches into the .cache/ folder
  • simpler examples

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracking Tracking a large amount of issues
Projects
None yet
Development

No branches or pull requests

1 participant