Topics

NEXTION DISPLAY UPDATES For KD8CEC ver 1.094 up


Bo Barry <wn4ghv@...>
 

The enhanced version allows addition of the little expansion board which will allow extra push button modes, among other things. Handy.
Bo W4GHV 


Allen Merrell
 

Enhanced has RTC on board.
--
Allen  Merrell


Jim Sheldon
 

New to the Nextion scene too, but I have had a 3.2" Nextion display for a while now and have been trying to make sense out of the editor.  I think I finally have that figured out.  I just loaded Ian's 1.095 software with the 3.2" TJC GUI.  Even using the "manager" program, I can talk to the uBITX and Nextion with the computer, but I can't get the 3.2" Nextion to do anything to control the uBITX.  None of the push buttons such as CWl, CWU, or even the configuration buttons in that menu on the display seem to cause anything to happen with the radio itself.   Also, no frequency control of the uBITX from the VFO keyboard or up down display menu either.  It just displays the frequencies as set by the main encoder.  Can't set bands in the display either, just with the function button and normal factory type menu that comes up.

It is a pretty display of those functions as set and controlled in the manager, but I thought the Nextion was supposed to work as a stand-alone display/control board once the functions were set.  Seems there's a lot of work still to be done.  I've seen similar complaints on the Facebook uBITX group as well.

Appreciate any help you guys can give as I'm building a uBITX for a friend and would like to give it to him in working condition with Ian's latest software and a 3.2" Nextion touch display.  It's a birthday present for him and I'm a bit short on time getting it running.

Thanks a million for any help,

Jim Sheldon, W0EB


Mark M
 

If the display is a Nextion and you loaded the TJC file (I assume you mean you loaded the tft file into the display), that might be the problem. I don't know the difference but I'd think there's a reason that there are two sets of files. FWIW, I have both a 2.4 and a 3.2 Nextion and both work fine with their respective tft files.

Mark AA7TA

On 7/9/18 10:42 AM, Jim Sheldon wrote:
New to the Nextion scene too, but I have had a 3.2" Nextion display for a while now and have been trying to make sense out of the editor.  I think I finally have that figured out.  I just loaded Ian's 1.095 software with the 3.2" TJC GUI.  ...


Joe
 

Hi,
The nextion uses 2 files.
.hmi which is the source code. This is used to modify existing code. Used with nextion editor

And
 .tft which is the compiled code, ready to use but not changeable. Installed on the micro sd card.

If you load the tft on the nextion display, it will do a count down then report sucessful.
Remove sd, reboot
Now the new screen will appear.
Everything will be functional if you connect to the ubitx. If not then only items which do not require a response from the ubitx will be fully functional.

To use the nextion editor you open the .hmi file.
To see the display in action press debug.


Joe
VE1BWV


On Mon, Jul 9, 2018, 4:17 PM Mark M <junquemaile@...> wrote:
If the display is a Nextion and you loaded the TJC file (I assume you
mean you loaded the tft file into the display), that might be the
problem. I don't know the difference but I'd think there's a reason that
there are two sets of files. FWIW, I have both a 2.4 and a 3.2 Nextion
and both work fine with their respective tft files.


Mark    AA7TA

On 7/9/18 10:42 AM, Jim Sheldon wrote:
> New to the Nextion scene too, but I have had a 3.2" Nextion display for
> a while now and have been trying to make sense out of the editor.  I
> think I finally have that figured out.  I just loaded Ian's 1.095
> software with the 3.2" TJC GUI.  ...




Jim Sheldon
 

I used the .hmi file and uploaded it from the editor. The .tft is the same file just already compiled and installed via the SD card. Either should be identical.

Jim

On Jul 9, 2018, at 2:17 PM, Mark M <junquemaile@...> wrote:

If the display is a Nextion and you loaded the TJC file (I assume you mean you loaded the tft file into the display), that might be the problem. I don't know the difference but I'd think there's a reason that there are two sets of files. FWIW, I have both a 2.4 and a 3.2 Nextion and both work fine with their respective tft files.

Mark AA7TA

On 7/9/18 10:42 AM, Jim Sheldon wrote:
New to the Nextion scene too, but I have had a 3.2" Nextion display for a while now and have been trying to make sense out of the editor. I think I finally have that figured out. I just loaded Ian's 1.095 software with the 3.2" TJC GUI. ...


Mark M
 

What I'm confused about is that in one place you say you have a Nextion display but then you say you loaded the TJC file. Nextion and TJC are different and each has it's own set of hmi and tft files on Ian's site. I don't know how they differ but I'd imagine that there are two sets for a reason and you need to use the files that go with the display you have. I don't know if you can load one's file into the other. It was just a suggestion of something to check.

