Elation Vision scan 575 Profile Issue on AZURE???

[ChrisLIT]

Hello... 1st post..

Ok now to the problem.

So this is the second time I've tried to patch some Vision 575's to the azure.
This time I am screwed cause the shows tomorrow, and for now there hooked to a amdj operator. yuk!!!!

I researched "avo's" personality site and it says
Elation vision scan 575
Disk#7
file name : ELVIS575.R20
Name on desk : ELSpot575

so I tired it. and what do you know. no worky

the dimmer channel on the console does some sort of macro function.
and pan is a non completely functional Pan.
nothing else works.

now, I have data, they home when connected, and the Lcd indicates dmx.
also, i have checked the fixture settings,mode etc to make sure they are ready to run via dmx.

Im not a noob. I've checked everything i could think of.

so... Im forced to come ask for help, and if anyone has had problems with this particular fixtures profile.

[niclights]

Comparing to online manual it does look completely wrong:
http://www.elationlighting.com/pdffiles ... Traits.pdf
In fact the only channel correctly mapped was Iris! I wonder if Elation have changed their DMX channels?

A quick unchecked correction:

Code: Select all

3    1   s   2   100   1N   E   1   "Pan"          128   -1   -1
0    0   L   1   100   1N   E   1   "Pan Low"      128   -1   -1
3   61   s   4   100   1N   F   1   "Tilt"         128   -1   -1
0    0   L   3   100   1N   F   1   "Tilt Low"     128   -1   -1
8    1   I   15  100   1N   0   1   "Speed P/T"      0    0    0
8   61   I   16  100   1N   0   1   "Control"      255    0    0
4    1   I   5   100   1N   A   1   "Colour1"        0    0    0
6    1   I   8   100   1N   I   1   "Gobo1"          0    0    0
4   61   I   14  100   1N   N   1   "Frost"          0    0    0
9    1   L   9   100   1N   P   1   "Prism"          0    0    0
6   61   I   6   100   1N   J   1   "Gobo2_Spin"     0    0    0
7    1   I   7   100   1N   K   1   "Gobo_Rot"       0    0    0
2    1   L   13  100   1N   G   1   "Iris"           0   -1   -1
5   61   L   10  100   1N   L   1   "Focus"        128   -1   -1
2   61   L   11  100   1N   O   1   "Shutter"       48    0    0
1    1   H   12  100   1N   H   1   "Dimmer"       255  255  255

I have not provided edits for PFTABLE or MACRO as the colour order and gobo number also do not tally. Currently they will be assigned to the wrong attribute. I guessed it was unlikely the Macro values would be correct either!

Something strange has happened here.

/edit: posted bug report

[ChrisLIT]

Sweet thanks for the help.


So is the code you listed a the correct code minus the stuff you mentioned.
I'm not to familiar with computer code.

I got a little lost in your reply in the end of the message.

I downloaded that R20 builder from the other thread and tried to build my own.It was very easy to understand.

I will find out if it works when i go to the set later today.

It seems like i built a new one correctly the r20 build process went smoothly.

[niclights]

To answer your questions, the code I edited is the part that defines which attributes go to which DMX channels and which buttons they are assigned to on the desk.

The .r20 files are not so complicated. You can open in notepad and edit directly. Most files have explanations of each section to help you. If you had not used the builder software you could have simply copy/pasted the code above to replace the existing part in the file.

The PFTABLE section defines preset focuses. These are used either for 'automatically create preset focusses' when patching or for tables available in the console - usually colour attribute.

The MACRO section defines any macros available via ML Menu/Macro (not sure if this is the same in the Azure). These are functions where a fixture requires a particular channel to be set to certain values for specific amounts of time with no other values in between, commonly for lamp on/off/reset etc. The definition will detail the attribute, timings and values.

There are also range tables. These are used for the 'intelligent' display of data above the wheel (in the Pearl). For example gobo names instead of just % numbers.

[ChrisLIT]

Sweet. thanks.

i kinda knew what you just told aboout the script
by just sitting there and staring at it trying to figure it out.


But It all make sense now. thanks for explaining it to me

Now one last question.

How do i open disk 7 to get to the File for the scanners to edit it?.

It only seems to want to burn it to floppy
and there are not any "Open with" options when i right click on the file.

I just tried to open it in notepad and got all crazy garble text.

[niclights]

Just run the apsdisk exe file without a floppy disk in the drive and another window will open with an 'unzip to folder' field. You can click the [browse..] button to select where you want it.

Then you can right-click the relevant .r20 file and use open with...

[ChrisLIT]

Ok.

so i edited (cut & pasted) the Vis575 file on disk 7
I also noticed the Pan/tilt degrees were off so i fixed those as well.
saved it and burned it to a disk.



So now i have two new and improved profiles..
hopefully one works/

thanks Niclights for all your help. you rock.!!!!



Ill let ya know the results.