24 replies to this topic

[thiago capalbo]

I'm having trouble running DOFLinx with PACLED64, because I can not recognize the board even following the tutorials found by forums.

 

I will describe all the procedures that I performed and present my files so that DDH69 and / or some other charitable soul can guide me in what I may be wrong to solve the problem.

 

OK, let's go...

 

I own the Zeb kit in which it has a pacled64 card in which DOF R3 ++ is working correctly with Visual Pinball 10.5.

 

Besides the zeb kit I have teensy that are working with my addressable led strips on the sides of my pincab. Both boards (pacled64 and teensy) are working correctly through DOF and VPX.

 

I have made countless attempts with DOFLinx following DDH69 step-by-step and failed to gain recognition of the PACLED64 board in DOFLinx.

 

I own future pinball, pinball FX2 (version not steam), pinball FX3 (steam version) and visual pinball.

 

I made some attempts of DOFLinx 6.27 with DOF R3 exactly as per DDH69 tutorial and made the necessary modifications to my DOFLinx.ini file according to the ports configured in dofconfigtool.

 

I created the DOFLinx.exe shortcut and on the command line I made countless attempts. Here are some of the attempts I made:

 

C:\DirectOutput\DOFLinx.exe PACLED64=1 PATH_INI=C:\DirectOutput\DOFLinx.ini

C:\DirectOutput\DOFLinx.exe PACLED64=1PATH_INI=C:\DirectOutput\DOFLinx.ini

C:\DirectOutput\DOFLinx.exe PACLED64=1 C:\DirectOutput\DOFLinx.ini

C:\DirectOutput\DOFLinx.exe PACLED64=1C:\DirectOutput\DOFLinx.ini

C:\DirectOutput\DOFLinx.exePACLED64=1C:\DirectOutput\DOFLinx.ini (Error - does not save when there is no space after .exedoes not save when there is no space after .exe)

 

does not save when there is no space after .exe

* In PACLED64 = 1, I made the attempts by changing to numbers 1,2,3 and 4 and none of them recognized the PACLED64 card.

 

But I'm pretty sure that my PACLED64 refers to ID = 1 because in the DirectOutput log file it is identified as ID = 1.

 

I did the tests first with DOF R3 and now I'm with the current version of DOF R3 ++, as directed by DDH69.

 

* Note: I am not making front-end attempts, only with emulators. I tried starting the emulator with the table after that I clicked as administrator in DOFLinx.exe and it generates the error as per the log file.

I did the tests also by clicking DOFLinx.exe directly and the log file remains with the same problem.

All attempts I delete the previously generated log file and end the DOFLinx.exe that is found as "started" through the end task.

 

I need to please someone to orient me what I may be doing wrong, because I do not know where else to find the error. I've done many reinstalls and I did not succeed.     

 

 

_{*The fields in red were the ones I modified according to the ports  of my configtool dof.}

 

DOFLinx.ini

 

####

# The config file for DOFLinx

# A mad idea by DDH69 to have some flipper sounds, RGB display and turn buttons on when playing Pinball FX2 via Steam

# Its grown a lot since that silly start!

# Note - this works with LEDWiz, PacLed64, Pinscape, Ultimate I/O and Sainsmart (FTDI devices)

# Edit this file as you see fit, lines that start with a hash (#) or are blank are not processed.  This blurb and comments can be cut out if you want.

#

# Output devices outputs are entered in the format of

# device (D) and output number (#) in the format D##, so controller device 1 and output 3 is "103" without the quotes, controller board 2 output 23 is "223" without quotes

####

 

# location of your standard DOF outut configuration file.  Keep this as the first item in the file

DIRECTOUTPUTCONFIG=C:\DirectOutput\Config\directoutputconfig20.ini

PATH_FX2=C:\DirectOutput\Config\FX2

PATH_FX3=C:\DirectOutput\Config\FX3

 

 

# If you want to list the processes that will wake up DOFLinx, comment it out if you just want Pinball FX2

PROCESSES=Pinball FX2,Pinball FX3,Future Pinball,VPinball_9_9_1,VPPhysMod5

 

# If you are using flag files, comment the line below out or set to 2000 as the default.

# If you need to use the Pinball FX2 grid to select games you will want this at around 30000 - I recommend not using the FX2 grid

PROCESS_TO_ACTIVE_TIME=1

 

# Which DOF Controller output for the flipper solenoids / contactors

L_FLIPPER_OUTPUT=101

R_FLIPPER_OUTPUT=112

# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx

# Left Shift = A0, Right Shift = A1

L_FLIPPER_KEY=A0

R_FLIPPER_KEY=A1

# Just in case things go wrong (ie no keyup signal is detected, flipper held down for a long time), what is the maximum time a flipper solenoid / contactor can be in in milliseconds

MAX_FLIPPER_ON=5000

# What LEDWiz output(s) are used for RGB devices.  Just enter the Red output number.  Multiples can be entered seperated by a comma

RGB_OUTPUT=133

# Rainbow - cycle through the colours, Random - pick a random next colour, A colour name as it appears in the DirectOutputConfig.ini file

RGB_STYLE=RANDOM

# What changes the colour?  Time - set time period, Flipper = flipper press after the RGB_TRIGGER minimum time (to stop rapid colour changes)

RGB_TRIGGER=FLIPPER

# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips

RGB_MIN_TIME=1000

# The button(s) to turn on when DOFLinx starts, ie the exit button LED

#BUTTONS_ON=142 146

# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121

KEY_TO_OUTPUT=32 101 35 106 36 105 (I did not modify it, because I did not find what it would certainly mean. I left it according to the model)

# Set a key to turn on a specific colour for your RGB.  The line below makes the Left Control (A2) and the Right Control (A3) turn my undercab RGB strip red.

# In Pinball FX2 this means when I nudge it all goes red.

#KEY_TO_COLOUR=A2 133 Red A3 133 Red (I modified it to the red RGB port that was in dofconfigtool. Same port of RGB_OUTPUT)

# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.  Handy for using it for things other than PinBall FX2

FORCE_ACTIVE=0

# If you want the program to stop when your named process stops then set this to 1.  If you want it to run in the background all the time leave it as 0

QUIT_AFTER_PROCESS=0

# Set to 1 to output the game name to the log regardless of the DEBUG flag setting.  Set to 0 to simply follow the DEBUG flag.

# Quite useful when you trying to get the FX2 window game name for setting game specific colours

OUTPUT_GAME_NAME=1

 

####

# Sample setup to enable the Future Pinball Link.  Edit the LINK_ items to be your ports and settings.

####

FP_ATTEMPT_LINK=1

# Use the line below if you need to extend the wait time for a FP table to load

#FP_LINK_WAIT_TIME=60000

LINK_LF=101,50,10000,255

LINK_RF=112,50,10000,255

LINK_LS=102,50,500,255

LINK_RS=111,50,500,255

LINK_ML=103,50,500,255

LINK_MC=104,50,500,255

LINK_MR=105,50,500,255

LINK_BL=106,50,500,255

LINK_BC=107,50,500,255

LINK_BR=108,50,500,255

LINK_SH=113,1000,5000,255

LINK_KN=109,120,500,255

LINK_SR=132,ON,0

LINK_BK=115,ON,0

LINK_FLOL=117

LINK_FLIL=120

LINK_FLCN=123

LINK_FLIR=126

LINK_FLOR=129

LINK_LB=141

LINK_ST=142

LINK_EB=143

LINK_CN=144

LINK_EX=146

LINK_FR=148

 

####

# 0 = OFF (normal operation), 1 = ON - When ON a window will appear and a log file will be created in the EXE directory.

DEBUG=1

 

#####

# Game specific colours in the formnat of a CSV of Game Name,Colour#1,Colour#2 - colours as they appear in your directoutputconfig

# Thanks to Vizzini here is a great starting list for Pinball FX2

#####

GAME_COLOUR=AlienIsolationPinball,Medium_Blue,Lime,Dodger_Blue,Lime_Green

GAME_COLOUR=AlienvsPredatorPinball,Medium_Blue,Lime_Green,Dodger_Blue,Yellow_Green

GAME_COLOUR=AliensPinball,Medium_Blue,Dark_Golden_Rod,Dodger_Blue

GAME_COLOUR=AmericanDadPinball,Medium_Blue,Lime_Green,Dodger_Blue,Yellow_Green

