SA404A alternative

Hello,

We are currently using the SA604A IC in our products. However, based on the information provided by your team, this IC has been discontinued.

I would like to know if there is a recommended replacement for this device. If no direct replacement is available, could you recommend an integrated circuit suitable for HDX demodulation?

Thank you in advance for your assistance.

I do not think there is a Pin-Compatible 2nd source for the SA604A.
sa605/sa615 are 20-pin, not 16-pin, and NXP descripes the SA605 as combining the sa602a with the sa604a. Different function set, so it means a board change either way. NXP also lists the sa605 as no longer manufactured.
The 16-pin parts that usually come up in searches are the LM3089 / CA3089 family, and that is a different application. Through-hole DIP, 16 V maximum supply, around 15 to 30 mA against roughly 3.3 mA for the SA604A, and a product detector rather than a quadrature detector. The long “cross reference” lists for those parts are alternate numbers for that same family, not equivalents to the SA604A.
If HDX means ISO 11784/11785 (FSK, 134.2 kHz and about 123 kHz, roughly 8 kbps), it is probably better to look at a reader front end instead of an IF strip. One worth evaluating is TI’s TMS3705, a 134.2 kHz base station IC that drives the antenna and also does the FSK demodulation. Check the suffix carefully: on TI’s own page the F and G variants are listed ACTIVE while the E variant is OBSOLETE. It is a 16-SOIC with the same 3.9 mm body width, but this is a board-level change, not a drop-in.
Please confirm all of this against the current datasheets before committing to a design.

Agree with DeepJudge, no drop-in. So its 2 separate decisions:

  1. Now: last time buy. Brokers still have SA604A, but take only ones with test reports, old NXP RF parts get faked a lot. Count boards for next 2-3 years plus some spare.
  2. Later: redesign on your own schedule, not in panic. Many newer HDX readers do the demod in MCU firmware, so new board can end up cheaper.
    How many units per year you build with it? That decides if LTB alone is enough.

Hello Mr. Zorin,

Thank you for your responses and suggestions.

We have successfully used the SA604A in a previous project. However, since we are currently developing a new product and the SA604A is already obsolete, continuing to use this component would be a significant concern for us. Therefore, we started looking for an alternative solution.

Our first option was the TMS3705, but so far, we have not achieved satisfactory results with HDX signal decoding. Since our design uses a full-bridge circuit to increase the transmission power, we are experiencing difficulties with the reception stage when using the TMS3705.

We are still investigating possible ways to overcome this issue, but we have not yet found a straightforward solution.

You mentioned that some newer HDX readers perform signal demodulation directly in the MCU firmware, without relying on a dedicated demodulation IC.

Would you happen to have a reference schematic, application note, technical documentation, or any other material that could serve as a starting point for developing a prototype based on this approach?

Any guidance or references you could provide would be greatly appreciated.

Thank you in advance for your time and support.

Best regards,
Hideraldo

Hi Hideraldo,
No ready reference schematic from me, sorry. But the idea is simple, I can describe how its usually done.

HDX is FSK, about 134.2 kHz for 0 and 124.2 kHz for 1, and the tag answers after the charge pulse, when your full bridge is off. So:

  1. Front end: after TX stops, take antenna signal through small cap and resistor divider, clamp with 2 diodes, then fast comparator (or MCU internal comparator) to get square wave.
  2. MCU: timer input capture on every edge, measure period. ~7.45 us is 0, ~8.05 us is 1. Average over few cycles, it is noisy at the start.
  3. Firmware: find start byte, decode bits, check CRC. ISO 11785 describes the frame.

Main problem with full bridge is ringing after TX off, so give some dead time before you start capture, or damp the coil with a switched resistor for first ~100 us.
Any MCU with 48 MHz+ timer is enough, STM32G0 or similar.

What volume do you plan for the new product? If its more than few hundred, I would check also ready reader modules, sometimes cheaper than own analog part in the end.

Check the tag protocol before tuning anything else. The TMS3705 reads HDX only, TI states it cannot read FDX tags. Most small 134.2 kHz tags are FDX-B, which is load modulation instead of FSK, so an FSK threshold cannot work on them whatever the front end does.

More carrier power may be making reception worse. HDX is half duplex and the limit is usually the return path. With a full bridge the coil voltage goes above the supply, the RF amplifier input gets clamped by its ESD diodes, and the signal comes back clipped and ringing. Any second bridge has to be high impedance in the read window too.

The analog and digital test pins separate an overdriven front end from a threshold problem. Clipping on the analog pin means too much signal. A clean analog pin with a corrupt digital one means the threshold, and that is a firmware fix.

Hello Mr. Zorin,

Thank you once again for your suggestions regarding the discrete implementation of these circuits. I will carefully evaluate this approach as a potential solution.

I have one question regarding the ready-made modules you mentioned in your last sentence. Could you recommend some specific modules or provide a few examples so that I can take a closer look and evaluate their suitability for our application?

Best regards,
Hideraldo

Hello Mr. Deep,

Thank you very much for your help!

The project also includes FDX reading. However, in this case, the FDX receiver circuit is implemented discretely. Only the full-bridge transmitter and the LC resonant circuit are shared between the two technologies.

During the reception phase, the signal amplitude appears to be within the IC’s supply voltage range. Nevertheless, the IC is unable to read the transponder. Interestingly, when I remove the full bridge and use only the previous driver circuit, the IC reads the transponder correctly. However, the reading distance is significantly reduced, making this solution unsuitable for our application.

I was particularly interested in the last paragraph of your message regarding the analog and digital test pins. I previously asked TI about these pins, but unfortunately, I did not receive a response.

Could you please explain in more detail how these test pins work and how they could be used to investigate the issue? In particular, I would like to understand what signals or internal circuit behavior can be monitored through these pins and how this information could help identify why the IC is unable to read the transponder when using the full-bridge configuration.

Thank you in advance for your time and assistance.

Best regards,
Hideraldo

By the way, this is the received signal captured at the input. The signal outside the response window is related to the transmission.

Hi Hideraldo,
Few directions I would look, not one magic part:

  1. Agrident ABR200. OEM module, 134.2 kHz, HDX + FDX-B (ISO 11784/85), UART 3.3V, small, made for mobile. Good if you need both protocols in one module.

  2. TI Series 2000 microreader: RI-STU-MRD2 / RI-SMD-MRD2 (and MRD2EVM kit). DigiKey/TI have them. Strong on HDX. Check FDX support against your tags before you lock it, your FDX path is already discrete so maybe HDX-only module is enough.

  3. Cheap UART boards sold as “ISO11784/85 HDX reader module” (eg. IVY134H series and similar). Fine for prototype, check stock and docs carefully before series.

For all of them: connect your own antenna, and keep full bridge TX off (or high-Z) in the read window, same problem you have now with TMS3705.

What read distance you need, and do both HDX and FDX must share one antenna always?

Hi Hieraldo:
Your scope capture above already answers the test-pin question, so I’ll start there.

Correction to my earlier post: D_TST does not carry demodulated data. Per the 1999 TMS3705A manual’s test-pin section, in normal modes it carries the internal digital reset (active low); the current datasheet only calls it “for testing the internal logic.” Decoded data leaves on SCIO. The ESD clamp I mentioned belongs to the charge phase, where TI expects it, and the diagnosis resistor at SENSE is off during read. A_TST is the pin you want: it sits at the limiter input after the band-pass, so it shows the receive signal just before slicing.

The clipping is expected. The problem is what happens after the drive stops: the coil rings down at its own carrier for about 10 to 15 ms, starting near +1 V.

That ring-down is what kills the read. After the RF stage (gain 5) and the band-pass plus limiter, cumulative gain is well over 1000, so even +1 V at the input is far above the limiter threshold of about 5 mVpp. The ring-down sits at roughly 134.7 kHz, which the demodulator counts near 119, inside its accepted window of 112 to 125. So instead of calibrating from the tag preamble, it calibrates from your ring-down. It never sees a clean start bit, and the whole frame drops. A shorter ring-down is very likely the dominant reason removing the full bridge gets you a read: less stored energy, the preamble finally gets through, but the range drops.

Two fixes, both in your trace.

One: damp the tank actively. A resistor switched across the coil for the first 15 ms after drive-off bleeds the ring-down fast. That is much longer than the 100 microseconds. I estimated earlier. Your capture shows the real decay is 10 to 15 ms, so the damping window has to cover that.

and two: during the HDX read window, disconnect the discrete FDX front end from the coil. FDX is load modulation, so that front end presents a low impedance across the coil right when you are trying to receive. Open a series switch or MOSFET in that path, but only during the HDX read window so FDX still works otherwise.

To confirm without a full rework: on the same board, switch a bleed resistor across the coil that is on only for the first ~15 ms after TX-off, then capture A_TST. If the start-bit signature cleans up, that confirms the ring-down calibration hypothesis; if not, the limiter or threshold path is the next thing to check. Your SENSE capture already shows the envelope stays high for about 10 to 15 ms, so size the bleed window to cover that.