Single PSU to supply multiple (mini-ITX) motherboards

S

skotl

Hi all,

thought I'd run a theory past the electronically minded amongst you.
I'm going to power 4 mini-ITX boards from a single ATX PSU and I intend
parallel cabling all of the power leads, apart from PWROK and PSON#.

It seems to me that I need to feed both of these to each of the mobos,
but that I should protect each of them from back-feed with a diode. I'm
not sure which way round they should go, tho, because PSON# is active
low, from mobo to PSU and PWROK is active high, from PSU to mobo.

So, I reckon I'm going to do this;

(PSU) PSON---------->|------pin 14 (Mobo1)
|
|--->|------pin 14 (Mobo2)


(PSU) PWROK--------->|------pin 8 (Mobo1)
|
|--->|------pin 8 (Mobo2)


Any thoughts, advice?
Cheers,
Scott
 
P

Paul

skotl said:
Hi all,

thought I'd run a theory past the electronically minded amongst you.
I'm going to power 4 mini-ITX boards from a single ATX PSU and I intend
parallel cabling all of the power leads, apart from PWROK and PSON#.

It seems to me that I need to feed both of these to each of the mobos,
but that I should protect each of them from back-feed with a diode. I'm
not sure which way round they should go, tho, because PSON# is active
low, from mobo to PSU and PWROK is active high, from PSU to mobo.

So, I reckon I'm going to do this;

(PSU) PSON---------->|------pin 14 (Mobo1)
|
|--->|------pin 14 (Mobo2)


(PSU) PWROK--------->|------pin 8 (Mobo1)
|
|--->|------pin 8 (Mobo2)


Any thoughts, advice?
Cheers,
Scott

AFAIK, PS_ON is open collector. There should not be a problem
connecting PS_ON signals from multiple motherboards together,
up to the limits of leakage current. The pullup to +5VSB inside
the PSU would determine how many PS_ON signals can be run in
parallel.

The thing is, when one of the four motherboards activates PS_ON,
the power will go to all four motherboards in parallel and they
will all power up at the same time. Is that what you wanted ?

To get the four motherboards to go to sleep, all motherboards that
are currently asserting PS_ON, will have to be told to stop. That
means that four users, running four copies of Windows, will have
to select S3 Standby, in order for the machine to go to sleep.
That looks messy, and I don't know how the four motherboards
will respond to still being powered, while they are supposed to
be sleeping. (The machines will not go to standby at the same
instant.)

Note that recently, a power conversion device was created, which
is compact and plugs into the ATX 20 pin connector. If you run
four of those power converters from an ATX power supply 12V output,
you would get independent control of the four Mini-ITX motherboards.
In effect, your old ATX power supply becomes a "brick" feeding
four power converters. To make the ATX supply into a "brick",
all that is needed is to connect PS_ON to COM on that PSU.

ATX PSU as source ------ 12V out ---------- Compact ATX
of +12V ------ COM ------------- Converter
PS_ON COM |
| | Mini-ITX
+------+

So, buy four of these, one ATX power supply, and at least you
will have a working solution. If you place a toggle switch
in place of the wire between PS_ON and COM, that will allow
you to turn off the ATX PSU at the end of the say. It will
have to be switched on, before using one of the four
Mini-ITX machines. You must calculate the number of amps
total, as determined by the actual operating power of the
Mini-ITX boards, in order to determine if the +12V output
of the ATX PSU is sufficient for the job.

http://www.mini-itx.com/store/?c=10#picoPSU

HTH,
Paul
 
S

skotl

Hi Paul,
thanks for that.

