|
RDMnet (E1.33) General Discussion General Discussion and questions concerning the E1.33 standard. |
|
Thread Tools | Search this Thread | Display Modes |
October 29th, 2024 | #1 |
Junior Member
Join Date: Jun 2006
Location: Melbourne Australia
Posts: 3
|
Are E1.33 RDM messages meant to be blocking?
We are currently implementing LLRP and have run into some questions.
In a wired RDM environment, RDM messages are half duplex and blocking. This means an RDM message is sent from the controller and no further RDM messages are sent until a response from the Responder is received or a timeout occurs. Is this the same in RDMnet or can a device expect to receive more than one request at a time? The examples in the document in D2 and D4 imply that is it half-duplex and blocking but I can't see anywhere in the standard that states this. If it blocking then what timing information should be implemented - that is how long is a timeout? What turnaround time is expected? These times are specified in Section 3 of E1.20 but they are clearly not applicable in E1.33 If it isn't blocking, then how many messages is a device required to queue? If these questions are answered somewhere in the standard then please just point me towards the relevant section otherwise I value your input. Last edited by GaryLsc; October 29th, 2024 at 04:49 PM. |
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Relative frequency of UID set changes to RDM messages events | nomis52 | RDM General Implementation Discussion | 6 | July 6th, 2010 11:02 PM |