Great as ever that you post details about everything you do so openly.
One question ... I assume you plan to include support for SMARTDMD / PIN2DMD colouring files that have already been done, on the MK64/66 platform?
Also, will your own software colouring solution use the same file format etc so it's also backportable to them, where the colouring does not exceed their feature set?
Edit: Oh, and what were the new and old refresh rates on the LED panels?
I must check yet if may I import pin2dmd format files. At any rate for pin2dmd there are currently only a few colored files and all (except one) are for SAM. The big problem to colouring for pin2dmd is that their editor is very simple, not optimal colouring by hand pixel by pixel, people need months to do a game. My idea about software to apply advanced color is very different.
I'm pretty sure at least half the files for PIN2DMD were actually done for SMARTDMD originally (like AC/DC and Metallica that PinballMikeD did). I don't know if the 2 platforms share the same file format, or if the colouring work for SMARTDMD on Pinball Browser was just exported to the PIN2DMD format. The only full recolouring (still not pixel by pixel) I have seen specifically for PIN2DMD is TSPP which the Russian guy recently did.
The main issue I find with your design Luis (and all the others) is it would improve the panel greatly if you had two 5v outputs on each PCB to feed the P2.5 RGB LED panels.
I am sure the actual 'data' part of the design is very low current draw, as the panels take most of the current.
How do you pick up the 5v to panels on this design?
Using your ST board it works perfect in visual pinball but not a stern SAM game. This is not your fault, its down to the way pin2dmd does things, and pinball browser.
How far away is MK66 to being released. I think you should concentrate on that! I know plenty of people that would buy these displays as they find pin2dmd too much of a headache. Most people want a plug in and play option.
Interested in CFTBL Mod, keep us informed
What is exactly the problem with Stern SAM ??.
Yes, I know. My only doubt now is whether to follow the design with Kinetis microcontrollers or use Raspberry pi 3. I've thought about preparing a prototype with Raspberry Pi3 and test it, its a very powerful option, better than any microcontroller. Now is the moment to choose.
And also I have thought about do development step by step and post each detail like I'm doing now with the Creature Holo Mod, so may I see how people is interested, suggestions and comments, I work faster than try to do all and then publish a product ready to work.
.
I'm really confused about if do DMD with Rpi3 or Kinetis microcontroller. Each one has advantages and disadvantages.
Rpi3 is a SOC with a Multitask OS (Linux), so its not dedicated to only one task and this may be a problem with software depending from timings, also do not has many direct I/O ports, but its so powerful that may be may compensate these disadvantages. Rpi3 also has a GPU, so may play video in High Resolution (1080) or control any TFT to display animations.
A custom device with a dedicated microcontroller, do not has dependencies from third party hardware, but do not has so much memory to store firmware and RAM. And this is a hardware that run ONLY the firmware, no more task at same time. So though not so powerful like Rpi3, run only one task is a dedicated device and finally may be even powerfull than Rpi3 to run same firmware. Also a microcontroller has many I/O ports, MK66 is a 144 pin TQFP, so more than 100 I/O ports available.
Both may use SD card to store config files, color palettes, and coloured animations, both access to SD by parallel SD port 4 bit, so its a very fast access. My MK66 also may install a flash memory 512Mb to store color animations for very fast access, but may be its enough SD 4 bit parallel access, it's cheaper and easy to do hardware.
The SD card holds the serial key and palette on pin2dmd. A few k only.
A pin2dmd takes 2 seconds to boot and start working. A pi takes longer. Especially if it has to load an os.
I do not understand why people are looking for another solution when this one is fine.
Is there a need to spend more time and effort?
The led panels cost the same whatever you use.
If you use a pi you'll still need a psu of 5amp, the new board has psu inbuilt. Plus you will need a daughter board with the pi to connect the dmd data and send data to the panels.
The cost will probably be more than this solution. You will spend weeks working on it to get same result.
You will end up with something like the dmdextender from Dr Pinball that drives vga monitor(s). That retails for £60 plus cost of pi and cost of screen panel.
I think part of the attraction is the possibility of incorporating it into an ecosystem of mods which Luis may or may not intend to build - like his CftBL holo mod. A Pi surely makes this rather more achievable.
Also, let's say in 2 years time much denser LED panels become affordable, and we can have 256*64 instead of 128*32 for the same or similar price. Presumably, aside from upscaling the data to double the horizontal and vertical resolution, a Pi based solution would require little if any modification. MK66 or other ... maybe a redesign?
The resolution of the signal coming in will not be improved.
Are you talking about what colordmd do with an LCD monitor and the MM remake? That work needs a lot of work programming.
These displays look great as is. I would post a video but my phone doesn't do it justice.
I've not noticed ghosting on these displays. Each dot currently is probably a little smaller but the light that is given off it you don't really notice. It is a different light to a normal plasma dmd.
Most people who are into pinball love the rgb led panels.
Have you purchased one of these @ducks as I think I can get one of these going with your bop2.