Date   

Re: uBITX Firmware (CEC) 0.30 released (Test version). #ubitx

Ian Lee
 

toggle between Straight <-> Paddle (A or B), so if crruent straight key selected, show Fn(A), Fn(B), if paddle key selected, show Key:Straight?
but, I used the Toggle method to reduce code usage.However, this seems to be difficult to use.
I will change it to a dial like any other menu.

Thanks for your information

Ian KD8CEC

2018-01-29 16:20 GMT+09:00 Mike Woods <mhwoods@...>:

Marco - you need to go into Setup mode and then re-enter the menu and select Key Fn.=A.  It defaults to a straight key

M

On Mon, 29 Jan 2018 at 7:08 PM, M Garza <mgarza896@...> wrote:
I forgot to mention that it worked before the upgrade and is wired according to the hfsignals instructions/schematic.

Thanks again.

Marco - KG5PRT

On Mon, Jan 29, 2018 at 12:05 AM, M Garza <mgarza896@...> wrote:
Hello Ian,
I have just upgraded to v.30 and all the settings and fixes are much appreciated.  I have a problem, though.  I am unable to use the keyer.  It does nothing.  
Is there a hardware mod that needs to be performed to get it working again?

Thank you in advance,

Marco - KG5PRT

On Sun, Jan 28, 2018 at 3:03 PM, Mike Woods <mhwoods@...> wrote:
Ian

I commend you on your latest software Beta release (v0.30). This worked faultlessly for me, and I loved being able to adjust the step rate (I have it set on 10Hz now). 

The band stacking registers and band switching is fantastic.  I had intended modding the software myself to get band stacking and easy ham band switching, but I no longer need to bother!  I may still add front panel buttons for band up/band down functions, but the menu band changing function is fairly handy already.  It would be good to have a SPLIT function (in addition to A/B) and perhaps a limited number of programmable memories (10?). 

I like the way that you can select either ham bands or general coverage RX.  You go into the band change menu, and then hold the switch down for longer to toggle between modes. 

I have some minor suggestions for improvement.  The main thought would be to change the display of the RIT function to show the frequency offset rather than the absolute frequency (i.e. show -0.415 KHz or +0.001 kHz etc).  This reflects how most people think of incremental tuning.  Once you are done setting the RIT and exit the menu it would show the absolute frequency as normal on the display while the RIT still turned on.  The display should, however, continue to display "RIT"/  There is a whole other line above the frequency display to show function settings on RX.  Similarly you could show the keyer mode on the first line (e.g. STRAIGHT, IAMBICA, IAMBICB).

I love the way in which you have corrected the frequency display below 1MHz and opened up the RX to 1kHz to 100MHz.   A shorter press allows you to set the step function.   A long press on the dial switch gives you dial lock.  This works well.  I like the way the step speed increases when you turn the dial faster, but the dial no longer goes crazy, throwing you half a Megahertz away on outside the ham band.   Well done!

The function to monitor ADC levels could be very useful for those having issues with CW keying. My uBITx has always worked fine with both manual and paddle keys.  This suggests that the resistor tolerances are probably a bit narrow.  My resistor values may be closer tolerance than what others have received.   A check on the monitor function shows this to be the case.

I didn't find documentation on exactly how the ADC monitoring function works.  I believe it shows a continuous stream of readings on the port (0 to 1023) with 6 readings at a time.   However, I don't think you can exit from this function without turning off the rig?  This allows you to press dit, dah or the manual key to get a reading for the ADC value being received by the arduino.   This then allows the setting ranges to be adjusted.

If you are still fence sitting about a software upgrade you shouldn't be!   Upgrading the stock software is reasonably straight forward.   Let me tell you that if you have a stock uBITx, you should definitely be downloading this sketch and increasing functionality and ease of use.  It is a fine effort. 


Mike ZL1AXG


On 28/01/18 6:12 PM, Ian Lee wrote:
Dave

Thanks for your information.

