-
Notifications
You must be signed in to change notification settings - Fork 38
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
Input from TEF6686 tuner #89
Comments
I took a look at it. The serial data looks quite odd - seems like the same group is always repeated four times, each with a different value of rdsErr. It would produce this:
But maybe it could work if only the ones with rdsErr=0 are accepted... |
Let me first try to modify the firmware for the device. So put this on hold for the moment. I'm aware that the same group is repeated several times. |
Sure. It's practically done though, just missing some test cases :) |
The firmware has been modified and the above mentioned bug was fixed. The following log from a502_serial.txt The line with leading R and the following hex code is the correct one, of course. I already have reported that because the |
R line has been fixed. Should now look like this: a502_ttyusb0.txt I have tried with
|
Can you check out the |
It's a new command-line option for input types: |
Great! Confirmed, this works!
|
The TEF6686 tuner outputs RDS groups as ASCII via serial USB. Redsea can decode this with the option `-i tef`. To allow for future input formats the option `-i` was added: `redsea -i {bits,hex,mpx,tef}` The old input format switches will continue working.
The output format has slightly changed in recent firmware version for several reasons. The only difference is, that in the "R"-Line now also the PI-Code is inserted. Please note, that the old firmware might be still used widely.
So let me propose to add the new format, too, but keep compatibility to the old one (by checking the length of the "R"-Line). |
Several radio freaks have recently bought a tuner with TEF6686 chip inside which can be connected to USB. See https://www.pe5pvb.nl/tef6686/
Its output (ttyUSB0) is in the following format:
the line starting with P contains the PI-Code (here A540)
the line starting with R consists of RDS blocks B (
rdsB
), C (rdsC
) and D (rdsD
) and a RDS error (rdsErr
) informationthe line starting with S shows the signal strength.
Do you think it's possible to implement this format in redsea? I tried with
awk
, but it seems to be too tricky for me.For example the following log
a201_ttyUSB.txt
was filtered by RDS error = 0 (maybe other values are ok as well)
a201.spy.txt
Specification of the chip:
https://github.com/makserge/tef6686_radio/blob/master/User_Manual_TEF6686.pdf
This is the source code which creates the format:
https://github.com/NoobishSVK/TEF6686-remastered/blob/330e4d591e0b09f664e36671db0b36627dc361f8/TEF6686_remastered.ino#L2251
The text was updated successfully, but these errors were encountered: