Date   

Re: I2C Display code

Paul Galburt - K2AYZ
 

Here is the latest version. This is a complete operating system for the uBitx radio, optimized for use with an I2C-based display. This was developed by W0EB, N5IB and W2CTX. It is intended for use with their RadI2Cino board, a replacement for the Raduino that is wired for I2C display interface.

You can find more information at this link.

73,

Paul


Re: BITX QSO Afternoon/Evening, Sunday, April 8, 3PM & 7PM Local Time, 7277 kHz in North America, 7177 kHz elsewhere.

W0PWE
 

I will be operating Bitx mobile in WI and IA with the help of small amp at about 50 watts. 7.277 is outside the BW my Hamstick is tuned for but I will give it a shot. I will probably only be on for the 3pm session so I'm hoping some close in stations (WI,IL,MN,IA,MI) will be participating.
73, Jerry - W0PWE/M


Re: BITX QSO Afternoon/Evening, Sunday, April 8, 3PM & 7PM Local Time, 7277 kHz in North America, 7177 kHz elsewhere.

John P
 

I'm probably not going to be able to be on for the afternoon session, but should be on this evening! That means conditions should be fantastic this afternoon! LOL!

--
John - WA2FZW


Re: uBitx just started transmitting a loud hum #ubitx-help

 

Tim,

In uBitx the TDA2822 is always powered.

Raj

At 08-04-18, you wrote:

Check to see if either the tda2822 and/or Q70 still has power on
transmit. If they do then you need to start looking at where the power
leakage is occurring.


Re: uBitx just started transmitting a loud hum #ubitx-help

Tim Gorman
 

If you are hearing yourself in your headphones then the most likely
culprit is crosstalk between the mic amp and the receive audio circuit
while the audio circuit is still energized.

Check to see if either the tda2822 and/or Q70 still has power on
transmit. If they do then you need to start looking at where the power
leakage is occurring.

You might also unplug your headphones while transmitting to another ham
and see if that removes the hum and noise. If it does its another
indicator of problems in the audio circuit.

tim ab0wr

On Sat, 07 Apr 2018 23:05:00 -0700
"James" <james.manion@gmail.com> wrote:

Hi all,

I have had a few issues with my ubitx since it arrived a month ago.

Initially it worked well although I had the loud pop on SSB transmit,
and I could also hear my own voice through headphones on transmit
(which I assumed was normal for the radio). After about an hour, of
receive and a few short transmissions on 40m, the TDA2822 caught fire
(yes actual flames). I blew out the fire, and replaced it with an lm
386 which was working well. Suprisingly R75 was also damaged so I
replaced it. I wonder if R75 damage was coincidental or related to
the mode of failure of the TDA2822. I didn't notice any damage to R75
prior to the failure of the TDA2822.

After another few hours of good use without anyobvious problems
(could still hear my voice through headphones on transmit) I
encountered a problem on transmit. Mid transmission, I could hear a
loud tone/hum/interference though my headphones, which was also being
transmitted according to the ham I was in QSO with. It is still
receiving fine, but every time I key the mic, loud tone/noise both
through the headphones and over the air.

Hooked up to dummy load:
I am still making 10w output power on 40m.
Same sound and tone when trying to transmit on 20m.
I have changed back to a replacement tda2822 - loud sound still
present.

Tx/Rx power is switching correctly at K1.
K3 appears to be working correctly - M1-M2 correctly shows infinite
ohms on transmit when probed with multimeter.

Probing with an oscilloscope, the collector of Q6 shows a saw tooth
wave form with freq around 50hz which appears to match what I can
hear. Power supply has small amount of 50hz ripple at 11.8V.

I'm really scratching my head about where this noise could possibly
be coming from, and I'm running out if ideas on how to troubleshoot
any further! Any thoughts would be greatly appreciated as I'm sure it
must be something simple, since the radio was working well prior to
developing the fault on transmit. Receive is still great.


Re: Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

Hidehiko Komachi - JA9MAT
 

Hi John,
I tried the AGC circuit you introduced as used in the pre-production uBitx. Yes! The 2N7002 is not needed when I add the S-Meter function. So I made the circuit except for 2N7002 and also using 10K-Pot for adjusting the level. And also I removed R75 from pin6 to GND resister. Then it works well with S-Meter even AGC function. I don't know why this circuit works as an AGC. Your firmware makes something about AGC?

Thanks again!

Hidehiko ja9mat


Re: RadioKits.in Case #ubitx

lou_w2row
 

Thanks to Ken VE3KCY, I did manage to fit the tuning knob. The "secret" is to pry the cap off the front of the knob which exposes the adjustment screw unerneath. The cap on mine fit so well that it was not obvious at first that it was removable. 

73,  Lou  W2ROW


Re: I2C Display code

Tim Gorman
 

It must be pretty common code.

Here is where I found it.

arduino-info.wikispaces.com/LCD-Blue-I2C

tim ab0wr


On Sat, 7 Apr 2018 23:20:13 -0500
"K9HZ" <bill@wjschmidt.com> wrote:

Here is W0EBs code and it has the I2C calls for that type of display
already complete...


Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ
PJ2/K9HZ

Owner - Operator
Big Signal Ranch – K9ZC
Staunton, Illinois

Owner – Operator
Villa Grand Piton – J68HZ
Soufriere, St. Lucia W.I.
Rent it: www.VillaGrandPiton.com
Like us on Facebook!

Moderator – North American QRO Yahoo Group.

email: bill@wjschmidt.com





---
This email has been checked for viruses by AVG.
http://www.avg.com



Re: POP fix

Tim Gorman
 

Ahhhh!

I didn't use that pop fix. I should have read closer!

The message was about receive mode and mic leakage.

Thanks for the correction.

tim ab0wr

On Sat, 07 Apr 2018 21:15:36 -0700
"Jerry Gaffke via Groups.Io" <jgaffke=yahoo.com@groups.io> wrote:

Tim wrote:

If there is no voltage applied to Q6 during transmit how much
microphone signal is going to be conducted through Q6? 
There's definitely power to Q6 during transmit.
I assume you mean during receive.
But with the VA7AT pop fix, Q6 is always powered.

 
From near the bottom of   http://ubitx.net/fix-audio-pop/
under section  Fifteen Component Fix:

"This circuit rewires the preamplifiers to be permanently powered and
inserts serial gating in each of the inputs, controlled directly from
the TX and RX power busses."

So Q6 is always powered up.

Jerry

On Sat, Apr 7, 2018 at 08:58 pm, Tim Gorman wrote:


If there is no voltage applied to Q6 during transmit how much
microphone signal is going to be conducted through Q6?


Re: #bitx40 Help needed with compiler error #bitx40

Allard PE1NWL
 

Keith,

The PinChangeInterrupt library is normally not installed by default. You
have to add it to your IDE by yourself. You only have to install the
library one time, once it is installed it will be kept on your pc.

  • in your IDE menu, go to 'sketch' => 'include library' => 'manage libraries'.
  • The Library Manager will be opened.
  • Wait for some time to collect all library information.
  • When it is ready: In the search box, enter "PinChangeInterrupt"
  • The Library Manager will show some libraries.
  • One of them is named "PinChangeInterrupt by Nico Hood".
  • Click on this library, and press the "install" button.
  • It takes only few seconds to install the library.
  • When installation is finished, press the "close" button.
After this you should be able to compile the Raduino sketch without error.

73 Allard PE1NWL


Re: uBitx just started transmitting a loud hum #ubitx-help

 

Check your grounds! Could be a loose contact to ground. Tighten everything.

Raj

At 08-04-18, you wrote:
Hi all,

I have had a few issues with my ubitx since it arrived a month ago.

Initially it worked well although I had the loud pop on SSB transmit, and I could also hear my own voice through headphones on transmit (which I assumed was normal for the radio).
After about an hour, of receive and a few short transmissions on 40m, the TDA2822 caught fire (yes actual flames). I blew out the fire, and replaced it with an lm 386 which was working well. Suprisingly R75 was also damaged so I replaced it. I wonder if R75 damage was coincidental or related to the mode of failure of the TDA2822. I didn't notice any damage to R75 prior to the failure of the TDA2822.

After another few hours of good use without anyobvious problems (could still hear my voice through headphones on transmit) I encountered a problem on transmit. Mid transmission, I could hear a loud tone/hum/interference though my headphones, which was also being transmitted according to the ham I was in QSO with.
It is still receiving fine, but every time I key the mic, loud tone/noise both through the headphones and over the air.

Hooked up to dummy load:
I am still making 10w output power on 40m.
Same sound and tone when trying to transmit on 20m.
I have changed back to a replacement tda2822 - loud sound still present.

Tx/Rx power is switching correctly at K1.
K3 appears to be working correctly - M1-M2 correctly shows infinite ohms on transmit when probed with multimeter.

Probing with an oscilloscope, the collector of Q6 shows a saw tooth wave form with freq around 50hz which appears to match what I can hear.
Power supply has small amount of 50hz ripple at 11.8V.