GAME_COLOUR=ArcherPinball,Medium_Blue,Yellow,Dodger_Blue,Blue_Violet

GAME_COLOUR=Biolab,Dark_Red,Lime,Blue,Cyan,Blue_Violet,Yellow

GAME_COLOUR=Blade,Blue,Blue_Violet,Salmon

GAME_COLOUR=BobaFett,Lime,Golden_Rod,Blue_Violet

GAME_COLOUR=BobsBurgersPinball,Medium_Blue,Lime_Green,Dark_Red,Dodger_Blue,Yellow_Green

GAME_COLOUR=CaptainAmerica,Blue,Dark_Red,Dodger_Blue,Gold

GAME_COLOUR=CastleStorm,Blue,Gold,Lime,Dodger_Blue,Orange,Lime_Green

GAME_COLOUR=CivilWar,Blue,Dark_Red,Dodger_Blue,Light_Salmon

GAME_COLOUR=Deadpool,Dark_Red,Blue,Medium_slate_blue,Dodger_Blue

GAME_COLOUR=DoomPinball,Yellow,Silver,Gray,Dark_Orange,Dim_Gray,Orange_Red,Peru,Crimson

GAME_COLOUR=DoctorStrange,Dark_Red,Blue,Gold,Lime_Green,Dark_Violet,Orange,Dodger_Blue,Lime,Medium_Slate_Blue

GAME_COLOUR=EarthDefense,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime

GAME_COLOUR=ElDorado,Orange,Lime_Green,Yellow,Coral,Lime,Yellow_Green,Cyan

GAME_COLOUR=EpicQuest,Lime_Green,Dodger_Blue,Yellow_Green,Cyan

GAME_COLOUR=Excalibur,Dark_Red,Blue,Lime,Dodger_Blue,Cyan

GAME_COLOUR=FalloutPinball,Crimson,White,Red,Brown,Light_Steel_Blue,Slate_Blue

GAME_COLOUR=FamilyGuyPinball,Dodger_Blue,Lime_Green,Salmon,Dark_Violet,Yellow_Green

GAME_COLOUR=FantasticFour,Blue,Yellow,Dodger_Blue,Orange_Red

GAME_COLOUR=FearItself,Dark_Red,Blue,Yellow,Lime,Dark_Violet,Orange

GAME_COLOUR=GhostRider,Dodger_Blue,White,Yellow,Light_Salmon,Orange_Red

GAME_COLOUR=GuardiansoftheGalaxy,Dodger_Blue,Orange,Medium_Purple

GAME_COLOUR=IRONMAN,Blue,Dark_Red,Dodger_Blue,Gold

GAME_COLOUR=Mars,Blue,Yellow,Deep_sky_blue,Gold

GAME_COLOUR=MarvelsAntMan,Medium_Blue,Dark_Red,Dodger_Blue

GAME_COLOUR=MarvelsAvengersAgeofUltron,Dark_Red,Dodger_Blue,Lime_Green,Light_Salmon,Cyan

GAME_COLOUR=MarvelsTheAvengers,Blue,Dark_Red,Dodger_Blue,Gold

GAME_COLOUR=MarvelsWomenofPowerAForce,Red,Lime,Gold,Slate_Blue,Tomato,Silver,Dark_Orchid,Spring_Green

GAME_COLOUR=MarvelsWomenofPowerChampions,Dodger_Blue,Yellow,Red,Gray,Golden_Rod,Crimson,Orange

GAME_COLOUR=MoonKnight,Dodger_Blue,Blue,Cyan,Royal_Blue

GAME_COLOUR=MsSplosionMan,Dodger_Blue,Pink,Medium_Blue,Purple,Royal_Blue

GAME_COLOUR=Paranormal,Lime_Green,Dodger_Blue,Yellow_Green

GAME_COLOUR=Pasha,Dark_Violet,Golden_Rod,Dodger_Blue

GAME_COLOUR=PlantsVSZombies,Lime_Green,Yellow_Green,Dodger_Blue

GAME_COLOUR=Portal,Dodger_Blue,Yellow_Green,Medium_Blue,Yellow

GAME_COLOUR=Rome,Dark_Red,Gold,Dodger_Blue,Light_Salmon,Yellow_Green,Orange

GAME_COLOUR=SecretsoftheDeep,Blue,Yellow,Dodger_Blue

GAME_COLOUR=Shaman,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime

GAME_COLOUR=SorcerersLair,Blue,Blue_Violet,Dodger_Blue,Slate_Blue

GAME_COLOUR=SouthParkButtersVeryOwnPinballGame,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime_Green

GAME_COLOUR=SouthParkSuperSweetPinball,Dark_Red,Lime,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime_Green,Yellow_Green

GAME_COLOUR=SpiderMan,Dark_Red,Lime,Blue,Gold,Dark_Violet,Orange

GAME_COLOUR=STARWARSDARTHVADER,Light_sky_blue,Dark_Red,Cyan

GAME_COLOUR=StarWarsEpisodeVTheEmpireStrikesBack,Medium_Blue,Yellow,Dark_Red,Dodger_Blue

GAME_COLOUR=StarWarsEpisodeVIReturnoftheJedi,Slate_Blue,Golden_Rod,Medium_Blue,Lime_Green,Dodger_Blue,Yellow

GAME_COLOUR=StarWarsPinballDroids,Medium_Blue,Yellow,Orange,Navy,Gold,Orange_Red

GAME_COLOUR=StarWarsPinballEpisodeIVANewHope,Cyan,Golden_Rod,Dodger_Blue,Yellow

GAME_COLOUR=StarWarsPinballHanSolo,Dodger_Blue,Royal_Blue,Antique_White

GAME_COLOUR=StarWarsPinballMastersoftheForce,Medium_Blue,Salmon,Dodger_Blue,Purple,Cyan,Dark_Red

GAME_COLOUR=StarWarsPinballMightoftheFirstOrder,Light_sky_blue,Dodger_Blue,Dark_Red,Cyan

GAME_COLOUR=StarWarsPinballStarWarsRebels,Medium_Blue,Yellow,Royal_Blue,Orange_Red,Purple,Lime_Green

GAME_COLOUR=StarWarsPinballTheForceAwakens,Dark_Red,Medium_Blue,Blue_Violet

GAME_COLOUR=StarWarsPinballRogueOne,Gray,Silver,Light_Sky_Blue,Teal,Beige,Bisque,Aqua_Marine,Slate_Gray,Dark_Orange

GAME_COLOUR=StarWarsStarfighterAssault,Medium_Blue,Dodger_Blue,Dark_Red

GAME_COLOUR=StarWarsTheCloneWars,Dark_Red,Pink,Medium_Blue,Medium_Turquoise,Lime,Lime_Green

GAME_COLOUR=SuperLeagueASRoma,Lime_Green,Orange,Lime,Yellow,Red

GAME_COLOUR=SuperLeagueZenStudiosFC,Lime_Green,Orange,Lime,Yellow,Red

GAME_COLOUR=SuperLeagueArsenalFC,Lime_Green,Orange,Lime,Yellow,Red

GAME_COLOUR=SuperLeagueLiverpoolFC,Lime_Green,Orange,Lime,Yellow,Red

GAME_COLOUR=SuperLeagueJuventus,Lime_Green,Orange,Lime,Yellow,Red

GAME_COLOUR=SuperLeagueACMilan,Lime_Green,Orange,Lime,Yellow,Red

GAME_COLOUR=SuperLeagueRealMadridCF,Lime_Green,Medium_Blue,Lime,Yellow,Red

GAME_COLOUR=SuperLeagueFCBarcelona,Slate_Blue,Lime_Green,Yellow,Blue_Violet,Lime,Red

GAME_COLOUR=Tesla,Lime_Green,Yellow_Green,Dodger_Blue,Golden_Rod

GAME_COLOUR=TheElderScrollsVSkyrimPinball,Light_Slate_Gray,Gold,Golden_Rod,Dark_Sea_Green,Peru,Tan

GAME_COLOUR=TheInfinity Gauntlet,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime

GAME_COLOUR=TheWalkingDead,Lime_Green,Royal_Blue,Yellow_Green

GAME_COLOUR=Thor,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime

GAME_COLOUR=V12,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue

