New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rdsspy output is garbage in groups [1], [2] and [3] #6
Comments
Output from XDR-F1HD is fine:
I believe something is wrong in the TEF firmware. |
I have added the following lines in order to check the value for
The result is
ok, let me try to re-flash the TEF. |
No, I have re-flashed 1.14 and then 1.15 again. I fear it's a bug in rdsspy output (= in this file https://github.com/kkonradpl/xdr-gtk/blob/master/src/rdsspy.c ), because xdr-gtk and stationlist show a correct Radiotext (despite of the RT A/B flag change bug). But I am not a programmer and have absolutely no C++ clue ... I also have tried several options in your tool It seems RDSSpy is also a bit delayed (some seconds) as the radiotext in xdr-gtk and stationlist switches from A to B at the same moment as on the TEF, but not so in RDSSpy. |
Seeems I am not only person with this issue as I found this video: |
In case you need that, this is what the PC receives from the TEF6686 over ttyUSB0:
|
I know that this is NOT a bugfix, but a small workaround for at least local stations. So it has to do with this above mentioned file. Radiotext in RDSSpy now without errors
ScreenshotIt seems that there are too much RDS codes transmitted, so let's write only the good ones to RDSSpy. Patch for Workaround
Advantage
Disadvantage
Please note, I'm NOT a programmer, but I have experience in RDS since MS-DOS ages. |
This is not a bug in XDR-GTK, but in ESP firmware. The RDS data should be sent once all blocks from a given group are ready (or not all, some of them can be missing with corresponding information in the error summary of the "R" message). The attached capture seems to be corrupt (?) – a lot of characters are missing. However, check this pattern: The "R" message should be sent only once (the last one). |
Thanks @kkonradpl for your answer. @PE5PVB and @NoobishSVK Dear Sjef and Marek, could you take a look in your code? Seems it's in https://github.com/NoobishSVK/TEF6686-remastered/blob/15a2f1dd063c63616f21dd5529b2b43c1565c0a3/TEF6686_remastered.ino#L2246 or similar. |
Don't understand this problem. Even when there is no data available, it will always send a 16-bit string, like FFFF or 0000. So, where are these ---- coming from? |
Please download the The R line has different lengths and even there is sometimes no line break between P line and R line. The Should I open a separate issue in your repository because Konrad told me it has to do with the TEF6686 Firmware? |
That's my idea too. The R line is not generated by the TEF software. BTW. I implemented direct connectivity with my TEF v2 with RDS Spy, and there all is OK. |
@NoobishSVK and @PE5PVB I found https://github.com/stailus/tef6686_rds/blob/master/tef6686_rds.ino#L568 which is slightly different than in your code.
Please mind the if-loop. Compared to
in https://github.com/NoobishSVK/TEF6686-remastered/blob/main/TEF6686_remastered.ino#L2210 or
I am not a programmer, but please note the |
Dear @kkonradpl Konrad, I have another workaround (but this is not a bugfix for the firmware): the following command helps me to get error-free radiotext (no missing characters) in lots of the local radio stations (= as long as they repeat the text). But a DXer from Belgrade (Serbia) told me he is working on a new firmware (not open source) and will fix that bug so that I will get RDS from weaker stations as well.
Some examples
playing the attached file
|
Dear Konrad, you were right, it was a firmware issue. Sjef has fixed it today in PE5PVB/TEF6686_ESP32@aba24c0 Now the result is identical to RTL-Sticks. I am so sorry that I have misused your issue tracking (but I could not know where the problem was coming from). |
Could you check if there is a bug in https://github.com/kkonradpl/xdr-gtk/blob/master/src/rdsspy.c ? I have the same issue under Windows 10 and Ubuntu.
Because I have error-free signals on my (Dutch) TEF6686 (v1) and error-free in xdr-gtk (for example the radiotext).
But the RDSSpy output is just garbage in lots of groups [1], [2] and [3]:
My expectation is that each line needs to be without
----
as the signal is error-free.I also tried some modifications in this file, but I am not a programmer in order to fix it.
Could you share your output?
The text was updated successfully, but these errors were encountered: