swisslizard

More details please. What does "some lights stay on" mean? Are the other leds working? Are those leds also on before a table is started?

Hi Has a quick look at your config files. The problem seems to be in the cabinet config. You have several toys which are all named "PF Back". DOF does not allow this. Toy names must be unique! Make sure you have only 1 PF Back toys, with the actual number of rows and columns you have on your PF back. The ledstrip toys should not care if the strips are connected to several different outputs of the controller. From a toy perspective there is always only one long strip which covers all outputs. To get the FirstLedNr you'll have to sum up the number of leds on all channels before the one which has to led you want to reference, e.g. to get the 4th led on the 3rd channel you have to calculate the following: NumberOfLedsOnChannel1 + NumberOfLedsOnChannel2 + 4 All the best Tom

Another small DOF update. http://pinball.weilenmann.net/DirectOutput_V0.9_Build_5850.21660.zip Changes: Logging is now on by default (can still be disabled on global config). Frontend main window does now show the path where DOF is installed. Both changes have been done, to help all those new DOF users having trouble to get DOF properly installed. In many cases those problems where caused by multiple B2S.Server installations on the same cab and VP starting another B2S.Server/DOF instance than yoe users thought. These changes should make it easier to detect such problems.

OK, there where a few small things to fix in your config. Backboard: LedStripArrangement was not correct. Have a look at the following page to get a idea of the different ledstrip arrangements that dof supports: http://pinball.weilenmann.net/docu/DirectOutputWIP/toy_builtin.html#DirectOutput_Cab_Toys_Hardware_LedStrip_LedStripArrangement Sideboard Right: Also here LedStrip Arrangment was not correct. Sideboard Left: Again, LedStripArrangment was not correct and the first LedNumber was wrong too. Calc for first led: 1+ leds on pf right + leds on backboard = 253 (1 + 60 + (6*32)). Hope these fixes will solve your problem. <LedStrip> <Name>BackBoard</Name> <Width>32</Width> <Height>6</Height> <LedStripArrangement>RightLeftBottomUp</LedStripArrangement> <ColorOrder>GRB</ColorOrder> <FirstLedNumber>61</FirstLedNumber> <FadingCurveName>SwissLizardsLedCurve</FadingCurveName> <OutputControllerName>TeensyStripController</OutputControllerName> </LedStrip> <LedStrip> <Name>Sideboard Right</Name> <Width>1</Width> <Height>60</Height> <LedStripArrangement>TopDownLeftRight</LedStripArrangement> <ColorOrder>GRB</ColorOrder> <FirstLedNumber>1</FirstLedNumber> <FadingCurveName>SwissLizardsLedCurve</FadingCurveName> <OutputControllerName>TeensyStripController</OutputControllerName> </LedStrip> <LedStrip> <Name>Sideboard Left</Name> <Width>1</Width> <Height>60</Height> <LedStripArrangement>TopDownLeftRight</LedStripArrangement> <ColorOrder>GRB</ColorOrder> <FirstLedNumber>253</FirstLedNumber> <FadingCurveName>SwissLizardsLedCurve</FadingCurveName> <OutputControllerName>TeensyStripController</OutputControllerName> </LedStrip>

OK, that should be easy to fix. Can you give some more information on your strip arrangement. As a example for my cab that would be: Teensy channel 0: PF Back: 3 * 32 leds - rows arranged top to bottom, columns within rows arranged left to right Ledstrip PF right: 65leds - direction back to front Flipper button right: 4leds - top to bottom Ledstrip PF Left: 65leds - direction front to back All other Teensy channels are empty. Please show us you cab config file too.

@Bashyrk: You'll have to change your config to use the TeensyStripController According to the waring in your log you are using the DirectStripController class which is for a different type of hardware. @All: Regarding the Teensystrip controller: Just a few minutes ago, I have uploaded a slightly extended version of the firmware for the Teensystrip controller to Github: https://github.com/DirectOutput/TeensyStripController/releases This version adds support for the control led on the Teensyboard, so you get a little feedback on whats going on from the boards perspective.

@Vampirlatino: Use fade curves to adjust the overall brigthness of your leds: http://pinball.weilenmann.net/docu/DirectOutputWIP/configexamples.html#configexamples_teensystripcontrollerfadecurve

As mentioned a few times before, setups with a lot of leds have to be carefully planned and built. Otherwise unpleasant surprises might occur. Things like diameter of the 5v and gnd lines, how often you inject power and so on are rather important, since doing this wrong can create a lot of heat (which can destroy a lot of things or even start a fire). In most cases where I had some part of the strips suddenly not working anymore, the only thing I had to do was to replace one single led (the first of the not active leds). As cool as those leds are they are still just a rather cheap china product and high quality is usualy not something you can rely on.

