Date   

My Bitx40 90% done

Mark W <K3MRK1@...>
 

Here are some pics of my Bitx40. I used a Harbor Freight ammo can. I will be putting a small battery inside. I havent decided on what I'll use for a mic. This one works fine, but only temporary.
Mark
K3MRK


Re: Blown by nearby transceiver #bitx40help

Jerry Gaffke
 

He did say "no antenna connected"
though that is not quite the same as saying "nothing connected to the Bitx40 antenna port".
Perhaps he still had coax from Bitx40 into the tuner.
Then a fault in the tuner or perhaps a switch in the wrong position could have brought on this sort of damage.
That would be considerably less mysterious.

However, if there was no connection to the Bitx40 antenna port, this could still be due to strong near-fields somehow.
The fact that Pat only managed to take out Q13 is no reason to think that things could not get worse with 
different a physical placement and perhaps a poor match through the tuner from his Icom. 

Jerry, KE7ER


On Mon, Feb 12, 2018 at 08:23 am, pat griffin wrote:

I think I am with Chris on this.  Early on, I fired up an Icom 735 a couple of feet away from the Bitx40 and it did indeed take out Q13 but left nary a mark.

 


Re: Blown by nearby transceiver #bitx40help

pat griffin
 

I think I am with Chris on this.  Early on, I fired up an Icom 735 a couple of feet away from the Bitx40 and it did indeed take out Q13 but left nary a mark.

Pat AA4PG



http://www.cahabatechnology.com/aa4pg.html


From: BITX20@groups.io <BITX20@groups.io> on behalf of chris gress <Chrisg0wfh@...>
Sent: Monday, February 12, 2018 9:42:38 AM
To: BITX20@groups.io
Subject: Re: [BITX20] Blown by nearby transceiver #bitx40help
 
My guess is he made a mistake and the 725 was wired to the bitx via coax and atu the poor bitx got a big dose of rf it can be fixed 

On 12 Feb 2018 15:37, "Jerry Gaffke via Groups.Io" <jgaffke=yahoo.com@groups.io> wrote:

Very curious. 
Blowing R131 and R132 might be due to a very large signal showing up at Q13,
though I would expect Q13 to blow first.

In your first post it says:
    > A quick flash, smoke, and the bitx40 that was only on, no antenna connected, died. 
I would think the Bitx40 would have to be in transmit to supply +12v via the TX rail
for R131,R132 to fry.  Perhaps the RF field also managed to turn on PTT somehow?

I find this to be very weird and still unexplained, we appreciate all the photos.
Another photo showing the tuner involved and the physical placement of transceiver, tuner, and Bitx40
would be appreciated.  Also any further information about what was going on when this occurred.

Jerry, KE7ER




On Mon, Feb 12, 2018 at 07:18 am, <edufortes@...> wrote:

I've found another two burned :/    R131 & R132


Re: Lost audio from receiver

Dennis Yancey <bigbluedry@...>
 

Put a socket in. That way you only need to fix the board once.. lm386 chips are cheap.


Re: Blown by nearby transceiver #bitx40help

Lawrence Galea
 

Looks like C131 has also flashed. There is a dark area as if has burned.

On Mon, Feb 12, 2018 at 4:18 PM, <edufortes@...> wrote:
Thanks to everyone for your help, I'll be checking those and trying to replace the burned components.

 Jerry Gaffke
 (KE7ER),

yes, we were testing 40m on a ICom IC-725. 

I've found another two burned :/    R131 & R132






Re: Blown by nearby transceiver #bitx40help

chris gress <Chrisg0wfh@...>
 

My guess is he made a mistake and the 725 was wired to the bitx via coax and atu the poor bitx got a big dose of rf it can be fixed 

On 12 Feb 2018 15:37, "Jerry Gaffke via Groups.Io" <jgaffke=yahoo.com@groups.io> wrote:

Very curious. 
Blowing R131 and R132 might be due to a very large signal showing up at Q13,
though I would expect Q13 to blow first.

In your first post it says:
    > A quick flash, smoke, and the bitx40 that was only on, no antenna connected, died. 
I would think the Bitx40 would have to be in transmit to supply +12v via the TX rail
for R131,R132 to fry.  Perhaps the RF field also managed to turn on PTT somehow?

I find this to be very weird and still unexplained, we appreciate all the photos.
Another photo showing the tuner involved and the physical placement of transceiver, tuner, and Bitx40
would be appreciated.  Also any further information about what was going on when this occurred.

Jerry, KE7ER




On Mon, Feb 12, 2018 at 07:18 am, <edufortes@...> wrote:

