E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM Interpretation Questions

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 September 17th, 2024   #1
Qasi_
Junior Member
 
Join Date: Sep 2024
Location: Germany Berlin
Posts: 6
Default RDM 1.37-5 Schema "different_pid" used in QUEUED_MESSAGE not part of Schema

While implementing 1.37-5 i found this.
if i validate QUEUED_MESSAGE with the Schema of 1.0.0
it prompt me an Exception, because the Enum "different_pid" is not specified in the Schema.
Currently in the Schem its defined like:

Code:
"enum": [
  "get_request",
  "get_response",
  "set_request",
  "set_response"
]

but should be

Code:
"enum": [
  "get_request",
  "get_response",
  "set_request",
  "set_response",
  "different_pid"
]
Qasi_ is offline   Reply With Quote
 

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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
DMXter4 says "not responding" dj41354 RDM General Implementation Discussion 11 November 27th, 2015 06:59 AM
New PID "Slot Labels" este_ RDM General Implementation Discussion 5 August 14th, 2014 09:26 AM
New PID "CURVE DEFINITION" este_ RDM General Implementation Discussion 0 July 13th, 2014 03:16 PM
Refreshing "parameter_description" ? theguenni RDM General Implementation Discussion 7 March 3rd, 2012 08:06 PM
Refreshing "parameter_description" ? theguenni RDM General Implementation Discussion 0 February 29th, 2012 02:36 PM


All times are GMT -6. The time now is 12:14 PM.


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