PD0DIB / NX3224T024 missing t21/t22/t23
Posted: Mon Apr 19, 2021 7:37 pm
I run Pi-Star on a Pi 2 Model B, with generic MMDVM HAT (12MHz).
I have a NX3224T024 with a modified NX3224T024_Model 10_2.4inch_SMPLX_Basic_v1.05.HMI loaded.
So, the mod is just the mode pages removed for the modes i will not use, to bring it down to a size so it will load into the display (Start, MMDVM, DStar and DMR are retained)
The display is driven from the headers on the modem.
PiStar has the ON7LDS driver installed and it is configured for ON7LDS L3 driver.
Rob PD0DIB notes that fields t21 : CPU frequency, t22 : CPU loadavg 1 min & t23 : Disk free % require the NextionDriver by ON7LDS, however these fields are blank, as are t8, t14, t15, t16 & t17 in the DMR screen.
If I choose G4KLX or ON7LDS L2 options, i have less information displayed as expected.
I'm not really sure what should be visible, as i can't find any example images of this layout in use.
(I've attached a few images of what I am seeing)
Anyone got any idea as to why the fields are not populated?
Reload the driver perhaps?
Is all the CPU/disk free data available on a Pi2B?
I have a NX3224T024 with a modified NX3224T024_Model 10_2.4inch_SMPLX_Basic_v1.05.HMI loaded.
So, the mod is just the mode pages removed for the modes i will not use, to bring it down to a size so it will load into the display (Start, MMDVM, DStar and DMR are retained)
The display is driven from the headers on the modem.
PiStar has the ON7LDS driver installed and it is configured for ON7LDS L3 driver.
Rob PD0DIB notes that fields t21 : CPU frequency, t22 : CPU loadavg 1 min & t23 : Disk free % require the NextionDriver by ON7LDS, however these fields are blank, as are t8, t14, t15, t16 & t17 in the DMR screen.
If I choose G4KLX or ON7LDS L2 options, i have less information displayed as expected.
I'm not really sure what should be visible, as i can't find any example images of this layout in use.
(I've attached a few images of what I am seeing)
Anyone got any idea as to why the fields are not populated?
Reload the driver perhaps?
Is all the CPU/disk free data available on a Pi2B?