![]() |
|
|||||||
| RDM Timing Discussion Discussion and questions relating to the timing requirements of RDM. |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#4 |
|
Senior Member
Join Date: Jan 2008
Posts: 102
|
Hi and thanks.
This is a responder based on a Linux non real time environment. The OS is busy doing heaps of other stuff so we are not able to use interrupts as it takes too much cpu time and we can't get them fast enough when the OS is busy. The coms stuff is therefore usually based on DMA control which is fully automatic, including the inter slot timout setting. The reception of a RDM packet or a DMX packet is therefore fully automatic and no software intervention is necessary. The bytes are reveiced until the timeout occurs and then a single interrupt occurs and this transfers the complete frame / buffer to the host. We will investigate what else we can do but the possibilies are limited. If we have to compromise one of the time 2 values, which one is preferable? I should also mention that we are already checking the start code. Based on DMX or RDM, we use different timout values as the specs differ. Regards Bernt Last edited by berntd; May 26th, 2015 at 04:33 PM. |
|
|
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Timing contraints driver switch from controller to responder | mkoelman | RDM Timing Discussion | 2 | March 18th, 2015 01:44 AM |
| 3.2.1 Responder Packet Timings | prwatE120 | RDM Timing Discussion | 6 | May 23rd, 2009 08:32 AM |
| Packet Captures? | jhuntington | RDM General Implementation Discussion | 0 | March 4th, 2007 07:19 PM |