Date   

Re: Tuning reversed issue

Gordon Gibby <ggibby@...>
 

Using FLDIGI, you can put your RTTY tonesanywhere you want them.....

And by watching the waterfall, you can visualize your receiving filter as well.

gordon


________________________________________
From: BITX20@groups.io <BITX20@groups.io> on behalf of Tim Gorman <tgorman2@...>
Sent: Sunday, January 7, 2018 11:36 PM
To: BITX20@groups.io
Subject: Re: [BITX20] Tuning reversed issue

Jim,

Aren't RTTY tones 2125hz and 2295hz? The filter in the ubitx should be
narrow enough to filter out 2nd and 3rd harmonics of these frequencies.

If it can't filter out the harmonics of these tones then the SSB voice
signal is probably also far wider than it should be.

tim ab0wr



On Sun, 07 Jan 2018 18:11:44 -0800
"Jim Sheldon" <@W0EB> wrote:

After Ron helped me get over the "stupids" and I finally learned how
to properly compile & upload stuff to the Raduino, I now have Ron's
mods running and he's fixed a lot of little annoying things (annoying
to me anyway). In between bricking & fixing the rig (all firmware,
no hardware) I managed to make a couple of real nice 20 meter SSB
QSO's and also a couple of 40 meter CW QSO's as well with it.

I heard a lot of RTTY (contest this weekend) and sure wish there were
at least 5 more digital pins on the Nano. Then it would really easy
to implement a good CW Keyer and even implement true FSK for RTTY.
You'd still need a computer with sound card running something like
Mako Mori's (JE1HHT) MMTTY program, but that would really work well.
Hardware FSK would be much cleaner to implement than tones into the
SSB section. As wide as the filter is, I'd be wary of the 2nd and
maybe even 3rd harmonics of the tones being transmitted at the same
time as the fundamentals. That would really create havoc on the
bands especially during a RTTY contest, not to mention incur the
wrath of the FCC as well.

Jim - W0EB

This little rig just keeps getting better and quite rapidly too!


Re: Tuner Kit Progress

K9HZ <bill@...>
 

There is plenty of overlap in the inductance rank now.  The final kit will probably be closer to doubling. 


Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ

 

Owner - Operator

Big Signal Ranch – K9ZC

Staunton, Illinois

 

Owner – Operator

Villa Grand Piton - J68HZ

Soufriere, St. Lucia W.I.

Rent it: www.VillaGrandPiton.com


email:  bill@...

 


On Jan 7, 2018, at 9:06 PM, Kelly Jack <kellyjack1968@...> wrote:

Hi Bill,

Great project. Very interested in this as a remote tuner. 

One query - why are the last two 5.2uH and 10.6uH as opposed to continuing to double up? Not a criticism just seeking to understand.

Regards

Simon VK3ELH 


Re: Tuning reversed issue

Tim Gorman
 

Jim,

Aren't RTTY tones 2125hz and 2295hz? The filter in the ubitx should be
narrow enough to filter out 2nd and 3rd harmonics of these frequencies.

If it can't filter out the harmonics of these tones then the SSB voice
signal is probably also far wider than it should be.

tim ab0wr



On Sun, 07 Jan 2018 18:11:44 -0800
"Jim Sheldon" <@W0EB> wrote:

After Ron helped me get over the "stupids" and I finally learned how
to properly compile & upload stuff to the Raduino, I now have Ron's
mods running and he's fixed a lot of little annoying things (annoying
to me anyway).  In between bricking & fixing the rig (all firmware,
no hardware) I managed to make a couple of real nice 20 meter SSB
QSO's and also a couple of 40 meter CW QSO's as well with it.

I heard a lot of RTTY (contest this weekend) and sure wish there were
at least 5 more digital pins on the Nano.  Then it would really easy
to implement a good CW Keyer and even implement true FSK for RTTY.
You'd still need a computer with sound card running something like
Mako Mori's (JE1HHT) MMTTY program, but that would really work well.
Hardware FSK would be much cleaner to implement than tones into the
SSB section.  As wide as the filter is, I'd be wary of the 2nd and
maybe even 3rd harmonics of the tones being transmitted at the same
time as the fundamentals.  That would really create havoc on the
bands especially during a RTTY contest, not to mention incur the
wrath of the FCC as well.

Jim - W0EB

This little rig just keeps getting better and quite rapidly too!


Re: BITX QSO Night, Sunday, January 7, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere

