Date   
Re: KD8CEC and S-Meter

Evan Hand
 

Vince,

There are 2 versions of the CEC software for each of the display types.  The difference is one uses a seperate I2C connected Nano to add functionality.  The other uses the spare input pin on the Nano to connect the S-Meter. Read the FileNameInfo.txt file to insure that you use the correct one.

http://www.hamskey.com/2019/04/release-cec-firmware-v1200-for-ubitx.html


The added hardware sensor for the direct connected S-Meter is in this article on the HamsKey web page:
http://www.hamskey.com/2018/06/creating-simple-s-meter-sensor-for.html

If you add a second Nano then this is the article on how to connect it:
http://www.hamskey.com/2018/07/standalone-signal-analyzer-i2c-type.html

If you go the rout of adding the I2C connected Nano, then there are other functions that can be added beyond the S-Meter.  As Werner suggested.

So the choice is yours.  That is the beauty of the uBitx and the great additions that Dr. Lee (KD8CEC) have provided.

73
Evan
AC9TU  

Re: Hi from Adrien F4IJA

Woody
 

Ran the output into a 50 ohm dummy load and measured the voltage with a 200 MHz 'scope.
Woody

On 9/23/2019 23:18, Mark - N7EKU wrote:
Hi Woody,

Thank you for the data!

How were you measuring and calculating the peak power?

73,


Mark
_._,_._,

--

Re: Stuck at LSB A:7.149.950

Horace@...
 

Removed from casing, clean, air dust, inspect.
All looks ok still same problem VFO stucked

How to reset the Adruino?

Thanks

Re: KD8CEC and S-Meter

Werner de Vos
 

Another idea is to install the extra nano (with s meter firmware) and install the _s firmware on the randiuno. The S meter also works a bit faster then. 

Re: KD8CEC and S-Meter

V Zecchinelli
 

I am using Nextion so using I2C.  I should have mentioned Nextion in original email.
Thanks,
Vince


On 9/24/2019 9:19 AM, Adrien F4IJA wrote:
If you're not on I2C, you need to comment this line because you want to use A7 to work with it.
--
73's
Adrien F4IJA
https://www.qrz.com/db/F4IJA

Re: KD8CEC and S-Meter

V Zecchinelli
 

Thanks Evan.  No, I had not seen this.  I think I found it here http://www.nd6t.com/bitx/S%20meter.htm.  A2 is A2 on the Nano or Pin 2 on the Analog Raduino connector which seems to be Pin 3 for A2 on the Nano?
Vince


On 9/24/2019 9:26 AM, Evan Hand wrote:
Just to confirm that you did connect the diode, cap and resistor per the KD8CEC directions to measure the audio output at the high connection of the volume control?

FWIW
73
Evan
AC9TU

Re: uBITX full design

Lawrence Galea
 

Farhan
I have the μbitx 3 and was thinking aloud about separate filters for each band
Thanks and regards
Lawrence

On Tue, Sep 24, 2019 at 4:10 AM Ashhar Farhan <farhanbox@...> wrote:
If you are thinking of a bank if band pass filters, then you dont need the complexity and performance hit of the double conversion  ubitx. Go for single conversion like the bitx40 or bitx20. The performance is kuch superior. 

On Tue 24 Sep, 2019, 1:29 AM Lawrence Galea, <9h1avlaw@...> wrote:
Thanks all for your feedback
Regards
Lawrence

On Mon, Sep 23, 2019 at 8:35 PM Jerry Gaffke via Groups.Io <jgaffke=yahoo.com@groups.io> wrote:
If building a new board for external low pass filters, 
could spend an extra $0.50 on a processor to interpret serial commands from the Raduino.
If wires kept short could use the i2c bus, pin count impact on the Raduino is a minus 3
since this frees up the TXA,TXB,TXC pins.
And perhaps include a tandem match style SWR detector out there, 
communicates back to the Raduino over that same serial bus.

None of the communications out to this LPF board need speed,
this LPF board is a better choice for i2c than the display.

Not that I feel any real need for 10 LPF's.  
The 4 we have on the uBitx adequately cover the WARC bands.
Putting the corner frequencies closer to the top edge of each band
would allow better attenuation of harmonics, but in some jurisdictions at least
the v5 uBitx meets regulatory requirements.
Sufficient in my book for a QRP rig.
Actually, 20/40/80m is sufficient in my book for an $129 SSB transceiver.

There were several reports in this forum of Raduino clones being built
that had more IO pins.  Moving to an Arm blue pill would seem ideal
for a Raduino upgrade.  W3JDR got most of the way there:
    https://groups.io/g/BITX20/topic/19284407

I'd much prefer something like that for getting extra pins for tasks where
execution time is a consideration, serial access over i2c is awfully slow.

If doing a Raduino clone, address these issues of the current Raduino:
    No reverse polarity protection for the 12v supply
    No protection for the IO pins that go off board, please add 100 or 1000 ohm series resistors.
    Avoid having Raduino oscillators create birdies in the receiver
    Perhaps improve si5351 drive power to 7dBm,  have optional second si5351 to avoid crosstalk?
Might be a good project for some engineering student.
Jonathan, you still out there?

Jerry, KE7ER

On Mon, Sep 23, 2019 at 10:05 AM, ajparent1/KB1GMX wrote:
On Mon, Sep 23, 2019 at 08:34 AM, Lawrence Galea wrote:
Farhan.
Did you ever think of making available a raduino with switching for every one of the 10 HF bands so that one could use external BPFs instead of the ones on the board or perhaps a program for those who want to change the original software to do so?
Or is there any programmer on this list who is willing to do it?
Thanks to all
Likely no as its too great a change to the Raduino and the ubitx.

The existing version is at best good for 8 bands if one uses TXA,TXB,TXC as 
a binary band select along with an external decoder chip like 74138 (3-8 decode).

If one is willing a ground up build and a improved raduino-like approach would be doable.
The trick with the Nano is using a I2C display to free up pins and readjusting what pins are
used where.

Allison

Re: uBITX rotary enconder

Jack, W8TEE
 

Agree, and I have some interesting things I want to try with the 4.0 Teensy. For a while, JackAl used a software timer to track the rate at which the user was "spinning" the frequency knob. If the rate when above some user-defined threshold, we upper the increment factor by 10x. It worked fine, but seemed awkward to us. Because we use a touchscreen with the JackAl, we just put a "floating" cursor above the current frequency (shown here above the '3' digit) and the user can tap the '<' or '>' to move the

Inline image

frequency increment value. Not the best solution, perhaps, but it works. Plus, if you don't like it, you have the source code to change it if you want.

Jack, W8TEE


On Tuesday, September 24, 2019, 6:26:37 AM EDT, John Scherer <jrsphoto@...> wrote:


Hey Jack!  Easier?  Sure, ok.  But its not always about what easy, is it.  If it were, we would just buy all of our ham gear and be done with it.  That being said, whats mentioned above isn't that difficult.  I used and attiny85 that I programmed with the ArduinoIDE.  Works like a champ.  The one thing I would love to add is, when I change the step size in the uBitx, I would like to have the radio change the divisor on the fly.  For 10 Hz step, divide by 2, for the others by 4.  The goal would be for about 2.4 kHz span per one knob revolution when 10 Hz is selected, and about 12 kHz when 100 Hz is selected.

My reasons for going to a higher PPR optical encoder over the mechanical encoder that most use was all about the feel.  Most optical encoders have bearings and makes for very smooth operation.  The encoder in my uBitx is 128ppr and the Nano just isn't up to that task.  It could likely be made to work but I'm no expert with the code or ISR's.  I also have the BITeensio board and I can tell you that with its Teensy 3.6 processor and  a few simple mods to their encoder routines, I was able to read my 1024 ppr encoders (overkill for sure) as fast as I could spin it, without missing a beat.  Point being, we really need a faster processor in the raduino, something like the Teensy 4 would be pretty interesting.  The Teensy 4 could open the door for having some fun with digital audio filters, better spectrum display, etc.

--
Jack, W8TEE

Re: KD8CEC and S-Meter

Evan Hand
 

Just to confirm that you did connect the diode, cap and resistor per the KD8CEC directions to measure the audio output at the high connection of the volume control?

FWIW
73
Evan
AC9TU

Re: KD8CEC and S-Meter

Adrien F4IJA <adrien.grelet@...>
 

If you're not on I2C, you need to comment this line because you want to use A7 to work with it.
--
73's
Adrien F4IJA
https://www.qrz.com/db/F4IJA

KD8CEC and S-Meter

V Zecchinelli
 

Good Morning,

I am having difficulty activating the S Meter.  I have it checked in Memory Manager V1.11 and have tried several different number configurations along with S Meter box checked and nothing shows on S Meter.
Memory Manager = V1.11
KD6CEC = V1.2
UbitX = V5

Am I missing something anywhere?  UbitX.h shows "//Select betwen Analog S-Meter and DSP (I2C) Meter
#define USE_I2CSMETER"

Thanks,
Vince

Re: uBITX rotary enconder

Sascha Bohnet | DL5SMB
 

I also installed one of these famous 100ppr ebay encoders.

The speed of the Nano is a restraint for sure, but in my case it was totally sufficient.

The probem I faced was the programming of the encoder function. It was written for the low-resolution mechanical encoders,
not for the faster optical ones. I just replaced two commands ("millis" to "micros") in the KD8CEC's source code and my encoder worked.

https://groups.io/g/BITX20/message/71360

Re: uBITX rotary enconder

John Scherer
 

Hey Jack!  Easier?  Sure, ok.  But its not always about what easy, is it.  If it were, we would just buy all of our ham gear and be done with it.  That being said, whats mentioned above isn't that difficult.  I used and attiny85 that I programmed with the ArduinoIDE.  Works like a champ.  The one thing I would love to add is, when I change the step size in the uBitx, I would like to have the radio change the divisor on the fly.  For 10 Hz step, divide by 2, for the others by 4.  The goal would be for about 2.4 kHz span per one knob revolution when 10 Hz is selected, and about 12 kHz when 100 Hz is selected.

My reasons for going to a higher PPR optical encoder over the mechanical encoder that most use was all about the feel.  Most optical encoders have bearings and makes for very smooth operation.  The encoder in my uBitx is 128ppr and the Nano just isn't up to that task.  It could likely be made to work but I'm no expert with the code or ISR's.  I also have the BITeensio board and I can tell you that with its Teensy 3.6 processor and  a few simple mods to their encoder routines, I was able to read my 1024 ppr encoders (overkill for sure) as fast as I could spin it, without missing a beat.  Point being, we really need a faster processor in the raduino, something like the Teensy 4 would be pretty interesting.  The Teensy 4 could open the door for having some fun with digital audio filters, better spectrum display, etc.

Re: uBITX rotary enconder

Jack, W8TEE
 

Wouldn't it just be easier (and less expensive) to buy an encoder with a lower ppr? Mouser sells good quality Bourns 20ppr encoders for under $2.


Jack, W8TEE

On Monday, September 23, 2019, 11:07:33 PM EDT, John Scherer <jrsphoto@...> wrote:


I've seen that code Guido, but there is more to that code.  For others coming here and seeing the link to the code above.  Please see this link for more info on how to implement it. But basicly, you program that code into a small microprocessor, something like a ATTiny85, though others even use a Nano.  You then connect you high-pulse count encoder to the processor, and it outputs a divide/N signal that you then feed to yourRaduinos encoder inputs:

test2

--
Jack, W8TEE

Re: uBITX rotary enconder

John Scherer
 

I've seen that code Guido, but there is more to that code.  For others coming here and seeing the link to the code above.  Please see this link for more info on how to implement it. But basicly, you program that code into a small microprocessor, something like a ATTiny85, though others even use a Nano.  You then connect you high-pulse count encoder to the processor, and it outputs a divide/N signal that you then feed to yourRaduinos encoder inputs:

test2

Re: uBITX full design

Ashhar Farhan
 

If you are thinking of a bank if band pass filters, then you dont need the complexity and performance hit of the double conversion  ubitx. Go for single conversion like the bitx40 or bitx20. The performance is kuch superior. 


On Tue 24 Sep, 2019, 1:29 AM Lawrence Galea, <9h1avlaw@...> wrote:
Thanks all for your feedback
Regards
Lawrence

