Notifications
Clear all

Vixen 3 LOR Module

15 Posts
6 Users
0 Reactions
26.9 K Views
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

While the above post certainly is functional, it is generally best practice in vixen 3 to get yourself away from the idea of naming your elements in relation to controllers and channels. You should instead name things appropriately for what they actually represent. This helps you get into a thought process that consistent with the V3 workflow. Once you get your mindset changed away from channel based sequencing to element based sequencing, then a everything else in V3 starts to make sense and V3 works more efficiently.
For example, If you have red, green and blue (or even more) strings on your roofline, you are better off defining just a single element called "roofline" and defining the color handling for this element to include the colors of the individual strings. This will reduce the number of elements on your sequencing screen, and will allow you to make good use of the V3 effects. If you want to fade your roofline from red to green, you can use a single pulse effect that says the roofline should change from red to green. No longer would you need to think about fading out the red and fading in the green.

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Posts: 34
(@tripplett)
Eminent Member
Joined: 13 years ago

Yea I realized that after I made the screen shots. It was just a functional test to prove concept. I mentioned that in the post, my naming convention would be less than ideal for sequencing.


Reply
Posts: 1159
(@deonb)
Noble Member
Joined: 13 years ago

What I don't quite understand, how does Vixen know where the LOR dongle is?

e.g. if I use a "LOR USB to RS485 adapter", there has to be some configuration somewhere that tells Vixen that that particular Dongle is on COM 3. Alternatively, if I map it to DMX in LOR itself, Vixen needs to know that the listener is running on port 8837.

However, there is no configuration in the "DMX Open" controller that allows me to set up everything. So how do I tie the particular controller into Vixen?

In the LORCommListener I see:
2014-12-06 02:30:01 30:Listener [INFO ] Listening on port 8837
2014-12-06 02:30:02 710:DMX1 [INFO ] A2004HOi: Raw DMX adapter opened
2014-12-06 02:30:02 32:Listener [INFO ] Connection accepted (768)

but no traffic from Vixen. Even that "Connection accepted" didn't seem to come from Vixen - I think it's the LOR software.

Needless to say, no blinky flashy.


Reply
Posts: 1159
(@deonb)
Noble Member
Joined: 13 years ago

Never mind - I figured it out. There are a few things in play that all have to work together:

1) Vixen will autodetect the LOR USB adapter as an FTDI, but the FTDI driver needs to be the one from VCP (from ftdichip.com), not the one from LOR.
2) Make sure all LOR software is closed, otherwise it will use the FTDI port. Vixen will log an error to the Vixen error log if this it can't open the FTDI. Also make sure the "Play" button is clicked under the LOR controller. If you press top & then play again, Vixen will generally crash. No big deal, just restart it and hit play.
3) Make sure all LOR controller firmware is updated to 4.2 or later. (Or 1.7 on the Gen3 controllers).
4) Make sure your LOR controllers stay on their unit numbers and don't renumber itself. I have a CTB16D that the moment you sent DMX to it, it resets itself to a different unit number. Now I just leave it alone to where it wants to be, and we're both much happier.

Thereafter it should work. DMX channel 1 to 16 will go to LOR Unit 1, channels 1 to 16, DMX channel 17 will go to LOR Unit 2 channel 1, etc.


Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

Actually the driver needed to use the dongle as an "open DMX" is the d2XX driver. This is the "direct mode" driver. It's included in the FTDI Virtual Com Port (VCP) package. It can be installed on it's own though. This driver doesn't use the device as a com port, it provides a lower level interface between the software and the dongle. It's less limited than the VCP driver is. I forget how to find this driver on the FTDI site, but there's a link on the Enttec Open USB page that points to this driver. I wasn't aware that the LOR driver version didn't use/include this part of the driver.

Thanks for the other process and firmware information though. That's much more detailed than anyone else has provided us. Would you mind if I copy some of that information to the vixenlights website to help future users?


Reply
Page 2 / 3
Share: