|
RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product. |
|
Thread Tools | Search this Thread | Display Modes |
November 3rd, 2017 | #1 |
Member
Join Date: Oct 2017
Location: Turkiye
Posts: 38
|
2 sets of personality
hi everyone
I m new to RDM, trying to design RDM-DMX LED fixture. I have read old posts and found answers for most of my questions. planning to make LED array fixture with 2 sets of personalities: 1: LED/pixel: {1 LED/pixel, 3/LED/pixel, ...} 2: Color: {RGB(3channel), RG(2ch), R(1ch) , ...} seems it is not possible to have more than 1 set of personalities. shall I do it using Manufacture specific PIDs? or is there better approach ? |
November 3rd, 2017 | #2 |
Administrator
|
Majid, Welcome to the forums!
Yes, there is only 1 set of personalities. I would take caution in how you implement this as having a large number of combinations/personalities will make it much more difficult for you to get support from lighting consoles as they may only choose to implement a couple of the personalities and not all 23 of them... DMX channels are relatively cheap these days so having lots of complex combinations just to save on DMX channels may not be actually saving you that much.
__________________
Scott M. Blair RDM Protocol Forums Admin |
November 3rd, 2017 | #3 |
Member
Join Date: Oct 2017
Location: Turkiye
Posts: 38
|
Thank you scott
I m happy joned the forum! I understand, I have already implemented LED/pixel yet, its amzing for me! I think its better to avoid Slot/pixel, it seems useless Thanks |
December 14th, 2017 | #4 |
Task Group Member
Join Date: Jun 2006
Posts: 181
|
Majid
Scott's answer may have been over cautious. There are plenty of fixtures with multiple personalities to allow the user to select the best slot allocation for their application and DMX footprint. That said, I suggest exceeding 15-20 is excessive, and may result in some (poorly implemented IMHO) controlllers not allowing access to all your options. I would restrict the use of Manufacturer specific PIDs where possible - as many of the current controllers so NOT allow access to them in any form. Again, a controller limitation that will reduce in time. Man Spec PIDS are ideal for things like calibration and current settings that the end user is not normally expected to tamper with. Since you are developing a responder, I would commend the RDMIntegrity package to you - it is a compregensive toolset for verifying RDM responder implementations. PM me if you would like more information. Peter |
December 16th, 2017 | #5 |
Member
Join Date: Oct 2017
Location: Turkiye
Posts: 38
|
I agree the "keep it simple" principle and try not to mess with special PIDs unless its really needed
For my current project, standard PIDs satisfy requirements, Actually I need a verification to unveil hidden bugs, faults Thanks |
August 11th, 2018 | #6 | |
Junior Member
Join Date: Aug 2018
Posts: 1
|
Quote:
Last edited by ArdenCro; November 19th, 2022 at 02:17 PM. |
|
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sub Device and Personality | kster | RDM Interpretation Questions | 1 | July 29th, 2009 10:00 AM |
DMX Personality | p_richart | RDM Interpretation Questions | 6 | November 12th, 2008 10:53 PM |
Personality & Subdevices | kocurr | RDM General Implementation Discussion | 1 | July 8th, 2008 10:30 PM |