EOS Programming wing and problems with RDM

Hello everyone.


* (Soft EOS 2.7.2)
I use a fixture that implements RDM. I connect it to the Dmx 1 or 2 wing universe, but it does not identify the fixture. There is noRDM communication. What can happen?

Thanks in advance.

Parents
  • Are you going through an Opto / Splitter?
    Is that Opto RDM Compliant?

    Is the Gadget using the exact same wiring configuration?

  • eeehhhh !!!!   [:O]
    I do not understand absolutely nothing. 
    After many  [C][C]       try something unusual ... and voila! It works ... but I do not understand it.
    It turns out that the ports marked as "Console", are not those of the console .... but then what is its meaning?

     

    [:#][:#][:#]                                                             [:#] [:#][:#]

  • So you plugged the Gadget in and assigned its port 1 as the same DMX output as the console's port 1 DMX output.
    I don't know the Gadget well, but it looks like it superseded control from the console.
Reply
  • So you plugged the Gadget in and assigned its port 1 as the same DMX output as the console's port 1 DMX output.
    I don't know the Gadget well, but it looks like it superseded control from the console.
Children
  • not....
    Actually, I was activating ports 1-2 that are marked as a console (?) .... thinking that they were those of the Programming wing.
    However, the Dmx-Rdm ports of the programming wing are marked (identified) as Gadget [serial no. --------]
    Programming wing only has two DMX-RDM ports.
    I imagine that the four ports (Console) DMX-RDM, correspond to Ion, Gio..etc.
    For me it is confusing, hence the mistake made.

    Summary; confusion with the identification of ports ... my fault. [+o(]

  • No worries.
    Learning something new is always a good day.