Keyboard Shortcuts
Likes
- BITX20
- Messages
Search
Re: Muffled and poor audio
#bitx20help
Your mileage may vary. On Tue, Aug 15, 2017 at 10:07 am, chris gress wrote:
|
Re: Muffled and poor audio
#bitx20help
I second the C102 change.? Also, monitor your power output while transmitting.? If it is lower than 5W, turn RV136 counterclockwise to increase PA gain as described at the bottom of the page here:.
http://www.hfsigs.com/bitx40v3_wireup.html |
Re: Muffled and poor audio
#bitx20help
chris gress
Change c102 to 27pf that will make LSB sound so much better I use the supplied mic chris? On 15 Aug 2017 18:02, "Fernando Garcia" <ferjanyen@...> wrote: Had reports of muffled and poor audio, any sugestions anyone?? |
Re: Encoder tinning
Vince Vielhaber
Look again:
r is defined more than once.#include <Rotary.h> Vince. On 08/15/2017 11:40 AM, Jack Purdum via Groups.Io wrote: He's not redefining the object/r/. He is defining an /unsigned char/-- Michigan VHF Corp. |
Re: W8TEE VFO Board
prizmev@gmail.com
Jack,
I sent payment for one board the other day. I didn't check first though...? Sent from prizmev@...? Let me know if you need more info. Ralph |
Re: Radio's
I wonder which radio is his favorite to operate? That's one heck of console! Looks like a person can visit the island per a reservation. ?40 years ago I and XYL visited the Door county at the tip.? Only way out to Washington Island is by ferry or private boat. I'd sure like to QSO W9EVT using my BITX40 Larry WA9DOH On Tue, Aug 15, 2017 at 10:37 AM, Jack Purdum via Groups.Io <econjack@...> wrote:
|
Re: Radio's
Hah, no kidding.? Washington Island has it's own wind turbine to supplement power coming over from the mainland.? They probably put it up just for him. I was just out on Washington island last fall.? I wish I would have known about this then.? Apparently he gives tours. On Tue, Aug 15, 2017 at 10:37 AM, Jack Purdum via Groups.Io <econjack@...> wrote:
|
Re: Encoder tinning
Jack Purdum
He's not redefining the object r. He is defining an unsigned char variable named result into which he is assigning the return value from the process() method of the ?r object. There should be no compiler error from that. Jack, W8TEE From: Vince Vielhaber <vev@...> To: BITX20@groups.io Sent: Tuesday, August 15, 2017 10:58 AM Subject: Re: [BITX20] Encoder tinning You're going to get an error or warning for redefining r.? You've definied it globally right under your include statement, then again in setup.? In setup it's only local but you'll still get an error/warning. Vince. On 08/14/2017 08:21 PM, Norberto Modanesi wrote: > Hi folks: > What if I add these lines to the Raduino code > #include <Rotary.h> > Rotary r=Rotary(3, 2); > > comment out? analogtinnig? A7 > > in setup() > Rotary r=Rotary(3, 2); > > Then the interrupt routine > ISR(PCINT2_vect) { >? unsigned char result = r.process(); >? if (result == DIR_CW) >? ? counter=counter+1; >? ? if(counter>1020){counter=1020;} >? else if (result == DIR_CCW) >? ? counter = counter-1; >? ? if(counter<5){counter=5;} >? ? Serial.println (counter); > >? ? } > Finaly, replace every analoRead(analogtunning) with counter.- > > Would it work? > > 73 de LU5DNM > > Norberto Modanesi > San Nicolás > > > -- ? Michigan VHF Corp.? ? ? ? ? ? ? ? ? ? ? ? ? ? ? |
Re: Radio's
Jack Purdum
Holy Crap, Batman! I wonder if he can operate all of them at one time? That would likely cause the city to go dim. I think that, rather than finding out where he managed to find all of that gear, I'd like to know where he found his XYL. Jack, W8TEE |
Re: does this sound like a bad encoder or just operator error?
#w8tee
Vince Vielhaber
On 08/14/2017 11:57 PM, John P wrote:
On Mon, Aug 14, 2017 at 08:08 pm, Doug W wrote:...just to have the problem sitting right in front of you staring right at you and you STILL don't see it. Been there, done that, didn't bother buying the t-shirt - it was ugly anyway. Vince. -- Michigan VHF Corp. |
Re: Encoder tinning
Vince Vielhaber
You're going to get an error or warning for redefining r. You've definied it globally right under your include statement, then again in setup. In setup it's only local but you'll still get an error/warning.
toggle quoted message
Show quoted text
Vince. On 08/14/2017 08:21 PM, Norberto Modanesi wrote:
Hi folks: --
Michigan VHF Corp. |
Re: BITX QSO Night, Sunday, August 13, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere
Heard same strong?growling transmission and it showed on SDR about 7285.? The growling bled over on to 7277 my thought was "there goes the BITX night".? Then it disappeared.? I think I'll dig out my old cassette recorder and try open mic. record for about 30 min.? Could be interesting audio log. 73 WA9DOH On Mon, Aug 14, 2017 at 11:18 AM, Karl Schwab via Groups.Io <ktschwab@...> wrote:
|
Re: does this sound like a bad encoder or just operator error?
#w8tee
Jack Purdum
That's good news. You should NOT beat yourself up on not detecting the switch...that's my fault. Users of the PCB should not have to worry about what the code is doing. I am going to change the assembly manual to warn them about a likely fix for an "unresponsive" encoder. The fact that you had to switch the pins back probably means that the INT05 vector is okay on your Mega. I would expect most people to have a "healthy" Mega, but I did read about it on the Arduino users group and I do have one myself. Considering I have purchased about 75 units of the Mega 2560 Pro Mini, that's a pretty small failure rate and might just be bad luck. Jack, W8TEE From: Doug W <KD9CYF@...> To: BITX20@groups.io Sent: Tuesday, August 15, 2017 9:40 AM Subject: Re: [BITX20] does this sound like a bad encoder or just operator error? #w8tee Thank you, that did the trick.? I should have compared the two versions when one worked for me and the other didn't.? This fancy Arduino stuff is still new to me but I missed a basic trouble shooting step and for that I got an ear full from the guy in the mirror.? I did still have to switch the pins for data and clock.
|
Re: does this sound like a bad encoder or just operator error?
#w8tee
Thank you, that did the trick.? I should have compared the two versions when one worked for me and the other didn't.? This fancy Arduino stuff is still new to me but I missed a basic trouble shooting step and for that I got an ear full from the guy in the mirror.? I did still have to switch the pins for data and clock.
|
Re: does this sound like a bad encoder or just operator error?
#w8tee
Jack Purdum
If your encoder works with the pins as they are marked on the board and an earlier release of the software, I would use those. I think from now on, I'll put both sets of symbolic constants in the code, but comment one set out, like this: #define ENCODERPINA ? ? ? ? ?18 ? ? ? // Encoder pin A, interrupt 5 #define ENCODERPINB ? ? ? ? ?19 ? ? ? // Encoder pin B, interrupt 4 #define ENCODERSWITCH? ? ? ? 20 ? ? ? // Encoder switch pin /* ? ? ? ? ? ? // Try these pin assignments if the encoder does not work with your Mega #define ENCODERPINA ? ? ? ? ?19 ? ? ? // Encoder pin A, interrupt 4 #define ENCODERPINB ? ? ? ? ?20 ? ? ? // Encoder pin B, interrupt 3 #define ENCODERSWITCH ? ? ? ?22 ? ? ? // Encoder switch pin */ This will keep the original set of pins as marked on the PCB and assumes that your board does not have an issue with the INT05 interrupt vector. Note that I changed the earlier symbolic constant SWITCH to ENCODERSWITCH because some builders may have added other switches to the circuit. Sorry for the confusion. Jack, W8TEE From: RCC WB5YYM <curtis03@...> To: BITX20@groups.io Sent: Tuesday, August 15, 2017 8:36 AM Subject: Re: [BITX20] does this sound like a bad encoder or just operator error? #w8tee Do ya'll recommend changing the code, or changing the wiring to the encoder? As things progress, I want to keep mine as "standard" as possible.?
|
W8TEE Encoder issues
Jack Purdum
All:
I changed the pin numbers associated with the encoder because some Mega 2560 clones don't process INT05 correctly and we were using that interrupt vector on pin 18. I also moved the encoder switch pin at the same time. Look around line 115 in Rel. 1.06 for the new encoder pin symbolic constants: ?
#define ENCODERPINA ? ? ? ? ?19 ? ? ? // Encoder pin A, interrupt 4
#define ENCODERPINB ? ? ? ? ?20 ? ? ? // Encoder pin B, interrupt 3
#define ENCODERSWITCH ? ? ? ?22 ? ? ? // Encoder switch pin
?
If your encoder worked with an earlier release, change the pin numbers you see above back to the pin numbers you were using previously. That should fix the problem. ?
Jack, W8TEE |
Re: does this sound like a bad encoder or just operator error?
#w8tee
Do ya'll recommend changing the code, or changing the wiring to the encoder? As things progress, I want to keep mine as "standard" as possible.?
|
Re: Encoder tinning
?
toggle quoted message
Show quoted text
Yes. I put Serial.print in ISR only to see how
counter goes up and down.-
?
Norberto Modanesi
San Nicolás
|