Date   
Re: W8TEE TFT/ VFO DISPLAY BOARD BOARD

David S
 

Jack and Art

The flicker is definitely due to the display 3.3v floating, if you look at the circuit there's a connector between the display supply and the Arduino 3.3v, I had the same problem, fitting a jumper cures it.  It's the jumper right by Jack's callsign, the two end pins nearest the edge of the PCB., See the the arrow in attached photo of the board.

Jack

Thanks for all your effort's, I think (hope) everyone appreciates your work.  I had one of your first batch of boards and just got around to assembling it, there,s nothing connected, the DDS and Mimic are yet to be fitted.  I need to run a few things past you.  I have two 3.5" displays, an ebay purchase from the same vendor, they have slightly different boards, both return the ID as 0x7796 and result in a shrunken sized display, see the attached pictures.  If I use 0x9486 the picture size is the same but the colours are wrong, using 0x9488 gives a grey scale full sized screen with a "dot" font similar to a 16 x 2 LCD.  If I run the Mcufriend examples they seems OK, their test card is small but it's only 240 x 320 pixels so I would not expect a full screen, I can also load your AA program, without any means to test correctly it appears to run correctly. Do you have any ideas.

The Arduino regulator is also running hot, not too hot to touch but very warm, it's drawing 300ma, on one of your earlier iterations of the circuit you had the Arduino 5v supply connected directly to the buck regulator, that would be one way of reducing the heat, any reason why that change was made.  I think most of the current is due the the screen backlight, I can't see anywhere in the software where you control the backlight, plus there's no indication of which pin on the display board is the backlight, I'll have to trawl the internet.  Any help very much appreciated.

Regards David G8DJM

Re: W8TEE TFT/ VFO DISPLAY BOARD BOARD

Art Olson
 

Jack
Thanks. Feel a bit foolish for missing the info in the manual

Art

Sent from my iPhone

On Jul 15, 2017, at 10:37 PM, Jack Purdum via Groups.Io <econjack@...> wrote:

Art:

I'm sure the flicker is because the voltage pin is floating. The code is written so the display updates every 2 seconds, but only if there is a "real" swing in the voltage. You can see the code in loop(), around line 1515. The way to get this to work on the display is explained in the B40 Assembly Manual (Rev. 2) that is in the Files section. Look for "Determining the Displayed Voltage". If you don't want the voltage display activated, just comment out the code block that starts at 1515.

Al Peter helped me fix the "encoder noise" is was hearing. Turns out it was a flat forehead mistake on my part. In the process of separating the PA power source from the TFT power source, I managed to introduce a ground loop. Once that was determined it was fairly easy to fix.

I'm back onto the other features I want to add.

Jack, W8TEE



From: Art Olson via Groups.Io <olsonaj6927@...>
To: BITX20@groups.io
Sent: Saturday, July 15, 2017 5:11 PM
Subject: Re: [BITX20] W8TEE TFT/ VFO DISPLAY BOARD BOARD

Jack

I must have missed this in the build or setup. The voltage continues to change so it must be floating. I have the tft/vfo connected to the bitx40 power so don't think I have a ground problem. Could you resend the detail about the voltage divider 

"If you connect the display voltage pin to your voltage source, it will flash one or two times at power up, but will only update itself if there is a measurable change in the supply voltage. My guess is that you don't have yours tied to either ground or a voltage divider. As a result, the pin is floating which is read as a new voltage which triggers a screen update.I had mine running several hours last night and it never varied enough to update the field". 

art


Re: BITX echolink node

bobolink
 

Maybe when you post your question you could include a voice mode where someone might contact you for a detailed discussion. Which D-Star/DMR/Fusion--Reflector/Talk Group/Room (or whatever Echolink uses) to find you on.

 

I use notifications to my phone to get my attention. APRS was working on a ham messaging system. Here is Twitter to DMR. YouTube

Re: BITX echolink node

Steve Greer
 

