on7lds / NextionDriver

Driver program to connect MMDVMhost with Nextion Displays, adding extra functionality
33 stars 33 forks source link

T13-T17 not populating #22

Closed VE3RD closed 2 years ago

VE3RD commented 2 years ago

I was running version 1.24 with the filter SendUserDataMask=0b00001110 DMR Screen would not populate T13-17, with or without the filter on both 2,4, or 3,5 inch K nextion screens

Reverted back to version 1,20 and all is well

Phil VE3RD

VE3RD commented 2 years ago

I am no expert in this code, but I made the suggested changes and got DMR working However P25 needs a little more work. From the log you can see that it is searching users.csv for a portion of my call, stripping off the VE and of couse I get a not found. Anyone point me in the the right direction ??

Feb 4 17:22:04 pi-star5 NextionDriver: RX: t0.txt="N VE3RD" Feb 4 17:22:04 pi-star5 NextionDriver: TX: t0.txt="N VE3RD" Feb 4 17:22:04 pi-star5 NextionDriver: NET: t0.txt="N VE3RD" Feb 4 17:22:04 pi-star5 NextionDriver: LH: check [t0.txt="N VE3RD"] on page 4 Feb 4 17:22:04 pi-star5 NextionDriver: LH: page 4 field 0 is [txt="N VE3RD"] Feb 4 17:22:04 pi-star5 NextionDriver: LH: statusval 5 Feb 4 17:22:04 pi-star5 NextionDriver: Search for call [3RD] Feb 4 17:22:04 pi-star5 NextionDriver: --- User index search for call 3RD (0 [] - 212672 [[KC2UOW] )

VE3RD commented 2 years ago

Thank you for the above. I changed all the &TXbuffer[12] to &TXbuffer[10] in the pertinent block of code and now all t18-t22 fields fill in with the correct info.

VE3RD commented 2 years ago

There are two completely separate lookup routines. One for DMR page and one for all other modes.

DMR fills in t13-t17. All other modes fill in t18-t22. Can't see anything that is broken so far. P25 and DMR work fine. Still in test mode for now.

I have a script that will cleanly switch over to the new NextionDriver when ON7LDS posts it. Depending on what he does, this may need a little tweaking, but bash scripts are my thing. I am 72years old with nothing to do but play(program) on my computer, so not worried about spending a little time tweaking. Just not good at C language, but can follow the logic trail.

VE3RD commented 2 years ago

I modified only the section that starts with //send user data if found (Slot 1) if (((1<<page)&sendUserDataMask)&&(strstr(TXbuffer,"t0.txt")!=NULL)&&(TXbuffer[8]!='"')) { and changed all references to TXBuffer[12] to TXBuffer[10]. This affect P25, YSF, NXDN etc Both YSF and P25 work just fine t18-t22

The section for DMR starting with

//send user data if found (Slot 2) if ((4&(1<<page)&sendUserDataMask)&&(strstr(TXbuffer,"t2.txt")!=NULL)&&(TXbuffer[8]!='"')) {

was NOT modified and thus the DMR lookup works just fine. t13-t17 NOTE: if ((4&(1<<page) was previously if ((2&(1<<page) // DMR Page is 00000100 = 4, not 2

VE3RD commented 2 years ago

TS1 is Not an option. It does NOT function on a Simplex Hotspot and has no place in our scheme

I am not advocating this mod for general use. It is for me and a small group of users who use simplex hotspots with Nextion 2.4 and 3.5 inch screens, where TS1 is NOT an option.

T is up to @ON7LDS to revise and publish a version that works for ALL MODES. In the mean time my mod works just fine for DMR TS2, P25 and YSF. When @ON7LDS gets around to making a new version available we will upgrade to it. Currently, our only option was to revert back to version 1.20. The current version 1,24 is totally unusable. Best Regards...

on7lds commented 2 years ago

correction has been pushed. I'm in the process of reviewing the data lookup routines to make them find data for as much modes as possible

VE3RD commented 2 years ago

Still Not Working for P25 LH: check [click S0,1] on page 4 Feb 7 12:50:23 pi-star4 NextionDriver: RX: dim=99 Feb 7 12:50:23 pi-star4 NextionDriver: RX: t0.txt="N VE3RD" Feb 7 12:50:23 pi-star4 NextionDriver: TX: t0.txt="N VE3RD" Feb 7 12:50:23 pi-star4 NextionDriver: NET: t0.txt="N VE3RD" Feb 7 12:50:23 pi-star4 NextionDriver: LH: check [t0.txt="N VE3RD"] on page 4 Feb 7 12:50:23 pi-star4 NextionDriver: LH: page 4 field 0 is [txt="N VE3RD"] Feb 7 12:50:23 pi-star4 NextionDriver: LH: statusval 5 Feb 7 12:50:23 pi-star4 NextionDriver: LH Inhibit#012 Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (0 [] - 212946 [[KC2UOW] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (0 [] - 106473 [KF7EJB] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (0 [] - 53236 [HB9BBM] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (0 [] - 26618 [DK7DN] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (0 [] - 13309 [BG9FMC] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (0 [] - 6654 [AB6XS] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (0 [] - 3327 [5V1JE] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (1663 [2E0WSP] - 3327 [5V1JE] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (1663 [2E0WSP] - 2495 [4G1BID] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2079 [2M0JST] - 2495 [4G1BID] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2287 [2W0RGL] - 2495 [4G1BID] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2287 [2W0RGL] - 2391 [4F1NKS] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2339 [2W1GLY] - 2391 [4F1NKS] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2339 [2W1GLY] - 2365 [4D1Z] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2352 [3B8GW] - 2365 [4D1Z] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2352 [3B8GW] - 2358 [3Z4S] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2352 [3B8GW] - 2355 [3Z1P] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2353 [3DA0MF] - 2355 [3Z1P] ) Feb 7 12:50:23 pi-star4 NextionDriver: --- User index search for call 3RD (2353 [3DA0MF] - 2354 [3X2021] ) Feb 7 12:50:23 pi-star4 NextionDriver: TX: t18.txt="DMRID 3RD" Feb 7 12:50:23 pi-star4 NextionDriver: NET: t18.txt="DMRID 3RD" Feb 7 12:50:23 pi-star4 NextionDriver: LH: check [t18.txt="DMRID 3RD"] on page 4 Feb 7 12:50:23 pi-star4 NextionDriver: LH: page 4 field 18 is [txt="DMRID 3RD"] Feb 7 12:50:23 pi-star4 NextionDriver: LH: statusval 5 Feb 7 12:50:23 pi-star4 NextionDriver: LH Inhibit#012 Feb 7 12:50:23 pi-star4 NextionDriver: TX: t19.txt="Not found in" Feb 7 12:50:24 pi-star4 NextionDriver: NET: t19.txt="Not found in"

I revised ver 1.24 as follows and had it working &TXbuffer[12] does not work for non DMR modes I added a filter on the TS1,P25,YSF etc blocks such that it would ignore DMR all together and changed all the [&TXbuffer[12] to &TXbuffer[10]

I then duplicated the TS2 block and converted it to TS1

not sure if I broke anything else, but everything I needed was working fine I I wrote a script that returns the info string as follows, /home/pi-star/Scripts/getuserinfo.sh K4WZV Robert|Springhill|Florida|United States This functions in all modes, so will be using this until the driver is repaired