Titan One Mobile Capture Trouble

[himswoka]

Hey all! I'm a brand new Avolites Titan user. I'm currently set up in my office with a Titan Mobile One and I am having trouble getting it to interface with Capture (the desktop version) I have the Mobile One on a mobile machine and am connected via Wireless to the network. (All the IP info is good) On my desktop computer I have Capture open with fixtures and the Streaming ACN from the Titan Mobile shows up as a potential Universe (And even changes names if I rename it on the Titan, so I know it is a live connection)

The problem is.. I can't get any of the fixtures to turn on. It seems that everything is patched fine and I have confirmed that the output is not operating in blind. Anybody have any ideas..? And help would be greatly appreciated!

[himswoka]

I should add that I have no problem getting fixtures to operate with the Titan Mobile 1 emulator that is also installed on the same desktop as Capture.. patched the same way.

[niclights]

I can't really think of any reason for a difference between the two unless the DMX settings are different or somehow a firewall is blocking one but not the other.

In Capture Universes tab does it see an external universe? If so, if you double-click a relevant line here to open the channel input view does it reflect the channel values in Titan?

[himswoka]

Right! That's kind of the crazy thing. The Universe shows up.. but the channel values are not correctly reflected I don't think. (They show up in the 1600 range when the fixtures are actually patched as channels 1 through 20 or so.) I even saved the show file from the Windows 7 Machine and opened the same file on the Windows 10 just to make sure everything was the same.

[himswoka]

Confirming Network Configuration.

Router: 192.168.1.1
Subnet Mask: 255.255.255.0

Windows 10 Machine (Running Titan Mobile 1) via Wireless Connection
IP Address: 192.168.1.61 (Obtained via DHCP)
Subnet Mask: 255.255.255.0
IPV4 Default Gateway: 192.168.1.1

Windows 7 Machine (Running Capture) Connected to switch port on Wireless Router
IP Address: 192.168.1.53 (Obtained via DHCP)
Subnet Mask: 255.255.255.0
IPV4 Default Gateway: 192.168.1.1



I have confirmed that both machines are exempting Capture and Console Software from the firewall.

Also, the patch does show up correctly in Capture when connected with 1 universe of sACN to Titan Mobile.. just no fixture control. If I pop open the Windows 7 Desktop (Also running Capture) then I am able to get activity no problem through both the sACN and the Bootstrap.

[niclights]

If, by 'channel values ... 1600' you mean the ones in the 'Console Patch' window ('View fixture patch...') I wouldn't take too much notice. I'm not sure why it's like that but if you add fixtures and address them manually they should respond as normal.

What happens if assign Art-Net nodes instead of sACN?

[himswoka]

The same thing. I don't have my Network set up on an ArtNet friendly structure though I don't believe. Everything shows up though. No fixtjre control.

[Gregory]

Can you post a screenshot of the 'channel values ... 1600' screen that you mentioned? Also a screenshot of Patch View and the DMX Settings window (showing the Streaming ACN Module Properties by clicking on the cog in the left hand column) might also be helpful.

[himswoka]

IT'S ALIVE. Thanks to both of you for your help. It turns out that when I was in the DMX settings window.. I clicked on the little cog on the section on the right for sACN universe 1 and didn't see a whole lot of options. I assumed that the sACN cog on the left would yield the same results but I was wrong! The sACN module was set to broadcast over the wrong network adapter. (I'm still curious how I was getting Capture to see the Universe though! Possibly because network information was correct everywhere else, it just wasn't allowing ACN data values to be streamed)

Thanks!