Posts by G0MJW

    What happened with ITU Resolution COM6/19 ? This problem was recognized in 2015 or earlier and should have been addressed at WRC 2019. :(

    Against the odds we were largely successful, due to a huge effort by many, in identifying spectrum for short duration missions. The result was:

    The frequency band 137.025–138 MHz may be used for short-duration missions, if they do not cause harmful interference and if they do not claim protection from other services. In this case, simplified filing procedures apply. For most countries, the coordination requirement Art. 9.21 was removed from the uplink band 148–149.9 MHz which enables it's use for these missions.

    It's not perfect but a good outcome given the circumstances.


    I will raise this with my ESA contacts to find out what has really happened.

    Regardless of what the IARU say, they don't have a veto over administrations who will always be able to authorise what they wish. Normally administrations do follow IARU guidance, so for one to not do so, is quite a problem. However, if a university or individual has acted independently here and for example claimed a permission they did not have, that needs to be dealt with appropriately.

    You say 95% of cubesats have nothing to do with amateur radio. That's not really true. More like 95% of cubesats have been enabled to exist through the creativity and work of radio amateurs. It's a sign of the value of amateur radio that such a large market for them now exists and this is evidence that justifies our continued access to these bands more than anything else. In fact, I can't think of any satellite that has not had a radio amateur significantly involved in the mission at some point.


    I expect you broke the tiny power chip. It can't be changed. If it is working with USB power via the power connector and USB data via the USB port then count yourself lucky and leave it like that. If not, have a look a the schematic to see how you can bypass it and feed 5V. That might work.


    It would be better to make a complaint of interference via your administration - but I am afraid commercial startups are using the amateur bands because they can and it's cheap and their administrations are prepared to accept it, so your argument is really with the country.

    Yes I saw that. Very interesting and why not as it is open source. However, unless it's an Analog Devices unit it should not have their logo on it.

    I don't see a GPIO connector. It's a pity they didn't take the opportunity to provide a proper 5V input.

    I took the risk on the original pluto ordering it will in advance of release. Someone else's turn to be guinea pig.


    If you want to use the ADALM-PLUTO DATV controller to set the parameters of the Pluto, you have to send the OBS data to the Pluto via UDP stream. Above you can see what has to be entered in OBD under "Output" "Recording". But what do you have to enter under "Stream" in the line "Server" and "Stream Key"?

    In my case nothing because I am not using streaming or recording. I am using the virtual webcam output and converting that with ffmpeg in a batch file.


    [user = '533'] SM7PNV [/ user] Those LNB's have been found months / years ago; -) (and also in use at several QO-100 stations & locked to GPS etc.)

    Point is, most fora don't have 'a memory' (it's more like a labyrinth), so everyone starts his own thread and invents his wheel: -)

    But this is useful - we would not want to forget how to make wheels.

    Hi Frans

    I anticipated that and the script for ffmpeg includes your encoder. This is the "vcodec hevc_nvenc" part. If you want to do it in OBS you need to select it similarly to me. Software encoding of H265 is hard and for most people, not really practical without hardware assistance of a graphics card. If you are sending H265 and your PC is not on fire, then you are probably already using the hardware encoder.


    Looking at this you have not set up any of the encoding parameters. Read the instructions at to use RTMP or look at what's written in the DATV forums. It's quite complicated to do this.

    for UDP your basic.ini in the OBS profile might contain text that looks something like this:


















    FFMCustom=max_delay=600 muxrate=7426 mpegts_original_network_id =1 mpegts_transport_stream_id=2 mpegts service_id=1 mpegts_start_pid=300 mpegts_pmt_start_pid=4096 pcr_period=40

    FFVCustom=profile=main level=4.0 rc=cbr_hq rc-lookahead=10 surfaces=2











    but really I don't recommend this as it's not so reliable. I prefer to use virtualcam plugin for OBS and do the encoding with a batch file. To do this you need ffmpeg installed on your PC but that opens up a much large range of options to try.

    There is a post about that on the BATC forum. You need to install the OBS Virtualcam plugin. I suppose you could just use a webcam with ffmpeg and no OBS. To test perhaps first send to VLC and you might try:

    c:\ffmpeg\bin\ffmpeg -f dshow -i video="OBS-Camera" -thread_queue_size 512 -f dshow -i audio="OBS-Audio" -vcodec hevc_nvenc -s 768x432 -r 15 -bf 0 -pix_fmt yuv420p -b:v 40k -preset slow -profile:v main -rc cbr_hq -rc-lookahead 5 -acodec aac -aac_coder twoloop -ar 48000 -ac 1 -b:a 24k -f mpegts -muxrate 170k -streamid 0:256 -streamid 1:257 -max_delay 2000000 -metadata service_provider="PE0F" -metadata service_name="Frans" -y "udp://"

    Which you can receive with VLC in the same way you direct minitioune output to VLC. Once working with VLC set parameters appropriately for your chosen symbol rate and fec and send to the pluto IP address and port. It should receive it. Make sure that force compliant (H265 Box) checkbox is off.


    My pluto has some custom firmware on it, it was preloaded by the seller, It is by some French Station for DATV I think ??

    Pre loaded by the seller - so this is a second hand unit with unknown history?

    So we probably now know why it doesn't work reliably. You have not correctly configured it via the web interface. When you access the web interface what do you get? please post the whole page. There should be a force compliant check box checked. It seems irrelevant but it's not.


    Trevor, I know it is frustrating but when everyone else has it working and you don't the likelihood is you have it wrong, not everyone else. Don't diss something when it's not necessarily at fault.

    Does it work plugged in to USB? If so it is your Ethernet adapter. In that case note that not all adaptors are supported by Pluto. I don't understand why you would take it apart and apply 5V. That seems very risky. You need to make sure it is one of the supported ones according to the analog devices website. .…otg_host_function_support

    Don't assume it is because it looks the same as they can be and often are different. Check it really is what it claims to be.

    If the adaptor is not the problem, then also why have you loaded F5OEO DATV firmware if you are not doing DATV? This firmware has many great features but it is not for absolute beginners who don't know what they are doing yet. Settings need to be made to work with SDR Console. That's easy to do via it's web interface, but you need to know what you are doing. Stick to the standard firmware for now.

    You say you went to have a QSO and it crashed - what does that mean. Did you activate a PTT somewhere? We know the Pluto is sensitive to PSU changes. Hence the ground mod. If by going to transmit you activated a relay that put a spike on the power line it will crash. Try it not connected to anything apart from the PC. If it works there, then that's your problem.

    Has it been modified in any way? If it has it's quite possible it has been broken. The USB power chips are easy to damage.

    If all else fails, return it via Digikey/Mouser and get a replacement.


    40 dB sounds pretty good with a 1m dish. Y ou can't expect much more I think without a better lens than the one Passion Radio supply. If you can't bear to break apart a Rocket LNB for its lens that the best seems to be the Rexolite version from HB9PZK. The the 3D printed one from HB9VQQ is not far behind. These are a dB or so better than the lens you have.

    It's very important the lens is at the focus and with some dishes you need to make mechanical adjustments to achieve this due to the larger size of the 2.4GHz feed.