And the key word is 'should'. I would not assume that they're identical, esp. if the one you compiled doesn't work correctly. The pre-compiled files are known to work. I'd try using them and if it still doesn't work there's probably something else at play.

Mark

On 7/9/18 12:47 PM, Jim Sheldon wrote:
I used the .hmi file and uploaded it from the editor. The .tft is the same file just already compiled and installed via the SD card. Either should be identical.
Jim


Jim Sheldon
 

Good point. I was under impression that TJC was the last three of the callsign related to the person that did the larger sized display conversions. I used the earlier file for the Nextion 3.2" Enhanced (which my display is, with both CEC 1.094 and 1.095 with exactly the same results. The display IS a real Nextion ordered from them.

Jim

On Jul 9, 2018, at 3:51 PM, Mark M <junquemaile@...> wrote:

What I'm confused about is that in one place you say you have a Nextion display but then you say you loaded the TJC file. Nextion and TJC are different and each has it's own set of hmi and tft files on Ian's site. I don't know how they differ but I'd imagine that there are two sets for a reason and you need to use the files that go with the display you have. I don't know if you can load one's file into the other. It was just a suggestion of something to check.

And the key word is 'should'. I would not assume that they're identical, esp. if the one you compiled doesn't work correctly. The pre-compiled files are known to work. I'd try using them and if it still doesn't work there's probably something else at play.

Mark

On 7/9/18 12:47 PM, Jim Sheldon wrote:
I used the .hmi file and uploaded it from the editor. The .tft is the same file just already compiled and installed via the SD card. Either should be identical.
Jim


Bob Bennett
 

I have an old TFT_320QVT layng around. I wonder if the code for the Nextion is generic for other touch displays or is it unique to Nextion?

Bob nz2z


Joe
 

Bob,
The code is unique to Nextion displays only.. The nextion display is one of the only intelligent displays having its own microprocessor, memory etc..

Joe

On Tue, Jul 10, 2018 at 12:49 AM Bob Bennett via Groups.Io <bobsmacbox=yahoo.com@groups.io> wrote:
I have an old TFT_320QVT layng around. I wonder if the code for the Nextion is generic for other touch displays or is it unique to Nextion?

Bob nz2z


Glenn
 

Digole make a 'smart' TFT also.  Not as smart though as the Nextion from what I have seen, but useful nonetheless in other projects.   There is no IDE like Nextion, just a large number of commands.  http://www.digole.com/

glenn


On Mon, Jul 9, 2018 at 08:59 pm, Joe wrote:
Bob,
The code is unique to Nextion displays only.. The nextion display is one of the only intelligent displays having its own microprocessor, memory etc..
 
Joe

On Tue, Jul 10, 2018 at 12:49 AM Bob Bennett via Groups.Io <bobsmacbox=yahoo.com@groups.io> wrote:
I have an old TFT_320QVT layng around. I wonder if the code for the Nextion is generic for other touch displays or is it unique to Nextion?

Bob nz2z


Jim Sheldon
 

Hi gang,
Got egg all over my face on this one! Been a tech and even taught electronics for the US Army for over 8 years before I retired from that career in 1981. Hooked this thing up, got all the software right but in the hookup to the Raduino's original display connector, I was off by 1 pin. I had power, ground and the Yellow (RX line to the Nextion) hooked where they were supposed to be. Had the TX line FROM the Nextion hooked to pin 5 of the Raduino's connector and since pin 5 on that connector is grounded on the Raduino, it's absolutely no wonder the uBITX could not receive commands from the Nextion!!!!

MY BAD!!!!! All is working as it should and the 3.2" display controls the rig just fine.

Amazing the problems a minor wiring error can cause when you are so sure you got it right that you don't re-check the connections!

Nice work on everything to all those who are involved in this project.

The only problem I can find is that the software is actually offsetting the CW Transmit carrier by the Sidetone frequency. This should actually leave the CW transmit carrier EXACTLY on the indicated frequency on the display. To properly use CW on any transceiver, the receiver frequency (not shown on the display though) should be moved into the filter's passband by the desired listening tone (usually the sidetone frequency). This has been the true way to do it ever since transceivers first came out (The Collins KWM-1 comes to mind). If you offset the transmit frequency, you wind up with two stations chasing each other either up or down the band depending on which sideband is used in CW receive. This COULD wind up with both stations walking right out of the band if they weren't watching what they were doing and that might get them in trouble with their respective governments.

I call on everyone writing firmware for the uBITX to take a close look at how they are implementing the CW vs Dial Frequency calibration. I think you will find that anyone having complaints of them not working right will find that the TX frequency is being offset rather than the RX.

