Any Pros can help with Vectorworks Showcase and ETC EOS Software

[Tai Zi Feng]

I am trying to use Vectorworks showcase as a visualizer instead of ETC Eos Augmented.

I have two laptop setup, with an unmanned switch establishing the connection, Both laptop can ping each other.

Laptop A have ETC EOS Software running (with dongle plugged in as well), and Laptop B have the vectorworks file.

 

1) Tried both Art-Net & sACN in "Showcase Preference" , neither respond to the ETC console.

 

2)The fixture in vectorworks is DMX patch reflecting the same universe and address as in the ETC Console as well.

 

3)Tried disabling Art-Net and use sACN only, tried the other way.

 

4) Tried restarting vectorworks multiple times

 

Anyone know what I could still be doing wrong/missing here?

 

How does Vectorworks showcase work? does it detect Channel ID from Artnet/sACN protocol over network? or does it detect addresses?

 

[Tai Zi Feng]

I have managed to got it to work somewhat.... 

Saw on Facebook that you have to "turn on" the light fixture first before starting showcase.

which then established the link between the console and vectorworks.

However, my channel 1 is controlling more than a bunch of lights on showcase. 

Double checked my DMX Patch, patch on etc and also GTDF is just ETC Lustr S2 

 

Anyone encountered similar issues?

 

[klinzey]

Can you post a sample file?
I haven't seen multiple lights turn on unless they have the same address.
Make sure your modes are the same. The Lustr has a bunch of different modes don't agree it would be very easy to turn on several lights at once.

The only thing I have found is that the ETC software does not like just being connected to a simple switch and manual IP addresses assigned to the machines on the network.
Most of the time I'm had to use a router with DHCP enabled to allow IP address to be automatically assigned.

[Tai Zi Feng]

I attached a video I took. 

When I turn on channel 1, a couple of lights turn on as well. Such as sola frame , Robe T1 profiles as we'll.

Then in turn, I could not control those moving lights which channel are 51-58 , 61-68 respectively.

[JBenghiat]

I recommend installing sACNView: https://sacnview.org That helps deduce whether the problem is on the sending, receiving, or networking end (you can run on both the Nomad and VW machines).

 

You seem to be past this point, but in patch, make sure that channels are set to use sACN (or ArtNet, if you're going that route), and that sACN output is enabled.

 

I've never had issues with self-assigned ip's (that's how most lighting networks are set up), as long as they don't conflict. You should make sure that you are outputting the correct interface, which needs to be connected when you launch Nomad. 

 

This sounds like a patch issue, though. If you can't figure it out, sending screen shots of both Eos's patch screen and the OIP for the three lights that come on together might help.