Jump to content



Photo
- - - - -

DOFlinx doesnt see all my ports


  • Please log in to reply
6 replies to this topic

#1 mdr05

mdr05

    Neophyte

  • Members
  • Pip
  • 9 posts

  • Flag: United States of America

  • Favorite Pinball: jacks open

Posted 27 April 2024 - 05:00 AM

Im new, but Im definitely learning. Thanks for the help thus far. 

 

I have a KLz with an expansion board. It appears when I run DOFlinx it sees only 32 ports, while I believe the expansion board takes it to 49 ports. I used the built in tool to make my DOFlinx.ini file and although when I put the ports in and tested for my lights (coin, launch, start,etc) they all worked when tested. When I created the ini file, those ports did not go into the ini file (they were all above port 32). 

DOFlinx works, my lightbar works (sorta), solenoids fire, shaker, knocker. Theyre all below port 32. When I launch DOFlinx with debug, right click and test ports, I can put a port number in higher then 32 and it TESTS just fine. Since the built in ini creator didnt put in those items over port 32, I manually put them in but they still wont work (syntax on them is correct)

 

I dont know what info you need from my debug to help me out, but below I will put my log file (just launched doflinx without a game), my port assignments, and Ill somehow attach a screenshot of the doflinx debug screen that comes up. The last line is suspect. 

I beg of you dont ask me to rewire lol. Im surprised I got it as far as I did. Im really hoping there is a way to get doflinx to see the expansion board properly instead of trying to rewire (Id still be short ports)

 

*** Log File

 