Ron, W2CTX and I had this conversation early on in our development efforts for the W0EB/W2CTX firmware and though it took a while to convince Ron that it was the proper way to go, he came round and our calibration, when done according to the instructions will put the CW transmit frequency right on the money when you tune the received CW audio tone to match the uBITX sidetone setting. Of course not everyone (including me) has perfect pitch, so this might vary a few cycles due to individual hearing, but it will certainly be very close compared to the way it works out when the TX carrier is offset.

I've said my piece and I hope it gets the attention of Ashhar Farhan and Dr. Ian Lee as Ashhar's original software use TX offset for CW and so apparently does Dr. Lee.

Not meaning to be nasty to them, far from that. I have the interest of the entire ham community, especially CW operators that use the uBITX, in mind and the proper use of the mode.

Again, KUDOS to those developing the Nextion control - It appears to be working very well (now that I fixed my stupid wiring error).

Jim Sheldon, W0EB
(www.w0eb.com)

------ Original Message ------
From: "Jim Sheldon" <@W0EB>
To: BITX20@groups.io
Sent: 7/9/2018 2:47:20 PM
Subject: Re: [BITX20] NEXTION DISPLAY UPDATES For KD8CEC ver 1.094 up

I used the .hmi file and uploaded it from the editor. The .tft is the same file just already compiled and installed via the SD card. Either should be identical.

Jim

On Jul 9, 2018, at 2:17 PM, Mark M <junquemaile@...> wrote:

If the display is a Nextion and you loaded the TJC file (I assume you mean you loaded the tft file into the display), that might be the problem. I don't know the difference but I'd think there's a reason that there are two sets of files. FWIW, I have both a 2.4 and a 3.2 Nextion and both work fine with their respective tft files.

Mark AA7TA

On 7/9/18 10:42 AM, Jim Sheldon wrote:
New to the Nextion scene too, but I have had a 3.2" Nextion display for a while now and have been trying to make sense out of the editor. I think I finally have that figured out. I just loaded Ian's 1.095 software with the 3.2" TJC GUI. ...




Richard Spohn
 

I am on the verge of purchasing one of the Nextion displays....2
questions: A) are there more KD8CEC "features" on the bigger
displays, or are the bigger displays just larger versions of the
smaller; and B) is the enhanced version desirable, as for the
real-time clock and bigger flash memory? Thanks - Rich WB2GXM


Joe
 

A. Same features but different resolution on standard Nextion displays.  I have 3.2(400*240) and 7 inch (800*480) cheaper and works as well as my E version

The "E" versions have more memory, real time clock with battery slot and faster  - cost more.

I find my 7 inch standard display  response is as fast as my 3.2 E   - At least I cant see any difference 

Both types work well,  mostly its a matter of personal choice and what resolution you want

Joe
VE1BWV

On Tue, Jul 10, 2018 at 7:32 PM Richard Spohn <wb2gxm@...> wrote:
I am on the verge of purchasing one of the Nextion displays....2
questions:  A) are there more KD8CEC "features" on the bigger
displays, or are the bigger displays just larger versions of the
smaller; and B) is the enhanced version desirable, as for the
real-time clock and bigger flash memory?  Thanks - Rich WB2GXM




Richard Spohn
 

Thanks Joe. I think the size of my display then, will depend on how
much space there is on the panel...I bought one of Sunil's cases, and
now I'm thinking I could mount the correct size of Nextion in a bezel
with bolts mounted on the back that are spaced to hold the Nextion to
the front of the case, covering the hole in it that was meant for the
16x2. That could work pretty nicely. As for the enhanced version, I
think the RTC would be a nice thing to have, I like how it looks on
Ian's graphics (your graphics). Thanks for all the info! - Rich
WB2GXM

On 7/10/18, Joe <@ve1bwv> wrote:
A. Same features but different resolution on standard Nextion displays. I
have 3.2(400*240) and 7 inch (800*480) cheaper and works as well as my E
version

The "E" versions have *more memor*y, *real time clock* with battery slot
and *faster* - cost more.

I find my 7 inch standard display response is as fast as my 3.2 E - At
least I cant see any difference

Both types work well, mostly its a matter of personal choice and what
resolution you want

Joe
VE1BWV

On Tue, Jul 10, 2018 at 7:32 PM Richard Spohn <wb2gxm@...> wrote:

I am on the verge of purchasing one of the Nextion displays....2
questions: A) are there more KD8CEC "features" on the bigger
displays, or are the bigger displays just larger versions of the
smaller; and B) is the enhanced version desirable, as for the
real-time clock and bigger flash memory? Thanks - Rich WB2GXM






