Posts by PY2RN

    Hi G0MJW thanks, yes the audio is a chapter apart that I am still working on, force H.265 compliant box is checked otherwise my image appears grey distorted, regarding the overriding issue I erased the h265 box ip addr so it is going through multicast mainstream udp, I noticed the throughput got worse.


    Hi, trying to implement "poor man H.265 encoding solution" using these H.265 Encoder Box available from AliExpress.

    Using Pluto with latest alpha 2908 firmware version from F5OEO, even following the good guide by F5UII the images are going out OK but still struggling to get the audio out. Some points intrigues me:

    1.As soon as Pluto boots up it overrides the previous configuration saved in the H.265 encoder box to this shown in picture A, so I need manually to change the config back as shown in picture B. Is there any way to avoid it?

    2. Also when Pluto boots up it already starts with PTT ON, is it possible to change this condition on start?

    3. Using the UDP option as described in F5OEO documentation page (picture C) it would be an option to the HDMI connection or it is necessary to be configured anyways? My H.265 box here would not accept Sub-Stream set, only main-stream when Pluto is connected (picture D) or we must change something in the H.264/H.265 Control menu? (Figure E)

    Thanks and sorry for excess of pictures, next time better I make a movie! :)


    DD0KP Heiner, deleting the callsign did not solve but it helped someway to monitor the problem between the variations it shows: blank, py2rn, unassigned and nocall.

    In my case loading the original v0.31 pluto.frm AND boot.frm then f5oeo beta for the brave solved the issue and Pluto TX is normal now.



    Ed PY2RN

    Hi all, I am running F5OEO beta firmware+OBS with no problems, but when I load the F5OEO Beta for the Brave version my Pluto will not TX, I can see OBS is streaming via rtmp OK to Pluto but no TX, anyone knows what it could be?


    Ed PY2RN

    I started my activity on QO-100 in Feb/2019 with great enthusiasm, I am on satellite operation/experiments since 80's with the Radio Sputink series and a first GEO for Amateur Radio certainly is a huge deflection point, but since several months I am losing interest to be active on the NB SSB, mostly no longer answer CQs and also do not make CQs as used to, the fact is that there is an increasing number of "police" operators that feels in the right to intrude in the middle of a conversation and start talking at the same time, then when you give him the opportunity to talk they come to complain about something: audio, signal level, splatter etc. I always ask the callsign, usually they do not give it but others do, anyway, this is very impolite to start talking and cause interruption on the same frequency when a qso had been already in progress unless it is an emergency, the complains are usually pointless since it was not causing LEILA trigger or affecting adjacent QSOs, with this SDR waterfall fever many does not know how to adjust it correctly and see / amplify things that actually does not exist and wouldn't be noticeable in a normal analog rig, but even though some "police" operators get not satisfied and start generating QRM over the QSO, blowing on the microphone, music, re-transmitting other stations, triggering LEILA on purpose etc. Just as a remembering : not everyone has the opportunity to buy an IC-9700, a super precise SDR or an expensive transverter, even if they do it will need to learn and adjust them first, also others use 100% home brew equipment that may be not as precise as the IC-9700 TX DSP to generate a perfect square in your waterfall, so be civilized, ask to enter in a frequency politely, or wait to the qso to finish and call the other station in a civilized manner or even send an email to avoid pointless discussions on the transponder, I have heard this happening to several stations / QSOs on the transponder (ssb portion) in may occasions, this type of aggressive approach will not contribute to save the transponder in any way.


    Ed PY2RN


    Hi Ed,

    Portsdown is a hardware system for DATV: I am using the 2019 version, but with vMix. I have tried OBS and Pluto, but without success so far. rtmp and udp don't work here. I am also interested to see the right settings and the proper script for H265. If you are using Pluto, I think you don't need any Portsdown hard- or software, just the right OBS settings. Maybe someone could point us to the right information.


    Gerhard OE3GBB

    Hi Robert,

    I have an i7/16GB Windows10 . My display cards are AMD Radeon HD 6450 (I have two in the PC)

    Thank you

    Ed PY2RN

    Hello, working to get everything ready to transmit DVB-S2 DATV via QO-100 from GG66LW.

    I noticed that Pluto with F5OEO firmware and OBS Studio is almost standard among the stations I watch on DATV, I tried to search several places on how to configure OBS Studio but either it was too basic or not clear. I just installed OBS Studio sftware here, I never used this software before for anything so I don't even know where to start configuring it. Along OBS studio I also installed VNC and FFMPEG ( well, ffmpeg is a difficulty apart, there is no installation, just throwing the files inside C:/FFMPEG ?? ) What about " Portsdown " is it needed? Is it a hardware or a software?

    So if you please have any information to share or indicate I would appreciate.

    PS: I am aware about this wiki: but it is not clear/too advanced to me.

    Thank you.

    Ed PY2RN


    Several people still do not use LoTW and many others do not include PROP_MODE and BAND set correctly. But it is getting little better since one year ago :)

    <call:5>df3qe <qso_date:8>20200206 <time_on:4>1504 <sat_name:6>QO-100 <band:4>13cm <mode:2>CW OPTIONAL
    <qslmsg:43>tks fb qso via qo-100 sat. Pls cfm via lotw

    73 de ED PY2RN

    I’m wandering how many from the 86 DXCC countries had been verified by LoTW? I have a record of 3 1/2 to 1!!!

    I got today the nice QSL card from TR8CA. Can you hold LOTW in your hand ?

    "Life is long enough to collect nice QSL cards" ;)

    @HB9SKA Please do not confuse QSL card exchange with LoTW confirmation, they are different things and one does not replace the other :) LoTW is a very smart and economic way to request diplomas, but the QSL card is a good remembering of a contact.

    73 de Ed PY2RN

    My QO-100 most wanted! :)

    Entity Prefix Status Call 1 Call 2 Call 3 Call 4 Call 5 Call 6
    Georgia 4L W 4l/sp9dlm
    Montenegro 4O W 4O6AH 4O5JD
    ITU HQ 4U1I W 4U1ITU
    Madagascar 5R W 5R8IC
    West Malaysia 9M2 W 9M2CQC 9M62MY
    Nepal 9N W 9N1AA
    Botswana A2 W A21EME
    United Arab Emirates A6 W A65DC
    Bahrain A9 W A92GR
    The Gambia C5 W C5WP
    Morocco CN W CN8BD
    Cape Verde D4 W D44TWO
    Liberia EL W EL2DT
    Estonia ES W ES5PC ES9B
    Belarus EW W EU2AA EW6FS EU/AI6YP
    Reunion Island FR W FR4OO FR4KF FR4LI FR5FC FR1GF FR4KM/P
    Isle Of Man GD W GT3PYE/P
    Thailand HS W HS0AJ
    Djibouti J2 W J28PJ
    Luxembourg LX W LX1BB LX1WJ LX2MG LX2LA
    Bangladesh S2 W S21ON
    Sudan ST W ST2NH
    Crete SV9 W SV9IOQ SV9ANK
    Ukraine UT W
    Serbia YU W YT7VG YU7BPQ

    I think one of the biggest challenges today is to get a good measurements of our TX power, almost 100% of the OMs heard reports "my power is about / aprox / near / something between x and y Watts" obviously this excludes those few lucky ones with access to professional instruments. In my knowledge the only "amateur" instrument that reaches up to 2.4GHz is the Daiwa CN-801S-II Meter which costs almost the same of a fully ready to go QO-100 station, and the not less expensive and hard to find Bird slugs. Few months ago I got one of this Chinese digital power meter (picture) that claims go from 1MHz to 5GHz, cheap, but so far can not tell if it is functional.

    Their specs:

    Measuring power range: -45~-5 dBm (external RF attenuator can be extended to 80dBm)

    Measurement resolution: 0.1 dBm power

    Measurement frequency range: 1 1MHz-5GHz

    Measured power: 1nW ~ 2W

    Working voltage: 5V DC (direct selection MICRO-USB powered)

    Working current: <50 mA

    Working temperature: -40 ° ~ 65 ° degrees Celsius

    I just found that injecting a 0dBm @ 2.4GHz from a trustable source it displays -19.0dBm so I suppose I will need to input +19dBm in the correction factor to start, so I placed an external 20.4dB attenuator which brings the correction to +39.4dB.

    Using SDR-Console I generated a CW tone on 2.4GHz @ 100% drive and got about 12.5dBm readout (picture), so for me it seems a little exaggerated but it is what is showing. Please let me know if you had made any testing with this type of instrument and the results, also how did you calibrated it?

    Thanks, 73

    Ed PY2RN