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.

Reply
 
Thread Tools Search this Thread Display Modes
Old November 24th, 2014   #1
daniel
Junior Member
 
Join Date: Nov 2014
Posts: 2
Default New PID: IDENTIFY_DEVICE_WITH_TIMEOUT

Relating to the discussion here:
http://www.rdmprotocol.org/forums/showthread.php?t=1058

This is my proposal for an expiring fixture identification message. The purpose is to allow a controller set the device into identify mode, while allowing the identify state to expire in the case that the controller is unplugged (such as a handheld device that is quickly moved to a new cable) or the cables are re-plugged, preventing an identify off command.

This should be a configurable option in the RDM controller being used.

IDENTIFY_DEVICE_WITH_TIMEOUT
One parameter, 16-bit, timeout in seconds.

Range: 0 - 65,535

Behavior:
IDENTIFY_DEVICE_WITH_TIMEOUT with a non-zero parameter causes the fixture to identify in the selected mode (loud or quiet if supported) for the specified time. When the time has elapsed, the fixture behaves as though it has received an IDENTIFY_DEVICE[off] message.

IDENTIFY_DEVICE_WITH_TIMEOUT[0] causes the fixture to identify 'once' or one cycle, or for one second, as it makes sense to the fixture implementation.

A fixture may return NR_OUT_OF_RANGE if the timeout is too long for the fixture to support for some reason. Although support up to an hour (3600 seconds) is required if this command is implemented.

If the message IDENTIFY_DEVICE is received, it overrides this command and cancels the timer.

As with IDENTIFY_DEVICE, a power cycle cancels the identification, even if the timer has not expired.

Use case:
A controller (such as the Swisson XMT-350 or the DFD RAD) sends the IDENTIFY_DEVICE[on] message when a fixture is selected. However if the DMX cable is removed from the tester and returned to console control, the fixture will be (possibly permanently) stuck in identify mode. Devices like this could use IDENTIFY_DEVICE_WITH_TIMEOUT[10] to cause the fixture to identify for 10 seconds. When 10 seconds has gone by, the controller can send another IDENTIFY_DEVICE_WITH_TIMEOUT[10], or if the fixture is de-selected, the controller will send IDENTIFY_DEVICE[off] to end identification.

This allows a fixture to return to operation in a sane way in the case that the tester is removed from the system.
daniel is offline   Reply With Quote
Old November 25th, 2014   #2
nomis52
Task Group Member
 
Join Date: May 2010
Location: San Franciscio
Posts: 57
Default

Hi Daniel,

It's fine to have a discussion here, but please submit the request during public review of E1.37-5 . It was approved for public review last week, so the public review period should open in a month or so.

Simon
__________________
Open Lighting Project: www.openlighting.org
RDM Responder Tests: www.rdmtests.org
nomis52 is offline   Reply With Quote
Old March 2nd, 2015   #3
prwatE120
Task Group Member
 
Join Date: Jun 2006
Posts: 180
Default

To resolve the problem you have identified, we ensure that IDENT is automatically disabled after 90 seconds on our products, at which time they also queue a message to inform the controller that the IDENT state has changed.
prwatE120 is offline   Reply With Quote
Reply

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


All times are GMT -6. The time now is 11:49 AM.


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