GAME_COLOUR=Venom,Dark_Red,Blue,Dark_Violet,Dodger_Blue

GAME_COLOUR=WildWestRampage,Yellow_Green,Dodger_Blue,Royal_Blue

GAME_COLOUR=Wolverine,Dark_Red,Medium_Blue,Yellow,Dark_Violet

GAME_COLOUR=WorldWarHulk,Lime_Green,Yellow_Green,Dodger_Blue,Lime,Yellow

GAME_COLOUR=XMen,Blue,Blue_Violet,Gold,Dodger_Blue,Slate_Blue,Orange

 

 

Log file DOFLinx.ini

 

10-jun-18 14:51:26.807 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

10-jun-18 14:51:26.857 - Starting up - version 6.27

10-jun-18 14:51:26.863 - For support come and visit the community here http://www.vpforums....p?showforum=104

10-jun-18 14:51:26.945 - 0 Pinscape device(s) found

10-jun-18 14:51:26.996 - 0 LEDWiz device(s) found

10-jun-18 14:51:27.014 - 0 FTDI (Sainsmart) device(s) found

10-jun-18 14:51:27.051 - 0 Ultimate IO device(s) found

10-jun-18 14:51:27.060 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

10-jun-18 14:51:27.070 - Reading DOFLinx.INI startup config file details

10-jun-18 14:51:27.088 - Reading DirectOutputConfig file named C:\DirectOutput\Config\directoutputconfig20.ini

10-jun-18 14:51:27.099 - Error in configuration for  left flipper trying to set device to 1 Needs to be in the range 1-0

 

 

Log file DirectOutput  (where it shows my DOF R3 ++ configuration and identifies PACLED64 as ID = 1)

 

---------------------------------------------------------------------------------

DirectOutput Version 3.1.6656.21457, built 2018.03.23 11:55

MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy

DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput

2018.06.10 12:44:52.634 DirectOutput Logger initialized

2018.06.10 12:44:51.957 Pre-loading DLL Ciloci.Flee.dll from C:\DIRECTOUTPUT\Ciloci.Flee.dll : ok

2018.06.10 12:44:51.991 Pre-loading DLL Extensions.dll from C:\DIRECTOUTPUT\Extensions.dll : ok

2018.06.10 12:44:51.991 Pre-loading DLL FTD2XX32.dll from C:\DIRECTOUTPUT\FTD2XX32.dll : ok

2018.06.10 12:44:51.991 Pre-loading DLL Newtonsoft.Json.dll from C:\DIRECTOUTPUT\Newtonsoft.Json.dll : ok

2018.06.10 12:44:51.992 Pre-loading DLL PacDrive32.dll from C:\DIRECTOUTPUT\PacDrive32.dll : ok

2018.06.10 12:44:51.992 Pre-loading DLL Q42.HueApi.ColorConverters.dll from C:\DIRECTOUTPUT\Q42.HueApi.ColorConverters.dll : ok

2018.06.10 12:44:51.992 Pre-loading DLL Q42.HueApi.dll from C:\DIRECTOUTPUT\Q42.HueApi.dll : ok

2018.06.10 12:44:52.387 Global config filename is "C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml"

2018.06.10 12:44:52.636 Global config loaded from: C:\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml

2018.06.10 12:44:52.636 Loading Pinball parts

2018.06.10 12:44:52.636 Loading cabinet

2018.06.10 12:44:52.637 Will load cabinet config file: C:\DirectOutput\Config\cabinet.xml

2018.06.10 12:44:53.105 1 output controller defnitions and 3 toy definitions loaded from cabinet config.

2018.06.10 12:44:53.105 Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.

2018.06.10 12:44:53.105 Cabinet auto configuration started

2018.06.10 12:44:53.209 Detected and added PacLed64 Id 1 with name PacLed64 1

2018.06.10 12:44:53.210 Added LedwizEquivalent Nr. 20 with name PacLed64 1 Equivalent 1 for PacLed64 with Id 1

2018.06.10 12:44:53.212 PacDriveSingleton.PacUIOGetIdList: i=0, numdevices=1, DeviceType=PacLED64

2018.06.10 12:44:53.214 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)

2018.06.10 12:44:53.231 Cabinet auto configuration finished

2018.06.10 12:44:53.231 Autoconfig complete.

2018.06.10 12:44:53.231 Cabinet config loaded successfully from C:\DirectOutput\Config\cabinet.xml

2018.06.10 12:44:53.231 Cabinet loaded

2018.06.10 12:44:53.231 Loading table config

2018.06.10 12:44:53.232 Warning: No table config file found. Will try to load config from LedControl file(s).

2018.06.10 12:44:53.233 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName bttf_a27

2018.06.10 12:44:53.238 Loading LedControl file C:\DIRECTOUTPUT\config\directoutputconfig20.ini

2018.06.10 12:44:53.246 Min DOF Version is 0.8 for file directoutputconfig20.ini

2018.06.10 12:44:53.627 Loading LedControl file C:\DIRECTOUTPUT\config\directoutputconfig30.ini

2018.06.10 12:44:53.633 Min DOF Version is 0.8 for file directoutputconfig30.ini

2018.06.10 12:44:53.872 2 directoutputconfig.ini or ledcontrol.ini files loaded.

2018.06.10 12:44:53.873 Config for RomName bttf_a27 exists in LedControl data. Updating cabinet and config.

2018.06.10 12:44:53.908 Table config loading finished: romname=bttf_a27, tablename=Back to the Future (Data East 1990)

2018.06.10 12:44:53.909 Pinball parts loaded

2018.06.10 12:44:53.909 Starting processes

2018.06.10 12:44:53.909 Initializing cabinet

2018.06.10 12:44:53.909 Debug: Initializing output controllers

2018.06.10 12:44:53.919 TeensyStripController TeensyStripController intialized and updater thread started.

2018.06.10 12:44:53.921 PacLed64 Id:1 initialized and updater thread started.

2018.06.10 12:44:53.921 Debug: Output controllers initialized

2018.06.10 12:44:53.923 TeensyStripController TeensyStripController updater thread  started.

2018.06.10 12:44:53.927 Cabinet initialized

2018.06.10 12:44:53.930 Loading shape definition file: C:\DIRECTOUTPUT\config\DirectOutputShapes.xml

2018.06.10 12:44:53.964 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.964 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.964 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.964 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.964 Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:85, W:100, H:15), Matrix(W:156, H:1), ResultArea(Left: 0, Top:132, Right:0, Bottom:155, Width:1, Height:24)

2018.06.10 12:44:53.965 Debug: MatrixBase for RGBAMatrixShiftEffect. Calculated area size: AreaDef(L:0, T:85, W:100, H:15), Matrix(W:156, H:1), ResultArea(Left: 0, Top:132, Right:0, Bottom:155, Width:1, Height:24)

2018.06.10 12:44:53.965 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.965 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.965 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.965 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.965 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.965 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.966 Debug: MatrixBase for RGBAMatrixColorEffect. Calculated area size: AreaDef(L:0, T:0, W:100, H:12), Matrix(W:156, H:1), ResultArea(Left: 0, Top:0, Right:0, Bottom:18, Width:1, Height:19)

2018.06.10 12:44:53.977 Framework initialized.

2018.06.10 12:44:53.977 Have fun!

2018.06.10 12:44:54.042 TeensyStripController TeensyStripController updater thread  has connected to TeensyStripController TeensyStripController.

2018.06.10 12:45:07.595 Finishing framework

2018.06.10 12:45:07.596 Finishing cabinet

2018.06.10 12:45:07.597 Debug: Finishing output controllers

2018.06.10 12:45:07.611 TeensyStripController TeensyStripController updater thread  has disconnected from TeensyStripController TeensyStripController and will terminate.

2018.06.10 12:45:07.611 TeensyStripController TeensyStripController finished and updater thread stopped.

2018.06.10 12:45:08.823 PacLed64 Id:1 finished and updater thread stopped.

2018.06.10 12:45:08.823 Debug: Output controllers finished

2018.06.10 12:45:08.823 Cabinet finished

2018.06.10 12:45:08.823 DirectOutput framework finished.

2018.06.10 12:45:08.823 Bye and thanks for using!

 

 

 

[Outhere]

Make a shortcut for DOFLinx.exe, Right click the shortcut go to properties, Go to the shortcut tab, In the target line try this..

