Become a leader in the IoT community!
Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.
Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.
So far this is what I have, I reduced the rate at which the duty cycle updates, to carry out some test, still having some issues with my AC current readings, for some reason I don’t even know at this point why it’s not working, the code looks ok, hardware looks ok, but no idea why its not working I don’t even know where to start troubleshooting from π I will have to spend more hours with it
While working on this project, I observed some things with my bench power supply, my st link, and my usart to ttl converter. The bench power supply i am using needs to be changed, the display may be showing 14v but when I measure the voltage at the connected wire, I get around 13v and also it does shock a little occasionally. Then for my st link when it’s connected to my laptop and connected to the board, I’m working on, when I send data from my board via usart to ttl converter to my laptop, the majority of the data is garbage, but once I remove the st link from my laptop, the data is readable and accurate. I decided to power the board directly with a battery, and all the issues above disappeared. I think the power supply has worked its money. Can anyone suggest a good affordable power supply for me, please?
I have finally fixed the issue as to why I could not get a current reading from my ac appliances. There was supposed to be a pull up resistor used to pull up my non-inverting pin of my op amp to 3.3v. I used a smaller value of 5.1k instead of the 22k then I also failed to multiply my value by my op amp gain on my firmware. I fixed it and I am finally able to measure my current, next thing to do is to fine tune it, to get a more accurate value. I had to use another board to try and figure out where the issue was coming from
0VID_20250424_072128.mp4
CONTRIBUTE TO THIS THREAD