So whats to do ?
The best would be If I would finish my work... but as many users are impatiently you will have to include it earlier in your frontends ?!
...and I have to earn money until 08 November - so I will have lesser time for it than I had the last 2 weeks
I have tried to started TMC interpretation... I have a lot of documents but not all... if someone could reach ISO14819 documents that would help (buying a PDF copy would cost around 6*80 Euros) - maybe you can fetch it at your university library for free ?
Otherwise there will be no TMC messages in any frontend directly (certainly they will be in Destinator...) .
ShowGPS is a stupid program because it doesn't offer its TMC interpretation for other programs.
Beamrider has done some TMC interpretation but has faded away since 2005.
Then we need a FMRadioHAL "stub" which asks for 2 FMRadioHAL drivers.
The first FMRadioHAL you are listening and the second does some radiocomfort for you - getting TMC messages (so that tuner 1 doesn't need to hear a TMC programme) and enhancing the EON list of the first

So this stub only does some data-switching...
Then we need more FMRadioHAL drivers for the Silabs (could be ideally used as 2. tuner in our stub or just listening as maintuner)
And we need a FMRadioHAL for a GPS/TMC mouse !
No stupid "GPS/TMC mouse to Destinator and we are listing HQCT" !
I prefer merging TMC messages to Destinator and enhancing our EON list !