Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/JEOOQ75677JEOEII5SRLN2M22HTPRC5V/
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/JEOOQ75677JEOEII5SRLN2M22HTPRC5V/", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/", "message_id": "[email protected]", "message_id_hash": "JEOOQ75677JEOEII5SRLN2M22HTPRC5V", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/JEOOQ75677JEOEII5SRLN2M22HTPRC5V/", "sender": { "address": "wa4cwi (a) bellsouth.net", "mailman_id": "4aa6f1e3f4cd4bf4b1492e47285ca527", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/4aa6f1e3f4cd4bf4b1492e47285ca527/emails/" }, "sender_name": "Jim McCullers", "subject": "[pacsat-dev] Re: Pullups/Pulldowns", "date": "2023-11-19T22:16:31Z", "parent": null, "children": [], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "Agree on all points.\n\n \n\nJim\n\n \n\n \n\nJim, \n\n \n\nI said earlier “you”and I should have said “we”…\n\n \n\nYes, these issues will go through changes and false starts.\n\n \n\nMay need to disable most IRQ lines in the beginning.\n\n \n\nYes, and my sheet is going to have issues. I got to thinking later that I did not label the I2C clock as a CLK. Have not gone back to look yet.\n\n \n\nI like and agree with what Burns said, once we get this all working we probably will not have to touch it any more. Temperature testing will be needed to be sure things work properly.\n\n \n\nWe may also find the pull-up they have on chip is not enough and have to add a pull-up or pull down to the board. I think I have most of them covered but may have missed something.\n\n \n\nOn the lines going to the PC104 I don’t know what is really going to be needed there without a lot more study on the interface. So i just made them inputs mostly to be safe. These lines should all be buffered but I did not want to add the additional chips and current. Careful coordination with others should be the solution but a lot of work there. We can address it later. I think the main goal is to get the CPU working and then test the radios, clock, and WDT etc.\n\n \n\nBob\n\n \n\n\n\n\n\nOn Nov 19, 2023, at 9:24 AM, Jim McCullers via pacsat-dev <[email protected] <mailto:[email protected]> > wrote:\n\n \n\nBob,\n\n \n\nThanks.\n\n \n\nI’ll look at the 570 data sheet and see what it says about pullup resistance.\n\nAn input can be configured with either a pullup, pulldown or nothing.\n\n \n\nWant to start a group pool to bet on how many iterations it will take to get the configuration correct?\n\nNot that difficult but easy to loose ones place going between your pin chart and the HCG settings.\n\n \n\n73,\n\n \n\nJim McCullers\n\nWA4CWI\n\n \n\n \n\n \n\nJim,\n\n \n\nYes need to be sure the pull ups are enabled on these IRQ lines which will be inputs. \n\n \n\nOk to have pull ups on all inputs. If we have a problem meeting the Vol input level we can disable later. \n\n \n\nPull-ups are probably a high resistance, maybe 100K?\n\n \n\nI have several external pull ups and a few pull downs. \n\n \n\nPOR could be a special case but we can start with pull-up. \n\n \n\nBob\n\n\n\n\n\n\nOn Nov 19, 2023, at 7:07 AM, Burns Fisher (AMSAT) via pacsat-dev <[email protected] <mailto:[email protected]> > wrote:\n\n \n\nYou should double check this but I seem to remember that the internal pull-up/downs only work for INPUTS. Not sure if for example they would work on i2c. FWIW\n\n \n\nOn Sat, Nov 18, 2023 at 10:41 PM Jim McCullers via pacsat-dev <[email protected] <mailto:[email protected]> > wrote:\n\nBob,\n\n \n\nIn the last column labeled Pullup/Down does “Add on chip pullup” mean set the pullup with the HCG configuration?\n\nMy assumption is yes but wanted to crosscheck before defining.\n\n \n\nThe configurator assigns a pullup to all inputs by default.\n\nIf not required I assumption they will need to be manually reset in HCG.\n\n \n\n \n\nThanks\n\n \n\nJim McCullers\n\nWA4CWI\n\n\n-----------------------------------------------------------\n\npacsat-dev mailing list -- [email protected] <mailto:[email protected]> \nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\nTo unsubscribe send an email to [email protected] <mailto:[email protected]> \nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org <https://mailman.amsat.org/> \n\n\n-----------------------------------------------------------\n\npacsat-dev mailing list -- [email protected] <mailto:[email protected]> \nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\nTo unsubscribe send an email to [email protected] <mailto:[email protected]> \nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org <https://mailman.amsat.org/> \n\n\n-----------------------------------------------------------\n\npacsat-dev mailing list -- <mailto:[email protected]> [email protected]\nView archives of this mailing list at <https://mailman.amsat.org/hyperkitty/list/[email protected]> https://mailman.amsat.org/hyperkitty/list/[email protected]\nTo unsubscribe send an email to <mailto:[email protected]> [email protected]\nManage all of your AMSAT-NA mailing list preferences at <https://mailman.amsat.org/> https://mailman.amsat.org\n\n \n\n\n\n", "attachments": [ { "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/JEOOQ75677JEOEII5SRLN2M22HTPRC5V/", "counter": 2, "name": "attachment.html", "content_type": "text/html", "encoding": "utf-8", "size": 13787, "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/JEOOQ75677JEOEII5SRLN2M22HTPRC5V/attachment/2/attachment.html" } ] }