OK let me get this right.  This is radio RIGHT!  All this echolink stuff what are you guys a bunch of 2 Meter Techs.  Sure some people want an 800 # they can call in and have some tech on the line walk them through programming their remote, but wanting people to download install and figure out how to get on echolink, IMO you will have people running in circles.  Lets face it if you can't read and understand how to put a few plugs on a board and make a few connections to power, how in the world do you expect people to figure out how to install and use echolink.  A chat room is a simple link and there is a way to send a private msg if someone wanted to exchange phone # or go on and connect on a video chat.  I'm just putting in my 2 Cents I bought the same $59 dollar radio, I have 3 of them, I read the wire up page and had no issues putting my boards together.  I didn't expect the first one to work but to my surprise it was great.  I didn't expect to have my hand held, I knew I would have to READ to get some answers.  I never used arduino before receiving my BITX.  I had to RTFM.  I never build anything prior, I'm a fairly new ham only a little over a year.  I don't know maybe I am just being harsh, but for pete sake!!!

Re: BITX echolink node

Arv Evans
 

David  KF4WBJ

Benefit of the BITX group is that it serves as a common collection point for information
and ideas that may be useful to others.  Because email text messages are preserved
on the group it then serves as a reference library that can be searched for historical or
topical information.  Splitting the group into multiple factions and multiple communication
modes would seem to minimize this information sharing and archive function.  There
have been attempts in the past to dilute the group by starting additional BITX discussion
groups and on-line chat systems. 

Using email as access to the discussion group provides a deliberate time lag that allows
contributors to read what they are saying before they send it.  This conceptually leads
to better content and less confusion.   Being able to type an email message and read
it over before sending may also be an advantage for those who do not use English as
a primary language.  It also benefits English speakers who want to translate messages
that may have been submitted in some language other than English.

For those who want optimum real-time response there is always the telephone and
VoIP (Voice over Internet Protocol) for private point-to-point communications.  And of
course there is ham radio using our BITX transceivers as the communication link.

Where something like Echo-Link or any of the radio focused chat systems might be interesting
is for areas where there is no Internet access.  To make this of maximum value though
would probably require implementation of a gateway between that system and the BITX
group.  Disadvantage of using EchoLink is that it locks out any non-ham licensed person
from participating in its use.  Since EchoLink is DOS/Windows software it also becomes
problematic for those who use UNIX-derived computer operating systems (OS-X, Android,
Linux, etc.).

Arv  K7HKL
_._


On Sat, Jul 15, 2017 at 3:56 PM, David Woodward <kf4wbj2@...> wrote:
While this is a great group with many capable people, it is way too slow in response time.
 Wouldn't an echolink node strictly for bitx related things be more convenient? 
 What are your thoughts?


Re: W8TEE TFT/ VFO DISPLAY BOARD BOARD

Jack Purdum <econjack@...>
 

Hey, Art...not a problem. The file's only been there a day or two and it will take a while to know it's available. No doubt I'll be posting new versions later on. BTW, my TFT/VFO PCB doesn't have to be used to replace the VFO. It's also a good way to experiment with the Mega 2560 Pro Mini since all of the pins are brought out to header pins, making it easy to attach things for testing. Indeed, you could leave off the support components and use it "stand-alone". I've tried to price it reasonably to encourage you people to experiment with it, to all of our benefit.

Jack, W8TEE



From: Art Olson <olson339@...>
To: BITX20@groups.io
Sent: Sunday, July 16, 2017 6:56 AM
Subject: Re: [BITX20] W8TEE TFT/ VFO DISPLAY BOARD BOARD

Jack
Thanks. Feel a bit foolish for missing the info in the manual

Art

Sent from my iPhone

On Jul 15, 2017, at 10:37 PM, Jack Purdum via Groups.Io <econjack@...> wrote:

Art:

I'm sure the flicker is because the voltage pin is floating. The code is written so the display updates every 2 seconds, but only if there is a "real" swing in the voltage. You can see the code in loop(), around line 1515. The way to get this to work on the display is explained in the B40 Assembly Manual (Rev. 2) that is in the Files section. Look for "Determining the Displayed Voltage". If you don't want the voltage display activated, just comment out the code block that starts at 1515.

Al Peter helped me fix the "encoder noise" is was hearing. Turns out it was a flat forehead mistake on my part. In the process of separating the PA power source from the TFT power source, I managed to introduce a ground loop. Once that was determined it was fairly easy to fix.

I'm back onto the other features I want to add.

Jack, W8TEE



