TT2 v12 / B-Eye K10 weirdness.

Questions or discussions about the Titan and classic consoles and software.

Moderator: Moderators

Beast
Posts: 47
Joined: 04 Feb 2011, 08:02
Location: Denmark

TT2 v12 / B-Eye K10 weirdness.

Postby Beast » 30 Nov 2019, 19:26

Hi.

We just had 2 shows, with 2 different TT2´s v12, one brand new, delivered with the v12 upgrade and one we have upgraded ourselves.
When patching K10´s,shape mode 35ch, if we patch them first in line from dmx 001, and the number exceeds 5, all sorts of weirdness happens. If able to locate, the clear wont take, eg the fixtures wont turn off. Sometimes locate wont work, and fixtures totally unresponsive. Here is where it gets weird: if we readress the first k10 to another fixture eg a 7th patched k10, all works fine. We experienced this at show, but have recreated the fault back at shop. New show, connected 2 k10s, patched 1, works, patched 2, works....5, at number 6, the weirdness starts again?? Readdress the first k10 and all fine again...We have also a new Quartz, native v12, doesnt have any problems.Have checked DMX out, and it reads as it should. Do we have ghosts in our TT2´s or k10´s..... Any suggestions?? BTW have other fixtures, Sharpy+, on the same line, not affected.

Sincerely yours

BeastDK
User avatar
niclights
The eManual
Posts: 4225
Joined: 24 Sep 2004, 01:06
Location: UK

Re: TT2 v12 / B-Eye K10 weirdness.

Postby niclights » 30 Nov 2019, 19:57

My gut feeling is there is some sort of address mismatch/conflict. I wonder if one of the pixel engine modes is enabled in the first (or possibly all) of the fixtures and addressed somewhere in the same range as the 6th fixture?
Beast
Posts: 47
Joined: 04 Feb 2011, 08:02
Location: Denmark

Re: TT2 v12 / B-Eye K10 weirdness.

Postby Beast » 01 Dec 2019, 20:01

Thanks Nic

Investigated further, including disabling pixelmode on fixtures, The problem persists. Have found out the magic number is 6. Regardless of how many fixtures patched, if we select 6 fixtures, the weirdness occurs. It doesnt happen with any other number up until 10 fixtures??? Have dived into DMX settings, tried stopbit, changing refreshrate, still there. This doesnt happen on our Quartz, with same fixtures.... Only thing that looks different between consoles, is that it looks like the TT2 takes 2 attempts at claiming the Titannode, where Quartz only takes one at startup.(TT2 within a second, running steady after.) Maybe a call to our distributor is warranted.

Sincerely

BeastDK
User avatar
niclights
The eManual
Posts: 4225
Joined: 24 Sep 2004, 01:06
Location: UK

Re: TT2 v12 / B-Eye K10 weirdness.

Postby niclights » 01 Dec 2019, 23:32

This doesn't sound like a DMX settings/hardware thing to me.

A slightly different test idea along the same lines to try and narrow things down:

Patch 1x B-EYE K10 in 35 channel mode to Line 1 001
Connect 1x fixture with matching mode/address
Locate/check responds normally
Assuming it does patch 35x dimmers starting at 176 (equivalent to 6th fixture if all fixtures are 35 channels and patched consecutively without gaps).
Locate the fixture again if you cleared it. Does it still respond normally?
If so select all the dimmers and locate them.
Does anything happen to the fixture now? Can you still control it normally?
User avatar
phb
Posts: 50
Joined: 09 Apr 2019, 14:02
Location: Avolites, Park Royal, London
Contact:

Re: TT2 v12 / B-Eye K10 weirdness.

Postby phb » 02 Dec 2019, 15:06

Hi everyone,

Thanks for reporting this. This sounds very much like it could be a known firmware issue affecting certain DMX output cards (TT2, Arena, Sapphire Touch) in V12.0 which will be resolved in a V12.1 release coming very soon.

The firmware error is triggered by the channel spacing of the fixtures. You should find that changing the offset between the fixture addresses (say introducing a few empty channels between each fixture) might improve the siutation for now.

To verify, you should find that the error is not present if you use network DMX output (sACN, Art-Net); this may be a useful strategy in the short term in advance of the release of V12.1.

Thanks,
Pete Bridgman :: Avolites
Beast
Posts: 47
Joined: 04 Feb 2011, 08:02
Location: Denmark

Re: TT2 v12 / B-Eye K10 weirdness.

Postby Beast » 02 Dec 2019, 18:22

Thanks for confirming, that were not seeing ghosts, will workaround for now.

Thanks everybody.

Sincerely

BeastDK

Who is online

Users browsing this forum: Google [Bot] and 23 guests