Microchip Technology HCS361T/SN

The HCS361 reads up to four button inputs and generates a changing code-hopping output for a compatible receiver. Its EEPROM stores configuration, serial-number and cryptographic-key information that must be programmed for the intended system. Receiver learning and synchronization are system-level functions, not automatic features of an unprogrammed encoder.

The /SN ordering suffix denotes an eight-lead, 150 mil plastic SOIC. This corresponds to the LCDChip registry's existing 8-SOIC package entry. The T device form is the tape-and-reel ordering option. No -I temperature suffix appears in HCS361T/SN, so use the data sheet's commercial-temperature interpretation rather than assuming an industrial grade.

Footprint checks

• Match the Microchip SOIC outline and pin-1 orientation.
• Check DATA, LED and button-input routing against the pin drawing.
• Use the manufacturer's controlled package drawing for land dimensions.

The image is a generic package reference, not the controlled mechanical drawing.

The manufacturer PDIP/SOIC top-view drawing assigns the eight pins as follows:

Confirm the physical pin-1 mark before board assembly.

Typical values, limits and mode-dependent timing require the original data-sheet conditions. System security depends on protected key provisioning and receiver design.

Other HCS encoders are not presumed interchangeable. Compare the complete ordering code, temperature grade, SOIC pinout, programming map, modulation and code format, receiver learning method and deployed cryptographic keys before considering a replacement. No internal alternative link is shown because no target product page was verified for this comparison.

Microchip Technology documents the HCS361 in DS40146E. The product identification section defines HCS361T as tape and reel, /SN as 8-lead SOIC, and the unsuffixed temperature grade as commercial. Verify current product, errata and lifecycle documents before release.

Confirm package marking, traceability and programmed device state against the intended build record. Keep cryptographic keys and manufacturer codes under controlled provisioning. A generic package illustration and catalog description cannot verify an individual lot or completed access-control system.

Do not infer present-day security adequacy from a legacy algorithm or device name alone. Review the threat model, key handling, receiver behavior, RF compliance, supply limits and applicable product standards before deployment. The manufacturer data sheet contains differing prose about total code-word length; this page does not assert that disputed total.