Testowanie poboru oraz logowanie
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- embedded-iot
Research direction
Start by locating the ServoService implementation and the existing current and voltage driver interfaces. Clarify the measurement duration, output values, threshold for active operation, configuration-file format, and logging format before implementing. Validate the chosen behavior with test measurements and confirm that the selected values are written to a file and logged through the existing mechanism.
Written by the indexing model from the issue text.
Description
User Story
Mamy na serwach mierniki prądu, mają one napisany driver, trzeba tylko dokończyć implementacje ich pomiarów w ServoService oraz wymyślić przrez jaki czas mają mierzyć prąd i co zwracać jako wynik. Myślałem o logowaniu do pliku wartosci napięcia i prądu co x ms albo logowaniu do pliku wartości maksymalnej pobranej mocy [W], średniej mocy w czasie działania oraz czasu działania gdzie czas działania byłby wyznaczany przez pobór prądu większy niż X.
TODO
- dokończyć implementację w ServoService
- wykonać testowe pomiary przebiegów
- zrobić wczytywanie konfiguracji z pliku
- zaimplementować zapis do pliku wybranych wartości w wybranej formie (powyższe dane powinny być również logowane po dlt)
- Dominant language
- C++
- Stars
- 1
- Forks
- 3
- Avg merge
- 14h 51m
- Merged PRs (30d)
- 7
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Simba-Avionic/srp
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Simba-Avionic/srp#510 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Simba-Avionic/srp#509 ·
Maintainers usually reply within 1 day
-
[SW] OptymalizacjaOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
Simba-Avionic/srp#508 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Simba-Avionic/srp#507 ·
Maintainers usually reply within 1 day
-
[SW] Prepeare Cross-compilation for rpiPossibly taken @Mateusz-Krajewski claimed this today. Open
Simba-Avionic/srp#506 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in Simba-Avionic/srp
Similar issues
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ROCm/FastFlowLM#1057 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NatronGitHub/openfx-gmic#45 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
app area::installer bug wg::gui-app
Difficulty 1/5 Under an hour Newbie friendliness 88/100
lemonade-sdk/lemonade#4186 ·
Maintainers usually reply within 1 day