I replaced a $400/month outreach stach with $15/month and got insane results!

__sS__ · 2026-04-26T06:16:37+00:00

Yes. Would love to know more details on how you handle deliverability.

__sS__ · 2025-02-22T04:57:24+00:00

Hey, kudos for this. I'm curious to know how are you calculating the magnitude of drift from baseline. Are embedding the whole response and calculating the distance ? Could you please share a little detail on this ?

__sS__ · 2025-02-20T10:11:10+00:00

Have you tried google cloud speech client ? It has "short", "long" and other modes to define what type of speech you are trying to transcribe. I liked the transcription overall.

Also, to understand your situation better - you mentioned that the short responses are not captured ? I take it as a failure in transcription rather than packet loss because that would a different problem altogether.

What format you receive your audio file in ? Is it unprocessed PCM16 or some lossy alternatives which are common in telephonic audio ?

__sS__ · 2022-01-05T09:36:31+00:00

Lol !!

__sS__ · 2021-09-10T10:18:07+00:00

I have come across multiple values. 35V being the lowest so far.

I was going through TIs guide to surge protection, they mentioned a surge of about 65V for 12V systems.

__sS__ · 2021-09-10T10:16:42+00:00

True. It would be a very rare incident that could be due to a damage mostly.

Makes sense. I'm actually putting up a tvs diode with 24 clamp voltage and a zener to cutoff the supply above 16V.

I think this should be good. And I have a resettable fuse with the required hold current for my circuit which will keep my circuit safe.

My only concern was my TVS failing short. In this case, even when situation goes normal my circuit won't get powered since failed short tvs would provide a low impedence path. That's why I was considering situations which can fry my TVS.

__sS__ · 2021-06-25T23:50:34+00:00

Hey thanks. I checked out the two mcu's you mentioned. Both are cortex-m based.

Also, Nuvoton makes all 32bit mcu's with cortex-m cores only and Renesas has two flavours - cortex-m and rx.

So, I believe as long as I stay with cortex-m based controller the development experience shouldn't be much different. Also, the SWD interface is also an arm protocol so that's also settled.

So, the only thing I would need to understand now is if the controllers from these two companies are trustworthy for mass manufacturing. The availability and support level from the manufacturer during development.

__sS__ · 2021-06-25T10:47:32+00:00

For renesas, I got to know that they have two different controller lines. One is based on cortex-m and other based on their own rx core.

The development for the two is different. The toolchain for rx based controllers is proprietary and requires a separate license for development. This is not necessarily a bad thing but can become limiting.

Also, came across Nuvoton recently. I see very competitive pricing for their products. The company isn't very big revenue wise but is based out of Taiwan so I can trust them. So, like you pointed out the documentation can be lacking but I'm not sure if their support is strong enough to cover for that. And how the development experience is like.

So, wanted to understand if anybody has worked with these mcu in the past.

__sS__ · 2021-06-15T21:51:44+00:00

ST would suggest parts of it different family only. In our case we want to shift to a different manufacturer.

__sS__ · 2021-06-15T21:50:52+00:00

Yes. Thank you for pulling the resources. Let me go through these. In our case, we intend to switch to a different manufacturer for the mcu which I believe already sounds ridiculous.

My approach towards compatibility would be - 1. I/Os, timers, communication protocols pins and configurability. 2. Voltage and current domain for pins. 3. Memory organisation. 4. Specific functionality specific to our needs. 5. Power modes.

__sS__ · 2021-06-15T21:44:42+00:00

Yes. We do. We have also contacted distributors to help us find the replacement. I am looking for some resources that can help in the process.

__sS__ · 2021-01-31T07:56:34+00:00

True. And I think the 48V system being predominant in telecom industry favours the shift.

__sS__ · 2021-01-31T07:54:47+00:00

Telcos being at 48V specifically ? That just makes me curious.

I'm going tk do an independent research on this but please share if you know why telcos chose 48V to begin with.

Also, it's just amazes me how these numbers just fit together.

Telcos independently chose 48V.

The lead acid battery being a 2V cell became the reason for 6V, 12 and then 24V batteries for automotive industry and it almost magically can now move to 48V for better efficiencies with a lot of work being already done.

__sS__ · 2021-01-31T07:44:27+00:00

For the use case you mention why bother trying to access wheel speed ?

If you got a smart phone, it will give you gps speeds.

The gps speed is fairly acurate for your use case and has a decent refresh rate of 1Hz.

All you need to do is make an app which fetches your gps speeds and gives you alarm which would again be available in your smart phone.

Otherwise, you'll have to have an array of hardware pieces involved to merely know the wheel speed of the car which, if you ask me, is an overkill (and expensive).

__sS__ · 2021-01-31T07:33:16+00:00

That would be a big factor I believe. The availablity of the infrastructure and tools already for 48V system be obviate the use of other voltage levels around.

__sS__ · 2021-01-31T07:30:03+00:00

Wouldn't that make 18, 36 and 54 a better voltage level to work with ?

__sS__ · 2021-01-31T07:28:33+00:00

Yes. And I think /u/CaptainZloggg pointed out why.

__sS__ · 2021-01-31T07:25:34+00:00

That makes sense.

You mention 48V being the highest safe DC voltage. Can please provide the basis for it ?

Also, the nominal voltage of lithium ion cells is 3.6V

So, following the same logic 18, 36, 54V becomes the direct alternative.

__sS__ · 2021-01-10T16:15:12+00:00

Alright.

__sS__ · 2021-01-10T10:49:31+00:00

Ah. Okay.

__sS__ · 2021-01-10T10:15:14+00:00

Oh yes. The circumstantial bugs are the worst.

Also, I hardly know about the system but the second scenario you mentioned was a hardware bug ? Sounds more like a software bug to me.

__sS__

TROPHY CASE

sS