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 January 23rd, 2026   #7
ericthegeek
Task Group Member
 
Join Date: Aug 2008
Posts: 390
Default

You can use the "Prefix" field of SENSOR_DEFINITION.

For example, if you need to display 6.3 volts, then you can use PREFIX_DECI in SENSOR_DEFINITION and return the integer 63 in SENSOR_VALUE.

Depending on how much precision you need, you could also use PREFIX_MILLI and return the integer 6300.

When using prefixes, it's up to the controller's User Interface to determine how to display the data. For my second example, the controller might display "6300 mV", or it might display "6.300 V". Or it might let the user configure how the data is displayed.
ericthegeek 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
Response to GET:QUEUED MESSAGE when NACKing query prwatE120 RDM Interpretation Questions 3 February 24th, 2016 05:33 PM
What NACK to use for messages sent to Subdevices ? prwatE120 RDM Interpretation Questions 0 February 24th, 2016 05:08 PM
Status Message Markers hamish RDM General Implementation Discussion 4 December 9th, 2010 11:12 PM
Personality & Subdevices kocurr RDM General Implementation Discussion 1 July 8th, 2008 09:30 PM
ENTTEC RDM controller (subdevices) nic123 RDM Marketplace Discussion 3 October 24th, 2007 12:03 AM


All times are GMT -6. The time now is 03:56 PM.


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