This ad8362 not working on the proteus ..

Hello there,

Thanks for reaching us and for reporting this issue. We are going to investigate it, and we will get back to you as soon as we have an update.

Have a nice day!

Hello jaiirock,

Thank you for waiting while we investigated your inquiry. The previous model for this part was created by one of our users; thus, it had not been verified by the SnapMagic team. Note that when there’s a SnapMagic model available, the part page prioritizes it. But we don’t have CAD models for every part in existence yet.

That said, we were able to prioritize an update for this part with our CAD team. You may now download the latest file and use it in your designs.

Regarding simulation in Proteus: there isn’t a vendor SPICE/macromodel for the AD8362 that reproduces its true RF detection, so a faithful RF-time-domain simulation isn’t possible, and the circuit may not behave as expected. Also note that the Figure 47 example uses a balun specified for roughly 0.5–2.5 GHz; sweeping at Hz/kHz/low-MHz will be heavily attenuated.

A practical workaround is to emulate the transfer curve (VOUT vs input power) with a simple behavioral block:

1. Sweep input power (dBm): Define a sweep variable (e.g., X) from −60 dBm to +5 dBm.
2. Behavioral source for VOUT: Use an arbitrary VCVS with VOUT = LIMIT(0.1, 0.05*(X + 60), 4.9) This encodes the typical ~50 mV/dB slope and ~−60 dBm intercept near 900 MHz, and clamps to ~0.1–4.9 V on a 5 V rail.
3. Output averaging (CLPF): Add a capacitor from VOUT to GND to mimic the detector’s video low-pass/settling behavior; choose the value to suit your response time.

If you happen to have a vendor SPICE/macromodel, please share it, and our engineers can try to simulate it on our side. (S-parameters alone won’t replicate the detector’s nonlinear DC output.)

I hope the details above are helpful. We’re here if you need anything else.

All the best,
Dizar