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; Mon, 11 May 2020 01:11:02 -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 04B81JSn009505; Mon, 11 May 2020 04:01:52 -0400 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 04B81HOO009502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 11 May 2020 04:01:17 -0400 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 04B81M0n024708 for ; Mon, 11 May 2020 04:01:23 -0400 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Mon, 11 May 2020 04:00:26 -0400 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 11 May 2020 04:01:16 -0400 Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.176) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 11 May 2020 04:01:16 -0400 Received: from DM5PR16CA0007.namprd16.prod.outlook.com (2603:10b6:3:c0::17) by MWHPR01MB2381.prod.exchangelabs.com (2603:10b6:300:46::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.33; Mon, 11 May 2020 08:01:15 +0000 Received: from DM3NAM03FT060.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:c0:cafe::d0) by DM5PR16CA0007.outlook.office365.com (2603:10b6:3:c0::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.28 via Frontend Transport; Mon, 11 May 2020 08:01:14 +0000 Received: from mail-pj1-f43.google.com (209.85.216.43) by DM3NAM03FT060.mail.protection.outlook.com (10.152.83.86) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.27 via Frontend Transport; Mon, 11 May 2020 08:01:14 +0000 Received: by mail-pj1-f43.google.com with SMTP id k7so2471271pjs.5 for ; Mon, 11 May 2020 01:01:14 -0700 (PDT) From: Justin Richards To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Mon, 11 May 2020 01:01:00 -0700 Subject: Re: [EE] Pick & Place Thread-Topic: [EE] Pick & Place Thread-Index: AdYna7aJ8S29tJjrTZyZN+pYi9gh/w== Message-ID: References: <37a7eca90bf277f37cf4c589f22aacef@mtlp000084> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <37a7eca90bf277f37cf4c589f22aacef@mtlp000084> 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.216.43 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.216.43; helo=mail-pj1-f43.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=7IqSTLXbzbzPsEHswXOyckRejzvgunZP4PT4rQ3h7a0=; b=YoJRbb4c0HRKw66bWhaHJs2Oo0dAXPBps4kTniBmBi15BXU/VnSuq+2K+cSaIlIY+d Y8nSGF8Rrs2GyUMwcN6l13DxnOobcPmV7A+r8qXmSil/pa5WmwYAcrf9LuxpA78Yur0b y7EiqyTaJJmxNYDe0LR6bOQRsrkDDNAq/mGBqLvtbES3uSc6TtYbMuw1lSsb2i4gLfyK VzXt+yk6VXylZOgfVDoSyf3hOkEvEiKDuR0CpmViSuRTuyNsCxY5KyJ31i7642COopc5 Fqa5qoMGSB5vHJQqxIF7wINXVxu2v49HiQrWCEbPVFrf0k6J1EgMb9CjVlvlnObd24Ig CKRw== authentication-results: spf=pass (sender IP is 209.85.216.43) 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:a17:90a:d0c3:: with SMTP id y3mr20411545pjw.25.1589184073092; Mon, 11 May 2020 01:01:13 -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 I know little more that what a PnP is, but following along with interest. Time take to change a component reel is often stated as a thing, so I am curious... Is this a thing when changing like reel for like reel or when changing to a different part reel or both? And typically, what is the actual time taken to change these reels on 'desktop' and 'big boy' PnPs? Is it minutes, 10's of minutes.? I am assuming its only minutes, yet it obviously represents a significant input cost of production and so I think I am missing the point. Justin > Main problem with the N4 systems is the > amount of time that it takes to change a component reel. > > --=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 .