Merry xmas @Karlson: Your log file looks fine, the Teensy and your ledwiz appear as they should, updater threads get started and so on. It is strange that things are not working. From my point of view there are 2 things which can be done now: Hardware Please check one more time if the wiring of your strips and of the controller are OK. The controller should only have its USB connection, plus the data and gnd lines from the controller resp. the OctoWS2811 board to the strips. The strips need in addition to the gnd and the data lines coming from the controller another 2 lines which connect them to +5V and GND. The power supply for the strips has to be strong enough, bot in terms of PSU and thickness of the cables. For 576 leds you should have a PSU which delivers at least 35A (personally I'd go for 40A) and you'll have to inject power in several places. Is all that correctly set up? Are you connecting to the correct pins of the controller. The networkcable I have used to connect my teens to the strip has the signals for the first channel on orange and the gnd on orange white (see image below). However, I cant guartee that this is the same for all cables. Teensy Firmware I'll try to hack a small extension of the Teensy firmware as soon as I can. The Teensy has a control led which is not yet used by the firmware. I'll add a bit of code to make that led flicker, whenever the Teensy receives data. This will make it much esier to determine if the Teensy is active and whether DOF sends data to it. But for now, I'll stop and head for the usual xmas festivities. All the best Tom

Hi Karlson First of all: Your post with the problem description is excellent! If all 'I got a problem' posts were like that, it would be more fun to help! Had a quick look at your files. Most things seem to fine, but I found one small problem: In your cabinet config you have the line <LedWizEquivalentOutputNumber>2</LedWizEquivalentOutputNumber> Try to replace 2 with 1 or if you want to target the second set of settings replace 2 with 4: <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber> Does that make a difference? Small explanation: The LedwizEquivalentToys are needed to help DOF to map the contents of the ini files correctly (The INIs are kind of sitting on top of DOF and are not a part of the inner architecture of the system). The structure of those ini files is still the same as it was in the old ledcontrol.vbs days. This means that config settings which are targeting 1 output (e.gh. a contector) will count for 1 column in the file. For RGB toys, the column with the config settings counts for 3 outputs (because a RGB toy has 3 outputs?). IMHO this a rather strange and not optimal approach (it is particularly absurd when dealing with ledstrips), but it is a legacy thing I cant change without breaking compatibility with old configs. When you deal with the outputnumber in the LedwizEquivalent toys, you have to take that 3 vs 1 column behaviour into account. To get the correct number you'll have to sum up the number of outputs for each column before the one for which you need the number (e.g. if you have a ini with RGB settings for 3 toys, the first toy will have output number 1, the second will have number 4 and the third will be number 7).

The pic of the first window of the DOF frontend shows that DOF doesnt load a global config file. For that reason it cant load a cabinet config either. Most likely the global config is in the wrong place. Put it into the config dir of dof.

Randr is right, the Teensy is not listed, which means that it did not get configured. I guess DOF does not find your global config and/or cabinet config. Please post a screenshot of the first window of the DOF frontend. It contains information on the loaded files.

OK, according to the screenshots DOF has been found and is active. Only did a quick check on your config files. They seem to be OK. So if I'm not mistaken your setup seems to be fine config wise. To get one step further, please go again to the B2S.Settings window and open the plugins window. Double click the entry for DOF. This should open up some kind of frontend for DOF. Check what the fields in that window say and let us know about it. Most important are the global config file and the cabinet config file. In addtion you can also click the "Show cabinet configuration" button and check which output controllers and toys DOF knows for your cab. This window is sometime VERY slow (its just a dirty hack), so be patient. Another thing to check is your hardware. Is the wiring of the ledstrip correct, did you connntect to the correct port pins of your Teensy?

Hi folks Please read the following points before asking for help with DOF issues: General As always RTFM! I know, reading manuals is maybe not the most interesting thing to do, but it often helps!DOF R2 Documentation: http://directoutput.github.io/DirectOutput/ Latest DOF WIP Documentation: http://pinball.weilenmann.net/docu/DirectOutputWIP/index.html In particular please make sure you read the pages on Installation and Configuration, Cabinet Configuration, Built in Toys, Built in Output Controllers. They contain a lot of sample xml structures which you can use for your own configs and there are explanations on most settings as well. Last but not least, here is a tutorial on the XML basics: http://www.w3schools.com/xml/default.asp DOF Installation Problems If DOF doesnt work, please check if it is installed correctly. Here are a few things to do: Double check your installation Instructions are on http://directoutput.github.io/DirectOutput/installation.html Make sure you really follow these instructions step by step. Check if DOF is visible for the B2S.Server Go to the B2S.Server settings screen and click the plugin settings button. This will open a new window, which should list DOF. If DOF is not visible there, check if DOF is in the right place (as explained in the installation instructions) and if the right B2S.Server instance is called (see next paragraph). Check B2S.Server installation(s) If the B2S.Server is working (backglass visible), but DOF is not visible in the settings window, your problem is probably that you have more than one B2S.Server instance on your machine and that VP calls a different B2S.Server instance than the one you think it is calling. Visual Pinball doesnt find the B2S.Server by its location in the filesystem (it is actually not relevant where you install the B2S.Server). Instead VP is looking up the B2S.Sever by its COM object name (that is the Createobject("B2S.Server") thing in the table scripts). This name is resolved by the system using a bunch of registry lookups, which will finally return the path to the B2S.Server dll file. If this path doesnt point to the B2S.Server which has DOF configured as its plugin, DOF will not be called. To fix this, try to reregister the B2S.Server instance for which you have installed DOF. Dont register any other B2S.Server instances on your machine. As a general rule of thumb, there is no reason to have more than one B2S.Server installation one a machine. IMHO it is bet to get rid of all duplicate installations if you have any. Unblock the files This is another typical installation problem, depending on how you put the DOF files into their installation dir, windows thinks that they might be dangerous (becaus you have downloaded them) and will block access to the files. This will stop DOF from working. Check if all DOF files are unblocked. Details can as usual be found here: http://directoutput.github.io/DirectOutput/installation.html#installation_unblockauc Enable Logging / Create a Global Config file For installations which only use a ledwiz or some other automatically detected controllers a global config file is not mandatory. However, if you have problems with your installation you should create a global config file, so you can enable the logging function of DOF. Instruction for global configs are overe here: http://directoutput.github.io/DirectOutput/globalconfig2.html Cabinet Configuration problems Most problems with config xml files are caused by a bad file structure resp. So before calling for help, please make sure your file contains valid XML. To check this open your xml file in Firefox, Chrome or even Internet Explorer. All those browsers are able to show properly structured xml in a nicely formatted fashion and even allow to expand and collapse parts of the file. If there are structural problems present, the browsers will not show the nicely formated structure and a error message (more or less helpful) is displayed. Use a tool which knows about XML to edit your files (plain text editors usually dont know xml by heart). There are quite a few XML editors available on the internet (I'm using Microsofts Visual Studio, but that is a full development IDE). These editors will help you to produce valid xml structures and typically they will also produce nicely formated files (which makes them much easier to read). Try to reduce the number of potential problems. E.g. if you try to extend your cabinet config for ledstrips and a Teensy controller get rid of everything you dont need to get that new stuff running (remove all ledwiz configs, all ledwizequivalent toys whiche are not related to the teens controller and so on) or start a new config file from scratch. This will make it much easier to detected the cause of a config problem. Once you have your new toys working or fixed the problem you can put all the other stuff back in place. If you still have trouble with your config files, please upload them to dropbox, Google drive or any other service you like and post the links instead of the file content! Dont post lengthy XML structures to the forums directly. It is much easier to just download a file and open it in a suitable xml editor instead of scrolling through long xml structures which are in many cases no even formated nicely. Posting help requests Dont ask for help using PMs Everybody should be able to learn from problems that occured earlier. For this reason I kindly request, that ask for help in the forums instead of private messages. Create your own thread Create your own thread with a decriptive name (e.g. Pinballwizard Ledstrip Config Problems) instead of reusing/hijacking another thread. It much simpler to keep track of things if they are in their own place. Threads where problems of several users are dicussed are becomming hard to follow pretty fast and it is more benefitial to concentrate on the actual problem solving than on trying to keep track of several different topics in one thread. Only reuse another thread if you have exactly the same problem as the one described in the thread first. "DOF is not working" is probably not the same problem for you as for someone else. Explain what you have tried Please explain in detail what you have tried already and what the outcome was. This will make it much easier to narrow down the possible causes of problems and will save us a lot of questions. Dont post lengthy file content It is much easier to just download a file and open it in a suitable tool, than to scroll through many pages of data in the forums. Therefore, please upload anything thats more than just a bunch of line to dropbox, google drive, one drive or any other service you like and post the link instead of the file content. If uploading several files or putting serveral file in one zip file, please give them a meaningfull name (Screenshot{Number}.jpg isnt a helpful name, B2SServerPluginSettings.jpg would be a good name). Be patient Everyone who is trying to help is only doing this a a hobby and we all got real life jobs and other duties as well. Therefore answers do sometimes take a bit longer. Nagging will not improve response times! Thanks and all the best Tom / Swisslizard