DirectOutput Version 3.1.8648.38370, built 2023.09.05 21:19
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2024.04.27 00:38:35.445 DirectOutput Logger initialized
2024.04.27 00:38:35.428 Finishing framework
2024.04.27 00:38:35.429 Finishing cabinet
2024.04.27 00:38:35.430 Debug: Finishing output controllers
2024.04.27 00:38:35.430 Debug: Output controllers finished
2024.04.27 00:38:35.430 Cabinet finished
2024.04.27 00:38:35.430 DirectOutput framework finished.
2024.04.27 00:38:35.430 Bye and thanks for using!
2024.04.27 00:38:35.433 Global config filename is "C:\DirectOutput\Config\GlobalConfig_B2SServer.xml"
2024.04.27 00:38:35.445 Global config loaded from: C:\DirectOutput\Config\GlobalConfig_B2SServer.xml
2024.04.27 00:38:35.446 Loading Pinball parts
2024.04.27 00:38:35.446 Loading cabinet
2024.04.27 00:38:35.446 No cabinet config file loaded. Will use AutoConfig.
2024.04.27 00:38:35.446 Cabinet auto configuration started
2024.04.27 00:38:35.569 Detected and added Pinscape Controller Nr. 1 with name Pinscape Controller 01
2024.04.27 00:38:35.570 Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 49
2024.04.27 00:38:35.577 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2024.04.27 00:38:35.581 LedWiz-like device at VID=49153, PID=7658, product string=<not available>, manufacturer string=<not available>
2024.04.27 00:38:35.582 LedWiz-like device at VID=64250, PID=247, product string=Pinscape Controller, manufacturer string=mjrnet
2024.04.27 00:38:35.582 HID caps: usage page=1, usage=4, number of link collection nodes=1, output report byte length=9
2024.04.27 00:38:35.584 LedWiz-like device at VID=1309, PID=2, product string=Back-UPS XS 1000M FW:945.d11 .D USB FW:d11     , manufacturer string=American Power Conversion
2024.04.27 00:38:35.584 LedWiz-like device at VID=6268, PID=1360, product string=AW-ELC, manufacturer string=Alienware
2024.04.27 00:38:35.586 LedWiz-like device at VID=1030, PID=10260, product string=2.4G Composite Devic, manufacturer string=<not available>
2024.04.27 00:38:35.587 LedWiz-like device at VID=1030, PID=10260, product string=2.4G Composite Devic, manufacturer string=<not available>
2024.04.27 00:38:35.587 LedWiz-like device at VID=64250, PID=247, product string=Pinscape Controller, manufacturer string=mjrnet
2024.04.27 00:38:35.587 HID caps: usage page=12, usage=1, number of link collection nodes=1, output report byte length=0
2024.04.27 00:38:35.589 Opening 64-bit LedWiz driver...
2024.04.27 00:38:35.589 Detected and added LedWiz Nr. 8 with name LedWiz 08
2024.04.27 00:38:35.589 Added LedwizEquivalent Nr. 8 with name LedWiz 08 Equivalent for Ledwiz Nr. 8
2024.04.27 00:38:35.592 Cabinet auto configuration finished
2024.04.27 00:38:35.592 Cabinet loaded
2024.04.27 00:38:35.592 Loading table config
2024.04.27 00:38:35.592 No TableFilename specified, will use empty tableconfig
2024.04.27 00:38:35.592 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName doflinx
2024.04.27 00:38:35.594 No directoutputconfig.ini or ledcontrol.ini files found.
2024.04.27 00:38:35.595 No config for table found in LedControl data for RomName doflinx.
2024.04.27 00:38:35.595 Table config loading finished: romname=doflinx, tablename=doflinx
2024.04.27 00:38:35.596 Pinball parts loaded
2024.04.27 00:38:35.596 Starting processes
2024.04.27 00:38:35.596 Initializing cabinet
2024.04.27 00:38:35.596 Debug: Initializing output controllers
2024.04.27 00:38:35.597 Pinscape Pinscape Controller 01 intialized and updater thread started.
2024.04.27 00:38:35.598 Debug: Initializing LedWiz Nr. 08
2024.04.27 00:38:35.598 Pinscape Pinscape Controller 01 updater thread  started.
2024.04.27 00:38:35.598 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2024.04.27 00:38:35.599 LedWiz Nr. 08 initialized and updater thread initialized.
2024.04.27 00:38:35.599 Debug: Output controllers initialized
2024.04.27 00:38:35.599 Updater thread for LedWiz 08 started.
2024.04.27 00:38:35.600 Cabinet initialized
2024.04.27 00:38:35.602 Warning: Could not determin name of shape definition file
2024.04.27 00:38:35.604 Framework initialized.
2024.04.27 00:38:35.604 Have fun! :)
2024.04.27 00:38:35.618 Initializing cabinet
2024.04.27 00:38:35.618 Debug: Initializing output controllers
2024.04.27 00:38:35.618 Debug: Output controllers initialized
2024.04.27 00:38:35.618 Cabinet initialized
2024.04.27 00:38:35.620 Pinscape Pinscape Controller 01 intialized and updater thread started.
2024.04.27 00:38:35.620 Pinscape Pinscape Controller 01 updater thread  started.
2024.04.27 00:38:35.620 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2024.04.27 00:38:35.625 Opening 64-bit LedWiz driver...
2024.04.27 00:38:35.625 Debug: Initializing LedWiz Nr. 08
2024.04.27 00:38:35.625 LedWiz Nr. 08 initialized and updater thread initialized.
2024.04.27 00:38:35.625 Opening 64-bit LedWiz driver...
2024.04.27 00:38:35.689 Debug: Disposing LedWiz instance 08.
2024.04.27 00:38:37.637 Finishing framework
2024.04.27 00:38:37.637 Finishing cabinet
2024.04.27 00:38:37.638 Debug: Finishing output controllers
2024.04.27 00:38:37.642 Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2024.04.27 00:38:37.642 Pinscape Pinscape Controller 01 finished and updater thread stopped.
2024.04.27 00:38:37.643 Debug: Finishing LedWiz Nr. 08
2024.04.27 00:38:37.644 Updater thread for LedWiz 08 terminated.
2024.04.27 00:38:37.669 LedWiz Nr. 08 finished and updater thread stopped.
2024.04.27 00:38:37.669 Debug: Output controllers finished
2024.04.27 00:38:37.669 Cabinet finished
2024.04.27 00:38:37.669 DirectOutput framework finished.
2024.04.27 00:38:37.669 Bye and thanks for using!
2024.04.27 00:38:37.669 Initializing cabinet
2024.04.27 00:38:37.669 Debug: Initializing output controllers
2024.04.27 00:38:37.669 Debug: Output controllers initialized
2024.04.27 00:38:37.669 Cabinet initialized
2024.04.27 00:38:37.678 Pinscape Pinscape Controller 01 intialized and updater thread started.
2024.04.27 00:38:37.678 Pinscape Pinscape Controller 01 updater thread  started.
2024.04.27 00:38:37.678 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2024.04.27 00:38:37.699 Opening 64-bit LedWiz driver...
2024.04.27 00:38:37.699 Debug: Initializing LedWiz Nr. 08
2024.04.27 00:38:37.699 LedWiz Nr. 08 initialized and updater thread initialized.
2024.04.27 00:38:37.699 Opening 64-bit LedWiz driver...
2024.04.27 00:38:37.699 Updater thread for LedWiz 08 started.
2024.04.27 00:38:37.770 Debug: Disposing LedWiz instance 08.
2024.04.27 00:38:37.770 Debug: Disposing LedWiz instance 08.
 
 
****** My Port Assignments

