I built (and currently testing) a 4 port automated PCB test & programming tool. I needed a way to produce a bunch of PCBs efficiently and couldn't find a solution that was flexible and didn't cost many thousands of dollars. I made a simple tool to solve this.
Features
- 4-channel DUT interface with individual power control via TPS22992
- JTAG multiplexer for programming (not exclusive to JTAG)
- Power monitoring using PAC1954 for per-channel current/voltage measurement
- Raspberry Pi Pico for control logic and automation
- USB interface through Pi Pico USB-CDC for host communication (1 port for each DUT)
- 1.8V - 5V IO support
- MicroPython support for test script automation
XTEink isn't using ESP32-S3 but C3. That S3 dev board from OP also comes with 8MB PSRAM (xteink/C3: 384kB RAM only) which IIUC makes quite the difference when it comes to building an embedded OS.
Super impressive project, especially for what seems to be your first embedded project. I haven't played with microPython/uOTA so this was an interesting read.
Since you mentioned the water meter Flume, I wanted to shamelessly plug my open source water meter that I'm currently developing. It also uses the ESP32 so I thought you might be interested.
I started working on my opensource water meter again (https://y-drip.com/). Hardware is basically done so I'm working on the backend website for those that don't want to setup their own server. More technical details here: https://hackaday.io/project/191398-ydrip
I'm a seasoned software engineer with extensive experience in embedded systems, real-time communication, and full-stack development. My background includes designing innovative hardware and software solutions for various applications.
Key Projects:
- Real-time Audio Communication Device: Developed a device supporting 16 participants over 700 meters with 18-hour battery life using STM32 and Silicon Labs EFR32.
- Android ROM Customization: Customized Android ROM for a video kiosk, added native USB camera support, and developed an over-the-air A/B update method.
- Innovative Water Meter Solution (Y-Drip): Designed a product for real-time water usage data and leak detection with ultra-low power consumption.
- Full Stack Development (Scalp Radar): Created a SAAS website for futures traders using Python, Django, and C#, with an automated license management system.
I'm currently seeking opportunities to leverage my skills in innovative projects, whether in embedded systems, software development, or full-stack applications. Open to remote work or on-site positions.
I recently launch a side project selling software on Shopify and needed a way to for users to manage their software license. Shopify's sample Django app was out dated and didn't implement all of the security features so I've improved it and wrote a guide on how to set it up.
I've found Shopify to be a good platform for selling software minus a few things like subscriptions. It's nice to have most of the e-commerce features like discount codes, analytics, order management taken care of. The only limitation is their free subscription management app is very limited so you might need to pay or build an app to take care of that.
Hopefully, this should give you a head start on adding custom functionality to your next Shopify side project.
This is a pretty cool solution. I didn't know the capabilities of USB4 before this.
The comparison with the Dell r630 power numbers got me interested since I just purchased a Dell r430 to host my site so I decided to benchmark mine.
Specs:
* 2x Xeon E5-2680 v3 (same CPU)
* 64GB RAM
* 2x power supply (can't remember if it's 500W or 750W each and too lazy to look)
* 1 SSD & 1 7300 RPM HDD
* Ubuntu server 22.04.3 LTS
Using a Kill-A-Watt meter I measure ~100 watts after boot. Running sysbench (sysbench --test=cpu --threads=12 --cpu-max-prime=100000 --time=300 run) I get up to ~220 watts.
If my calculations are correct that's 72 kW per day or $11.05 per month at idle:
I'm not sure of OP's use case, but these numbers are probably more realistic than using the max wattage of the power supply for most people. I will still be hosting in a co-location for the reliable internet and so I can sleep without the sound of a jet engine taking off. Those fans are loud!
Lack of understanding. Even comparing 65W to 1000W should had ring some bells, but.
> but these numbers are probably more realistic
Almost, depends on the load (hardware) and load (software), as someone who manages a fleet of 720/730/630, a standby server eats around 150W and under the load up to 300-350W, depending on the package.
Thanks. The Power Meter menu entry is there, but clicking on it just gives a blank page with this text:
The Power Manager is unavailable for this configuration.
That's with iLO "Advanced" too. :(
Haven't bothered with setting up SNMP nor IPMI on the Microservers though, as it seemed like a bunch of effort for no real benefit (for a homelab). The HPE agents thing is an idea. I'll have to take a look at what that needs, can hook into, etc. :)
These Microservers are definitely running the latest firmware, and the latest iLO firmware too (released last year).
I inherited a few R420's from my work, and the coolest thing about it is the iDRAC. I'm not a SRE or anything of the sort, so don't get to see stuff like that much, but the utility of the iDRAC is fantastic.
The machines each have 192GB of ram, so I thought I'd set them up as LLM inference machines. I figured that with that much ram, I could load just about any model.
Then I discovered how slow the CPUs on these older machines is. It was so utterly slow. I have a machine I bought from Costco a few years ago that was under $1k and came with a RTX 3060 with 12GB of GPU ram. That machine can run around 20+/tokens per second on 13B models (I actually don't know - I stream the text, and cap it at 9 tokens per second so I can actually read it).
The R420? Its tokens per second were in the 0.005 to 0.01 range.
So, yeah, not a good CPU for that sort of task. For other stuff, sure. I thought I'd setup a small file server with one instead, but the fans are so jet engine loud that it's intolerable to have in any part of the house, even when managing fan speeds with software.
CPUs are slow in comparison to GPUs for lots of tasks. Comparing a 10 year old CPU vs. a 4 year old GPU only make that comparison "more offensive." That said, you pair your R420 with something like a RTX A2000 and you'll have a much fairer fight.
Thanks. Detecting slow leaks while also conserving battery life is tricky so I opted to do it in hardware with digital logic. I keep a count of all of the low speed revolutions of the magnet inside of the brass housing. It needs more testing, but it seems to work for now.
Features
https://www.youtube.com/watch?v=NKTlRVKJuS8&thttps://github.com/Netlist-Studio/dut_hub_hw
reply