Add to the end of the target line PACLED64=1

"C:\DirectOutput\DOFLinx.exe" PACLED64=1

Also you will need add this to the end of these lines -> \

PATH_FX2=C:\DirectOutput\Config\FX2\

PATH_FX3=C:\DirectOutput\Config\FX3\

[thiago capalbo]

Thanks for your return Outhere!

 

I did the tests you mentioned and unfortunately the error in the log file remains the same.   

 

Would you have any other ideas on how you could recognize pacled64?

 

 

 

Make a shortcut for DOFLinx.exe, Right click the shortcut go to properties, Go to the shortcut tab, In the target line try this..

Add to the end of the target line PACLED64=1

"C:\DirectOutput\DOFLinx.exe" PACLED64=1

Also you will need add this to the end of these lines -> \

PATH_FX2=C:\DirectOutput\Config\FX2\

PATH_FX3=C:\DirectOutput\Config\FX3\

 

[DDH69]

outhere's advice is correct, but clearly didn't get you a result.

 

Until we get DOFLinx to recognise your PacLED64 everything else like INI files, etc is irrelevant.

 

Your correct shortcut is the top one;

C:\DirectOutput\DOFLinx.exe PACLED64=1 PATH_INI=C:\DirectOutput\DOFLinx.ini

Is this the one you modified with 2,3 , and 4?  As you said, it is most likely ID#1, 99% are and it makes sense when you have only one device.

 

The issue is definitely still in your command line argument somehow.  Perhaps zip and attach your shortcut for DOFLinx. - my strongest belief is this is where the problem is.

 

What you should see is below.  I've just given it a try here.  If you have the command line correct you will get more messages that you are currently seeing regardless of a device being found.

 

11-Jun-18 11:51:15.783 - DOFLinx device: 1 Initialising as PacLed64 #1
11-Jun-18 11:51:15.803 - DOFLinx device:1 PacLed64 setup with 64 outputs

Other than success outputs there is little logging as the PacLED64 is setup because I've never needed it!  I'll add a couple of extra debug messages and PM you a test DOFLinx version.  At least we can then see if you are adding the ID# to the PacLED64 search array internally and what DOF itself is returning.  When you get a log file from the test version just post it back in this thread, then everyone can have a look and help as possible.

 

Don't worry - we'll figure this out.

 

[thiago capalbo]

Many thanks for your DDH69 return!

 

I also think Outhere advice is correct, but I can not understand why my PACLED64 is not being recognized only in DOFLinx.

 

This log file below is in relation to the new tests that I did with the version that you sent me via PM.

 

It was exactly with this command line in the shortcut that I modified the line PACLED64 = 1 to 1,2,3 and 4 and all were the same log result.

 

I do not know if I can be creating the shortcut in the wrong way, but I do not think it is.

 

I right-click on DOFLinx.exe and go to the Create Shortcut option and it creates a shortcut in the C: \ DirectOutput folder itself. I cut this shortcut (Control + X), go to Win + R in shortcut start-up folder, and paste this shortcut into this folder.

After that, I right click and go to properties and put this command line that you reported (exactly as it is). I just modified the numbers to 1,2,3 and 4 during the tests to verify if I was locating my PACLED64. But unfortunately, with no success in all attempts.

 

I just do not understand what you said about the issue of doing the zip test.

 

But I made an attempt with the zipped folder to rule out the hypothesis. But in the destination of the shortcut the file will be like .rar, being not possible to save the command line in .exe.

 

And if I click directly on the .exe file with it in zip the program does not work and does not do any log file.

 

I do not know if it would be this way that you asked me to test. But beyond the standard attempts of your step by step, I also made this attempt with the zip file.

 

Below is the log file that appeared in all attempts.

 

In the log file it seems that no DOF Config file was found. But I think this is because DOFLinx is not able to find PACLED64 because the directoutput20.ini file is correctly referenced in the DOFLinx.ini file.

 

I really can not find any other alternative. Because my computer skills are limited to think of a more thorough solution and I need a lot of guidance from you how I can solve this.

 

Thank you immensely for your help and if you have any new ideas, please let me know, because I really want to see it all working and I really need your help.

 

See what you think about the log file I've attached below.

 

Wish you a great day!

Cheers

 

 

Log File DOFLinx v6.30 Beta 3

 

11-jun-18 13:30:07.408 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

11-jun-18 13:30:07.449 - Starting up - version 6.30 Beta 3

11-jun-18 13:30:07.457 - For support come and visit the community here http://www.vpforums....p?showforum=104

11-jun-18 13:30:07.466 - Pre-Reading DOFLinx.INI startup config file details

11-jun-18 13:30:07.530 - No DOF Global Config file supplied

11-jun-18 13:30:07.591 - 0 Pinscape device(s) found

11-jun-18 13:30:07.604 - 0 LEDWiz device(s) found

11-jun-18 13:30:07.611 - 0 FTDI (Sainsmart) device(s) found

11-jun-18 13:30:07.626 - 0 Ultimate IO device(s) found

11-jun-18 13:30:07.631 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

11-jun-18 13:30:07.638 - Reading DOFLinx.INI startup config file details

11-jun-18 13:30:07.644 - Reading DirectOutputConfig file named C:\DirectOutput\Config\directoutputconfig20.ini

11-jun-18 13:30:07.656 - Error in configuration for  left flipper trying to set device to 1 Needs to be in the range 1-0

11-jun-18 13:30:09.569 - 0 Pinscape device(s) found

11-jun-18 13:30:09.575 - 0 LEDWiz device(s) found

11-jun-18 13:30:09.581 - 0 FTDI (Sainsmart) device(s) found

11-jun-18 13:30:09.588 - 0 Ultimate IO device(s) found

11-jun-18 13:30:09.595 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

11-jun-18 13:30:13.515 - Shutting down

11-jun-18 13:30:13.528 - Program close

 

outhere's advice is correct, but clearly didn't get you a result.

 

Until we get DOFLinx to recognise your PacLED64 everything else like INI files, etc is irrelevant.

 

Your correct shortcut is the top one;

C:\DirectOutput\DOFLinx.exe PACLED64=1 PATH_INI=C:\DirectOutput\DOFLinx.ini

Is this the one you modified with 2,3 , and 4?  As you said, it is most likely ID#1, 99% are and it makes sense when you have only one device.

 

The issue is definitely still in your command line argument somehow.  Perhaps zip and attach your shortcut for DOFLinx. - my strongest belief is this is where the problem is.

 

What you should see is below.  I've just given it a try here.  If you have the command line correct you will get more messages that you are currently seeing regardless of a device being found.

 

11-Jun-18 11:51:15.783 - DOFLinx device: 1 Initialising as PacLed64 #1
11-Jun-18 11:51:15.803 - DOFLinx device:1 PacLed64 setup with 64 outputs

Other than success outputs there is little logging as the PacLED64 is setup because I've never needed it!  I'll add a couple of extra debug messages and PM you a test DOFLinx version.  At least we can then see if you are adding the ID# to the PacLED64 search array internally and what DOF itself is returning.  When you get a log file from the test version just post it back in this thread, then everyone can have a look and help as possible.

 

Don't worry - we'll figure this out.

 

[DDH69]

One of the log messages I added was to show if a command line parameter of PACLED64=1 was being picked up.  The absence of a message in log tells me that it is not.  So I still believe your issue is the shortcut and command line parameter.  Can you please send your shortcut file.

[thiago capalbo]

I can not send the shortcut file you requested or images to you. 

 

Is it because I'm not currently signed in vpforum?

 

If not, and to expedite your request I could already send you the DOFLinx.exe file from my initialization folder and images from the DirectOutput folders in another way for you to take a lookup (email or something similar)?

 

I do not know if it could be this way or it would be a nuisance for you.

 

If this is possible send me the address via PM that will send you immediately.

 

Just to expedite the sending of the file and the images.

 

Well with regards to the posting of files and images here I am verifying if it is for the issue of the signature, and if that is why, I intend to solve this question as soon as possible.

 

Let me know if this is not uncomfortable for you!

 

Sorry about anything.

 

I look forward to your return and thank you immensely!

 

Thanks again!

 

One of the log messages I added was to show if a command line parameter of PACLED64=1 was being picked up.  The absence of a message in log tells me that it is not.  So I still believe your issue is the shortcut and command line parameter.  Can you please send your shortcut file.

