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/APJN3MA7KMXY7A7ETRU3ZNEQMRS46PZO/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "APJN3MA7KMXY7A7ETRU3ZNEQMRS46PZO",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/OABE3MIGX3YDWBRWF3CV6DOFYWJA7UJG/",
    "sender": {
        "address": "greencl (a) mindspring.com",
        "mailman_id": "5421c5ff9a12494f8f7bd304db4ac696",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/5421c5ff9a12494f8f7bd304db4ac696/emails/"
    },
    "sender_name": "Chuck Green",
    "subject": "[eagle] Re: CAN-Do noise abatement plan and questions",
    "date": "2007-06-13T14:24:13Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/OABE3MIGX3YDWBRWF3CV6DOFYWJA7UJG/",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/2EZIKXK2X6RNEMHVS43I5NQVXFPPMCSC/",
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/HMGU3BDCVUJ7M73TUIGPN3PRNESB4MFC/"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi Juan,\n\nI'll take a cut at some of your questions and let Stephen correct me.\n\nJuan Rivera wrote:\n>\n> Good morning Stephen,\n>\n> I do have a few questions. Thanks for asking!\n>\n> 1) What if the CAN-Do module suffers a failure that causes a current \n> overload? Is it protected by a fuse? The next generation receiver \n> should continue to function as long as it has power. An overload in \n> either unit should not cause the other to fail.\n>\nThe CAN-Do! does have a 2 amp fuse at it's power input. The switched \ncurrent to the module also goes through this fuse. If the module mission \nrequires it to be impervious to the condition of this fuse, then \nadditional power input to the box is needed. If this power requirement \nis small (less than a couple of amps) then you could use one or more of \nthe \"user\" pins on the CAN-Do! If the power requirements are large (such \nas a transmitter) then an external connector should be used and that \npower controlled by the CAN-Do! supplied \"switched\" power. In either \ncase, the module design should measure the current and provide that as \ntelemetry (more on telemetry below).\n>\n> 2) Do you have any information of previous efforts to reduce CAN-Do \n> noise by either shielding the module or replacing the inductor with a \n> shielded version?\n>\nI think you are the first.\n>\n> 3) Do you have a shielded inductor that I could swap for the existing \n> one if that proved necessary?\n>\nNone has been looked for.\n>\n> 4) Have you designed a circuit that would allow temperature to be \n> determined inside the receiver PCB itself, and not just on the CAN-Do \n> module? This will be important, especially if the receiver is split \n> into two separate enclosures.\n>\nThere are some \"user\" analog inputs to the CAN-Do! that can be used for \nthis or any other analog thing you want included in the telemetry.\n>\n> My plan is to desolder the CAN-Do module from the receiver PCB today \n> and move the receiver PCB to the enclosure’s rear set of mounts. This \n> will put about 2-inches of space between the two. I’ll make up two \n> interconnecting cables – one just long enough to attach the two while \n> in the case, and one that is a foot or two long, assuming that I can \n> find the parts I need and don’t have to solder the cable to the two \n> units. I can use that long cable to try some troubleshooting. I’ll use \n> that CAN-Do’s noisy inductor as the noise source and move it around \n> over the receiver to see what affect it has. Perhaps I can find the \n> area that is the most susceptible to noise that way.\n>\n> I think the next receiver could use the entire available board space to:\n>\n> 1) Put distance between the two modules\n>\n> 2) Further isolate the CAN-Do module with a shield if necessary\n>\n> 3) Add power supply input filtering and input current overload protection\n>\n> 4) Include CAN-Do data line filtering if that turns out to be necessary\n>\n> 5) Add a temperature sensor in the vicinity of the SAW filters, and \n> another on the second PCB if it gets split into two sections\n>\n> One last question… How do I reduce the heartbeat timing below three \n> seconds? I couldn’t find any way to do that using the net controller. \n> I’d like to confirm that the jump in frequency I see in the CAN-Do \n> module’s 5 kHz noise every three seconds goes away.\n>\nI think your question is \"How do I stop the CAN-Do! from having its \nwatchdog time out?\" You can't change the length of the watchdog timeout \nas that is set by the firmware in the CAN-Do! Sending the CAN-Do! \nconfig. packets at intervals of less that three seconds should stop the \nCAN-Do! from resetting. It is intended that the IHU will do this in the \nsatellite at 20 ms intervals while collecting telemetry.\n\nI hope this helps,\nChuck\n>\n> 73,\n>\n> Juan\n>\n> ------------------------------------------------------------------------\n>\n> *From:* [email protected] [mailto:[email protected]] *On Behalf Of \n> *Stephen Moraco\n> *Sent:* Tuesday, June 12, 2007 7:21 PM\n> *To:* Juan Rivera; Juan Rivera\n> *Cc:* Jim Sanford; Bdale Garbee\n> *Subject:* late to tonight's meeting\n>\n> Juan,\n>\n> Sorry I missed your presentation/discussion tonight.\n>\n> Any questions/issues for me re: CAN Do! ?\n>\n> Regards,\n> Stephen\n> --\n>\n> [email protected] <mailto:[email protected]>\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",
    "attachments": []
}