Led Strips doesn't work on Teensy 4.0 with OCTOWS2811

[Inalambrico]

Hi All,

 

I have installed Fat-Fred's firmware version 1.04 on my Teensy 4.0 with an OCTOWS2811 Board. All the wiring and LED strips are functional, as the lights turn on correctly during the firmware's initial startup test.

 

Based on my checks, the entire Visual Pinball X and DirectOutput (64-bit) installation seems to be working properly. However, when I launch VPX, the lights do not turn on.

 

Currently, I am testing with a single strip of 11 LEDs. I have tried plugging it into every single port on the OCTO board; the initial test works on all of them, but they always remain off afterwards.

My only suspicion comes from the DirectOutput.log, where the ComPort initialization is always set to 9600 baud. I believe this shouldn't be the case, but I don't know why it's happening or where I can change it.

 

I have attached screenshots of the active DOF plugin, the cabinet.xml file, and the DirectOutput.log.

 

Any clues or help would bDirectOutput.loge greatly appreciated. Thank you very much in advance!

cabinet.xml

[Rappelbox]

1. did you configure the ws2811 device in dofconfigtool and update your directoutput30.ini files?

2. check your GlobalConfig.xml, GlobalConfig_B2sServer.xml and GlobalConfig_PinballX.xml they all should look something like this,

especially the lines with "GlobalConfigFilePatterns" and "TableConfigFilePatterns" should both point to files and be complete with the matching</> closing brackets

 

i attached my config for reference

 

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 0.9.6474.38194: 2018-05-12 14-20-27-->
<!--Created and shared by GermanGamingSupplies.com-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>1</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <IniFilesPath>C:\DirectOutput\Config</IniFilesPath>
  <ShapeDefintionFilePattern>C:\DirectOutput\Config\DirectOutputShapes.xml</ShapeDefintionFilePattern>
  <CabinetConfigFilePattern>C:\DirectOutput\Config\cabinet.xml</CabinetConfigFilePattern>
  <TableConfigFilePatterns>C:\DirectOutput\Config\tablemappings.xml</TableConfigFilePatterns>
  <EnableLogging>false</EnableLogging>
  <FastInitialization>true</FastInitialization>
  <ClearLogOnSessionStart>true</ClearLogOnSessionStart>
  <LogFilePattern>C:\DirectOutput\Config\DirectOutput.log</LogFilePattern>
</GlobalConfig>

 

[Inalambrico]

22 hours ago, Rappelbox said:

1. did you configure the ws2811 device in dofconfigtool and update your directoutput30.ini files?

2. check your GlobalConfig.xml, GlobalConfig_B2sServer.xml and GlobalConfig_PinballX.xml they all should look something like this,

especially the lines with "GlobalConfigFilePatterns" and "TableConfigFilePatterns" should both point to files and be complete with the matching</> closing brackets

 

i attached my config for reference

 

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 0.9.6474.38194: 2018-05-12 14-20-27-->
<!--Created and shared by GermanGamingSupplies.com-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>1</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <IniFilesPath>C:\DirectOutput\Config</IniFilesPath>
  <ShapeDefintionFilePattern>C:\DirectOutput\Config\DirectOutputShapes.xml</ShapeDefintionFilePattern>
  <CabinetConfigFilePattern>C:\DirectOutput\Config\cabinet.xml</CabinetConfigFilePattern>
  <TableConfigFilePatterns>C:\DirectOutput\Config\tablemappings.xml</TableConfigFilePatterns>
  <EnableLogging>false</EnableLogging>
  <FastInitialization>true</FastInitialization>
  <ClearLogOnSessionStart>true</ClearLogOnSessionStart>
  <LogFilePattern>C:\DirectOutput\Config\DirectOutput.log</LogFilePattern>
</GlobalConfig>

 

Hi Rappelbox,

 

Thank you for your interest.

 

Related to 1.

Unless I set it up wrong, I'm pretty sure it's OK.
Under "devices" I selected WS2811=1, and under "Port Assignments" I have P:001 assigned to RGB Flippers, since the tables I am using for testing feature this effect.

I generate the directoutputconfig.zip, go to properties and check "Unblock", unzip it, and copy directoutputconfig30.ini, tablemappings.xml, DirectOutputShapes.png, and DirectOutputShapes.xml into C:\DirectOutput\Config.

In tablemappings, the Space Shuttle table is mapped to the "sshtl" ROM, while my table launches "sshtl_l7". In the directoutputconfig30.ini I only see references to "sshtl", though I assume it will also link to "sshtl_l7".

In fact, directoutputconfig30.ini is generated with what looks like an error, showing:
…
gw,ON Red
gw_l5,FF,ON Red
FF,ON Red
gwarfare,ON Cyan
…
Which I correct and change to:
gw,ON Red
gw_l5,ON Red
gwarfare,ON Cyan
In any case, those ROMs do not affect my testing tables.

Additionally, in the log referred to the [Config DOF] section, there are warnings referring to PinballX,\(sevenwinner /\)cp #006666/…. and PinballY,\(sevenwinner /\)cp #006666/…. which I decide to delete since those are not the Frontends I use. This leaves my directoutputconfig30.ini as attached, and I also attach the resulting log file using this .ini.

 

Regarding your configuration file in 2.

 

I have some differences that could explain the failure. I only had assigned:

<IniFilesPath/>
<CabinetConfigFilePattern>C:\DirectOutput\Config\cabinet.xml</CabinetConfigFilePattern>
<TableConfigFilePatterns/>

 

Which I correct and change to:
<IniFilesPath>C:\DirectOutput\Config</IniFilesPath>
<ShapeDefintionFilePattern>C:\DirectOutput\Config\DirectOutputShapes.xml</ShapeDefintionFilePattern>
<CabinetConfigFilePattern>C:\DirectOutput\Config\cabinet.xml</CabinetConfigFilePattern>
<TableConfigFilePatterns>C:\DirectOutput\Config\tablemappings.xml</TableConfigFilePatterns>

 

I have:
<EnableLogging>true</EnableLogging>
Which I keep to analyze the execution.

 

I do not have:
<FastInitialization>true</FastInitialization>
So I add it.

 

Both in GlobalConfig.xml and in GlobalConfig_B2sServer.xml. I also do not have a GlobalConfig_PinballX.xml; I assume it is for the PinballX frontend, but I am including it anyway even though I am going to use PinUpPopper.

 

With all this analyzed and corrected, there are still no lights when launching Leprechaun King (Orbital 2020) — they should light up Green — or Space Shuttle (Williams 1984) — they should light up Red — using VPX64. Although when the table starts, you can see that there is communication between the PC and the Teensy via the board's status LED.

 

I hope all this information is helpful. Thanks again.

directoutputconfig30.ini DirectOutput.log GlobalConfig_B2SServer.xml

[Rappelbox]

for ALL addressable LEDs you have to use the MX variants, not the regular RGB devices!

 

 

[Inalambrico]

21 hours ago, Rappelbox said:

for ALL addressable LEDs you have to use the MX variants, not the regular RGB devices!

 

 

Well, that was the last missing piece. It's working!!!

 

Time to move to another forum to look for help solving some minor issues with the contactors via PinScape and the SSF, so I can finally finish my Pinball after 5 years of work.

 

Thank you very much. 🙌