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 10:44:03 -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 033HYXP7028687; Fri, 3 Apr 2020 13:35:01 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 033HYWxb028666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 3 Apr 2020 13:34:32 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 033HYfRJ015139 for ; Fri, 3 Apr 2020 13:34:51 -0400 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 3 Apr 2020 13:33:48 -0400 Received: from oc11exhyb4.exchange.mit.edu (18.9.1.100) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 3 Apr 2020 13:34:28 -0400 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.103) by oc11exhyb4.exchange.mit.edu (18.9.1.100) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 3 Apr 2020 13:34:28 -0400 Received: from MWHPR2001CA0019.namprd20.prod.outlook.com (2603:10b6:301:15::29) by BYAPR01MB4165.prod.exchangelabs.com (2603:10b6:a03:16::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.16; Fri, 3 Apr 2020 17:34:27 +0000 Received: from CO1NAM03FT014.eop-NAM03.prod.protection.outlook.com (2603:10b6:301:15:cafe::8b) by MWHPR2001CA0019.outlook.office365.com (2603:10b6:301:15::29) 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 17:34:26 +0000 Received: from NAM02-CY1-obe.outbound.protection.outlook.com (40.92.4.20) by CO1NAM03FT014.mail.protection.outlook.com (10.152.80.101) 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 17:34:26 +0000 Received: from BL2NAM02FT058.eop-nam02.prod.protection.outlook.com (10.152.76.56) by BL2NAM02HT128.eop-nam02.prod.protection.outlook.com (10.152.76.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15; Fri, 3 Apr 2020 17:34:25 +0000 Received: from BYAPR02MB4055.namprd02.prod.outlook.com (2a01:111:e400:7e46::48) by BL2NAM02FT058.mail.protection.outlook.com (2a01:111:e400:7e46::176) 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 17:34:25 +0000 Received: from BYAPR02MB4055.namprd02.prod.outlook.com ([fe80::1cf1:f69e:a6bb:396]) by BYAPR02MB4055.namprd02.prod.outlook.com ([fe80::1cf1:f69e:a6bb:396%3]) with mapi id 15.20.2856.019; Fri, 3 Apr 2020 17:34:25 +0000 From: Bob Blick To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 3 Apr 2020 10:34:25 -0700 Subject: Re: [EE] 74HC123, tie nA and B inputs together? Thread-Topic: [EE] 74HC123, tie nA and B inputs together? Thread-Index: AQHWCbv021jr9Kz/TEepTngPe9IDFahnpdov Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-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: acceptlanguage: en-US received-spf: Pass (protection.outlook.com: domain of outlook.com designates 40.92.4.20 as permitted sender) receiver=protection.outlook.com; client-ip=40.92.4.20; helo=NAM02-CY1-obe.outbound.protection.outlook.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LN2MXi5p/u2XJPZ8fOTg7hDYSoKyvEmVrGja9LZDpfo=; b=bcEChmNpjQd3sP2r0QYyGkauRtWYKtN96AAEBsAz0DFcMrS0EwZNkRryVgimdXwTZP/j4Z/Kwg6LoG4EuwIMsAxHXi7vhJuWF6qkWwddvOXhig6q03PhkEssRlOwlzYK4aSTl/g3ebcs27Fgil9MtlEXhNnOCodclyiAD5b0pYJMenNi0MxIKPrV/Tg4QAeD1PHQiVnG4EZZapokKEHRfq6+KH75cX9ew9K2cxfvv+C35mTY6XiXYY7ZtBa5OTTjcARtSCEKrDnXub8pMjYJbt1Q055iab28QVHOjX7/gOXNCdneql00tbw+rFuBpp+UnBzHCsb2AmmzSypI+3/FsQ== authentication-results: spf=pass (sender IP is 40.92.4.20) smtp.mailfrom=outlook.com; mit.edu; dkim=pass (signature was verified) header.d=outlook.com;mit.edu; dmarc=pass action=none header.from=outlook.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-topics: [EE] x-mime-autoconverted: from quoted-printable to 8bit by PCH.mit.edu id 033HYWxb028666 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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. Ther= e are ways to make it work, like with an RC network, but they are either ha= cks that violate rise/fall time and setup time requirements of HC logic, or= something proper that involves adding more logic such as an XOR gate and f= lip-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 -- --=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 .