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/Q4J6BL3PJRFDSUVWSQHYR3FLEJKAUHFR/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "Q4J6BL3PJRFDSUVWSQHYR3FLEJKAUHFR",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/SKIOQMZV7Q2MKTO7265BX7X7CS2P3JSG/",
    "sender": {
        "address": "kd6ire (a) sbcglobal.net",
        "mailman_id": "ee16508aab254d889b1ac3ee3c882683",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/ee16508aab254d889b1ac3ee3c882683/emails/"
    },
    "sender_name": "Don Ferguson",
    "subject": "[eagle] Re: YAHOO!!!! IT WORKS!!!!",
    "date": "2007-09-17T02:54:39Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/K54PD3UHAGMFFYRQY4HU2HTE5AZILGDC/",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/Q4WAYYRD2HU6CNONFFHVYLOJWMMHSKUM/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Jim,\n\nYou are correct that some documentation is necessary. The reason we did not\nrelate to this concern earlier was that when we received the Widget for the\nUHF Receiver I first communicated with it using CDNC and in doing a Query\nthe module returned its presence and created log records with the correct\naddress in them.\n\nI then used these original Log records to create the data stream to include\nthe initialization data for the U-Rx. The fact that these records already\ncontained the correct address, via CDNC Query, made the concept of Widget\nAddress a non issue.\n\nOur lack of understanding was not obvious until we attempted to use our\ninitialization stream on a different widget and the receiver failed to\nfunction. There was no noticeable indication from the CDNC program that the\nwidget addressed was not available. \n\nIt is now apparent that we will need to document this area and I will add\nsome documentation to the CAN-DO part of the U-RX ATP. Others will want to\nuse this experience to guide them in documenting their part of the Eagle\nproject.\n\nDon  \n\n-----Original Message-----\nFrom: [email protected] [mailto:[email protected]] On Behalf Of\nChuck Green\nSent: Sunday, September 16, 2007 5:53 PM\nTo: Jim Sanford\nCc: Robert McGwier; [email protected]\nSubject: [eagle] Re: YAHOO!!!! IT WORKS!!!!\n\nHi Jim,\n\nThe mode and address must be soldered onto the widget (jumper pads \nprovided on the widget for this purpose).  It is assumed that the module \nbuilder would do this.  It's that assumption that should be documented.  \nI say this to bring up the follow-on issue.\n\nThe module builder chooses the mode.\n\nThe address should be specified by the system administrator since the \naddresses must be unique for each module and the priority is a function \nof the address.  Module builders should give input to the system \nadministrator as to what they feel their priority should be, but \npresumably only the system administrator is in a position to know the \npriority requirements of *all* modules and is therefor in a position to \nmake these priority (address) decisions.\n\nChuck\n\nJim Sanford wrote:\n> Guys:\n> There's a lesson here:   DOCUMENTATION\n>\n> Juan expected/assumed one thing, the CAN-Do! widget was something \n> else.  Other teams will go through exactly the same issue.  SO, it \n> appears we need to add some documentation to each WIDGET in terms of \n> serial number, address, and probably a handful of other things I don't \n> know about. \n>\n> Let's learn from this experience.\n>\n> Juan, thanks to you and your team for perservering.\n>\n> Stephen, thanks for your prompt support on a short fuse.\n>\n> This kind of response and mutual support is exemplary, and what it \n> will take to get Eagle on orbit.\n>\n> Thanks & very 73,\n> Jim\n> [email protected]\n>\n>\n> Dave hartzell wrote:\n>> Wow, this is a relief.  I'm glad it was something simple....after all\n>> the hunting and pecking we did yesterday, I'm glad it was something so\n>> simple.\n>>\n>> I guess when the term \"bus\" is used, an address as probably key to\n>> getting to your destination.  ;-)\n>>\n>> Dave\n>>\n>> On 9/16/07, Juan Rivera <[email protected]> wrote:\n>>   \n>>> All,\n>>>\n>>> We need to take up a collection to buy Stephen a large hero badge.  He\nfixed\n>>> the problem and the receiver is now sitting on my bench happily\nreceiving a\n>>> signal.  The new CAN-Do module that he sent me had a different address\nthan\n>>> the old one and the old files were addressing the initialization\n>>> instructions to a non-existent device.  All we have to do is change the\n>>> address field in the initialization files and everything is fine.\n>>>\n>>> Whew!  The train of life in back on the tracks!\n>>>\n>>> 73 to all,\n>>>\n>>> Juan\n>>>\n>>>\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>>   \n> ------------------------------------------------------------------------\n>\n> _______________________________________________\n> Via the Eagle mailing list courtesy of AMSAT-NA\n> [email protected]\n> http://amsat.org/mailman/listinfo/eagle\n>   \n_______________________________________________\nVia the Eagle mailing list courtesy of AMSAT-NA\[email protected]\nhttp://amsat.org/mailman/listinfo/eagle\n\n\n",
    "attachments": []
}