at91r40008
 

Same here I didn't hear anything.
--
73, Yvon NU6I


Re: BITX QSO Night, Sunday, January 7, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere

John P
 

I've been lobbying for an afternoon time for months now. A few of us got on at 3PM EST a month or so ago and made a number of contacts.

So if anyone can agree on a betting time I'm in. 
--
John - WA2FZW


Re: BITX QSO Night, Sunday, January 7, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere

Gordon Gibby <ggibby@...>
 

This is kinda  normal....the critical frequency (vertical 180 degree refraction) is dropping to 80 meters or BELOW right after dark over a lot of North America....traffic hounds in the north are having to use 160 meters at times....   


Cuba station checked into my WINLINK server in late afternoon on 40 meters --- 570 km south of me, great propagation.  


Australia has multiple web pages that show exactly how propgation is going and what frequencies will work for what distances, anywhere in the world, all based on radioionosonde data gathered from those stations scattered around the world.....


take a look at this web page:   http://www.sws.bom.gov.au/HF_Systems/6/5


As I write this, the critical frequency for most of north america is TWO MEGAHERTZ.


If you're working a longer distances, the MUF will of course be higher than the CRITICAL FREQUENCY as glancing signals are much more easily refracted than straight-up-and-down ones, but this is all fairly well understood and available information now for all of us to use!


Cheers,


gordon




From: BITX20@groups.io <BITX20@groups.io> on behalf of Tom VE3THR <muzzmobility@...>
Sent: Sunday, January 7, 2018 11:03 PM
To: BITX20@groups.io
Subject: Re: [BITX20] BITX QSO Night, Sunday, January 7, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere
 
noticed same thing here up north since last fall. After grey line NOTHING! Local path only. I suggest earlier times - 4pm EDT - 2100 Z perhaps. Real hit and miss an evening net this time of year and crappy propagation. Thanks for trying. I usually listen on 7.277 during the day if I'm in the shack and not doing my "chores". Don't be afraid to call CQ anytime anywhere.


Re: BITX QSO Night, Sunday, January 7, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere

Tom VE3THR
 

noticed same thing here up north since last fall. After grey line NOTHING! Local path only. I suggest earlier times - 4pm EDT - 2100 Z perhaps. Real hit and miss an evening net this time of year and crappy propagation. Thanks for trying. I usually listen on 7.277 during the day if I'm in the shack and not doing my "chores". Don't be afraid to call CQ anytime anywhere.


Re: Ubitx calibration help

Gordon Gibby <ggibby@...>
 

​Ah!   From your QRZ page you have an ICOM 718 exactly like me.   


One additional question:  are you able to make small changes in the code of the firmware that you've downloaded? like minor edits?


And which VERSION of firmware are you using?


Cheers,


gordon



From: BITX20@groups.io <BITX20@groups.io> on behalf of Gordon Gibby <ggibby@...>
Sent: Sunday, January 7, 2018 10:52 PM
To: BITX20@groups.io
Subject: Re: [BITX20] Ubitx calibration help
 

​Can you give a little more information?


How far off?  Exactly how did you measure?  


What did you do (give the details) when you tried "calibrating"??


Do you have accesss to an accurate existing receiver with a digital readout?


Cheers,


gordon



From: BITX20@groups.io <BITX20@groups.io> on behalf of Art Olson <olson339@...>
Sent: Sunday, January 7, 2018 10:01 PM
To: BITX20@groups.io
Subject: [BITX20] Ubitx calibration help
 
Need some advice on how to calibrate my ubitx. I have read the instructions.  After several tries no success. Reloaded the firmware but freq is still off. Is there a better way to calibrate 

Art- N2AJO 


Re: Ubitx calibration help

Gordon Gibby <ggibby@...>
 

​Can you give a little more information?


How far off?  Exactly how did you measure?  


What did you do (give the details) when you tried "calibrating"??


Do you have accesss to an accurate existing receiver with a digital readout?


Cheers,


gordon



From: BITX20@groups.io <BITX20@groups.io> on behalf of Art Olson <olson339@...>
Sent: Sunday, January 7, 2018 10:01 PM
To: BITX20@groups.io
Subject: [BITX20] Ubitx calibration help
 
Need some advice on how to calibrate my ubitx. I have read the instructions.  After several tries no success. Reloaded the firmware but freq is still off. Is there a better way to calibrate 

