¿ªÔÆÌåÓý

  1. BITX20
  2. Messages
Expanded Topics Messages Polls
Date
Re: WIKI Pages

 

¿ªÔÆÌåÓý

So, is this the link on the WIKI that we want to point to Farhan¡¯s original code?

? ??

?

Mike K5ESS

?

From: [email protected] [mailto:[email protected]] On Behalf Of K5ESS
Sent: Tuesday, March 21, 2017 10:22 PM
To: [email protected]
Subject: [BITX20] WIKI Pages

?

On the WIKI under the main page topic of "Raduino Topics" I've added the following pages:

Installing the Arduino IDE

Installing the Arduino Libraries

Retrieving the Raduino Code

Retrieving the Si5351A Library

?

Would like input on the content of these pages.

Thanks,

Mike

K5ESS

?
Re: PA voltage and RF output

William Kimber
 

¿ªÔÆÌåÓý

He never said he? did.? Power is voltage x current.? Are you assuming 1 Amp?

If it is 1.25 amp then not 96%.

Cheers,

Will


On 03/22/2017 04:01 PM, Dr Fred Hambrecht wrote:

How did he get 96% efficiency?

?

?

From: [email protected] [mailto:[email protected]] On Behalf Of Sasi Nayar
Sent: Tuesday, March 21, 2017 8:49 PM
To: [email protected]
Subject: Re: [BITX20] PA voltage and RF output

?

Thanks John.?Usful to know you are getting around 24W RF output for 25V into the final. I am trying to ascertain the increment in RF power with an increase in Voltage in to the PA stage (someone has documented this somewhere but I just connot recollect where).??The objective here is to set the step-up voltage module for an RF output of around 20W without pushing it too far. I was planning on beefing up the heat sink and adding a little fan

73

Sasi

VK5SN
Re: WIKI Pages

Jack Purdum
 

I'll try to add some of my files tomorrow.

Jack, W8TEE


From: College Professor Simon Thompson <nwccenglishprofessor@...>
To: [email protected]
Sent: Tuesday, March 21, 2017 11:33 PM
Subject: Re: [BITX20] WIKI Pages

Provide a link to the page you are talking about...
On Mar 21, 2017, at 8:22 PM, K5ESS <k5ess.nothdurft@...> wrote:

On the WIKI under the main page topic of "Raduino Topics" I've added the following pages:
Installing the Arduino IDE
Installing the Arduino Libraries
Retrieving the Raduino Code
Retrieving the Si5351A Library

Would like input on the content of these pages.
Thanks,
Mike
K5ESS
Re: Master file for Bitx40 Opinion by W8LM

Jack Purdum
 

I think this is workable. See comments below:

Jack, W8TEE

From: Jerry Gaffke via Groups.Io <jgaffke@...>
To: [email protected]
Sent: Tuesday, March 21, 2017 10:52 PM
Subject: Re: [BITX20] Master file for Bitx40 Opinion by W8LM

> ?Farhan should have absolute control over the "official" Raduino code.
Should. ?But he seems to have other stuff on his plate. ?I don't think managing Raduino code is his thing. ?As I recall, he was previously asking somebody with a fix to just go ahead an push it up into github. ?Perhaps we need somebody else here to take over that job. ?(Hi Jack!) This probably isn't necessary given the way you've suggested we do this. If people follow the process Jerry described here, it should work without guidance. (Of course, since I love this kind of stuff, so I'll probably be watching things pretty closely anyway.)
?
> ? ?RaduinoSource-Ver02.ino
> ? ? ? ?/* This file adds to the Ver01 file by W8TEE by W6DQ, April 10, 2017. The major changes are: CW/SSB switch, keyer, and?
> ? ? ? ? ? ?AGC. */
> ? ? ? ?/* This file is based on the original Raduino source code with additions by W8TEE--March 21, 2017. The major changes?
> ? ? ? ? ? ?include: TFT display, Fast Tune, etc.
> ? ? ? ?*/?

> ?I'm sure others have ideas on the mechanics of how we should do this.

