2 replies to this topic

[repulp565]

Hi all,
I'm setting up feedback (shaker) effects on a mini pincab and could use some help narrowing down where the chain is breaking.

Setup:
PinUP Popper installed via the "Baller Installer" package (DOF, B2S Server, VPX, etc. all installed through it)
Raspberry Pi Pico running Pinscape Pico firmware, 2 output ports (GP20, GP21), each driving a pair of recovered Xbox 360 controller rumble motors through MOSFET modules (so 4 motors total across 2 logical outputs GP20 = two larger/low-freq motors, GP21 = two smaller/high-freq motors)
DOF R3++ v3.2.9432.38451, x64-Release, built 2025.10.28
Cabinet.xml defines a <PinscapePico> output controller (NumberOfOutputs: 2, Number: 1) plus a LedWizEquivalent wrapper and two named <Shaker> toys pointing to Pinscape Pico 01\Pinscape Pico 01.01 / .02
directoutputconfig51.ini generated via the configtool.vpuniverse.com Port Assignments tool (both ports labeled "Shaker")

standalone DirectOutput configuration tester:
The motors work perfectly when tested directly from the Pinscape Pico config/setup tool (its own built-in output test). But the standalone "DirectOutput configuration tester" app never shows any rows after "Load config" with Cabinet.xml table stays empty (Type/Name/Number/Value/Activate/Pulse columns, nothing listed). Windows detects the Pico fine in the device tray. Tried running the tester as admin, closing other DOF-related processes, reloading the config no change.

Real gameplay symptom:
Launching an actual table (Medieval Madness, MOD "Bigus 3.0") through PinUP Popper, DirectOutput.log shows a clean init with no fatal errors and connects to the Pico fine, but nothing vibrates during play even after putting the ball in play and hitting slingshots/bumpers repeatedly. Not sure if this is related to the Tester issue above or a separate problem (e.g. RomName mismatch, or the table script not routing through B2S.Server).

This is my cabinete.xml:

<?xml version="1.0"?>
<Cabinet xmlns:xsi="http://www.w3.org/20...Schema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Toys>
<LedWizEquivalent>
<Name>Pinscape Pico 01 Equivalent</Name>
<Outputs>
<LedWizEquivalentOutput>
<OutputName>Pinscape Pico 01\Pinscape Pico 01.01</OutputName>
<LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
</LedWizEquivalentOutput>
<LedWizEquivalentOutput>
<OutputName>Pinscape Pico 01\Pinscape Pico 01.02</OutputName>
<LedWizEquivalentOutputNumber>2</LedWizEquivalentOutputNumber>
</LedWizEquivalentOutput>
</Outputs>
<LedWizNumber>120</LedWizNumber>
</LedWizEquivalent>
<Shaker>
<Name>shaker</Name>
<OutputName>Pinscape Pico 01\Pinscape Pico 01.01</OutputName>
<FadingCurveName>Linear</FadingCurveName>
<MaxRunTimeMs>300000</MaxRunTimeMs>
<KickstartPower>255</KickstartPower>
<KickstartDurationMs>100</KickstartDurationMs>
<MinPower>1</MinPower>
<MaxPower>255</MaxPower>
</Shaker>
<Shaker>
<Name>shaker2</Name>
<OutputName>Pinscape Pico 01\Pinscape Pico 01.02</OutputName>
<FadingCurveName>Linear</FadingCurveName>
<MaxRunTimeMs>300000</MaxRunTimeMs>
<KickstartPower>255</KickstartPower>
<KickstartDurationMs>100</KickstartDurationMs>
<MinPower>1</MinPower>
<MaxPower>255</MaxPower>
</Shaker>
</Toys>
<Colors />
<Curves />
<AutoConfigEnabled>true</AutoConfigEnabled>
<OutputControllers>
<PinscapePico>
<Name>Pinscape Pico 01</Name>
<NumberOfOutputs>2</NumberOfOutputs>
<Number>1</Number>
<MinCommandIntervalMs>1</MinCommandIntervalMs>
</PinscapePico>
</OutputControllers>
<ScheduledSettings />
<SequentialOutputSettings />
<TableOverrideSettings />
</Cabinet>

Thanks a lot for any pointers!

[Tesla]

Do all your DOF toys test properly with DOF Test Table from VPU?

[Suikazz]

remove toy and controller definitions from your cabinet.xml as they're not needed due to auto-config of the pinscape pico.

It could have the opposing effect that it prevents the pico from being properly addressed.

 

use the dof-test-table as you have more control over the used toys and output ports.

the shaker is not used on the slingshots and bumpers, btw.