Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Fri, 3 Apr 2020 13:34:07 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 033KNVMx030767; Fri, 3 Apr 2020 16:24:03 -0400 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 033KNTdB030748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 3 Apr 2020 16:23:30 -0400 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 033KNFTF000708 for ; Fri, 3 Apr 2020 16:23:24 -0400 Received: from w92expo28.exchange.mit.edu (18.7.74.34) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 3 Apr 2020 16:23:26 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92expo28.exchange.mit.edu (18.7.74.34) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 3 Apr 2020 16:23:28 -0400 Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.55) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 3 Apr 2020 16:23:28 -0400 Received: from DM5PR07CA0078.namprd07.prod.outlook.com (2603:10b6:4:ad::43) by BN6PR0101MB2849.prod.exchangelabs.com (2603:10b6:405:2d::35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.19; Fri, 3 Apr 2020 20:23:27 +0000 Received: from DM3NAM03FT045.eop-NAM03.prod.protection.outlook.com (2603:10b6:4:ad:cafe::7d) by DM5PR07CA0078.outlook.office365.com (2603:10b6:4:ad::43) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15 via Frontend Transport; Fri, 3 Apr 2020 20:23:26 +0000 Received: from mail-oi1-f182.google.com (209.85.167.182) by DM3NAM03FT045.mail.protection.outlook.com (10.152.82.208) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15 via Frontend Transport; Fri, 3 Apr 2020 20:23:26 +0000 Received: by mail-oi1-f182.google.com with SMTP id y71so7284016oia.7 for ; Fri, 03 Apr 2020 13:23:26 -0700 (PDT) Received: by 2002:a05:6830:14d2:0:0:0:0 with HTTP; Fri, 3 Apr 2020 13:23:24 -0700 (PDT) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 3 Apr 2020 13:23:24 -0700 Subject: Re: [EE] 74HC123, tie nA and B inputs together? Thread-Topic: [EE] 74HC123, tie nA and B inputs together? Thread-Index: AdYJ9zm7njYpnO+CRmu8aL+ss8FtYw== Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.167.182 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.167.182; helo=mail-oi1-f182.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Ih2A4wqs/NNX4ZjRmVshn20SbxTQlrpSuRlzV+ULu6o=; b=bJoqUNuAA5SpoqSEGA39/l9mgIP/JmUzYOEvT7i4J0tcHp+Rw/xcZqcjVVn+UgRACA f6No+xzF9FfuK3aZr6na19YV8TJ6O/26UmFr9BNfQXPKdsar1eTAGaBDK/xs4/G0kIl6 9eylbhlyRvpoFRxnpiV+xcL/AHTwcQBmO3rButdQcmFeu6omhyVALPYvJim4ny7WXLkb htkmBZMp68Inlwd1dmYDX977Y2Vgm+Nh+ke4slIdIz4nW2YqF9aY/OZbUFyZRiCLVTjG NBxIXpe2kJplqjq42iCDqlndVq36s+nmmiZliT4OHnsbh7ReF4lP2bwW7a/EFJCqWFIw taTA== authentication-results: spf=pass (sender IP is 209.85.167.182) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com;mit.edu; dmarc=pass action=none header.from=gmail.com;compauth=pass reason=100 errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:aca:682:: with SMTP id 124mr4591510oig.69.1585945405752; Fri, 03 Apr 2020 13:23:25 -0700 (PDT) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Okay, that makes sense. On Friday, April 3, 2020, Bob Blick wrote: > Hi Jason, > > You can't do it the way you suggest. If you look at the internal diagram > of the '123, both inputs just go to an AND gate with one input inverted. > There are ways to make it work, like with an RC network, but they are > either hacks that violate rise/fall time and setup time requirements of H= C > logic, or something proper that involves adding more logic such as an XOR > gate and flip-flop. There may exist some parts that incorporate what you > want, but I have always done it with FF+XOR, or in a CPLD. > > Cheers, Bob > > ________________________________________ > From: piclist-bounces@mit.edu on behalf of > Jason White > Sent: Friday, April 3, 2020 6:18 AM > To: Microcontroller discussion list - Public. > Subject: [EE] 74HC123, tie nA and B inputs together? > > Hi everyone, > > I have an application where I need to trigger a reset pulse at powerup > and each time a signal changes from low to high or high to low [2]. > The 74HC123 [1] is a dual monostable multi-vibrator with two trigger > pins: one that triggers on high-to-low transitions and one that > triggers at low-to-high transitions. > > I am trying to figure out if I can tie the two trigger pins (nA and B) > together to achieve sensitivity to both rising and falling edges > without requiring two multi-vibrator elements. An application note [3] > suggests that one has to use both multi-vibrator elements to get dual > edge sensitivity. However, a note [4] on the "'123 Function Table" in > the datasheet [1] suggests (at least to me) that tying both the inputs > together would result in a triggering each time a signal changes. Does > anyone have insight on weather or not doing so would result in the > behavior I need? > > Due to the virus it is going to be a while until I can get my hands on > a physical 74HC123 and test - that is why I am asking for help from > PICLIST. > > [1] http://www.ti.com/lit/ds/symlink/sn74123.pdf > [2] I actually have 2 signals called DIRECTION and ERROR. I have to > trigger a reset pulse at powerup and each time either of these signals > changes (high to low or low to high). I am space constrained such that > I only have room for one 74HC123. Being able to tie the two inputs > together would permit me to use one IC for both signals. > [3] http://www.ti.com/lit/an/slva720/slva720.pdf > [4] function able note: "These outputs are based on the assumption > that the indicated steady-state conditions at the A and B inputs have > been set up long enough to complete any pulse started before the > setup." > > Regards, > Jason White > -- > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 Jason White --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .