Responder Testing FAQ - Revision history

Nomis52 at 03:17, 10 November 2012

2012-11-10T03:17:06Z

Nomis52: /* Which RDM controllers are supported? */

2012-10-13T16:48:40Z

‎Which RDM controllers are supported?

Nomis52 at 16:47, 13 October 2012

2012-10-13T16:47:16Z

Nomis52: /* Which RDM controllers are supported? */

2012-05-08T15:03:30Z

‎Which RDM controllers are supported?

66.92.11.32: /* I disagree with the output of a test / I disagree with the interpretation of the standard */

2011-02-12T20:40:23Z

‎I disagree with the output of a test / I disagree with the interpretation of the standard

Nomis52 at 03:50, 31 January 2011

2011-01-31T03:50:40Z

Nomis52: moved Responser Testing FAQ to Responder Testing FAQ

2011-01-31T03:45:35Z

moved Responser Testing FAQ to Responder Testing FAQ

66.92.11.32: Created page with "== General Information == ==== Is this a E1.20 Compliance Test? ==== No. There is no known industry standard compliance tests for E1.20. Developing these sort of tests is e…"

2011-01-31T03:44:47Z

Created page with "== General Information == ==== Is this a E1.20 Compliance Test? ==== No. There is no known industry standard compliance tests for E1.20. Developing these sort of tests is e…"

New page

== General Information ==

==== Is this a E1.20 Compliance Test? ====

No. There is no known industry standard compliance tests for [[E1.20]]. Developing these sort of tests is expensive and the industry is reasonably small.

==== How is this related to PLASA and the PLASA Standards Group ? ====

Although some of the test developers sit on the PLASA Control Protocols Working Group and/or various Task Groups, this effort is in no way affiliated with PLASA.

== Testing Devices ==

==== Can I run the tests myself? ====

Yes. You need one of the [[#Which RDM controllers are supported?| supported controllers]] and a system on which to run [[OLA]].

==== Can I send my equipment somewhere to have it tested? ====

Yes. You can send RDM responders to us (located in California) and we'll run the tests and send you the output. You'll either need to organize return postage, or agree to leave the hardware with us. If you provide us with a way to upgrade firmware on your devices we'll test new firmware versions for you.

==== I'll only send RDM responders if you pay a deposit, sign an NDA etc. ====

Sorry, this is a best effort volunteer service. We don't have the financial or legal resources to get into this.

==== Can someone work with me to debug my responder? ====

We'll do the best we can to explain the expected behavior and why tests fail. We don't provide consulting services but can recommend freelance RDM developers.

==== Can I pay someone to perform testing for me? ====

Not at the moment. We may provide this service in the future.

== Technical Questions ==

==== Which RDM controllers are supported? ====

Currently the following controller devices are supported:
* [[RDM-TRI]]
* [[DMXter4 RDM]] / [[MiniDMXter]]

==== I make RDM Controllers and I'd like to have my device supported ====

The fastest way is to write the code yourself. Failing that, if you provide the hardware we can work on supporting it.

==== Why isn't signal timing checked? ====

Simply because the developers haven't had time to add this. The amount of information on signal timing is limited by what the RDM controller interfaces provide to the host PC. For now we recommend adding a inline RDM sniffer and using that to check for timing problems.

==== I disagree with the output of a test / I disagree with the interpretation of the standard ====

Where the [[E1.20]] standard is ambiguous, the . If you think one of the test cases is wrong start a discussion on the [[http://www.rdmprotocol.org/ RDM Protocol Forums]].

← Older revision		Revision as of 20:40, 12 February 2011
Line 49:		Line 49:
	==== I disagree with the output of a test / I disagree with the interpretation of the standard ====		==== I disagree with the output of a test / I disagree with the interpretation of the standard ====

−	Where the [[E1.20]] standard is ambiguous, the test output reflects the consensus reached by well respected engineers within the industry. If you think one of the test cases is wrong please start a discussion on the [[http://www.rdmprotocol.org/ RDM Protocol Forums]].	+	Where the [[E1.20]] standard is ambiguous, the test output reflects the consensus reached by well respected engineers within the industry. If you think one of the test cases is wrong please start a discussion on the [http://www.rdmprotocol.org/ RDM Protocol Forums].

← Older revision		Revision as of 03:50, 31 January 2011
Line 49:		Line 49:
	==== I disagree with the output of a test / I disagree with the interpretation of the standard ====		==== I disagree with the output of a test / I disagree with the interpretation of the standard ====

−	Where the [[E1.20]] standard is ambiguous, the . If you think one of the test cases is wrong start a discussion on the [[http://www.rdmprotocol.org/ RDM Protocol Forums]].	+	Where the [[E1.20]] standard is ambiguous, the test output reflects the consensus reached by well respected engineers within the industry. If you think one of the test cases is wrong please start a discussion on the [[http://www.rdmprotocol.org/ RDM Protocol Forums]].

@@ Line 32: / Line 32: @@
 == Technical Questions ==
 ==== I make RDM Controllers and I'd like to have my device supported ====
@@ Line 48: / Line 40: @@
 Simply because the developers haven't had time to add this. The amount of information on signal timing is limited by what the RDM controller interfaces provide to the host PC. For now we recommend adding a inline RDM sniffer and using that to check for timing problems.
 ==== I disagree with the output of a test / I disagree with the interpretation of the standard ====
 Where the [[E1.20]] standard is ambiguous, the test output reflects the consensus reached by well respected engineers within the industry. If you think one of the test cases is wrong please start a discussion on the [http://www.rdmprotocol.org/ RDM Protocol Forums].

@@ Line 36: / Line 36: @@
 Currently the following controller devices are supported:
-* [[RDM-TRI]]
+* [[RDM-TRI]], supports all except the Discovery Unique Branch tests (under development).
 * [[DMXter4 RDM]] / [[MiniDMXter]]
 * [[DMX USB Pro]]

@@ Line 3: / Line 3: @@
 ==== Is this a E1.20 Compliance Test? ====
-No. There is no known industry standard compliance tests for [[E1.20]]. Developing these sort of tests is expensive and the industry is reasonably small.
+No. There is no known industry standard compliance tests for [[E1.20]]. Developing these sort of tests is expensive and the industry is reasonably small. These tests check a wide range of behavior, but '''do not''' perform extensive testing of the E1.20 timing requirements.
 ==== How is this related to PLASA and the PLASA Standards Group ? ====

← Older revision	Revision as of 03:45, 31 January 2011
(No difference)