Item         Output Number

Right Solenoid 1

Left Solenoid 2

Knocker 3

Beacon 8

Shaker 12

Far Left LED bar Red 18 Far Left LED bar Green 19 Far Left LED bar Blue 20 Mid left LED bar Red 21 Mid left LED bar Green 22 Mid left LED bar Blue 23 Center LED bar Red 24 Center LED bar Green 25 Center LED bar Blue 26 Mid Right LED bar Red 27 Mid Right LED bar Green 28 Mid Right LED bar Blue 29 Far Right LED bar Red 30 Far Right LED bar Green 31 Far Right LED bar Blue 32 Strobes 33 Right Flipper Red 34 Right Flipper Green 35 Right Flipper Blue 36 Fire Button Red 37 Fire Button Green 38 Fire Button Blue 39 Left Flipper Red 40 Left Flipper Green 41 Left Flipper Blue 42 Right Magna Save 43 Play Button 44 Left Magna Save 46 Coin Button Lights 47 Launch Ball Button 48

 

 

DirectOutput Version 3.1.8648.38370, built 2023.09.05 21:19
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2024.04.27 00:38:35.445 DirectOutput Logger initialized
2024.04.27 00:38:35.428 Finishing framework
2024.04.27 00:38:35.429 Finishing cabinet
2024.04.27 00:38:35.430 Debug: Finishing output controllers
2024.04.27 00:38:35.430 Debug: Output controllers finished
2024.04.27 00:38:35.430 Cabinet finished
2024.04.27 00:38:35.430 DirectOutput framework finished.
2024.04.27 00:38:35.430 Bye and thanks for using!
2024.04.27 00:38:35.433 Global config filename is "C:\DirectOutput\Config\GlobalConfig_B2SServer.xml"
2024.04.27 00:38:35.445 Global config loaded from: C:\DirectOutput\Config\GlobalConfig_B2SServer.xml
2024.04.27 00:38:35.446 Loading Pinball parts
2024.04.27 00:38:35.446 Loading cabinet
2024.04.27 00:38:35.446 No cabinet config file loaded. Will use AutoConfig.
2024.04.27 00:38:35.446 Cabinet auto configuration started
2024.04.27 00:38:35.569 Detected and added Pinscape Controller Nr. 1 with name Pinscape Controller 01
2024.04.27 00:38:35.570 Added LedwizEquivalent Nr. 51 with name Pinscape Controller 01 Equivalent for Pinscape Controller Nr. 1, 49
2024.04.27 00:38:35.577 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2024.04.27 00:38:35.581 LedWiz-like device at VID=49153, PID=7658, product string=<not available>, manufacturer string=<not available>
2024.04.27 00:38:35.582 LedWiz-like device at VID=64250, PID=247, product string=Pinscape Controller, manufacturer string=mjrnet
2024.04.27 00:38:35.582 HID caps: usage page=1, usage=4, number of link collection nodes=1, output report byte length=9
2024.04.27 00:38:35.584 LedWiz-like device at VID=1309, PID=2, product string=Back-UPS XS 1000M FW:945.d11 .D USB FW:d11     , manufacturer string=American Power Conversion
2024.04.27 00:38:35.584 LedWiz-like device at VID=6268, PID=1360, product string=AW-ELC, manufacturer string=Alienware
2024.04.27 00:38:35.586 LedWiz-like device at VID=1030, PID=10260, product string=2.4G Composite Devic, manufacturer string=<not available>
2024.04.27 00:38:35.587 LedWiz-like device at VID=1030, PID=10260, product string=2.4G Composite Devic, manufacturer string=<not available>
2024.04.27 00:38:35.587 LedWiz-like device at VID=64250, PID=247, product string=Pinscape Controller, manufacturer string=mjrnet
2024.04.27 00:38:35.587 HID caps: usage page=12, usage=1, number of link collection nodes=1, output report byte length=0
2024.04.27 00:38:35.589 Opening 64-bit LedWiz driver...
2024.04.27 00:38:35.589 Detected and added LedWiz Nr. 8 with name LedWiz 08
2024.04.27 00:38:35.589 Added LedwizEquivalent Nr. 8 with name LedWiz 08 Equivalent for Ledwiz Nr. 8
2024.04.27 00:38:35.592 Cabinet auto configuration finished
2024.04.27 00:38:35.592 Cabinet loaded
2024.04.27 00:38:35.592 Loading table config
2024.04.27 00:38:35.592 No TableFilename specified, will use empty tableconfig
2024.04.27 00:38:35.592 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName doflinx
2024.04.27 00:38:35.594 No directoutputconfig.ini or ledcontrol.ini files found.
2024.04.27 00:38:35.595 No config for table found in LedControl data for RomName doflinx.
2024.04.27 00:38:35.595 Table config loading finished: romname=doflinx, tablename=doflinx
2024.04.27 00:38:35.596 Pinball parts loaded
2024.04.27 00:38:35.596 Starting processes
2024.04.27 00:38:35.596 Initializing cabinet
2024.04.27 00:38:35.596 Debug: Initializing output controllers
2024.04.27 00:38:35.597 Pinscape Pinscape Controller 01 intialized and updater thread started.
2024.04.27 00:38:35.598 Debug: Initializing LedWiz Nr. 08
2024.04.27 00:38:35.598 Pinscape Pinscape Controller 01 updater thread  started.
2024.04.27 00:38:35.598 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2024.04.27 00:38:35.599 LedWiz Nr. 08 initialized and updater thread initialized.
2024.04.27 00:38:35.599 Debug: Output controllers initialized
2024.04.27 00:38:35.599 Updater thread for LedWiz 08 started.
2024.04.27 00:38:35.600 Cabinet initialized
2024.04.27 00:38:35.602 Warning: Could not determin name of shape definition file
2024.04.27 00:38:35.604 Framework initialized.
2024.04.27 00:38:35.604 Have fun! :)
2024.04.27 00:38:35.618 Initializing cabinet
2024.04.27 00:38:35.618 Debug: Initializing output controllers
2024.04.27 00:38:35.618 Debug: Output controllers initialized
2024.04.27 00:38:35.618 Cabinet initialized
2024.04.27 00:38:35.620 Pinscape Pinscape Controller 01 intialized and updater thread started.
2024.04.27 00:38:35.620 Pinscape Pinscape Controller 01 updater thread  started.
2024.04.27 00:38:35.620 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2024.04.27 00:38:35.625 Opening 64-bit LedWiz driver...
2024.04.27 00:38:35.625 Debug: Initializing LedWiz Nr. 08
2024.04.27 00:38:35.625 LedWiz Nr. 08 initialized and updater thread initialized.
2024.04.27 00:38:35.625 Opening 64-bit LedWiz driver...
2024.04.27 00:38:35.689 Debug: Disposing LedWiz instance 08.
2024.04.27 00:38:37.637 Finishing framework
2024.04.27 00:38:37.637 Finishing cabinet
2024.04.27 00:38:37.638 Debug: Finishing output controllers
2024.04.27 00:38:37.642 Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2024.04.27 00:38:37.642 Pinscape Pinscape Controller 01 finished and updater thread stopped.
2024.04.27 00:38:37.643 Debug: Finishing LedWiz Nr. 08
2024.04.27 00:38:37.644 Updater thread for LedWiz 08 terminated.
2024.04.27 00:38:37.669 LedWiz Nr. 08 finished and updater thread stopped.
2024.04.27 00:38:37.669 Debug: Output controllers finished
2024.04.27 00:38:37.669 Cabinet finished
2024.04.27 00:38:37.669 DirectOutput framework finished.
2024.04.27 00:38:37.669 Bye and thanks for using!
2024.04.27 00:38:37.669 Initializing cabinet
2024.04.27 00:38:37.669 Debug: Initializing output controllers
2024.04.27 00:38:37.669 Debug: Output controllers initialized
2024.04.27 00:38:37.669 Cabinet initialized
2024.04.27 00:38:37.678 Pinscape Pinscape Controller 01 intialized and updater thread started.
2024.04.27 00:38:37.678 Pinscape Pinscape Controller 01 updater thread  started.
2024.04.27 00:38:37.678 Pinscape Pinscape Controller 01 updater thread  has connected to Pinscape Pinscape Controller 01.
2024.04.27 00:38:37.699 Opening 64-bit LedWiz driver...
2024.04.27 00:38:37.699 Debug: Initializing LedWiz Nr. 08
2024.04.27 00:38:37.699 LedWiz Nr. 08 initialized and updater thread initialized.
2024.04.27 00:38:37.699 Opening 64-bit LedWiz driver...
2024.04.27 00:38:37.699 Updater thread for LedWiz 08 started.
2024.04.27 00:38:37.770 Debug: Disposing LedWiz instance 08.
2024.04.27 00:38:37.770 Debug: Disposing LedWiz instance 08.
2024.04.27 01:07:25.014 ArtNet  finished and updater thread stopped.
2024.04.27 01:07:25.014 PinControl  finished and updater thread stopped.
2024.04.27 01:07:25.017 Pinscape Pinscape Controller 01 updater thread  has disconnected from Pinscape Pinscape Controller 01 and will terminate.
2024.04.27 01:07:25.017 Pinscape Pinscape Controller 01 finished and updater thread stopped.
2024.04.27 01:07:25.017 ArtNet  finished and updater thread stopped.
2024.04.27 01:07:25.017 PinControl  finished and updater thread stopped.
2024.04.27 01:07:25.017 Debug: Finishing LedWiz Nr. 08
2024.04.27 01:07:25.017 Updater thread for LedWiz 08 terminated.
2024.04.27 01:07:25.030 LedWiz Nr. 08 finished and updater thread stopped.
2024.04.27 01:07:25.030 ArtNet  finished and updater thread stopped.
2024.04.27 01:07:25.030 PinControl  finished and updater thread stopped.
2024.04.27 01:07:25.030 Finishing cabinet
2024.04.27 01:07:25.030 Debug: Finishing output controllers
2024.04.27 01:07:25.030 Debug: Output controllers finished
2024.04.27 01:07:25.030 Cabinet finished
2024.04.27 01:07:25.045 Debug: Disposing LedWiz instance 08.
 

 

 

I noticed that the formatting changed from what I had and makes the port assignments difficult to read, and I attempted to attach a snip of what DOFlinx shows when it starts up but was unable to.


Edited by mdr05, 27 April 2024 - 05:12 AM.


#2 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,072 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 27 April 2024 - 06:53 AM

We're all here to learn, the smarter ones admit it!

 

Anyway, seems you've attached 2 x DirectOutput logs and 0 x DOFLinx LOG.  Remember DOFLinx uses DOF, they are two different things.

 

When you say KL25Z, yes, I presume running PinScape. I have PinScapes with >100 outputs, all good.

 

In the Pinsape setup (sorry can't grab a shot at the moment as I'm not near the cabinet, but below is a DOFLInx.LOG snippet from someone else I was helping today, it shows both devices), you need to enable the Pinscape to be seen as a Pinscape and not just LEDWiz equivalents.  LEDWiz's are limited to 32 ports each..  I suspect this is your issue.  DOFLinx wants to use it in native (Pinscape) mode, DOF will happily use either.  Once you do this, at startup DOFLinx will "see" both your Pinscape with all outputs and a LEDWiz with 32 outputs and numbers them as output #1 and output #2.  For your toys use output#1 only, ie the real Pinscape, not then emulated LEDWiz.

 

Hope this gets you on your way.

 

26-Apr-24 09:12:13.153 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
26-Apr-24 09:12:13.154 - DOFLinx device:1 Pinscape setup with 64 outputs
26-Apr-24 09:12:13.154 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
26-Apr-24 09:12:13.154 - DOFLinx device:2 LEDWiz setup with 32 outputs
26-Apr-24 09:12:13.155 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one

DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#3 mdr05

mdr05

    Neophyte

  • Members
  • Pip
  • 9 posts

  • Flag: United States of America

  • Favorite Pinball: jacks open

Posted 27 April 2024 - 05:59 PM

 

We're all here to learn, the smarter ones admit it!

 

Anyway, seems you've attached 2 x DirectOutput logs and 0 x DOFLinx LOG.  Remember DOFLinx uses DOF, they are two different things.

 

When you say KL25Z, yes, I presume running PinScape. I have PinScapes with >100 outputs, all good.

 

In the Pinsape setup (sorry can't grab a shot at the moment as I'm not near the cabinet, but below is a DOFLInx.LOG snippet from someone else I was helping today, it shows both devices), you need to enable the Pinscape to be seen as a Pinscape and not just LEDWiz equivalents.  LEDWiz's are limited to 32 ports each..  I suspect this is your issue.  DOFLinx wants to use it in native (Pinscape) mode, DOF will happily use either.  Once you do this, at startup DOFLinx will "see" both your Pinscape with all outputs and a LEDWiz with 32 outputs and numbers them as output #1 and output #2.  For your toys use output#1 only, ie the real Pinscape, not then emulated LEDWiz.

 

