-
Notifications
You must be signed in to change notification settings - Fork 2
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
question about: docs/schematic.txt #3
Comments
Since the GPIO only outputs a DC voltage, simply connecting it directly to the TX keying circuit will not work (in addition, the direct connection may cause the RaspPi to fail.) |
Ok. Thanks for the explanation. A mechanical relay or SSR could also be used... probably..... I use one of those with a different Pi in my garage to control my driveway gate. I'll see about using that to control the TX on the rig. Will let you know how it goes. Thanks again. |
Had another question(s) about the schematic.txt file... Is the 1k ohm resistor and the 10uF cap on the pwm output to the speaker really needed.... i.e. what is their purpose. For 'testing' I just hooked up GPIO18 directly to my Kenwood SP-930 speaker and I heard tone. Sounded fine to me.... are those extra components really that important? AND... you have 3 pins listed on the Side Tone Out... but I guess you just use 2.... R and E (common ) What are 'L', 'R', and 'E' supposed to mean.... of you're only using 2 pins for speaker... why list 3... that confuses me. ( I confuse easily ) |
The resistor may serve as a protective measure by limiting overcurrent, mitigating the impact of excessive current that the PWM signal might induce. And its output is intended to be output from a stereophone jack, so there are left(L) and right(R) terminals. |
In the docs/schematic.txt file you say:
(future plan:
TX control)
for GPIO22
does that mean that the TX function of the code..... TX of rig connected to GPIO22 won't work if I connect my transmitter to that pin or what exactly.... what is 'future' about that pin?
The text was updated successfully, but these errors were encountered: