Vixen 3 Output Modu...
 
Notifications
Clear all

Vixen 3 Output Module Programming Tutorial

13 Posts
7 Users
0 Reactions
10.2 K Views
Posts: 2215
Topic starter
(@ctmal)
Famed Member
Joined: 19 years ago

I don't have an answer for you right now but I do see that it is not working correctly when you set the data class as static. I'll take a look as soon as I have a chance.

I do think that you really don't want the static class for your module though. In general(as I see it) you would want to set up a controller for each RS485 run. So, for example, if you have 2 8 port physical controllers on one com port you would set up a Vixen controller for 16 channels. Otherwise you would have to program another output module if you wanted to set up a run on a 2nd com port.


Reply
Posts: 3650
(@jhinkle)
Famed Member
Joined: 15 years ago

Yes and No.

I'm not using one controller per RS485 run. I will have multiple controllers all hanging onto one RS485 bus. Each controller will has an ID which will be part of the message packet (message will be ignored by all controllers not having that ID).

If I have 6 controllers on one COM bus - I don't want to open the same COM port six times - that is why I wanted static.

Only the first call to START would open the COM port and the last STOP would close it.

Vixen may not let me do this as it believes there is only a one to one relationship with COM port and Controller.

What is needed is for Vixen to have another level of hierarchy, One that defines the physical path of communication, COM port, pipe, etc and then allow controllers to be attached to the path.

In my case - I would open a single RS485 communication channel, attach to that path - say - 6 different controllers - each controller controlling 16 to 24 physical lighting channels.

If the above was made possible - now two type of setup Dialogs would need to be created - first one which defines the communication path (COM port) - THAT one would be static, and Controller Setup Dialogs - those would be local and just acquire the unique Controller ID assigned.

I would probably save a list of available controller IDs in the static communication path data block.

That is what I was attempting to do - may be it can be added since it appears to fall right into the type of design Vixen 3 is implementing.

Using the way Vixen 3 is designed to day, I will have to tell Vixen I have a controller that supports - say - 96 channels. In my data block, I would add additional structure that would associate those 96 channels with logical controller IDs.

During the OUTPUT phase, I would parse off the data for each of the logical controllers, build separate message packets and then do multiple Com port writes.

Its possible using today's Vixen 3 design - just a bit clumsy.

Merry Christmas.


Reply
Posts: 448
(@bobkeyes)
Honorable Member
Joined: 17 years ago

Chris,
Thanks for the great tutorial. I'm just starting with it. However, when I open the Vixen testbed I do not have the Administration tab like you show. All I can bring up is the DisplayPreview. What am I doing wrong?? I've reloaded 3.0 to no avail.


Reply
Posts: 2215
Topic starter
(@ctmal)
Famed Member
Joined: 19 years ago
bobkeyes wrote:Chris,
Thanks for the great tutorial. I'm just starting with it. However, when I open the Vixen testbed I do not have the Administration tab like you show. All I can bring up is the DisplayPreview. What am I doing wrong?? I've reloaded 3.0 to no avail.

Check out the video about testBed changes(the one after part 1). I think that is your issue. When I started the tutorials Vixen 3 beta was not out yet so I was using an older version of the tested. Let me know if that video solves your problem.


Reply
Posts: 2215
Topic starter
(@ctmal)
Famed Member
Joined: 19 years ago
JHinkle wrote:Yes and No.

I'm not using one controller per RS485 run. I will have multiple controllers all hanging onto one RS485 bus. Each controller will has an ID which will be part of the message packet (message will be ignored by all controllers not having that ID).

If I have 6 controllers on one COM bus - I don't want to open the same COM port six times - that is why I wanted static.

Only the first call to START would open the COM port and the last STOP would close it.

Vixen may not let me do this as it believes there is only a one to one relationship with COM port and Controller.

What is needed is for Vixen to have another level of hierarchy, One that defines the physical path of communication, COM port, pipe, etc and then allow controllers to be attached to the path.

In my case - I would open a single RS485 communication channel, attach to that path - say - 6 different controllers - each controller controlling 16 to 24 physical lighting channels.

If the above was made possible - now two type of setup Dialogs would need to be created - first one which defines the communication path (COM port) - THAT one would be static, and Controller Setup Dialogs - those would be local and just acquire the unique Controller ID assigned.

I would probably save a list of available controller IDs in the static communication path data block.

That is what I was attempting to do - may be it can be added since it appears to fall right into the type of design Vixen 3 is implementing.

Using the way Vixen 3 is designed to day, I will have to tell Vixen I have a controller that supports - say - 96 channels. In my data block, I would add additional structure that would associate those 96 channels with logical controller IDs.

During the OUTPUT phase, I would parse off the data for each of the logical controllers, build separate message packets and then do multiple Com port writes.

Its possible using today's Vixen 3 design - just a bit clumsy.

Merry Christmas.

I just read in another thread that linking the controllers just as you described is a function in Vixen 3.0 but the UI interface is not in the beta version. Knowing this you can probably go ahead and program your module but you'd need to either only use 1 controller or assign all the channels as 1 controller.
I still haven't had a chance to work out the static data issue but I will.


Reply
Page 2 / 3
Share: