E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM Physical Layer/Hardware Discussion

RDM Physical Layer/Hardware Discussion Discussion and questions relating to the physical or hardware layer of RDM.

Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old October 20th, 2006   #1
Andy Macdonald
Junior Member
Join Date: Sep 2006
Location: London
Posts: 6
Default Line biasing


I'm sure you're busy at LDI, but when you're back in the office and have a moment, could you explain a little of the background to line biasing please. What is it used for/why does it need to be there? Is it just to maintain the marking state between packets as per section 2.4 or is there more going on?

Sections 2.3 and 2.4.1 of the spec says that you need to have it, and 2.6 says it "shall be enabled prior to RDM communication beginning", but I'm not sure what that means in practice. In particular:

- Should a piece of RDM distribution equipment (eg a DMX/RDM splitter or merger) put line bias on its output ports if it does not detect any on an input port?
- If a fixture/device receives a valid RDM packet, but does not detect line bias, should it obey the packet or ignore it?

The best reason I can come up with for having line bias is that it indicates to a fixture that the controller would receive any RDM response messages it send, and therefore would know that it exists as an RDM fixture. This depends on the behaviour of the fixture and any RDM distro equipment as per my questions though.

For example, if an RDM console was connected to an RDM fixture via a DMX only (non RDM) splitter, the fixture would receive any RDM messages the console sent, but the DMX splitter would not pass any responses back to the console. The console would not therefore be able to detect the fixture, so would not realise there was a fixture it did not know about. It might then send out a command aimed at the RDM fixtures it knew about, but which might be obeyed by the RDM fixture in the non RDM portion of the network. The fixture would not have been detected, so the console would not know its UID, but it could still be something a broadcast message like Set Lamp State where it would have an unintended effect on those fixtures. Maybe the issue of undetected fixtures obeying broadcast messages is just too insignificant a problem to worry about.


Andy Macdonald
Carallon Ltd
Andy Macdonald is offline   Reply With Quote


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Line biasing Flaws - need solutions berntd RDM Physical Layer/Hardware Discussion 7 April 9th, 2009 06:32 PM
3.3V Biasing William CANO RDM Physical Layer/Hardware Discussion 3 December 5th, 2006 08:17 AM In-line device Port Turnaround during Discovery prwatE120 RDM Timing Discussion 1 August 7th, 2006 11:52 PM

All times are GMT -6. The time now is 11:16 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2023, vBulletin Solutions, Inc.