Davidmk

Nor me. In fact I don't think I dare to dream. ☹️

@kgallen Correct, although I suspect the processor board isn't custom, more likely an off the shelf unit that has become uneconomical because other customers have moved on. I figured that... The problem with producing FLX is the availability of the processor/screen combination. ZerOS has been shown to run on Rasberry Pi, not only that but an old model of RP. Newer RPs have more muscle than old ones. So it is possible, probable even, that a RP 5 has the capability to run as an FLX The problem with that is interfacing the hardware bits the FLX has and the S doesn't. I speculate that the various peripheral boards inside an FLX actually talk to the processor via USB. We know the fader wing does so its possible the internal faders do as well plus it is the sort of interface an off the shelf board might use. Even back in the day, Zero 88 wouldn't want to develop a whole new protocol so, even if it isn't USB, it will be something for which an RP hat might already be available. So, assuming the hardware interfaces are USB, or something that someone in the community could sort out with widely available circuitry (OK, that might not be possible), then, with access to the source code, you have to identify how it 'knows' what hardware it is running on and all the places it uses that information. For that, you need a software specialist. I'm rusty, and it would probably be in a language I'm not familiar with but I reckon I could give that a go and I'd bet I'm not alone. I don't know the background of everyone in this and the Facebook forums but, given that about half the LX techs I know have backgrounds in IT and/or telecommunications the expertise is out there. The flaw in this is that Vari-Lite have paid for the ZerOS intellectual property and are highly unlikely to give it away for free. Plus they wouldn't want all the support calls which would result from the unofficial versions that would spring up as a result. The other thing is why has there been no announcement of a Pi based FLX S+ to replace the full FLX? Is it that it is much harder than I have assumed or that they bought Zero 88 for the other products?

I doubt it will happen but, if they did, the first thing to look at is whether an FLX could run with a Raspberry Pi processor board and touch screen. Vary-Lite could do this themselves of course.

Sorry about that. Fixed, I think, for posterity.

Just noticed this under Missing Fixtures in the manual Didn't see any news about that. Thought I should bring it to the everyone's attention.

Too complicated to explain here but Search & Filtering and Fixture Creator should help. There is also the Windows Fixture Editor and you can also look into the Generic fixtures already in the library where, for example, an LED PAR where ch1 is red, ch2 is green, ch3 is blue and ch3 is intensity will be listed as RGBI. All of his does, of course, rely on you knowing what parameters your fixtures use (i.e. having access to the manual for the specific model). If you don't have the manual then proceed as follows... With an empty patch, assign some dimmers (more than the number of parameters you think the fixture has got) and starting at the fixture's address. With the fixture powered up, try all the "dimmers" and see what happens. Bear in mind that, to get output, you may need at least two parameters (intensity and colour) up at the same time. You may need three if there is a "shutter" parameter that isn't open at zero. Try to be methodical but it does involve some trial and error. Good luck!

That's the trouble with answering queries on a forum - where between noobs and "actually they know more than me" should you pitch your reply. On a full FLX I'd use an MFK but a playback (as described in my last post) should work as well.

But that's the thing with LTP. When the playback is released, the "last" value (from before the playback) is the one that takes precedence. Your playback needs to set the beam parameter to zero, have release on lower set and should (maybe) have trigger level set to 1% instead of the default 5% https://www.zero88.com/manuals/zeros/cues-playbacks/playback-settings/raise-and-lower#level The snag is that the release is a snap not a fade. I think there's a setting somewhere to fix that but I've never looked it up.