Yup. ?I suggest code get placed in the files section under your call.?This?is a good idea, since it has a lineage of who is doing what. The problem comes when someone finds a code in my file. At that point, what should be done is the person who finds the bug notifies me about the bug, I fix it, change the Version number with a comment in the source file describing the bug and how it was fixed using style similar to what Jerry describes below. If we can do that, this will work.? Give the file an arbitrary name, perhaps W8TEE/FixDualVfo00.ino
Note the final 00 there, that's the revision number. ?If Jack sees the inevitable bug, he creates a new file ?FixDualVfo01.ino, but leaves the rev 00 file as it was since somebody may have started with FixDualVfo00.ino when creating their code.?This process?is important: Leave the original 00 file UNCHANGED. Make the changes to a copy of the original file, but increase the Version number. It's important to be able to go back to the state of the file prior to the bug fix.?Give the entire path name for the new file at the start of your comment that describes the file. ? ?If it's just a single file, then make it the ino file. ?If it's multiple files, give the directory name. ?So, to badly hack Jack's example:

// Files/KE7ER/FlutterFix00: ?March 21, 2017 ??Added code to reduce noise from tuning pot. ?

// Files/W8TEE/FixDualVfo00: ?Jan 31, 2017 ? ?Fixed Ashhar's original code to use function switch to select VFO A or B ?

// ?? ??Ashhar's original Raduino code as posted to github

I've never messed with git (but should). ?That final line should include some way of getting the correct version. ?If what you have to say needs more than one line, then indent lines or perhaps add a blank line. ?Use any valid comment scheme you are comfortable with.

I fully agree with Jack's suggestion that any library used should have a comment right there in the source code telling you where to find the library. ?And tell us the ?revision number of the library you used.?

> ?A small TXT file should be uploaded with the new file that explains what features/mods are in the file.?
The only reason I made this suggestion was in case multiple people wanted to know what's changed in the file without actually loading the file. (I'm assuming the TXT file would be shorter.) I can live without this.
Assuming most of these will be a single *.ino file, I'd tend to make that a comment at the top of the source code, just below the revision control stuff. ?If your code is multiple files, then make it a subdirectory under your call in the files section.

Jerry, KE7ER?


On Tue, Mar 21, 2017 at 08:21 am, Jack Purdum wrote:
All:

I personally think Farhan should have absolute control over the "official" Raduino code. This could be placed somewhere (github?) where only he can alter the source code. Others can download it, but no uploads would be allowed other than by Farhan.?

Others who add features or otherwise modify the "official" code need to place their call somewhere in the modified file (e.g., RaduinoSourceW8TEE.ino) and then upload it to the Files section of the group web site. A small TXT file should be uploaded with the new file that explains what features/mods are in the file. A brief summary of those changes could also be in a comment within the file itself. I would further suggest that we adopt the convention of placing the download site (URL) for any required libraries that are not part of the standard Arduino IDE as part of the #include statement:

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

This would help avoid the problems associated with libraries that are not part of the IDE. It then becomes the responsibility of the user to locate those additional libraries and install them properly in the IDE. I have made a few posts on how new libraries should be installed. I have also uploaded a file that tells how to download, install, and test the IDE.

Now, the complications that I envision. Someone likes some of the features in a new file (e.g., RaduinoSourceW8TEE.ino) but then wants to add their own feature set to that file. How do we show the lineage of the code? One way is to append the current person's call to the base file being modified (e.g., RaduinoSourceW8TEE-W6DQ.ino). That will quickly get out of hand and make for unwieldy file names. Instead, how about adding a new comment line at the top of the source file that can be added to, and change the Version number in the file name:

? ? RaduinoSource-Ver01.ino
? ? ? ? /* This file is based on the original Raduino source code with additions by W8TEE--March 21, 2017. The major changes?
? ? ? ? ? ? include: TFT display, Fast Tune, etc.
? ? ? ? */?

Now Dennis comes along and modifies that file:

? ? RaduinoSource-Ver02.ino
? ? ? ? /* This file adds to the Ver01 file by W8TEE by W6DQ, April 10, 2017. The major changes are: CW/SSB switch, keyer, and?
? ? ? ? ? ? AGC. */
? ? ? ? /* This file is based on the original Raduino source code with additions by W8TEE--March 21, 2017. The major changes?
? ? ? ? ? ? include: TFT display, Fast Tune, etc.
? ? ? ? */?