Art- N2AJO 


Re: Tuning reversed issue

W2CTX
 

Jack you are right.

I was thinking of this ubitx software center git.

Ron



From: Jack Purdum via Groups.Io <jjpurdum@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 10:20 PM
Subject: Re: [BITX20] Tuning reversed issue

Sounds like more work to me. There's nothing sacrosanct about the two analog pins. As far as changing sketches, whose sketches? If you write your own, it really doesn't matter. If you use someone else's, make a few typing changes and you're done. If you change the wires and then replace the board, then what? Quite often it is easier to make a software change than a hardware change.

Jack, W8TEE



From: John McFadden <johnamcf@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 10:15 PM
Subject: Re: [BITX20] Tuning reversed issue

Even easier is using a small object (thumb tack, tiny drill bit, etc) to unhook the black and brown wires from the header and reverse their positions. Then you can change sketches without worry in the future.
John

On 1/7/2018 4:22 PM, Jack Purdum via Groups.Io wrote:
One of the beautiful things in C are symbolic constants. These are textual strings that get substituted by the compiler. Around line 75 in ubitx_20.ino you will find  these two symbolic constants:

#define ENC_A (A0)
#define ENC_B (A1)

these define encoder tab A and B to be assigned to Nano pins A0 and A1. Now reverse these to:

#define ENC_A (A1)            // NOTE: these are reversed from the original code
#define ENC_B (A0)

and everywhere those symbolic constants (END_A and ENC_B) are used have now been reversed. Save, recompile, and upload and you're done.

                                                                                  OR

you can open your µBITX, unsolder pins A1 and A0, reverse those two connections, resolder the two leads, and put everything back in it's case. To me, the software change is easier and the change presented here doesn't mess with the function code.

Jack, W8TEE



From: Ronald Pfeiffer via Groups.Io <w2ctx@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 4:09 PM
Subject: [BITX20] Tuning reversed issue

Working with Jim, W0EB, I found that if the black and brown wires
are reversed on the encoder then the frequency tuning is backwards.
Some people, including myself, just changed the "doTuning" routine
to reverse the offsets.  This however fixes the frequency tuning but
the menus options seem to be backwards.

Better fix is to change the enc_read(void) routine and then both the
freq tuning and menus selections are in sync.

Please correct me if I am wrong.

Ron








Re: Tuning reversed issue

Jack, W8TEE
 

Sounds like more work to me. There's nothing sacrosanct about the two analog pins. As far as changing sketches, whose sketches? If you write your own, it really doesn't matter. If you use someone else's, make a few typing changes and you're done. If you change the wires and then replace the board, then what? Quite often it is easier to make a software change than a hardware change.

Jack, W8TEE



From: John McFadden <johnamcf@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 10:15 PM
Subject: Re: [BITX20] Tuning reversed issue

Even easier is using a small object (thumb tack, tiny drill bit, etc) to unhook the black and brown wires from the header and reverse their positions. Then you can change sketches without worry in the future.
John

On 1/7/2018 4:22 PM, Jack Purdum via Groups.Io wrote:
One of the beautiful things in C are symbolic constants. These are textual strings that get substituted by the compiler. Around line 75 in ubitx_20.ino you will find  these two symbolic constants:

#define ENC_A (A0)
#define ENC_B (A1)

these define encoder tab A and B to be assigned to Nano pins A0 and A1. Now reverse these to:

#define ENC_A (A1)            // NOTE: these are reversed from the original code
#define ENC_B (A0)

and everywhere those symbolic constants (END_A and ENC_B) are used have now been reversed. Save, recompile, and upload and you're done.

                                                                                  OR

you can open your µBITX, unsolder pins A1 and A0, reverse those two connections, resolder the two leads, and put everything back in it's case. To me, the software change is easier and the change presented here doesn't mess with the function code.

Jack, W8TEE



From: Ronald Pfeiffer via Groups.Io <w2ctx@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 4:09 PM
Subject: [BITX20] Tuning reversed issue

Working with Jim, W0EB, I found that if the black and brown wires
are reversed on the encoder then the frequency tuning is backwards.
Some people, including myself, just changed the "doTuning" routine
to reverse the offsets.  This however fixes the frequency tuning but
the menus options seem to be backwards.

Better fix is to change the enc_read(void) routine and then both the
freq tuning and menus selections are in sync.

Please correct me if I am wrong.

Ron






