What is range of typical Controller traffic? - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · November 27th, 2015

It's going to vary widely. During discovery, systems startup, or user configuration activities you could see several hundred requests per second. During normal operation, one RDM request per second is a common behavior in my experience, but some controllers don't send any background traffic unless the user specifically does something that requires it.

Nearly all of this background traffic will be GETs and background discovery. SETs typically only happen in response to the user deliberately making a change.

dj41354 · December 7th, 2015

Ok... I'm thinking about a algorithm for scheduling the eeprom write.. how about if I start a timer, say 1second, when I get a SET_DMX_START_ADDRESS command.. then if I get ANY RDM command to me (broadcast, vendorcast or unicast) I restart the time to 1second before writing the new DMX address to eeprom. What this does is tries to fins a "lull" between responding before the eeprom writes take place. Maybe 1second isn't the right value.. maybe 500msec?... Can anyone help me here?
Thanks..
Doug / BlackTank

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
SELF_TEST_DESCRIPTION index range	tim_ecue	RDM General Implementation Discussion	16	February 25th, 2011 09:25 AM

November 27th, 2015	#1
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	It's going to vary widely. During discovery, systems startup, or user configuration activities you could see several hundred requests per second. During normal operation, one RDM request per second is a common behavior in my experience, but some controllers don't send any background traffic unless the user specifically does something that requires it. Nearly all of this background traffic will be GETs and background discovery. SETs typically only happen in response to the user deliberately making a change.

December 7th, 2015	#2
dj41354 Member Join Date: Nov 2015 Posts: 33	Ok... I'm thinking about a algorithm for scheduling the eeprom write.. how about if I start a timer, say 1second, when I get a SET_DMX_START_ADDRESS command.. then if I get ANY RDM command to me (broadcast, vendorcast or unicast) I restart the time to 1second before writing the new DMX address to eeprom. What this does is tries to fins a "lull" between responding before the eeprom writes take place. Maybe 1second isn't the right value.. maybe 500msec?... Can anyone help me here? Thanks.. Doug / BlackTank