Date   
Re: bitx40, sk

Ashhar Farhan
 

Allard,
I hope you will continue to engage in developing the software. My main rig is now an allard version of the bitx. Many thanks from us all for the wonderful effort you , arv, rahul and many others put into this project.
Whatever future holds, it shall certainly carry the allard code!
- f

On Tue 29 Oct, 2019, 2:18 PM Allard PE1NWL, <pe1nwl@...> wrote:
Dear Farhan,

many thanks for this wonderful BitX40 project!
I hope that you and your team enjoyed it as much as I and thousands of other builders did.

73 Allard PE1NWL

Re: bitx40, sk

Allard PE1NWL
 

Dear Farhan,

many thanks for this wonderful BitX40 project!
I hope that you and your team enjoyed it as much as I and thousands of other builders did.

73 Allard PE1NWL

Re: bitx40, sk

Viktors Miske
 

This is a sad day in radio history to say the least.

Re: cw filters

kh6sky
 

The MAX7410 can also be used as a notch filter.  I usually need one of these about as often as I do a peak filter. I am going to order a couple and experiment.  They are about $6 each at Digikey.

https://www.maximintegrated.com/en/design/technical-documents/app-notes/4/431.html

Jim KH6SKY

bitx40, sk

Ashhar Farhan
 

This is a little disappointing, but we had to pull the plug on the bitx40 run. The sales were sparse and frankly it had become a bit of a frankenstien.
There were too many connectors that one could plug in the wrong place, we moved from analog vfo (that drifted due to heating of the predriver) to raduino which wasn't well integrated. 

However, it was a bit deal for us all. It was first time we could ship a full ssb transceiver for 50 dollars. This went over and above the ARRL challenge that wanted just parts for $50. We could build, test and ship it for that price point. postage for a challenge and we ended up with going over the $50 mark, but it served many well. Once you had it going, it performed pretty well. it had a triple tuned front-end and the currently favourite 'down conversion' to 12 MHz IF.

We will miss this one, but all is not gone. Sunil continues to ship the bitx20v3 kits which can be modded to 40 meters. if time permits and some in the group volunteer, we could update the original bitx with a more contemporary design while preserving the original's bidirectional, single conversion scheme. Until then, we will continue to see more scratch built bitxs, a kind of return to the roots.

- f 

#ubitx-help #parts #ubitx-help #parts

Brad, K7NNR
 

I am getting ready to order my first µBITx with hopes that it will be here in time to put under the Christmas tree.