[DDH69]

Just place the shortcut on your favourite file share and post a public link to download.

[thiago capalbo]

Hello DDH69,

 

I generated the files via google drive for download.

 

It was the easiest way I found it.

 

I am forwarding to download the file of my DOFLinx.exe shortcut and also the "print" screens of my folders.

 

See if you can help me solve the problem.

 

I apologize for the inconvenience.

 

Please check and let me know what you think is wrong about my setup.

 

Follow the link: 

 

https://drive.google...hVCx25yJ-ktWXvb

 

Cheers! 

 

Just place the shortcut on your favourite file share and post a public link to download.

[DDH69]

Using your shortcut I get the following log

 

13-Jun-18 19:37:34.069 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
13-Jun-18 19:37:34.085 - Starting up - version 6.30 Beta 3
13-Jun-18 19:37:34.100 - For support come and visit the community here http://www.vpforums.org/index.php?showforum=104
13-Jun-18 19:37:34.100 - Adding PacLed64 ID# 1 to the search list
13-Jun-18 19:37:34.116 - Pre-Reading DOFLinx.INI startup config file details
13-Jun-18 19:37:36.038 - Found Teensy controller named 'TeensyStripController'
13-Jun-18 19:37:36.053 - Found ArtNet controller named 'Artnet Node 1'
13-Jun-18 19:37:36.069 - 0 Pinscape device(s) found
13-Jun-18 19:37:36.085 - 0 LEDWiz device(s) found
13-Jun-18 19:37:36.100 - 0 FTDI (Sainsmart) device(s) found
13-Jun-18 19:37:36.100 - DOFLinx device: 1 Initialising as PacLed64 #1
13-Jun-18 19:37:36.116 - DOFLinx device:1 PacLed64 setup with 64 outputs
13-Jun-18 19:37:36.131 - 0 Ultimate IO device(s) found
13-Jun-18 19:37:36.147 - DOFLinx device:2 PinControl2 setup
13-Jun-18 19:37:37.147 - PinControl2 at address 192.168.178.50 DID NOT responded
13-Jun-18 19:37:37.147 - Reading DOFLinx.INI startup config file details
13-Jun-18 19:37:37.163 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini
13-Jun-18 19:37:38.053 - 0 Pinscape device(s) found
13-Jun-18 19:37:38.069 - 0 LEDWiz device(s) found
13-Jun-18 19:37:38.069 - 0 FTDI (Sainsmart) device(s) found
13-Jun-18 19:37:38.085 - DOFLinx device: 1 Initialising as PacLed64 #1
13-Jun-18 19:37:38.116 - DOFLinx device:1 PacLed64 setup with 64 outputs
13-Jun-18 19:37:38.116 - 0 Ultimate IO device(s) found
13-Jun-18 19:37:38.131 - DOFLinx device:2 PinControl2 setup
13-Jun-18 19:37:39.147 - PinControl2 at address 192.168.178.50 DID NOT responded
13-Jun-18 19:37:42.288 - Shutting down
13-Jun-18 19:37:43.319 - Program close

The first orange line is when DOFLinx processes the command line argument.  You can physically remove / disconnect the PacLED64 device and still get this.  This line is not in your log.  Are you sure you are starting DOFLinx using the shortcut you sent?  Given your shortcut works, you have some other basic Windows / startup issue.  Are you trying to run this manually, ie double clicking on your shortcut?

[thiago capalbo]

Hello DDH69,

 

I ran new tests and attached new files to my google drive for you to take a look.

 

I'll answer all your questions.

 

Are you sure you are starting DOFLinx using the shortcut you sent?  - It's exactly this shortcut I'm using. I made a shortcut according to the DOFLinx version that you forwarded me via PM.

 

Given your shortcut works, you have some other basic Windows / startup issue.   - In fact I do not know if I have a problem between the initialization of my Windows and DOFlinx, but as you can see in the image that I sent you now, it is enabled to perform the startup along with windows, but I do not know where and how to verify for sure if this is really working.

 

Are you trying to run this manually, ie double clicking on your shortcut? - I was doing a double click on DOFLinx.exe directly in the folder it is in C: / DirectOutput. But now you have asked me this question of double clicking directly on the shortcut. And it seems to me that now PACLED64 has been recognized!    

 

Does this sound like great news, or am I mistaken?

 

But on the other hand this is appearing another error and from what I understand is something related to my Strobe, but according to my configuration in dofconfigtool the port is correct. 

I've forwarded a photo of my DOF setup for you to take a look at.

 

It seems to me that we are moving towards a great victory.

 

Let me know if this new log file represents good results and if you have any idea of ​​the next step I should take to solve this.

 

Thank you very much so far

 

Cheers 

 

https://drive.google...Eqk22UOhJDwQ2Md

 

 

 

DOFLinx - log file

 

13-jun-18 13:20:23.500 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

13-jun-18 13:20:23.509 - Starting up - version 6.30 Beta 3

13-jun-18 13:20:23.516 - For support come and visit the community here http://www.vpforums....p?showforum=104

13-jun-18 13:20:23.524 - Adding PacLed64 ID# 1 to the search list

13-jun-18 13:20:23.531 - Pre-Reading DOFLinx.INI startup config file details

13-jun-18 13:20:23.566 - No DOF Global Config file supplied

13-jun-18 13:20:23.588 - 0 Pinscape device(s) found

13-jun-18 13:20:23.601 - 0 LEDWiz device(s) found

13-jun-18 13:20:23.608 - 0 FTDI (Sainsmart) device(s) found

13-jun-18 13:20:23.615 - DOFLinx device: 1 Initialising as PacLed64 #1

13-jun-18 13:20:23.629 - DOFLinx device:1 PacLed64 setup with 64 outputs

13-jun-18 13:20:23.637 - 0 Ultimate IO device(s) found

13-jun-18 13:20:23.647 - Reading DOFLinx.INI startup config file details

13-jun-18 13:20:23.654 - Reading DirectOutputConfig file named C:\DirectOutput\Config\directoutputconfig20.ini

13-jun-18 13:20:23.669 - Parameter data failed for LINK_SR with System.IndexOutOfRangeException: O índice estava fora dos limites da matriz.

   em DOFLinx.MainForm.LoadLinkDevice(Byte DeviceKey, String InData, Boolean RGBItem)

   em DOFLinx.MainForm.ProcessParameter(String TheParam, String TheData, Boolean Realtime)

13-jun-18 13:20:25.578 - 0 Pinscape device(s) found

13-jun-18 13:20:25.586 - 0 LEDWiz device(s) found

13-jun-18 13:20:25.593 - 0 FTDI (Sainsmart) device(s) found

13-jun-18 13:20:25.602 - DOFLinx device: 1 Initialising as PacLed64 #1

13-jun-18 13:20:25.609 - DOFLinx device:1 PacLed64 setup with 64 outputs

13-jun-18 13:20:25.618 - 0 Ultimate IO device(s) found

13-jun-18 13:34:20.816 - Shutting down

13-jun-18 13:34:21.056 - Program close

 

 

Using your shortcut I get the following log

 

13-Jun-18 19:37:34.069 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
13-Jun-18 19:37:34.085 - Starting up - version 6.30 Beta 3
13-Jun-18 19:37:34.100 - For support come and visit the community here http://www.vpforums.org/index.php?showforum=104
13-Jun-18 19:37:34.100 - Adding PacLed64 ID# 1 to the search list
13-Jun-18 19:37:34.116 - Pre-Reading DOFLinx.INI startup config file details
13-Jun-18 19:37:36.038 - Found Teensy controller named 'TeensyStripController'
13-Jun-18 19:37:36.053 - Found ArtNet controller named 'Artnet Node 1'
13-Jun-18 19:37:36.069 - 0 Pinscape device(s) found
13-Jun-18 19:37:36.085 - 0 LEDWiz device(s) found
13-Jun-18 19:37:36.100 - 0 FTDI (Sainsmart) device(s) found
13-Jun-18 19:37:36.100 - DOFLinx device: 1 Initialising as PacLed64 #1
13-Jun-18 19:37:36.116 - DOFLinx device:1 PacLed64 setup with 64 outputs
13-Jun-18 19:37:36.131 - 0 Ultimate IO device(s) found
13-Jun-18 19:37:36.147 - DOFLinx device:2 PinControl2 setup
13-Jun-18 19:37:37.147 - PinControl2 at address 192.168.178.50 DID NOT responded
13-Jun-18 19:37:37.147 - Reading DOFLinx.INI startup config file details
13-Jun-18 19:37:37.163 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini
13-Jun-18 19:37:38.053 - 0 Pinscape device(s) found
13-Jun-18 19:37:38.069 - 0 LEDWiz device(s) found
13-Jun-18 19:37:38.069 - 0 FTDI (Sainsmart) device(s) found
13-Jun-18 19:37:38.085 - DOFLinx device: 1 Initialising as PacLed64 #1
13-Jun-18 19:37:38.116 - DOFLinx device:1 PacLed64 setup with 64 outputs
13-Jun-18 19:37:38.116 - 0 Ultimate IO device(s) found
13-Jun-18 19:37:38.131 - DOFLinx device:2 PinControl2 setup
13-Jun-18 19:37:39.147 - PinControl2 at address 192.168.178.50 DID NOT responded
13-Jun-18 19:37:42.288 - Shutting down
13-Jun-18 19:37:43.319 - Program close

