28 replies to this topic

[mviars]

I am sorry guys I really really tried to do this without having to post. Its been about a year since I setup my cabinet but wanted to check out these need features and tables especially the FX2 & 3 tables with some feedback. I have spent numerous hours trying to get this setup using the step by step guide but having issues probably due to my time away from setting these up. Anyways I am getting an error running DOFLinx that I will post.

 

Win7

I believe DOF R3

 

 

Attached Files

•  DOFLinx.zip   4.29KB   63 downloads
•  directoutputconfig.zip   72.01KB   64 downloads

[Outhere]

DEBUG=0 -- Change to DEBUG=1   --  Re-post log

What hardware are you using that the DOF would be looking for and do you have the DOF set up and running in visual pinball?

[mviars]

OK will do. I have a zeb boards LED Wiz Virtual output kit with a bear bones booster breakout board. I did notice that it says in the log that it cannot find the LED Wiz. Not sure what thats about. Dof does work in VP just loaded up avengers and full lights, solenoids,shakers, etc.

 

 

Attached Files

•  DOFLinx.zip   510bytes   22 downloads

[DDH69]

DOFLinx will find a LEDWiz if reported by the Direct Output Framework as  one being there.  This has been tested (and run) with multiple genuine LEDWiz devices in one cabinet, plus a PinScape emulating a LEDWiz.  I am unfamiliar and unsure about the Zeb device you have.  It depends if it emulates a LEDWiz, or is configured as LEDWiz device X within the DOF - they are two different things. (I suspect it may be the latter)

Edited by DDH69, 02 January 2018 - 04:37 AM.

[mviars]

I am pretty sure its set as a LEDWiz device and I am also pretty sure it is not DOFLinx itself but something I am not doing right I just do not know what

[DDH69]

There really shouldn't be much you can do wrong at that point.  You have it working in DOF, just not DOFLinx.  I'll read some more later tonight, but I suspect the device is not emulating a LEDWiz (like the Pinscape does) at a hardware level, rather its seen as its native device, but the DOF allows it to be setup as a LEDWiz for configuration purposes.  DOFLinx needs to see something that is reported as a native LEDWiz by DOF, ie an actual LEDWiz or Pinscape with emulation turned on.

[mviars]

OK great. Please take your time and let me know if there is anything on my end I can do to help.

[DDH69]

So I looked up what I think is the board you have.  If I've found the correct one, then yes it runs with a LEDWiz.  Ideally if you can, peek inside your cabinet and double check that you have a LEDWiz board.  That way we know what we're chasing.  Assuming you have a LEDWiz, then we're chasing a software / driver issue.

 

So is DOFLinx in a folder with LEDWiz.dll?  The easiest way is to have the DOFLinx.exe in the same folder as your DirectOutput stuff. ie

C:\DirectOuput\

C:\DirectOutput\config\

C:\DirectOuput\DOFLinx_B2S\

C:\DirectOuput\DOFLinx_FX2\

C:\DirectOuput\DOFLinx_FX3\

 

Can you post a listing of the folder with all of this in?  That way I should be able to see the LEDWiz.dll version, DOF version, etc.

[mviars]

Here does this help any?

Attached Files

•  Capture.JPG   116.29KB   7 downloads

[DDH69]

OK, looks like a clean DOF R3 installation from the key files I checked for size and date/time.  I've run that version with a LEDWiz without issue.  I still have it on my test machine but only have a Pinscape on that machine.  So what I just did was turn on LEDWiz emulation mode on my Pinscape, restore the same version of DOF R3 that you have and try DOFLinx => works fine.

 

I'm temporarily stumped.  Have you managed to peek inside and look at the LEDwWz board?  Might be time for versions, etc on the board.

[mviars]

This is the main board but not much info on it

Main board & Breakout board

Attached Files

•  Board 1.jpg   362.29KB   6 downloads
•  Board 2.jpg   383.08KB   5 downloads

Edited by mviars, 04 January 2018 - 05:43 AM.

[mviars]

Something else im noticing too. After looking at the online DOF config tool(which I almost forgot that is how I set this up). I see that maybe my ports are not set up correctly. Can someone look at these setting and tell me if thats the case? files attached.

Attached Files

•  DOF Config tool.JPG   89.85KB   3 downloads
•  DOFLinx.zip   3.82KB   10 downloads

[DDH69]

OK, so yo have a PacLED64, not a LEDWiz.  DOFLinx cannot auto-find a PacLED64, you need to tell it its there.  So when you start DOFLinx you will need to add PACLED64=1 on the command line.  Check the DOFLinx guide for more detail.

 

L_FLIPPER_OUTPUT=118

R_FLIPPER_OUTPUT=119

 

RGB_OUTPUT=142

 

LINK_LF=118,50,10000,255

LINK_RF=119,50,10000,255

LINK_LS=117,50,500,255

LINK_RS=120,50,500,255

LINK_ML=122,50,500,255

#LINK_MC=128,50,500,255

LINK_MR=123,50,500,255

LINK_BL=121,50,500,255

#LINK_BC=131,50,500,255

LINK_BR=124,50,500,255

LINK_SH=125,1000,5000,255

LINK_GR=129,750,10000,255

LINK_KN=128,120,500,255

LINK_SR=116,ON,0

#LINK_BK=218,ON,0

LINK_FLOL=101

LINK_FLIL=104

LINK_FLCN=107

LINK_FLIR=110

LINK_FLOR=113

LINK_ST=147

LINK_EB=148

LINK_CN=146

#LINK_EX=104

LINK_KN=128

 

I'm not sure about your outputs 26,27 and 30.

 

I think this should get you pretty close.

 

It looks like what you have is a PacLED64 physical device.  This is dealt with by DOF as two logical LEDWiz devices.  DOFLinx treats it as a native PacLED64 device, so a single output device with 64 outputs.  The key missing part to the DOFLinx puzzle for you is the PACLED64=1 on your command line.  The rest is just about getting the correct toys setup within DOFLinx.

Edited by DDH69, 04 January 2018 - 11:41 AM.

[mviars]

OK OK I am following now. I have made all those changes in the DOFLinx config file. I think port 26 and 27 may be one of the 10 relay coils and 30 I think must be the escape exit  button since I do not see it listed. anyways do I put the PACLED64=1 in the main windows startup folder for the DOFLinx.exe shortcut in the target box?

\

like

 

"C:\Program Files (x86)\DirectOutput\DOFLinx.exe" PACLED64=1 PATH_INI=C:\Program Files (x86)\DirectOutput\DOFLinx_INI\

Edited by mviars, 04 January 2018 - 11:56 PM.

[DDH69]

The command line looks good.  Let's just concentrate on that first, then once we have an output device recognised we'll get back to the ports.

 

It is possible that the PacLED64 device you've got is not ID #1, they can be 1,2,3 or 4.  Try the other ID's ie, 2, 3 and 4.  ID#1 is the most likely so if 2,3 or 4 don't deliver a positive outcome, go back to ID #1 and produce another DOFLinx log file.

[mviars]

Here is the info you requested.

Attached Files

•  DOFLinx.zip   272bytes   17 downloads
•  error.JPG   48.14KB   2 downloads
•  shortcut.JPG   37.41KB   2 downloads

[mviars]

Changing the device number had no effect

[mviars]

I just cant seem to get DOFLinx to recognize the PACLED64

[DDH69]

Are you getting the crash with the PACLED64=1 parameter?

 

Is the error occurring with your target "C:\Program Files (x86)\DirectOutput\DOFLinx.exe" PACLED64=1 PATH_INI=C:\Program Files (x86)\DirectOutput\DOFLinx_INI\  that you posted previously?

 

There is likely to be an issue with the fact you have a space in your PATH_INI=   I don't think quoting this works.  You may want to try a path with no space in it, or temporarily copy your DOFLinx.ini into the same directory as DOFLinx.exe and remove the PATH_INI= from your shortcut.  DOF:Linx will look for its INI in the startup directory as a default.

[mviars]

Well I tried what you said and put deleted the path parameter and have the DOFLinx.ini in the same folder as the DOFLinx.exe ran the shortcut and got his new error. At least it shows the pacled64 as a devise now.

 

 critical error.JPG   24.7KB   2 downloads

 

 DOFLinx.zip   3.81KB   5 downloads

 

DOFLinx.log

05-Jan-18 23:48:33.364 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

05-Jan-18 23:48:33.365 - Starting up - version 6.01

05-Jan-18 23:48:33.397 - 0 Pinscape device(s) found

05-Jan-18 23:48:33.397 - 0 LEDWiz device(s) found

05-Jan-18 23:48:33.397 - 0 FTDI (Sainsmart) device(s) found

05-Jan-18 23:48:33.397 - DOFLinx device: 1 Initialising as PacLed64 #1

05-Jan-18 23:48:33.462 - DOFLinx device:1 PacLed64 setup with 64 outputs

05-Jan-18 23:48:33.468 - Reading DOFLinx.INI startup config file details

05-Jan-18 23:48:33.490 - Reading DirectOutputConfig file named c:\Program Files (x86)\DirectOutput\config\directoutputconfig.ini

05-Jan-18 23:48:33.500 - Parameter data failed for LINK_SR with System.IndexOutOfRangeException: Index was outside the bounds of the array.

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

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