Filling Device Labels to 32 chars is an error? - E1.20 RDM (Remote Device Management) Protocol Forums

sblair · June 13th, 2013

Hamish and Eric are correct. I'm really not even sure why there should be a case you would need to NACK any of the Discovery commands.

ACK_TIMER is absolultely out for Discovery Commands. No good would come from allowing that.

este_ · June 13th, 2013

"I'm really not even sure why there should be a case you would need to NACK any of the Discovery commands." -> This might be the only way to let the controller know something was incorrectly formatted.

"It's common to see responders that will NACK invalid discovery requests, so controllers should be able to handle that condition." Yes!

"The intent of the standard was to simplify discovery... and not be slowed down by NACK responses." Right, but generating a less than 2ms response will not slow down the discovery process, when compared to a timeout.

"Table 6-7: Response Type Field Allowable Values from Responder". That's convincing. My resolution is simple: I'll let the controller talk rubbish and shut up.

June 13th, 2013	#1
sblair Administrator Join Date: Feb 2006 Posts: 441	Hamish and Eric are correct. I'm really not even sure why there should be a case you would need to NACK any of the Discovery commands. ACK_TIMER is absolultely out for Discovery Commands. No good would come from allowing that. __________________ Scott M. Blair RDM Protocol Forums Admin

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

June 13th, 2013	#2
este_ Junior Member Join Date: Jan 2010 Location: Germany Posts: 24	"I'm really not even sure why there should be a case you would need to NACK any of the Discovery commands." -> This might be the only way to let the controller know something was incorrectly formatted. "It's common to see responders that will NACK invalid discovery requests, so controllers should be able to handle that condition." Yes! "The intent of the standard was to simplify discovery... and not be slowed down by NACK responses." Right, but generating a less than 2ms response will not slow down the discovery process, when compared to a timeout. "Table 6-7: Response Type Field Allowable Values from Responder". That's convincing. My resolution is simple: I'll let the controller talk rubbish and shut up.