Wednesday, February 15, 2017

A Practical Problem ~ How to make your hombrew rig do TUNE?

(A note from Pete -- I can see the number of hits on each post and was somewhat surprised that the secrets of homebrewing got nearly 500 hits and the troubleshooting one just over 150. So that is helpful and very telling --we like to build stuff; but don't like to fix it. That is the last time that troubleshooting will be discussed by me. I know how to do it --do you?)

How to make your Rig do TUNE?

So you asked has Pete been in the house too long because of all the rain in California and now has gone bonkers?  Everyone knows for SSB only rigs (like the stock Bitx40) you simply whistle into the microphone or yell the standard "HOLA"  into the microphone! Others will ask why do you even want to tune your radio? VU2ESE's Bitx40 instructions basically say plug in the microphone and talk it up.
Well having your SSB only rig be able to TUNE has some very practical and necessary applications. The CW ops are smiling now as they think --just hold the key down for about 10 seconds and you are in TUNE.
The "why" is now unveiled. Firstly if you have homebrewed your own rig, then you need to make adjustments so that the performance is optimized such as tuning the Band Pass Filter or setting drive levels to intermediate stages or even adjusting the bias on your IRF510. Of course you would never do this "on air" but into a dummy load. That is a lot of whistling or shouting HOLA. CW ops are still smiling!
Thus rig adjustment for best performance is probably the 1st use and the second after that  is the adjustment of the rig to the antenna. So OK, you have one of those fancy auto tuners and you let the tuner do the hard work. But if you are like me and have no such devices, then you need to be able to provide a tune signal to make the adjustments -- thusly reason #2. Perhaps a third is maintenance --suppose you suspect you are not getting full smoke to the antenna --then you would want to put your rig in TUNE and see what the output looks like.
So how does one generate a TUNE signal. Mind you the TUNE doesn't have to be at full power but just enough to put a couple of watts of RF into a dummy load or into your antenna system. So how is it done?
Method #1. In an SSB only radio if there is a way to unbalance the carrier in the balanced modulator then a simple unbalancing will output the carrier. This seems like an antithesis of its purpose. We work hard in our rigs to make the carrier "go away" --we get nervous when the carrier suppression is only 65 dB down and now we want to undo that. Well many of the old boat anchor radios had a carrier balance control right on the front panel so you could make that adjustment. Now with our packaged Double Balanced Mixer a bit harder to do. The SBL-1 however can be unbalanced --read EMRFD for a way as described by W6JFR (yes me in another life). But you cannot do this in a casual manner --so not for everyone.
Method #2 which offers some bonus features in that you effectively can add CW to your SSB only transceiver. In my KWM-4 I added CW by having a separate CW oscillator tuned to the center frequency of the filter and that signal was fed to a keyed buffer stage. This CW oscillator was only turned on when you hit the key and was held on for a short period of time. The output from the keyed buffer was fed to a relay where it was injected into the 1st  bilateral IF stage bypassing the filter. From there the signal went to the RxTx mixer stage. Sorry CW ops this is not QSK and is like semi-break in with delay. Clunky for the ardent CW op --yes but it would do CW with an offset since on receive  the Rx was set to USB. This same approach could be used for TUNE. Just hold down the key. The real hard part of this was the control and sequencing circuitry. But it did work. I have made one CW contact on the KWM-4 and it worked flawlessly. I had to do the CW contact for proof of concept.
Method #3. Since my primary interest is SSB --- how would you do this? Many early transceivers  used a tone for generating CW and that same tone keyed the VOX which put the rig into transmit. The Collins KWM-2 used this approach as did others. Staring me in the face was the Arduino and I said why can't I let the Arduino do all of the heavy lifting. I researched generating tones with the Arduino and it was possible to do just that. For the earlier IDE's there is a library called "toneAC" that must be in your library section of the Arduino folder. Now the rub --you will have to find a later version of this library to work with the IDE 1.6.0 and above.

So that is step one. Next you will have to include the following in your sketch: #include <toneAC.h>  Now I picked a tone that was close to 1000 Hz and the best I could do was 988 Hertz. That to needs to be in the sketch in this form  #define NOTE_B5 988 Finally you need to designate a tone pin --where will the output be on the Arduino and you will need this statement const int tonepin = 4; //tune up tone  We will also need to start the cycle and thus an input pin --in the set up you must write code for the pinMode and to define a status for the pin so that it is HIGH. We picked pin 12 and called that SW1 which is really a push button.

#include <toneAC.h>
#define NOTE_B5 988
const int tonepin = 4; //tune up tone
const int SW1 =12; // provides the TUNE function
const int LED = (some free pin number); //attach mini relay to parallel PTT contacts

In the setup()

     pinMode(SW1, INPUT); //Tune

So how does generating a tone work and how does this cause a TUNE signal? Essentially the sequence is to momentarily hit a panel mounted Push Button which we call SW1. There is a call function in the loop that constantly looks to see if the push button has been pushed which would be a signal that Pin 12 is LOW. From there the call function starts and the main loop is on hold. In the most current use I have pretty much used up all of the Arduino pins so had to come up with a bit of a work around.

When I first used this approach I was not constrained for pins and here is the sequence of what happened. The PB is engaged and the loop takes over and recognizes the button was pushed and immediately moves to the call function. Another free pin was designated as a Push To Talk pin and so upon initiation would go HIGH to which a 5 VDC mini relay was connected whose contacts were in parallel with then normal PTT contacts --the rig would now be placed into transmit. Next a message would appear on the screen, that the rig was in TUNE. Finally the tone was generated at 988 Hz, But there was a loop counter inside the loop that would turn the 988 Hz tone on and off for a specific number of cycles and thus a pulsed tone. That was the "if" part of the call function. The else part is where the word Tune is once again painted on the face of the display only it is the color of the background and thus "disappears". The pin driving the 5 VDC mini relay goes low and the PTT un-keys and the receiver comes to life. The pulsed tone is better than a constant tone as it is easier on the finals and is helpful during a antenna tune where the SWR is high. Below is an example of the rig in the TUNE mode. Pretty cool?

In one of my current projects I was short of pins so I just paralleled a panel mounted switch that is in parallel with the PTT. After engaging the (MOX) switch the rig is in transmit and I simply press the momentary PB and we are in tune. The "MOX" switch on the panel is nice if your are testing microphones so you don't have to hold down the PTT.

But wait you are NOT done. That beautiful 988 Hz tone is a SQUARE wave and perhaps a bit hard on some of the circuitry downstream. On the internet I found a square wave to sine wave RC network that uses three 1.5K resistors and three 10 NF caps. --almost like a phase shift network --well it does knock of the corners but is no pure sine wave.

Here is the call function code: //For Check Mode --ie TUNE If you have added the 5 VDC relay to one of the pins you need to add digitalWrite(LED, HIGH) in the "if" part and digitalWrite(LED,LOW) in the "else" part. I simply called the PTT pin LED and you will also have to declare the LED pin number and the initial setup() add  pinMode(LED, OUTPUT); and initial state digitalWrite(LED, LOW);

     void CheckMode(){
      buttonState = digitalRead(SW1); // creates a 10 second tuning pulse train50% duty cycle       makes TUNE appear on the screen
       if(buttonState != lastButtonState){
       if(buttonState == LOW){
     tft.setTextColor(WHITE); // This puts a white TUNE on a black background
     tft.setCursor(126, 110); 
     for(int i = 0; i < 100; i++) {
     tone(4, NOTE_B5);
         tft.setTextSize(2);    // This prints a black TUNE over the white TUNE and makes it disappear  from the screen
         tft.setCursor(126, 110);
Pete N6QW.

This is a useful tool but does require some noodling.


Thursday, February 9, 2017

The Art of Troubleshooting!

Three Easy Steps To Troubleshooting!

2/10/2017 ~ See the PS Note at the end.

What, are you kidding? There simply are no three easy steps. So get over it! That indeed is the heart of the problem --we all want to slide into home, take the easy way out, do the minimum work, send out 100 emails in hopes of having someone else resolve your problem. It just doesn't work that way! I repeat there are no three easy steps! No fellow hams, this is not Fake News!
That said there is however a process for troubleshooting a project and that is what I will share with you. A long time ago I came up with my process after observing how heathkit was successful in the kit market until they became a dinosaur and were overrun by the black boxes from the land of the rising sun. Heathkit's success was build and test a portion of the circuit before moving on to the next element. In effect the portions completed actually became a part of the test system as you added new elements. How simple!
I like to scratch build my radios and avoid the many kits that are currently on the market. Here is the rub --current kits --you get a board and bag of parts. Some suggest installing all the resistors first and then the capacitors. Or the reverse, caps first. Next install the devices, hook up the wires and give it the smoke test --often it not only smokes; but catches fire too!

So now you have this semi-burnt mess or if it hasn't burned it plain don't work! How in the world do you methodically go about isolating the problem areas? There was/is no testing of what you built as you progress through the bags of parts. One notable exception was the 'softrock" kits from KB9YIG. This was the heathkit model. See the video below --where do you start troubleshooting this jewel?????

So here is my process:
 Turning on the soldering iron is weeks if not months away. The first steps are to get smart about your project. I call this noodling! Do your homework and research the hell out of it. Be wary of the "Internet Boasts". There is no way you can run an IRF510 with 12 volts on it and from a single device have a 500 Watt PEP linear stage. Ain't gonna happen!

Collect data on similar projects and set up a system that is easy to use so when you need the data it can be readily found. Think in terms of circuit chunks such as an audio amplifier block, a microphone amplifier block, a product detector/balanced modulator block, an IF block, a Mixer stage block, a receiver and transmitter RF amp stage, Band Pass and Low Pass filter blocks. Most of my transceivers are just that, a collection of blocks. An article I wrote for QRP Quarterly on a SSB transceiver was entitled JABOM (Just A Bunch Of Modules).

Using the modular approach serves the purpose of ease of trouble shooting as well as providing a pathway for circuit improvements. Want a Digi VFO instead of that drifty analog VFO --pull the analog module and install the Digi VFO? Want a better audio amp --Boom same drill! The module approach serves another purpose --simply flexibility in how to cram, stuff, and/or shoehorn  the boards into that neat metal tin that formerly housed cookies.

I often make card board cutouts that are the same size as my module boards and using these cutouts can move them around the enclosure to determine a best fit --all the while mindful of minimizing circuit interaction and unwanted coupling of signals. I can't think of one of my projects that is just a single circuit board. I have over 100 you tube videos of my projects and you can confirm this for yourself

Backing up from the troubleshooting side is the decision you made early on to homebrew something and with that brings the other side in having suitable test equipment. Don't begin a homebrew effort if you have no means to verify if it is working. Bill, N2CQR has a monthly podcast where I just ride along and have lots of fun talking about radios. Almost two years ago we started an effort to encourage homebrewing a simple 7 part 80M CW transmitter, known as the Michigan Might Mite. We even supplied 3.579 MHz crystals (mostly Bill) for the project. That seemed to be a hit with the listeners.

One ham who competed his MMM emailed Bill and asked how to know if it was working --as all he had was a crystal set and couldn't hear any CW notes. Yes a crystal set --no meters, no O' Scope not even a receiver that could tune to 80 Meters. This clearly illustrates the issue --what a downer to have built the MMM and not know it was working.

Another ham put a Bitx20 on the air and while he could readily hear other stations --no contacts. He asked how would he know if his rig was working as he had no other receiver in his shack so he could listen for a signal. Bill suggested he look at his SWR meter and see if the meter moved in concert with the voice peaks (about 1/2 scale from tune). Yes, No SWR Meter in line and simply didn't have one. So acquiring some test equipment is very much in order if you want to homebrew your own rig and is mandatory when you have to troubleshoot same.

There are about 6 or 7 pieces that I would put on the list including an SWR meter [Note one of the reasons for low output or oscillating finals is too high an SWR but you would never know unless you knew how was the antenna (load).] Next would be a DVM (Digital Voltmeter) such as the ExTech series from Jameco Electronics and a frequency generator/counter such as the Feel Tech which can be had for around $50 on eBay. An LC meter (Marlin P Jones is selling one for about $40). To that I would add a DSO (Digital Storage Oscilloscope) such as Bill has the 100 MHz, Rigol about $400. For the ham with the Bitx20 who didn't know if it worked -- if he had  DVM, he could have built an RF probe (three parts) where he could see if there was an RF voltage when the rig is fed into a 50 Ohm dummy load which is another item to the list. Dummy loads are easily homebrewed! Take twenty 1K 1/2 watt resistors in parallel --Boom 10 watt, 50 Ohm resistive load which is good for QRP levels.

OK come up for air and swallow hard -- that comes to around $700. The biggest item is the DSO but the others can be acquired over a few months of time and are far better than just a crystal set. Should not forget about finding an all band inexpensive shortwave radio (Sanjean) and that would give you a radio where you could at least find your signal.

To that I would add an isolated low wattage soldering iron-- that Radio Shack 80 watt iron helps heat the shack but not good on surface mount soldering or repair. While we are at it, throw out all of those $1.95 12VDC WalWarts --they are noisy and will make it seem like your project is not working! Get yourself or build a 12VDC, 2 Amp Linear power supply (one with a real transformer). Hand tools are still more items to the list. Trash those crappy Harbor Freight screwdrivers and pliers. I could go on an on -- but why try to do brain surgery with nothing more than a rusty spoon is the message.

This is a really good example of what I preach I should practice as earlier today I was testing the new board and Boom the radio went dead. Jostling the board made it come back to life! That could only be an intermittent connection --where was my quality control? See the yellow wire --well when I built this radio almost four years ago I thought I had properly soldered the wire to the pad. But instead the wire was just resting on the pad, caught under the resistor so it was making contact. By my handling the board that wire came loose and thus the intermittent nature based on the flexing of the board. I have several pairs of tweezers -- after cooling I should have "tugged on" each wire to assure there was a good mechanical connection --had I done that --the problem would have been found 4 years ago. Good lesson for me and good lesson for you


The build philosophy is the next part of my process. Bill, N2CQR and I have talked about this several times. Bill likes to start with what he considers the "tough nut to crack" and since he is partial ( I should say very partial) to analog VFO's --he always starts there. My approach is to start at the back end and build the audio amplifier stage wherein I have a couple of standard designs. [I have committed these designs to circuit boards that are cut on my CNC mill. If I want more "poop" out of the audio I use the NE5534 driving the LM380. A less demanding application would be a 2N3904 driving an LM386-3.]

I know these designs work AND I know how much "poop" they will deliver. So once built I can easily tell if they are working properly! The next element is the Product Detector/ Balanced Modulator. I favor the use of the SBL-1 or TUF-1 DBM for this application. Again I have templates in my CNC files. Once installed I can hook up to the audio amp and being careful to not exceed 1.414 Volts Peak to Peak (7dBM) inject that signal into the LO port --you can tell if it working -- any LO signal (any frequency at this point) will give you that test.

At one time I had a small single transistor test oscillator using a 2N3904 and a socket built from a SIM socket ran various crystals into the LO port. The Feel Tech generator will do the same BUT watch the 7dBM --you'll smoke the DBM otherwise. Now with these two stages working build the IF amp stage (consisting of the IF amps and crystal filter)  and when that is completed hook that up to the product detector.

If you have that single transistor test oscillator use that to supply the BFO signal to the SBL-1 and the Feel Tech can supply the signal into the 1st IF. Caution, Caution, Caution!!!!  Loosely couple into the IF stage and run the signal level way down like may 50 Millivolts. Loose coupling means using a small value capacitor like 10 PF. The signal generator can be used to sweep the filter about the center frequency. If you hooked a voltmeter up to the audio amp output and if you were using a homebrew crystal filter --this is now a test system! By sweeping the filter and noting the audio output readings you can plot the voltage versus the frequency and this will tell you much about your filter!

Do you get the point? What you built becomes part of the test system and when you add a circuit and it does not work --the problem is pretty much confined to what you just added.
    Most problems with a circuit can be traced to some common roots, especially when you are dealing with a proven design and what is replicated simply does not work. These root tracings include: wrong component installed, bad component, improper wiring of the circuit, cold solder joints, wiring not connected (see the photo above). To digress I love receiving emails that start by saying "Your Circuit Doesn't Work!". One chap who generated such an email sent me a photo of the circuit and had marked voltage levels at every location on the module. At one transistor (a 2N3904)  the collector had a "0 Volts" reading which quickly caught my eye. Hmmm 0 volts tells me there is a problem at the collector. Upon close examination of the photo --there was absolutely nothing connected to the collector --it was just sitting there soldered to a pad. Well here is the rub -- the chap had all of the data in front of him --Clue 0 volts, Clue nothing connected, Clue why it doesn't work. I politely responded that he hook up the circuit as designed and then it would work. Never heard back from him. But this illustrates the point of how the taking of simple data can often provide the answer.

    Another similar email/ photo from another ham reflected the need to improve soldering skills --yes it was a cold solder joint. Many of the components are surface mount and that opens the door to solder bridges shorting out pins or worse hot pins to ground. My process therefore before applying power is to reaffirm: right components right place, tracing the wiring to assure correctness and to observe polarities on diodes and electrolytic caps, checking the quality of solder joints especially grounded connections and to look (with a headband magnifier ) for any solder shorts! Needless to say --is the power connected with the proper polarity.

More Troubleshooting Wisdom:

I have a stable of proven horses (circuit modules) so I well know their level of performance. I know what works and how well it works. Some argue I would never try anything new -- no --it is simply I will try a new circuit in an existing well understood design. Then if that new circuit adds to the performance it will now become one of the horses in the stable. A friend is building a project where he is utilizing the Simpleceiver project that was featured on this blog as a part of his project. For the front end RF amp he was using the Dual Gate MOSFET (two J310's in a cascode circuit) developed with the Simpleceiver but he wanted to compact things.

 I suggested the use of a single 2N3904 as an RF amp (have used this over and over). Both provide about the same level of gain BUT the J310's offer a way to apply AGC-- but for his application not needed thus the 2N3904 choice. He reported back the 2N3904 was not as good as the J310's --well 15 dB of gain is 15 dB. So that is a clue that there is something needing further attention with the 2N3904 build (not the design). I further suggested simulating both circuit in LT Spice and if you get the same answer on gain then it is how it was built.
Soldering skills must be learned! We do not weld our projects (that is a different hobby)! Many problems are encountered that are traced to lack of soldering genes. If the joint looks like it is welded there is a good chance the parts being "welded" have suffered heat damage. Too much solder can lead to poor connections --cold solder joints and often a large welded joint spills over and shorts out other parts. There is also the problem of how to "unsolder" the welded joint. Take time to learn how to flow solder on to joints and how to do it without overheating the parts being soldered. This is where a temperature controlled iron is vital. Grounded irons are important to prevent static discharge to very sensitive (CMOS) electronic parts. Like I said the soldering part is like the last thing you do!
So OK you bought a kit and as usual soldered all of the caps (or resistors) first and then did the wiring, added the devices and are just about to enjoy your new toy(and with out additional checks) when  you hit the power and it smokes and nothing more. Before you power up that new radio that took three weeks to come from India (or China) use this process to review what you have done. Are the right wires to the right controls and/or connections, is the power supply polarity correct, etc.? If you go to my website and follow the link or go direct you will see embedded in the building of the Bitx40 all of what is described in this blog post. So while the focus has been on homebrew the information applies to kit projects too!
Pete N6QW

PS: One reader has suggested that analog scopes are available at very cheap prices as many hams have moved to the DSO and these older analog units can be had for pennies. An analog oscilloscope works FB for troubleshooting!

Tuesday, February 7, 2017

Gum on your shoe --- the Bitx40

Have you ever stepped in Chewing Gum?

The questioned posed is more like the result rather than the question --- no matter what you do it sticks and is just there, never to leave. So it is with my involvement with Bitx40 --- no matter how hard I try, there always seems to be an email in the queue asking me a question. Most recently there have been a flood of questions about the use of OLED displays on the Bitx40.
First asking me has some really negative aspects especially since the information is not being shared with the greater Bitx40 community such as would happen if posted on the Yahoo group reflector. Despite what  I tell my XYL that "I know everything", I don't and thus posing your question via the Yahoo group will give you the benefit of the "group grope" to wrestle with your question. I don't subscribe to the reflector so I may give you info that has been proven wrong.
The other negative aspect is asking me to do work that you should be doing. One ham made an inquiry about the 240X320 Color TFT display and I found out later he didn't like my suggestion that he start with some basic stuff like learning to swim before attempting to compete on the Olympic Swim Team. He loaded some one else's code and got it to work but then wanted me to make changes for him. I have declined to do so.
One scary experience is that my OLED implementation on the Bitx40 was done with a Nano, the OLED and Adafruit Si5351 board which was all external to the Bitx40. I have shared that code on my website at --- keep in mind when I bought my Bitx40 the "digi" module was not offered for sale. Thus the external homebrew digi-board with the OLED is what I used.. The scary part is that individuals have "ripped up" their VU2ESE supplied board and "haywired" in the OLED using my code. One report I got was the OLED displays OK but the Bitx doesn't seem to change frequency and the computer noise in the Rx masks everything. I asked did you put a scope or frequency counter on CLK0 to see if you are getting RF and what frequency is it? I am thinking that the overwhelming computer noise is masking the real signals. I have had no reply.
Now that is another bad aspect as I never imagined someone would cobble up Farhan's board as my implementation was a standalone board. The other negative by connecting directly into the Bitx40 , power rail you are opening up the possibility of noise. My outboard digi has the additional isolation. Bill N2CQR on his blog has covered active decoupling to resolve the noise issues with the OLED'S.
I don't mind helping but in the future will ask that Bitx40 questions be posted on the yahoo Bitx40 (actually Bitx20) group reflector.
The really Good News the Bitx40 is taking the World by storm!
Pete N6QW

Friday, February 3, 2017

Cool Stuff from N6QW

Cool Radios from the N6QW Laboratories!

 2/4/2017 ~ Request for AGC circuit being used. This was supplied to me by PD7SSB who came up with modification to my 20M Shirt Pocket Transceiver Project. It is an audio derived circuit. I have no details for implementing an RF/IF derived circuit such as the W7ZOI Hycas.

2/5/2017 ~ More on the AGC
Tribal knowledge here. The 4.7K Ohm Resistor connected to the output and feeding the diode was replaced by a 25K trim pot in series with a 3.3K fixed resistor. I found that there was too much "AGC" action with just the 4.7K ohm as shown on the schematic. The 25K pot was wired as a variable resistor (If you have to ask how to do that --turn off your soldering iron). Thus the range is 3.3K to 28.3K --now giving you a span of adjustments. Hold off  sending me an email as there will be some who suggest just using the 25K pot with one end to ground and the center wiper to the diode and the other end connected to the LM386 output. That is not what I did and I leave that to others for experimentation. The photo below the schematic is actually what is on the schematic including the microphone amplifier, audio amp, AGC and S Meter circuitry.

N6QW Two Band XCVR:  Mic Amp, Audio Amp, AGC, and S Meter Board

Pete N6QW

Wednesday, February 1, 2017

Secrets to Homebrewing ~ Revealed!

Secrets to Successful Homebrewing -- An Art!

Many years ago there was a joke going around about the person who widely advertised "Become Rich Quick!" Send $2 and discover how. As the story goes a reply would be received in the form of a postcard ( at that time 3 cents) which simply said "Do What I Did!" 
Well I could tell you to do what I have done; but that would undoubtedly be a disservice in that simply repeating what I have done has no guarantee and you didn't even have to spend the $2.
So for free -- you know how good free is -- are some suggestions for the would be or seasoned homebrewer on being successful in your builds.
  1. Getting organized by having a good information storage and retrieval system. A well established library, collections of data sheets, and cataloged project articles are worth their weight in gold
  2. A suitable well lit workspace where you can stop a project and return to it later picking up where you left off. I remember an article about a ham who had very limited space in his home save for the family laundry room. Clever guy that he was he built a swing down work table that was above the family washer and dryer. When he wanted to build something he simply let down the chains on either end of the hinged table and instant workbench. That worked very well once! Seems his XYL (like my XYL) absolutely hated ham radio. His XYL literally waited in the bushes until he just had everything ready to go and she would come in with the laundry basket and announce it was time to do the laundry. Of course they had a top loading washer --so his bench had to be put back. Find a better solution than this chap.
  3. Tools and Test Gear -- take a tip from Tim Allen (Star of Tool Time and also a ham today) and get the best tools and you do need something more than a 1920's voltmeter for test gear.  There have been many suggestions on a minimum tool set and test gear and if you navigate over  to there are several pages devoted to getting a good stock of basic tools and info on test equipment.
  4. Junk Box. Start now by collecting common parts in your junk box. You will not find a Radio Shack open at midnight when all you need is a 10K 1/4 resistor. Several years ago I wrote an article on how to stuff a junk box. You can find it on my website under Konstruction Korner. This is a recommendation on what you should have in the bins.
  5. Start with a small project like building the Michigan Mighty Mite one transistor transmitter as this has many benefits starting with low part count (less than 10 parts), low cost as many of the parts cost pennies, short build time, and UNDERSTANDING --yes not only build it but take the time to know what is the function of each part. Finally 9 out of 10 builders smoke the transistor for various reasons. Thus another few pennies and you are back in business. Smoking a set of finals in your Yaseu, ICOM or Kenwood will cost well  over $100. A small project is easier to troubleshoot!
  6. If it is a receiver you want then start with a direct conversion receiver (low part count, good sensitivity, easy build) and get that working. A DCR is a very usable rig! Once you have that going you can move up to a superhet with a crystal filter and other goodies. In 2015, Ben KK6FUT and I wrote a series of articles on the LBS (Lets Build Something) which is a project that did exactly that and the bonus literally all of the DCR was incorporated into the Superhet.
  7. A word here about the Bitx40 which is a pre-built complete radio including a digi LO and LCD for an amazing price of $59 delivered from India. This is a good starter project as there is much support and documentation to assist the builder. Costing only $59 and pre-built save for mounting in the customer supplied enclosure, this satisfies many of the criteria mentioned earlier.
  8. KEEP NOTES and RECORDS of settings, wiring diagrams, modifications, parts substitutions and as built sketches. You simply cannot remember all of this in your head!
  9.  Finally :Do not be afraid to ask questions from suitably knowledgeable people, in fact ask lots of them. Asking WHY leads to understanding and wisdom =. (Tnx Rob)
That is it --secrets revealed.
Pete N6QW

Tuesday, January 31, 2017

Sunday, January 29, 2017

SolderSmoke Podcast 193 ~ Insight and Comment

All Information is Good Information!

Someone once told me that and I have firmly come to believe that. Not that the information in itself may be good; but it is good to know that certain individuals believe something (which maybe erroneous) that you now know where they stand. The other side of the good information is that you may be presented with thoughts or concepts that perhaps were unintended in what you personally have presented. An example is to merely say "hook it up" and run the test failing to mention that the test needs to be run with a dummy load. You know to hook it into a dummy load; but that may not be clear to others.
For three years now I have participated in a monthly podcast along with Bill, N2CQR who has been at it for 10 years and is one of the original founders. Check out Bill's blog for a link to the latest podcast (#193). The subject matter of the blog --yep ham radio with an emphasis on homebrewing, current technical topics and a trip across our respective work benches to share projects we are  building. I tend to favor the newer technologies (digital VFO's) and Bill likes the older type (Analog VFO's). We had thought this was a good approach as it offered our listeners a range of topics or how to perform a task using different technologies. (A comment here: I see Bill drifting more and more toward the "digi" stuff.)
Usually the podcast starts by Bill asking me what number is it -- and I respond much like the Rock Jock's of the 1960's by shouting with enthusiasm the current number. I guess I always wanted to be a rock jock --a dream of mine that was fulfilled by my daughter who actually was one!
Hopefully our format shares technical knowledge and even our tales of woe as we  smoked parts and most importantly to include projects by our listeners. In fact Bill's blog is mostly about projects being built around the world with many of the projects directly relating to subjects covered in the podcast. At one time we ran a series about the Michigan Mite Mite a single transistor transmitter using colorburst crystals. Bill (mostly Bill) and I even supplied crystals to those wanting to build the project. We did supply about 50 crystals and we know of many being built using their own crystals. So we do think our efforts have been impactful across the world of ham radio.
The last several podcasts have highlighted a currently world wide popular ham transceiver known as the Bitx40. This amazing complete built 40 Meter SSB transceiver comes to you pre-built, delivered to your door for an amazing price of $59 --and that includes a digi LO and LCD display! Bill has built two  and I have built one!
But the real thrill of this radio is the ability to customize the project and there is even a "hack page" provided by the manufacturer to collect these mods/improvements, to which both Bill and I have contributed. I have even created a series of web pages to assist the 1st time builder to get the Bitx40 on the air. You can find that here Bitx40 from N6QW  We believe about 2000 of these radios are now in ham shacks across the globe. We have VU2ESE, Farhan to thank for this wonderful project and the idea of how to spread the ham radio gospel.

Two other recent technical highlights discussed reverse polarity protection and the use of active de-couplers to remove noise from audio circuit resulting from the use of OLED displays. Perhaps the message to us is that these were too simple technically to even merit a word let alone a discussion.  Inputs like this would help guide a selection of topical discussions.
Since we do the podcast monthly at times it may stretch to five weeks and to alert the podcast fans Bill will send notice the various reflectors in essence saying "we're back at it." So was the case yesterday when SS #193 was announced to the world.
On one particular reflector there were several negative comments about the podcast including a derisive comment about my "wanna be rock jock announcing" of the podcast number. Further comments involved the lack of technical content and it not being very useful. That is good information! Unlike our current POTUS 45 we are not thin skinned about negative comments nor have we banned any listeners!
Instead what would be helpful is if listener's would share with us the good, the bad and the ugly! If my shouting into the microphone is offensive to many of the listeners then it is an easy fix. Just tell us. But if you laugh a bit while I say it --let me know. As to technical content let us know that too. If you would like to know about Hilbert transforms or how does a Double Balanced Mixer perform a commutating action to demodulate a signal --we can do that too. Although a treatise on 3rd order linear regression might lose a few listeners. But let us know. The podcast is for you not us!
So to those several hams that had the courage to input negative comments we salute you and say thank you. But we'd also like to hear from others who may share those same negative (or positive) feelings about what Bill and I do. Let me assure you will not be banned from the podcast nor will you have to show proof of license.
Pete N6QW