Mark M
 

I have one of Sunil's cases and was looking at a way to use a Nextion without major butchering of the nice case. The 2.4" that I have looks like it might just barely fit...I measured the height of the display as about 43mm and the distance from the top edge of the front panel to the top of the jack labels is about 48mm. The 3.2" display is about 47mm high. Looks like either might fit but it would be close, if you don;t want to cover up the labels. A bezel would add some to the size of the display.

I have a second uBitX waiting to be assembled. I think I'll leave the first one in Sunil's case with the 16x2 display (altho I swapped it for white-on-blue version that I like better) and build the second one into another case that I can set up the way I like it.

Also, I believe that Sunil is planning to offer cases cut for some of the Nextion displays but I don't know how far along he is with that. Maybe he'll chime in here with more info.

Anyway, just some info that may be of use.

(We might want to start a new thread about this.)

Mark AA7TA

On 7/10/18 7:20 PM, Richard Spohn wrote:
Thanks Joe. I think the size of my display then, will depend on how
much space there is on the panel...I bought one of Sunil's cases, and
now I'm thinking I could mount the correct size of Nextion in a bezel
with bolts mounted on the back that are spaced to hold the Nextion to
the front of the case, covering the hole in it that was meant for the
16x2. That could work pretty nicely. ...


Jim Sheldon
 

I enlarged the window of one of my earlier uBITX rigs (that had been installed in a Circuit Specialists extruded aluminum case) to fit the 3.2 inch Enhanced Nextion. Originally I had used a 4 line by 20 character I2C LCD display and I was able to make the Nextion fit in that case by seriously enlarging the opening.  It isn't as neat as if I would have been able to start with a blank panel, but I have a Bezel on order (should be here today) that I hope will cover most of the old screw holes and then I can re-label the jacks & controls.

I got complacent when I wired it originally and was off on the blue "TX" wire from the display to Raduino display socket by 1 pin.  I had the Nextion's TX going to pin 5 (ground) rather than pin 4 (RST) and it displayed everything just fine but would not (of course) command the rig.  Once I got my head removed from a dark place and wired it correctly (LOL) it now works really well. 

I had to go back and re-read Ian's info on the Manager program and do some configuring (still more to do, but I'm on the road now) to get it running smoothly.  Hopefully the new Bezel will help me make it look as nice as the original did with the 4 X 20 display with it's original bezel.  The color Nextion will definitely spiff it up quite a bit with a cleaned up front panel.  Here's a couple pix of the work in progress. Even with the old, vacated holes in the panel it still doesn't look too bad.

Jim Sheldon, W0EB


Richard Spohn
 

Thanks Mark, haven't measured anything yet....if the Nextion on a
Sunil case proves unworkable, well, will just have to leave v1 uBitx
in the case and buy a shiny new v4 for the Nextion version, with a
homemade enclosure. And why not, I may ask! - Rich

On 7/10/18, Mark M <junquemaile@...> wrote:
I have one of Sunil's cases and was looking at a way to use a Nextion
without major butchering of the nice case. The 2.4" that I have looks
like it might just barely fit...I measured the height of the display as
about 43mm and the distance from the top edge of the front panel to the
top of the jack labels is about 48mm. The 3.2" display is about 47mm
high. Looks like either might fit but it would be close, if you don;t
want to cover up the labels. A bezel would add some to the size of the
display.

I have a second uBitX waiting to be assembled. I think I'll leave the
first one in Sunil's case with the 16x2 display (altho I swapped it for
white-on-blue version that I like better) and build the second one into
another case that I can set up the way I like it.

Also, I believe that Sunil is planning to offer cases cut for some of
the Nextion displays but I don't know how far along he is with that.
Maybe he'll chime in here with more info.

Anyway, just some info that may be of use.

(We might want to start a new thread about this.)

Mark AA7TA

On 7/10/18 7:20 PM, Richard Spohn wrote:
Thanks Joe. I think the size of my display then, will depend on how
much space there is on the panel...I bought one of Sunil's cases, and
now I'm thinking I could mount the correct size of Nextion in a bezel
with bolts mounted on the back that are spaced to hold the Nextion to
the front of the case, covering the hole in it that was meant for the
16x2. That could work pretty nicely. ...



Kai Nilakari
 

Hi guys,

can't see any NOT ENHANCED tft file for 3.2 in screen which I use in my radio.
Tried 32E_F_0_2d.tft but no go...

Or do I just miss something?

73
Kai OH3WE


Kai Nilakari
 

Couldn't get it even in as the display says it is not for this 3.2 standard.

How can this be so damn difficult?...

Kai OH3WE