The tef6686_esp32 from pe5pvb

Wrong calculation for SNR on OIRT

My antenna cable was not properly connected, so I got these values

Switching to FM the values were ok, so only OIRT affected.

BTW: Have not tried to get that behavior a second time.

Battery percentage on v1 useless

On my original (Dutch) v1 TEF switching to Battery options -> Show percentage will show that anyway but break the layout.

Screenshots from English and German translation

Cannot switch band in MEM mode

In order to change from FM to AM you need to be in MAN or AUTO mode.

In case you are in MEM switching won't work.

Tested with 8d46bcf

Overlapping text

In German, FM is called UKW, but the MEM-number is overlapping with the word UKW

Tickers in advanced RDS screen

The tickers in advanced RDS stop and restart too early and therefore the last characters are (almost) not to be seen. In detail:
EON: The last digit of the last frequency is only to be seen for a few milliseconds, so it should scroll a bit longer even if there is no more information.
AF: Same as for EON
RT: In case of RT with 64 characters the last few characters are not to be seen.
RT+: Actually I couldn't receive RT+ with full 64 characters, maybe it needs also a bit of prolongation.

Support for German Ö and Ä in RT

In case there is a special character in the Radiotext, this will be skipped (even for the following ones)

The interesting thing is, that the TEF shows the character ü but not the other ones like ä.

Nächste Sendung: Journal um fünf gets Nste Sendung: Journal um fünf

Im Gespräch mit der gets Im Gespr mit der

RT and PS show wrong characters

From June commits on, the PS and RT on the TEF sometimes show wrong characters (even displayed in yellow letters). Till 30th May (1.16RC) it was correct.

See 825cc68

For example the correct PS

RADIO-K

gets

RADIO,?

Better to show nothing rather than garbage ...

see screenshots.

Testing with latest commit:

$ git show
commit f926634f0152cd8c7e7e718ada4cad4aff3522f5 (HEAD -> main, origin/main, origin/HEAD)
Merge: dac00bc e1add2c
Author: Sjef Verhoeven PE5PVB <[email protected]>
Date:   Fri Jun 9 12:51:14 2023 +0200

Problems with "screen off" in the menu.

When I have activated "Touch rotating", then "screen off = 3 sec" is set in the settings when I switch the screen off and on with the "band" button on the LW/MW/SW band.

for example:
if I set "Touch rotating = On" and "Screensaver = Off" then Exit and Store.
Go to a SW band and hold the band button to turn off the screen.
When I then press the band button once to turn on the screen, it turns off automatically after 3 sec.
I then go into the menu and see "Screensaver = 3 sec"

PTYN color when it's N/A

TEF6686_ESP32/TEF6686_ESP32.ino

Lines 2260 to 2266 in fc14a4b

    
           if (ptynold != radio.rds.PTYN) { 
        
             tftPrint(-1, "PTYN N/A", 216, 109, BackgroundColor, BackgroundColor, FONT16); 
        
             tftPrint(-1, ptynold, 216, 109, BackgroundColor, BackgroundColor, FONT16); 
        
             if (radio.rds.PTYN.length() == 0) radio.rds.PTYN = "PTYN N/A"; 
        
             tftPrint(-1, String(radio.rds.PTYN), 216, 109, PrimaryColor, PrimaryColorSmooth, FONT16); 
        
             ptynold = radio.rds.PTYN; 
        
           }

Can you print the word PTYN in white and N/A in yellow?

I know that the space is limited and the word PTNY might be skipped when it's not 0 (as far as I understood, because there is no station with PTYN here).

Improvements for RT

Dynamic RT typically changes flag A/B in about 15 seconds (sometimes only about 5 seconds). Those times comply to IEC 62106-2. Actually one transition in the TEF lasts about 45 seconds (in main screen) or 23 seconds (in advanced RDS screen). So most of the time RT is switching before transition is done. IMHO it can be speeded up so that transition is completed in about 15 seconds. With the smoothed fonts it should still be easily readable.
In case of flag A/B change RT should be reset and start the new text even if the previous transition is not done.
In the main screen RT scrolls until the last character has vanished beyond the left margin. This should be equalized to the advanced mode: start RT again after the last character (and a bit of empty space) has become visible.

