|
|
Post by strouse on Jun 27, 2017 11:07:10 GMT -5
I feel like dealing with dmx snakes and home runs could be made easier with some sort of circuit name+circuit number type fields. Basically "these lights are on this line" type of thing with the ability to link it to a universe in the maintenance window. This would streamline the process of making labels for snakes and homeruns. Included in this wish is the ability to generate spare circuits.
Any thoughts?
|
|
|
|
Post by litedoctor on Jun 27, 2017 12:14:30 GMT -5
Interesting idea. It would tie in nicely with something I've been thinking about.
I'd love to see a network/control page. Someplace in LW to lay out Console, NSPs, RVIs and the like with IP numbers, Universes, home runs, etc.
|
|
|
|
Post by strouse on Jun 27, 2017 17:48:30 GMT -5
LiteDoctor,
In your vision does this work somewhat like dimmers? This data line goes to this port in this node (dimmer rack)? all linkable?
|
|
|
|
Post by litedoctor on Jun 27, 2017 18:11:24 GMT -5
Something like that, yes. What I have in my head might be overkill for the scope of LW, or might even be a whole other program. Picture this:
You start with the console. Choose the profile for GrandMA2 and LW will know how many network ports, monitors, SMPTE, Midi, etc. Each one is a field which can later be labeled. (Network Port A, sACN, runs to Port 3 in Switch 1, whatever you need)
Now add NSPs, (or Net3 Nodes, or Pathport Octos....) give it an IP and map out which Universes go where. (Which dovetails in with your idea)
Need an RVI? Backup Console?
Right now I end up laying all this out with a flowchart and spreadsheet combo. How great would it be to have it all in one place?
|
|
|
|
Post by strouse on Sept 14, 2018 20:26:48 GMT -5
Again, i'd really like this feature right now.
|
|
|
|
Post by danhar on Aug 23, 2019 9:06:03 GMT -5
Hello,
The above would be great, but as a start bieng able to make a "Data circuit name" field would help for quite a few things.
Main reason for this as strouse stated is to document where a light is fed from (currently power wise its done, but not for data)
following on from this then the below could be possible:
- To be able to list out ALL cables required for a job, currently no way to caputure Data cables in looms, so they are not countable.
- To be able to create systems for data like the power cables are into racks (control racks / splitters nodes etc) this then links into litedoctor's later bigger wishes.
- To be able to create a loom by adding a "loom" field to "Data circuit name" maintainance lists. Then a loom schedule can be exported to show what cables are needed for looming.
|
|
