[Feature]: Plotting sensor stats via UDP/TCP as opposed to direct UART

Open
#10 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
frontend, networking

Research direction

The issue names no files, tests, or entry points. Start by tracing the existing direct-UART plotting path and its data format, then determine the scope of UDP/TCP support and central-console connectivity. Done should mean equivalent sensor logging from multiple remote devices through the web console.

Written by the indexing model from the issue text.

Description

enhancement
Problem to solve

Many of our test devices are in remote locations, hence no direct UART connection.

All we need is the ability to log sensor settings from multiple devices via internet to central web console.

Proposed solution

It would help if the APP could be addressed via UDP or TCP, exact same functionality, same data format, just different medium.

Alternatives considered

No response

Area of the app

None

Willingness to contribute
  • I'd be willing to submit a PR for this
  • I can help test and provide feedback
Additional context, screenshots or mockups

No response

Dominant language
TypeScript
Stars
198
Forks
25
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from atomic14/web-serial-plotter

All issues in atomic14/web-serial-plotter

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.