Think I'm getting there, after a bit of R&D and soldering. There are 4
VIA boards, and their combined rail requirements (plus the disks) are
more than met by the 450w supply I'm putting in.
I could have put 4 ATX supplies, or fed DC-DC supplies (although the
overall power consumption would be higher, given the losses in the
DC-DC tx's) but I'm after a neat, pretty and over-engineered solution.
I bought a brand new 6U server chassis and everything (including the
KVM switch and USB switch for the CDROM) is going in here.

I have also figured out the diode shenanigans; PWROK is just going to
be fed to every board, but PSON# has a 1n4148 flowing *from* the PSU to
each board. This means that as long as one of them is still connecting
their PSON# to ground, current flows thru the diode and the PSU
supplies juice.
When the last of the four raises PSON# (actually, allows it to float)
then PSON# at the PSU will float up and the power will be cut.
Worst effect on the other boards that were waiting is that they sit
with the OpSys saying "it is OK to remove power".

Final trick is that I couldn't figure how to split all the power cables
without using veroboard (doubts over current capacity) or splicing them
together (yuck), so I have invented my own bus with eight 2.5mm rails,
and the cables are looped and soldered to the rails.
There are eight cos that is the number of discrete supplies / signals
from an ATX PSU.

All works, with 2 boards on the bench. I'll let you know when I tie 'em
all up for real!
Cheers,
Scott
 
P

Paul

"skotl" said:
Hi Paul,
thanks for that.

Think I'm getting there, after a bit of R&D and soldering. There are 4
VIA boards, and their combined rail requirements (plus the disks) are
more than met by the 450w supply I'm putting in.
I could have put 4 ATX supplies, or fed DC-DC supplies (although the
overall power consumption would be higher, given the losses in the
DC-DC tx's) but I'm after a neat, pretty and over-engineered solution.
I bought a brand new 6U server chassis and everything (including the
KVM switch and USB switch for the CDROM) is going in here.

I have also figured out the diode shenanigans; PWROK is just going to
be fed to every board, but PSON# has a 1n4148 flowing *from* the PSU to
each board. This means that as long as one of them is still connecting
their PSON# to ground, current flows thru the diode and the PSU
supplies juice.
When the last of the four raises PSON# (actually, allows it to float)
then PSON# at the PSU will float up and the power will be cut.
Worst effect on the other boards that were waiting is that they sit
with the OpSys saying "it is OK to remove power".

Final trick is that I couldn't figure how to split all the power cables
without using veroboard (doubts over current capacity) or splicing them
together (yuck), so I have invented my own bus with eight 2.5mm rails,
and the cables are looped and soldered to the rails.
There are eight cos that is the number of discrete supplies / signals
from an ATX PSU.

All works, with 2 boards on the bench. I'll let you know when I tie 'em
all up for real!
Cheers,
Scott

Well, I really don't think the diodes are necessary on PS_ON#. But
if you feel it is safer, and it actually works for you, then go ahead.

Page 25 here states the spec for the PS_ON# input:

http://www.formfactors.org/developer\specs\ATX12V PSDG2.01.pdf

The PS_ON# signal should be pulled to 0.8V or lower, to turn
on the supply. The diode in series with the output driver from
the EPIA, will make that spec a bit harder to meet.

I looked at an 8712F Super I/O chip, which has a PS_ON# driver on
it, and it uses an open collector driver when in PS_ON# controlling
mode. Leakage is 10uA (which is negligible and can be ignored).
The driver can sink 8mA on that device. And the ATX spec says you
should be able to sink at least 1.6mA.

Perhaps using a Schottky diode, instead of the 1N4148, would help
reduce the voltage drop. I suppose, as long as it works
for you, then carry on :) (Your use of the diode handles the case
where the motherboard uses a normal push/pull driver, instead of
the proper open collector one. I don't think there is anything
to prevent a motherboard maker from using a normal push/pull
driver. Using open collector or open drain is just by convention.
So your use of the diode on PS_ON# does cover off that possibility.)

I'm a bit curious about how the two computers deal with the
common power.

Say we have Comp1 and Comp2...

1) We turn on via Comp1. Both Comp1 and Comp2 power up ?
Does Comp2 complain in any way, that its power control circuit
is not currently asserting PS_ON# and yet the computer is powered ?

2) With Comp1 controlling PS_ON#, as in (1), if you select shutdown
on Comp2 menu, do you see "It is safe to turn off..." message on the
video output of Comp2 ?

3) With Comp1 controlling PS_ON#, as in (1), what happens if you
press the power switch on Comp2 ? I presume if it wasn't asserting
PS_ON#, then it might start to. If it wasn't asserting PS_ON#, how
does it deal with the Power Management event that says "hey, we
are powered, and we just received a request to power up" ?

For this to work properly, you would think a computer that finds itself
powered, would be best advised to start asserting PS_ON# as soon as
it POSTs. I'm curious just how the four computers deal with the
lack of synchronization between power states and the condition of
their logic. (I'm not suggesting something destructive happens,
just that the software on the computer will be in states you might
not normally run into in a one_supply/one_motherboard system.)

As for the pico power converter, I think it is a fairly high
efficiency device, and the lack of visible heat sinks tells you
that. If it is 90+% efficient, and you used a Seasonic 80% efficient
supply as a "brick", I think the 72% efficient overall result, might
still beat a crappy 68% efficient cheap ATX supply :) So while
the pico power idea is expensive, it isn't the worst source of
power you could find from an efficiency viewpoint. I have seen
concatenated conversion used in commercial non-ATX power supplies
(one switcher circuit feeds a second switcher, before driving the
load). So it has been done.

Paul
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top