Double check whether you have accidentally included intensity (I'm always doing that!). If you have then you can update with remove (or just set it up again). If you haven't made that mistake then maybe inhibit only works on intensities. It's what it is intended for after all. I've never tried it for anything else. Intensity is HTP of course (hence the need for inhibit). Other parameters are LTP so you don't really need inhibit. A normal playback with the beam at 0 should do it.

Phantom ZeroOS is ZeroOS with a Windows "wrapper" - unlike a hardware desk, you don't/can't load ZeroOS onto it. So Phantom ZerOS version is ZeroOS v8. If you want ZeroOS v7.14.3 then you need to download Phantom ZerOS v7.14.3 which should be in the 7.14.3 zip file under legacy software on the downloads page.

No at all. Valid correction.

Yep, OK, point taken. My take on it was affected by wanting static i/p addresses in my network. Not that I've used TB, just wanted a network I could use it on without re-configuration.

You have to use sACN if you want tracking backup. It cannot work with ArtNet. See the grey information box on the manual page for tracking backup. https://www.zero88.com/manuals/zeros/setup/devices/tracking-backup

To me, this sounds both complicated to set up and hard work to play back but, if it works for you, then carry on!

With you there, however I'm still addicted to the "candy" and try to treat the rigging as good exercise as I slide the last couple of months to my 70th birthday. Good luck with the new hobby but it's called fishing not catching for a reason 😀

You should report the CMY issue as well I think, maybe include your before and after show files if you have them.

Not sure I can help since I've no experience of CMY fixtures. I've scanned through the manual and not spotted any quirks that could trip you up. Best I can do is ask stupid questions and, maybe, you'll see the problem for yourself by answering them. Have you tried a colour or full fixture reset (channel 22 or 19)? Is the colour wheel at "open" when you are trying to colour mix? What output is the fixture giving? Is it (apparently) stuck on white? Black? Something else? What does the desk's DMX output screen say for the CMY, colour wheel and shutter channels? I see from the manual that these fixtures can display the DMX values being received. Do they agree with what the desk says it is sending? Have you contacted @kgallen? He's generally more use than me.

For a more "busker" approach (i.e. without cues) and only if you can accept Red->Yellow->Orange->Green... Something to set the fixture(s) to red. This will depend on what else you are using the fixture(s) for but could be fixture default, a cue, another playback, possibly even RGB colour mixing playbacks) and an intensity only fader OR A playback that sets the colour red and controls intensity. Fader action is intensity only, NOT colour. This will switch to red when the fader goes about 5% but you can change that to 1% if you like. AND A playback with fader action colour ONLY that fades to green. I haven't time to actually try this but I think it should work.

For the record the spam has been dealt with, presumably by @RJP who logged on shortly after I mailed support.

If you've got sufficient evidence you should mail support as it doesn't look as though anyone at VariLite ever looks at the forum.

The issue here is that the "admins" @DMH and @RJP don't actually log in to the forum, respond to DMs or deal with reports. DMH hasn't logged on since December, RJP logged in a week ago but only after I mailed support about the last batch of spam. As to the crazy concept of them actually responding to posts... Well, so far there is no evidence of that. Mailed support.

I think a lot of fixtures with "16 bit" parameters ignore the a few of the least significant bits. Presumably they are limited by the steps on their stepper motors. We live and learn. 😊

Interesting and makes sense. Did you try the intensity wheel by any chance?

The order you start things in may be significant. My guess is desk first is best but it's by no means certain.

So, @saitekx830, you seem to be doing the right things. If I was in this position I'd probably run Netscan (other network scanners are available) from the PC running your cueing software to just check that it can see itself and the desk. I'd expect that to work if the remote app is working but you never know. I use wired connections and find it helpful to disable WiFi to make sure the software isn't trying to use the wrong network. I guess, if you are using WiFi, you could disable any wired connections. Next, I'd go to the desk and after (like you) checking the network connections, I'd go to event monitor and send a few OSC commands. I do find that the first couple after switch on don't appear on the monitor (fine from about the 4th command and continues fine as long as the connection remains up) Now there are three possibilities, if you commands are not appearing then there is something wrong with the connection between your software and the desk, if they are appearing but with errors then they are just plain wrong (format, invalid commands or something) and if they appear without errors but don't do anything then they are valid but the thing (cue, playback, whatever) they should fire doesn't exist. If that didn't solve it then I guess the next step is to consult your neighbourhood witch or sorcerer. 😀