Sudden reboot during RDSSPY WiFi connection

During an RDSSPY connection via WiFi the TEF rebooted suddenly.

After this reboot RDSSPY received no data at all. I have switched it off an on several times to get it working again.

This sudden reboot happened a second time some minutes later.

I have no idea what went wrong here.

Using e2cc859, old Win 7 laptop 32 bit. WiFi is my hotspot on the mobile next to the TEF.

If RDS is lost, there will be no retuning to AF.

When the signal drops rapidly and RDS is lost, retuning to AF will not occur, even though the entire AF list is loaded.

Offset on OIRT frequencies

@ohmytime

Dear Kevin, the OIRT frequencies are wrong. There is an offset as the edges are not correct.

I've changed them to

#define FREQ_FM_OIRT_START         6590   // use values of 1/10 * kHz
#define FREQ_FM_OIRT_END           7400   // use values of 1/10 * kHz

And it works!

Due to the new OIRT band implementation, there is no need to have a menu item for the FM lower edge in my opinion.

Font too small

Since a couple of commits the pop-up "SCANNING" or "NOT POSSIBLE" is too small in comparison to before.

Missing sprites

In this issue all missing sprites should be reported.

(at M from MHz)

Strange behaviour on OIRT band with step size and presets

First of all, I think OIRT being its own band is a very handy solution! It's useful to be able to wrap around on (CCIR) FM from 87.5 --> 108.0 and vice versa.

There seems to be some strange behaviour with the OIRT band in terms of step size and setting presets.

For the tuning steps - if you tune to the top of the OIRT band (74.00 MHz), and wrap around back to the bottom, the steps are incorrect (64.02 ... 66.00 MHz ... etc.) - these are 10kHz too high. If you wrap back in the opposite direction from 64.02 down to 74.00 and tune down, they're back to the correct steps ( 74.00 ... 66.02 ... 65.90). Presumably this is because 74.00 is a correct step so it syncs up in that direction - hopefully the fix for this is as simple as setting the first channel to 64.01 rather than 64.02.

Secondly, if you save a preset on OIRT and then return to it in MEM mode, the signal level suddenly rises to around 115dBµV on the display, and the audio seems to be from an AM signal rather than the OIRT frequency displayed. Cycling back to OIRT via the band selection button clears the error.

I hope this is helpful, let me know if any more details are required! This behaviour has been confirmed by a few different beta testers trying the 27/07/2023 build.

Thanks,
Adam

RDS Block A error indicator

The RDS block A error indicator is not working properly.

VID_20230804_095819.webm

RDS Errors are green when RDS got lost

When RDS signal got lost, the 4 RDS error dots still show green instead of red.

Complilation from src

Hi
I'm trying to compile it from sources but I have to many errors, can u help me with this? I'm using Arduiono IDE and all libraries seems to look ok
Thanx

Wider capital PS characters overlap EON

Due to larger widths for some capital letters it may happen that PS has a display collision with S/M and EON.

For example in this screenshot
ANTENNE_ and
KAERNTEN
hide the following text a bit.

Internal noise increased on latest firmware

After flashing a recent firmware version, dated on Aug 3rd, overall noise levels significantly increased on numerous FM frequencies, most notably around 87.3-87.8, and as mentioned by other users on 101.8. As well as many frequencies below 87 MHz. On 87.45 two regularly received stations are badly interfered, this internally generated display noise was much weaker on the earlier firmware, dated around Jul 11 (released just after the AM signal level offset was included to the menu, several days before adding the advanbced FM AF lists). In addtition to that several weak FM signals mainly in the lower portion of the band around 91 MHz sounded slightly noisier (but not as serious as around 87 MHz). Perhaps this is caused by changed, altered clock frequencies, more data transfer between the chip and the display or something else related to the display? After downgrading to a older firmware version dated on Jul 15, noise levels on the lower FM band decreased, 87.8 and several other frequencies became usable (when the display switch off long press band button function was added, and before more AF list features were implemented). Besides this there are some performance issues on another post,

RT+ shows first character when Raw Data are 0

