![]() |
|
|||||||
| RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product. |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#6 |
|
Administrator
|
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 |
|
|
|
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Manufacturer Specific Pids | berntd | RDM General Implementation Discussion | 4 | November 29th, 2009 02:50 PM |
| PARAMETER_DESCRIPTION data type semantics | tim_ecue | RDM Interpretation Questions | 4 | October 14th, 2009 10:47 AM |
| PDL size and manufacturer specific parameter ID's | jamie | RDM General Implementation Discussion | 5 | July 13th, 2009 12:31 AM |