Hope this gets you on your way.

 

26-Apr-24 09:12:13.153 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
26-Apr-24 09:12:13.154 - DOFLinx device:1 Pinscape setup with 64 outputs
26-Apr-24 09:12:13.154 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
26-Apr-24 09:12:13.154 - DOFLinx device:2 LEDWiz setup with 32 outputs
26-Apr-24 09:12:13.155 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one

 

 

I understand wat you re saying, but Im confused as to how to get it done - to acknowledge the ports over 32, even if I set it as a device #2. My output log clearly shows doflinx in thinking that there is a second device, but how do I tell it that device is not supposed to be seen as a ledwiz. I tried along the lines of (example for my statrt button) LINK_ST=244 to point it to the second device, but it throws an error stating that port assignment for that device needs to be 1-32. In the DOF config tool, I only have 1 device listed there, as you mentioned is fine for DOF. I looked at sample doflinx ini files, and in the guide, but I am still confused with this point. I can see what needs to be done in my head, and understand why, just not how to do it! frustrating to say the least. 

I sincerely appreciate your helping me to understand. 



#4 mdr05

mdr05

    Neophyte

  • Members
  • Pip
  • 9 posts

  • Flag: United States of America

  • Favorite Pinball: jacks open

Posted 27 April 2024 - 06:38 PM

So, I need to have it see the "second" device as a pinscape device. I hopped over to the config tool, and added a second device. It now shows up in the dropdown for me to choose (currently blank). Do I set up a 2nd device in the config tool using the ports above 32 only? Wouldnt that give me 2 config files? And would I just add a line in DOFlinz ini pointing to another directoutputconfig? I might be COMPLETELY wrong on this, but thats how confuse I currently am lol. Im hoping Im at least poking in the right direction.

 

Current doflinx output when I start it up. 

 