Described in https://discord.com/channels/1053804249651359765/1053804250276298895/1132563377839943791

When RT+ has the following flags:

RT Plus:
Tag 1    = Tag 1 = 
Tag 2    = Tag 2 = 
Raw Data = 0,0,0,0,0,0

RT History:
20:26:33 VIALE SARCA 223 - MILANO

then the RT+ will show the first character from the RT, in this case V from VIALE

Slower performance, lagging on recent fimware

After flashing a recent beta firmware version (Aug 3rd), navigating through the menu pages became noticeably slower, and loading the RDS AF listing requires at least twice as long, compared to a earlier firmware version (Jul 15). Overall performance seems to have worsened. After downgrading to the Jul 15 firmware, performance improved, menu pages and RDS AF lists are loading much quicker (similar to the Jul 11 firmware that was used before).

Trigger for TMC flag

I am still curious about TMC response time. This should work much faster. TMC receivers I have seen display the first message after a few seconds.
So I worked on RDS specification (IEC 62106): The presence of a TMC service is signalized in Group 3A (about every five seconds). If there is AID = 0xCD46 in Block 4 this is first strong evidence that TMC is transmitted. To make it more secure check also if group 8A is indicated in block 2 (10000 in the last five bits of block 2). And for perfection check if group 8A is truely transmitted. With this the TMC indicator should respond much faster than actually. Hope that I didn't missunderstood anything...

Only a minor issue; AM sensitivity, mainly on LW, decreased a little bit

Upon flashing the Aug 3rd beta firmware version, using the very same settings as before, signal levels mainly on LW decreased a little bit, this was most apparent on 198 kHz BBC Radio 4. Around 5 dB less compared to the Jul 11 or 15 firmware versions. The AM display switch off (long press band button) feature is very useful, thanks for adding that to the firmware, it really reduces a lot of noise or display interference. On the currently installed Jul 15 firmware, 198 kHz BBC Radio 4 peaks at aound 70 dB or S=9+40 dB on a BNC connected telescopic whip (one of the strongest signals overall).

when trying to enter the menu, it displays "not possible"

Sometimes it won't allow me to enter the menu using the middle button and displays "not possible". This has now happened to me twice in a short period of time. I still don't know how to target this error.

Flipped rotary for BAND selection on SW

The rotary on SW for the BAND selection is flipped. I guess it is checking the meters, instead of the frequency.

For example if you want to switch from 49m to 41m band you need to scroll down instead of up.

Squelch shows double text

The word OFF (in the pic it's the localized German word AUS) is in the background of the squelch value.

This seems to happen when the squelch is changed during scanning.

WiFi icon broken resp. wrong sprites

I wonder that nobody has reported already

Problem with patch #163, Screensaver issues.

Hello,
I still have problems with the screensaver.
When the screen saver is off and I long press the band button, a 3 sec delayed screen saver is forced on. Even in fm mode and I press the band button to get more RDS info.

I deleted these lines:
if (touchrotating) {
if (poweroptions != LCD_OFF) poweroptions = LCD_OFF;
if (!screensaverset) screensaverset = 1;
}

And everything was fine again.

I use the gray china model with silver buttons and have no problems with either the screensaver or anything else after I deleted the #163 patch.

onmytime, could you please check it?

The last characters of the AF list on the RDS screen are missing.

On the advanced RDS screen, when the AF list is scrolled, the last few characters are not displayed. For example, the last frequency in the list is "106.1", but only "10" is displayed. It happens often, but not always.

Redrawing the frequency on AF screen

On the AF screen does not completely redraw the previous frequency when changing to another frequency.

PTYN only shows 4 characters

Described in https://discord.com/channels/1053804249651359765/1080501413651693578/1133824988483440640

PTYN is specified for 8 characters, but it will only show the first 4.

White display (crash?)

Sometimes on my original v1 TEF I have a white display and I need to reboot it.

I don't know if this is related to WiFi (as I'm currently testing a lot) of will show after a while.

Squelch values always in dBuV

I've noticed that if I change signal unit in the settings to dBf or dBm squelch values on the main screen are still in dBuV and don't switch to dBf or dBm

Limit "set volume"