The first orange line is when DOFLinx processes the command line argument.  You can physically remove / disconnect the PacLED64 device and still get this.  This line is not in your log.  Are you sure you are starting DOFLinx using the shortcut you sent?  Given your shortcut works, you have some other basic Windows / startup issue.  Are you trying to run this manually, ie double clicking on your shortcut?

 

[Outhere]

Try adding this to the line in the ini file

,255

[DDH69]

Great progress!  @outhere has you covered.

[thiago capalbo]

Hello DDH69 and Outhere,

 

It took me a while to get back because I was making all the attempts and tests before I came to post the results for you.

 

I think I have some great news today ....

It looks like I have DOFLinx working with FX3 !!!

 

It's such a good feeling that I do not know how to explain .... I have so much to thank you!

 

In fact I still have some problems in the operation, but DOFLinx already gave a great sign of life with the kit of zeb, and for me this was already a big step.

 

I will report some problems that are occurring during the course of the operation, okay?  

 

FX3 - When starting the table, if it starts very fast until DOFLinx loads, FX3 hangs giving a small "BUG", and I need to leave the table until DOFLinx fully loads.

With regard to toys, most of the toys are working, except for the strobe, beacons and only the launch button turns on the light, the other buttons are not giving any sign of life. 

My fan is turning off at the moment, but it's because I've put the # option while it's off.

 

FX2 (non steam version) and Future Pinball - only the right and left flipper solenoids (L and R) and the undercab strips work. The rest, nothing works. No solenoids, flashers, strobe, buttons and adressable leds.

 

I had to change some data from my DOFLinx.ini to make the side addressable leds work. For this I adopted a model configuration of Terry and modified according to my doors. And in AUTO_MX it was set to 0. Because I tested it by setting it to 1, my side stripes were crazy.

 

I have some doubts about all this. Could you clarify? 

 

- How do I make FX3 toys work from other emulators that are not running?

- How do I know that my setup is working properly? Could you guys take a look at my setup and my log file? (link below)

- How DOFLinx should work from the moment I start my pincab, because even though it is activated in a shortcut in the startup folder, I realize it goes into operation only after clicking twice on its shortcut. And my intention is that after it starts up as soon as I boot my pincab, as soon as I finish setting up my pincab correctly I plan not to have to use keyboard and mouse to activate DOFLinx before any game that it is used.

 

Thank you very much for your great help. And hopefully soon see everything working in sync like an orchestra. 

 

https://drive.google...RE7x2WxD4829lAl

 

Cheers!

 

Great progress!  @outhere has you covered.

 

Try adding this to the line in the ini file

,255

[DDH69]

- How do I make FX3 toys work from other emulators that are not running?

I presume the other emulator is FP. 

There are two types of tables in FP that DOFLinx handles.  Regular FP tables - for these you just get flippers, just as you have achieved.  There are also tables that have been modified with DOFLinx code - for these you will get whatever effects the author added.

From the log you provided it looks like you are not running a DOFLinx enabled FP table.  Locate one on this site and load it up.  Ideally you load it via a front end menu or command line as you want the table to load straight away, the delay of navigating the FP menu will allow DOFLinx to timieout.  You can exptend the timeout in DOFLinx if you really need to.

 

- How do I know that my setup is working properly? Could you guys take a look at my setup and my log file? (link below)

It looks fine.  IF your devices are firing when using FX3 the output side is working.  Just setup your strobe when you're ready.

 

- How DOFLinx should work from the moment I start my pincab, because even though it is activated in a shortcut in the startup folder, I realize it goes into operation only after clicking twice on its shortcut. And my intention is that after it starts up as soon as I boot my pincab, as soon as I finish setting up my pincab correctly I plan not to have to use keyboard and mouse to activate DOFLinx before any game that it is used.

It is best to start DOFLinx when your cabinet starts up.  This is best achieved by placing the DOFLinx shortcut in your Windows startup folder.  DOFLinx will then just sit there quietly until an emulator you have it monitoring starts.  Doing this avoids any emulator startup timing.

 

 

I am glad to hear that things are going well.  I suggest getting FX3 fully working with all of your toys, then move on the FP.

[thiago capalbo]

Thanks DDH69 for the return,

 

His guidance was a great satisfaction to me.

 

I'm going to follow your advice and first I want to see FX3 all synchronized for only after continuing with the FP configuration.

 

I still have a little doubt that I still can not solve.if possible, you could try to clarify? I promise not to inconvenience you any more. 

 

As you said about the strobe and the other toys below are the ones that seem to me not to be working, although all the doors are configured correctly.

Is there something I need to turn them on or fix them in this setting for this?

 

LINK_SR=132,ON,0,255

LINK_BK=115,ON,0,255

 

LINK_SH=113,1000,5000,255

LINK_KN=109,120,500,255

 

My buttons also only light up the Launch button. Can I have something wrong with that?

Well, my question is a bit of a beginner, but I'd like to know ... In FX3, the correct configuration of the button ports would have to light up the other buttons configured in the .ini file (Extra button, start, exit, coin ...) or only Launch Button?

 

Thank you for your attention and your efforts to help me.

 

Cheers

 

 

- How do I make FX3 toys work from other emulators that are not running?

I presume the other emulator is FP. 

There are two types of tables in FP that DOFLinx handles.  Regular FP tables - for these you just get flippers, just as you have achieved.  There are also tables that have been modified with DOFLinx code - for these you will get whatever effects the author added.

From the log you provided it looks like you are not running a DOFLinx enabled FP table.  Locate one on this site and load it up.  Ideally you load it via a front end menu or command line as you want the table to load straight away, the delay of navigating the FP menu will allow DOFLinx to timieout.  You can exptend the timeout in DOFLinx if you really need to.

 

- How do I know that my setup is working properly? Could you guys take a look at my setup and my log file? (link below)

It looks fine.  IF your devices are firing when using FX3 the output side is working.  Just setup your strobe when you're ready.

 

- How DOFLinx should work from the moment I start my pincab, because even though it is activated in a shortcut in the startup folder, I realize it goes into operation only after clicking twice on its shortcut. And my intention is that after it starts up as soon as I boot my pincab, as soon as I finish setting up my pincab correctly I plan not to have to use keyboard and mouse to activate DOFLinx before any game that it is used.

It is best to start DOFLinx when your cabinet starts up.  This is best achieved by placing the DOFLinx shortcut in your Windows startup folder.  DOFLinx will then just sit there quietly until an emulator you have it monitoring starts.  Doing this avoids any emulator startup timing.

 

 

I am glad to hear that things are going well.  I suggest getting FX3 fully working with all of your toys, then move on the FP.

 

Edited by thiago capalbo, 15 June 2018 - 05:48 PM.

[Outhere]

With the debug window open - right click the window...

Brings up small test Menu.. In some cases you have to click on the fake emulation on, depending on your setup Before the menu will come up and then you can test your items..

-

Not every game will use all the DOF options

[DDH69]

More good advice from outhere, particularly the last line.

 

With the debug window open - right click the window...

Brings up small test Menu.. In some cases you have to click on the fake emulation on, depending on your setup Before the menu will come up and then you can test your items..

-

Not every game will use all the DOF options

 

Knocker (KN) is used in

