Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
does this sound like a bad encoder or just operator error?
#w8tee
|
I am leaning toward operator error, but I am wondering if I have a bad encoder.? I finally found the time to put together Jack's VFO board.? I have not connected it to my BITX40 yet but the following behavior occurs either with a USB cable connected to the Arduino board or with 12v applied directly to the power in on the VFO board.? After paying attention and getting the libraries installed correctly I got W8TEE's 1.05 and 1.05 to compile and load correctly.? Everything seems to look ok except the WPM text is not aligned correctly.? I remember seeing another post about that and will track that down later.? My problem is turning the encoder did nothing.? Just for sport I installed 1.00 and not only did the WPM text appear correctly but the encoder works.? It tuned opposite of what I expected but switching the clock and data leads fixed that.? Additionally, I can not get fast tune to work.? The longer I stare at this the dumber I get so I need to walk away for the night.? Does this jump out at anyone as a software or hardware problem or anything obvious that I have been overlooking?
thanks, |
|
Jack Purdum
I just posted 1.06. See if that helps. Jack, W8TEE From: Doug W <KD9CYF@...> To: [email protected] Sent: Monday, August 14, 2017 11:08 PM Subject: [BITX20] does this sound like a bad encoder or just operator error? #w8tee I am leaning toward operator error, but I am wondering if I have a bad encoder.? I finally found the time to put together Jack's VFO board.? I have not connected it to my BITX40 yet but the following behavior occurs either with a USB cable connected to the Arduino board or with 12v applied directly to the power in on the VFO board.? After paying attention and getting the libraries installed correctly I got W8TEE's 1.05 and 1.05 to compile and load correctly.? Everything seems to look ok except the WPM text is not aligned correctly.? I remember seeing another post about that and will track that down later.? My problem is turning the encoder did nothing.? Just for sport I installed 1.00 and not only did the WPM text appear correctly but the encoder works.? It tuned opposite of what I expected but switching the clock and data leads fixed that.? Additionally, I can not get fast tune to work.? The longer I stare at this the dumber I get so I need to walk away for the night.? Does this jump out at anyone as a software or hardware problem or anything obvious that I have been overlooking? thanks, |
|
Thanks for the quick reply and all your work on this.? I actually did try 1.06 before posting.? That's a typo in my first post.? Where I said 1.05 and 1.05 I meant to say 1.05 and 1.06.? I have the same issue with both but the darn thing works with 1.00.? I am sure I am overlooking something dumb but I should call it a night before I trade mouse for hammer.
|
|
Jack Purdum
DId you check the #defines for the encoder controls? I had to change the pin numbers because some Mega 2560 clones don't process INT05 correctly. I also had to move the encoder switch pin. Look around line 115: #define ENCODERPINA ? ? ? ? ?19 ? ? ? // Encoder pin A, interrupt 4 #define ENCODERPINB ? ? ? ? ?20 ? ? ? // Encoder pin B, interrupt 3 #define ENCODERSWITCH ? ? ? ?22 ? ? ? // Encoder switch pin It's always worthwhile looking at the code, but I neglected to tell everyone about the change in pin numbers. Sorry about that. Jack, W8TEE From: Doug W <KD9CYF@...> To: [email protected] Sent: Monday, August 14, 2017 11:24 PM Subject: Re: [BITX20] does this sound like a bad encoder or just operator error? #w8tee Thanks for the quick reply and all your work on this.? I actually did try 1.06 before posting.? That's a typo in my first post.? Where I said 1.05 and 1.05 I meant to say 1.05 and 1.06.? I have the same issue with both but the darn thing works with 1.00.? I am sure I am overlooking something dumb but I should call it a night before I trade mouse for hammer.
|
|
John P
On Mon, Aug 14, 2017 at 08:08 pm, Doug W wrote:
I am wondering if I have a bad encoderIf it works with version 1.0, then most likely it's not a hardware problem. But do I know the feeling of staring at code for hours trying to figure something like that out. At least once upon a time, I got paid to?do that! ? -- John - WA2FZW |
|
Doug
Jack gave you a big clue, if your encoder worked with ver 1.0 it's OK. ?I had the same problem with 1.05 and now with 1.06, it's an easy fix. If you do this change it will give you the same encoder pins as in ver 1.0. #define ENCODERPINA ? ? ? ? ?18 //19 ? ? ? // Encoder pin A, interrupt 5
#define ENCODERPINB ? ? ? ? ?19 //20 ? ? ? // Encoder pin B, interrupt 4
#define ENCODERSWITCH ? ? ? ?20 //22 ? ? ? // Encoder switch pin
I've also noticed the gap between the WPM and mode boxes, I think that it's the WPM box that's high. Regards? David G8DJM |
|
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: [email protected] 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.?
|
|
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.
|
|
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: [email protected] 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.
|
|
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. |
to navigate to use esc to dismiss