No, just as a variable string descriptor.

By “variable string descriptor”, do you mean what is contained in the example 
in the App Note?  I’m just asking for clarification, in case variable string 
descriptor is something different than shown there.

The way they do the string descriptors in the example is how I have mine now.  
They return a size and address, but it is to something that was defined at 
compile time.  I guess I’ve been fixated on that, so I don’t know if I can 
simply pass a different string that what was defined before.  And I don’t know 
how to handle something of an unknown size (though in my case, the MAX size of 
the serial number can be defined)

That’s why I was asking about the variable string descriptor...it sounds more 
like something where you can pass a string of any size and address, which would 
definitely be what I’m looking for.

Looking at the data being passed, I realized that battery.type is something 
else that I possibly won’t know until the code is running.  Our UPS can use 
different attached batteries, and will be able to discern what it is at 
runtime, and that’s when it would be able to report battery.type.

Thanks for the help Charles…that is a very good link to the Appnote considering 
you haven’t done PIC32 work.  ☺  My google skills failed me.


Rob Groner
Software Engineer Level II

RTD Embedded Technologies, Inc.
ISO 9001 and AS9100 Certified
Ph: +1 814-234-8087
www.rtd.com<http://www.rtd.com/>


_______________________________________________
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Reply via email to