AliensPinball.FX3

 

Shaker (SH) is  used in

AdventureLand.FX3

AlienIsolationPinball.FX3

AliensPinball.FX3

AlienvsPredatorPinball.FX3

AmericanDadPinball.FX3

ArcherPinball.FX3

BackToTheFuture.FX3

Biolab.FX3

Blade.FX3

BobaFett.FX3

BobsBurgersPinball.FX3

CaptainAmerica.FX3

CastleStorm.FX3

CivilWar.FX3

Deadpool.FX3

DEFAULT.FX3

DoctorStrange.FX3

DOOMPinball.FX3

EarthDefense.FX3

ET.FX3

Excalibur.FX3

FalloutPinball.FX3

FamilyGuyPinball.FX3

FantasticFour.FX3

FearItself.FX3

GhostRider.FX3

GuardiansoftheGalaxy.FX3

Jaws.FX3

JurassicMayhem.FX3

JurassicPark.FX3

JurassicWorld.FX3

Mars.FX3

MarvelsAntMan.FX3

MarvelsAvengersAgeofUltron.FX3

MarvelsTheAvengers.FX3

MarvelsWomenofPowerAForce.FX3

MarvelsWomenofPowerChampions.FX3

MoonKnight.FX3

Paranormal.FX3

Portal.FX3

SecretsoftheDeep.FX3

SonOfZeus.FX3

SpiderMan.FX3

StarWarsAhchToIsland.FX3

STARWARSDARTHVADER.FX3

StarWarsEpisodeVTheEmpireStrikesBack.FX3

StarWarsLastJedi.FX3

StarWarsPinballEpisodeIVANewHope.FX3

StarWarsPinballMightoftheFirstOrder.FX3

StarWarsPinballRogueOne.FX3

StarWarsPinballStarWarsRebels.FX3

StarWarsPinballTheForceAwakens.FX3

StarWarsStarfighterAssault.FX3

StarWarsTheCloneWars.FX3

Tesla.FX3

TheElderScrollsVSkyrimPinball.FX3

TheInfinityGauntlet.FX3

TheWalkingDead.FX3

Thor.FX3

Venom.FX3

Wolverine.FX3

WorldWarHulk.FX3

 

Beacon (BK) is used in

AdventureLand.FX3

AlienIsolationPinball.FX3

AliensPinball.FX3

AlienvsPredatorPinball.FX3

All.FX3

AmericanDadPinball.FX3

ArcherPinball.FX3

BackToTheFuture.FX3

Biolab.FX3

Blade.FX3

BobaFett.FX3

BobsBurgersPinball.FX3

CaptainAmerica.FX3

CastleStorm.FX3

CivilWar.FX3

Deadpool.FX3

DEFAULT.FX3

DoctorStrange.FX3

DOOMPinball.FX3

EarthDefense.FX3

ET.FX3

Excalibur.FX3

FalloutPinball.FX3

FamilyGuyPinball.FX3

FantasticFour.FX3

FearItself.FX3

GhostRider.FX3

GuardiansoftheGalaxy.FX3

Jaws.FX3

JurassicMayhem.FX3

JurassicPark.FX3

JurassicWorld.FX3

Mars.FX3

MarvelsAntMan.FX3

MarvelsAvengersAgeofUltron.FX3

MarvelsTheAvengers.FX3

MarvelsWomenofPowerAForce.FX3

MarvelsWomenofPowerChampions.FX3

MoonKnight.FX3

Paranormal.FX3

Portal.FX3

SecretsoftheDeep.FX3

SonOfZeus.FX3

SpiderMan.FX3

StarWarsAhchToIsland.FX3

STARWARSDARTHVADER.FX3

StarWarsEpisodeVTheEmpireStrikesBack.FX3

StarWarsLastJedi.FX3

StarWarsPinballEpisodeIVANewHope.FX3

StarWarsPinballMightoftheFirstOrder.FX3

StarWarsPinballRogueOne.FX3

StarWarsPinballStarWarsRebels.FX3

StarWarsPinballTheForceAwakens.FX3

StarWarsStarfighterAssault.FX3

StarWarsTheCloneWars.FX3

Tesla.FX3

TheElderScrollsVSkyrimPinball.FX3

TheInfinityGauntlet.FX3

TheWalkingDead.FX3

Thor.FX3

Venom.FX3

Wolverine.FX3

WorldWarHulk.FX3

 

Strobe (SR) is used in

AdventureLand.FX3

AlienIsolationPinball.FX3

AliensPinball.FX3

AlienvsPredatorPinball.FX3

All.FX3

AmericanDadPinball.FX3

ArcherPinball.FX3

BackToTheFuture.FX3

Biolab.FX3

Blade.FX3

BobaFett.FX3

BobsBurgersPinball.FX3

CaptainAmerica.FX3

CastleStorm.FX3

CivilWar.FX3

Deadpool.FX3

DEFAULT.FX3

DoctorStrange.FX3

DOOMPinball.FX3

EarthDefense.FX3

ET.FX3

Excalibur.FX3

FalloutPinball.FX3

FamilyGuyPinball.FX3

FantasticFour.FX3

FearItself.FX3

GhostRider.FX3

GuardiansoftheGalaxy.FX3

Jaws.FX3

JurassicMayhem.FX3

JurassicPark.FX3

JurassicWorld.FX3

Mars.FX3

MarvelsAntMan.FX3

MarvelsAvengersAgeofUltron.FX3

MarvelsTheAvengers.FX3

MarvelsWomenofPowerAForce.FX3

MarvelsWomenofPowerChampions.FX3

MoonKnight.FX3

Paranormal.FX3

Portal.FX3

SecretsoftheDeep.FX3

SonOfZeus.FX3

SpiderMan.FX3

StarWarsAhchToIsland.FX3

STARWARSDARTHVADER.FX3

StarWarsEpisodeVTheEmpireStrikesBack.FX3

StarWarsLastJedi.FX3

StarWarsPinballEpisodeIVANewHope.FX3

StarWarsPinballMightoftheFirstOrder.FX3

StarWarsPinballRogueOne.FX3

StarWarsPinballStarWarsRebels.FX3

StarWarsPinballTheForceAwakens.FX3

StarWarsStarfighterAssault.FX3

StarWarsTheCloneWars.FX3

Tesla.FX3

TheElderScrollsVSkyrimPinball.FX3

TheInfinityGauntlet.FX3

TheWalkingDead.FX3

Thor.FX3

Venom.FX3

Wolverine.FX3

WorldWarHulk.FX3

 

So, for the most toys try Aliens and see if you can trigger them all !

You can trigger the shaker with left, right or forward nudge.

 

The only button controlled from FX3 files if BUT_LB - Launch Ball - thins comes on when the ball is in the launch lane.  I don't even have this button because I use a plunger.  Any other buttons being lit up when FX3 activates DOFLinx are really decorative for your own enjoyment.  IT really depends what you have them mapped to do within the FX3 emulator.

 

If you look in the "Sample INI folder" in the DOFLinx distribution you will see two sample file for FX3 to turn on / off button action, ie "SUP-Pinball FX3 ON - setup keys to turn on LEDs in buttons".  These are from my configuration.  What this does is make the button light when its pressed giving a fun effect.  I use an ON and OFF SUP file in DOFLinx because I only want this action within FX3, not any other emulator.  This means I use a Launch Before and Launch after command to run these SUP files via DOFLinxMsg.  I just looked and there is no image for PinballX setup of FX3 in the DOFLinx guide.  I have now added one, here is a link to it.

 

 

 

While you keep trying to help yourself and posting meaningful material, we will continue to help you.

[thiago capalbo]

Thanks for the return DDH69 and Outhere,

 

For me it's very strange as I run the tests for each port through the DOFLinx debugging window and everything seems to work.

 

I tested the table Aliens and Portal, and my beacon, and strobe still do not work.

 

Regarding the shaker and other buttons I understood what DDH69 meant.

 

The shaker really worked as you told me.

 

The buttons for now I will keep the way it is, because I am working without a definite front end.

 

But I wanted to see my strobe and beacon working and unfortunately I do not get any sign of life. 

 

I'm looking for what may be wrong in my setup. But so far I still have not found it.

 

Would you have any other alternative to see these two toys working?

 

I am very grateful for your help.

 

Cheers

 

