Variables sent to Nextion

All things relating to the Nextion Screen(s)
Post Reply
F6GVE
Posts: 13
Joined: Sat Apr 28, 2018 8:39 am

Variables sent to Nextion

Post by F6GVE » Fri May 24, 2019 6:19 pm

Does somebody know where can be find the exhaustive list of t2 t3 t20 etc ?
I can find something which is 1 year old but it is now very partial
Thanks

KE7FNS
Posts: 363
Joined: Wed Apr 17, 2019 11:11 pm

Re: Variables sent to Nextion

Post by KE7FNS » Fri May 24, 2019 10:05 pm

Nobody has made any significant changes to that portion of the code in the last year, so how old it is doesn't really matter.

Also, theres different txt fields and screen instructions being passed to the screen depending on which Nextion Layout you have selected in the configuration, and even different ones if you are running the nextion driver. That info would help narrow down what exactly you are looking for.

Code: Select all

MMDVM
t0 : owner call & ID / errortext  LOCKOUT
t1 : status / ERROR
t2 : date & time


screenLayout >2 :
t3 : ip address
t4 : owner call
t5 : owner ID
t20 : CPU Temperature
t30 : RX Frequency
t31 : Location
t32 : TX Frequency


D-Star
t0 : type my1 my2
t1 : your
t2 : reflector
t3 : rssi
t4 : ber


DMR
t0 : src1 id / call / TA
t1 : dst
t2 : src2 id / call / TA
t3 : dst
t4 : rssi1
t5 : rssi2
t6 : ber1
t7 : ber2

screenLayout >2 :
t8 : GPS1 dec
t9 : GPS1 DMS
t10: GPS2 dec
t11: GPS2 DMS
t12: GPS1 err
t13: GPS2 err


YSF
t0 : type,source
t1 : dst
t2 : src
t3 : rssi
t4 : ber


P25
t0 : type,source
t1 : dst
t2 : rssi
t3 : ber


NXDN
t0 : type,source
t1 : dst
t2 : rssi
t3 : ber

POCSAG
t0 : waiting / RIC
t1 : message
All views, comments, posts and opinions shared are entirely my own.

F6GVE
Posts: 13
Joined: Sat Apr 28, 2018 8:39 am

Re: Variables sent to Nextion

Post by F6GVE » Fri May 31, 2019 9:28 am

Thanks a lot. Your answer is very helpfull for me
KE7FNS wrote:
Fri May 24, 2019 10:05 pm
Nobody has made any significant changes to that portion of the code in the last year, so how old it is doesn't really matter.

Also, theres different txt fields and screen instructions being passed to the screen depending on which Nextion Layout you have selected in the configuration, and even different ones if you are running the nextion driver. That info would help narrow down what exactly you are looking for.

Code: Select all

MMDVM
t0 : owner call & ID / errortext  LOCKOUT
t1 : status / ERROR
t2 : date & time


screenLayout >2 :
t3 : ip address
t4 : owner call
t5 : owner ID
t20 : CPU Temperature
t30 : RX Frequency
t31 : Location
t32 : TX Frequency


D-Star
t0 : type my1 my2
t1 : your
t2 : reflector
t3 : rssi
t4 : ber


DMR
t0 : src1 id / call / TA
t1 : dst
t2 : src2 id / call / TA
t3 : dst
t4 : rssi1
t5 : rssi2
t6 : ber1
t7 : ber2

screenLayout >2 :
t8 : GPS1 dec
t9 : GPS1 DMS
t10: GPS2 dec
t11: GPS2 DMS
t12: GPS1 err
t13: GPS2 err


YSF
t0 : type,source
t1 : dst
t2 : src
t3 : rssi
t4 : ber


P25
t0 : type,source
t1 : dst
t2 : rssi
t3 : ber


NXDN
t0 : type,source
t1 : dst
t2 : rssi
t3 : ber

POCSAG
t0 : waiting / RIC
t1 : message

User avatar
AG4OJ
Posts: 8
Joined: Sun Jun 16, 2019 12:34 pm
Location: Macon, Georgia USA
Contact:

Re: Variables sent to Nextion

Post by AG4OJ » Fri Jun 21, 2019 1:22 am

OK, I like the list of variables, does anyone have examples of the text strings that come out of MMDVMHost into the Nextion Display?
W. R. Pelfrey PE (Retired Professional Engineer, Severely Disabled Veteran)
Macon, Georgia USA - AG4OJ https://AG4OJ.com

User avatar
f5swb
Posts: 5
Joined: Wed Sep 05, 2018 4:41 pm

Re: Variables sent to Nextion

Post by f5swb » Fri Jun 21, 2019 7:18 am

Hello,

I saw also some texts like t201.bis or t200.txt ....
Is there any list available ?

73" F5SWB
https://www.youtube.com/watch?v=jocnxWF ... c4tb08ryzE

KE7FNS
Posts: 363
Joined: Wed Apr 17, 2019 11:11 pm

Re: Variables sent to Nextion

Post by KE7FNS » Sat Jun 22, 2019 2:19 am

AG4OJ wrote:
Fri Jun 21, 2019 1:22 am
OK, I like the list of variables, does anyone have examples of the text strings that come out of MMDVMHost into the Nextion Display?
As far as what I've seen and not seen in the documentation a list of examples like that simply doesn't exist, and I don't think it would be very useful, but feel free to create it.

I just don't have the time to gather it all up for you, but there are multiple ways you could accomplish this.

One would be just looking at the code and getting the information you need from there.
https://github.com/g4klx/MMDVMHost/blob ... n.cpp#L517

Just realize that when you see \" it is escaped, so the output string will only contain a " and not the \. If you didn't put in the \ before the " the compiler would see the quote as the end of the string instead of including the " with the string. And yes, those " (quotes) are VERY important and the nextion is VERY VERY picky about its structure.

The other would be to spit out more detailed information in the NextionDriver logs.
You should be able to follow the instructions on how to get that in one of my other posts( start one paragraph above the RED text.).
viewtopic.php?f=20&t=1848#p8463

f5swb wrote:
Fri Jun 21, 2019 7:18 am
I saw also some texts like t201.bis or t200.txt ....
Is there any list available ?
Those are fields that are created by the person that created the .tft file, and they are calculated and populated on the fly by the screen, and MMDVMHost doesn't ever send data to those fields.

If you want specific info on what those fields are for and do, you should contact the person who created the .tft you loaded.
All views, comments, posts and opinions shared are entirely my own.

PD0DIB
Posts: 31
Joined: Wed Apr 11, 2018 1:34 pm
Location: Uden, The Netherlands

Re: Variables sent to Nextion

Post by PD0DIB » Thu Jul 04, 2019 8:36 am

Lots of info regarding Nextion, designers of the screens (including used field-codes):

https://www.facebook.com/groups/Nextion/files/
-------------------------------
PD0DIB
Playing around with all types of hotspots (simplex & duplex) for DMR and D-Star.
Most of them has a Nextion screen ...

73 de PD0DIB (since 1977 8-) )

User avatar
f5swb
Posts: 5
Joined: Wed Sep 05, 2018 4:41 pm

Re: Variables sent to Nextion

Post by f5swb » Thu Jul 11, 2019 10:50 am

many thanks for yours reply I will continue to explore it :)

On another way, have you ever played with this command from nextion to the system :

com_star
printh 2A
printh F1
print "sudo pistar-update"
printh FF
printh FF
printh FF

I think it would be possible to launch a bash script, I found this for example :

https://github.com/EA7KDO/Nextion.Image ... rhostip.sh

the question is quite simple ok to launch the command from a button but how to catch and see it on the screen ?

Any help wil be very appreciated

73"s qro.
F5SWB

KE7FNS
Posts: 363
Joined: Wed Apr 17, 2019 11:11 pm

Re: Variables sent to Nextion

Post by KE7FNS » Fri Jul 12, 2019 3:54 am

f5swb wrote:
Thu Jul 11, 2019 10:50 am
the question is quite simple ok to launch the command from a button but how to catch and see it on the screen ?
Yes, I have experimented with running scripts from touch areas.

The current implementation simply doesn't support such a thing. It currently allocates a buffer of 256 characters to store the scripts output, which would be too small to capture all of the output of a command like pistar-update. It also isn't setup to drop off the oldest characters, and make space for the newest ones, so you would have to write the programming for that. The maximum size of a textbox in the nextion editor is 255, so to display it now you are forced to have to figure out how to break up a long message into multiple textboxes, and shuffle all the text around. It would be quite a chore.

While I think it would be neat to see information like that, I just don't think its very useful when you can just open a ssh terminal, but good luck.
All views, comments, posts and opinions shared are entirely my own.

Post Reply