27-Apr-24 13:48:26.683 - DOFLinx for Pinball Emulators - DOFLinx by DDH69
27-Apr-24 13:48:26.686 - Starting up - version 8.00
27-Apr-24 13:48:26.687 - 64 bit operating system
27-Apr-24 13:48:26.687 - 64 bit application
27-Apr-24 13:48:26.687 - For support come and visit the community here http://www.vpforums....p?showforum=104
27-Apr-24 13:48:26.689 - Pre-Reading DOFLinx.INI startup config file details
27-Apr-24 13:48:26.749 - DEBUG enabled with showing of window True
27-Apr-24 13:48:26.987 - Joystick # 1 detected : 32 buttons   Z-Axis
27-Apr-24 13:48:26.993 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
27-Apr-24 13:48:26.996 - DOFLinx device:1 Pinscape setup with 49 outputs
27-Apr-24 13:48:26.999 - PinOne Port = 
27-Apr-24 13:48:27.001 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
27-Apr-24 13:48:27.002 - DOFLinx device:2 LEDWiz setup with 32 outputs
27-Apr-24 13:48:27.004 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
27-Apr-24 13:48:27.009 - Reading DOFLinx.INI startup config file details
27-Apr-24 13:48:27.011 - Turning DEBUG off
27-Apr-24 13:48:27.041 - DEBUG enabled with showing of window True
27-Apr-24 13:48:27.046 - Reading DirectOutputConfig file named C:\DirectOutput\directoutputconfig51.ini
27-Apr-24 13:48:27.084 - Set Debug Privilege = Set OK
27-Apr-24 13:48:28.964 - Stopping ROM
27-Apr-24 13:48:28.995 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
27-Apr-24 13:48:29.006 - DOFLinx device:1 Pinscape setup with 49 outputs
27-Apr-24 13:48:29.016 - PinOne Port = 
27-Apr-24 13:48:29.026 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
27-Apr-24 13:48:29.036 - DOFLinx device:2 LEDWiz setup with 32 outputs
27-Apr-24 13:48:29.040 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
27-Apr-24 13:52:40.849 - Shutting down
27-Apr-24 13:52:40.880 - Program close

 

We're all here to learn, the smarter ones admit it!

 

Anyway, seems you've attached 2 x DirectOutput logs and 0 x DOFLinx LOG.  Remember DOFLinx uses DOF, they are two different things.

 

When you say KL25Z, yes, I presume running PinScape. I have PinScapes with >100 outputs, all good.

 

In the Pinsape setup (sorry can't grab a shot at the moment as I'm not near the cabinet, but below is a DOFLInx.LOG snippet from someone else I was helping today, it shows both devices), you need to enable the Pinscape to be seen as a Pinscape and not just LEDWiz equivalents.  LEDWiz's are limited to 32 ports each..  I suspect this is your issue.  DOFLinx wants to use it in native (Pinscape) mode, DOF will happily use either.  Once you do this, at startup DOFLinx will "see" both your Pinscape with all outputs and a LEDWiz with 32 outputs and numbers them as output #1 and output #2.  For your toys use output#1 only, ie the real Pinscape, not then emulated LEDWiz.

 

Hope this gets you on your way.

 

26-Apr-24 09:12:13.153 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
26-Apr-24 09:12:13.154 - DOFLinx device:1 Pinscape setup with 64 outputs
26-Apr-24 09:12:13.154 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
26-Apr-24 09:12:13.154 - DOFLinx device:2 LEDWiz setup with 32 outputs
26-Apr-24 09:12:13.155 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one

 



#5 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,072 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 27 April 2024 - 10:26 PM

Its this bit in the Pinscape setup utility.  I think you've gone to the DOF setup utility.  The Pinscape utility runs locally on your PC and is where you would have setup your buttons and outputs on the Pinscape.

Attached Files


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#6 mdr05

mdr05

    Neophyte

  • Members
  • Pip
  • 9 posts

  • Flag: United States of America

  • Favorite Pinball: jacks open

Posted 28 April 2024 - 02:17 AM

Its this bit in the Pinscape setup utility.  I think you've gone to the DOF setup utility.  The Pinscape utility runs locally on your PC and is where you would have setup your buttons and outputs on the Pinscape.

Eureka. That little thumbnail was all I needed. Much obliged for your direction! Now that I got it seeing everything it needs to see, I can move on with making it do the things I want it to do! And by the way, it makes sense now. Well, much more sense than it did before. I set this up almost 2 years ago already, and it was working fine but I decided it was time I relearned what I did, if you know what I mean. With the addition of Pinball FX, and all the 64bit updates, I figgred now was the time.

Thank you much again!



#7 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,072 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 28 April 2024 - 02:23 AM

Great news, thanks for letting me know.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here