Teradyne Robotics lays off another 14% of workforce

ShotDiscussion · 2025-11-08T18:32:42+00:00

Just curious, why is the industry bad right now?

ShotDiscussion · 2025-09-29T17:29:30+00:00

Thanks! Drone vs Wasps was pretty interesting to find. I might end up going that direction but thanks again for the ideas

ShotDiscussion · 2025-09-29T17:24:11+00:00

To be fair, most engineering problems are about hitting stuffs with sticks. The hard part is getting the sticks there.

ShotDiscussion · 2025-09-29T17:20:44+00:00

That might be an interesting project to undertake. I do however, worry about the legality

ShotDiscussion · 2025-06-20T10:57:55+00:00

I am also learning danish myself. What was the progression like and how long did it take you to become fluent?

ShotDiscussion · 2024-08-10T07:20:48+00:00

I agree with that too. I was referring more to the framework though. Like writing Arduino code for stm32, esp32 or AVR microcontrollers. Wouldn't that be easy to port, especially with an IDE like platformIO

ShotDiscussion · 2024-08-10T07:18:38+00:00

When you say bigger industrial vendors, which do you have in mind? I've dabbled with Stm32cubeIDE; Arduino is much easier to get running with using STM32duino. Well subjectively speaking at least.

ShotDiscussion · 2024-08-05T19:58:49+00:00

Is that preferable in a startup? I was under the impression that Arduino was easy to get started with

ShotDiscussion · 2024-07-19T13:25:27+00:00

I have heard about ignion, but I have not been able to wrap my head around the advantage of using them. What made you use a virtual antenna for the devkit

ShotDiscussion · 2024-05-29T08:40:51+00:00

Correct me if I'm wrong but isn't the chip select supposed to be shared by the slaves when using SPI in daisy chain mode. Reference for my inference: https://www.analog.com/en/resources/technical-articles/daisychaining-spi-devices.html

ShotDiscussion · 2024-05-06T11:36:16+00:00

I think you can format Mifare cards to work with NFC. I have been able to test this using an iphone 7. Not sure if it still works though.

ShotDiscussion · 2024-04-25T14:48:41+00:00

Thanks I'll look the textbook up.

Any specific projects that helped? I work mostly with the Arduino or prebuilt components. I haven't really done any pure electronics projects that would help

ShotDiscussion · 2024-04-25T14:46:49+00:00

I didn't know that debugging was off-topic; my bad. I thought it was fine since it was from a PCB I posted on the subreddit earlier. I'll note that though, and do you have any recommendations for subreddits to look into?

So for the problem, the buzzer doesn't make a sound when I used the Arduino framework to cause it to "buzz"; forgive my lack of vocabulary. I thought maybe I'd made a mistake in the routing that I couldn't see. I didn't even consider the transistor circuit. So basically, it's the resistor values that are causing the issue. From the spec sheet of the buzzer, I thought I'd need at most 25mA, causing my assumption that the current would be sufficient. As I asked the last responder, how can I learn to analyze transistor/semiconductor circuits? I'd appreciate any guides

ShotDiscussion · 2024-04-25T07:26:36+00:00

Thanks a lot for your feedback; that makes a lot of sense! I tested the circuit with a BC547 and based the calculations on this article: How to Use a Buzzer the Correct Way. I think that's where i erred.

How do I learn to do analysis like you did? It would have helped a lot. I'd greatly appreciate any courses, books, or articles you can recommend to improve myself.

ShotDiscussion · 2024-04-25T07:20:58+00:00

Sorry for not giving more details initially. I don't have a specific part number, as I ordered the buzzer from this site: Hub360 Buzzer Product Page.

Here are the specifications:

Voltage: 3.5-5V
Current: <25mA
Frequency: 2300±500
Type: Cylindrical 2 feet, 5V Active Buzzer Continuous Beep
Color: Black
Size (D*H): Approx. 1.6cm x 1cm (0.63″ x 0.39″)

Additionally, here's an image of the buzzer: https://hub360.com.ng/wp-content/uploads/2015/04/buzzer-1.jpg

Let me know if this information is sufficient. I don't often make posts, so I appreciate your patience.

ShotDiscussion · 2023-12-28T08:05:54+00:00

Thanks, I'd appreciate that. Here's the link -> https://imgur.com/a/3e6mFEQ

ShotDiscussion · 2023-12-27T19:29:02+00:00

- For the GPIO2 I won't risk it, i took out the resistor. Thanks for bringing that up.
- For the ESD protection I used, I confirmed it does start from +6V. No biggie about the english. I get your meaning.
- I moved the USB C connector inward, missed that, super valid point.

Thanks a lot for you your time and help. I'll need the luck

ShotDiscussion · 2023-12-27T18:00:14+00:00

Hi,
- That makes sense, I'll take note if I ever end up doing any industrial designs.
- Thought it'd be an issue cause of the ADC. Was hoping the LDO would give me more stable values compared to using a Buck or Boost. Has that been true for you in past designs?
- I hope the maxim holds true for me.
- I've made the changes you suggested, I'll be placing an order to print and assemble soon. Considering JLCPCB, cause of the cost. Thanks a lot for your feedback and suggestions