I'm really scratching my head about where this noise could possibly be coming from, and I'm running out if ideas on how to troubleshoot any further!
Any thoughts would be greatly appreciated as I'm sure it must be something simple, since the radio was working well prior to developing the fault on transmit.


uBitx just started transmitting a loud hum #ubitx-help

James
 

Hi all,

I have had a few issues with my ubitx since it arrived a month ago.

Initially it worked well although I had the loud pop on SSB transmit, and I could also hear my own voice through headphones on transmit (which I assumed was normal for the radio).
After about an hour, of receive and a few short transmissions on 40m, the TDA2822 caught fire (yes actual flames). I blew out the fire, and replaced it with an lm 386 which was working well. Suprisingly R75 was also damaged so I replaced it. I wonder if R75 damage was coincidental or related to the mode of failure of the TDA2822. I didn't notice any damage to R75 prior to the failure of the TDA2822.

After another few hours of good use without anyobvious problems (could still hear my voice through headphones on transmit) I encountered a problem on transmit. Mid transmission, I could hear a loud tone/hum/interference though my headphones, which was also being transmitted according to the ham I was in QSO with.
It is still receiving fine, but every time I key the mic, loud tone/noise both through the headphones and over the air.

Hooked up to dummy load:
I am still making 10w output power on 40m.
Same sound and tone when trying to transmit on 20m.
I have changed back to a replacement tda2822 - loud sound still present.

Tx/Rx power is switching correctly at K1.
K3 appears to be working correctly - M1-M2 correctly shows infinite ohms on transmit when probed with multimeter.

Probing with an oscilloscope, the collector of Q6 shows a saw tooth wave form with freq around 50hz which appears to match what I can hear.
Power supply has small amount of 50hz ripple at 11.8V.

I'm really scratching my head about where this noise could possibly be coming from, and I'm running out if ideas on how to troubleshoot any further!
Any thoughts would be greatly appreciated as I'm sure it must be something simple, since the radio was working well prior to developing the fault on transmit.
Receive is still great.


Re: Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

K9HZ <bill@...>
 

To get my I2C display to work I did the following TWO things in Ian’s version 1.07 code:

 

1.        Change Display models in “ubitx_20” :

 

From this:

 

#define UBITX_DISPLAY_LCD1602P      //LCD mounted on unmodified uBITX

//#define UBITX_DISPLAY_LCD1602I    //I2C type 16 x 02 LCD

//#define UBITX_DISPLAY_LCD2404P    //24 x 04 LCD

//#define UBITX_DISPLAY_LCD2404I    //I2C type 24 x 04 LCD

 

To this:

 

//#define UBITX_DISPLAY_LCD1602P    //LCD mounted on unmodified uBITX

#define UBITX_DISPLAY_LCD1602I        //I2C type 16 x 02 LCD

//#define UBITX_DISPLAY_LCD2404P    //24 x 04 LCD

//#define UBITX_DISPLAY_LCD2404I    //I2C type 24 x 04 LCD

 

2.       Update Ian’s code to use the I2C libraries in “ubitx_lcd_1602i” :

 

From this:

 

#include <LiquidCrystal.h>

LiquidCrystal lcd(8,9,10,11,12,13);

 

To this:

 

#include <LiquidCrystal_I2C.h>

LiquidCrystal_I2C lcd(0x3F, 2, 1, 0, 4, 5, 6, 7, 3, POSITIVE);  //

 

JUST MAKE SURE THE ADDRESS IS CORRECT… in my case the add-on board on the back of the display is set to address “3F”.  You can use the scanner to find the correct address.

 

3.       Boom.  Works.

 

 

 

 

Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ

 

Owner - Operator

Big Signal Ranch – K9ZC

Staunton, Illinois

 

Owner – Operator

Villa Grand Piton – J68HZ

Soufriere, St. Lucia W.I.

Rent it: www.VillaGrandPiton.com

Like us on Facebook! facebook icon

 

Moderator – North American QRO Yahoo Group.

 

email:  bill@...

 

 

From: BITX20@groups.io [mailto:BITX20@groups.io] On Behalf Of Jerry Gaffke via Groups.Io
Sent: Saturday, April 7, 2018 11:57 PM
To: BITX20@groups.io
Subject: Re: [BITX20] Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

 

I'm seeing a bunch of different LiquidCrystal_I2C libraries out there.
And they take different arguments when getting initialized.

Most example programs on the web look like this, with three args:
    https://github.com/fdebrabander/Arduino-LiquidCrystal-I2C-library/blob/master/examples/HelloWorld/HelloWorld.ino
First arg is the i2c address, then the number of columns,  then the number of rows.

