Nut upsdev - Jul 2010 - Prefered Method for UPS?

Hello,

since I had delayed the programming of the UPS Device part,  now  it  is
time to continue...

My Device is "24 V DC modular ATX PSU" which replace  the  standard 
ATX
Power Supply in PCs and use 15-43 V Input Voltage.  The  microcontroller
is a TI LM3S5T36 Cortex M3 and I get the "UPS" infos using up to 4
Maxim
DS1780 and some I?C current sensors.  The ATX  PSU  has  4 Module  Slots
which can be indivdualy equiped.  Also the ATX PSU can be equiped with a
4-Cell LiPoly-Block (14,4V/12Ah).

Also the "24 V DC modular ATX PSU" identify it self as USB serial
device
using /dev/ttxyUSBxx

All infos from the DS1780 and current sensors are currently stored in  a
multi-dimensional Array.

So, currently I realy do not know HOW I schould send the infos to NUT.

Can you tell me what the prefered method is for NUT?

The MCU is gattering the infos like:

1)  own identification (Maxim DS28CZ04)
    0000 -> "12345678"               # serial number           \
    0001 -> "24V DC modular ATX      # real name of the modue  | I?C
EEPROM
    0002 -> "electronica at tdnet"      # Vendor Real Name        |
Maxim DS28CZ04
    0003 -> "1.0.0"                  # Version                 |
    0004 -> "2010-07-08"             # Manufacturing Date      /
    0010 -> "24,0"                   # Input voltage  (200mV/LSB)
    0011 -> "12,0"                   # input current  (0-25.5A)

2)  Expansion Module Slot 0
    0100 -> "12345678"          # serial number      \
    0101 -> "ATX 1"             # real name          | I?C EEPROM
    0102 -> "electronica at tdnet" # Vendor Real Name   | Maxim
DS28CZ04
    0103 -> "1.0.0"             # Version            | on module
    0104 -> "2010-07-08"        # Manufacturing Date /
    0110 -> "3,30"        # +3.3V voltage
    0111 -> "15,0"        # +3.3V current           (17.3mV/LSB)
    0112 -> "5,00"        # +5V   voltage
    0113 -> "5,0"         # +5V   current           (26mV/LSB)
    0114 -> "12,0"        # +12V  voltage
    0115 -> "8,0"         # +12V  current           (62.5mV/LSB)
    0116 -> "5,00"        # +5V   standby voltage   (26mV/LSB)
    0117 -> "0,3"         # +5V   standby current
    0118 -> "-12,30"      # -12V  voltage           (96mV/LSB)
    0119 -> "53"          # Temp  in ?C             (-40 to +125?C)
    011A -> ""            # Fan Speed 1
    011B -> ""            # Fan Speed 2
    011C -> "false"       # Chassis Intrusion

2)  Expansion Module Slot 2
    0200 -> "12345678"          # serial number      \
    0201 -> "SATA 16"           # real name          | I?C EEPROM
    0202 -> "electronica at tdnet" # Vendor Real Name   | Maxim
DS28CZ04
    0204 -> "1.0.0"             # Version            | on module
    0205 -> "2010-07-08"        # Manufacturing Date /
    0210 -> "3,30"        # +3.3V voltage
    0211 -> "15,0"        # +3.3V current           (17.3mV/LSB)
    0212 -> "5,00"        # +5V   voltage
    0213 -> "5,0"         # +5V   current           (26mV/LSB)
    0214 -> "12,0"        # +12V  voltage
    0215 -> "8,0"         # +12V  current           (62.5mV/LSB)
    ...

4)  Expansion Module Slot 4
    0400 -> "12345678"          # serial number           \
    0401 -> "Backup"            # real name               | I?C
EEPROM
    0402 -> "electronica at tdnet" # Vendor Real Name        |
Maxim
    0403 -> "1.0.0"             # Version                 |
DS28CZ04
    0404 -> "2010-07-08"        # Manufacturing Date      | on
module
    0405 -> "4"                 # Number of cells         |
    0406 -> "120"               # Capacity in mAh/100     |
    0407 -> "2010-07-08"        # Cell Manufacturing Date /
    0410 -> "14,4"        # Batterie voltage
    0411 -> "15,0"        # Dis/Charging current    \
    0412 -> "3.7"         # Cell Voltage 1          |
    0413 -> "3.7"         # Cell Voltage 2          | using
    0414 -> "3.7"         # Cell Voltage 3          | Maxim
