Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ashram56

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good morning, I would need to build acrylic protection panel for PIN2DMD, similar to those used in Stern SAM machines (except that in this case the acrylic panel is red, I need fully transparent). I thought the acrylic frame in the github would answer my need, but it seems the SVG file for 128x32 is empty (whereas the other files are not), plus the other files seem to be STM32 Shield instead of EVO. Would someone have this information ? I can probably rebuild it otherwise, it's a simple rectangular panel with 6 holes Thanks and regards
  2. I posted this on Pinside.com but with no response so far I'm trying to make sense of the various colorization options for a DMD, and there seems to be vastly different approach between Pin2DMD Editor and PB From what I understand: - Using Pinball Browser: PB dumps all DMD frames from the rom file, you can colorize them individually, this will generate a smartdmd.txt file which you can then use to create a pin2dmd.pal file that you put on an SD card in Pin2DMD, BUT you need to reflash your ROM. It also does not work for older machines (prior to SAM). - Using Pin2DMD Editor: you can only edit DMD frames which you have previously manually dumped (simulated gameplay using a vpin, or equivalent), in the end you get a project file which you can use to generate a pin2dmd.pal and a pin2dmd.fsq file. Using this solution there is no need to reflash the ROM, and it works on older machines - but from what I understand it does not work for Stern Sam So first, is my understanding correct ? If so, one could wonder why PB does not allow to export all DMD frames to use them as the basis for pin2dmd editor as Pin2DMD method seems more flexible to me. Granted PB has this "side channel" option, but it requires an additional cable, but since it only works with SAM from what I understand Anyway, I just wanted to check if my assumptions are correct Thanks
  3. Good morning everyone, I also received today a set of pictures from PCB Way (for some of them it's kind of hard to check) It looks OK to me (they only pointed out in details one diode), but would appreciate a second point of view just to be sure Thanks
  4. I recently acquired a few real pinball units (among them a Tron, a Star Trek and a LOTR), and going through the overall HW architecture it seems it would be possible to implement PuP packs (among other capabilities) for these (Stern SAM, Whitestar, WPC, etc). And the beauty is that the concept is pretty much identical to what has been done in the VPinball world, ie add a snooping interface to a RPI or equivalent to the DMD interface (it's a relatively simple cable with level shifters) to capture DMD frames and identify them, and trigger video playback using gstreamer or equivalent on the RPI. @TerryRed I see on Pinside that a pinball modder actually did something similar on a Tron unit (you actually responded to that thread), and used your PuP Packs, but his implementation was significantly different, ie he used a modified SAM firmware to enable serial communication between the main Stern SAM CPU board and the RPI, so installation was a pain, and it was limited to Stern SAM pinball machines. Plus he never disclosed his source and essentially sold three units from what I could gather on Pinside Using a DMD snooper essentially mimics Vpinball implementation, it can be used across multiple generations (essentially all DMD units), and it's much easier to physically install (a very simple PCB with a few components that would insert itself between the CPU board and the DMD board). PuP Packs triggers could be used as is... I see here an opportunity to bridge the gap between virtual pinball and pinball, but I lack the SW skills to develop this (HW and architecture is fine). I can contribute a Jetson Nano to interested developers (within reason, ie a few units). Why a Jetson... because 🙂 Joke aside, primarily because of my background it would be a shame, and second because I know where/how to get support for multimedia and the like, and I know the architecture better than a RPI (Jetson has a VIC, which is essentially a compositing unit for video). Plus Jetson carrier boards are cross compatible (you have Nano 2GB, Nano, NX), so if performance is a limitation, you can actually upgrade easily. Any taker ? @NailBuster, any interest into this ? Cheers
  5. Thanks for your response, indeed the github you are referring to is a good starting point, as my goal is to essentially deploy it on a RPI or equivalent (I know about SmartDMD, but I prefer to go the open source route, as SmartDMD being closed source I can't modify and add to it easily).
  6. Good morning, May I know what are the conditions to get access to PIN2DMD source code ? I'm not specifically interested into building something that would mimic Pin2DMD, I'm more interested into the DMD protocol itself (from a Stern SAM/Whitestar/etc). Idea is to grab the DMD frame, generate trigger based on this (very similar to what is done in the PuP pack world on a pincab), and other activities. So I'm not necessarily interested into the whole source code, just the "frame grabber" portion Is there any limitation to access it ? Regards
  7. Many thanks for this clarification. I guess the rationale for colorization creators is that real pinball owner will likely pay a premium (and rightly so) for a colorization, whereas virtual pinball owners might not be so inclined. It's indeed perfectly legitimate to ask for a donation given the amount of work required. Is there however a "catalog" somewhere with a list of colorization and who to contact to get them ? Or is this a matter of searching the internet ?
  8. Good afternoon, Beside my virtual pinball machine, I now own a few real pinball units, which I'm considering upgrading to PIN2DMD for color support. Now what I don't understand is why is there a difference between a virtual pinball and a real pinball with regards to colorization support. Specifically technically, is there any reason why a virtual pinball colorization could not be transferred over to a real pinball machine (besides the specific file required) ? Couldn't any of the author of vpin colorization generate the fsq file required for operation on a real pinball ? Is there a legal reason, a technical reason, or something else ? I'm specifically looking at Lord of the Ring, which does have a virtual pinball colorization, but no real pinball version. Creature of the Black Lagoon (and a few others, but not many), does have both. So just wondering what I'm missing here Thanks and regards
  9. Good morning/afternoon, As an owner of a LOTR real pinball, I would be interested to know about the availability of a colorized DMD before I actually buy a pin2dmd unit for it. Is there any timeline set? Thanks
  • Create New...