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

Power/cap bug by @Bonio #1

Open
piratfm opened this issue Dec 17, 2014 · 1 comment
Open

Power/cap bug by @Bonio #1

piratfm opened this issue Dec 17, 2014 · 1 comment

Comments

@piratfm
Copy link
Owner

piratfm commented Dec 17, 2014

Кстати, я нашел один баг. Попробую описать.
По моему он связан со значение согласующей емкости или с флагом "автонастройка".
Заключается он в том, что при запуске передатчика, он запускается не на 100% мощности. Решение - повторное нажатие на кнопку "отправить конфигурацию из программы в передатчик".
Проявляется не во всем диапазоне. Зависит от того, какое значение согласующей емкости было последний раз записано.
Решается так же указанием конкретной согласующей емкости, но тогда максимальная мощность будет отдаваться только на одной частоте, неудобно.

@XPA1
Copy link

XPA1 commented Feb 15, 2022

To Anyone Who Dont Know What they said they Said Was:

By the way, I found one bug. I'll try to describe.
In my opinion, it is associated with the value of the matching capacitance or with the "auto-tuning" flag.
It consists in the fact that when the transmitter is started, it does not start at 100% power. The solution is to press the "send configuration from the program to the transmitter" button again.
It doesn't show up in the whole range. Depends on what matching capacitance value was last recorded.
It is also solved by indicating a specific matching capacitance, but then the maximum power will be given only at one frequency, which is inconvenient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants