Nextion sometimes shows the name and sometimes doesn't for the same callsign

[rogerclarkmelbourne]

I'm not sure if this is something specific to PiStar, but...

I've written my own parser for the Nextion data output, and I've noticed that sometimes MMDVMHost just sends the callsign e.g.

t2.txt="2 N VK3VM"

but sometimes sends callsign and name. e.g.

t2.txt="2 N VK3VM STEPHEN"

These 2 different outputs can be sent within a minute of each other.

PS. I'm parsing the data using an external MCU (STM32F103) connected to an ePaper display.

[d51r3verse]

Reproduced with duplex hotspot DMR#1: BrandMeister TG91 -> RF:TS1 DMR#2: IPSC2 bMaster+'s TG91 -> RF:TS2 *TS1 shows with name on DMRIds.dat well, but TS2 randomly callsign only shows. *This happens all PiStar and plain linux, windows binaries too. *Changed DMR#1, DMR#2, TS1, TS2 orders, and with or without custom S0 scripts... Same problems occurs on TS2(t2.txt) only.

Patched MMDVM_HS firmware's UART repeater baud to 115200bps for display(display connection through 'modem'). I confirmed it is not baud related issue.

[rogerclarkmelbourne]

@d51r3verse

Do you think this is a MMDVMHost problem or a PiStar problem ?

[d51r3verse]

Issue occurs both TS1/TS2 source name resolutions. It must happens after I key up(Accessing TG or Reflector). Also occurs randomly(usually TS2) Tested on Windows, Armbian with latest commit source compiled,. same results.

After add similar clockInt code to here for tracking status changes, sometimes MMDVM does not report(ignore/bypass) status codes to display when I receiving both TS1/TS2 sametime.