Jump to content

DMX Connectivity Articles


Recommended Posts

  • Vectorworks, Inc Employee
  1. Using Sandnet to Connect to Vision 2.3 PC
    INSTALLING SANDNET Step 1: You may have selected to install Sandnet when you
  2. Connecting Vision 2.3 PC using Enttec USB PRO Box
    There are a few things you need to know in order to properly configure the Enttec USB PRO Box for it to work properly with ESP Vi
  3. Enttec Open DMX Ethernet to Vision 2.3 PC & 3.0 MAC
    There are a few things you need to know in order to properly configure the Enttec Open DMX Ethernet Box for it to work properly w
  4. Connect Hog 3/4 to Vision 2.3 PC & Vision 4 MAC via Artnet
    To run Artnet on the Hog 3/4 Console you will need to have a DP 8000 (internal or external). This discussion is valid
  5. Connect Hog3PC/Hog4PC/Console to Vision 2.3/Vision 4/ Vision 2017 PC
    It is important to start by making sure that you have the correct direct connectivity driver, before trying to connect Hog 3 and
  6. Connecting GrandMA Console to Vision 3 MAC
    There are a few things you need to know in order to properly configure the GrandMA Console for it to work properly with ESP Visio
  7. Connect GrandMA onPC/Console to Vision 2.3 PC w/ multi comps
    There are a few things you need to know in order to properly configure the GrandMA console (or OnPC) for it to work with ESP Visi
  8. Connect GrandMA onPC to Vision 2.3 PC w/ same comp
    During the last few years, MA-Net protocol has changed, requiring different drivers for different versions of the onPC software.
  9. Connecting Jands Vista Offline to Vision
    There are a few things you need to know in order to properly configure the Jands Vista offline editor for it to work properly wit
  10. Connecting Compulite VectorPC to Vision 2.3PC via Art-Net
    There are a few things you need to know in order to properly configure the Compulite VectorPC offline editor for it to work prope
  11. Connect Hog 4 PC/Console V3.2+ to Vision 2.3/4 PC
    It is important to start by making sure that you have the correct direct connectivity driver, before trying to
  12. Connect Road Hog to Vision using Artnet
    This discussion is valid for the following configurations: Road Hog Full Boar Console to Vis
  13. Connecting ETC OFFLINE editors to Vision via ARTNET
    There are a few things you need to know in order to properly configure the ETC Offline Editors for it to work properly with ESP V
  14. Connecting Jands Vista Console to Vision
    There are a few things you need to know in order to properly configure the Jands Vista CONSOLE for it to work properly with ESP V
  15. Connecting Jands Vista 2 (Byron) to Vision
    There are a few things you need to know in order to properly configure the Jands Vista offline editor for it to work properly wit
  16. Hog3PC to Vision 2.3 PC SAME COMPUTER
    It is important to start by making sure that you have the correct direct connectivity driver, before trying to connect Hog 3 and
  17. Connecting grandMA3 to Vision 2021
    Vision 2021 SP2.1 and later uses MA viz-key technology to connect to the grandMA3 and join an MA-Net3 session.

Link to comment
  • Vectorworks, Inc Employee
34 minutes ago, GoodwinLtg said:

I am trying to connect vision 17 to Hog 4 PC to start programming a show.  Both are on the same computer running windows 10.  Can anyone guide me on the correct settings I need to get the programs talking to each other?

 

Thanks

 

This article, listed above:

http://kbase.vectorworks.net/questions/1404/Connect+Hog3PC{47}Hog4PC{47}Console+to+Vision+2.3{47}Vision+4+PC

Link to comment
  • 1 year later...
  • Vectorworks, Inc Employee

Hey Mauro, I will write a new one, it looks like when we migrated to the new forums that article got lost somewhere. If you have an MA2 (or dot2) console, just plug it in, send artnet or sACN and change dmx provider in Vision to artnet or scan, that's it.

 

If you are using ma2onPC, and are in a windows environment you can use MA-Net (ACT hasn't made a driver for mac). Download and install the MA driver from: http://www.actlighting.com/MA/software/utility/ESP%20Vision/gMA-ESPVision[3.100][6.800]-v1.220.zip Then go to Control Panel>Sort by icons> ESP – grandma driver. Change it to ma-net 2, and 127.0.0.1 if using ma on the same computer as vision, or the other option (it will be your computer’s Ip address) if sending across a network.

 

Luckily the article that was lost is also the easiest one to explain. Give us a shout at tech@vectorworks.net if you have any trouble!

Link to comment

Hey Edward, thanks for answering.

 

I'm doing step by step an Arnet connection between Vision (running in Mac) and grandMA2 Light. The problem is that when I plug it in the second Arnet slot on my console, Vision crashes and quits instantly. Doesn't happen with the first slot (which is MA-net)

This is happening with the SP2 version. Do I've to delete any kind of cache folder? Maybe is that!

Link to comment
  • Vectorworks, Inc Employee

Ah, that's actually great news! What happened is, as soon as you made the connection, you must have been telling vision to turn on a bunch of lights, so it did it all at once. Vision will crash to desktop to save your GPU. Unlike video games, or something we can predict GPU load, we don't have any idea how many lights the user will turn on at once, so to save the GPU from overheating and well...melting, we crash out. 

 

Bring your lights to 0 and bring them up one at a time, and see if they respond. If you are crashing when just bringing up a normal amount of lights, you're probably running into a GPU limitation - our minimum is a GTX 580 or equivalent benchmark. More info here: 

 

Also, make sure you're not sending over any needlessly complex geometry. Vision is essentially running something between a fast and final quality renderworks 60 times per second, so avoid things like truss symbols (which model nuts and bolts for some reason), large amounts of soft goods (smooth = more polygons = more GPU load), and stage tool stages with the support posts rendered (you can't see them anyway). All of this is subjective, and I just trim what I need to depending on the show and my hardware. 

 

