E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM Interpretation Questions
Register FAQ Community Calendar Today's Posts Search

RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard.

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old April 1st, 2025   #3
zano_villa
Junior Member
 
Join Date: Jan 2014
Location: Treviso, Italy
Posts: 21
Default

Hello,
On page 55 of the standard in reference to SUPPORTED PARAMETERS PID it is written: "Manufacturer specific PIDs may or may not be included in the response". If I have implemented a MANUFACTURER SPECIFIC PID in my device, I need to list it otherwise the controller has no other way of knowing about its existence. Am I right? And what about the STATUS_ID_DESCRIPTION of a MANUFACTURER SPECIFIC message? How does the controller know in advance the implemented STATUS ID to be able to request its description?
Does it request it a posteriori? Thanks
zano_villa is offline   Reply With Quote
 

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
SubDevice Required PIDs LarryDew RDM General Implementation Discussion 1 March 25th, 2014 08:27 PM
Subdevice labelling question berntd RDM General Implementation Discussion 13 August 15th, 2013 11:13 PM
Self test description question sondericker RDM Interpretation Questions 28 November 2nd, 2010 10:31 PM
Command Class / Parameter ID mismatch handling dangeross RDM Interpretation Questions 2 April 16th, 2009 01:39 PM
ASN.1 description of RDM sjackman RDM General Implementation Discussion 2 September 19th, 2006 10:20 AM


All times are GMT -6. The time now is 06:37 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.