E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM General Implementation Discussion

RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product.

Thread Tools Search this Thread Display Modes
Old January 30th, 2021   #1
Junior Member
Join Date: Apr 2008
Posts: 5
Default E1.37-5 URL parameters

Hey all.

I'm wondering what happened to E1.37-5. Was it ratified? Or is it still under development?

I'd really like to implement URL features, so that controllers can grab device user manuals and other info online. PIDs (proposed) in E1.37-5 include:

4.2 Get Manufacturer URL (MANUFACTURER_URL)
4.3 Get Product URL (PRODUCT_URL)
4.4 Get Firmware URL (FIRMWARE_URL)

Of course, there could be URLs for help on every individual PID, which makes me think there could be a HELP_URL that uses the PID code in its syntax as either a static page or a query. For example:

HELP_URL might be set to "https://mygreatcompany.com/"

Then an RDM controller help feature goes to:



Obviously, the syntax would need to be defined in the standard.


RC4 Wireless / Soundsculpture Inc.
soundscu is offline   Reply With Quote
Old January 31st, 2021   #2
Join Date: Feb 2006
Posts: 436
Send a message via AIM to sblair Send a message via MSN to sblair


E1.37-5 is getting ready to go back out to Public Review in the next couple months. Interesting suggestion on the HELP PID. I'm hoping that the Parameter Description JSON functionality will reduce the need for that by being able to completely describe PID functionality. We also have a JSON URL PID that allows a device to provide a URL where the machine readable JSON description can be fetched as well that should provide similar functionality as to what you've described.
Scott M. Blair
RDM Protocol Forums Admin
sblair is offline   Reply With Quote
Old January 31st, 2021   #3
Junior Member
Join Date: Apr 2008
Posts: 5

Thanks for the quick reply!

The JSON PID sounds ideal for flexibility.

I've been concerned that I don't have a ton of space in flash on our small devices to store long static JSON scripts. I certainly wouldn't do it as straight ASCII, more likely I'd devise a system of symbols to represent keywords in a lookup table. It's considerable infrastructure to build, in any case.

A URL to an online JSON script is a good solution. I look forward to these things becoming part of the spec, and then -- of course -- for controllers to implement them, grabbing those JSON scripts and storing them locally for when the cord is cut while running a live show.

Thanks again,
soundscu is offline   Reply With Quote


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
Sensor Defintion/Support Parameters gthaliath RDM General Implementation Discussion 25 September 1st, 2016 09:38 AM
Request -> Response 2.8ms time requirement and storing parameters in flash alvangee RDM Timing Discussion 6 January 27th, 2015 02:28 PM
CURVE supported : implies CURVE_DESCRIPTION in supported parameters ? RenZO RDM Interpretation Questions 3 April 14th, 2014 04:29 PM

All times are GMT -6. The time now is 04:06 AM.

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