From: Art Olson via Groups.Io <olsonaj6927@...>
To: BITX20@groups.io
Sent: Saturday, July 15, 2017 5:11 PM
Subject: Re: [BITX20] W8TEE TFT/ VFO DISPLAY BOARD BOARD

Jack

I must have missed this in the build or setup. The voltage continues to change so it must be floating. I have the tft/vfo connected to the bitx40 power so don't think I have a ground problem. Could you resend the detail about the voltage divider 

"If you connect the display voltage pin to your voltage source, it will flash one or two times at power up, but will only update itself if there is a measurable change in the supply voltage. My guess is that you don't have yours tied to either ground or a voltage divider. As a result, the pin is floating which is read as a new voltage which triggers a screen update.I had mine running several hours last night and it never varied enough to update the field". 

art





Virus-free. www.avast.com

Re: BITX echolink node

Herb
 

So Echolink is for people with no internet? Just how do you connect??
It ONLY works on Dos/Windows??? Uh NO it is runs on Linux/Android/Ios/Windows

How is it everyone complaining at the very thought of using some other platform to discuss the BITXxx system can't be bothered to even Google Echolink so as to discuss it intelligently.

Re: BITX echolink node

Arv Evans
 

On Sun, Jul 16, 2017 at 9:16 AM, Herb <sailor422@...> wrote:
So Echolink is for people with no internet? Just how do you connect??
It ONLY works on Dos/Windows??? Uh NO it is runs on Linux/Android/Ios/Windows

How is it everyone complaining at the very thought of using some other platform to discuss the BITXxx system can't be bothered to even Google Echolink so as to discuss it intelligently.


Re: W8TEE TFT/ VFO DISPLAY BOARD BOARD

DH2LAB
 

Hi David S,

YES, the jumper solves the flickering!!!
Many Thanks,

73 de Matt, DH2LAB

Re: BITX echolink node

Herb
 

No Steve THIS is an internet group TALKING about Ham radio.
You will find groups discussing virtually every topic from the proper way to trim your toenails to how to migrate to Mars
Echolink IS a part of ham just like the digital modes.or moon bounce or building kits

Re: BITX echolink node

Francesca Wine <francescawine@...>
 

More fun with HFwith  Bitx40  echeolink is internet  base not a challenge.
Francesca W7LTG NV

--
Sent from Hotmail Email App for Android

Sunday, 16 July 2017, 08:21AM -07:00 from Herb sailor422@...:

No Steve THIS is an internet group TALKING about Ham radio.
You will find groups discussing virtually every topic from the proper way to trim your toenails to how to migrate to Mars
Echolink IS a part of ham just like the digital modes.or moon bounce or building kits

--
I have  bitx40  and completely wired up. get nice hiss when the volume up. display lights up only showing Raduino V1.01.  frequency never shown, anyone have that problem?  i think the software is not in the chip.
Francesca W7LTG   NV 

Re: W8TEE TFT/ VFO DISPLAY BOARD BOARD

Jack Purdum <econjack@...>
 

Hi David:

Thanks for the callout on the flicker. I'm not exactly sure what your mod was. The pins you reference are actually take-off points for various voltages and not (what I think of as) jumper points. Can you give me a little more detail on your mod.

I had a board where the colors were outta whack. I vaguely remember looking at the color values that seem to be shown and they looked like the compliment of the color I needed, so I tried something like:

#define BLUE                 ~0x001F        // The compliment of 0x001f

and that worked for that display. (This code can be seen in the AA setup() function.) See if that works for you. Take the AA code below (note the colors code), and add the yellow test code:

 g_identifier = tft.readID();    // Get TFT ID  3.95" = 0x9486, 3.6" = 0x9488

 Serial.print("ID = ");
 Serial.println(g_identifier);

  if (g_identifier == 0x9486) {   // If 3.6" TFT, invert colors
    BLUE    = ~BLUE;
    GREEN   = ~GREEN;
    RED     = ~RED;
    YELLOW  = ~YELLOW;
    WHITE   = ~WHITE;
    BLACK   = ~BLACK;
    DKGREEN = ~DKGREEN;
  }

Since the display ID works for you on the AA, match the returned ID in the B40 code and see what happens. If you see white smoke, it didn't work...naw, just kidding.

