I have almost 2 decades of interesting experience as a software dev. I am now learning hardware design so that I can create niche hardware products and use my dev experience as an advantage.
I decided to fix it only because I am of the opinion that if I want to act professional in any area I can't shy away from projects like that.
If I calculated the time I spent on this I could have easily bought few of these, new, for the time I was not spending on billable hours.
I know it's one of those compliance issues, but it might be a good idea to have an electrician come out. Last thing a renter wants to see, is bodged together "fire badness".
I'm not saying yours is by any means! But sane-ness and law hardly go together :/
My kitchen was completely miswired since the building was built. The ground exchanged with neutral line. I tested the lines and put it back together as it should. There were many complaints from previous tenants but nobody was able to figure out and fix it -- seems so basic but nobody could do it.
I get you - that your work is likely higher quality, and you could claim ignorance if anyone did have a complaint.
But yeah, on Sunday, I redid some of our outlets and switches. We live in a trailer, and some of the switches were getting intermittent, and some outlets were loose to the point of turning off stuff if they jiggled. But.. I did find out that 1 outlet in the bathroom, the hallway lights, and 1 wall of the living room were on 1 gang... (sigh). I have my work cut out for me if I actually want to do it right.
I think its best to start by utilizing your software experience as much as possible and having just enough hardware to get by. Also don't try to learn/solve too many problems at the same time.
Most of my projects is relatively little/simple hardware + lots of features in software.
For example -- one of my complicated projects requires very precise temperature measurement, precise regulation of mains AC power to 1kW heating element, dealing with PCB environment being very hot and humid (up to 80C), etc.
I am splitting the effort of learning all of those things, and first thing I am building is a precise, standalone thermometer. I will build some software features (data acquisition to SD card, USB, etc.) which is relatively simple compared to getting precise temperature measurement.
Then I will maybe build standalone power regulator that I could have many uses for especially when connected to the thermometer (for example control my oven to do reflow!).
Once I know the building blocks I will attempt building the complex project I have in mind.
Previously there would be one switch to control light, 3 switches to control speed modes and extra switch that I don't exactly know what it did -- probably it controlled some kind of timer.
The 3 switches that controlled modes were 0/1 (change speed to 1 if anything else than 1, turn off if it is currently 1), and 2 and 3 which would turn on 2 and 3 speed mode.
I have added a 500ms long press to 0/1 switch which means that whatever is happening it turns off both light and fan at the same time. You don't have to turn off light and fan separately and you don't have to press 0/1 twice to reduce the speed to 1 and then to turn it off.
As it was sometimes difficult to figure out which speed it was on without looking at the indicators (on the side and not on the front of the extractor) you never knew you had to press it once or twice which was quite irritating.
I haven't looked inside the fan because it worked correctly. I also didn't want to test it to see how it works so I figured it out by analyzing the PCB. Actually that was quite good idea because the relays seem to be connected in such a way as to only allow valid combination to be sent to the fan even in case of invalid input from the microcontroller.
I suspect bad things would happen if I sent incorrect inputs to the fan -- looking at how crappy the board was but at the same time that the person put effort into placing the relays to explicitly disallow invalid combinations of power lines to the fan.
Yes, of course, but it just doesn't look good when the price almost doubled in twelve months, specially when you have better and more powerful micros like the STM32 for less money.
If you can get both MCUs to do the same thing but one of them takes 1/10th the time to set up then which one is better?
Any investment in time or tools is orders of magnitude more than prices of these parts.
Agree for getting things going though - definitely faster and none of that PICkit crap to deal with.
For me there just isn't enough middle ground between 8-bit AVRs and ARM Cortex that would justify learning another platform.
I might be biased, as I learned starting with AVRs and then took to Cortex-M3/M4 when my projects outgrew 8-bit. If I started with PIC that would probably be PIC/Cortex-M, but AVR is so much easier on a newb like I was few years ago.
Want 8, 2 bit timers? Sure thing! One large 32bit timer? Done!
Having a CPLD to drive your peripherals so that you can reconfigure them is a brilliant idea. The fact that you can drop down to VHDL is an awesome bonus. They've also got some small reconfigurable op-amps built in as well that lets do you really clever things while sleeping.
For example, recently I found that the fumes extractor in the kitchen of the flat I rented failed. The PIC on board got tazed with 10V from a broken PSU. I fixed the PSU (replaced cap and regulator, added TVS diode for protection), but the programming on the PIC was lost.
So I found that there is one AVR with matching pinout that I could use in place of the PIC. Thanks to AVRs being so easy to program I could program and test it in an hour or so, and even added some extra features.
I do other projects where I need more power (Cortex M3/M4), but AVR is hard to beat where it comes to how quickly you can get simple things going.