[Nut-upsuser] MGE Pulsar Extreme communication problems

[Daniel O'Connor]

Hi,
I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the 
mge-shut driver but I'm having some problems.

It appears to init OK but I can't, say, turn the outlets off, eg..
harrow:~>upsc mge at localhost
battery.charge: 78
battery.charge.low: 20
battery.runtime: 05760
driver.name: mge-shut
driver.parameter.port: /dev/cuad1
driver.version: 2.0.3
driver.version.internal: 0.65
input.frequency: 50
input.voltage: 237
outlet.0.desc: Main Outlet
outlet.0.id: 0
outlet.0.switchable: 0
outlet.1.autoswitch.charge.low: 0
outlet.1.delay.shutdown: -1
outlet.1.delay.start: -1
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 1
outlet.1.switch: 1
outlet.1.switchable: 1
outlet.2.autoswitch.charge.low: 0
outlet.2.delay.shutdown: -1
outlet.2.delay.start: -1
outlet.2.desc: PowerShare Outlet 2
outlet.2.id: 2
outlet.2.switch: 1
outlet.2.switchable: 1
output.frequency: 50
output.voltage: 231
output.voltage.target.battery: 48
output.voltage.target.line: 48
ups.delay.shutdown: -1
ups.delay.start: -1
ups.load: 26
ups.mfr: MGE UPS SYSTEMS
ups.power.nominal: 1500
ups.serial: 885F50007
ups.status: OL CHRG
ups.test.result: No test initiated

However...
harrow:/usr/local/etc/nut>upsrw -u admin -p password -s outlet.1.switch=0 
mge at localhost
harrow:/usr/local/etc/nut>upsrw -u admin -p password -s outlet.2.switch=0 
mge at localhost
harrow:/usr/local/etc/nut>upsc mge at localhost outlet.1.switch ; upsc 
mge at localhost outlet.2.switch
1
1

ie no change.
Also, trying to set, say ups.delay.shutdown works unreliably - I can set it
but I usually either have to wait a bit or repeat the command a few times.

I've tried USB comms but it comes up with a small subset of status..
(I see a lot of IO errors scroll by in debug mode)

I tried setting pollinterval=20 in ups.conf (in the mge section) but no
change.

I have sniffed the RS232 traffic using watch & hexdump and it seems to be
a fairly continuous stream of data.. Maybe the UPS can't keep up? I'm 
not seeing any buffer overflow type messages from my kernel so I think
the PC is OK.

Here is what it looks like starting up..
harrow:~>sudo /usr/local/libexec/nut/mge-shut -D -D -a mge
Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.65 (2.0.3)
debug level is '2'
entering upsdrv_initups()
entering shut_ups_start()

Communication with UPS established
entering shut_get_descriptor(n 21, 9)
shut_wait_ack(): ACK received
entering shut_get_descriptor(n 01, 18)
shut_wait_ack(): ACK received
Device Descriptor:
bLength:                0x12
bDescriptorType:                                        0x01
bcdUSB:                 0x0110
bDeviceClass:           0x00
bDeviceSubClass:                                        0x00
bDeviceProtocol:        0x00
bMaxPacketSize0:                                        0x08
idVendor:               0x0463
idProduct:              0xffff
bcdDevice:                                              0x0100
iManufacturer:          0x04
iProduct:                                               0x7c
iSerialNumber:          0x36
bNumConfigurations:     0x01

entering shut_get_descriptor(n 22, 1535)
shut_wait_ack(): ACK received
entering initinfo()

entering shut_identify_ups(0x0004, 0x007c)

shut_wait_ack(): ACK received
shut_wait_ack(): ACK received
] on /dev/cuad1 [885F50007
entering shut_get_report(id: 0c, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 34, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 0c, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 0d, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 16, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 17, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 2f, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 20, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 07, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 0a, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 0a, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 07, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 04, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 04, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 12, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 04, len: 1800)
shut_wait_ack(): ACK received
entering shut_get_report(id: 04, len: 1800)
shut_wait_ack(): ACK received
...

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060516/853a5ab0/attachment.pgp