Posts by CT1EAT

    Dear All


    I am trying to compile a list of all the grids where DP0POL/MM operated from.

    Here is what I got so far (in chronological order).


    IL27

    HK98

    HK97

    HK82

    HJ89

    HJ99

    HJ98

    HJ95

    HJ94

    HJ93

    HJ90

    HI91

    HI90

    HH99

    IH09

    IH05

    IG09

    IG08

    IG04

    IG10

    IF19

    IF10

    IE17

    IE26

    IE25


    Please let me know of any errors/omissions.

    Thank you.


    73 CT1EAT/M0HOJ

    ... may be, in Germany one speaks of greetings, but also many greetings (viele Grüße), so the "s" has its justification as an increase ...

    Same as Portuguese (Muitos Cumprimentos), but that still does not make "73s" correct.


    73 FCosta, CT1EAT/M0HOJ

    Hallo Flo


    Thank you for the correction. You are a good cop ;)


    73 F.Costa, CT1EAT/M0HOJ


    P.S. By the way, "73" is "plural", so you don't need the "s".

    FYI, I did the same mistake 30 years ago (after I became an amateur) and I was corrected by an american ham :)

    Dear All


    Everybody is aware of the amateur radio "policemen".

    They are on every band, on every mode and, of course, on QO-100.

    I don't want to discuss their reason to exist, but I want to say a few words about their activity.

    Today afternoon, one station was enjoying the first day of being active on this satellite. Unfortunately, the operator didn't not notice he was exceeding the typical SSB bw (3kHz).

    (Ok, we could argue that is not an excuse and all operators should operate according to the rules in all circumstances. Yes, fair enough. But we all know not all operators are young, bright, smart or tech savy. That is the reality and we can't ignore it.)

    As you can expect, It didn't took longer for a station to call the QO-100 newbie, not to welcome him, but to say he should reduce his bandwidth. He was not looking to make QSO, he didn't bother to gave his name, report or grid locator. No, he just asked to reduce the BW. He didn't asked if the newbie knew what he was talking about or offer any help/advice on how to fix the issue. No, he just asked to reduce the BW, again. (he did say his call, however. I aplaud that. Not all "policemen" identify themselfs)

    How do I know all of this? Because I heard that intereaction first, and then did QSO with the newbie station. He was clearly puzzled with the previous caller. So I explain him the problem and the usual ways to fix it.

    Having said that, I understand this is a cultural thing and I don't expect the "policemen" to be tolerant. But I would like them to be, at least, more helpful. Thank you in advance.

    See you on QO-100


    73 FCosta, CT1EAT/M0HOJ

    Hi Trevor


    Although this might have no relation with your Pluto, I will share my experience, just in case.


    After I did the GND mod to my Pluto, the computer no longer recognized it. Better said, the computer did recognize the USB device (for second or so), but then the disconnected, then connected again... I couldn't understand out what was going on.

    I searched the foruns, including this one, and I couldn't see anything similar. I decided to disconned the external antenna (Comet GP-3 V/UHF vertical) and, for my surprise it worked fine. I connected the external antenna again, just to be sure, and again the Pluto stop working! So I have no doubt, the antenna has caused the USB crashes!

    I have no explanation for this, but I am preety sure some clever guy will know what is going on.


    On another note, the suggested 1.8V_CLK point (to supply the new TCXO), close to C170, is dead on my unit. I used a point close to C150 instead and works fine.


    Good luck


    73 FCosta, CT1EAT/M0HOJ

    Nice DXCC List. Seems that OX (North America) is issing in the list, which has a low elevation access to QO-100 from some of the villages on the East Coast. Otherwise a nice complete list.


    73, Oscar

    Hi Oscar


    Well spotted. My mistake. Here is the explanation. I started with the full latest DXCC list. Then I sorted by continents, and after I deleted the entities that were not covered by QO-100 theoretical footprint. I guess I thought it was safe to delete all NA, but my assumption was wrong.

    Thank you for pointing that. Revised list attached.

    Good Dx

    73 FCosta, CT1EAT/M0HOJ

    Hi David


    I did the same exercise some time ago.

    First I draw the theoretical footprint of the sat based on the position and distance from the earth. Then I generated the DXCC list.

    See files attached.


    73 FCosta CT1EAT/M0HOJ

    Files

    • qo100_dxcc.zip

      (20.06 kB, downloaded 188 times, last: )

    Dear OM


    I understand we can't all like the same.

    What I don't understand is why don't let other do whatever they like.

    Is FT4 necessary? No. Neither is SSB, CW, or any other mode. We just do it because we can and because we like it.

    So, yes, as long as it is not against the rules, do whatever you fancy, and let other do whatever they fancy.


    73 FCosta, CT1EAT/M0HOJ

    Dear All


    For those who use SDR# software, you can add the lines below on BandPlan.xml file to easily comply with new NB transponder band plan.


    <RangeEntry minFrequency="10489500000" maxFrequency="10489505000" mode="CW" step="10" color="red">EB</RangeEntry>

    <RangeEntry minFrequency="10489505000" maxFrequency="10489540000" mode="CW" step="10" color="blue">CW</RangeEntry>

    <RangeEntry minFrequency="10489540000" maxFrequency="10489580000" mode="USB" step="10" color="navy">NB DIGI</RangeEntry>

    <RangeEntry minFrequency="10489580000" maxFrequency="10489650000" mode="USB" step="10" color="yellow">DIGI</RangeEntry>

    <RangeEntry minFrequency="10489650000" maxFrequency="10489745000" mode="USB" step="10" color="green">SSB</RangeEntry>

    <RangeEntry minFrequency="10489745000" maxFrequency="10489755000" mode="CW" step="10" color="red">EB</RangeEntry>

    <RangeEntry minFrequency="10489755000" maxFrequency="10489850000" mode="USB" step="10" color="green">SSB</RangeEntry>

    <RangeEntry minFrequency="10489850000" maxFrequency="10489995000" mode="USB" step="10" color="brown">MIXED</RangeEntry>

    <RangeEntry minFrequency="10489995000" maxFrequency="10490000000" mode="CW" step="10" color="red">EB</RangeEntry>


    It looks like this






    73 FCosta, CT1EAT/M0HOJ

    Satellite via QO100 shouldn't count for DXCC because there is no propagation skill. If you build the capability to work one station then you have capability to work them all. Working as many different stations as you can is valid but that's not DXCC. It shouldn't matter where those stations are and all are equally valued, which is the antithesis of DXCC. Let's evolve beyond HF DX.


    With all respect, I strongly disagree.

    If you reduce Dxing to "propagation skill", you probably haven't Dx before.


    Dxing is much more than making a fast contact!

    You need to:

    - get the best equipment you can afford (not critical on QO-100, I agree)

    - be continiously informed of all future activities

    - be available during the Dx activity

    - improve operation skills

    - work the Dx

    - get the QSL card (sometimes it's harder than all mentioned aboved combined)

    - apply for the award once you achieve it.

    This could take years, decades, or a life time!

    Yes, in case of QO-100 there is a limit of DXCC (200 or so) and operating years (15, I have been told).

    Yet, for someone who don't have any chance to have a decent HF/VHF station in the current QTH, this is much better than nothing!


    Last, but not least, I do understand not everybody fancies Dxing or support it.

    What I do not understand is the criticism to those who like it.

    I always believed amateur radio world is big enough and there is room for everybody.

    Just do whatever you fancy and let others have their fun.


    73 FCosta, CT1EAT/M0HOJ

    Dear All


    Here are my tips for Dxing on QO-100


    DX side

    - Announce your activity previously going on air, with all the relevant details (e.g. Dates, Schedule, Grid Locator, QSL information, equipment, etc.). The purpose of doing so is to warn potential interested amateurs in advance and avoid to repeat on air (over and over) the same information.

    - If you can't pick up full calls due pileup, WORK SPLIT. Just listen a few kHz up (or in a range, if the pile up is too big.) DO NOT work by numbers, take lists or ask just the "last 2" (partial call). Those "systems" are useless and unfair.

    - Whatever rules you make, DON'T BREAK THEM. If you do, the pile up will have no respect for you and will break them too.

    - Make sure YOU are always in control. Leave no room for ambiguity or any opportunity for anyone to break in.


    Pileup side

    - Have patience. If you don't have, turn off your radio and return a couple hours later. The pile-up is probably over by then.

    - Increase your ability, not your power. Unlikely on HF, driving more power will not increase your chances to beat the pileup, but trigger LEILA instead.

    - Don't spoil others fun. Once the pileup is over you will have plenty of time to have a long chat and tell the Dx station all about your setup, wx, etc. so, unless been asked, please refrain to do that while others are still struggling to work the Dx.

    - Report activity on DX Cluster e.g. http://www.dxsummit.fi/ spotting Downlink frequency (eg 10489700)


    For more tips (written for HF, but partially applicable to SAT as well) , go to https://www.hamradio-operating-ethics.org/ and download the slide set on your language.


    See you on QO-100 pileups


    73 FCosta, M0HOJ/CT1EAT