I'm not sure why the changes were made, as I have as much EE talent as a box of rocks. Farrrukh did the PCB and made the changes, but I'm not sure why. As I recall, someone complained that using the back-to-back diode voltage drop to get from 5V to the 3.3V need by the AD9850 was not good. I think the change came after that, but I've slept since then so I can't be sure. As it is now, the voltage change to 3.3V is a burden now carried by the Mega. I'm working with Al Peter, AC8GY, who is a member of my club and an expert on Diptrace and a talented EE guy to look at the board with an eye to integrating the remaining changes Dennis Kidder (W6DQ) is making to the B40. At this time, I don't know if there will be any significant changes to the PCB. We'll take a look at the regulator problem, however.

I'll try to keep the group posted on anything significant that might change.

Jack, W8TEE



From: David S via Groups.Io <dcsuk10@...>
To: BITX20@groups.io
Sent: Sunday, July 16, 2017 6:28 AM
Subject: Re: [BITX20] W8TEE TFT/ VFO DISPLAY BOARD BOARD

Jack and Art

The flicker is definitely due to the display 3.3v floating, if you look at the circuit there's a connector between the display supply and the Arduino 3.3v, I had the same problem, fitting a jumper cures it.  It's the jumper right by Jack's callsign, the two end pins nearest the edge of the PCB., See the the arrow in attached photo of the board.

Jack

Thanks for all your effort's, I think (hope) everyone appreciates your work.  I had one of your first batch of boards and just got around to assembling it, there,s nothing connected, the DDS and Mimic are yet to be fitted.  I need to run a few things past you.  I have two 3.5" displays, an ebay purchase from the same vendor, they have slightly different boards, both return the ID as 0x7796 and result in a shrunken sized display, see the attached pictures.  If I use 0x9486 the picture size is the same but the colours are wrong, using 0x9488 gives a grey scale full sized screen with a "dot" font similar to a 16 x 2 LCD.  If I run the Mcufriend examples they seems OK, their test card is small but it's only 240 x 320 pixels so I would not expect a full screen, I can also load your AA program, without any means to test correctly it appears to run correctly. Do you have any ideas.

The Arduino regulator is also running hot, not too hot to touch but very warm, it's drawing 300ma, on one of your earlier iterations of the circuit you had the Arduino 5v supply connected directly to the buck regulator, that would be one way of reducing the heat, any reason why that change was made.  I think most of the current is due the the screen backlight, I can't see anywhere in the software where you control the backlight, plus there's no indication of which pin on the display board is the backlight, I'll have to trawl the internet.  Any help very much appreciated.

Regards David G8DJM



Virus-free. www.avast.com

Re: W8TEE TFT/ VFO DISPLAY BOARD BOARD

K5ESS
 

David,

To get the 3.5” Mcufriend TFT LCD for Arduino uno to display properly you need to make the following changes in the TFT VFO software.

At around line 1352 after

case 0x9488:

add

case 0x9486:

 

And change lines 87 through 94 to the following:

 

#define BLUE              0xFFE0

#define GREEN             0xF81F

#define RED               0x07FF

#define YELLOW            0x001F

#define GREY              0x39E7

#define WHITE             0x0000

#define BLACK             0xFFFF

#define DKGREEN           0xFC1F

 

Mike

K5ESS

 

From: BITX20@groups.io [mailto:BITX20@groups.io] On Behalf Of David S via Groups.Io
Sent: Sunday, July 16, 2017 5:28 AM
To: BITX20@groups.io
Subject: Re: [BITX20] W8TEE TFT/ VFO DISPLAY BOARD BOARD

 

Jack and Art

The flicker is definitely due to the display 3.3v floating, if you look at the circuit there's a connector between the display supply and the Arduino 3.3v, I had the same problem, fitting a jumper cures it.  It's the jumper right by Jack's callsign, the two end pins nearest the edge of the PCB., See the the arrow in attached photo of the board.

Jack

Thanks for all your effort's, I think (hope) everyone appreciates your work.  I had one of your first batch of boards and just got around to assembling it, there,s nothing connected, the DDS and Mimic are yet to be fitted.  I need to run a few things past you.  I have two 3.5" displays, an ebay purchase from the same vendor, they have slightly different boards, both return the ID as 0x7796 and result in a shrunken sized display, see the attached pictures.  If I use 0x9486 the picture size is the same but the colours are wrong, using 0x9488 gives a grey scale full sized screen with a "dot" font similar to a 16 x 2 LCD.  If I run the Mcufriend examples they seems OK, their test card is small but it's only 240 x 320 pixels so I would not expect a full screen, I can also load your AA program, without any means to test correctly it appears to run correctly. Do you have any ideas.

