Fixture Request Martin RoboScan 518 Mode 3

What version are you running? The current profile looks like it handles the CTC filter about as well as can be expected. It's got the snap parameter in the ML and it can be dialed in with the encoder or by using {Beam FX Select}[At] DMX #. (DMX is posted to the command line using //)

I can't speak to the Lamp Off behaviour but I know the Roboscan 918 uses a similar strategy of distinct values on 2 channels for 5 seconds and it works for that fixture. I'm a bit surprised it is not working for the 518. 

Adding to sk8rs_dad, you can also press Shift while moving the Beam Fx Select encoder, which will allow you to move along the range of the CTC wheel. The DMX command will let you get to the exact value as well.

The lamp controls look correct for the fixture -- for lamp off, it sets the strobe channel to DMX 254, color to DMX 121 (UV Pass), and the effects wheel to DMX 95 all together for 5 seconds. If that isn't working, I'd recommend trying to set the time for that command a bit longer. It runs for 5 seconds per the manual, but try setting it to 7 or 8 seconds.

To adjust this, you'll need to make a copy of the fixture, adjust the lamp controls, and repatch it to the existing channel. The library fixtures are more or less "locked" - you can't edit them, but making a copy will bring all of the attributes over, allowing you to change items.

• Go to patch and press the {Fixtures} softkey. (Fixtures won't be available unless you have a clear command line).
• Find the Roboscan 518 in the list. Press the {Copy} button on screen.
• Select the Roboscan 518 (Copy) fixture and press the {Edit} button on screen.
• Press the {Lamp Controls} softkey, and select the {Lamp Off} command, and press the {Steps} button on screen
• Adjust the time from 5 seconds to 8 seconds
• Patch this fixture to the target channel and try the lamp control out again.

Thanks!

Hans

Using the latest version of the fixture library with the newest version of the software. Just updated everything yesterday.

I have tried all of the above suggestions, but I still am unable to access the CTC Filter. If I try and use just the encoder, you can briefly see the filter as it goes right on by. If I try to use Shift while moving the Beam Fx Select encoder the same thing happens. If I try the command {Beam Fx Select} [At] //# the CTC filter still will not set.

No matter what we try, we can't get the fixture to lamp off properly.

In ML Controls, there is no Snap button for Beam Fx Select, and there is no button for the CTC Filter. There is a button for both frost and prism.

Long story short, we can't get the fixture to function as it should using the profile that currently exists. That is why we have asked for a new one.

There's something else going on here. The control is definitely there for me and the output is varying as I twiddle the encoders.

I'll look at this today in version 2.1.2 to test the output. sk8rs_dad, are you in 2.1.2 or the 2.2.0 beta?

Thanks!

Hans

The picture's from the client on 2.2 but the console is on 2.1.2.

This is what I am seeing on my ML controls:

This is from the actual Ion screen, and I just updated the patch to include the default profile. We were using altered copies on the others from a very older fixture library.

Hi Charles,

Can you post a showfile where you're seeing this issue where the tile doesn't appear? I patched a Roboscan 518 M3 in version 2.1.2 and I'm seeing the CTC option like sk8rs_dad and can adjust it within the range. I'll continue to look at output/lamp controls - I've only had a chance to patch the fixture and check it out in ML controls. 

Thanks!

Hans

When I get out of the show today I will send you an updated show file that includes this behaviour.

Thanks!

The lamp controls rely on a value in the CTC range that is misbehaving. I suspect that resolving the issue with the CTC range will resolve the lamp control issue too. I had a look at the detailed profile for the lamp controls and they adhere to the manual, using DMX values right in the middle of the documented ranges.

The lamp controls rely on a value in the CTC range that is misbehaving. I suspect that resolving the issue with the CTC range will resolve the lamp control issue too. I had a look at the detailed profile for the lamp controls and they adhere to the manual, using DMX values right in the middle of the documented ranges.