Attribute Library's for strand 300

[sus.lighting]

Hi

 

I was programming some scanners (I know not the best) into a Strand 300 consol the other day, and since the light wasnt in the fixture library I had to write it into the syntax. BUT as I wrote in what attributes I wanted I (I wanted to use it as a moving head) and patched it to a channel I came across a problem. The attribute channels worked BUT they were working different attributes on the light

 

e.g

 

attribute 3 and 4 were saying pan and tilt, yet when I used the trackball the light was changing colour and strobe speed.

 

This is bizzare and thought the light was broken then patched it to 6normal channels on the desk insted of using attributes and it worked

 

(obviously the fixture library is different to that of the light as all the attributes are mixed up but are still working.)

 

I am using the original fixture library from the strand 300?

 

What should I do? Download a newer fixture library? or is my programming wrong?

 

And if, where would you get a newer fixture library??

 

Thanks so much

 

sori for the long post!

[gareth]

If the light isn't in the fixture library, downloading a new one (or any one!) won't make a difference. You have to edit the FIXTURE.LIB file on the console and edit it to teach the desk how to talk to your scanners. The notes at the beginning of the file (access it either by dropping out into DOS or using the notes display on the console) are fairly clear in telling you how to go about creating a new fixture definition.

[Jeremy MLS]

To me (who did much the same thing on a 520i last week) it sounds like when you put in the attributes you possibly put them in strand attribute number order. Instead the attributes need to be put in the channel order of the scanner. ;)

[Germaine]

Do you have any other intelligent lights on the gig/is there a possibility that someone has been messing about with the desk. you can change the assosciation of what the trackball does to be anything you like i.e. pan on ball = strobe and tilt = colour etc etc. This is done in the ATC page is I remember correctly. I'd try the previous suggetions first but failing that it could be the above mentioned issue.

 

Germaine

[gareth]

This is in danger of over-complicating itself with lots of speculative advice ...

 

Why not tell us exactly what the fixtures are, and if you have it to hand the DMX control protocol for the units? Then it'll be an easy matter to point you in the right direction for creating an appropriate fixture definition.

[GridGirl]

To me (who did much the same thing on a 520i last week) it sounds like when you put in the attributes you possibly put them in strand attribute number order. Instead the attributes need to be put in the channel order of the scanner. ;)

 

Sounds like this to me as well - I've done it before, was trying to be orderly and so put in the attribute numbers in Strand numerical order - ended up with gobo and colour wheels on the trackball, and the reset channel on the wheel! Get hold of the manual for your scanners, and make sure the fixture attributes are entered in the order the channels appear on the scanner and not numerical order according to how Strand number them.

[sus.lighting]

To me (who did much the same thing on a 520i last week) it sounds like when you put in the attributes you possibly put them in strand attribute number order. Instead the attributes need to be put in the channel order of the scanner. :)

 

Sounds like this to me as well - I've done it before, was trying to be orderly and so put in the attribute numbers in Strand numerical order - ended up with gobo and colour wheels on the trackball, and the reset channel on the wheel! Get hold of the manual for your scanners, and make sure the fixture attributes are entered in the order the channels appear on the scanner and not numerical order according to how Strand number them.

 

 

Thanks for that advice. Im setting up for the show as we speak.Ill try entering them in the order the scanner works. This will be awesome as I need to program some groups.

 

A concurrent post has been automatically merged from this point on.

 

If the light isn't in the fixture library, downloading a new one (or any one!) won't make a difference. You have to edit the FIXTURE.LIB file on the console and edit it to teach the desk how to talk to your scanners. The notes at the beginning of the file (access it either by dropping out into DOS or using the notes display on the console) are fairly clear in telling you how to go about creating a new fixture definition.

 

 

Hi, I have written the scanner into the fixture library so the attributes work. Its just they are in wrong order, as in pan on desk moves colour.

[Ynot]

Gareth suggested...

Why not tell us exactly what the fixtures are, and if you have it to hand the DMX control protocol for the units? Then it'll be an easy matter to point you in the right direction for creating an appropriate fixture definition.

 

.........................................

[gareth]

Hi, I have written the scanner into the fixture library so the attributes work. Its just they are in wrong order, as in pan on desk moves colour.

With respect, if they all appear in the wrong order (i.e. on the wrong encoders) then they don't really "work", do they? :)

 

The offer stands - if you want to post the fixture's DMX protocol here, I'm sure I or one of the other experienced Strand programmers hanging around on the BR would be happy to give you the right attribute numbers in the right order to edit into your LIB file. On the other hand, if you've worked it out for yourself (it's not difficult - just put intensity, pan and tilt as the first three and you can't go far wrong), then you're done and dusted.

[sus.lighting]

Thanks very much for the advice. Yeah I ad programmed the atrributes in the wrong order. Sorted now thanks.

 

PS sorry for the late reply.