Jump to content


  • Content count

  • Joined

  • Last visited

  1. Hello. I have put addressable LEDs in my speaker grilles (Teensy controlled). Looks very nice when they use same setting as the Pinball buttons (also same LEDs). I use DOF "Flipper Button MX" for these. Constantly ON function. Now I tried to add some flashing to the speakers too, making a combo of "Flipper Button MX" and "PF Back Strobe MX". But nothing happens... the speaker LEDs are still constantly on... They can't flash wihout being turned off?? Or is it some layering issue, that the "Flipper Button MX" has to uppermost layer, covering everything else?? Anyone has an idea how to get my desired effect?
  2. DOF not working in VP, but in DOF testing??

    Now I saw it!! Blue color LED at the teensy means it's not original. Very strange, I bought it at a trusty european electronic store. New teensy board ordered! Big thanks for the support, I was totally focused that it was a communication problem.
  3. DOF not working in VP, but in DOF testing??

    Thanks, I followed the same directions. This is so strange.. Today I've reprogrammed the teensy, reconfigured and tested COM7 instead of COM3, played with baud, bits in the serial config. Reinstalled B2S (incl clean it out of registry). Whatever I try I get the same result. Testing config all LED's OK, playing table no LED at all. I don't have one single error message, everything looks just like pictures/directions. If I could get some reference from working setups, I might figure it out... * How is your teensy blinking/responding while playing table in VP? * What version of B2S are you running? * Is there any program to monitor the B2S communication?
  4. DOF not working in VP, but in DOF testing??

    Anyone have an idea how to solve this?
  5. DOF not working in VP, but in DOF testing??

    Nope, makes no difference... Every LED responds in "DirectOutputConfigTester", but at table in VP all LED's dead. Other idea´s ?? In my opinion: If the LED's are acually working, then it must be related either Teensy or B2S sending and receiving commands. Teensy is flashing in blue constantly repeating: Two blinks - short pause - two blinks - short pause - two blinks - short pause - etc.. I've tried connecting Teensy to another USB-port. It made no difference..
  6. DOF not working in VP, but in DOF testing??

    Ok, here we go! I stripped the log file, otherwise this is my current set up. This time testing Jurassic Park... Thanks for all help! Cabinet.xml GlobalConfiguration_b2SServer.xml DirectOutput_LastLog.txt
  7. DOF not working in VP, but in DOF testing??

    Ok thanks, I tried a couple of more times, same results. I can't find any difference compared to https://directoutput.github.io/DirectOutput/installation.html But b2sserversettings.xml ?? I made a search for that and could not find it! Interesting, where is the standard location for that file? Otherwise, is a full re-install including windows a good option? Been struggling for weeks, at this moment I hate this Pinball Cab more than my wife does...
  8. Hello I need some help to isolate my problem. I'ven running A LOT of testing, reading, testing, etc but I can't understand what's wrong. I have Teensy + one strip 156 addressable LED's running right+back+left side. If I load Medieval Madness in DirectOutputConfigTester.exe, I get solenoid and switches list. While sending pulse or activation all my LED's respond nicely. BUT when I start the exact same table in VP nothing happens??! No blink, nothing... Plugins are activated, DOF is running, table is running, no lag, etc etc. What could cause this behavior?
  9. Pin2dmd fried?

    I know for sure that I by misstake connected the panels to 12V instead of 5V. I also know that sound of electric overload (crackling, frying), so I pulled the chord at once. These became useless (but not exactly dead either, they're constantly like the picture). Buy new panels was my solution, expensive misstake...
  10. Startup trouble

    Ok, Thanks for all help! I got it working now!! I found another China STM32 board that I had forgotten (Too much stuff?? Yes I think so..). This also had the same faulty MicroUsb socket, so I built a reversed MicroUsb cable, connected, flashed, and installed driver. All fine. Extra wire from PA9 to 5V also working for powering the board. Only thing is another hardware means I need a new activation code, but that's cheap and fast compared to buying new hardware. BIG WARNING for those who buy China-STM32's: The MicroUsb socket/cable must be upside-down compared to the MiniUsb socket/cable! Otherwise you'll fry your board, or even worse your computer. Wrong MicroUsb socket makes the board a complete short-curcuit.
  11. Startup trouble

    Ok, I need a new board... Searched the net for STM32F407, but it seems they're out of stock everywhere and not manufacured anymore. Just "china-versions" available. I'll skip those... Can I go for the STM32F411VE instead?? Looks similar.
  12. Startup trouble

    Since this seemed to be useless, I spent some time "repairing" it. What I found is the MicroUsb socket must be upside down. Simple measuring showed that the +5V pin at a normal MicroUsb cable is routed to the boards common ground!! WTF! So I made some soldering. Put the faulty socket off, and soldered a Usb-cable directly to the board. Correct this time. Now, Windows find something at least and PC boots without any problem. But when I start Zadig install tool, I don't have any PIN2DMD at the dropdown list?? What to do here? Does it look normal?
  13. Startup trouble

    Picture of STM32 board and panels. Power from Mini Usb. Powering STM32 only by Micro USB is impossible, but according to everything I read it should have worked... Display looks nice, but a bit boring with nothing else than the PIN2DMD logo all the time
  14. Startup trouble

    OK! Thanks for that info. I can't power up the board at all by Micro Usb, 4 green leds while powering by Mini Usb... Then this board must be defect. I'll get a new one.
  15. Startup trouble

    I feed the panels with a separate old PC PSU. Should be ok and enough current. I think it's something round the STM32 board. It's almost like a short curcuit when I connect the MICRO-Usb cable. I've checked the instructions over and over, but I can't find what I'm missing... so frustrating...