After some tests with xdr-gtk and rdsspy the value in "set volume" got suddenly +100 dB (of course no sound)

MEM places (are not band-related)

Although the description changed from FM to OIRT, the MEM places are not related to each band. I know that this is a limitation, but the MEM position after the BAND is misunderstanding.

So a user will overwrite the MEM position 1 although he thinks, this is free.

Suggestions: the text for BAND and MEM place should not be displayed one after the other. See advanced RDS view.

interference on 101.8 MHz

With version 2.0, I have interference at a frequency of 101.8 MHz when the display is running (and redraws). If the display turns off, the interference disappears. I had similar interference to a lesser extent with version 1.18 at the frequency of 90.1 MHz, here it is now fine.

"hijacking" the station

I discovered an interesting bug. If I have the AF function on and I have a station "ABC" tuned in that temporarily has no other AF available and another station "XYZ" starts playing on most recently tuned frequency over the hill and his RDS data is loaded, the receiver will start retuning to the station's alternate frequencies "XYZ" and station "ABC" will not return. This causes the rotary control function to freeze and TEF needs to be restarted. Unfortunately, I cannot repeat this error at home, but maybe someone with their own transmitter and RDS encoder could do it.

Stationlist for Android just one direction on direct connections

Seems TEF does not tell Stationlist for Android a changed frequency.

The other way round works, Stationlist for Android controls the TEF.

Empty AF does not show text 87

Other than EON or RT+, empty AF will not tell, that there is no AF.

For example, this station has no AF:
http://andimik.bplaced.net/sendinfo.php?id=256

Expectation:
Write the text defined in 87.

TEF6686_ESP32/src/language.h

Line 91 in 921b041

"No AF available", // 87

Could you check

TEF6686_ESP32/TEF6686_ESP32.ino

Line 3239 in 921b041

    
           if (radio.rds.hasAF) for (byte i = 0; i < radio.af_counter; i++) afstring += String(radio.af[i].frequency / 100) + "." + String((radio.af[i].frequency % 100) / 10) + (radio.af[i].filler ? "(f)" : "") + (i == radio.af_counter - 1 ? " " : " | "); else afstring = myLanguage[language][87];

Direct RDSSpy connection

TEF6686_ESP32/TEF6686_ESP32.ino

Line 309 in 4835871

WiFiServer Server(7373);

RDS Spy connection seems to be configured in this line using port 7373. Of course RDS Spyin menu is set for the USB (and wifi) connection.

But in the latest versions (maybe last 2-3 weeks) I could not establish a direct RDS Spy connection. I even have tested if some serial.print outputs are printed (like I have seen before), but there is nothing on 7373.

I found my postings in a German radio forum dated 15th and 16th June, where I informed my colleagues, that RDS Spy works well. I remember that I could set the frequency in RDS Spy and the TEF re-tuned to it.

https://www.rundfunkforum.de/viewtopic.php?p=1716663#p1716663
https://www.rundfunkforum.de/viewtopic.php?p=1716856#p1716856

Switching back to xdr-gtk option in menu, and connection works well with xdr-gtk.

See pictures. Signal quality is excellent.

I could reproduce it several times.

RT+ double text

If RT+ is received, the advanced RDS menu shows double text

Advanced RDS menu not accessible during xdr-gtk connection

Advanced RDS menu is not accessible during an xdr-gtk connection. Long pressing the button does not work here.

	if (ptynold != radio.rds.PTYN) {
	tftPrint(-1, "PTYN N/A", 216, 109, BackgroundColor, BackgroundColor, FONT16);
	tftPrint(-1, ptynold, 216, 109, BackgroundColor, BackgroundColor, FONT16);
	if (radio.rds.PTYN.length() == 0) radio.rds.PTYN = "PTYN N/A";
	tftPrint(-1, String(radio.rds.PTYN), 216, 109, PrimaryColor, PrimaryColorSmooth, FONT16);
	ptynold = radio.rds.PTYN;
	}

pe5pvb / tef6686_esp32 Goto Github PK

tef6686_esp32's People

Contributors

Stargazers

Watchers

Forkers

tef6686_esp32's Issues

Recommend Projects

Recommend Topics

Recommend Org