Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/A5V4VHLCW3ZG3BDJBNXY5UNM5CTVAJMK/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "A5V4VHLCW3ZG3BDJBNXY5UNM5CTVAJMK",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/RJRBBEQ5TZQVS5WULMUJILG3CB7VF54Z/?format=api",
    "sender": {
        "address": "hans.bx2abt (a) msa.hinet.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Hans BX2ABT",
    "subject": "Re: [amsat-bb] How to digipeat?",
    "date": "2019-09-08T14:51:31Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/KRB4ZVIO37WDPEMVOLWG45VMMP4JPTN5/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hello Scott,\n\nThank you so much for writing this long reply. We should archive it for \nfuture use, because this is very comprehensive.\n\nJust by trying many options I was able to get UISS to send something out \non Falconsat-3. I tried CQ, ARISS, and BEACON and used the FPS3-1 as \npath. Half an hour later on Twitter I received a notification from \nE29AHU in Thailand that he saw my digipeat on his soundmodem output. \nThere are some tweets on Twitter with screenshots, so just search for \nBX2ABT. So a little success and at least I know UISS is working.\n\nUnfortunately, if this whole digipeating means there is no \nstore-and-forward and you need iGates to be able to see your digipeats \non the web then I won't have much fun with this, because here in east \nAsia it is very quiet. There were some JA hams working the FS-3 BBS and \nalso digipeating, but they have been inactive lately. Maybe I can \npersuade them to do some experimenting with me.\n\n73 de Hans\n\nBX2ABT\n\n\nOn 09/08/2019 04:35 AM, Scott via AMSAT-BB wrote:\n> Hi Hans!\n>\n> Like any digital mode, 1200 or 9600 packet requires several things to work\n> together using the correct settings.  This might run a little long, but\n> I'll be glad to outline them.\n>\n> But first, one helpful thing to remember is that you want to treat the\n> uplink & downlink as completely separate affairs.  Depending on the\n> satellite, the uplink and downlink might find you using different bands,\n> different radios, different antennas, different software... at a MINIMUM\n> you'll be using different RF frequencies even if it's a simplex packet\n> digipeater since the doppler compensation will be opposite for up -vs-\n> down. (caveat - on 2m normal FM you can get by with sitting on one freq)\n>   To me it's always made sense to verify that you're 100% good to go on the\n> downlink, then set yourself up for the uplink.\n>\n> So, if anyone wants to read on, here are the things to consider.\n>\n> RF:  you'll need to know what the uplink & downlink RF frequencies are and\n> if either is in the 70cm band, doppler compensation is mandatory.  Here's a\n> tip: several of the newer sats are using NARROW-FM... even if you're\n> working on 2 meters, doppler compensation to/from a narrow-band satellite\n> radio is making a huge difference in my experience.  CAT control your radio\n> if possible; if not, then pre-program 5 memory channels the way most people\n> have their FM radios setup for voice satellite work.\n>\n> MOD/DEMOD:  your radio needs to have a connection to your computer where\n> you run software set to decode the type of modulation in use by the\n> satellite.  On Windows, the various UZ7HO Soundmodem versions provide\n> perhaps the easiest interface to work with.  Direwolf is an option on\n> Windows, too, and by-the-way makes for a very easy to use iGate utility\n> running off to the side of your screen.  On linux, Direwolf is the most\n> popular option to my knowledge.  On either platform, of course we have to\n> find out from the satellite documentation what settings are required.  A\n> critical note that often prevents success on rates above 1200 baud is that\n> beyond that speed we need more audio bandwidth than is normally available\n> for general listening.  So, whether you're using a \"real\" radio or an SDR,\n> good rules of thumb are 3KHz of audio bandwidth for 1200 baud and 15KHz of\n> audio bandwidth for the higher rates.  On modern radios, that means using a\n> connection to the radio's \"DATA\" port for rates above 1200.  My TM-V71A,\n> for example, also has a menu option to switch between 1200 & 9600 - very\n> important!\n>\n> USER INTERFACE:  as you mentioned, the UISS software is a great tool to use\n> as the interface when sending/receiving the packet modes.  It communicates\n> with UZ7HO Soundmodem or Direwolf to send/receive data to/from the\n> satellite.  But what to transmit?  We need that info from the satellite\n> documentation.  The \"TO\" is most often \"CQ\", but read everything you can\n> find about the satellite in question to be sure. (hint: monitor the\n> downlink & see what others are using!)  The \"VIA\" can be confusing because\n> many sats will respond to more than one name.  It all comes down to the\n> documentation - historically the 1200 baud APRS sats will answer to \"ARISS\"\n> which is handy... you don't have to change all your settings between\n> satellites.  FalconSat-3 is different; we use \"PFS3-1\" when transmitting to\n> FS-3.  \"If\" there actually is an active digipeater on BugSat-1, the team\n> has instructed us to use \"LU7AA\" as the call sign to access that satellite.\n> (I've tried BugSat-1 twice now but at the time of this post, have not had\n> any success)  As for the payload text to transmit, UISS helps a lot (for\n> APRS sats) by guiding us into sending properly formatted 'TEXT',\n> 'POSITION', and 'MESSAGE' type APRS packets.  Monitoring the downlink and\n> seeing what message types others are having success with is helpful here.\n> Heck, everything I do on the sats is a copy-cat of the operating techniques\n> used by the operators that you see post repeatedly here, on Twitter,\n> QRZ.com, and elsewhere.   A huge 'thank-you' to all who share how-to info!\n>\n> So, aside from individual considerations that are unique to particular\n> satellites (FS-3 is cross-band full-duplex, for example), that is an\n> overview.  If anyone has read this far, you have my sympathy.  I just\n> wanted to spell out what is common knowledge to most here on the chance\n> that one item might ring a bell and answer a question for you.  If the ISS\n> or either of the PSAT digipeaters would come back online, that would make\n> it a lot easier to practice with these modes.  As of the date I'm typing\n> this, all we have active over my location in the U.S.  are AISAT-1 (1200\n> narrow-FM) & FS-3 (9600).\n>\n> Good luck!\n>\n> -Scott,  K4KDR\n>\n> ===========================\n>\n> On Sat, Sep 7, 2019 at 11:01 AM Hans BX2ABT via AMSAT-BB <[email protected]>\n> wrote:\n>\n>> Hello all,\n>>\n>> Apparently my mail about BugSat-1 raised some interest into that bird's\n>> digipeater. But that still leaves me with the following question (and I\n>> hope I don't sound too obtuse): how do you digipeat? I've tried to\n>> understand it by googling it over the past year or so, but I still don't\n>> get it much. Most tutorials explain about setting it up, but with HTs. I\n>> am running a home station only, with the rig connected to a PC. From\n>> what I understand you need to use the program UISS then.\n>>\n>> I got as far as this: I installed UISS (under Wine) and got it connected\n>> to Direwolf. Right now I can work the Falconsat-3 BBS using PacSat\n>> Ground Station and while running that program I see the same messages\n>> that Direwolf displays also appearing in UISS. So far, so good, but then\n>> what? I press either F5, F6, or F7, but nothing happens. Yes, my rig\n>> burps out some data for a split second, but I can't find myself back on\n>> APRS.fi. So what am I doing wrong? Any parameters to adjust? Or are\n>> digipeats not stored for the next iGate to put it on the internet?\n>>\n>> Again, I hope I don't sound too witless, but I've never really\n>> understood APRS, apart from terrestrial position reporting and even that\n>> was kind of hard with all the paths and whatnot. Hope you nice people on\n>> this list can drop some pointers. 73 de Hans\n>>\n>> P.S. I've got some nasty local interference on 145.825 MHz and that\n>> makes receiving the ISS and other birds almost impossible. I was lucky\n>> to get two frames in from IO-86 the other day, because that was due\n>> south, with the QRM coming from the north-east. Getting a signal up\n>> shouldn't be much of a problem, though.\n>>\n> _______________________________________________\n> Sent via [email protected]. AMSAT-NA makes this open forum available\n> to all interested persons worldwide without requiring membership. Opinions expressed\n> are solely those of the author, and do not reflect the official views of AMSAT-NA.\n> Not an AMSAT-NA member? Join now to support the amateur satellite program!\n> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb\n>\n>\n>\n\n",
    "attachments": []
}