MMDVM/MMDVMHost
1
0
Fork 0
mirror of https://github.com/g4klx/MMDVMHost synced 2025-12-24 09:35:40 +08:00
Code Issues Packages Projects Releases Wiki Activity

Changed the display layout examples and readme to reflect the code changes

Browse Source
This commit is contained in:
ON7LDS
2017-12-31 19:20:20 +01:00
parent eb14aeb861
commit 52c76040a1
8 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
Nextion_ON7LDS/NX3224T024-L3.HMI
View File

Binary file not shown.

BIN
Nextion_ON7LDS/NX3224T024-L3.tft
View File

Binary file not shown.

BIN
Nextion_ON7LDS/NX3224T028-L3.HMI
View File

Binary file not shown.

BIN
Nextion_ON7LDS/NX3224T028-L3.tft
View File

Binary file not shown.

BIN
Nextion_ON7LDS/NX4832T035-L3.HMI
View File

Binary file not shown.

BIN
Nextion_ON7LDS/NX4832T035-L3.tft
View File

Binary file not shown.

7
Nextion_ON7LDS/README-L3
View File

@@ -50,9 +50,10 @@ to do some tasks when receiving data from MMDVMHost or NextionDriver:
- change colors and fonts of the TA on the DMR page when it arrives.
(TA length calculation is done in the display itsself !)
- remove the slot number from t2.txt (since it's always 2)
- display the GPS data (if received) in a new field (called 'GPS'),
by copying the GPS data form the field where MMDVMHost has
written to (t11 for GPS data from slot 2 in DMS format)
- in the middle of the DMR screen, the previous user is displayed
for each slot (S1 at the left, S2 at the right)
This is done by copying the data from the ID/TA field to these
fields at call end.
The examples are there to give you an idea of what can be done.
It is up to your imagination to go even further.

7
Nextion_ON7LDS/README.md
View File

@@ -13,14 +13,13 @@ are activated.
Layout 2 is a no-nonsense layout. It is the original (G4KLX) layout with the Talker Alias added. TA color and fonts size can not be changed. At least not easily.
Layout 3 (as is 4) is a layout without any predefined layout options (color, fonts). It sends the fields *and* information about what was sent to the display, so all layout processing can and should be done in the display ittself.
Layout 3 (as is 4) is a layout without any predefined layout options (color, fonts). It sends the fields *and* information about what was sent to the display, so all layout processing can and should be done in the display itself.
More information about the layouts can be found in
* README-L2 for the screenLayout 2 setting
* README-L2 for the screenLayout 3 and 4 settings
When you want extra control over what has to be sent to the Nextion display,
you could consider the program 'NextionDriver' at https://github.com/on7lds/NextionDriver as a companion to MMDVMHost.
This program sends extra information about the host to the display and can do processing which would not be the task of MMDVMHost (for example: with the help of this program, it is possible to use buttons on the display).
When you want extra control over what has to be sent to the Nextion display, you could consider the program 'NextionDriver' at https://github.com/on7lds/NextionDriver as a companion to MMDVMHost.
This program sends extra information about the host to the display, can do callsign lookup with extended information (name, city, country) and can do more processing which would not be the task of MMDVMHost (for example: with the help of this program, it is possible to use buttons on the display).
In verbose mode, this program shows you all communication between MMDVMHost and the display.