Re: Tuning reversed issue

John McFadden <johnamcf@...>
 

Even easier is using a small object (thumb tack, tiny drill bit, etc) to unhook the black and brown wires from the header and reverse their positions. Then you can change sketches without worry in the future.

John


On 1/7/2018 4:22 PM, Jack Purdum via Groups.Io wrote:
One of the beautiful things in C are symbolic constants. These are textual strings that get substituted by the compiler. Around line 75 in ubitx_20.ino you will find  these two symbolic constants:

#define ENC_A (A0)
#define ENC_B (A1)

these define encoder tab A and B to be assigned to Nano pins A0 and A1. Now reverse these to:

#define ENC_A (A1)            // NOTE: these are reversed from the original code
#define ENC_B (A0)

and everywhere those symbolic constants (END_A and ENC_B) are used have now been reversed. Save, recompile, and upload and you're done.

                                                                                  OR

you can open your µBITX, unsolder pins A1 and A0, reverse those two connections, resolder the two leads, and put everything back in it's case. To me, the software change is easier and the change presented here doesn't mess with the function code.

Jack, W8TEE



From: Ronald Pfeiffer via Groups.Io <w2ctx@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 4:09 PM
Subject: [BITX20] Tuning reversed issue

Working with Jim, W0EB, I found that if the black and brown wires
are reversed on the encoder then the frequency tuning is backwards.
Some people, including myself, just changed the "doTuning" routine
to reverse the offsets.  This however fixes the frequency tuning but
the menus options seem to be backwards.

Better fix is to change the enc_read(void) routine and then both the
freq tuning and menus selections are in sync.

Please correct me if I am wrong.

Ron




Re: Tuner Kit Progress

Kelly Jack
 

Hi Bill,

Great project. Very interested in this as a remote tuner. 

One query - why are the last two 5.2uH and 10.6uH as opposed to continuing to double up? Not a criticism just seeking to understand.

Regards

Simon VK3ELH 


Ubitx calibration help

Art Olson
 

Need some advice on how to calibrate my ubitx. I have read the instructions.  After several tries no success. Reloaded the firmware but freq is still off. Is there a better way to calibrate 

Art- N2AJO 


Re: "More than one XXX library found" error message

Dale Brooks KG7SSB <kg7ssb@...>
 

Thanks for the information Jack I really appreciate your help....Dale

On Sun, Jan 7, 2018 at 2:44 PM, Jack Purdum via Groups.Io <jjpurdum@...> wrote:
The "more than one LCD library found" is because there are multiple libraries named "LiquidCrystal" out there and your directory might have several installed.

The solution:

1) Find where your IDE is installed. Mine is installed on E:\Arduino1.8.5. Yours will likely be on the C drive, perhaps in the Programs directory. It all depends on where/how you installed it.

2) Inside your IDE directory will be a subdirectory named libraries. Inside that subdirectory should only ONE LiquidCrystal library, so on my system I see something
    like this:

    E:\Arduino1.8.5\libraries\LiquidCrystal           // You will likely see a bunch of libraries before and after this one...

    If you see mutliple libraries, you need to delete one of them. But, which one?

In my BITX code, I use a TFT display, so instead of the LiquidCrystal library, I use:

    #include <MCUFRIEND_kbv.h>    // https://github.com/prenticedavid/MCUFRIEND_kbv

Anytime I use a library that is not included in the standard IDE installation, I have a comment that tells you were to go to download that library (yellow above). I'm not sure which software you are trying to install, but look at the line that includes the LiquidCrystal library (e.g., #include <LiquidCrystal>) and see if the programmer left you a URL for the library. Rename the original LiquidCrystal library directory (e.g., OriginalLiquidCrystal) before you install the new library just in case you need to go back to the original setup if it doesn't work.

Jack, W8TEE



From: Dale Brooks KG7SSB <kg7ssb@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 4:14 PM
Subject: Re: [BITX20] worried now

This one is for Jack Purdum about the software loading. First I want to thank Jack for his wonderful contribution to our group. My problem is this. when I perform the compile on a known working program I get all these error messages such as: more than one LCD library found, unable to to download and a list of attempts to download. I have your book and sorry to say I haven't had much chance to really dig in and try to learn from it but I don't see anything that assists in troubleshooting the error codes and making the necessary changes to correct them. Jack can you or any one else assist me in finding information on how to troubleshoot and repair the compiler errors so I can reliable load my programs. Thanks in advance for the assistance. Dale kg7ssb