This makes it easy to see the lineage of the source file without extending the name. If we preserve each source file (e.g., Ver01 even if a later version exists), it would allow anyone to "backup" to an earlier version if they wish. This would also make it possible to run a file compare program to see exactly what the differences are between two files.

I'm sure others have ideas on the mechanics of how we should do this. Right now, I think the important thing is that we agree there needs to be some simple form of source code control.

Jack, W8TEE
?
Re: WIKI Pages

College Professor Simon Thompson
 

¿ªÔÆÌåÓý

Provide a link to the page you are talking about...

On Mar 21, 2017, at 8:22 PM, K5ESS <k5ess.nothdurft@...> wrote:

On the WIKI under the main page topic of "Raduino Topics" I've added the following pages:

Installing the Arduino IDE

Installing the Arduino Libraries

Retrieving the Raduino Code

Retrieving the Si5351A Library


Would like input on the content of these pages.

Thanks,

Mike

K5ESS
WIKI Pages

 

On the WIKI under the main page topic of "Raduino Topics" I've added the following pages:

Installing the Arduino IDE

Installing the Arduino Libraries

Retrieving the Raduino Code

Retrieving the Si5351A Library


Would like input on the content of these pages.

Thanks,

Mike

K5ESS
Re: PA voltage and RF output

 

¿ªÔÆÌåÓý

How did he get 96% efficiency?

?

?

From: [email protected] [mailto:[email protected]] On Behalf Of Sasi Nayar
Sent: Tuesday, March 21, 2017 8:49 PM
To: [email protected]
Subject: Re: [BITX20] PA voltage and RF output

?

Thanks John.?Usful to know you are getting around 24W RF output for 25V into the final. I am trying to ascertain the increment in RF power with an increase in Voltage in to the PA stage (someone has documented this somewhere but I just connot recollect where).??The objective here is to set the step-up voltage module for an RF output of around 20W without pushing it too far. I was planning on beefing up the heat sink and adding a little fan

73

Sasi

VK5SN
Re: Master file for Bitx40 Opinion by W8LM

 

I started a WIKI page for "Retrieving the Raduino Code"? so now I need to know the link to Farhan's code that is under his control.?

Mike

K5ESS
Re: Master file for Bitx40 Opinion by W8LM

 

> ?Farhan should have absolute control over the "official" Raduino code.

Should. ?But he seems to have other stuff on his plate. ?I don't think managing Raduino code is his thing. ?As I recall, he was previously asking somebody with a fix to just go ahead an push it up into github. ?Perhaps we need somebody else here to take over that job. ?(Hi Jack!)

?

> ? ?RaduinoSource-Ver02.ino
> ? ? ? ?/* This file adds to the Ver01 file by W8TEE by W6DQ, April 10, 2017. The major changes are: CW/SSB switch, keyer, and?
> ? ? ? ? ? ?AGC. */
> ? ? ? ?/* This file is based on the original Raduino source code with additions by W8TEE--March 21, 2017. The major changes?
> ? ? ? ? ? ?include: TFT display, Fast Tune, etc.
> ? ? ? ?*/?

> ?I'm sure others have ideas on the mechanics of how we should do this.

Yup. ?I suggest code get placed in the files section under your call. ?Give the file an arbitrary name, perhaps W8TEE/FixDualVfo00.ino
Note the final 00 there, that's the revision number. ?If Jack sees the inevitable bug, he creates a new file ?FixDualVfo01.ino, but leaves the rev 00 file as it was since somebody may have started with FixDualVfo00.ino when creating their code. ?Give the entire path name for the new file at the start of your comment that describes the file. ? ?If it's just a single file, then make it the ino file. ?If it's multiple files, give the directory name. ?So, to badly hack Jack's example:

// Files/KE7ER/FlutterFix00: ?March 21, 2017 ??Added code to reduce noise from tuning pot. ?

// Files/W8TEE/FixDualVfo00: ?Jan 31, 2017 ? ?Fixed Ashhar's original code to use function switch to select VFO A or B ?

// ?? ??Ashhar's original Raduino code as posted to github

I've never messed with git (but should). ?That final line should include some way of getting the correct version. ?If what you have to say needs more than one line, then indent lines or perhaps add a blank line. ?Use any valid comment scheme you are comfortable with.

