Ciceronic 2 Posted March 15, 2018 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? Share this post Link to post Share on other sites
Thalamus 413 Posted March 15, 2018 Very hard to say. You've double verified that you've do it this way and that eg b2sserversettings.xml is correct ? https://directoutput.github.io/DirectOutput/installation.html Share this post Link to post Share on other sites
Ciceronic 2 Posted March 16, 2018 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... Share this post Link to post Share on other sites
outhere 164 Posted March 17, 2018 Post your GlobalConfig_B2SServer.xml, Cabinet.xml and log File Share this post Link to post Share on other sites
Ciceronic 2 Posted March 17, 2018 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 Share this post Link to post Share on other sites
outhere 164 Posted March 17, 2018 GlobalConfiguration_b2SServer.xml <----Try rename this file to this --->GlobalConfig_B2SServer.xml Share this post Link to post Share on other sites
Ciceronic 2 Posted March 17, 2018 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.. Share this post Link to post Share on other sites
Ciceronic 2 Posted March 18, 2018 Anyone have an idea how to solve this? Share this post Link to post Share on other sites
outhere 164 Posted March 18, 2018 Here is some information I found but it does not look good https://www.pjrc.com/teensy/troubleshoot.html Share this post Link to post Share on other sites
outhere 164 Posted March 18, 2018 These are the directions I went by and The links in the directions take you to the area to buy the boards http://www.vpforums.org/index.php?showtopic=36156&hl= Share this post Link to post Share on other sites
Ciceronic 2 Posted March 19, 2018 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? Share this post Link to post Share on other sites
outhere 164 Posted March 19, 2018 Here is some information I found but it does not look good https://www.pjrc.com/teensy/troubleshoot.html Share this post Link to post Share on other sites
Ciceronic 2 Posted March 19, 2018 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. Share this post Link to post Share on other sites