On Sun, Jan 7, 2018 at 12:23 PM, Jack Purdum via Groups.Io <jjpurdum@...> wrote:
Close to that easy. It boils down to downloading the free Arduino IDE, loading in the source code files, compiling and uploading the code to the Raduino. Most of this process has been described elsewhere and is the subject of the second half of Chapter 1 of my programming book (Beginning C for Arduino). I have attached the draft copy of that chapter from the 1st Edition of the book.

Jack, W8TEE



From: Paul Smith <paulsmi55@...>
To: BITX20@groups.io
Sent: Sunday, January 7, 2018 1:30 PM
Subject: Re: [BITX20] worried now

Like most I have few concerns about the radio being 'perfect' in every sense and I can fudge my way around circuit mods without too much hassle and enjoy it at the same time. That's what this hobby is all about.  While I knew from the outset that a software upgrade was necessary I am wondering how easy it will be for me (a total code dummy) to upload new sketches. There are likely already guidelines posted somewhere that I haven't come across. Is it as easy as plugging in a USB cable and a few commands on my PC ?

Paul ZS2OE







Tuner Kit Progress

K9HZ <bill@...>
 

So for all the folks that sent me emails about the cheap auto tuner kit... i made some progress this week.  The cores came in and i would a staggered set that total 20 uh.  All checked out and tested.  Very simple to wind. I decided not to use chip capacitors.  They are expensive in the size needed to carry the current needed at large values. Silver mica capacitors are cheaper and easier for most people (like me with marginal eyes) to solder to boards.  Plus the space savings is almost nil. I also found some cheap latching relays so the current draw stays low and the price of the kit stays in the sweet spot.  This week ill design the discriminator (phase and magnitude) for power reading and tuning.   More next weekend. 

image1.jpeg


Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ

 

Owner - Operator

Big Signal Ranch – K9ZC

Staunton, Illinois

 

Owner – Operator

Villa Grand Piton - J68HZ

Soufriere, St. Lucia W.I.

Rent it: www.VillaGrandPiton.com


email:  bill@...

 


Re: BITX QSO Night, Sunday, January 7, 7pm Local Time, 7277 kHz in North America, 7177 kHz elsewhere

Arvo W0VRA
 

I watched the band go dead after it got dark here.


Re: Ubitx case #ubitx

M Garza <mgarza896@...>
 

The cases you see are for the bitx40.  They will have a ubitx case, shortly.  It has not been released for sale, yet.  It is supposed to be released sometime his month.

Marco - KG5PRT 

On Jan 7, 2018 8:13 PM, "Richard Lawn" <rjlawn@...> wrote:
I’m considering ordering this great looking all band semi kit. I’ve built s number of kits of varying levels of difficulty. I noticed that there are some cases for sale on eBay but it’s unclear if these are compatible with he ubitx. Anyone know?
73
Rick, W2JAZ 


Ubitx case #ubitx

Richard Lawn <rjlawn@...>
 

I’m considering ordering this great looking all band semi kit. I’ve built s number of kits of varying levels of difficulty. I noticed that there are some cases for sale on eBay but it’s unclear if these are compatible with he ubitx. Anyone know?
73
Rick, W2JAZ 


Re: Tuning reversed issue

Jim Sheldon
 

After Ron helped me get over the "stupids" and I finally learned how to properly compile & upload stuff to the Raduino, I now have Ron's mods running and he's fixed a lot of little annoying things (annoying to me anyway).  In between bricking & fixing the rig (all firmware, no hardware) I managed to make a couple of real nice 20 meter SSB QSO's and also a couple of 40 meter CW QSO's as well with it.

I heard a lot of RTTY (contest this weekend) and sure wish there were at least 5 more digital pins on the Nano.  Then it would really easy to implement a good CW Keyer and even implement true FSK for RTTY.  You'd still need a computer with sound card running something like Mako Mori's (JE1HHT) MMTTY program, but that would really work well.  Hardware FSK would be much cleaner to implement than tones into the SSB section.  As wide as the filter is, I'd be wary of the 2nd and maybe even 3rd harmonics of the tones being transmitted at the same time as the fundamentals.  That would really create havoc on the bands especially during a RTTY contest, not to mention incur the wrath of the FCC as well.

Jim - W0EB

This little rig just keeps getting better and quite rapidly too!