View Single Post
Old January 7th, 2011   #6
Join Date: Feb 2006
Posts: 432
Send a message via AIM to sblair Send a message via MSN to sblair

As has been said, the current PARAMETER_DESCRIPTION PID was only intended to handle a single data value and even at that it is of limited use.

A reminder that you only need to use the PARAMETER_DESCRIPTION PID if you're trying to publicly expose a manufacturer-specific PID to others. If you are just creating it for your own use, then you don't even need to bother with trying to describe it as you'll already know the data structure for it.

If you're trying to make it publicly accessible to other controllers, then I'd try rethinking it and breaking it down into multiple PIDs that each handle a single data value.

Not the best solution, but those are the current workarounds.
Scott M. Blair
RDM Protocol Forums Admin
sblair is offline   Reply With Quote