I fully agree with Jack's suggestion that any library used should have a comment right there in the source code telling you where to find the library. ?And tell us the ?revision number of the library you used.?

> ?A small TXT file should be uploaded with the new file that explains what features/mods are in the file.?

Assuming most of these will be a single *.ino file, I'd tend to make that a comment at the top of the source code, just below the revision control stuff. ?If your code is multiple files, then make it a subdirectory under your call in the files section.

Jerry, KE7ER?


On Tue, Mar 21, 2017 at 08:21 am, Jack Purdum wrote:

All:

I personally think Farhan should have absolute control over the "official" Raduino code. This could be placed somewhere (github?) where only he can alter the source code. Others can download it, but no uploads would be allowed other than by Farhan.?

Others who add features or otherwise modify the "official" code need to place their call somewhere in the modified file (e.g., RaduinoSourceW8TEE.ino) and then upload it to the Files section of the group web site. A small TXT file should be uploaded with the new file that explains what features/mods are in the file. A brief summary of those changes could also be in a comment within the file itself. I would further suggest that we adopt the convention of placing the download site (URL) for any required libraries that are not part of the standard Arduino IDE as part of the #include statement:

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

This would help avoid the problems associated with libraries that are not part of the IDE. It then becomes the responsibility of the user to locate those additional libraries and install them properly in the IDE. I have made a few posts on how new libraries should be installed. I have also uploaded a file that tells how to download, install, and test the IDE.

Now, the complications that I envision. Someone likes some of the features in a new file (e.g., RaduinoSourceW8TEE.ino) but then wants to add their own feature set to that file. How do we show the lineage of the code? One way is to append the current person's call to the base file being modified (e.g., RaduinoSourceW8TEE-W6DQ.ino). That will quickly get out of hand and make for unwieldy file names. Instead, how about adding a new comment line at the top of the source file that can be added to, and change the Version number in the file name:

? ? RaduinoSource-Ver01.ino
? ? ? ? /* This file is based on the original Raduino source code with additions by W8TEE--March 21, 2017. The major changes?
? ? ? ? ? ? include: TFT display, Fast Tune, etc.
? ? ? ? */?

Now Dennis comes along and modifies that file:

? ? RaduinoSource-Ver02.ino
? ? ? ? /* This file adds to the Ver01 file by W8TEE by W6DQ, April 10, 2017. The major changes are: CW/SSB switch, keyer, and?
? ? ? ? ? ? AGC. */
? ? ? ? /* This file is based on the original Raduino source code with additions by W8TEE--March 21, 2017. The major changes?
? ? ? ? ? ? include: TFT display, Fast Tune, etc.
? ? ? ? */?

This makes it easy to see the lineage of the source file without extending the name. If we preserve each source file (e.g., Ver01 even if a later version exists), it would allow anyone to "backup" to an earlier version if they wish. This would also make it possible to run a file compare program to see exactly what the differences are between two files.

I'm sure others have ideas on the mechanics of how we should do this. Right now, I think the important thing is that we agree there needs to be some simple form of source code control.

Jack, W8TEE

?
Re: Order has not yet arrived

 

it will arrive!?

On Mar 21, 2017 6:58 PM, "N7PXY" <hickspj467@...> wrote:

Wow Alan,

It took a while but at least you found it. I and the Tacoma guys plus Wayne are having a blast playing with the BitX40. And learning some Arduino as well. Very glad you found it.


Peter,

There is a very active group of BitX hackers down here in Tacoma. About 6 of us plus Wayne McFee and a few others from the pQRP group are making mods and improvements almost daily. It's really caught on. If you get a chance come on down to the Radio Club of Tacoma on any Saturday from about 09:30 to 2:00 and there is always a bunch of BitX enthusiasts hanging out and talking mods and code. We also have an active email list that keeps everyone up to speed.


PJH, N7PXY
Re: Order has not yet arrived

N7PXY
 

Wow Alan,

It took a while but at least you found it. I and the Tacoma guys plus Wayne are having a blast playing with the BitX40. And learning some Arduino as well. Very glad you found it.


Peter,