I've found another two burned :/    R131 & R132


Re: Blown by nearby transceiver #bitx40help

Jerry Gaffke
 

When bored with all the cat videos, take a look at this:
    https://www.youtube.com/watch?v=urglg3WimHA
Weird Al rules!

Jerry, KE7ER


On Mon, Feb 12, 2018 at 07:27 am, Gordon Gibby wrote:
Hi Jack, I hope your response was in jest!
 


Re: Blown by nearby transceiver #bitx40help

Jerry Gaffke
 

Very curious. 
Blowing R131 and R132 might be due to a very large signal showing up at Q13,
though I would expect Q13 to blow first.

In your first post it says:
    > A quick flash, smoke, and the bitx40 that was only on, no antenna connected, died. 
I would think the Bitx40 would have to be in transmit to supply +12v via the TX rail
for R131,R132 to fry.  Perhaps the RF field also managed to turn on PTT somehow?

I find this to be very weird and still unexplained, we appreciate all the photos.
Another photo showing the tuner involved and the physical placement of transceiver, tuner, and Bitx40
would be appreciated.  Also any further information about what was going on when this occurred.

Jerry, KE7ER




On Mon, Feb 12, 2018 at 07:18 am, <edufortes@...> wrote:

I've found another two burned :/    R131 & R132


Re: Blown by nearby transceiver #bitx40help

Gordon Gibby <ggibby@...>
 

Hi Jack, I hope your response was in jest!

I once gave a four session training package on financial planning to the docs at my institution and I told them the last session would be way off the beaten path, and I actually made a tin hat to wear to start off that session. As usual, my predictions turned out to be mostly completely wrong so far.  Luckily, I never completely believe even myself.


On Feb 12, 2018, at 10:24, Jack Purdum via Groups.Io <jjpurdum@...> wrote:

Fashion a hat with any leftover scraps.
Uncalled for...

Jack, W8TEE


From: Jerry Gaffke via Groups.Io <jgaffke@...>
To: BITX20@groups.io
Sent: Monday, February 12, 2018 10:22 AM
Subject: Re: [BITX20] Blown by nearby transceiver #bitx40help

Those with plastic cases for their Bitx40/uBitx and with nearby high power gear
might line the inside of that case with tinfoil.  Fashion a hat with any leftover scraps.
Jerry, KE7ER


On Sun, Feb 11, 2018 at 09:17 pm, Jerry Gaffke wrote:
I am still quite surprised that enough energy got coupled in to blow the trace. 
The traces do form a moderately large loop, a single turn inductor, perhaps that was all it took.
Or perhaps those toroids are not as self shielding as I had figured.



Re: Blown by nearby transceiver #bitx40help

Jack, W8TEE
 

Fashion a hat with any leftover scraps.
Uncalled for...

Jack, W8TEE


From: Jerry Gaffke via Groups.Io <jgaffke@...>
To: BITX20@groups.io
Sent: Monday, February 12, 2018 10:22 AM
Subject: Re: [BITX20] Blown by nearby transceiver #bitx40help

Those with plastic cases for their Bitx40/uBitx and with nearby high power gear
might line the inside of that case with tinfoil.  Fashion a hat with any leftover scraps.
Jerry, KE7ER


On Sun, Feb 11, 2018 at 09:17 pm, Jerry Gaffke wrote:
I am still quite surprised that enough energy got coupled in to blow the trace. 
The traces do form a moderately large loop, a single turn inductor, perhaps that was all it took.
Or perhaps those toroids are not as self shielding as I had figured.



Re: Blown by nearby transceiver #bitx40help

Jerry Gaffke
 

Those with plastic cases for their Bitx40/uBitx and with nearby high power gear
might line the inside of that case with tinfoil.  Fashion a hat with any leftover scraps.
Jerry, KE7ER


On Sun, Feb 11, 2018 at 09:17 pm, Jerry Gaffke wrote:
I am still quite surprised that enough energy got coupled in to blow the trace. 
The traces do form a moderately large loop, a single turn inductor, perhaps that was all it took.
Or perhaps those toroids are not as self shielding as I had figured.


Re: Blown by nearby transceiver #bitx40help

edufortes@...
 

Thanks to everyone for your help, I'll be checking those and trying to replace the burned components.

 Jerry Gaffke
 (KE7ER),

yes, we were testing 40m on a ICom IC-725. 

I've found another two burned :/    R131 & R132





Re: Second batch of uBITX shipping? #ubitx

Art Howard
 

Steve
 I should get mine today I noticed that it's in Minneapolis now.
  Do you know if the package has to be signed for ?
