DiyLightAnimation

You are not allowed to view links. Register or Login

So right now with my firefli in legacy mode (controllers 17, 18 & 19) on the LOR network xlights should control them, correct?

So with what Jon is saying (Correct me if I am wrong) NO you cannot run Firefli without first programming them to work in DMX open.

Well then once again, I hit the wall......

OMG!!! Did I read that correctly? So xlights will not see/control the firefli on a regular LOR dongle? So I would have to add the firefli as their own network and use the d-light dongle? yikes!

My firefli are run in Legacy mode on the LOR network.

I still cannot get the test tab in xlights to turn them on.

Does the firefli controller number matter at all? The number is way up there compared to my other controllers.

Thank you
Eric

I am not at home, but here is an old network config picture. The only difference is that the LOR Com was moved to the first postion after rdebolt mentioned to switch it around.

Here is a picture of the channel config in LSP. Is this my problem? Should I go through and change all LOR controllers?
In LSP (for this sequence) I use 2 zones. A LOR Com3 szone for all my LOR controllers and an E1.31 zone for the 5 E682 noards.

Are my firefli compatible with xlights? Cause they are the only thing that doesn't work on the testing tab.
But maybe if I re-number everything we will be okay.

Thank you
Eric

Okay! I finally was able to get LightElf to export the file successfully (it was throwing a memory error! luckily that was old hat!)

I tried using xlights to convert a LOR sequence to xseq and I used LightElf to convert the same sequence from LSP to xseq....

Both had terrible results.....

First! The network setup: This happens with both output files from each sequencer. My firefli will not recognize the xlights setup test page. Everything else on the LOR COM3 network looks great! And actually runs perfectly! But no firefli..... The E1.31 numbers are perfect. I went through I shimmered the first pixel in each DMX universe and each of them lit up appropriately.

second: When I use the xlights convert tab to change over a LOR sequence to xseq, I received a lot off errors. 2/3s of my DMX channel unmapped. What can I do to correct that? The E1.31 were off by a color. Green was blue....

Third: when I used LightElf to convert the same sequence (but in LSP form) it created a HUGE log file. And all the DMX channels were off..

forth: I have no clue what to do now.

Thank you for your help.
Eric

Ok, small fix.
I allowed python to use more than 2GB of memory and now it seems to be working. It spiked a 2.1GB and then drops down and then seems to be holding at 1.7GB and the green bar is actually growing! The program is 5 min further into conversion then before (I have been used to timing processes since all the memory issues I had with LSP and LOR) and so it is either working, or just messing with me out of spite!

LOL!

HAHA!! Spoke too soon!

I received an memory error!

Am I finished?

I assume this is a 32bit program? If so what file should I manipulate to use more memory? Python?

Eric