I need to drive a Peltier element for thermal stabilization. Typically they are driven by a linear source and it's even recommended to do it that way. I did use MAX1968 as a bipolar driver, but that has a few drawbacks - hardware PID controller is fixed so there's very little room for thermal load variations; limited current/voltage. So I decided to try out driving an H-bridge with PWM and LC filter. While looking at PWM module in STM32F429 I noticed an interesting "complimentary" feature. I tested it out and here we go.
One authentication system to rule them all! Part I: Migrate users from Atlassian Crowd to FreeIPA via LDAP
TL;DR: Don't do this. A colleague recommended me not doing this, but dump users data and recreate users in FreeIPA which is much simpler, quicker and more reliable. And now I agree with him. For I have aged.
If you do, however, plan to do this for whatever reasons, lots of text under the cut
OV5640 with STM32F429 (part II) - automatic gain and shutter control
Once basic image capture and acquisition is working, it is time to start playing with some advanced configurations. This time I'll take a look at how to set up automatic gain control (AGC) and automatic exposure control (AEC) and how it performs.
STM32 HAL DCMI gocha
I've been slowly digging through the OV5640 configuration, trying to fit it to my needs. And it's difficult to do, if you have 3 sets of potential error sources:
- Your own code
- Target device (camera) driver code
- STM HAL!
Every now and then I've been getting chopped up images, such as this:
Eventually they would go away (after 5-10 captures), but meanwhile it's unusable. Especially if you are dealing with an autonomous device, which needs proper imagery.
Of course, first I blame myself, then others. Except this time it's not me, it's ST Micro!
Subscribe to:
Posts (Atom)