MAX11068
    0415 -> "3.7"         # Cell Voltage 4          |
    0416 -> "48"          # Temperature             |
    0416 -> "100"         # Charging state          /

Note:  I have currently 8 differnt Modules available and
       it is not limited to.

So, which is the prefered solution to send this data to NUT?

And my last question:

Is it possibel to SET values from NUT in the "24 V DC modular ATX
PSU"?
I mean something like Alarm, Tresholds and such?

Thanks, Greetings and nice Day/Evening
    Michelle Konzack

-- 
         Development and Production of Low-Energie Electronics,
            Computer Hardware and Solar/Wind-Energie Systems

electronica at tdnet France EURL          electronica at tdnet UG (lim. liab.)
Owner Michelle Konzack                 Owner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz                      Kinzigstra?e 17
67100 Strasbourg/France                77694 Kehl/Germany
Tel: +33-6-61925193 mobil              Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

<http://www.electronica.tamay-dogan.net/>   
<http://www.can4linux.org/>
<http://www.tamay-dogan.net/>           
<http://www.flexray4linux.org/>

Jabber electronica at jabber.ccc.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100708/4e61d2c9/attachment.pgp>

On Thu, Jul 8, 2010 at 7:50 AM, Michelle Konzack
<linux4michelle at tamay-dogan.net> wrote:
> My Device is "24 V DC modular ATX PSU" which replace ?the
?standard ?ATX
> Power Supply in PCs and use 15-43 V Input Voltage. ?The ?microcontroller
> is a TI LM3S5T36 Cortex M3 and I get the "UPS" infos using up to
4 Maxim
> DS1780 and some I?C current sensors. ?The ATX ?PSU ?has ?4 Module ?Slots
> which can be indivdualy equiped. ?Also the ATX PSU can be equiped with a
> 4-Cell LiPoly-Block (14,4V/12Ah).
For reference, here is our documentation on the interface layers that
are available in NUT (and the corresponding terminology):

http://buildbot.networkupstools.org/~buildbot/docs/latest/website/developer-guide.html#_design

So far, new equipment has not required changes in the server (upsd).
For extended information (such as all of the module voltages), certain
clients may need to be extended, but that is something to consider
later.

And you are designing the equiment, so that means that the answer to
your question lies in how much work you want to do on a custom driver,
versus reusing an existing driver. That decision drives what you will
have to do with the PSU firmware.

If you are primarily looking for NUT's original design goal of
shutting down a system when the power gets low, there are many serial
protocols that you can reuse for this. Most of the serial protocols
are limited to status* (line power good, battery level good, etc.), a
single input voltage measurement, a single output voltage measurement,
load percentage, and possibly runtime. This is probably the least
amount of work you can get by with - just pick a driver, and send back
an identification string that the driver recognizes.

*
http://buildbot.networkupstools.org/~buildbot/docs/latest/website/developer-guide.html#_manipulating_the_data
(specifically "5.9.3. Status data")

If you want a more extensible system (so that users don't need to
change drivers if you decide to upgrade the firmware) I would suggest
looking at the USB HID Power Device Class specification:

* http://www.usb.org/developers/devclass_docs/pdcv10.pdf

...which is essentially an addendum to the generic USB HID document:

* http://www.usb.org/developers/hidpage/ (Device Class Definition for HID 1.11)

It is probably easier to add a set of HID mappings to NUT's usbhid-ups
than to write a completely extensible serial driver from scratch. On
the other hand, if your USB interface does not have a good HID device
class API, there might be a lot of setup work involved. I guess it
depends on your timeline, and how much you want to set up before
starting to get your users to test the driver.
> Is it possibel to SET values from NUT in the "24 V DC modular ATX
PSU"?
> I mean something like Alarm, Tresholds and such?
*
http://buildbot.networkupstools.org/~buildbot/docs/latest/website/developer-guide.html#_enumerated_types
and the following sections

*
http://buildbot.networkupstools.org/~buildbot/docs/latest/website/developer-guide.html#new-names

-- 
- Charles Lepple