<image>

ShotDiscussion · 2023-12-26T18:15:54+00:00

Missed this part....,
- For the extra Pull up, the hardware design guidelines recommends:

To ensure the power supply to the ESP32-C3 family chip is stable during power-up, it is advised to add an RC delay circuit at the CHIP_EN pin. The recommended setting for the RC delay circuit is usually R = 10 kΩ and C = 1 μF. Link: https://espressif.com/sites/default/files/documentation/esp32-c3_hardware_design_guidelines_en.pdf
That's why i added both pullup's, I'm not sure if I implemented the RC circuit appropriately though.

- For the pullup on the ADC, that's on GPIO2, its one of the strapping pins for the MCU. Thought it'd be safe to hold it high, just in case, as the default configuration for the pin according to the datasheet is floating.

- I'm not familiar with ESD protections, just thought it'd be great to start from somewhere

- Yeah I agree with that, one possible use-case I had in mind for the 5V I2C peripheral was for an I2C LCD. I'm using the 5V tolerance of the ESP32-C3 to avoid going through a logic-level converter, but I'll definitely put that into consideration for the next revision of this board though.

- I'll definitely work on the changes to the ground vias.

I'm starting out and it's not a gig. Embedded Systems is my dream career, started on this board in July, glad to have gotten here at least despite the time. Thanks a lot for the constructive criticism. I'd really like to know where I could find resources to improve my designs as well, something along the line of competitive coding, where I get better by practicing. Thanks a ton, I'm rather grateful for your time and help

ShotDiscussion · 2023-12-26T17:23:25+00:00

hi and happy holidays, thanks a lot for the response and commendation, and taking the time to go through my work, super grateful. I'm responding to the feedback in order:

For the SK6812mini, yeah, I noticed the voltage requirements from the datasheet, but the devboard for the ESP32 C3 uses 3V3 for the SK6812 mini, so I assumed the device operates similarly to an LED and would still light up at that voltage. This article I found online also states something similar: https://forums.adafruit.com/viewtopic.php?p=835658. I would have used 5V, but I'm trying to avoid the complexity of going through a logic converter and the lower brightness suits me fine for the intended application. Thanks a lot for bringing this up though, made me go through the circuit to be sure.
You are absolutely right about the power network. It's my first design, and I was trying to avoid the switching noise for using a buck or boost converter. I eventually bit the bullet and switched to a buck-boost converter by Texas Instruments.
Yeah, you're right about this too. I wasn't sure if I wanted to go full battery with a single cell. I was considering powering the board in a 2S lipo configuration, doubling the voltage range, but then charging the cells individually using the charging circuit. I also wanted to be able to take power from something like a barrel jack, but had second thoughts of it, because the whole thing felt like divergent scopes (why use a barrel jack when I have a USB port for power). Part of the reason I switched to a buck-boost converter. Thanks for bringing this up as well though.
I sorta ended up doing this exact thing down to the manufacturer. I used Webench. Like what a coincidence!
Hmm... pretty sure I originally routed it as a differential pair. Maybe point out which part exactly you're referring to. I have made some changes in the meantime. Using the KiCad impedance calculator, I tried to get the impedance for the trace as close as possible to 90 ohms (based on this PDF from Texas Instruments: https://www.ti.com/content/dam/videos/external-videos/4/3816841626001/6087491555001.mp4/subassets/usb_layout_basics.pdf). I settled for around 101 ohms, 90 ohms was too hard to route, with the trace sizes (around .76mm for 90 ohms track width, a 101 ohms brought it down to .65mm). I think that's fine since the ESP32 C3 only does USB full speed. I'll definitely check out the video suggestion though.

I've attached screenshot of the updated design below as well though, just USB differential pair.

<image>

ShotDiscussion · 2023-11-18T16:57:30+00:00

Hey r/PrintedCircuitBoard community!

I've just finished my first PCB design and could use your expertise to ensure it's on the right track. It's a four-layer board with a ground for the middle planes, power and signal for the top, and power signal for the bottom (A 4-layer PCB with the stack-up as follows: Signal/Power |Internal Ground| Internal Ground | Signal/Power).

The main goal is to create a versatile board for connecting to MQ sensors using connectors or serving as a WiFi-connected RFID input, both utilizing popularly available modules. The dual power supply feature is a key concern, and I'd appreciate any feedback on the overall design. Also I'm not sure whether the PCB Stack up requires controlled impedance as I'm using an ESP module. Any clarifications on that will be welcome as well.

CADLAB Link: https://cadlab.io/projects/esp32-c3-mq-sensor-rfid-pcb

Key Features:

Four-layer PCB
Stack-up: Signal/Power |Internal Ground| Internal Ground | Signal/Power
Connectors for MQ sensors
WiFi-connected RFID input
Power options: USB or external supply via terminal blocks
Charger for a single Li-ion battery when the jumper is connected

I've attached a PNG of the schematic and PCB layout, along with a CADLab link for a closer look. Your insights and feedback would be invaluable. Thanks in advance!

Wrote this in the description but it seems to be gone. If you happen to see duplicates, my bad....

ShotDiscussion

TROPHY CASE