Update of rpidatv project is now located on github :
https://github.com/F5OEO/rpidatv
It is not a complete image but sources and installer which have to be setup from a raspbian distribution :
https://www.raspberrypi.org/downloads/raspbian/
It works on the minimal image (Raspbian Jessie Lite)
I surely make an image later, but regularly updates are easier with github (just typing git pull under the rpidatv folder).
Features since last image (1.2.1) :
- Output pins could be changed (in order to avoid conflicts pins for example touchscreen)
- H264 latency
- Graphical interface for touchscreen
- Leandvb integrated in the project (receiving with DVB-S RTL-SDR thanks to Pascal)
- Modulator shoud work with : RF mode, Digithin, I/Q modulator, DTX1, DATV-Express...
A litlle video could be seen at :
http://www.youtube.com/watch?v=vo77Jy-_xOs
73's Evariste F5OEO
rpidatv update
Forum rules
This forum is run by the BATC (British Amateur Television Club), it is service made freely available to all interested parties, please do not abuse this privilege.
Thank you
This forum is run by the BATC (British Amateur Television Club), it is service made freely available to all interested parties, please do not abuse this privilege.
Thank you
Re: rpidatv update
Very impressive stuff - might have to have a go at this myself !
73 Tim
73 Tim
Re: rpidatv update
Hi Evariste
I can't get it to work at all in IQ mode on a B+. There are no outputs on any of the pins. IQ mode defaults to pins 12/13 but I checked all other pins on the header. 5V and ground are as expected. Incidentally, I will need a different pin for Q. The program is running and appears to be outputting on the default pins but there isn't any output.
Steps were to download Raspian Jessie (normal, not lite) and follow your instructions from github. There has been a recent firmware update to the PI. Could that be an issue?
Mike
I can't get it to work at all in IQ mode on a B+. There are no outputs on any of the pins. IQ mode defaults to pins 12/13 but I checked all other pins on the header. 5V and ground are as expected. Incidentally, I will need a different pin for Q. The program is running and appears to be outputting on the default pins but there isn't any output.
Steps were to download Raspian Jessie (normal, not lite) and follow your instructions from github. There has been a recent firmware update to the PI. Could that be an issue?
Mike
Re: rpidatv update
Hi Mike,
Mine didn't work either so I reverted to the original firmware and mentioned it to Colin. He hadn't tried the new version so couldn't confirm whether there was a problem or not.
Since then I'm just using the earlier version which does give I and Q out.
Steve
Mine didn't work either so I reverted to the original firmware and mentioned it to Colin. He hadn't tried the new version so couldn't confirm whether there was a problem or not.
Since then I'm just using the earlier version which does give I and Q out.
Steve
Find me on the LEO/MEO satellites.
https://m0skm.com/2024/03/29/worked-all-states/
https://m0skm.com/2024/03/29/worked-all-states/
Re: rpidatv update
Can you remember where you got the earlier version of the RPI firmware?
I assume you are using the earlier SD image too? I found that I could get IQ out by running rpidatv directly. However, while pin 12 (I) was correct, the other pin (Q) wasn't. I set it to 23 and eventually found it up in the 30s. So something wrong there. Checking wiggling the pins in python, worked as expected, so its something in the datv software.
Also, I have a huge DC spike of about 20dB. The IQ balance going in to the modulator is fairly good, 0.7 V with just a few mV across the test points. I don't know what's causing it. It could be a less than random IQ stream or something not right with the modulator.
Wonder why the bandwidth select isn't driven by the IO pins. Would seem the obvious thing to do!
Mike
I assume you are using the earlier SD image too? I found that I could get IQ out by running rpidatv directly. However, while pin 12 (I) was correct, the other pin (Q) wasn't. I set it to 23 and eventually found it up in the 30s. So something wrong there. Checking wiggling the pins in python, worked as expected, so its something in the datv software.
Also, I have a huge DC spike of about 20dB. The IQ balance going in to the modulator is fairly good, 0.7 V with just a few mV across the test points. I don't know what's causing it. It could be a less than random IQ stream or something not right with the modulator.
Wonder why the bandwidth select isn't driven by the IO pins. Would seem the obvious thing to do!
Mike
Re: rpidatv update
Hi Mike,
Yes I'm using the earlier RpiDATV software, It does all I need.
Retrieved my original firmware version from here https://github.com/raspberrypi/firmware/commits/master
Luckily I had another Pi of the same age and I interrogated it for the version number.
If you are using a Pi with the 40 pin GPIO you can route the (Q) signal from pin 35 to your RBTVMOD board.
Steve
Yes I'm using the earlier RpiDATV software, It does all I need.
Retrieved my original firmware version from here https://github.com/raspberrypi/firmware/commits/master
Luckily I had another Pi of the same age and I interrogated it for the version number.
If you are using a Pi with the 40 pin GPIO you can route the (Q) signal from pin 35 to your RBTVMOD board.
Steve
Find me on the LEO/MEO satellites.
https://m0skm.com/2024/03/29/worked-all-states/
https://m0skm.com/2024/03/29/worked-all-states/
Re: rpidatv update
Hi,
Just see that installing the latest version is not easy.
Be sure to start from a jessie raspbian distribution (Lite is preferred).
About GPIO pin number : WARNING : the GPIO number is not the Pin header Number :
By default it is GPIO 12 for I and GPIO 13 for Q -> means Pin 32 and 33 oh the header.
If after instructions that doesn't work : you can send me a mail in order to debug it and see what I didn't explain well.
Regarding the touchscreen interface : I test mainly with Tontec screen (https://www.amazon.fr/laffichage-Raspbe ... B00OFLKPG4)
For RBTVMOD, all future updates will be base on the new distribution on github, so could be good that most of people succeed in installing it !
73's Evariste F5OEO
Just see that installing the latest version is not easy.
Be sure to start from a jessie raspbian distribution (Lite is preferred).
About GPIO pin number : WARNING : the GPIO number is not the Pin header Number :
By default it is GPIO 12 for I and GPIO 13 for Q -> means Pin 32 and 33 oh the header.
If after instructions that doesn't work : you can send me a mail in order to debug it and see what I didn't explain well.
Regarding the touchscreen interface : I test mainly with Tontec screen (https://www.amazon.fr/laffichage-Raspbe ... B00OFLKPG4)
For RBTVMOD, all future updates will be base on the new distribution on github, so could be good that most of people succeed in installing it !
73's Evariste F5OEO
Re: rpidatv update
Hi Evariste,
I think the problem is with the latest 4.4 kernel it doesn't work at all for me on my B+. However, it does seem to be OK with kernel 4.1 so I reverted to the last version of that.
Regarding the pins, unfortunately the pins I need to use are 12 and 23 as these are the ones connected on the PCB, which only has the 26 pin header. I know 12 maps to 18 but 23 does not seem to map at all.
Mike
I think the problem is with the latest 4.4 kernel it doesn't work at all for me on my B+. However, it does seem to be OK with kernel 4.1 so I reverted to the last version of that.
Regarding the pins, unfortunately the pins I need to use are 12 and 23 as these are the ones connected on the PCB, which only has the 26 pin header. I know 12 maps to 18 but 23 does not seem to map at all.
Mike
Re: rpidatv update
Hi Mike,
I have to test on 4.4..I am still on 4.1 kernel ! Thanks for pointing it.
About GPIO pin : Pin 23 doesn't handle Q : because the original PCB seems that the signal is getting from a wire soldered on a resistor (old method to have I/Q with 26 pin header from raspberry pi B version).
If you have a 40 pin header, the easiest way is to wire Pin 33 for example to pin 23.
I have to test on 4.4..I am still on 4.1 kernel ! Thanks for pointing it.
About GPIO pin : Pin 23 doesn't handle Q : because the original PCB seems that the signal is getting from a wire soldered on a resistor (old method to have I/Q with 26 pin header from raspberry pi B version).
If you have a 40 pin header, the easiest way is to wire Pin 33 for example to pin 23.
Re: rpidatv update
Hi Evariste
Thanks for the reply. Is there any pin I could use on the 26 pin header? I would rather modify the plug in board than the PI. I can use a jumper lead but its not so neat. I expect this will be the same for several builders.
Hopefully the next iteration of the PCB will use the 40 pin header and include all the facilities for control and connections for the touch screen.
Mike
Thanks for the reply. Is there any pin I could use on the 26 pin header? I would rather modify the plug in board than the PI. I can use a jumper lead but its not so neat. I expect this will be the same for several builders.
Hopefully the next iteration of the PCB will use the 40 pin header and include all the facilities for control and connections for the touch screen.
Mike