On Mon, Sep 23, 2019 at 8:35 PM Jerry Gaffke via Groups.Io <jgaffke=yahoo.com@groups.io> wrote:
If building a new board for external low pass filters, 
could spend an extra $0.50 on a processor to interpret serial commands from the Raduino.
If wires kept short could use the i2c bus, pin count impact on the Raduino is a minus 3
since this frees up the TXA,TXB,TXC pins.
And perhaps include a tandem match style SWR detector out there, 
communicates back to the Raduino over that same serial bus.

None of the communications out to this LPF board need speed,
this LPF board is a better choice for i2c than the display.

Not that I feel any real need for 10 LPF's.  
The 4 we have on the uBitx adequately cover the WARC bands.
Putting the corner frequencies closer to the top edge of each band
would allow better attenuation of harmonics, but in some jurisdictions at least
the v5 uBitx meets regulatory requirements.
Sufficient in my book for a QRP rig.
Actually, 20/40/80m is sufficient in my book for an $129 SSB transceiver.

There were several reports in this forum of Raduino clones being built
that had more IO pins.  Moving to an Arm blue pill would seem ideal
for a Raduino upgrade.  W3JDR got most of the way there:
    https://groups.io/g/BITX20/topic/19284407

I'd much prefer something like that for getting extra pins for tasks where
execution time is a consideration, serial access over i2c is awfully slow.

If doing a Raduino clone, address these issues of the current Raduino:
    No reverse polarity protection for the 12v supply
    No protection for the IO pins that go off board, please add 100 or 1000 ohm series resistors.
    Avoid having Raduino oscillators create birdies in the receiver
    Perhaps improve si5351 drive power to 7dBm,  have optional second si5351 to avoid crosstalk?
Might be a good project for some engineering student.
Jonathan, you still out there?

Jerry, KE7ER

On Mon, Sep 23, 2019 at 10:05 AM, ajparent1/KB1GMX wrote:
On Mon, Sep 23, 2019 at 08:34 AM, Lawrence Galea wrote:
Farhan.
Did you ever think of making available a raduino with switching for every one of the 10 HF bands so that one could use external BPFs instead of the ones on the board or perhaps a program for those who want to change the original software to do so?
Or is there any programmer on this list who is willing to do it?
Thanks to all
Likely no as its too great a change to the Raduino and the ubitx.

The existing version is at best good for 8 bands if one uses TXA,TXB,TXC as 
a binary band select along with an external decoder chip like 74138 (3-8 decode).

If one is willing a ground up build and a improved raduino-like approach would be doable.
The trick with the Nano is using a I2C display to free up pins and readjusting what pins are
used where.

Allison

Re: WTB 680nF Inductors #parts

 

Hi Curt,

Thank you for the information.  It is good to hear more about fixing the mixer spurs.

My harmonic spurious are also good, using Alison's relay mod on the wiki and the original relays.

73,


Mark.

Re: Hi from Adrien F4IJA

 

Hi Woody,

Thank you for the data!

How were you measuring and calculating the peak power?

73,


Mark

Re: WTB 680nF Inductors #parts

Curt
 

Mark

I am thinking that the impact of substituting 680 nH shielded inductors for the toroids on the 45 MHz can be checked by monitoring a 28 MHz beacon (if you are where you can hear one) or by measuring SSB transmit output on an upper band.  I have some shielded inductors to try, but not yet installed.  Yes I am reading Raj that these are a good thing to reduce leakage that may cause more than one malady, and maybe with Axicom relays in might mitigate these mixer spurious. 

I did not find any improvement using the LC filter that was recommended, without other fixes for mixer spurious.  I sense they may be a small impact, but of course part of the v5 fix. 

I did try a second 45 MHz crystal filter - and this wrecked my low band CW transmit output.  Perhaps installing the shielded inductors may allow the second xtal filter to work, a path I plan to try. 

Meanwhile my harmonic spurious are good, using Gordan's board. 

Curt

Re: USB Problems Continue

Evan Hand
 

I went this route, and does allow you to go back, however transferring to the new Nano, you lose the calibration data that is stored in the eeprom on the Nano.  You will need to recalibrate when starting with a fresh Nano.

FWIW
73
Evan
AC9TU