Edward Z88

Hi @SKLSKL I would recommend operating the Equinox PIXELpoint Battens in 120-channel mode. This will allow you to patch a "40-cell – 8-bit" RGB Multicell fixture, which can be found under the “Generic” manufacturer in Add Fixtures. If you cannot find these generic multicell fixtures on your console, I would recommend updating your console’s software. If you would like installation instructions, please let me know. Once you have patched this fixture, please watch the video below for more information on controlling multicell fixtures... Please let us know if you have any questions.

Hi @EwenA Thanks very much for grabbing all of those. Please find the zip file attached, including each of the RDM modes for these fixtures... Please extract the files and load each one in, and then plug in a fixture. It should be discovered and patched, and you should then be able to change its mode correctly. I hope this helps. Please let me know if you have any questions. Cameo F2 FC RDM.zip

Hi @EwenA Thank you very much for attaching your show file. This is interesting. These fixtures are reporting an RDM "Device Model ID", that does not match the RDM Device Model ID that is in our library. Therefore, when the console sees these fixtures, it thinks they must be different to the F2 FC fixtures already in the library. This is why you are seeing this behaviour: As the console cannot find a suitable fixture in the library with a matching RDM Device Model ID, the console is then creating a fixture personality automatically, based on the information it can obtain over RDM. These fixtures are only reporting a limited amount of information over RDM. For example, the fixtures are not telling the console what its parameters are doing. The console therefore has no way of knowing which parameter is intensity, or which parameter is red for example. This is why you are seeing this behaviour: Your show file includes the RDM Device Model ID that your fixtures are actually reporting. I have therefore added this RDM information into the F2 FC fixture from the library, and then exported this fixture file, which can be found attached... If you reset the console, load in this fixture file, and then connect your fixtures, the console should then automatically patch this correct fixture from the file, rather than attempt to create a basic fixture file over RDM. The only issue is this file only includes the RDM information for the personality the fixtures were in when you saved your show file. Therefore if you were to change your fixture's mode, it would report RDM information that the console cannot find a match for. The only way around this, would be to send me separate show files for each of the fixture's modes, where you have allowed the console to discover the fixture in each mode. I can then extract the RDM information from the show files for each mode, and then add these into fixture files, which you can then load in to your console. That way, the console will then know about the fixtures, irrespective of which mode they're in, and RigSync will then work seamlessly. As you can see, things get complicated quite quickly with RDM. Ultimately this is all due to these fixtures reporting something different to the information that we have for them. I hope this helps. Please let me know if you have any questions. Edward Cameo F2 FC 7ChRGBCCT RDM.zfix

Hi @Sape & @kgallen I have emailed you both a link to the Rackmaster schematic.

Hi Brett, In this situation I would have used the Output Window Preview function, or the Fixture Levels window, to work out which cue the movers were incorrectly recorded in. Then, I would have gone into that cue, selected the fixtures, tapped HOME, tapped UPDATE, and in the Update Options window disabled "SmartTag", enabled "Track Forwards" and "Remove", and then tapped the playback's GO button. Edward

Hi Brett, Please tap the RECORD button to open the Record Options window. You should see a "SmartTag" button. You may wish to disable SmartTag, so that it has a blue stripe on its button. This will mean the console will only include parameters you have manually adjusted when recording/updating. Unchanged parameters, or parameters currently being controlled by other cues, will not be included when recording/updating. If SmartTag is enabled, the console will decide what does and what doesn't get included. Edward

Hi @MilesBuckley Welcome to the forum. I have not personally had experience with converting MSC to OSC. However, another potential solution - could you contact the SFX6 team, and see whether OSC is on their road-map? You never know - they may be planning on implementing it soon, which would save you the time and effort of figuring out a protocol converter.

Hi @Speedy Welcome to the forum. To record custom Home, Default, or Max Level values, you will need to ensure that “SmartTag” is disabled in the record options. If your custom Max Level values are not currently how you want them, first tap DELETE > HOME > Max Level. Then double tap CLEAR, and set the fixtures you need to your desired maximum level. Then press and hold RECORD, and in the Record Options that open on the touchscreen, ensure SmartTag has a blue stripe, meaning disabled. If it has a red stripe, tap to disable. Then tap the HOME key, and then choose Max Level. Now only the lights you adjusted will be given a Max Level. I hope this helps.

Hi Benjamin, If these errors appear, and the console is switched off and on again, the console will usually reboot into the previously installed version. However as your console has booted into ZerOS 7.14.3, this confirms the software installation completed successfully. The installer must have encountered an issue right at the end whilst it was wrapping things up. The only thing I’d check is going into Setup > Add Fixtures, to check the fixture library is installed. If it is, then you can ignore those errors. Edward

Thank you for emailing the photo of the console's serial number. We will be in touch.

Hi @Niels-Oliver Harfst Welcome to the forum. Thank you for your description of the issue. The first thing to look at would be the internal touchscreen ribbon cable that plugs into the processor. This intermittent behavior could suggest the touchscreen is not connected correctly. Please email a photo of your console's serial number to support@zero88.com, and we can then confirm whether the console is in warranty. If it is out of warranty, we can provide instructions on how to open the console. FLX S24 does not have an external monitor output. Please let us know if you have any questions.

