Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/RNSYWXMO5E6MS4VDWK7HLOTB4PABMRJ2/
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/RNSYWXMO5E6MS4VDWK7HLOTB4PABMRJ2/", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/", "message_id": "CANsNeaohZqE8sSdiCDmJGEt-XH9xT_A7Vmq5GDWSBuo7xh5bGw@mail.gmail.com", "message_id_hash": "RNSYWXMO5E6MS4VDWK7HLOTB4PABMRJ2", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/RNSYWXMO5E6MS4VDWK7HLOTB4PABMRJ2/", "sender": { "address": "rich (a) ourowndomain.com", "mailman_id": "de4e965f89da4d4790638af3cb47f33c", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/de4e965f89da4d4790638af3cb47f33c/emails/" }, "sender_name": "Rich Gopstein", "subject": "[pacsat-dev] Re: Latchup Protection and Watchdog Parts", "date": "2023-01-20T13:38:56Z", "parent": null, "children": [], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "Good question... Maybe it was just during development you need to disable\nit in order to successfully flash new code since nothing would be resetting\nthe wd? I know on my board, the jumper is always in place so I don't know\nthat we've tested the hw wd.\n\nBtw, the tms570 has a software watchdog which we have code for and we have\ntested.\n\nI also vaguely recall a conversation about the timing of the hw wd. I don't\nremember if it was the wd on the 1.1 board or the 1.2 board, but Zach had\nproposed a chip with a maximum timeout of something pretty short - well\nunder a second. I was concerned that if something went south, the wd chip\nwould continuously power cycle the processor multiple times a second.\n\nThese conversations were from a while ago and I likely have the details\nwrong.\n\n\n\n\n\nOn Fri, Jan 20, 2023, 8:18 AM Jonathan Brandenburg via pacsat-dev <\[email protected]> wrote:\n\n> This I didn't know! Does anybody on the list know why the hardware\n> watchdog wasn't working as expected on the RT-IHU?\n>\n> Jonathan\n> On 1/19/23 17:43, Rich Gopstein wrote:\n>\n> And - as long as I'm thinking about it, we had to disable the hardware\n> watchdog on the RT-IHU to get it to run. I don't recall if that changed,\n> but if you get some RT-IHU boards, you might need to jumper the hardware WD\n> disable.\n>\n> Rich\n>\n>\n> On Thu, Jan 19, 2023 at 6:40 PM Rich Gopstein via pacsat-dev <\n> [email protected]> wrote:\n>\n>> Burns might remember the details (or Zach certainly would), but one of\n>> those parts was undersized for the RT-IHU and would cut out when we were\n>> transmitting with the ax5043. I think we had to back down the xmit power\n>> in order for the device not to reset.\n>>\n>> Rich\n>>\n>>\n>> On Thu, Jan 19, 2023 at 5:46 PM Jonathan Brandenburg via pacsat-dev <\n>> [email protected]> wrote:\n>>\n>>> In last week's meeting, I noted I had been looking at the schematics for\n>>> Fox-1 and RT-IHU and found the circuits for the latchup protection and\n>>> watchdog functions. I admit this might be basic to some, but I'm finding\n>>> it fascinating! Anyway...\n>>>\n>>> Since last week's meeting, I researched the parts used:\n>>>\n>>> onsemi FPF2001 is a current limit switch used on both Fox-1 and half the\n>>> RT-IHU. It's obsolete, replaced by onsemi's FPF2000. But the FPF2000 is\n>>> listed as end-of-life. It's replacement part is the TI TPS22942.\n>>>\n>>> MAX4995 is a current limit switch used on the other half of the. This\n>>> part looks good for new designs.\n>>>\n>>>\n>>> For the watchdog functionality, both Fox-1 and RT-IHU use the\n>>> STWD100NYWY3F chip. this parts looks good for new designs.\n>>>\n>>>\n>>> That's as far as I got. Next, I want to research the Fox-1 and RT-IHU\n>>> designs to determine the thresholds of the current limit switches. In\n>>> particular, I want to see if the TPS22942 is a suitable replacement,\n>>> assuming we have the same current requirements.\n>>>\n>>> That's where I'm at,\n>>>\n>>> Jonathan\n>>>\n>>>\n>>> --\n>>> Jonathan Brandenburg\n>>> Radio Amateur Satellite Corporation\n>>> 1-214-213-1066\n>>>\n>>>\n>>> -----------------------------------------------------------\n>>>\n>>> pacsat-dev mailing list -- [email protected]\n>>> View archives of this mailing list at\n>>> https://mailman.amsat.org/hyperkitty/list/[email protected]\n>>> To unsubscribe send an email to [email protected]\n>>> Manage all of your AMSAT-NA mailing list preferences at\n>>> https://mailman.amsat.org\n>>>\n>>\n>> -----------------------------------------------------------\n>>\n>> pacsat-dev mailing list -- [email protected]\n>> View archives of this mailing list at\n>> https://mailman.amsat.org/hyperkitty/list/[email protected]\n>> To unsubscribe send an email to [email protected]\n>> Manage all of your AMSAT-NA mailing list preferences at\n>> https://mailman.amsat.org\n>>\n> --\n> Jonathan Brandenburg\n> Radio Amateur Satellite Corporation\n> 1-214-213-1066\n>\n>\n> -----------------------------------------------------------\n>\n> pacsat-dev mailing list -- [email protected]\n> View archives of this mailing list at\n> https://mailman.amsat.org/hyperkitty/list/[email protected]\n> To unsubscribe send an email to [email protected]\n> Manage all of your AMSAT-NA mailing list preferences at\n> https://mailman.amsat.org\n>\n\n\n", "attachments": [ { "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/RNSYWXMO5E6MS4VDWK7HLOTB4PABMRJ2/", "counter": 2, "name": "attachment.html", "content_type": "text/html", "encoding": "utf-8", "size": 7914, "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/RNSYWXMO5E6MS4VDWK7HLOTB4PABMRJ2/attachment/2/attachment.html" } ] }