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/O7OOEZTG7IS35OKT7SV3B4FP3CHGWLXF/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "O7OOEZTG7IS35OKT7SV3B4FP3CHGWLXF",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/RQX4DLDIYY3MVVVNFRFO357N5UXLTUIQ/?format=api",
    "sender": {
        "address": "bill (a) hsmicrowave.com",
        "mailman_id": "d7ecbf0c1df148f289f27dd7a8c37974",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/d7ecbf0c1df148f289f27dd7a8c37974/emails/?format=api"
    },
    "sender_name": "Bill Ress",
    "subject": "[eagle] Re: CAN-Do-Too!   ??????????",
    "date": "2007-07-10T02:34:19Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ZOSQOIPBUZ4X4DNKUPEJLILX7SO5DWNK/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/RM4KDBP6S5CCZCIVDV2DU5ARLIK2QEVO/?format=api",
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/R7TO6BWWJJA6E3SXP3VDV55RN6ZHEE42/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Jim Sanford wrote:\n> 4.  EMI Spec:  You put a gun to my head, and I'm going to pull out the \n> MIL-STD, which is probably overkill, but MAYBE NOT.  I'd really prefer \n> that one of you guiys current in the INDUSTRIAL world take on this \n> task and come up with something good enough and reasonable.  In \n> general, I'd like to eliminate as much mass and extra \"touch\" labor in \n> the assembly process (multiple shields) as possible.  Bob Davis:  \n> Please weigh in here, if the possible milled modules simplify this \n> issue, please enlighten us.\nJim, I think an EMI spec pulled out of a MIL-STD would be an over kill \neffort and likely not representative of \"our\" real world. What we need \nis not assumptions but data reflecting what the hardware does. The \nproblem is that we don't have the hardware - and that's my issue. The \npower distribution circuits are what I call a \"top level\" subsystem \nwhich feeds \"everyone.\" Instead of working on the circuitry that will \nrun from it and trying to \"imagine\" what we can expect, let's focus on \nbreadboarding the key power distribution circuits and get some hard data \nso we know what we're working with.\n\nI'll again reiterate (as I have several times in the past) the same \nthing for the satellite's 10 MHz reference. It's another top level \n\"subsystem\" that will feed \"all\" LO's. Instead of guessing what we'll be \nworking with, let's get it defined too.\n\n(I'm proposing we put that one to bed and use the time tested, well \ndefined, high stability, low noise HP (OK - Agilent) 10811 series of \nreference standards used in most of their test instruments. If that \nwon't cut it - someone please tell me why!)\n> 7.  Requirements:  Bob McGwier is correct, we really did start with a \n> very top-level requirements document.  It is not perfect (Bob has \n> hated it from the word go), but can be found on EaglePedia under \n> Functional Requirements.  It is also in need of updating, after the \n> October BoD decision.  On my list to do.  Like you, I have finite \n> energy and time, but it is on my list.  I think John did an EXCELLENT \n> job of documenting the UHF Receiver requirements based on what he \n> knew.  The need for an EMI spec was not obvious, but is now, thanks to \n> Juan's testing efforts and exceptional documentation.  Lou:  \n> Functional requirements for power supplies?  Bob Davis:  Functional \n> requirements for structure and thermal performance?  etc. etc.....we \n> have much to do, but I think worthwhile effort.  By the way, I'm \n> reading (in a few spare minutes here and there) an EXCELLENT book on \n> requirements management.  When I finish, look for a review of it on my \n> project management page.  I will also be providing suggestions on \n> writing \"good\" requirements, based on that book and my recent \n> experiences in the day job.\n>\nYes, we have \"top level requirements\" for desired satellite functions, \noperating modes and parameters and link budgets. But again, I think \nwe're sorely lacking in key \"system\"  performance requirements based on \nreal data  - - -  which can only be obtained by building and testing \nthese key functions.\n\nI'm not a power supply guy, but I'll offer to assist in building and \ntesting the circuits we need to characterize. Lou - point me in the \nright direction - tell me what you need!\n\nRegards...Bill - N6GHz\n\n",
    "attachments": []
}