With the debug window open - right click the window...

Brings up small test Menu.. In some cases you have to click on the fake emulation on, depending on your setup Before the menu will come up and then you can test your items..

-

Not every game will use all the DOF options

 

 

More good advice from outhere, particularly the last line.

 

With the debug window open - right click the window...

Brings up small test Menu.. In some cases you have to click on the fake emulation on, depending on your setup Before the menu will come up and then you can test your items..

-

Not every game will use all the DOF options

 

Knocker (KN) is used in

AliensPinball.FX3

 

Shaker (SH) is  used in

AdventureLand.FX3

AlienIsolationPinball.FX3

AliensPinball.FX3

AlienvsPredatorPinball.FX3

AmericanDadPinball.FX3

ArcherPinball.FX3

BackToTheFuture.FX3

Biolab.FX3

Blade.FX3

BobaFett.FX3

BobsBurgersPinball.FX3

CaptainAmerica.FX3

CastleStorm.FX3

CivilWar.FX3

Deadpool.FX3

DEFAULT.FX3

DoctorStrange.FX3

DOOMPinball.FX3

EarthDefense.FX3

ET.FX3

Excalibur.FX3

FalloutPinball.FX3

FamilyGuyPinball.FX3

FantasticFour.FX3

FearItself.FX3

GhostRider.FX3

GuardiansoftheGalaxy.FX3

Jaws.FX3

JurassicMayhem.FX3

JurassicPark.FX3

JurassicWorld.FX3

Mars.FX3

MarvelsAntMan.FX3

MarvelsAvengersAgeofUltron.FX3

MarvelsTheAvengers.FX3

MarvelsWomenofPowerAForce.FX3

MarvelsWomenofPowerChampions.FX3

MoonKnight.FX3

Paranormal.FX3

Portal.FX3

SecretsoftheDeep.FX3

SonOfZeus.FX3

SpiderMan.FX3

StarWarsAhchToIsland.FX3

STARWARSDARTHVADER.FX3

StarWarsEpisodeVTheEmpireStrikesBack.FX3

StarWarsLastJedi.FX3

StarWarsPinballEpisodeIVANewHope.FX3

StarWarsPinballMightoftheFirstOrder.FX3

StarWarsPinballRogueOne.FX3

StarWarsPinballStarWarsRebels.FX3

StarWarsPinballTheForceAwakens.FX3

StarWarsStarfighterAssault.FX3

StarWarsTheCloneWars.FX3

Tesla.FX3

TheElderScrollsVSkyrimPinball.FX3

TheInfinityGauntlet.FX3

TheWalkingDead.FX3

Thor.FX3

Venom.FX3

Wolverine.FX3

WorldWarHulk.FX3

 

Beacon (BK) is used in

AdventureLand.FX3

AlienIsolationPinball.FX3

AliensPinball.FX3

AlienvsPredatorPinball.FX3

All.FX3

AmericanDadPinball.FX3

ArcherPinball.FX3

BackToTheFuture.FX3

Biolab.FX3

Blade.FX3

BobaFett.FX3

BobsBurgersPinball.FX3

CaptainAmerica.FX3

CastleStorm.FX3

CivilWar.FX3

Deadpool.FX3

DEFAULT.FX3

DoctorStrange.FX3

DOOMPinball.FX3

EarthDefense.FX3

ET.FX3

Excalibur.FX3

FalloutPinball.FX3

FamilyGuyPinball.FX3

FantasticFour.FX3

FearItself.FX3

GhostRider.FX3

GuardiansoftheGalaxy.FX3

Jaws.FX3

JurassicMayhem.FX3

JurassicPark.FX3

JurassicWorld.FX3

Mars.FX3

MarvelsAntMan.FX3

MarvelsAvengersAgeofUltron.FX3

MarvelsTheAvengers.FX3

MarvelsWomenofPowerAForce.FX3

MarvelsWomenofPowerChampions.FX3

MoonKnight.FX3

Paranormal.FX3

Portal.FX3

SecretsoftheDeep.FX3

SonOfZeus.FX3

SpiderMan.FX3

StarWarsAhchToIsland.FX3

STARWARSDARTHVADER.FX3

StarWarsEpisodeVTheEmpireStrikesBack.FX3

StarWarsLastJedi.FX3

StarWarsPinballEpisodeIVANewHope.FX3

StarWarsPinballMightoftheFirstOrder.FX3

StarWarsPinballRogueOne.FX3

StarWarsPinballStarWarsRebels.FX3

StarWarsPinballTheForceAwakens.FX3

StarWarsStarfighterAssault.FX3

StarWarsTheCloneWars.FX3

Tesla.FX3

TheElderScrollsVSkyrimPinball.FX3

TheInfinityGauntlet.FX3

TheWalkingDead.FX3

Thor.FX3

Venom.FX3

Wolverine.FX3

WorldWarHulk.FX3

 

Strobe (SR) is used in

AdventureLand.FX3

AlienIsolationPinball.FX3

AliensPinball.FX3

AlienvsPredatorPinball.FX3

All.FX3

AmericanDadPinball.FX3

ArcherPinball.FX3

BackToTheFuture.FX3

Biolab.FX3

Blade.FX3

BobaFett.FX3

BobsBurgersPinball.FX3

CaptainAmerica.FX3

CastleStorm.FX3

CivilWar.FX3

Deadpool.FX3

DEFAULT.FX3

DoctorStrange.FX3

DOOMPinball.FX3

EarthDefense.FX3

ET.FX3

Excalibur.FX3

FalloutPinball.FX3

FamilyGuyPinball.FX3

FantasticFour.FX3

FearItself.FX3

GhostRider.FX3

GuardiansoftheGalaxy.FX3

Jaws.FX3

JurassicMayhem.FX3

JurassicPark.FX3

JurassicWorld.FX3

Mars.FX3

MarvelsAntMan.FX3

MarvelsAvengersAgeofUltron.FX3

MarvelsTheAvengers.FX3

MarvelsWomenofPowerAForce.FX3

MarvelsWomenofPowerChampions.FX3

MoonKnight.FX3

Paranormal.FX3

Portal.FX3

SecretsoftheDeep.FX3

SonOfZeus.FX3

SpiderMan.FX3

StarWarsAhchToIsland.FX3

STARWARSDARTHVADER.FX3

StarWarsEpisodeVTheEmpireStrikesBack.FX3

StarWarsLastJedi.FX3

StarWarsPinballEpisodeIVANewHope.FX3

StarWarsPinballMightoftheFirstOrder.FX3

StarWarsPinballRogueOne.FX3

StarWarsPinballStarWarsRebels.FX3

StarWarsPinballTheForceAwakens.FX3

StarWarsStarfighterAssault.FX3

StarWarsTheCloneWars.FX3

Tesla.FX3

TheElderScrollsVSkyrimPinball.FX3

TheInfinityGauntlet.FX3

TheWalkingDead.FX3

Thor.FX3

Venom.FX3

Wolverine.FX3

WorldWarHulk.FX3

 

So, for the most toys try Aliens and see if you can trigger them all !

You can trigger the shaker with left, right or forward nudge.

 

The only button controlled from FX3 files if BUT_LB - Launch Ball - thins comes on when the ball is in the launch lane.  I don't even have this button because I use a plunger.  Any other buttons being lit up when FX3 activates DOFLinx are really decorative for your own enjoyment.  IT really depends what you have them mapped to do within the FX3 emulator.

 

If you look in the "Sample INI folder" in the DOFLinx distribution you will see two sample file for FX3 to turn on / off button action, ie "SUP-Pinball FX3 ON - setup keys to turn on LEDs in buttons".  These are from my configuration.  What this does is make the button light when its pressed giving a fun effect.  I use an ON and OFF SUP file in DOFLinx because I only want this action within FX3, not any other emulator.  This means I use a Launch Before and Launch after command to run these SUP files via DOFLinxMsg.  I just looked and there is no image for PinballX setup of FX3 in the DOFLinx guide.  I have now added one, here is a link to it.

 

 

 

While you keep trying to help yourself and posting meaningful material, we will continue to help you.

 

[DDH69]

Other than the test routines, the only other way is to trigger the toy during the game.

 

If its working via the test routine then I can only assume you have not hit the event in the game.  I could give you commands to add the toy triggering to something basic like a slingshot or flipper if you really want to see it run.