Art

On 12 Feb 2018 7:59 am, "S. Porter" <srporter@...> wrote:
Art,

Just got off the phone with a DHL rep who said DHL will deliver here, not USPS. Your mileage may vary. The package is on the move again this morning! :-)

73,
Steve

On Sat, Feb 10, 2018 at 04:08 pm, Art Howard wrote:
I also ordered mine on the 18th and mine is also sitting in Cincinnati for the last day.
 It is indicated that once it hits the USA it is USPS. Was supposed to deliver this last Friday so I figure maybe Tuesday here in Minnesota.
 


Re: wrong frequency after software change. #ubitx

Jack, W8TEE
 

The Files --> Open Recent menu choice holds the 10 most-recently opened projects. I find that very handy.

Jack, W8TEE



From: at91r40008 <yvon@...>
To: BITX20@groups.io
Sent: Monday, February 12, 2018 12:32 AM
Subject: Re: [BITX20] wrong frequency after software change. #ubitx

Thanks Jack. I missed that one.
It still doesn't show me the exact location of my project.
The problem is only I open more than one project at a 
time for comparison.
From now on when I download a project I'll rename it
immediately and insert a note where it is coming from.

--
73, Yvon NU6I



Re: AGC kits

Tim Gorman
 

The actual resistance will also depend on the input resistance of the final amplifier. For instance, if the volume pot is set to maximum you would have the 10K pot in parallel with the input resistance of the final amp. 

I will try a 10K resistor and rerun the test in the next couple of days. 


Re: Second batch of uBITX shipping? #ubitx

S. Porter <srporter@...>
 

Art,

Just got off the phone with a DHL rep who said DHL will deliver here, not USPS. Your mileage may vary. The package is on the move again this morning! :-)

73,
Steve


On Sat, Feb 10, 2018 at 04:08 pm, Art Howard wrote:
I also ordered mine on the 18th and mine is also sitting in Cincinnati for the last day.
 It is indicated that once it hits the USA it is USPS. Was supposed to deliver this last Friday so I figure maybe Tuesday here in Minnesota.
 


Re: uBITX woes, feeling disheartened. #ubitx

rlawson695@...
 

Ran :  does rx mean receive, if it does? The radio has been  reviveing the last four weeks  very good hearing  stations all over the world.  73’s de AC8XZ 


Re: Aluminum enclosure

Randy
 

6" x 6" is what it needs (for a very very tight fit). At least 2-1/2" inches if you are on standoffs. The stand-offs are 1/2 inch, the display is another 1-3/4 inch above the PCB.


Si5351mcu library update

Pavel Milanes Costa <pavelmc@...>
 

Hi OM.

I have re-worked on my lib for the Si5351, I have a few new features in there, if you like to peek you can check the code in github

https://github.com/pavelmc/Si5351mcu

Comments, critics, error spotting are welcomed.

Features

This are so far the implemented features (Any particular wish? use the Issues tab for that):

  • Custom XTAL passing on init (Default is 27.000 MHz (See Si.init() )
  • You can pass a correction to the xtal while running (See Si.correction() )
  • You have a fast way to power off all outputs of the Chip at once. (See Si.off() )
  • You can enable/disable any output at any time (See Si.enable(clk) and Si.disable(clk) )
  • By default all outputs are off after the Si.init() procedure. You has to enable them by hand.
  • You can only have 2 of the 3 outputs running at any moment (See "Two of three" section below)
  • Power control on each output independently (See Si.setPower(clk, level) on the lib header)
  • Initial power defaults to the lowest level (2mA) for all outputs.
  • You don't need to include and configure the Wire (I2C) library, this lib do that for you already.
  • Frequency limits are not hard coded on the lib, so you can stress your hardware to it's particular limit (You can move usually from ~3kHz to ~225 MHz, far away from the 8kHz to 160 MHz limits from the datasheet)
  • NEW: You has a way to verify the status of a particular clock (Enabled/Disabled by the Si.clkOn[clk] var)
  • NEW: From v0.5 and beyond we saved more than 1 kbyte of your precious firmware space due to the use of all integer math now (Worst induced error is below +/- 2 Hz)
  • NEW: Overclock, you can move the limits upward up to ~250MHz (see the "OVERCLOCK" section below)
  • NEW: Improved the click noise algorithm to get even more click noise reduction (see Click noise free section below)
  • NEW: Fast frequency changes as part of the improved click noise algorithm (see Click noise free section below)

73 Pavel CO7WT


Re: Aluminum enclosure

John KC9OJV
 

For the uBitx