<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Integrated Circuits | Sensors &amp; Electronic Components - DuoMy</title>
	<atom:link href="https://www.duomy.com/product-category/integrated-circuits/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.duomy.com/product-category/integrated-circuits/</link>
	<description></description>
	<lastBuildDate>Fri, 20 Nov 2026 01:29:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://www.duomy.com/wp-content/uploads/2026/04/cropped-电子-32x32.png</url>
	<title>Integrated Circuits | Sensors &amp; Electronic Components - DuoMy</title>
	<link>https://www.duomy.com/product-category/integrated-circuits/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>MEMS Oscillator, 50 MHz, LVCMOS, ±20 ppm, 5032</title>
		<link>https://www.duomy.com/products/mems-oscillator-50mhz-lvcmos/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:29:02 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/mems-oscillator-50mhz-lvcmos/</guid>

					<description><![CDATA[<p>50 MHz MEMS oscillator in a 5.0 × 3.2 mm package, ±20 ppm, LVCMOS output, 6 mA. No quartz blank, so it survives shock and vibration that crack a crystal.</p>
<p>The post <a href="https://www.duomy.com/products/mems-oscillator-50mhz-lvcmos/">MEMS Oscillator, 50 MHz, LVCMOS, ±20 ppm, 5032</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>A quartz oscillator is a tiny tuning fork suspended in a can. It is accurate and cheap, and it fails when the product is dropped, because the blank fractures or the mount breaks. A MEMS resonator is etched silicon, so the same shock that destroys a crystal leaves it working.</p>
<p>The trade-off is phase noise close to the carrier, where quartz is still better. For a microcontroller clock or a communication bus, that difference does not matter; for a radio local oscillator, it does. Choose MEMS when mechanical robustness is the dominant requirement and the jitter specification is modest.</p>
<h2>Key features</h2>
<ul>
<li>Silicon resonator, no quartz blank to fracture</li>
<li>30,000 g shock tolerance</li>
<li>±20 ppm over the full industrial temperature range</li>
<li>3 ms start-up, suitable for fast boot sequences</li>
<li>1.8 to 3.3 V supply in a 5.0 × 3.2 mm package</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Handheld and portable instruments</li>
<li>Vibration-exposed machine mounted electronics</li>
<li>Microcontroller and FPGA system clocks</li>
<li>Automotive body and access modules</li>
</ul>
<h2>Selection note</h2>
<p>MEMS is the right choice when the product will be dropped or vibrated. If the requirement is low phase noise for RF, use a quartz oscillator instead; the MEMS advantage does not extend to close-in noise.</p>
<h2>Ordering</h2>
<p>Send the frequency, output standard, stability and shock or vibration environment. We confirm whether MEMS or quartz fits the noise budget, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/mems-oscillator-50mhz-lvcmos/">MEMS Oscillator, 50 MHz, LVCMOS, ±20 ppm, 5032</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Clock Generator, 4 Differential Outputs, 1 kHz–200 MHz, I²C</title>
		<link>https://www.duomy.com/products/clock-generator-4-output-i2c/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:29:01 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/clock-generator-4-output-i2c/</guid>

					<description><![CDATA[<p>Four-output clock generator with integrated PLLs, programmable from 1 kHz to 200 MHz over I²C. Replaces four discrete oscillators and lets a single 25 MHz reference feed an entire board.</p>
<p>The post <a href="https://www.duomy.com/products/clock-generator-4-output-i2c/">Clock Generator, 4 Differential Outputs, 1 kHz–200 MHz, I²C</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>Once a board needs three or four unrelated clock frequencies, discrete oscillators stop making sense. Each one costs a placement, a power pin and a bill-of-materials line, and each drifts independently. A single generator with an integrated PLL produces them all from one reference.</p>
<p>The real benefit appears in the lab. Changing a frequency means writing a register over I²C instead of respinning the board for a different oscillator footprint, which is why these parts show up on evaluation boards and prototype hardware far more often than on shipping products.</p>
<h2>Key features</h2>
<ul>
<li>Four independently programmable output frequencies</li>
<li>1 kHz to 200 MHz from a single 25 MHz reference</li>
<li>Sub-picosecond RMS jitter for SerDes and converter clocks</li>
<li>LVDS, LVPECL and LVCMOS selectable per output</li>
<li>Configuration stored in on-chip memory or loaded at boot</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Multi-rail FPGA and SoC clock trees</li>
<li>ADC and DAC sampling clocks</li>
<li>Networking and SerDes reference clocks</li>
<li>Prototype boards that need several frequencies</li>
</ul>
<h2>Selection note</h2>
<p>Place the reference crystal close to the device and keep the loop filter components on the same side of the board. A generator is only as good as its reference, and a 25 MHz crystal with 30 ppm drift sets the absolute accuracy of every output.</p>
<h2>Ordering</h2>
<p>Send the required output frequencies, output standards, jitter budget and reference available on the board. We confirm the configuration and programming method, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/clock-generator-4-output-i2c/">Clock Generator, 4 Differential Outputs, 1 kHz–200 MHz, I²C</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Clock Fanout Buffer, 1:4, LVCMOS, 200 MHz, SOIC-8</title>
		<link>https://www.duomy.com/products/clock-buffer-1-to-4-lvcmos/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:29:01 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/clock-buffer-1-to-4-lvcmos/</guid>

					<description><![CDATA[<p>One-to-four LVCMOS clock buffer, 200 MHz, 50 ps output skew. Distributes a single clock to four loads without loading the source or letting one branch corrupt another.</p>
<p>The post <a href="https://www.duomy.com/products/clock-buffer-1-to-4-lvcmos/">Clock Fanout Buffer, 1:4, LVCMOS, 200 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>A clock buffer solves a specific physical problem: four devices each present a few picofarads of input capacitance, and four in parallel on one driver produce ringing, slow edges and a clock that fails at one load and works at another.</p>
<p>Buffering isolates each branch. The source sees one load, and each output drives its own trace with matched impedance. The 50 ps skew specification is what keeps setup and hold margins in a synchronous interface where two devices latch data on the same edge.</p>
<h2>Key features</h2>
<ul>
<li>Four LVCMOS outputs from one input</li>
<li>200 MHz maximum, 50 ps channel-to-channel skew</li>
<li>Low additive jitter, 0.05 ps RMS typical</li>
<li>Individual output enable pins for power reduction</li>
<li>2.5 V and 3.3 V supply options</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Distributing a system clock to multiple ICs</li>
<li>Synchronous interface timing</li>
<li>Clock fanout on backplanes and daughter cards</li>
<li>Reducing source loading on oscillators</li>
</ul>
<h2>Selection note</h2>
<p>Terminate each output trace in series at the source with a resistor matched to the trace impedance, typically 22 to 33 Ω. Without it, the 200 MHz edges reflect and the low skew specification is wasted.</p>
<h2>Ordering</h2>
<p>Send the clock frequency, number of loads, supply voltage and skew budget. We confirm the fanout and termination, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/clock-buffer-1-to-4-lvcmos/">Clock Fanout Buffer, 1:4, LVCMOS, 200 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>I²C Real-Time Clock, TCXO, ±5 ppm, SOIC-8</title>
		<link>https://www.duomy.com/products/rtc-i2c-tcxo-5ppm-soic8/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:29:00 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/rtc-i2c-tcxo-5ppm-soic8/</guid>

					<description><![CDATA[<p>I²C real-time clock with an integrated temperature-compensated crystal, ±5 ppm from −40 to +85 °C. Battery switchover and a 2 µA timekeeping current keep calendar time across power loss.</p>
<p>The post <a href="https://www.duomy.com/products/rtc-i2c-tcxo-5ppm-soic8/">I²C Real-Time Clock, TCXO, ±5 ppm, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>A plain RTC with an external 32.768 kHz crystal drifts with temperature, typically by 20 ppm over the industrial range, which is about a minute a month. An integrated TCXO corrects for that in hardware, so the firmware does not have to run a compensation table against a temperature sensor.</p>
<p>±5 ppm is still ±13 seconds a month, or about two and a half minutes a year. For time-stamped logs and scheduling that is enough. For anything that must agree with a network clock to the second, the RTC is only there to keep approximate time between synchronisations.</p>
<h2>Key features</h2>
<ul>
<li>±5 ppm across −40 to +85 °C, no calibration in firmware</li>
<li>No external crystal or load capacitors required</li>
<li>Automatic battery switchover with 2 µA timekeeping current</li>
<li>Two independent alarms plus a programmable square wave</li>
<li>Wide 1.8 to 5.5 V supply range</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Data logger timestamps</li>
<li>Schedules, dosing and defrost cycles</li>
<li>Utility meter time-of-use registers</li>
<li>Equipment operating-hour counters</li>
</ul>
<h2>Selection note</h2>
<p>Fit a battery or supercapacitor on VBAT sized for the expected outage. A 2 µA load drains a 200 mAh coin cell in roughly eleven years, but a 0.1 F supercapacitor holds time for only a few days.</p>
<h2>Ordering</h2>
<p>Send the accuracy budget, supply voltage, backup duration and alarm requirements. We confirm the timekeeping current against your backup source, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/rtc-i2c-tcxo-5ppm-soic8/">I²C Real-Time Clock, TCXO, ±5 ppm, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>SPI SRAM, 512 Kbit, 20 MHz, SOIC-8</title>
		<link>https://www.duomy.com/products/sram-512kbit-spi-soic8/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:28:59 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/sram-512kbit-spi-soic8/</guid>

					<description><![CDATA[<p>512 Kbit serial SRAM on SPI, 20 MHz, with unlimited write endurance and 3 µA standby. For buffers and counters that are rewritten continuously and would wear out EEPROM or flash.</p>
<p>The post <a href="https://www.duomy.com/products/sram-512kbit-spi-soic8/">SPI SRAM, 512 Kbit, 20 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>Serial SRAM exists because a microcontroller often needs more RAM than it has pins for a parallel bus. It gives 64 KB over four wires with no erase cycle and no endurance limit, which is exactly what a sample buffer or a high-rate counter needs.</p>
<p>The trade-off is volatility. The contents vanish when power drops, so it is used as an extension of working memory rather than as storage. In practice it holds the buffer that firmware drains to flash or EEPROM later, which also protects the non-volatile part from excessive write cycles.</p>
<h2>Key features</h2>
<ul>
<li>512 Kbit, unlimited write cycles</li>
<li>20 MHz SPI with burst read and write</li>
<li>3 µA standby current, suitable for battery-backed nodes</li>
<li>No erase or write delay, unlike EEPROM or flash</li>
<li>SOIC-8 footprint, four-wire interface</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>ADC and sensor sample buffers</li>
<li>High-rate event counters</li>
<li>Scratch memory for protocol stacks</li>
<li>Display and framebuffer staging</li>
</ul>
<h2>Selection note</h2>
<p>Serial SRAM loses data at power-down. If the buffer must survive a power cut, add a backup supply and a supervisor that holds chip select high during the ramp down, or copy the contents to EEPROM on a power-fail interrupt.</p>
<h2>Ordering</h2>
<p>Send the buffer size, access rate, supply voltage and whether the data must survive power loss. We confirm SRAM against a non-volatile alternative, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/sram-512kbit-spi-soic8/">SPI SRAM, 512 Kbit, 20 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>SPI EEPROM, 4 Mbit, 20 MHz, SOIC-8</title>
		<link>https://www.duomy.com/products/eeprom-spi-4mbit-soic8/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:28:58 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/eeprom-spi-4mbit-soic8/</guid>

					<description><![CDATA[<p>4 Mbit SPI EEPROM, 20 MHz clock, 3 ms page write and one million erase cycles. For larger configuration tables, event logs and parameter sets that still need byte-level rewrite rather than sector erase.</p>
<p>The post <a href="https://www.duomy.com/products/eeprom-spi-4mbit-soic8/">SPI EEPROM, 4 Mbit, 20 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>At 4 Mbit the part crosses from storing a handful of bytes to storing a structured record: a parameter set with a hundred fields, a rolling log of the last thousand fault codes, a language table. SPI is used instead of I²C because shifting half a megabyte over a 1 MHz two-wire bus takes long enough to matter at boot.</p>
<p>It still behaves like EEPROM rather than flash: no erase-before-write, no sector management, no bad block table. That simplicity is worth the price premium when the firmware team would otherwise spend a week writing a flash translation layer for a few kilobytes of data.</p>
<h2>Key features</h2>
<ul>
<li>4 Mbit in 256-byte pages, 2,048 pages total</li>
<li>20 MHz SPI, full 512 KB read in about 210 ms</li>
<li>Byte and page write without a separate erase step</li>
<li>Block protect bits in the status register</li>
<li>2.5 to 5.5 V, drop-in for 3.3 V and 5 V designs</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Parameter sets and recipe storage</li>
<li>Fault and event logs</li>
<li>Boot counters and warranty records</li>
<li>Field-replaceable configuration modules</li>
</ul>
<h2>Selection note</h2>
<p>Allow the full 3 ms write time before the next command. Reading the status register in a poll loop is reliable; issuing the next write after a fixed 1 ms delay is not, because write time rises with temperature and with the number of previously written bytes in the page.</p>
<h2>Ordering</h2>
<p>Send the data volume, update rate, bus voltage and retention requirement. We confirm density and package, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/eeprom-spi-4mbit-soic8/">SPI EEPROM, 4 Mbit, 20 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>SPI NOR Flash, 64 Mbit, Quad SPI, 104 MHz, SOIC-8</title>
		<link>https://www.duomy.com/products/nor-flash-spi-64mbit-soic8/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:28:58 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/nor-flash-spi-64mbit-soic8/</guid>

					<description><![CDATA[<p>64 Mbit SPI NOR flash, quad mode at 104 MHz, 4 KB sectors and 100,000 erase cycles. Holds firmware images, bootloaders and audio or font assets for embedded systems that execute in place.</p>
<p>The post <a href="https://www.duomy.com/products/nor-flash-spi-64mbit-soic8/">SPI NOR Flash, 64 Mbit, Quad SPI, 104 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>NOR flash is chosen for code, not for data. It supports execute-in-place and random access at the byte level, so a processor can fetch instructions directly from it without copying the image into RAM. That is the reason a 8 MB part costs more than a 64 MB NAND device.</p>
<p>Quad mode is what makes it fast enough to be useful: four data lines at 104 MHz give roughly 50 MB/s of theoretical bandwidth, which turns a slow boot into a normal one. The catch is that the first commands after power-up must run in single-bit mode, so the boot sequence has to switch the interface before it can load the image at speed.</p>
<h2>Key features</h2>
<ul>
<li>64 Mbit in 4 KB sectors, 64 KB blocks</li>
<li>Quad SPI at 104 MHz for fast boot and XIP</li>
<li>100,000 erase cycles, 20-year retention</li>
<li>Hardware and software write protection regions</li>
<li>Standard SOIC-8 footprint shared across densities</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Firmware and bootloader storage</li>
<li>FPGA and SoC configuration images</li>
<li>Font, audio and UI asset storage</li>
<li>Data logging where sector erase is acceptable</li>
</ul>
<h2>Selection note</h2>
<p>Plan for erase granularity in the data layout. Updating one 32-byte record still costs a 4 KB sector erase, so logs should be appended across the sector and rewritten in bulk rather than updated in place.</p>
<h2>Ordering</h2>
<p>Send the image size, boot interface, read bandwidth target and update frequency. We confirm density, sector map and package, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/nor-flash-spi-64mbit-soic8/">SPI NOR Flash, 64 Mbit, Quad SPI, 104 MHz, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>I²C EEPROM, 256 Kbit, 1.7–5.5 V, SOIC-8</title>
		<link>https://www.duomy.com/products/eeprom-i2c-256kbit-soic8/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:28:57 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/eeprom-i2c-256kbit-soic8/</guid>

					<description><![CDATA[<p>256 Kbit serial EEPROM on I²C, 1.7 to 5.5 V, 1 MHz bus, 3.5 ms page write. Two-wire interface with three address pins, for calibration data, serial numbers and configuration that must survive power loss.</p>
<p>The post <a href="https://www.duomy.com/products/eeprom-i2c-256kbit-soic8/">I²C EEPROM, 256 Kbit, 1.7–5.5 V, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>EEPROM is the only common non-volatile memory that writes a single byte without erasing a sector first. That is why it survives in designs where flash would be simpler: when the firmware has to store a counter, a calibration offset or a last-known state every few seconds, byte-write granularity is what keeps the endurance budget manageable.</p>
<p>The 3.5 ms write time is the constraint that shapes the firmware. A page write of 64 bytes takes the same 3.5 ms as a single byte, so data should be batched into pages rather than written field by field. The part also does not acknowledge during the internal write, which means the driver has to poll rather than assume the next transaction will succeed.</p>
<h2>Key features</h2>
<ul>
<li>256 Kbit organised as 32,768 bytes, 512 pages of 64 bytes</li>
<li>1.7 to 5.5 V supply, so it runs on 1.8 V, 3.3 V and 5 V rails</li>
<li>1 MHz I²C bus, fast mode plus compatible</li>
<li>Three address pins allow eight devices on one bus</li>
<li>Hardware write-protect pin for the upper quadrant</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Calibration coefficients and sensor offsets</li>
<li>Serial numbers, MAC addresses and board identity</li>
<li>User settings and last-known operating state</li>
<li>Event and fault counters</li>
</ul>
<h2>Selection note</h2>
<p>Budget the endurance before choosing a part. One write per second to the same byte reaches a million cycles in eleven days. Rotate the write address across a page, or cache in RAM and flush on power-down, when the update rate is high.</p>
<h2>Ordering</h2>
<p>Send the density, bus voltage, expected write frequency and address count. We confirm the endurance strategy and package, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/eeprom-i2c-256kbit-soic8/">I²C EEPROM, 256 Kbit, 1.7–5.5 V, SOIC-8</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Octal Bus Transceiver, 74HC245, SOIC-20</title>
		<link>https://www.duomy.com/products/74hc245-octal-bus-transceiver-soic20/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:18:10 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/74hc245-octal-bus-transceiver-soic20/</guid>

					<description><![CDATA[<p>Octal bidirectional bus transceiver, 74HC245 function, 2 to 6 V supply, three-state outputs, SOIC-20. Buffers an eight-bit bus in either direction with one direction pin.</p>
<p>The post <a href="https://www.duomy.com/products/74hc245-octal-bus-transceiver-soic20/">Octal Bus Transceiver, 74HC245, SOIC-20</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>A microcontroller pin drives a few milliamps and one load; a bus has capacitance and several loads. The octal transceiver sits between them, driving the bus in either direction under a single direction pin, and goes to high impedance when the board is not the one talking.</p>
<p>The 6 mA output is the number that decides whether it can drive the bus directly. For a backplane with several boards and long traces, the capacitance per pin is what limits the rise time, and a stronger driver or a bus termination is required.</p>
<h2>Key features</h2>
<ul>
<li>Eight bits, bidirectional, one direction pin</li>
<li>Three-state outputs for shared buses</li>
<li>6 mA drive per pin at 5 V</li>
<li>8 ns propagation delay</li>
<li>SOIC-20 with standard pinout</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Microcontroller to bus buffering</li>
<li>Backplane and card-cage interfaces</li>
<li>Level separation between board sections</li>
<li>Driving high-capacitance loads</li>
</ul>
<h2>Selection note</h2>
<p>The part has no bus-hold. On a shared bus where every driver can go to high impedance, add pull-up or pull-down resistors so the lines do not float into an undefined state.</p>
<h2>Ordering</h2>
<p>Send the bus width, direction control, load capacitance and supply. We confirm drive current and whether bus-hold is needed, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/74hc245-octal-bus-transceiver-soic20/">Octal Bus Transceiver, 74HC245, SOIC-20</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>8-Channel Analogue Multiplexer, 74HC4051, SOIC-16</title>
		<link>https://www.duomy.com/products/74hc4051-analog-mux-soic16/</link>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 20 Nov 2026 01:18:09 +0000</pubDate>
				<guid isPermaLink="false">https://www.duomy.com/products/74hc4051-analog-mux-soic16/</guid>

					<description><![CDATA[<p>8-channel analogue multiplexer and demultiplexer, 74HC4051 function, 2 to 6 V supply, 70 Ω on-resistance, SOIC-16. Eight sensor inputs into one ADC channel.</p>
<p>The post <a href="https://www.duomy.com/products/74hc4051-analog-mux-soic16/">8-Channel Analogue Multiplexer, 74HC4051, SOIC-16</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<p>One ADC channel plus three address lines is cheaper than eight ADC channels, which is why the analogue multiplexer survives in every sensor-dense design. The 70 Ω on-resistance is the parameter to check: in series with a high-impedance sensor it forms a divider with the ADC input, and the reading shifts by the ratio.</p>
<p>Flatness of 10 Ω across the signal range is the more subtle specification. A switch whose resistance varies with the applied voltage distorts the signal, and the error appears as non-linearity in the ADC result rather than as a gain error.</p>
<h2>Key features</h2>
<ul>
<li>8 inputs to 1 output, or 1 to 8</li>
<li>70 Ω on-resistance, 10 Ω flatness</li>
<li>20 ns switching time</li>
<li>Three address lines plus enable</li>
<li>Bidirectional analogue signal path</li>
</ul>
<h2>Typical applications</h2>
<ul>
<li>Multi-sensor ADC front ends</li>
<li>Signal routing in test equipment</li>
<li>Keyboard and potentiometer scanning</li>
<li>Audio and control signal switching</li>
</ul>
<h2>Selection note</h2>
<p>Buffer the multiplexer output before the ADC if the sensor impedance is above a few kilo-ohms. The switch resistance and the ADC sample capacitor form a settling time that limits the scan rate.</p>
<h2>Ordering</h2>
<p>Send the channel count, signal range and sensor impedance. We confirm the on-resistance and settling requirement, then quote.</p>
<p>The post <a href="https://www.duomy.com/products/74hc4051-analog-mux-soic16/">8-Channel Analogue Multiplexer, 74HC4051, SOIC-16</a> appeared first on <a href="https://www.duomy.com">DuoMy Sensing</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
