Current Sensor ACS70331EOLCTR-2P5B3 appears to be EOL, any alternative?

[pat-bohn]

Hi,
Thank you for sharing your interesting design! In attempting to source the parts for it, I stumbled upon a sourcing issue for the current sensor. It appears that it's in EOL stage, as it's not available from mouser or digikey (marked as "not for new design" on digikey) and there's only a single seller on aliexpress charging 22€ per piece. What would be suitable alternatives?

Thank you and best wishes

[zapta]

I believe that this one is compatible https://www.lcsc.com/product-detail/Current-Sensors_Cross-chip-CC6920BSO-5A_C2880430.html . It's a different technology, slightly more noisy, but I think it's pin compatible. This sensor also has slightly different calibration constant, due to its higher internal impedance so you may need to make minor changes to the configuration code. https://github.com/zapta/simple_stepper_motor_analyzer/blob/main/platformio/src/misc/hardware_config.cpp BTW, I recently posted a new design that does about the same, but can be ordered fully assembled from JLCPCB and is less expensive. This design doesn't use a display and instead sends the data in real time via bluetooth to a Mac/Windows/Linux graphical app. With this design, you can embed one or more in your system and connect to it and display data whenever you want. This design uses the current sensor I mentioned above. https://github.com/zapta/ble_stepper_motor_analyzer

…

On Mon, Apr 10, 2023 at 10:25 PM pat-bohn ***@***.***> wrote: Hi, Thank you for sharing your interesting design! In attempting to source the parts for it, I stumbled upon a sourcing issue for the current sensor. It appears that it's in EOL stage, as it's not available from mouser or digikey (marked as "not for new design" on digikey) and there's only a single seller on aliexpress charging 22€ per piece. What would be suitable alternatives? Thank you and best wishes — Reply to this email directly, view it on GitHub <#13>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQVMQMPE5TBM2GPQODH3HDXATTM7ANCNFSM6AAAAAAWZY3U6Q> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[zapta]

This is a short video that shows how the bluetooth application looks on the PC screen. https://vimeo.com/798169140

…

On Tue, Apr 11, 2023 at 12:44 PM Tal Dayan ***@***.***> wrote: I believe that this one is compatible https://www.lcsc.com/product-detail/Current-Sensors_Cross-chip-CC6920BSO-5A_C2880430.html . It's a different technology, slightly more noisy, but I think it's pin compatible. This sensor also has slightly different calibration constant, due to its higher internal impedance so you may need to make minor changes to the configuration code. https://github.com/zapta/simple_stepper_motor_analyzer/blob/main/platformio/src/misc/hardware_config.cpp BTW, I recently posted a new design that does about the same, but can be ordered fully assembled from JLCPCB and is less expensive. This design doesn't use a display and instead sends the data in real time via bluetooth to a Mac/Windows/Linux graphical app. With this design, you can embed one or more in your system and connect to it and display data whenever you want. This design uses the current sensor I mentioned above. https://github.com/zapta/ble_stepper_motor_analyzer On Mon, Apr 10, 2023 at 10:25 PM pat-bohn ***@***.***> wrote: > Hi, > Thank you for sharing your interesting design! In attempting to source > the parts for it, I stumbled upon a sourcing issue for the current sensor. > It appears that it's in EOL stage, as it's not available from mouser or > digikey (marked as "not for new design" on digikey) and there's only a > single seller on aliexpress charging 22€ per piece. What would be suitable > alternatives? > > Thank you and best wishes > > — > Reply to this email directly, view it on GitHub > <#13>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAQVMQMPE5TBM2GPQODH3HDXATTM7ANCNFSM6AAAAAAWZY3U6Q> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >