[HW] Zaprojektowanie nowych SafetyPinów
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
- Mostly clear
- Activity status
- Active
- Domain
- embedded-iot
Research direction
Read the competition rules and the issue’s requirements for four independent power channels, a maximum of one small board, and standalone operation. The issue suggests XT30/XT60 jumper connectors and asking Jan Sacharuk about alternatives; compare options against those requirements and the rules. Done means selecting a compliant safety-pin design that can physically switch all four channels independently.
Written by the indexing model from the issue text.
Description
Regulamin konkursu wymaga metody aby fizycznie móc włączyć/wyłączyć zasilanie. Ten system musi mieć kilka niezależnych kanałów:
- COTS 1 - system zapasowego komputera 1 (odzysk)
- COTS 2 - zapasowy system zapasowego komputera 2 (odzysk)
- SRAD 1 - zasilanie logiki Avioniki
- SRAD 2 - zasilanie actuatorów Avioniki (serwa etc)
Fajnie jakby był to możliwie najprostrzy system, na konkursie podpatrzyliśmy że niektóre zespołu stosują po prostu "zworki" na bazie XT30 / XT60 które fizycznie zwierają kable, to jedno z sensowniejszych rozwiązań, ale Jan Sacharuk znalazł też jakieś lepsze alternatywy, może warto by go podpytać
Wymagania:
- 4 niezależne kanały
- Maksymalnie 1 mała płytka
- brak ingerencji w reszte systemów, jest tot system bezpieczeństwa i musi sobie radzić sam
- zgodność z regulaminem konkursu
- 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