My modified code (Ron's cw keying) does not use A7 for factory shipping users.
Until now, the firmware concept was applied without modification of the hardware.
I am going to end this project because I do not have any further improvements without hardware modifications.

When additional uBITX order arrives, I try to do a variety of fun H / W hacks.At that time, I will use A7 as Paddle and connect to S.Meter.

Ian KD8CEC

2018-01-28 6:14 GMT+09:00 Dave Bottom <ars.kd6az@...>:
Ian 

The v.30 with Ron’s CW Keying code does include adding the 4.7k pull-up at A7, as a modification to hardware.

I’m planning on adding both 4.7K chip resistors directly on the pads of the Raduino so there are no loose resistors to mount at the key jack(s).

Dave WI6R

Sent from my iPhone

On Jan 27, 2018, at 2:39 AM, Ian Lee <kd8cec@...> wrote:

I have not posted it on my blog separately since it is a test version. When the test is complete,  write a usage and post it.
I am writing for someone who is interested and test.  If I get an error report or a fix, I'll fix it and make it into github's 0.31 branch.

Here is a brief description of the change from 0.30.
improved CW Keying, Frequency Tune and CW performance according to users' requirements.
In particular, CW Keying applied ron's logic for use with original hardware. also made it possible to set the CW Key ADC range to reduce errors in CW.
ADC monitoring function is added to know the exact resistance and key contact status.
I thought that if you set your own ADC range using the measured values here, you would get an error. I need to test these things, so I leave this post.

removed all existing sources related to frequency tune. And i applied threshold, weight about speed, and steps. The problem of changing the frequency at the moment of catching the knob has probably disappeared. when the threshold has been exceeded, start frequency changing, i added some logic to prevent the thresholds from becoming unnatural.
If you want to fine-tune, slowly turn it and the threshold will be applied continuously and change very slowly.
The tune steps you can select now are 10, 20, 50, 100, 200, but you can change them in uBITX Manager 0.31 (now working)
You can change the step by pressing the function key for a long time. If you keep pressing it, Diallock will work.

The ham band movement applied at 0.28 was set to 0.30, so that region1 was set as the default.
Of course, you can change to the previous operation state by pressing the function key in the band select menu for a long time.
And like the 0.28 version, you can set up to 10 frequency bands in uBITX Manager to suit your country or your liking.

Please refer to below for the improvements and how to upload firmware and more detail.
The source and compiled firmware can be found in the release below link.
https://github.com/phdlee/ubitx

How to upload firmware and use version up to version 0.27
http://www.hamskey.com

--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Mike Woods
mhwoods@...





--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


Re: IRF510 amplifier failures

Tim Gorman
 

A current "limiter" which modulates the current, i.e. limiting the
current no matter the drive level, is like applying an ALC to the
exciter. Improper design can result in compression of the signal which
can then generate spurious responses in the output.

If the current limiter is of a "drop-out" style which requires
resetting then this won't happen, it will just shut down the exciter.
In that case, however, it doesn't provide much efficiency over a plain
old fuse!

tim ab0wr

On Fri, 26 Jan 2018 05:32:08 -0800
"n5ib_2" <n5ib@...> wrote:

One other possibility to consider to protect against overcurrent
situations is to use a current limiting power supply, or add a
current limiter to an existing power supply or battery.

The current limiter circuit whose link is at this site:
<http://n5ib.net/Index.xht>
will go up to 2.2 amps, and includes a low-dropout voltage regulator
that also provides reverse polarity protection.

There is a version, in a different package, of that same regulator
chip that has an added "tracking" feature - being able to parallel
multiple chips to increase the available current. Details are on the
datasheet in the document.

Jim, N5IB



Re: uBITX Firmware (CEC) 0.30 released (Test version). #ubitx

Ian Lee
 

Marco

First, there was a problem with previous H / W compatibility. Are you using a straight key?
The concept of this firmware is that it can be used without any modification.
Please upgrade only once again.
also You need to set the key. You can select Paddle and Paddle from the setup menu.
After receiving this e-mail, please try to upload firmware again in 2 hours. It has been modified.

Ian KD8CEC


2018-01-29 15:05 GMT+09:00 M Garza <mgarza896@...>:

Hello Ian,
I have just upgraded to v.30 and all the settings and fixes are much appreciated.  I have a problem, though.  I am unable to use the keyer.  It does nothing.  
Is there a hardware mod that needs to be performed to get it working again?

Thank you in advance,

Marco - KG5PRT

On Sun, Jan 28, 2018 at 3:03 PM, Mike Woods <mhwoods@...> wrote:
Ian

I commend you on your latest software Beta release (v0.30). This worked faultlessly for me, and I loved being able to adjust the step rate (I have it set on 10Hz now). 

The band stacking registers and band switching is fantastic.  I had intended modding the software myself to get band stacking and easy ham band switching, but I no longer need to bother!  I may still add front panel buttons for band up/band down functions, but the menu band changing function is fairly handy already.  It would be good to have a SPLIT function (in addition to A/B) and perhaps a limited number of programmable memories (10?). 

I like the way that you can select either ham bands or general coverage RX.  You go into the band change menu, and then hold the switch down for longer to toggle between modes. 

I have some minor suggestions for improvement.  The main thought would be to change the display of the RIT function to show the frequency offset rather than the absolute frequency (i.e. show -0.415 KHz or +0.001 kHz etc).  This reflects how most people think of incremental tuning.  Once you are done setting the RIT and exit the menu it would show the absolute frequency as normal on the display while the RIT still turned on.  The display should, however, continue to display "RIT"/  There is a whole other line above the frequency display to show function settings on RX.  Similarly you could show the keyer mode on the first line (e.g. STRAIGHT, IAMBICA, IAMBICB).

I love the way in which you have corrected the frequency display below 1MHz and opened up the RX to 1kHz to 100MHz.   A shorter press allows you to set the step function.   A long press on the dial switch gives you dial lock.  This works well.  I like the way the step speed increases when you turn the dial faster, but the dial no longer goes crazy, throwing you half a Megahertz away on outside the ham band.   Well done!

The function to monitor ADC levels could be very useful for those having issues with CW keying. My uBITx has always worked fine with both manual and paddle keys.  This suggests that the resistor tolerances are probably a bit narrow.  My resistor values may be closer tolerance than what others have received.   A check on the monitor function shows this to be the case.

I didn't find documentation on exactly how the ADC monitoring function works.  I believe it shows a continuous stream of readings on the port (0 to 1023) with 6 readings at a time.   However, I don't think you can exit from this function without turning off the rig?  This allows you to press dit, dah or the manual key to get a reading for the ADC value being received by the arduino.   This then allows the setting ranges to be adjusted.

If you are still fence sitting about a software upgrade you shouldn't be!   Upgrading the stock software is reasonably straight forward.   Let me tell you that if you have a stock uBITx, you should definitely be downloading this sketch and increasing functionality and ease of use.  It is a fine effort. 


Mike ZL1AXG


On 28/01/18 6:12 PM, Ian Lee wrote:
Dave

Thanks for your information.

My modified code (Ron's cw keying) does not use A7 for factory shipping users.
Until now, the firmware concept was applied without modification of the hardware.
I am going to end this project because I do not have any further improvements without hardware modifications.

When additional uBITX order arrives, I try to do a variety of fun H / W hacks.At that time, I will use A7 as Paddle and connect to S.Meter.

Ian KD8CEC

2018-01-28 6:14 GMT+09:00 Dave Bottom <ars.kd6az@...>:
Ian 

The v.30 with Ron’s CW Keying code does include adding the 4.7k pull-up at A7, as a modification to hardware.

I’m planning on adding both 4.7K chip resistors directly on the pads of the Raduino so there are no loose resistors to mount at the key jack(s).

Dave WI6R

Sent from my iPhone

On Jan 27, 2018, at 2:39 AM, Ian Lee <kd8cec@...> wrote:

I have not posted it on my blog separately since it is a test version. When the test is complete,  write a usage and post it.
I am writing for someone who is interested and test.  If I get an error report or a fix, I'll fix it and make it into github's 0.31 branch.

Here is a brief description of the change from 0.30.
improved CW Keying, Frequency Tune and CW performance according to users' requirements.
In particular, CW Keying applied ron's logic for use with original hardware. also made it possible to set the CW Key ADC range to reduce errors in CW.
ADC monitoring function is added to know the exact resistance and key contact status.
I thought that if you set your own ADC range using the measured values here, you would get an error. I need to test these things, so I leave this post.

removed all existing sources related to frequency tune. And i applied threshold, weight about speed, and steps. The problem of changing the frequency at the moment of catching the knob has probably disappeared. when the threshold has been exceeded, start frequency changing, i added some logic to prevent the thresholds from becoming unnatural.
If you want to fine-tune, slowly turn it and the threshold will be applied continuously and change very slowly.
The tune steps you can select now are 10, 20, 50, 100, 200, but you can change them in uBITX Manager 0.31 (now working)
You can change the step by pressing the function key for a long time. If you keep pressing it, Diallock will work.

The ham band movement applied at 0.28 was set to 0.30, so that region1 was set as the default.
Of course, you can change to the previous operation state by pressing the function key in the band select menu for a long time.
And like the 0.28 version, you can set up to 10 frequency bands in uBITX Manager to suit your country or your liking.

Please refer to below for the improvements and how to upload firmware and more detail.
The source and compiled firmware can be found in the release below link.
https://github.com/phdlee/ubitx

How to upload firmware and use version up to version 0.27
http://www.hamskey.com

--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Mike Woods
mhwoods@...




--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


Re: uBITX Firmware (CEC) 0.30 released (Test version). #ubitx

Ian Lee
 

Mike

Thanks for your fulltest.. perfect!
I have found improvements in your mail.
These improvements will be reflected in version 0.3.
When version 0.3 is finalized, we will change the version to 1.0
And I am going to go to the fun world with uBITX h/w modification. There are a lot of interesting ideas.
Thank you again.
Ian KD8CEC


2018-01-29 6:03 GMT+09:00 Mike Woods <mhwoods@...>:

Ian

I commend you on your latest software Beta release (v0.30). This worked faultlessly for me, and I loved being able to adjust the step rate (I have it set on 10Hz now). 

The band stacking registers and band switching is fantastic.  I had intended modding the software myself to get band stacking and easy ham band switching, but I no longer need to bother!  I may still add front panel buttons for band up/band down functions, but the menu band changing function is fairly handy already.  It would be good to have a SPLIT function (in addition to A/B) and perhaps a limited number of programmable memories (10?). 

I like the way that you can select either ham bands or general coverage RX.  You go into the band change menu, and then hold the switch down for longer to toggle between modes. 

I have some minor suggestions for improvement.  The main thought would be to change the display of the RIT function to show the frequency offset rather than the absolute frequency (i.e. show -0.415 KHz or +0.001 kHz etc).  This reflects how most people think of incremental tuning.  Once you are done setting the RIT and exit the menu it would show the absolute frequency as normal on the display while the RIT still turned on.  The display should, however, continue to display "RIT"/  There is a whole other line above the frequency display to show function settings on RX.  Similarly you could show the keyer mode on the first line (e.g. STRAIGHT, IAMBICA, IAMBICB).

I love the way in which you have corrected the frequency display below 1MHz and opened up the RX to 1kHz to 100MHz.   A shorter press allows you to set the step function.   A long press on the dial switch gives you dial lock.  This works well.  I like the way the step speed increases when you turn the dial faster, but the dial no longer goes crazy, throwing you half a Megahertz away on outside the ham band.   Well done!

The function to monitor ADC levels could be very useful for those having issues with CW keying. My uBITx has always worked fine with both manual and paddle keys.  This suggests that the resistor tolerances are probably a bit narrow.  My resistor values may be closer tolerance than what others have received.   A check on the monitor function shows this to be the case.

I didn't find documentation on exactly how the ADC monitoring function works.  I believe it shows a continuous stream of readings on the port (0 to 1023) with 6 readings at a time.   However, I don't think you can exit from this function without turning off the rig?  This allows you to press dit, dah or the manual key to get a reading for the ADC value being received by the arduino.   This then allows the setting ranges to be adjusted.

If you are still fence sitting about a software upgrade you shouldn't be!   Upgrading the stock software is reasonably straight forward.   Let me tell you that if you have a stock uBITx, you should definitely be downloading this sketch and increasing functionality and ease of use.  It is a fine effort. 


Mike ZL1AXG


On 28/01/18 6:12 PM, Ian Lee wrote:
Dave

Thanks for your information.

My modified code (Ron's cw keying) does not use A7 for factory shipping users.
Until now, the firmware concept was applied without modification of the hardware.
I am going to end this project because I do not have any further improvements without hardware modifications.

When additional uBITX order arrives, I try to do a variety of fun H / W hacks.At that time, I will use A7 as Paddle and connect to S.Meter.

Ian KD8CEC

2018-01-28 6:14 GMT+09:00 Dave Bottom <ars.kd6az@...>:
Ian 

The v.30 with Ron’s CW Keying code does include adding the 4.7k pull-up at A7, as a modification to hardware.

I’m planning on adding both 4.7K chip resistors directly on the pads of the Raduino so there are no loose resistors to mount at the key jack(s).

Dave WI6R

Sent from my iPhone

On Jan 27, 2018, at 2:39 AM, Ian Lee <kd8cec@...> wrote:

I have not posted it on my blog separately since it is a test version. When the test is complete,  write a usage and post it.
I am writing for someone who is interested and test.  If I get an error report or a fix, I'll fix it and make it into github's 0.31 branch.

Here is a brief description of the change from 0.30.
improved CW Keying, Frequency Tune and CW performance according to users' requirements.
In particular, CW Keying applied ron's logic for use with original hardware. also made it possible to set the CW Key ADC range to reduce errors in CW.
ADC monitoring function is added to know the exact resistance and key contact status.
I thought that if you set your own ADC range using the measured values here, you would get an error. I need to test these things, so I leave this post.

removed all existing sources related to frequency tune. And i applied threshold, weight about speed, and steps. The problem of changing the frequency at the moment of catching the knob has probably disappeared. when the threshold has been exceeded, start frequency changing, i added some logic to prevent the thresholds from becoming unnatural.
If you want to fine-tune, slowly turn it and the threshold will be applied continuously and change very slowly.
The tune steps you can select now are 10, 20, 50, 100, 200, but you can change them in uBITX Manager 0.31 (now working)
You can change the step by pressing the function key for a long time. If you keep pressing it, Diallock will work.

The ham band movement applied at 0.28 was set to 0.30, so that region1 was set as the default.
Of course, you can change to the previous operation state by pressing the function key in the band select menu for a long time.
And like the 0.28 version, you can set up to 10 frequency bands in uBITX Manager to suit your country or your liking.

Please refer to below for the improvements and how to upload firmware and more detail.
The source and compiled firmware can be found in the release below link.
https://github.com/phdlee/ubitx

How to upload firmware and use version up to version 0.27
http://www.hamskey.com

--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Mike Woods
mhwoods@...



--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


Re: uBITX Firmware (CEC) 0.30 released (Test version). #ubitx

Mike Woods
 

Marco - you need to go into Setup mode and then re-enter the menu and select Key Fn.=A.  It defaults to a straight key

M


On Mon, 29 Jan 2018 at 7:08 PM, M Garza <mgarza896@...> wrote:
I forgot to mention that it worked before the upgrade and is wired according to the hfsignals instructions/schematic.

Thanks again.

Marco - KG5PRT

On Mon, Jan 29, 2018 at 12:05 AM, M Garza <mgarza896@...> wrote:
Hello Ian,
I have just upgraded to v.30 and all the settings and fixes are much appreciated.  I have a problem, though.  I am unable to use the keyer.  It does nothing.  
Is there a hardware mod that needs to be performed to get it working again?

Thank you in advance,

Marco - KG5PRT

On Sun, Jan 28, 2018 at 3:03 PM, Mike Woods <mhwoods@...> wrote:
Ian

I commend you on your latest software Beta release (v0.30). This worked faultlessly for me, and I loved being able to adjust the step rate (I have it set on 10Hz now). 

The band stacking registers and band switching is fantastic.  I had intended modding the software myself to get band stacking and easy ham band switching, but I no longer need to bother!  I may still add front panel buttons for band up/band down functions, but the menu band changing function is fairly handy already.  It would be good to have a SPLIT function (in addition to A/B) and perhaps a limited number of programmable memories (10?). 

I like the way that you can select either ham bands or general coverage RX.  You go into the band change menu, and then hold the switch down for longer to toggle between modes. 

I have some minor suggestions for improvement.  The main thought would be to change the display of the RIT function to show the frequency offset rather than the absolute frequency (i.e. show -0.415 KHz or +0.001 kHz etc).  This reflects how most people think of incremental tuning.  Once you are done setting the RIT and exit the menu it would show the absolute frequency as normal on the display while the RIT still turned on.  The display should, however, continue to display "RIT"/  There is a whole other line above the frequency display to show function settings on RX.  Similarly you could show the keyer mode on the first line (e.g. STRAIGHT, IAMBICA, IAMBICB).

I love the way in which you have corrected the frequency display below 1MHz and opened up the RX to 1kHz to 100MHz.   A shorter press allows you to set the step function.   A long press on the dial switch gives you dial lock.  This works well.  I like the way the step speed increases when you turn the dial faster, but the dial no longer goes crazy, throwing you half a Megahertz away on outside the ham band.   Well done!

The function to monitor ADC levels could be very useful for those having issues with CW keying. My uBITx has always worked fine with both manual and paddle keys.  This suggests that the resistor tolerances are probably a bit narrow.  My resistor values may be closer tolerance than what others have received.   A check on the monitor function shows this to be the case.

I didn't find documentation on exactly how the ADC monitoring function works.  I believe it shows a continuous stream of readings on the port (0 to 1023) with 6 readings at a time.   However, I don't think you can exit from this function without turning off the rig?  This allows you to press dit, dah or the manual key to get a reading for the ADC value being received by the arduino.   This then allows the setting ranges to be adjusted.

If you are still fence sitting about a software upgrade you shouldn't be!   Upgrading the stock software is reasonably straight forward.   Let me tell you that if you have a stock uBITx, you should definitely be downloading this sketch and increasing functionality and ease of use.  It is a fine effort. 


Mike ZL1AXG


On 28/01/18 6:12 PM, Ian Lee wrote:
Dave

Thanks for your information.

My modified code (Ron's cw keying) does not use A7 for factory shipping users.
Until now, the firmware concept was applied without modification of the hardware.
I am going to end this project because I do not have any further improvements without hardware modifications.

When additional uBITX order arrives, I try to do a variety of fun H / W hacks.At that time, I will use A7 as Paddle and connect to S.Meter.

Ian KD8CEC

2018-01-28 6:14 GMT+09:00 Dave Bottom <ars.kd6az@...>:
Ian 

The v.30 with Ron’s CW Keying code does include adding the 4.7k pull-up at A7, as a modification to hardware.

I’m planning on adding both 4.7K chip resistors directly on the pads of the Raduino so there are no loose resistors to mount at the key jack(s).

Dave WI6R

Sent from my iPhone

On Jan 27, 2018, at 2:39 AM, Ian Lee <kd8cec@...> wrote:

I have not posted it on my blog separately since it is a test version. When the test is complete,  write a usage and post it.
I am writing for someone who is interested and test.  If I get an error report or a fix, I'll fix it and make it into github's 0.31 branch.

Here is a brief description of the change from 0.30.
improved CW Keying, Frequency Tune and CW performance according to users' requirements.
In particular, CW Keying applied ron's logic for use with original hardware. also made it possible to set the CW Key ADC range to reduce errors in CW.
ADC monitoring function is added to know the exact resistance and key contact status.
I thought that if you set your own ADC range using the measured values here, you would get an error. I need to test these things, so I leave this post.

removed all existing sources related to frequency tune. And i applied threshold, weight about speed, and steps. The problem of changing the frequency at the moment of catching the knob has probably disappeared. when the threshold has been exceeded, start frequency changing, i added some logic to prevent the thresholds from becoming unnatural.
If you want to fine-tune, slowly turn it and the threshold will be applied continuously and change very slowly.
The tune steps you can select now are 10, 20, 50, 100, 200, but you can change them in uBITX Manager 0.31 (now working)
You can change the step by pressing the function key for a long time. If you keep pressing it, Diallock will work.

The ham band movement applied at 0.28 was set to 0.30, so that region1 was set as the default.
Of course, you can change to the previous operation state by pressing the function key in the band select menu for a long time.
And like the 0.28 version, you can set up to 10 frequency bands in uBITX Manager to suit your country or your liking.

Please refer to below for the improvements and how to upload firmware and more detail.
The source and compiled firmware can be found in the release below link.
https://github.com/phdlee/ubitx

How to upload firmware and use version up to version 0.27
http://www.hamskey.com

--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Mike Woods
mhwoods@...




Re: uBITX woes, feeling disheartened. #ubitx

David Beal
 

Hi Cesar, 

I'm also following this thread which is similar to what I'm experiencing:  https://groups.io/g/BITX20/topic/no_tx/7733258?p=Created,,,20,1,20,0&jump=1 
--
Dave Beal
AE6RQ


Re: uBITX woes, feeling disheartened. #ubitx

Bob McMillan
 

Must have missed them. I look again
Thanks

Bob
W5rkm


Re: PiZeroW Controlling a uBitx

Diver Martin <diver.martin@...>
 

Arv, yeah, the susceptibility of the zeroW to the RF would probably be the hardest part.

I was discussing this with another friend, and another major issue came up:  Sourcing the damned things.  You can buy them onsie-twosie as a private party from the likes of adafruit/etc, but buying 100 for a build (or 1000 if one went to something like the current uBitx build volumes) is more difficult.  So either each person buys their own (Add $6 shipping to that $10), or you gotta deal with the logistics.  Meh.

Still an interesting idea though the horsepower that's available...  (Integrating the MCU off a teensy3.2 would be cheap & easy if it weren't for the $8 one pays for the bootloader from pjrc, but then it wouldn't be arduino / teensyduino compatible).

On Sun, Jan 28, 2018 at 10:02 PM, Arv Evans <arvid.evans@...> wrote:
Two problems that may affect use of a Pi-ZERO inside the uBITX.  First it will have
to be shielded to minimize radiation of spurious signals that might detract from 
typical BITX quiet background and high sensitivity.  Second would be the need to
"harden" Pi-ZERO ports so they will survive the high RF levels that exist inside the
case when transmitting.  Both fixes re possible but not something that a neophyte
would want to attempt.

Arv  K7HKL
_._


On Sun, Jan 28, 2018 at 10:54 PM, Diver Martin <diver.martin@...> wrote:
I need yet another project like I need a hole in my head! :)  The my top mod PCB is something I should get working first, but I may later try doing a simple rpizerow to teensy3.2 adapter or something.  Power consumption and boot-up time are two issues with the PiZeroW, but it sounds like RFI and the wireless getting 'zapped' are others.   Still something to consider down the road...

On Sun, Jan 28, 2018 at 2:03 PM, Mike Woods <mhwoods@...> wrote:
Martin

It seems like nobody has (yet) used the Pi Zero W.   Why don't you give it a go?  I suspect that it will be a noise generator as well as RF prone ... but worth a try!

Mike



On 28/01/18 7:21 PM, Diver Martin wrote:
Anyone thought about using a PiZeroW (or even a regular RPi) for controlling a uBitx?

I thought to myself, while pondering my design decisions, "Hey, a PiZeroW is $10.  A Teensy3.2 is $20..."  Looking quickly at the pinout, it has spi and i2c, and a few GPIO's.  I don't have any experience programming the raspberry pis, but adding an i2s audio dac (or two) could easily do DSP audio, spectrum display, etc... I have my RpiZeroW hooked up to a 3.5" TFT touchscreen display I got off amazon... (https://www.amazon.com/UCTRONICS-Display-Touch-Screen-Raspberry/dp/B073QGW2M6/)

Mostly just curious.  Doubt I'll change directions with my top mod PCB, but it certainly could be an interesting option (The RpiZeroW consumes ~250mA @ 5V as I recall)

--
Martin Held - AE7EU
http://ae7eu.com/
-------------------------------------------------------------------------------
If there aren't any questions, then what is there to learn?


--
Mike Woods
mhwoods@...




--
Martin Held - AE7EU
http://ae7eu.com/
-------------------------------------------------------------------------------
If there aren't any questions, then what is there to learn?





--
Martin Held - AE7EU
http://ae7eu.com/
-------------------------------------------------------------------------------
If there aren't any questions, then what is there to learn?


Re: uBITX Firmware (CEC) 0.30 released (Test version). #ubitx

M Garza <mgarza896@...>
 

I forgot to mention that it worked before the upgrade and is wired according to the hfsignals instructions/schematic.

Thanks again.

Marco - KG5PRT

On Mon, Jan 29, 2018 at 12:05 AM, M Garza <mgarza896@...> wrote:
Hello Ian,
I have just upgraded to v.30 and all the settings and fixes are much appreciated.  I have a problem, though.  I am unable to use the keyer.  It does nothing.  
Is there a hardware mod that needs to be performed to get it working again?

Thank you in advance,

Marco - KG5PRT

On Sun, Jan 28, 2018 at 3:03 PM, Mike Woods <mhwoods@...> wrote:
Ian

I commend you on your latest software Beta release (v0.30). This worked faultlessly for me, and I loved being able to adjust the step rate (I have it set on 10Hz now). 

The band stacking registers and band switching is fantastic.  I had intended modding the software myself to get band stacking and easy ham band switching, but I no longer need to bother!  I may still add front panel buttons for band up/band down functions, but the menu band changing function is fairly handy already.  It would be good to have a SPLIT function (in addition to A/B) and perhaps a limited number of programmable memories (10?). 

I like the way that you can select either ham bands or general coverage RX.  You go into the band change menu, and then hold the switch down for longer to toggle between modes. 

I have some minor suggestions for improvement.  The main thought would be to change the display of the RIT function to show the frequency offset rather than the absolute frequency (i.e. show -0.415 KHz or +0.001 kHz etc).  This reflects how most people think of incremental tuning.  Once you are done setting the RIT and exit the menu it would show the absolute frequency as normal on the display while the RIT still turned on.  The display should, however, continue to display "RIT"/  There is a whole other line above the frequency display to show function settings on RX.  Similarly you could show the keyer mode on the first line (e.g. STRAIGHT, IAMBICA, IAMBICB).

I love the way in which you have corrected the frequency display below 1MHz and opened up the RX to 1kHz to 100MHz.   A shorter press allows you to set the step function.   A long press on the dial switch gives you dial lock.  This works well.  I like the way the step speed increases when you turn the dial faster, but the dial no longer goes crazy, throwing you half a Megahertz away on outside the ham band.   Well done!

The function to monitor ADC levels could be very useful for those having issues with CW keying. My uBITx has always worked fine with both manual and paddle keys.  This suggests that the resistor tolerances are probably a bit narrow.  My resistor values may be closer tolerance than what others have received.   A check on the monitor function shows this to be the case.

I didn't find documentation on exactly how the ADC monitoring function works.  I believe it shows a continuous stream of readings on the port (0 to 1023) with 6 readings at a time.   However, I don't think you can exit from this function without turning off the rig?  This allows you to press dit, dah or the manual key to get a reading for the ADC value being received by the arduino.   This then allows the setting ranges to be adjusted.

If you are still fence sitting about a software upgrade you shouldn't be!   Upgrading the stock software is reasonably straight forward.   Let me tell you that if you have a stock uBITx, you should definitely be downloading this sketch and increasing functionality and ease of use.  It is a fine effort. 


Mike ZL1AXG


On 28/01/18 6:12 PM, Ian Lee wrote:
Dave

Thanks for your information.

My modified code (Ron's cw keying) does not use A7 for factory shipping users.
Until now, the firmware concept was applied without modification of the hardware.
I am going to end this project because I do not have any further improvements without hardware modifications.

When additional uBITX order arrives, I try to do a variety of fun H / W hacks.At that time, I will use A7 as Paddle and connect to S.Meter.

Ian KD8CEC

2018-01-28 6:14 GMT+09:00 Dave Bottom <ars.kd6az@...>:
Ian 

The v.30 with Ron’s CW Keying code does include adding the 4.7k pull-up at A7, as a modification to hardware.

I’m planning on adding both 4.7K chip resistors directly on the pads of the Raduino so there are no loose resistors to mount at the key jack(s).

Dave WI6R

Sent from my iPhone

On Jan 27, 2018, at 2:39 AM, Ian Lee <kd8cec@...> wrote:

I have not posted it on my blog separately since it is a test version. When the test is complete,  write a usage and post it.
I am writing for someone who is interested and test.  If I get an error report or a fix, I'll fix it and make it into github's 0.31 branch.

Here is a brief description of the change from 0.30.
improved CW Keying, Frequency Tune and CW performance according to users' requirements.
In particular, CW Keying applied ron's logic for use with original hardware. also made it possible to set the CW Key ADC range to reduce errors in CW.
ADC monitoring function is added to know the exact resistance and key contact status.
I thought that if you set your own ADC range using the measured values here, you would get an error. I need to test these things, so I leave this post.

removed all existing sources related to frequency tune. And i applied threshold, weight about speed, and steps. The problem of changing the frequency at the moment of catching the knob has probably disappeared. when the threshold has been exceeded, start frequency changing, i added some logic to prevent the thresholds from becoming unnatural.
If you want to fine-tune, slowly turn it and the threshold will be applied continuously and change very slowly.
The tune steps you can select now are 10, 20, 50, 100, 200, but you can change them in uBITX Manager 0.31 (now working)
You can change the step by pressing the function key for a long time. If you keep pressing it, Diallock will work.

The ham band movement applied at 0.28 was set to 0.30, so that region1 was set as the default.
Of course, you can change to the previous operation state by pressing the function key in the band select menu for a long time.
And like the 0.28 version, you can set up to 10 frequency bands in uBITX Manager to suit your country or your liking.

Please refer to below for the improvements and how to upload firmware and more detail.
The source and compiled firmware can be found in the release below link.
https://github.com/phdlee/ubitx

How to upload firmware and use version up to version 0.27
http://www.hamskey.com

--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Mike Woods
mhwoods@...




Re: uBITX Firmware (CEC) 0.30 released (Test version). #ubitx

M Garza <mgarza896@...>
 

Hello Ian,
I have just upgraded to v.30 and all the settings and fixes are much appreciated.  I have a problem, though.  I am unable to use the keyer.  It does nothing.  
Is there a hardware mod that needs to be performed to get it working again?

Thank you in advance,

Marco - KG5PRT

On Sun, Jan 28, 2018 at 3:03 PM, Mike Woods <mhwoods@...> wrote:
Ian

I commend you on your latest software Beta release (v0.30). This worked faultlessly for me, and I loved being able to adjust the step rate (I have it set on 10Hz now). 

The band stacking registers and band switching is fantastic.  I had intended modding the software myself to get band stacking and easy ham band switching, but I no longer need to bother!  I may still add front panel buttons for band up/band down functions, but the menu band changing function is fairly handy already.  It would be good to have a SPLIT function (in addition to A/B) and perhaps a limited number of programmable memories (10?). 

I like the way that you can select either ham bands or general coverage RX.  You go into the band change menu, and then hold the switch down for longer to toggle between modes. 

I have some minor suggestions for improvement.  The main thought would be to change the display of the RIT function to show the frequency offset rather than the absolute frequency (i.e. show -0.415 KHz or +0.001 kHz etc).  This reflects how most people think of incremental tuning.  Once you are done setting the RIT and exit the menu it would show the absolute frequency as normal on the display while the RIT still turned on.  The display should, however, continue to display "RIT"/  There is a whole other line above the frequency display to show function settings on RX.  Similarly you could show the keyer mode on the first line (e.g. STRAIGHT, IAMBICA, IAMBICB).

I love the way in which you have corrected the frequency display below 1MHz and opened up the RX to 1kHz to 100MHz.   A shorter press allows you to set the step function.   A long press on the dial switch gives you dial lock.  This works well.  I like the way the step speed increases when you turn the dial faster, but the dial no longer goes crazy, throwing you half a Megahertz away on outside the ham band.   Well done!

The function to monitor ADC levels could be very useful for those having issues with CW keying. My uBITx has always worked fine with both manual and paddle keys.  This suggests that the resistor tolerances are probably a bit narrow.  My resistor values may be closer tolerance than what others have received.   A check on the monitor function shows this to be the case.

I didn't find documentation on exactly how the ADC monitoring function works.  I believe it shows a continuous stream of readings on the port (0 to 1023) with 6 readings at a time.   However, I don't think you can exit from this function without turning off the rig?  This allows you to press dit, dah or the manual key to get a reading for the ADC value being received by the arduino.   This then allows the setting ranges to be adjusted.

If you are still fence sitting about a software upgrade you shouldn't be!   Upgrading the stock software is reasonably straight forward.   Let me tell you that if you have a stock uBITx, you should definitely be downloading this sketch and increasing functionality and ease of use.  It is a fine effort. 


Mike ZL1AXG


On 28/01/18 6:12 PM, Ian Lee wrote:
Dave

Thanks for your information.

My modified code (Ron's cw keying) does not use A7 for factory shipping users.
Until now, the firmware concept was applied without modification of the hardware.
I am going to end this project because I do not have any further improvements without hardware modifications.

When additional uBITX order arrives, I try to do a variety of fun H / W hacks.At that time, I will use A7 as Paddle and connect to S.Meter.

Ian KD8CEC

2018-01-28 6:14 GMT+09:00 Dave Bottom <ars.kd6az@...>:
Ian 

The v.30 with Ron’s CW Keying code does include adding the 4.7k pull-up at A7, as a modification to hardware.

I’m planning on adding both 4.7K chip resistors directly on the pads of the Raduino so there are no loose resistors to mount at the key jack(s).

Dave WI6R

Sent from my iPhone

On Jan 27, 2018, at 2:39 AM, Ian Lee <kd8cec@...> wrote:

I have not posted it on my blog separately since it is a test version. When the test is complete,  write a usage and post it.
I am writing for someone who is interested and test.  If I get an error report or a fix, I'll fix it and make it into github's 0.31 branch.

Here is a brief description of the change from 0.30.
improved CW Keying, Frequency Tune and CW performance according to users' requirements.
In particular, CW Keying applied ron's logic for use with original hardware. also made it possible to set the CW Key ADC range to reduce errors in CW.
ADC monitoring function is added to know the exact resistance and key contact status.
I thought that if you set your own ADC range using the measured values here, you would get an error. I need to test these things, so I leave this post.

removed all existing sources related to frequency tune. And i applied threshold, weight about speed, and steps. The problem of changing the frequency at the moment of catching the knob has probably disappeared. when the threshold has been exceeded, start frequency changing, i added some logic to prevent the thresholds from becoming unnatural.
If you want to fine-tune, slowly turn it and the threshold will be applied continuously and change very slowly.
The tune steps you can select now are 10, 20, 50, 100, 200, but you can change them in uBITX Manager 0.31 (now working)
You can change the step by pressing the function key for a long time. If you keep pressing it, Diallock will work.

The ham band movement applied at 0.28 was set to 0.30, so that region1 was set as the default.
Of course, you can change to the previous operation state by pressing the function key in the band select menu for a long time.
And like the 0.28 version, you can set up to 10 frequency bands in uBITX Manager to suit your country or your liking.

Please refer to below for the improvements and how to upload firmware and more detail.
The source and compiled firmware can be found in the release below link.
https://github.com/phdlee/ubitx

How to upload firmware and use version up to version 0.27
http://www.hamskey.com

--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)


--
Mike Woods
mhwoods@...



Re: PiZeroW Controlling a uBitx

Arv Evans
 

Two problems that may affect use of a Pi-ZERO inside the uBITX.  First it will have
to be shielded to minimize radiation of spurious signals that might detract from 
typical BITX quiet background and high sensitivity.  Second would be the need to
"harden" Pi-ZERO ports so they will survive the high RF levels that exist inside the
case when transmitting.  Both fixes re possible but not something that a neophyte
would want to attempt.

Arv  K7HKL
_._


On Sun, Jan 28, 2018 at 10:54 PM, Diver Martin <diver.martin@...> wrote:
I need yet another project like I need a hole in my head! :)  The my top mod PCB is something I should get working first, but I may later try doing a simple rpizerow to teensy3.2 adapter or something.  Power consumption and boot-up time are two issues with the PiZeroW, but it sounds like RFI and the wireless getting 'zapped' are others.   Still something to consider down the road...

On Sun, Jan 28, 2018 at 2:03 PM, Mike Woods <mhwoods@...> wrote:
Martin

It seems like nobody has (yet) used the Pi Zero W.   Why don't you give it a go?  I suspect that it will be a noise generator as well as RF prone ... but worth a try!

Mike



On 28/01/18 7:21 PM, Diver Martin wrote:
Anyone thought about using a PiZeroW (or even a regular RPi) for controlling a uBitx?

I thought to myself, while pondering my design decisions, "Hey, a PiZeroW is $10.  A Teensy3.2 is $20..."  Looking quickly at the pinout, it has spi and i2c, and a few GPIO's.  I don't have any experience programming the raspberry pis, but adding an i2s audio dac (or two) could easily do DSP audio, spectrum display, etc... I have my RpiZeroW hooked up to a 3.5" TFT touchscreen display I got off amazon... (https://www.amazon.com/UCTRONICS-Display-Touch-Screen-Raspberry/dp/B073QGW2M6/)

Mostly just curious.  Doubt I'll change directions with my top mod PCB, but it certainly could be an interesting option (The RpiZeroW consumes ~250mA @ 5V as I recall)

--
Martin Held - AE7EU
http://ae7eu.com/
-------------------------------------------------------------------------------
If there aren't any questions, then what is there to learn?


--
Mike Woods
mhwoods@...




--
Martin Held - AE7EU
http://ae7eu.com/
-------------------------------------------------------------------------------
If there aren't any questions, then what is there to learn?



Re: PiZeroW Controlling a uBitx

Diver Martin <diver.martin@...>
 

I need yet another project like I need a hole in my head! :)  The my top mod PCB is something I should get working first, but I may later try doing a simple rpizerow to teensy3.2 adapter or something.  Power consumption and boot-up time are two issues with the PiZeroW, but it sounds like RFI and the wireless getting 'zapped' are others.   Still something to consider down the road...

On Sun, Jan 28, 2018 at 2:03 PM, Mike Woods <mhwoods@...> wrote:
Martin

It seems like nobody has (yet) used the Pi Zero W.   Why don't you give it a go?  I suspect that it will be a noise generator as well as RF prone ... but worth a try!

Mike



On 28/01/18 7:21 PM, Diver Martin wrote:
Anyone thought about using a PiZeroW (or even a regular RPi) for controlling a uBitx?

I thought to myself, while pondering my design decisions, "Hey, a PiZeroW is $10.  A Teensy3.2 is $20..."  Looking quickly at the pinout, it has spi and i2c, and a few GPIO's.  I don't have any experience programming the raspberry pis, but adding an i2s audio dac (or two) could easily do DSP audio, spectrum display, etc... I have my RpiZeroW hooked up to a 3.5" TFT touchscreen display I got off amazon... (https://www.amazon.com/UCTRONICS-Display-Touch-Screen-Raspberry/dp/B073QGW2M6/)

Mostly just curious.  Doubt I'll change directions with my top mod PCB, but it certainly could be an interesting option (The RpiZeroW consumes ~250mA @ 5V as I recall)

--
Martin Held - AE7EU
http://ae7eu.com/
-------------------------------------------------------------------------------
If there aren't any questions, then what is there to learn?


--
Mike Woods
mhwoods@...




--
Martin Held - AE7EU
http://ae7eu.com/
-------------------------------------------------------------------------------
If there aren't any questions, then what is there to learn?


Re: IRF510 amplifier failures

Arv Evans
 

Tim AB0WR

No modulation involved.  The operation is as a switch between ON and almost
OFF.  Gain of the two BJTs makes it operate quickly and drop the output voltage
to the point where the current sensing resistor has less than the 0.65 threshold
voltage across its base-emitter junction.

I see where it does look like some of the CB-era AM modulators because it
causes a drop in voltage when current exceeds the base-emitter threshold.   

I'm still looking at the current limiter with an eye toward possibly adding another
MOSFET to get both polarity protection and current limiting.  Problem with fuses
for protection is that most do not operate fast enough.  There are specialty
Fast-Acting fuses  and Slow-Blow fuses but most hams do not have a ready stock
of these.

Arv
_._


On Sun, Jan 28, 2018 at 9:59 PM, Tim Gorman <tgorman2@...> wrote:
It would seem to me that this type of operation is actually AM
modulation of final. When you limit the current flow in an FET that is
very similar to plate modulation in a vacuum tube. It certainly can't
be good for the linearity of the amplifier since the operational curve
would no longer be linear but, instead, flat-topped at some value.

Why not just fuse the power lead? It would tell you immediately that
you have a problem.

tim ab0wr

On Sat, 27 Jan 2018 12:13:49 -0800
"Arv Evans" <arvid.evans@...> wrote:

> Hello
>
> Still thinking about IRF510 failures and ways to avoid making
> smoke.....
>
> It seems that there may be two ways to limit current in BITX RF PA
> stages that use the IRF510 device.  First would be to incorporate a
> current limiter in the positive voltage supply to the RF PA stage.
> Second might be to use current sensing in the RF PA supply line to
> cause a voltage drop in the MOSFET bias line(s). 
>
> In the first instance it should be possible to use another IRF510 or
> preferably a higher power, MOSFET as a control that limits voltage to
> the RF PA section if the current exceeds a preset value (usually this
> would be 2.0 to 3.0 amperes). 
>
> This circuit has not been built or tested by me (too cold in Idaho
> hamshack in winter). The MOSFET could be an IRF840, or similar.
> Option-B  potentially solves another problem, that of low level noise
> from powered RF PA stage during receive mode. 
>
> In the second instance we could get by with smaller control devices
> if we used current sensing in the RF PA power line to turn off bias
> to the IRF510 device(s). 
>
> This bias control circuit used by AC2CZ in his 50 watt IRF510 linear
> ( http://www.g0kla.com/scpa/SimpleCheapPA.php ).  You could probably
> do this using 2N3906 transistors.  I like the fact that it includes a
> warning light/LED.
>
> Arv  K7HKL
> _._






Re: SMD Group Build

Tim Gorman
 

Surfboards (digikey) are your friends. I use them all the time. Pretty
expensive but for single applications nothing beats them for using all
kinds of smt parts.

tim ab0wr

On Thu, 25 Jan 2018 16:49:51 -0500
"Ken KM4NFQ" <@KM4NFQ> wrote:

On Thu, Jan 25, 2018 at 12:03 AM, Ashhar Farhan <farhanbox@...>
wrote:

I use double side, plain copper clad. Then, with a sharp knife (i
use a glass cutter), i score off an island of 3x2 to 5x2 squares of
about 0.25inch to a side. I use all around for the ground plane,
and solder the 1206 betweeb the pads. The sot23 transistors are
soldered at a corner of three squares. If the ground planing ia
crucial, i drill a number of holes around the top ground plane and
solder small pieces of wire to connect to the Bottom ground

Hello Ashhar, VU2ESE,

I really like the technique you have described for working with SMDs.
It reminds me of Chuck Adam's (K7QO) MUPPET (Manhattan Ugly
Professional Placement Experimental Technique) Style Construction. I
have already used that style with PTH components. I can see how it
will also work very well with 1206's. The soldered wire connecting
the top and bottom of the board's ground planes is great. You must
use a breakout board for SOICs.

Regards,
Ken, KM4NFQ


Re: End whistling into the mic

AA9GG
 

JUST SAY NOOOOOO!!!!!!!!!!!!!   Rather than modulating your signal, why not just use a noise bridge to tune up your antenna WITH OUT TRANSMITTING!!!!
Check this out....  http://www.nd6t.com/antenna/Polite%20Tuner.htm


On Sat, Jan 27, 2018 at 5:48 AM, chris gress <Chrisg0wfh@...> wrote:
Built on back of a switch low power atu to the right chris

On 27 Jan 2018 11:45, "chris gress" <Chrisg0wfh@...> wrote:
You could always use this so you could have built in swr/rf out on your bitx the 51ohm resistors I use 2x 100 ohm 3watt I picked this up from the internet 

On 27 Jan 2018 09:32, "gw4akz via Groups.Io" <gw4akz=aol.com@groups.io> wrote:
On Thu, Jan 25, 2018 at 01:20 pm, David wrote:
Instead of whistling into the mic when using an antenna tuner on SSB, we could easily add a tone generator and switch to do that for us. Thoughts?
I have fitted a switchable -6db pad between the output of the pcb and the anttena socket. With the circuit switched in the worst case swr is about 1.65 to 1 with an open or short circuit, this prevents the finals from ever seeing a poor swr. tune is easily achived with the key down and reduced radiated power when tunning up. I use 2 watt carbon resistors 33 ohms in a t attenuator circuit. 2 in parrarlel to give 16.5 ohms which is close enough to the callculated value. I use a relay to switch this attenuator in and out.




--
Paul Mateer, AA9GG
Elan Engineering Corp.
www.elanengr.com
NAQCC 3123, SKCC 4628


Re: IRF510 amplifier failures

Tim Gorman
 

It would seem to me that this type of operation is actually AM
modulation of final. When you limit the current flow in an FET that is
very similar to plate modulation in a vacuum tube. It certainly can't
be good for the linearity of the amplifier since the operational curve
would no longer be linear but, instead, flat-topped at some value.

Why not just fuse the power lead? It would tell you immediately that
you have a problem.

tim ab0wr

On Sat, 27 Jan 2018 12:13:49 -0800
"Arv Evans" <arvid.evans@...> wrote:

Hello

Still thinking about IRF510 failures and ways to avoid making
smoke.....

It seems that there may be two ways to limit current in BITX RF PA
stages that use the IRF510 device.  First would be to incorporate a
current limiter in the positive voltage supply to the RF PA stage.
Second might be to use current sensing in the RF PA supply line to
cause a voltage drop in the MOSFET bias line(s). 

In the first instance it should be possible to use another IRF510 or
preferably a higher power, MOSFET as a control that limits voltage to
the RF PA section if the current exceeds a preset value (usually this
would be 2.0 to 3.0 amperes). 

This circuit has not been built or tested by me (too cold in Idaho
hamshack in winter). The MOSFET could be an IRF840, or similar.
Option-B  potentially solves another problem, that of low level noise
from powered RF PA stage during receive mode. 

In the second instance we could get by with smaller control devices
if we used current sensing in the RF PA power line to turn off bias
to the IRF510 device(s). 

This bias control circuit used by AC2CZ in his 50 watt IRF510 linear
( http://www.g0kla.com/scpa/SimpleCheapPA.php ).  You could probably
do this using 2N3906 transistors.  I like the fact that it includes a
warning light/LED.

Arv  K7HKL
_._


Re: TEST MESSAGE...Please Ignore

Mark Phillips
 

I'm a bit busy right now. Can I ignore it later? :)

On Sun, Jan 28, 2018 at 7:36 PM, Arv Evans <arvid.evans@...> wrote:
This is a test message by a moderator for testing addition of an informational footer to email replies.

Arv  K7HKL
_._



Re: uBITX woes, feeling disheartened. #ubitx

Michael Hagen
 

They are standard relays, look on eBay.

73's

Mike, WA6ISP


On 1/28/2018 7:58 PM, Bob McMillan wrote:
I had trouble with k3 relay not switching back to receive. Couldn’t find a replacement
Luckily re-solder seemed to solve the problem. I would like to find a replacement just in case.

Bob
W5rkm

-- 
Mike Hagen, WA6ISP
10917 Bryant Street
Yucaipa, Ca. 92399
(909) 918-0058
PayPal ID  "MotDog@..."
Mike@...


Re: I did it again.. i plugged the arduino pins on reverse

Mike Woods
 

I haven’t measured it ... but machine pin headers may work?  They are pretty low profile.

M


On Mon, 29 Jan 2018 at 5:03 PM, John Backo <jabac@...> wrote:
True. Raj.

But it is easy enough to cable the display.
This has been discussed before on the forum.

It means a little bit different way of mounting the rig.
And the benefit of a removable nano outweighs
the inconvenience, I think.

john
AD5YE




Re: I did it again.. i plugged the arduino pins on reverse

John Backo
 

True. Raj.

But it is easy enough to cable the display.
This has been discussed before on the forum.

It means a little bit different way of mounting the rig.
And the benefit of a removable nano outweighs
the inconvenience, I think.

john
AD5YE