Author Topic: LOR - CCR problems  (Read 4473 times)

Offline BobinWV

  • Jr. Member
  • **
  • Posts: 97
    • View Profile
LOR - CCR problems
« on: March 26, 2014, 10:30:55 AM »
Having  xLights/Falcon FPD/LOR CCR problems and I am not sure what is causing the problem.
My CCR is set for RGB only.  I am using xLights 3.3.2.
The CCR is connected to a FPD with port set for DMX control.
If I plug a 27 channel DMX controller into  the DMX port everythings works as expected.
If I connect the CCR to the  DMX port the CCR flashes are very erratic.  I have some WS2811’s connected to an F-16 also connected to the FPD and they follow the test commands from xLights correctly.

Any thoughts?

Bob

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: LOR - CCR problems
« Reply #1 on: March 26, 2014, 08:28:17 PM »
The LOR CCRs (like ALL LOR or D-Light boards) must use a "crossover" adapter.

Look in the CAT5 jack. There are 8 wires. The FPD uses the first two (1 and 2).  LOR uses the 4th and 5th. You need a crossover to move the signal to the correct wires.

http://nutcracker123.com/forum/index.php?topic=134.msg620#msg620


Offline BobinWV

  • Jr. Member
  • **
  • Posts: 97
    • View Profile
Re: LOR - CCR problems
« Reply #2 on: March 26, 2014, 08:38:48 PM »
I am.

Bob

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: LOR - CCR problems
« Reply #3 on: March 28, 2014, 09:04:13 AM »
Bob, how are you connected to the FPD?  I have to assume you are using a Falcon Pi (FPP) in bridge mode, but you never mentioned it in your setup.

Have you gotten any other help from your LOR forum post?

Offline BobinWV

  • Jr. Member
  • **
  • Posts: 97
    • View Profile
Re: LOR - CCR problems
« Reply #4 on: March 28, 2014, 10:17:08 AM »
Jon I am running in the bridge mode and have set Ports 9-12 on the FPD to be dmx.  I have verified that I have signal out with a 27 channel  DMX board and the lights react accordingly.  The CCR controller is set to RGB only and has an address of 01.  It is connected via a crossover cable.
Did some more checking and used Nutcracker color was so I would have a steady signal.  The colors are right and the light count is right, BUT the lights are flashing very slowly rather then being on constantly.

Thanks

Bob

Offline dkulp

  • Supporting Member
  • Hero Member
  • *
  • Posts: 812
    • View Profile
Re: LOR - CCR problems
« Reply #5 on: March 28, 2014, 02:54:47 PM »

Can you try a rainbow colorwash or chase or something that would cause the color value to change every tick?   Even a fast shimmer between two very close values.   By default with xLights, if nothing changes in a universe, it will only send it out every 500ms instead of every 50ms.  I'm wondering if the CCR's cannot handle that and require it more often.

If you have a Mac, I'd be happy to give you a custom build of xlights that sends out more often if you want to try it.  :-)

Dan
Daniel Kulp
Framingham, MA

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: LOR - CCR problems
« Reply #6 on: March 28, 2014, 04:17:37 PM »
Jon I am running in the bridge mode and have set Ports 9-12 on the FPD to be dmx. 
Bob

While I have zero experience with CCRs from LOR, my FPD output on port 9 was never as steady as it was on port 1 or port 5. You can assign the exact same DMX channels to all 12 ports and see if any of them work better.

Now that I put that in words, it occurs to me that if you put DMX out on Port 3, Port 7 or Port 11, it would be on "wires 4 and 5" and you may not need to use a crossover to talk to an LOR board (unless they have Data+ and Data- backwards).
« Last Edit: March 28, 2014, 04:19:10 PM by JonB256 »

Offline BobinWV

  • Jr. Member
  • **
  • Posts: 97
    • View Profile
Re: LOR - CCR problems
« Reply #7 on: March 28, 2014, 07:38:23 PM »
Jon Tried all ports and they all act the same.  I am going to call David Pitts tomorrow..perhaps he has some thoughts on the problem.  I tend to think that it might be a CCR problem since another device on the same port works perfectly.

Bob