When I started putting together Total Lightshow I only wanted lights. Lot's of lights! But I realised that I wasn't going to bother unless I could lock those lights into the game code properly, and not being able to hack the code directly, the next best thing is to read all the inserts and switches. Thus was born the Matrix Interceptor. And if you have been following the Total Lightshow development thread you'll know what it does.

I'm toying with the idea of taking the Matrix Interceptor from within Total Lightshow and offering it as a standalone mod-controlling board. Given that production of the PIG 2 seems to have ceased, maybe there is a need.

So, if you aren't familiar with the board, here is a quick introduction..
The board reads the ENTIRE insert and switch matrices of SAM(currently) machines, both Pro and Premium, and returns the following..

Any switch/s ON,
Any switch/s OFF,
Any Insert lamp/s ON,
Any Insert lamp/s OFF,
Any Insert lamp/s FLASHING.
It then drives 8 separate PWM power outputs (up to 6.3V), and 3 serial ouputs.

There are no alligator clips. Everything is plugged properly into and read at the main board, not out on the playfield. The real power of the board is being able to use COMBINATIONS of the above indications, along with timing and counting, to generate really complicated triggers for mods that can not only trigger in one way, but in different ways depending on different modes for example.

I have been thinking of GUI ideas for programming it, but as the possibilities are way too broad, it is only really feasible to program it properly though a Dev environment (it will ship as an Atmel Studio Project). Atmel Studio is free, and the only thing a user would have to do to program it is open up a window and choose which of the included chunks of code to activate.

I would include all the code devices I have developed for GI Theatre, which include faders, flashers, timers and switch counters to name a few. All the code examples would simply be commented out, and a simple copy/paste of a block of code would have it ready to go.
I may also include a library of standard images that can be played through LED strips via the serial outputs. LED strip images can be played at a chosen speed, can be played once or looped, and have a priority setting.

Now it may be simply too difficult for people to use, although all the code would be there in front of you, to be of broad interest. The board is obviously operational now as it is shipping as part of Total Lightshow, but I would need to do a bit of a clean up to get it fit for general consumption.

I'm thinking it would be around US$165(give or take, and this may change), including mounting hardware and all the cables required to get it connected. This is a bit more than the PIG 2 was, but it does more.

If there are only four guys out there who could be bothered using it, it's a bit tough to go through the work of updating it, but enough noise from the audience may get me over the line. I will actually be doing another rev of the board if I go ahead, to get some 12V outputs on it, plus a few other tweaks. I am also in the process of getting it going on White Star and some Williams platforms.

So, in short, it lets you read the whole machine's behaviour, and generate signals to drive your mods in any way you want. As an example, the primary use at the moment is replicating the GI lightshow and rising cross mechanism of Metallica Premium in Metallica Pro. You can dig up info from this long thread.. https://pinside.com/pinball/forum/topic/ramp-lighting-in-your-face-st-pro-brought-to-lifevideo

There are some photos below of the board and as it is mounted.

Shout out if you would want it, or if you have any questions on how it is implemented. If it is too hard, or too expensive, or just overkill, then it may not fly as an idea, but I thought I'd put it out there. It works, it's available now, it may fill a need.

IMG_3932_(resized).JPG

IMG_3931_(resized).JPG

IMG_3935_(resized).JPG

IMG_3934_(resized).JPG

Bump just in case I posted while the boards were too inactive, but the deafening silence is giving me a clue.

I think the issue I'm trying to clear up is whether there is really that much demand for complicated mod triggering. With something like the Lightshow it is crucial that it is constantly aware of what state the machine is in. A Flynn sign on Tron? Maybe not so much. But then, as Frax says, if you have a LOT of mods it might be useful.

I'm trying to get it ready for a fellow Pinsider to trial on a Williams machine so it may be one of those slow-burner things that just gets more interest as uses are gradually found for it.

I'm relaxed and will continue making it as part of the Lightshow and the add ons I have coming for that, so it will always be available. I will look at the standalone idea from time to time.

Completely flexible. The only limits are your coding skills. Program it in C++ to your hearts content. I built state machines to handle drop targets. It's providing you with lamp and switch events then you build on them as you please. I am only providing my code examples in order to get non-programmers started. If you're a developer already then have at it.

No flashers. I agree it would be nice to have everything, and on the odd occasion I admit I wanted the flasher info for a quick solution, but have so far found that combinations of lamp and switch states will get me where I need to get.

A bit of code syntax for example..

This is just a snippet out of the Met GI Lightshow. It's using some switch hits to activate the FUEL flash effect. It may look complicated to a non-programmer (it may look horrible to a better coder than me), but it shows you can use timing, and the simple commands to set power outputs to on, or to a pwm level.

CodeI_(resized).PNG
CodeII_(resized).PNG

The flash operation is raw, and I would put a macro in there to make it more user friendly.

Eli's mod takes lamp driving signals at the CPU bus. While I take the signal down at the matrix headers, Eli is still taking the signals as an output from the pinball machine and interpreting them in a similar process to me. He is getting signals that are on their way to the driver board but are still "post-code" for want of a better expression, and having to do his own processing to return on, off, or flashing states.

Thanks for the bump, haha, and questions. I'm generally not too worried about getting attention yet. I'm a product-speaks-for-itself kinda guy. A lot of promises get made with this kind of stuff and it's freaking hard to deliver, so softly softly.
To your questions generally, outputs are only limited by what I want to build in. At the moment the power outputs can draw around 1.5A each, but in total they are limited to around 2A. It's all based around driving lights, but I do have a motor project going with the Met Cross.

The serial outputs will drive WS 2812b protocol commercial LEDs. I dropped the proprietary strips as they were cost prohibitive to manufacture. They are not limited to driving those, as they are just hanging off SPI pins and can do whatever if you want to get down and build your own drivers.