View Single Post
Old June 13th, 2013   #12
este_
Junior Member
 
Join Date: Jan 2010
Location: Germany
Posts: 24
Default

"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.
este_ is offline   Reply With Quote