Show an email

GET /hyperkitty/api/list/[email protected]/email/2S4PLAMXYE7BXBT5P76JFHTXVOKVEPNK/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2S4PLAMXYE7BXBT5P76JFHTXVOKVEPNK/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "2S4PLAMXYE7BXBT5P76JFHTXVOKVEPNK",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/RQX4DLDIYY3MVVVNFRFO357N5UXLTUIQ/?format=api",
    "sender": {
        "address": "kc0ftq (a) amsat.org",
        "mailman_id": "ba1a40f6c28b40e4ae4bb8725a211491",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/ba1a40f6c28b40e4ae4bb8725a211491/emails/?format=api"
    },
    "sender_name": "Stephen Moraco",
    "subject": "[eagle] Re: CAN-Do-Too! ??????????",
    "date": "2007-07-09T16:31:12Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/67GB3DVX35OY2RFF2TT6GQAONRPIJWWI/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Chuck, Lyle,\n\n   Good to hear from you.  I'm excited to see a plan forming!\n\n   You probably expect this but I want to confirm... you have\n   my support for the firmware, User's Guide authoring, control\n   software development, etc.\n\nRegards,\nStephen\n--\n\n\nOn 7/9/07, Chuck Green <[email protected]> wrote:\n>\n> Hi Guys,\n>\n> Juan has done a lot of outstanding work which resulted in some\n> substantial critiquing of the CAN-Do!  (Affectionately called a\n> \"widget.\")  It is unfortunate that it has taken several years since the\n> CAN-Do! was designed and then 100 units built before an application of\n> sufficient sensitivity used it to discover it's shortcomings.  History\n> can provide lessons that I hope we can learn from, but it seldom\n> provides solutions to the problems encountered.  Lyle and I have\n> exchanged a few thoughts privately and it seems it may now be time to\n> consider solutions to the problems found.\n>\n> The only practical way to accomplish this is to develop the next\n> generation CAN interface device.  Dare I call it the CAN-Do-Too!  ?\n>\n> All technical specifications should remain the same.  What this really\n> means is that a next-generation controller must run *exactly* the same\n> firmware currently running the CAN-Do! .\n>\n> All specifications added or redefined should be carefully defined and be\n> measurable.\n>\n> General specifications that we worked from before were that the widget\n> should use as little power as possible and consume as little of a\n> module's volume as possible.  The first of these should remain the same,\n> \"use as little power as possible.\"\n>\n> But the second should be changed to \"consume as little of the connector\n> panel space as possible\" even if it means consuming a little more of the\n> module volume.  This means the widget PCB and components should not\n> extend beyond the dimensions of the DA-15P connector in either\n> dimension.  A possible compromise to this would be to let the PCB run\n> past one end of the DA-15P but not more than the DA-15P is forced away\n> from the side of the box by the box design.\n>\n> The power supply could be completely redesigned.  Or the inductor of the\n> existing supply could be exchanged for one that is a toroid (the\n> existing one is not).  If someone wants to step up and design a new\n> power supply, great!  If not, then we would simply change the inductor.\n> I'd sure like to see someone take this on.  With so many of these in the\n> satellite, only a few milliwatts is important.  And the noise issue Juan\n> uncovered is *very* important.\n>\n> It may be that some, or maybe all, of the widget should be enclosed in a\n> metal box.  It may be that just changing the inductor would allow a new\n> widget to meet the yet-to-be-defined noise specifications.\n>\n> The input power filter for module power should be separate from the\n> widget power supply input filter.  The module power filter is a filter\n> that will not meet all module requirements, but would likely meet the\n> requirements of a digital module.  Some modules, such as receivers, may\n> need additional power conditioning.  But in any case, the widget power\n> supply should not add to the module power supply noise.\n>\n> There should be a simple way to disconnect the filter capacitors on the\n> widget from the data lines when the widget is in Byte mode.  Most people\n> are not aware of this problem which was uncovered by another module\n> builder.  It only effects those using the CAN-Do! in Byte mode.\n>\n> Using a synchronizing signal does not seem practical to us.  It would\n> complicate the design of the widget power supply so that it would\n> function with or without the presence of the synchronizing signal (we\n> don't want to introduce a single-point-of-failure).  It would\n> dramatically increase the satellite wiring harness complexity, something\n> the widget was intended to a simplify.  And it would inhibit the widget\n> power supply from going into various power-saving modes.\n>\n> Recruit some new people into this project.  Lyle simply doesn't have any\n> time for doing new designs right now.  We need a power supply designer\n> as stated above.  And my time is limited.  I'm willing to lay out the\n> new design and build a few prototypes, but I need others to do parts\n> procurement and volume building of widgets.  I'll prepare flight units\n> if desired.  We've talked about having someone skilled in parts\n> procurement before but I don't know of anything having come of it.  The\n> bottom line, if this is going to happen, Lyle and I need others to be\n> involved.\n>\n> If you think this is a good idea, or bad, please express yourself.  And\n> if you have other comments to add to the above, or would like to\n> modify/expand on above comments, please do so.\n>\n> Looking forward to your comments,\n>\n> Chuck and Lyle\n> _______________________________________________\n> Via the Eagle mailing list courtesy of AMSAT-NA\n> [email protected]\n> http://amsat.org/mailman/listinfo/eagle\n>\n\n\n\n-- \nRegards,\nStephen\n--\n\[email protected]\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2S4PLAMXYE7BXBT5P76JFHTXVOKVEPNK/?format=api",
            "counter": 2,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "iso-8859-1",
            "size": 6140,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/2S4PLAMXYE7BXBT5P76JFHTXVOKVEPNK/attachment/2/attachment.html"
        }
    ]
}