This should be a helpful one to watch... Setup > Clear Options > Clear All will clear all programming, but leave all of your settings and patch. Setup > Clear Options > Reset Desk will clear the patch and most settings, but will leave any network protocols enabled and configured. Often the best option is load the "Setup Only", of a show file where you know the settings are how you'd like them... ZerOS Show Files - ZerOS | Zero 88 Please let me know if you have any questions.

Bonjour, Si vous avez enregistré des positions sur un fader de lecture, vous constaterez peut-être que les appareils se déplacent vers leur position lorsque vous augmentez le fader de lecture. Pour éviter de voir ce mouvement, maintenez SETUP et appuyez sur le bouton de votre lecture pour ouvrir les paramètres de lecture. Ici, définissez la « Fonction du bouton » sur « Go (Snap) », plutôt que sur Flash. Cliquez ensuite sur OK. Maintenant, vous pouvez appuyer sur le bouton de lecture pour préparer les appareils, puis augmenter le fader de lecture pour activer l'intensité. J'espère que ça aide. Hello, If you have recorded positions onto a playback fader, you may find you see the fixtures moving to their position upon raising the playback fader. To avoid seeing this movement, hold SETUP and tap your playback's button, to open the playback's settings. In here, set the "Button Function" to "Go (Snap)", rather than flash. Then click OK. Now, you can tap the playback's button to prepare the fixtures, and then raise the playback's fader to turn on the intensity. I hope this helps.

Hi @delicolor support@zero88.com is still valid and comes through to me and the rest of the team. I’ve been on holiday without access to my emails. I’m back next week.

Hi All, Apologies for the confusion here. Group/palette syntax isn’t available on Solution consoles. Keys such as GROUP purely change the MFKs, and do not bring the function onto the command line. You therefore cannot delete/copy/move multiple Groups or Effects in one operation.

Hi @showguy From memory, ArtNettominator reports itself as an Art-Net controller, not a receiver. In older software versions, FLX S would only send Art-Net to receivers, not other controllers on the network (this is what @kgallen is correctly recalling). Normally you wouldn’t want to send Art-Net DMX data to another console on the network for example. This behaviour was changed in ZerOS 7.14, to avoid the exact confusion you’ve encountered. Therefore, make sure your console is running ZerOS 7.14.3, so Art-Net is sent to “controllers” such as ArtNetominator. Hope this helps.

As @Davidmk says, you cannot have two devices on the network with the same IP address. They must be unique, but on the same subnet in range. So, if the FLX S and laptop both had a subnet of 255.255.255.0, these would be valid IP addresses: FLX S Remote connection: 192.168.1.10 Laptop (running ZerOS Monitor for example): 192.168.1.20 Default gateway/router is not required for simple network configuration like this. More information here… https://www.zero88.com/manuals/zeros/networking/using-the-remote-apps

Bonjour, J'ai répondu à votre email le 24 mai. S'il vous plaît laissez-moi savoir si vous souhaitez que je le renvoie. Hello, I replied to your email on the 24th May. Please let me know if you'd like me to resend it.

Hi @pierotec No it is not - .zfix files support “multicell” fixtures, whereas the Zero 88 Fixture Editor does not. Therefore .zfix files cannot be converted to .ift. .zfix files can be edited in the ZerOS Fixture Creator… https://www.zero88.com/manuals/zeros/patching/add-fixtures/edit-export Hope this helps.

In Phantom ZerOS if you right-click a button on the console's Front Panel, this will press and hold it. Right-click it again to release. Don't forget that most of the console's front panel buttons are mapped to a keyboard shortcut. END will toggle your Fader Function between Channels and Playbacks. V is mapped to VIEW, and F1 is mapped to the button below the first fader. Therefore when your faders are toggled to Playbacks, hold V and tap F1, to view playback 1. Keyboard Shortcuts can be found here... Keyboard Shortcuts | Zero 88 Hope this helps.

No problem - let me know how you get on.

Move On Dark won't actually be able to help you here. This is because Move On Dark only looks at what cues are coming next in this playback. Move On Dark won't be able to prepare fixtures ready for other playbacks that may be triggered. So in this situation, I would manually record the start position for the moving lights in the cue before the "search light" playback is triggered. To do this, go into the cue before the "search light" playback is triggered, select the moving light, and set it to its first position. Ideally if you recorded the first cue of your "search light" playback with a palette, you can apply this same palette, and your fixture will go to the correct position. Once in position, you can then update the cue. By default, "SmartTag" will be enabled in the console's Record Options. With SmartTag enabled, ZerOS will not include data for a fixture, if the fixture is @ 0%. So in this situation, you will need to disable SmartTag, so that the position information can be included with the light @ 0%. To do this, press and hold UPDATE to open the Update Options, and in here ensure that the SmartTag button has a blue stripe, meaning disabled. Then, tap your Master Playback's GO button to update the current cue. Now upon going into the cue before your search light playback is triggered, the mover will prepare, and upon going into the next cue, the search light playback will be triggered with your mover ready in position. Hope this helps.

Yes that is correct. In case it is useful, please see the link below... Example Systems | Zero 88

Thank you for letting me know. I have informed our website team, and have emailed you a download link for the software.

All of the software/fixture library files can be found here... 500 SERIES CONSOLE | Vari-Lite Hope this helps.