The Arduino regulator is also running hot, not too hot to touch but very warm, it's drawing 300ma, on one of your earlier iterations of the circuit you had the Arduino 5v supply connected directly to the buck regulator, that would be one way of reducing the heat, any reason why that change was made.  I think most of the current is due the the screen backlight, I can't see anywhere in the software where you control the backlight, plus there's no indication of which pin on the display board is the backlight, I'll have to trawl the internet.  Any help very much appreciated.

Regards David G8DJM

Re: I don't believe it!

Bill Meara
 

Dex:  You should be able to hear hams on 40 in ZL, especially at night.   I am cc'ing Peter Parker who is over in VK3 -- -he'll be able to advise you better on what you should be hearing on 40 "down under."    73  Bill 


On Saturday, July 15, 2017 7:28 PM, Andrew Krause <andrew.krause@...> wrote:


Is this related to the solar flare earlier this week, maybe?


Re: BITX echolink node

Joe Puma
 

I have a suggestion but this post below pretty much is spot on.  This email group is searchable and contains all the conversations that have been going back-and-forth. To move the conversation somewhere else might be counterintuitive.  But if you really want another platform let's say to talk in real time with one another. Why don't someone start a channel on IRC in the freenode.net?

Currently I hang out there in the #rtlsdr channel and there is a lot of knowledgeable people there already. There is also a channel called #hamradio which is a very active group as well.  As a matter of fact I will create a room called #bitx40 and hold the channel down. All is welcome to join and talk if you'd like.  Get an IRC app like hexchat, Connect to the freenode.net server and join the channel #bitx40

I am pretty sure that there are individuals who are in the RTLSDR or hamradio channel that are also part of this group. Anyway see you guys there and use it if you want or continue to post in this group, no big deal. My handle there is pumaj


Joe,
KD2NFC

Sent from my iPhone

On Jul 16, 2017, at 10:46 AM, Arv Evans <arvid.evans@...> wrote:

David  KF4WBJ

Benefit of the BITX group is that it serves as a common collection point for information
and ideas that may be useful to others.  Because email text messages are preserved
on the group it then serves as a reference library that can be searched for historical or
topical information.  Splitting the group into multiple factions and multiple communication
modes would seem to minimize this information sharing and archive function.  There
have been attempts in the past to dilute the group by starting additional BITX discussion
groups and on-line chat systems. 

Using email as access to the discussion group provides a deliberate time lag that allows
contributors to read what they are saying before they send it.  This conceptually leads
to better content and less confusion.   Being able to type an email message and read
it over before sending may also be an advantage for those who do not use English as
a primary language.  It also benefits English speakers who want to translate messages
that may have been submitted in some language other than English.

For those who want optimum real-time response there is always the telephone and
VoIP (Voice over Internet Protocol) for private point-to-point communications.  And of
course there is ham radio using our BITX transceivers as the communication link.

Where something like Echo-Link or any of the radio focused chat systems might be interesting
is for areas where there is no Internet access.  To make this of maximum value though
would probably require implementation of a gateway between that system and the BITX
group.  Disadvantage of using EchoLink is that it locks out any non-ham licensed person
from participating in its use.  Since EchoLink is DOS/Windows software it also becomes
problematic for those who use UNIX-derived computer operating systems (OS-X, Android,
Linux, etc.).

Arv  K7HKL
_._


On Sat, Jul 15, 2017 at 3:56 PM, David Woodward <kf4wbj2@...> wrote:
While this is a great group with many capable people, it is way too slow in response time.
 Wouldn't an echolink node strictly for bitx related things be more convenient? 
 What are your thoughts?


Test of chat function

Ken Hansen
 

if you wouldn't mind, why not post a comment here, curious how the chat function works...

Re: Test of chat function

Ken Hansen
 

This is how chat works...

Ken, N2VIP

On Jul 16, 2017, at 11:37 AM, Ken Hansen <ken@...> wrote:

if you wouldn't mind, why not post a comment here, curious how the chat function works...

Raduino wont load