This being my first build, I am trying to get everything ordered prior to Christmas so I can spend the weekend building.  I am planning on going very basic this go around and besides a power supply and case (https://amateurradiokits.in/product/universal-case-black-for-ubitx/) what other components/parts will I need to source? 

It sounds like volume and tuning knobs will also be needed. I have read that these are not a standard size. Can someone provide any links to what I will need and the sizes.

Thanks in advance,

K7NNR

Re: Bitx 40 radino

Tech Guy
 

The hfsignals page shows 2nd from left as +12, 5th from left gnd, 3rd from left dds out (red), 4th from left dds gnd. I am looking at the dds board with the nano on the left and think pin 1 is on the end nearest the usb connector. Is that right? I guess I will tack some rg 174 to the pins for output and solder the power and gnd.

Re: Slow t/r receive recovery #ubitxcw

Mark Johnsen
 

Curt thank you for your advice.

Question regarding agc timing...

Referencing the July 2019 QST article authored by K1BQT he says that R5(680k) and C6(2.2uf) establishes the agc recovery time. A release time of approx. 1/2 second is noted.  
Multiplying the 2 values gives a value close to 1.5 seconds if I performed the math correctly.  
To reduce the agc time constant to published 0.5 second value should I decrease both C and R or can I reduce just one component?

Bitx 40 radino

Tech Guy
 

I just ordered a radino dds board for my bitx 40 version 3 board. I received a radino dds with an 8 pin header on the top but a 16 pin sip header pin on the bottom (like the ubitx to plug directly into the u bitx main board). I assume that I need to give the dds 12v and gnd but what output pin is the dds output? My old bitx 40 has the two pin header for vfo input. I seem to have the new dds board that doesn’t have the 5 pin header on the bottom. It came without the 8 pin plug. Anybody know where I can get one? Mouser? Digikey? Thanks
-John N4HNO

Faint 1 Hz "tick" heard on v5 uBITX, seems to be related to I2C #ubitx

Rob French (KC4UPR)
 

Hey there,

When I turned up the volume on my v5 uBITX relatively high, I realized that I was hearing a 1 Hz, somewhat high-pitched "ticking".  Now that I'm aware of it, I can hear it at lower volume settings too.  It appears to be related to I2C (I have an I2C 20x4 LCD display), since I get the exact same sound more rapidly if I turn the encoder (which obviously changes frequency on the display, requiring a display update as well as synthesizer update, and hence I2C noise).  I haven't looked into the KD8CEC source code, but I'm guessing there's a nominal 1 Hz message being sent on I2C in the absence of any other I2C traffic.  

Turning down my RF gain (I have the kit-projects.com ND6T AGC board installed, with a 1K audio taper pot for RF gain) makes the I2C noise more pronounced relatively to noise, i.e. turning down the RF gain makes my noise generally go down, but the I2C noise volume remains constant--so I'm assuming that means the I2C noise is coupling in downstream of the AGC, but that obviously isn't hard since the AGC is prior to the first RF.  I'll be honest, I probably didn't do enough testing/notetaking before installing the AGC to be able to say whether or not that is a cause... I know kit-projects recently removed the RF gain from the kit as offered, citing user challenges.  I attached an RF gain using two lengths of RG-174, with the shield of each grounded at the pot but not at the PCB, as I saw recommended on ND6T's website.  I do know that I had discovered the I2C "tuning noise" prior to the AGC installation, I just hadn't noticed the 1 Hz "tick".

So, anyway... I guess I'm talking myself out of the idea that I am picking up extra noise now with my install of the AGC.  Just trying to figure out how to alleviate it now.  Shield the I2C cable between the Raduino and the LCD?  Any thoughts on how to do that?  So far I haven't managed to find any shielded I2C cables.  I was thinking of taking the braid from some coax, inserting my leads through it, and then putting some heat shrink tubing on it.  Seems complicated... would definitely like to have a good vector on reducing the I2C noise before I expend too much effort!  Appreciate any suggestions...

Rob KC4UPR

Re: #bitx40 New BitX40 firmware release with Roger Beep function #bitx40

Ken Hansen
 

The beep is commonly referred to as a Roger Beep these days.

Opinions on CB vary by time (decade) and location - during the late 70s, when 'skip' was the order of the day, it was a generally fun thing in both the CA and NJ areas I lived in, and sidebanders stuck to frequencies between 11 and 10 meters, AMers stuck between 12 and 11 meters.

In the 80s, it seemed like the 'CB scene' turned into amplifier festivals, and that persisted in certain cultures to today (every year in Belton Hamfest there's a few guys selling multi "pill" amplifiers that look like horrible home brew projects.

In the 60s I think CB was fairly gentlemanly, but that's based on things I read, not experienced.

Most hams that disparage CBers assume they will bring their 10-codes and odd speech mannerisms to their local repeater and reflect badly on their hobby. 

Many hams in my area were once 'big' on CB, running power, beams, etc. and having a few hundred watts of linear power in their mobile.

Where I live now, DFW, there is still a very active REACT club, much to my surprise, and REACT still advertises in CQ magazine as I recall.

Ken, N2VIP

On Oct 28, 2019, at 12:40, Donald <donwestpwl@...> wrote:

I shall never understand this bias against CB radio. I do hope it only occurs in the U.S.A.

Donald, KB5PWL

Re: nextion 2.8 installation

Jim Willis
 

Evan,

Excellent advice!

Best regards,

Jim

On Oct 28, 2019, at 5:28 PM, Evan Hand <elhandjr@...> wrote:

When I did my v5 rig, I first got it working on the stock display and firmware.  After verifying that all was working, then I did the modifications needed for the display change and the KD8CEC firmware updates.  The firmware from CEC must match the display.  So if you have the Nextion display, then I would do both the display and the Raduino (Nano) upgrade at the same time.  If you do it changing first to the KD8CEC firmware on the Raduino Nano, and not change the display, you need to load a different version than the Nextion display version.  Not really much value in doing the extra load of the firmware, as the things you are changing will need to be redone when you change the display.

If you do not have the display, and want to use the memory manager software, then upgrading to the KD8CEC firmware for the 16x2 parallel input software will at least get you going on using the Memory Manager and allowing you to operate some of the digital modes.  Just be sure you get the correct version (read the .txt file info file in the CEC software zip file).

The case that you bought may have some of the wiring different than stock,so you need to verify with the supplier on how to wire the new display.  For me, with an off the shelf generic case, it was simply wiring up a set of header pins to take the place of the 16x2 display soldering the correct wires from the Nextion display to it.  Then download the software to the Nano and a microSD card for the Nextion.

The programming is best done with the Hexloader program for the Nano in the Raduino.  Here again make sure you have the correct program file, as there is one for each type of display.

The next hurdle is to get the tft correct (there are two version for each size display.  If you have a basic display you need the basic tft file, and if an enhanced display you need the enhanced tft file.  Again make sure you read the file info from the CEC zip file.  I would also recommend that you use no more than a 16gb microSD card.  That way the file system will be correct.  There are ways to make higher capacity cards work, however the 8 or 16 gb are so cheap, just get one of those.

The above are my experiences, others may have different ones and different recommendations Please check out for yourself as it is all at your own risk.

73
Evan
CA9TU.

Re: nextion 2.8 installation

Evan Hand
 

When I did my v5 rig, I first got it working on the stock display and firmware.  After verifying that all was working, then I did the modifications needed for the display change and the KD8CEC firmware updates.  The firmware from CEC must match the display.  So if you have the Nextion display, then I would do both the display and the Raduino (Nano) upgrade at the same time.  If you do it changing first to the KD8CEC firmware on the Raduino Nano, and not change the display, you need to load a different version than the Nextion display version.  Not really much value in doing the extra load of the firmware, as the things you are changing will need to be redone when you change the display.

If you do not have the display, and want to use the memory manager software, then upgrading to the KD8CEC firmware for the 16x2 parallel input software will at least get you going on using the Memory Manager and allowing you to operate some of the digital modes.  Just be sure you get the correct version (read the .txt file info file in the CEC software zip file).

The case that you bought may have some of the wiring different than stock,so you need to verify with the supplier on how to wire the new display.  For me, with an off the shelf generic case, it was simply wiring up a set of header pins to take the place of the 16x2 display soldering the correct wires from the Nextion display to it.  Then download the software to the Nano and a microSD card for the Nextion.

The programming is best done with the Hexloader program for the Nano in the Raduino.  Here again make sure you have the correct program file, as there is one for each type of display.

The next hurdle is to get the tft correct (there are two version for each size display.  If you have a basic display you need the basic tft file, and if an enhanced display you need the enhanced tft file.  Again make sure you read the file info from the CEC zip file.  I would also recommend that you use no more than a 16gb microSD card.  That way the file system will be correct.  There are ways to make higher capacity cards work, however the 8 or 16 gb are so cheap, just get one of those.

The above are my experiences, others may have different ones and different recommendations Please check out for yourself as it is all at your own risk.

73
Evan
CA9TU.

Re: #bitx40 New BitX40 firmware release with Roger Beep function #bitx40

MadRadioModder
 

Roger, good buddy... beep beep.  


MRM

 


On Oct 28, 2019, at 2:13 PM, ajparent1/KB1GMX <kb1gmx@...> wrote:

Donald,

OM mode and some history.

The roger beep was not a common thing until the CB  mess broke down
in the early 80s and it was often accompanied with  other electronic noise
makers and profanity.  Then that mess started move into the lower (cw)
sections of the 10M band and they got tired of freebanding.

Most of us back when that used CB found it annoying and unneeded especially
for SSB.  The general feeling is it was those that were disruptive or trying to
feel like they were running something important doing it initially.  It was
especially noxious when it appeared in the 80s.  Then it became a feature
on CB radios (a signal that those that were modified for non CB allocated
frequencies) and later Chinese made HTs.

One questions the importance of the beep and its need.  For the Space activities 
(Mercury and later) it was needed as the communications were actually full duplex
on the data links and you had to have some way of knowing when the other guy
was done as in really did release the button and it was also to confirm the
button didn't stick as in heard in the astronauts headphone when he released 
the button (or VOX).  Until CB adopted it if you heard a over beep  is was likely
a repeater (usually ham) or space based radio (space program).

To date I know of the use of "over beep" appearing is standard communications
systems, those being Space program, Repeaters, military systems that use
satellite links, and CB.

Personally I don't care, if its short and unobtrusive.  It does however represent 
a range of what one can do with a MPU of reasonable power and programming.

Allison

--

…_. _._

Re: #bitx40 New BitX40 firmware release with Roger Beep function #bitx40

Donald <donwestpwl@...>
 

Okay, you want to hate CB radio, hate it. I might have become a ham when I was a teenager, but the only ham in my area was a less-than-amiable person who didn't want to bother with me. It was, in fact, a CBer-turned-ham who encouraged and helped me get a ham license.

Fortunately for me, I didn't judge all hams by the first one I met.

Donald, KB5PWL

On 10/28/2019 1:13 PM, ajparent1/KB1GMX wrote:
Donald,

OM mode and some history.

The roger beep was not a common thing until the CB  mess broke down
in the early 80s and it was often accompanied with  other electronic noise
makers and profanity.  Then that mess started move into the lower (cw)
sections of the 10M band and they got tired of freebanding.

Most of us back when that used CB found it annoying and unneeded especially
for SSB.  The general feeling is it was those that were disruptive or trying to
feel like they were running something important doing it initially.  It was
especially noxious when it appeared in the 80s.  Then it became a feature
on CB radios (a signal that those that were modified for non CB allocated
frequencies) and later Chinese made HTs.

One questions the importance of the beep and its need.  For the Space activities 
(Mercury and later) it was needed as the communications were actually full duplex
on the data links and you had to have some way of knowing when the other guy
was done as in really did release the button and it was also to confirm the
button didn't stick as in heard in the astronauts headphone when he released 
the button (or VOX).  Until CB adopted it if you heard a over beep  is was likely
a repeater (usually ham) or space based radio (space program).

To date I know of the use of "over beep" appearing is standard communications
systems, those being Space program, Repeaters, military systems that use
satellite links, and CB.

Personally I don't care, if its short and unobtrusive.  It does however represent 
a range of what one can do with a MPU of reasonable power and programming.

Allison

Re: nextion 2.8 installation

HB9FIH
 

Dave have a look int the site. There is a vy nice description how to do step by step.
http://www.hamskey.com/2019/04/release-cec-firmware-v1200-for-ubitx.html?m=1

Erich



On Mon, Oct 28, 2019 at 11:23 PM, <dgclifford@...> wrote:
Hi men I  know i am a bit late to the party .I have finished  my ubitx   and it works a treat,  i also have the nextion 2.8 front panel and the nextion 2.8 unit. The question is where to start having never done much software work i feel at a bit of a loss, are there any step by step guides available that will take me through the process of installation and maybe update my software.  Should i get one thing done at a time or go for both in one session .Any views or help would be most gratefully  received  Dave C     GW0NVF

nextion 2.8 installation

dave
 

Hi men I  know i am a bit late to the party .I have finished  my ubitx   and it works a treat,  i also have the nextion 2.8 front panel and the nextion 2.8 unit. The question is where to start having never done much software work i feel at a bit of a loss, are there any step by step guides available that will take me through the process of installation and maybe update my software.  Should i get one thing done at a time or go for both in one session .Any views or help would be most gratefully  received  Dave C     GW0NVF

Re: How to secure the inductors

Geoff G3NPI
 

Nigel,

 

Please be aware that if the Toroids are very close to a metal surface it may detune them.

 

73

 

Geoff  G3NPI   EX  ZS1GS a very l o n g time ago………

 

Sent from Mail for Windows 10

 


Virus-free. www.avg.com

Re: How to secure the inductors

Nigel
 

Greetings from ZS land :-)

Timing of question is perfect!  Reason being is that I am nearing assembly stage of my V3 uBitx now that the hardware design / fabrication is almost complete and due to space limitations, I need to reduce overall height of main board / components in one area by a couple of mm. The items that are proving too high are the toroids associated with the mixers.

On inspection, I notice that there are plastic / nylon bases (well at least they melt if prodded with the tip of a hot soldering iron!) between the pcb and the toroid serving to keep the windings in position (I guess?).  My plan is to remove so that each 'transformer' assembly will be lowered and hence allow use of the case I am building. An alternative (but this is likely to be more disruptive than just lowering) is to mount the transformers on their side.

Hence my interest in this topic as wondering if by removing the toroid base (or changing orientation but keeping the relative 90 degree alignments) there will be any (significant) difference to performance?

Anyone care to comment?

I have thought about making a temporary harness to test prior to undertaking the modifications but hopefully someone who can advise will make that step unnecessary. Then again, I am thinking that if this was a VHF or above unit then yes, there would more than likely be a difference but at HF I doubt it. Guess is better to ask than find out the hard way!

As an aside, my intention is to test after assembly BEFORE adding enhancements / changing the firmware...

Many thanks in advance for any and all feedback.

Best regards to all

Nigel ZS6RN ex G8DEV (l-o-n-g time ago)

Re: #bitx40 New BitX40 firmware release with Roger Beep function #bitx40

ajparent1/kb1gmx
 

Donald,

OM mode and some history.

The roger beep was not a common thing until the CB  mess broke down
in the early 80s and it was often accompanied with  other electronic noise
makers and profanity.  Then that mess started move into the lower (cw)
sections of the 10M band and they got tired of freebanding.

Most of us back when that used CB found it annoying and unneeded especially
for SSB.  The general feeling is it was those that were disruptive or trying to
feel like they were running something important doing it initially.  It was
especially noxious when it appeared in the 80s.  Then it became a feature
on CB radios (a signal that those that were modified for non CB allocated
frequencies) and later Chinese made HTs.

One questions the importance of the beep and its need.  For the Space activities 
(Mercury and later) it was needed as the communications were actually full duplex
on the data links and you had to have some way of knowing when the other guy
was done as in really did release the button and it was also to confirm the
button didn't stick as in heard in the astronauts headphone when he released 
the button (or VOX).  Until CB adopted it if you heard a over beep  is was likely
a repeater (usually ham) or space based radio (space program).

To date I know of the use of "over beep" appearing is standard communications
systems, those being Space program, Repeaters, military systems that use
satellite links, and CB.

Personally I don't care, if its short and unobtrusive.  It does however represent 
a range of what one can do with a MPU of reasonable power and programming.

Allison