Link to comment
  • 2 months later...
  • Vectorworks, Inc Employee

Hey Simon!

 

Chances are likely that your patch is off. Make sure you adjust the edit Vision data mapping in Vectorworks via: File>Document Settings>Spotlight Preferences>Edit Vision Data Mapping. Vision uses a two-part addressing system using "Universe" and "Channel" as the two parts change the drop downs on the right to align with the Object info palette fields you prefer - i.e. Universe and Address, or Universe and Dimmer.

 

Sorry for the delay, I was out last week moving! If that doesn't fix it for you or you have any other questions, shoot us an email over at tech@vectorworks.net and we'd be happy to help.

Link to comment
  • 1 year later...

I can't figure out how to connect Vista 3 to Vision 2019 on a Mac computer running macOS Mojave. I have followed the instructions above to connect Vista 2 to Vision. I am assuming that not much has changed. However, Vision does not seem to be receiving the Art-Net signal. Any help would be appreciated. 🙂

 

Thanks

Link to comment
  • 6 months later...

Hey everyone,

 

Has the console connectivity instructions for ETC Eos been updated? That link is now three years out of date, and I am having some issues connecting Eos Offline (with Previz) to Vision (both are running on the same computer). When I bring up channel one on the console, channels 1-7 (all identical fixtures) come up as if they were patched together. Same thing happens on sACN. And the Vision DMX Viewer is showing no output even though those lights are turning on and responding (albeit as one fixture as opposed to 7).

 

I should also note that if I try and bring up those fixtures by address, the problem persists. It's as if they were all addressed the same, even though they are patched correctly in both VW/Vision and in the console.

 

Thanks

Link to comment
  • 3 weeks later...
  • 6 months later...

Hello,

 

Trying to connect Vision 2020 sp5 with ma2 onPC (same computer), using the grandma ESP Vision driver. Every time i try and change the Vision DMX provider to grandma and click ok i get an error saying "cannot open HASP driver.

Tryed to update Vision as well as reinstalled Vision with getting the same error.

 

Win10 64-bit

 

Thank you.

Dave Carr

Link to comment
  • 2 months later...

Hi there - Im running an MBP with vision & Chamsys onPC (the same MBP) - I can only get vision to connect to the virtual desk when I have a valid IP (ie, Im on a network). I cannot get it to connect on a 127.0.0.1 address. Im doing a lot of programming sat in fields (!) so this is an issue...how do I get Vision to work on a 127.0.0.1 (loopback) address please?

 

Many thanks

 

(Vision 2021)

 

 

Edited by anthall5
added version
Link to comment
  • Vectorworks, Inc Employee

We have seen the same problem before on the ETC offline software.

We are not quite sure why it happens but it appears that some software sees there is not valid network address and then doesn't broadcast the data over the network or it's internal communication protocol requires multiple valid IP addresses.

The easiest solution we have found is to connect it to a router that will give it an IP address. It doesn't need to be connected to the intranet, just a router or other device that will be able to distribute IP addresses.

Vision listens to all interfaces for for data, so if it's being broadcast Vision should see it.

Link to comment
  • 11 months later...

Hello,

 

Trying to connect Vision 2022 with ma2 onPC (same computer), using the grandma ESP Vision driver. When I try and change the Vision DMX provider to grandma and click ok i get an error saying "cannot open HASP driver.

Tryed to update Vision as well as reinstalled Vision with getting the same error.

 

Win10 64-bit

 

Thank you.

DaeHyun

Link to comment
  • 4 weeks later...

All,

 

I have upgraded from Vision 2020 to Vision 2022 and have tried to open my .v3s file that worked in Vision 2020. I get a file migrator popup that asks to convert it to a .vsn file and open. However, when it loads, none of the fixtures respond to DMX commands. I have confirmed that the DMX provider is the same as previous (sACN), and that Vision is seeing the DMX signals on the DMX Viewer. All of the fixtures appear to have retained their universe and channel assignments as well.

 

I have also tried exporting an entirely new file from Vectorworks 2022 to Vision, but get the same results. I can see the DMX signals coming in, but none of the lights respond.

 

Any suggestions for what I can try next?

 

I am very new to Vectorworks and Vision, so any help is appreciated.

 

Thanks.

Link to comment

Similar question to those above:

 

I'm trying to connect an ma3 compact (running mode 2) into vision 2022. Vision 2022 is the version provided with the spotlight service select subscription.

Running sACN or Artnet seems to give no results/no output and nothing in the dmx Viewer.

 

Does the ma3 still require a viz-key despite being in mode 2?

Link to comment
  • Vectorworks, Inc Employee

If you are using an ma3 compact is should output native sACN or Artnet to Vision. 
Since you are using the Vision license that came with Spotlight Service select you will be limited to using the first 2 universes.
The full paid version of Vision allows you to access unlimited universes.
Make sure you are using Vision 2022 SP3, we fixed an issue where Vision may not see the data from all network interfaces.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...