Michael Davis <maddmd818@...>
 

hi, my buddy has 3 Bitx40's. One died yesterday in the midst of using it. One is being used for spare parts and its Raduino used in place of a potentially defective Raduino. My goal is to get the third one operational. After updating 2 of his radios and my own with v1.18, I tried to load the questionable Raduino with 1.18. It is just the stand alone board in my hand. It won't load. I get an error message after it compiles and tries to upload. Should the device load without a display attached and out of the radio? I should think so. Next question, if the Nano on the board has failed, can it be replaced onto the board if I can get one somewhere? It does display one red steady led and no other lights. Thanks

Re: BITX echolink node

Andrew Krause
 

This entire discuss has strayed into the realm of the asinine and farcical. We're talking about unladen swallow type stuff here. 

Those that want an EchoLink node, go make it happen. Advertise it here. Those opposed, ignore it.


On Sun, Jul 16, 2017 at 11:16 AM Herb <sailor422@...> wrote:
So Echolink is for people with no internet? Just how do you connect??
It ONLY works on Dos/Windows??? Uh NO it is runs on Linux/Android/Ios/Windows

How is it everyone complaining at the very thought of using some other platform to discuss the BITXxx system can't be bothered to even Google Echolink so as to discuss it intelligently.

--

Andrew Krause
General Class Amateur Radio License: KM4ZJO
andrew.krause@...
(404) 732-2369



Re: W8TEE TFT/ VFO DISPLAY BOARD BOARD

K5ESS
 

Jack’s solution better.

Mike

K5ESS

 

From: BITX20@groups.io [mailto:BITX20@groups.io] On Behalf Of K5ESS
Sent: Sunday, July 16, 2017 10:32 AM
To: BITX20@groups.io
Subject: Re: [BITX20] W8TEE TFT/ VFO DISPLAY BOARD BOARD

 

David,

To get the 3.5” Mcufriend TFT LCD for Arduino uno to display properly you need to make the following changes in the TFT VFO software.

At around line 1352 after

case 0x9488:

add

case 0x9486:

 

And change lines 87 through 94 to the following:

 

#define BLUE              0xFFE0

#define GREEN             0xF81F

#define RED               0x07FF

#define YELLOW            0x001F

#define GREY              0x39E7

#define WHITE             0x0000

#define BLACK             0xFFFF

#define DKGREEN           0xFC1F

 

Mike

K5ESS

 

From: BITX20@groups.io [mailto:BITX20@groups.io] On Behalf Of David S via Groups.Io
Sent: Sunday, July 16, 2017 5:28 AM
To: BITX20@groups.io
Subject: Re: [BITX20] W8TEE TFT/ VFO DISPLAY BOARD BOARD

 

Jack and Art

The flicker is definitely due to the display 3.3v floating, if you look at the circuit there's a connector between the display supply and the Arduino 3.3v, I had the same problem, fitting a jumper cures it.  It's the jumper right by Jack's callsign, the two end pins nearest the edge of the PCB., See the the arrow in attached photo of the board.

Jack

Thanks for all your effort's, I think (hope) everyone appreciates your work.  I had one of your first batch of boards and just got around to assembling it, there,s nothing connected, the DDS and Mimic are yet to be fitted.  I need to run a few things past you.  I have two 3.5" displays, an ebay purchase from the same vendor, they have slightly different boards, both return the ID as 0x7796 and result in a shrunken sized display, see the attached pictures.  If I use 0x9486 the picture size is the same but the colours are wrong, using 0x9488 gives a grey scale full sized screen with a "dot" font similar to a 16 x 2 LCD.  If I run the Mcufriend examples they seems OK, their test card is small but it's only 240 x 320 pixels so I would not expect a full screen, I can also load your AA program, without any means to test correctly it appears to run correctly. Do you have any ideas.

The Arduino regulator is also running hot, not too hot to touch but very warm, it's drawing 300ma, on one of your earlier iterations of the circuit you had the Arduino 5v supply connected directly to the buck regulator, that would be one way of reducing the heat, any reason why that change was made.  I think most of the current is due the the screen backlight, I can't see anywhere in the software where you control the backlight, plus there's no indication of which pin on the display board is the backlight, I'll have to trawl the internet.  Any help very much appreciated.

Regards David G8DJM