There is a very active group of BitX hackers down here in Tacoma. About 6 of us plus Wayne McFee and a few others from the pQRP group are making mods and improvements almost daily. It's really caught on. If you get a chance come on down to the Radio Club of Tacoma on any Saturday from about 09:30 to 2:00 and there is always a bunch of BitX enthusiasts hanging out and talking mods and code. We also have an active email list that keeps everyone up to speed.


PJH, N7PXY
Re: PA voltage and RF output

 

It kinda sounds like you are going to use a boost converter to increase voltage from the 12V input from the main board to power the PA. If that is the case you will have a lot of noise in the audio from both the boost converter and the fan. it's best to keep them separate if you step up, or down voltage and, or use a fan too. Is that what you mean by step-up voltage module?

I think it's better to have 12V 1A for the main board and Raduino. And use a higher voltage supply, (mine it 31V 1.6A) and step it down for the PA, then step down again for the fan. This will keep switching, and induction noise out of the radio audio. Keep the PA current draw at or under 1 amp, and under 25V, you will not push it too far. Adjust R136 for current draw which will also affect RF watts output.
Re: PA voltage and RF output

 

Thanks John.?Usful to know you are getting around 24W RF output for 25V into the final. I am trying to ascertain the increment in RF power with an increase in Voltage in to the PA stage (someone has documented this somewhere but I just connot recollect where).??The objective here is to set the step-up voltage module for an RF output of around 20W without pushing it too far. I was planning on beefing up the heat sink and adding a little fan

73

Sasi

VK5SN
Package on at my Front Door!

 

I ordered the BITX40 on March 2, 2017. I received it today 3/21/2017. SN: N3-554c...maybe its an L?
Re: PA voltage and RF output

 

Amps X Volts = Watts. I supply 25V into final, draw 1 Amp, MFJ-9213 meter indicates 24 watts output with 1khz tone into mic for tuning. This is with a tuned 40M dipole and not a dummy load. Plus a much bigger heatsink and fan powered by buck converter from 25V input stepped down to about 7V for 12V 60MM computer fan without noise, including TX. Using main board 12V induces a lot of noise into audio from switching circuitry in brushless fan. Use final PA power for fans.

Does that help?
low output and beep bitx40

 

Hello,

The rf output is just 1 watt and there is a loud beep, even when i disconnect the mic.

Is there anybody who knows this problem?


Paul Brookhuis? PD2PB
Re: Order has not yet arrived

 

I had my local post office research the shipment and they found it! It seems that it arrived in our town on February 17. So the actual shipping time was about 19 days.

73

Alan K6ZY
Re: Order has not yet arrived

 

PJ,

I've just unboxed my BITX40 and am in Redmond... perhaps we need to have a Puget Sound BITX meetup? ?

Peter, K3OG
Re: Order has not yet arrived

 

Peter,

What is the serial number of your BITX?

Randy, K7AGE


On Tue, Mar 21, 2017 at 10:05 AM, <peter.fahringer@...> wrote:

Randy,

Just left the post office with my BITX40 and came into the office...? The parts are scattered everywhere but the plastic case is intact so hopefully work and family commitments allow me to assemble and test this weekend. ?

You can add my order to your database:

Ordered 2/16/17, shipped 2/28/17, received @ zip 98074 3/21/17 (actually 3/20 but I wasn't home to sign for it).

Peter, K3OG


_._,
Re: Master file for Bitx40 Opinion by W8LM

Michael Davis
 

One member's advice to take your time, evidently is not being heeded by many. The old adage "measure twice, cut once" sure applies here. Read five times solder once, if you are lucky. The potentiometer, for example, is shown in a photo, in place, with the correctly colored wires attached. The other drawing of the tuning pot is depicted from the shaft end, but not obvious. I'm not sure if the "wire it" section has been changed at all recently. The directions lead one to believe that the Bitx can be built using only the first photo/drawing page. Maybe on your second build or with much luck or experience, but not most of us. Many of us remember checking the little block on a Heathkit or Eico kit, as we connected each wire or component, but not soldering until the directions said so. The Bitx requires more reading ahead 5 times, to get the jist of what is next. Then there is the color codes...what color codes?

Sent from Mike's iPad WA1MAD
92421 - 92440 of 116224