This from the same github account shows 4 args, the last arg being charsize, which is apparently optional. 
    https://github.com/fdebrabander/Arduino-LiquidCrystal-I2C-library/blob/master/LiquidCrystal_I2C.cpp

The one described here looks closer to what you got, takes 8 args, more than I want to bother giving it:
    http://forum.arduino.cc/index.php?topic=128635.0
Looks like we are giving it a full set of parallel pins, should not be needed when talking to an i2c display.
The 0 is probably to define a "select" pin, which if 0 probably means the display is always selected.
This looks really silly, I'd go find another library.

Jerry

On Sat, Apr 7, 2018 at 09:13 pm, Tim Gorman wrote:

Jerry,

I assume the 0 is to initially set the lcd to instruction mode so it
can be cleared or whatever. It would then be set high by the program
when it needs to write a character.

I'm not an Arduino programmer nor a C++ programmer. But I do find this
"constructor" in the LiquidCrystal.h file:

LiquidCrystal_I2C(uint8_t lcd_Addr, uint8_t En, uint8_t Rw, uint8_t Rs,
uint8_t d4, uint8_t d5, uint8_t d6, uint8_t d7,
uint8_t backlighPin, t_backlighPol pol);

I assume this has something to do with setting up the program to
properly handle the lcd.

tim ab0wr


Virus-free. www.avg.com


Re: Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

Jerry Gaffke
 

I'm seeing a bunch of different LiquidCrystal_I2C libraries out there.
And they take different arguments when getting initialized.

Most example programs on the web look like this, with three args:
    https://github.com/fdebrabander/Arduino-LiquidCrystal-I2C-library/blob/master/examples/HelloWorld/HelloWorld.ino
First arg is the i2c address, then the number of columns,  then the number of rows.

This from the same github account shows 4 args, the last arg being charsize, which is apparently optional. 
    https://github.com/fdebrabander/Arduino-LiquidCrystal-I2C-library/blob/master/LiquidCrystal_I2C.cpp

The one described here looks closer to what you got, takes 8 args, more than I want to bother giving it:
    http://forum.arduino.cc/index.php?topic=128635.0
Looks like we are giving it a full set of parallel pins, should not be needed when talking to an i2c display.
The 0 is probably to define a "select" pin, which if 0 probably means the display is always selected.
This looks really silly, I'd go find another library.

Jerry


On Sat, Apr 7, 2018 at 09:13 pm, Tim Gorman wrote:
Jerry,

I assume the 0 is to initially set the lcd to instruction mode so it
can be cleared or whatever. It would then be set high by the program
when it needs to write a character.

I'm not an Arduino programmer nor a C++ programmer. But I do find this
"constructor" in the LiquidCrystal.h file:

LiquidCrystal_I2C(uint8_t lcd_Addr, uint8_t En, uint8_t Rw, uint8_t Rs,
uint8_t d4, uint8_t d5, uint8_t d6, uint8_t d7,
uint8_t backlighPin, t_backlighPol pol);

I assume this has something to do with setting up the program to
properly handle the lcd.

tim ab0wr


I2C Display code

K9HZ <bill@...>
 

Here is W0EBs code and it has the I2C calls for that type of display already complete...


Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ

Owner - Operator
Big Signal Ranch – K9ZC
Staunton, Illinois

Owner – Operator
Villa Grand Piton – J68HZ
Soufriere, St. Lucia W.I.
Rent it: www.VillaGrandPiton.com
Like us on Facebook!

Moderator – North American QRO Yahoo Group.

email: bill@wjschmidt.com





---
This email has been checked for viruses by AVG.
http://www.avg.com


Re: Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

John <passionfruit88@...>
 

Yes Tim, we all know what is more important..hihi

73, John


Re: POP fix

Jerry Gaffke
 

Tim wrote:

> If there is no voltage applied to Q6 during transmit how much
> microphone signal is going to be conducted through Q6? 

There's definitely power to Q6 during transmit.
I assume you mean during receive.
But with the VA7AT pop fix, Q6 is always powered.

 
From near the bottom of   http://ubitx.net/fix-audio-pop/
under section  Fifteen Component Fix:

"This circuit rewires the preamplifiers to be permanently powered and inserts serial gating in each of the inputs, controlled directly from the TX and RX power busses."

So Q6 is always powered up.


Jerry


On Sat, Apr 7, 2018 at 08:58 pm, Tim Gorman wrote:

If there is no voltage applied to Q6 during transmit how much
microphone signal is going to be conducted through Q6?


Re: Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

K9HZ <bill@...>
 

The point is that he is already heading down the trail of incorporating the update.  Compare it to 1.06x.  It’s really better that Ian incorporate this into his firmware and release it rather than forks (unless, of course, you are ok with being incompatible in future releases…).

 

 

Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ

 

Owner - Operator

Big Signal Ranch – K9ZC

Staunton, Illinois

 

Owner – Operator

Villa Grand Piton – J68HZ

Soufriere, St. Lucia W.I.

Rent it: www.VillaGrandPiton.com

Like us on Facebook! facebook icon

 

Moderator – North American QRO Yahoo Group.

 

email:  bill@...

 

 

From: BITX20@groups.io [mailto:BITX20@groups.io] On Behalf Of Jerry Gaffke via Groups.Io
Sent: Saturday, April 7, 2018 11:07 PM
To: BITX20@groups.io
Subject: Re: [BITX20] Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

 

I did.
See old history below.

You have to be careful about taking comments in the source code too seriously.

Jerry

On Sat, Apr 7, 2018 at 08:55 pm, K9HZ wrote:

Try release 1.07…

 

  From: BITX20@groups.io [mailto:BITX20@groups.io] On Behalf Of Jerry Gaffke via Groups.Io

 KD8CEC is using the standard parallel LCD display.


chronos@localhost ~/Downloads/kd8cec/ubitx-1.07/ubitx_20 $ grep Liquid *

ubitx_lcd_1602i.ino:#include <LiquidCrystal.h>


Virus-free. www.avg.com


Re: Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

Tim Gorman
 

John,

Thank you. I'll let you know what I find.

After I finish the income tax up that the wife has been after me to do!

tim ab0wr

On Sat, 07 Apr 2018 20:14:11 -0700
"John" <passionfruit88@hotmail.com> wrote:

I have just uploaded a test version for I2C LCD display (16x2 size).
It has the option of two libraries, with the smallest one beind teh
default.

In fact if this library works, it is smaller than the original
digital output wired library.

The file is uBitx-Raduino-KD8CEC based-VK2ETA-Variation -
I2C_Display_test-v0.1.zip in the same folder as my original post.

I can't test it so any feedback will be great.

All the best,

73, John (VK2ETA)


Re: Variation on Ian's KD8CEC uBitx software (based on his 1.04 release for now) and ATU sketch. #ubitx

Tim Gorman
 

Jerry,

I assume the 0 is to initially set the lcd to instruction mode so it
can be cleared or whatever. It would then be set high by the program
when it needs to write a character.

I'm not an Arduino programmer nor a C++ programmer. But I do find this
"constructor" in the LiquidCrystal.h file:

LiquidCrystal_I2C(uint8_t lcd_Addr, uint8_t En, uint8_t Rw, uint8_t Rs,
uint8_t d4, uint8_t d5, uint8_t d6, uint8_t d7,
uint8_t backlighPin, t_backlighPol pol);

I assume this has something to do with setting up the program to
properly handle the lcd.

tim ab0wr

On Sat, 07 Apr 2018 20:02:57 -0700
"Jerry Gaffke via Groups.Io" <jgaffke=yahoo.com@groups.io> wrote:

Perhaps that's a different library, and you have to specify pin
numbers on a part on the little i2c backpack soldered to the back of
your lcd display? But what's that zero doing in there?

The way most code examples on the web kick it off is as follows:
  LiquidCrystal_I2C lcd(0x27, 16, 2);

That's for an i2c device address of 0x27, 16 characters per line, 2
lines. The library assumes you are using the only pins with hardware
support for i2c on the Nano, so you don't have to specify pin numbers.

You still have to find the i2c device address for your display (0x27
here), which can vary between LCD displays.
And you should remove the display's 5v pullup resistors on SDA and
SCL. https://groups.io/g/BITX20/message/39966

Here's a complete "Hello World":from   
   https://github.com/fdebrabander/Arduino-LiquidCrystal-I2C-library/blob/master/examples/HelloWorld/HelloWorld.ino

#include <Wire.h> 
#include <LiquidCrystal_I2C.h>
LiquidCrystal_I2C lcd(0x27, 16, 2);
void setup()  {
lcd.begin();
lcd.backlight();
lcd.print("Hello, world!");
}
void loop()  { }

Jerry, KE7ER

On Sat, Apr 7, 2018 at 07:41 pm, Tim Gorman wrote:


// Set the pins on the I2C chip used for LCD connections:
// addr, en,rw,rs,d4,d5,d6,d7,bl,blpol
LiquidCrystal_I2C lcd(0x3F, 2, 1, 0, 4, 5, 6, 7, 3, POSITIVE);