Software for Dave's power supply? (UI sample pics inside)

[george graves]

I know Dave has added the provision for a serial communications for his power supply.

I ran across this project when googling for some more info about DIY bench/lab power supplies - I though it was really interesting!  What do you guys think?  I'm not sure if this project I'm linking to is open source or not - but it looks like all the source code is there!

http://www.soygul.com/projects/microcontroller-based-power-supply/

http://www.soygul.com/wp-content/uploads/2009/08/Diploma_Thesis.pdf

I was thinking of might trying to knock something up in "Processing" (to keep with the open source theme and make it cross platform friendly.  It would be great to make it someone easy to "skin" it, so that there could be several "looks" available.

[PeterG]

Is there an English version of the PDF?

Regards

[Bored@Work]

I ran across this project when googling for some more info about DIY bench/lab power supplies - I though it was really interesting!  What do you guys think?

Piss-poor design. The regulation is done with a digital loop. And that one is too slow to make a good regulating power supply

The hardware (page 14) is a copy of an old, also piss-poor open-source power supply (http://www.linuxfocus.org/English/September2005/article389.shtml) I am surprised that this isn't referred in the list of references in the diploma thesis. Further taking the build "quality" of the power supply in the diploma thesis onto account I have to ask how the guy could get a diploma at all.

[george graves]

I was asking more about the UI and software.     But thanks for the heads up.

[Bored@Work]

I was asking more about the UI and software.   

Lipstick on a pig.

[electrode]

Well he's really just asking about the lipstick.

[Bored@Work]

Well he's really just asking about the lipstick.

The wife says a warm burgundy color would be worth a try. And who am I to disagree with the wife when it comes to lipstick color?

[Mint.]

That looks very very nice. I think I want to buy the kit now. I like how you can see the load percentage and various graphs, very useful!

[george graves]

I was asking more about the UI and software.   

Lipstick on a pig.

Lol

[Mechatrommer]

this is a good example in term of completeness (i mean hardware vs/connection with software) much better than 1hunglow SW from the look. about the analog side of the hardware, sure it can be improved. i do not bother to download the thesis, but  i think most of people around here can do better esp Dave!. just look at how he cut the front panel for the lcd, thats piss poor. poorer than my quick and easy darwinian technique. i can do better (if i want to), others can do alot better than me. @BAW: its just a diploma, in my place, with that level of completeness, i believe the undergrad can be promoted up to bachelor level.

[shebu18]

Why don't we develope a software for Dave's Supply? Data logging, and i don't know what feature we could set in.

[Bored@Work]

@BAW: its just a diploma, in my place, with that level of completeness, i believe the undergrad can be promoted up to bachelor level.

In some areas of the world the diploma is the highest engineering qualification just below the PhD, not the lowest entry level. No, I didn't check what is the case for this particular thesis. However, lowest or highest qualification, providing proper references should always be required.

Why don't we develope a software for Dave's Supply? Data logging, and i don't know what feature we could set in.

Because no one except Dave has the latest, up-to-date hardware and software of that supply. And my understanding is Dave is still thinking about changes, e.g. going SMD. You are, of course, free to start your own software project for Daves or any other power supply right now. No need to wait for "us".

[george graves]

[EEVblog]

I have no plans for any PC/web control software, as I don't really need that myself (for now). I'm just building in the capability to have PC control if people want that.

Dave.

[shebu18]

Because no one except Dave has the latest, up-to-date hardware and software of that supply. And my understanding is Dave is still thinking about changes, e.g. going SMD. You are, of course, free to start your own software project for Daves or any other power supply right now. No need to wait for "us".

I do not mean to do it right now, we could start after the final PCB and Code are published. If you do not want to participate, there is no problem with that.

[Bored@Work]

I do not mean to do it right now, we could start after the final PCB and Code are published.

You know, I always get nervous when someone says "we". It typically means "someone else". So, when will you start?

[TerminalJack505]

I do have to admit that the software looks pretty cool. 

I'm sure that there will be no shortage of control software for Dave's PSU once it's released.  All the software people will want to do it their own way so you'll wind up with about a dozen different implementations.  LOL.

[shebu18]

I do not mean to do it right now, we could start after the final PCB and Code are published.

You know, I always get nervous when someone says "we". It typically means "someone else". So, when will you start?

As soon as the official PCB and Code are out. My knowledge of codeing is kind of low, but i will do my best.

[sacherjj]

To design a UI, you need to first figure out what you are going to do with it.  But before that you need an API design.  For this, there are not many functions.  You would have something like this.

Read Values:
OutputEnabled
PanelEnabled
VoltageSet
VoltageActual
CurrentSet
CurrentActual
CurrentSensorMode [uCurrent/Normal]  ?
LimitType [Voltage/Current]

Set Values:
OutputEnabled
PanelEnabled [Lock out local control from accidental changes?]
Voltage
Current

If we go with an ethernet module, there will be some configuration.  Perhaps IP address and logging time interval.  It would then send a values packet to a certain IP address when logging is enabled.  Or it could send based on a certain percentage change in values. 

The project that started this thread is completely backwards from my point of view.  It looks like a power supply that is designed to be controlled by a PC.  That is great.  I think Dave's is more realistic.  A power supply that works as a power supply, but also may be controlled by a PC. 

I'm trying to figure out where I would use a setup that would vary the voltage over a fixed time frame, like the macros do in the original project.   I can understand using data logging and graphing features.  I might want to run a micro sensor project for hours and see what it looks like when active or in sleep mode. 

Also, before ANY of this work is done, we should find out what protocols and packets are used by existing power supplies with data capability.  If there is a standard or common API, we would be dumb not to use it if it meets our needs.  For example, does it make sense to follow something like MODBUS/TCP or MODBUS/TCPIP?

[firewalker]

I think (I am sure) that this is the tuxgraphics.org design.

http://tuxgraphics.org/electronics/201005/bench-power-supply-v3.shtml

No reference to in the thesis though. Could be violating the GNU/G.P.L. tbh. 

[Jad.z]

Just look at my avatar and you will know how I fell about this PS and the ~engineer who claimed it.

[BravoV]

I’ve gotta ask. Why do all you people want a PC controlled Bench-top PSU?

One of the reason that I've been thinking and wondering if this combination can be made to form a poor man battery simulator ?

Since the PC can monitor the power consumption vs time, and have a program to adjust the voltage and the current that is proportional with a known battery discharge curve.

[sacherjj]

I’ve gotta ask. Why do all you people want a PC controlled Bench-top PSU?

One of the reason that I've been thinking and wondering if this combination can be made to form a poor man battery simulator ?

Since the PC can monitor the power consumption vs time, and have a program to adjust the voltage and the current that is proportional with a known battery discharge curve.

There were two possible uses that came to mind.  One is that, a battery discharge simulator.  The other was a simulation of a solar cell to develop a charge controller.

[george graves]

I have no plans for any PC/web control software, as I don't really need that myself (for now)

Thanks for adding that functionally in.  If you were to, what would you use?  Processing perhaps? 

Just out of courisity, I picked up some LM317 and plan to bread board them with just a stand alone arduino.  I wonder what kind of accuracy I could get with just the on-board ADC and PWM?  You last 10 videos on the subject have really encouraged me not to be too afraid - and try things out.   (I think "board-at-work" dude could learn a lot from you.  (That is if he doesn't get banned first))

At the risk of sounding like a "brown noser" - you've done an amazing job with the series of tutorials.  I think even the most noob-ish viewer could follow along and understand the process.  Hats off to you.

[codeboy2k]

I think (I am sure) that this is the tuxgraphics.org design.

http://tuxgraphics.org/electronics/201005/bench-power-supply-v3.shtml

No reference to in the thesis though. Could be violating the GNU/G.P.L. tbh. 

It's exactly the tuxgraphics design. He didn't even improve on it, or study it for Load/Line regulation, ripple, etc.  If I was doing that thesis, I'd build it, test all the
Power Supply specs (Line/Load regulation, ripple, holdup time, any overshoot or undershoot, ramp-up time, etc)

Then try to improve upon it. That would be the meat of the thesis. 

Take a look at any thesis from the 60's, 70's, 80's  and you'll see how much more complex and demanding they are of the student, compared to
the theses of today's students.  Most EE theses produced today are garbage, but they get a degree anyways.

A thesis should make a student think, solve something, improve upon something, etc. Students today just "make" something and write it up like a blog entry.