Profile Editor Problem

Question

Whilst constructing a profile I entered the Min and max values and the system plugged in the home quite nicely, until I got to the last one. I plugged in the min 117 and 127 for the max but the home clicked to 127. I tried another number like 130 to test things and sure enough the home cell copied that. Thinking to fool the system I added an extra row at the bottom and redid the 127. In this case the home settled on 120. However, deleting the new unwanted row and - woops the home entry jumped back to 127!

Hans.Hinrichsen · Answer

The first and last ranges' home values have special rules applied -- they will be set to the min and max, respectively. You can add an extra range to work around this hard-coded rule, as you observed. 
 Your other question needs a bit more context. If you can post the showfile or a screenshot of the parameters you are using, we might be able to see what's happening. As for how to add a new mode section in the range editor, the mode column can be added by pressing "New Mode" on the far left of the screenshot above.

Hans.Hinrichsen · Answer

Check out the manual page here: https://www.etcconnect.com/webdocs/Controls/EosFamilyOnlineHelp/en-us/Default.htm#Patch/Modes.htm%3FTocPath%3DPatch%7CFixture%2520Editor%7CCreating%2520a%2520New%2520Fixture%7C_____2 
 Towards the bottom of that page is a tutorial on how to create the mode parameter using a simple gobo rotator as the example fixture. 
 To your question more directly, the labels for mode conditions are obtained from the range labels for the mode parameter. This is an entirely separate parameter that is defined (often without a DMX address) and set up before applying it as a condition. If you look in the Intimidator profile, there will be a Color Wheel Mode parameter that has three ranges defined, which are then available as conditions. 
 This is a tad complex, let us know if this makes sense.

Hans.Hinrichsen · Answer

Ah, yes I see. Mode parameters become read-only once you assign them as conditions to other parameters. 
 In this case, you'll want to set the DMX value to 0 (to make it virtual) before applying it to the Index/Speed parameter. It will go back to being editable once you remove it from the Index/Speed parameter as a condition.