7 replies to this topic

[Outhere]

When I add a Saintsmart board I get this Error every time

 

Error

Spoiler

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at DOFLinx.MainForm.UpdateTheDevice(Int16 UpdateDevice)
at DOFLinx.MainForm.DOFDeviceUpdate(Int16 DeviceID)
at DOFLinx.MainForm.DOF_Fixed_Outputs()
at DOFLinx.MainForm.DoStartup()
at DOFLinx.MainForm.SteamTimer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3110.0 built by: NET472REL1LAST_C

----------------------------------------
DOFLinx
Assembly Version: 1.0.0.0
Win32 Version: 5.0.0.0

----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.7.3056.0 built by: NET472REL1

----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3110.0 built by: NET472REL1LAST_C

----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
DirectOutput
Assembly Version: 3.1.6623.21194
Win32 Version: 3.1.6623.21194

----------------------------------------
Extensions
Assembly Version: 3.1.6623.21194
Win32 Version: 3.1.6623.21194

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Security
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3101.0 built by: NET472REL1LAST_B

----------------------------------------
System.Data.SqlXml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Web.ApplicationServices
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0

----------------------------------------
System.ComponentModel.DataAnnotations
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0

----------------------------------------
System.DirectoryServices.Protocols
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.DirectoryServices
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
System.Runtime.Caching
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0

----------------------------------------
Microsoft.Build.Framework
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1

----------------------------------------
B2SBackglassServer
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0

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

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:





When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

log

Spoiler

20-Jun-18 18:26:20.976 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Jun-18 18:26:21.007 - Starting up - version 6.30
20-Jun-18 18:26:21.007 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Jun-18 18:26:21.007 - Pre-Reading DOFLinx.INI startup config file details
20-Jun-18 18:26:23.537 - Found Teensy controller named 'LEDStripController'
20-Jun-18 18:26:23.585 - 1 Pinscape device(s) found
20-Jun-18 18:26:23.585 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Jun-18 18:26:23.585 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Jun-18 18:26:23.585 - 3 LEDWiz device(s) found
20-Jun-18 18:26:23.596 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=1
20-Jun-18 18:26:23.598 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Jun-18 18:26:23.598 - DOFLinx device: 3 Initializing as LEDWiz #2 with ID=0
20-Jun-18 18:26:23.598 - DOFLinx device:3 LEDWiz setup with 32 outputs
20-Jun-18 18:26:23.598 - DOFLinx device: 4 Initializing as LEDWiz #8 with ID=2
20-Jun-18 18:26:23.606 - DOFLinx device:4 LEDWiz setup with 32 outputs
20-Jun-18 18:26:23.606 - 1 FTDI (Sainsmart) device(s) found
20-Jun-18 18:26:23.606 - DOFLinx Device: 5 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
20-Jun-18 18:26:23.606 - DOFLinx device:5 FTDI (Sainsmart) setup with 8 outputs
20-Jun-18 18:26:23.616 - 0 Ultimate IO device(s) found
20-Jun-18 18:26:23.616 - Reading DOFLinx.INI startup config file details
20-Jun-18 18:26:23.631 - Reading DirectOutputConfig file named E:\DirectOutput\config\directoutputconfig.ini
20-Jun-18 18:26:27.834 - Game name = 'Fake'
20-Jun-18 18:26:27.849 - Named process detected and startup commenced
20-Jun-18 18:26:27.865 - 1 Pinscape device(s) found
20-Jun-18 18:26:27.865 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Jun-18 18:26:27.881 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Jun-18 18:26:27.881 - 3 LEDWiz device(s) found
20-Jun-18 18:26:27.896 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=1
20-Jun-18 18:26:27.896 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Jun-18 18:26:27.896 - DOFLinx device: 3 Initializing as LEDWiz #2 with ID=0
20-Jun-18 18:26:27.896 - DOFLinx device:3 LEDWiz setup with 32 outputs
20-Jun-18 18:26:27.912 - DOFLinx device: 4 Initializing as LEDWiz #8 with ID=2
20-Jun-18 18:26:27.912 - DOFLinx device:4 LEDWiz setup with 32 outputs
20-Jun-18 18:26:28.066 - 1 FTDI (Sainsmart) device(s) found
20-Jun-18 18:26:28.213 - DOFLinx Device: 5 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
20-Jun-18 18:26:28.235 - DOFLinx device:5 FTDI (Sainsmart) setup with 8 outputs
20-Jun-18 18:26:28.251 - 0 Ultimate IO device(s) found
20-Jun-18 18:26:28.266 - Using full colour palette

Attached Files

•  DOLLINX-5.jpg   31.89KB   1 downloads

Edited by Outhere, 20 June 2018 - 11:52 PM.

[TerryRed]

if you have dof r3++ installed....and you have sainsmart configured in a cabinet.xml, then you "may" need to remove the sainsmart from the cabinet.xml because dofr3++ now autodetects sainsmart.

[Outhere]

Using dof r3++

Not in cabinet.xml

if you have dof r3++ installed....and you have sainsmart configured in a cabinet.xml, then you "may" need to remove the sainsmart from the cabinet.xml because dofr3++ now autodetects sainsmart.

[DDH69]

Once you add a SainSmart device it forces the output devices to be closed in between when DOFLinx is activated by a running process.  The reason for this is that the USB driver for a SainSmart can only handle one process talking to it at a time.  (this is why I don't like them!).

 

So I'm not sure if it is your issue, but you have now changed the way DOFLinx is working.  The close between process activation's can be forced via a parameter, but at work (midday here) I can't remember what its called.  You'll find it in the guide.

 

The issue becomes if you use any DOFLinx functions that need the output devices open in between being activated by running processes, then you can no longer do this and this may be causing you the issue.

 

To test if it is the SainSmart, or the change in the way things run, I'd suggest

1) disconnect the SainSmart cable

2) Check if things start up OK again

3) Find the parameter to force closing devices, turn it on with the SainSmart still disconnected

4) See if you get the same error

 

All very brief I know, but wanted to do a quick "brain dump" to try and help you keep moving.

[Outhere]

Everything works fine if I do not use the SainSmart..

After adding the parameter To force closing devices turned on with the SainSmart disconnected I do not get the Error...

It would appear the SainSmart board does that like the KL25Z microcontroller board, So the SainSmart board will have to go.

  Thanks TerryRed And DDH69 for your Help

[DDH69]

Glad to help.  Looks like some boosted outputs for the LEDWiz or Pinscape to me

[supermario0523]

So if I understand this correctly, there really is no viable workaround for the "Index outside the bounds" issue? 

 

I got everything to work on Pinball FX3 and DOFLinx... but as soon as I open PBX or VPX, and try to open up FX3 again, all bets are off. I'm trying to look for a process that VPX creates that I can have it close on exit that would allow the DOFLinx to talk to the FTDI device again, but I'm not seeing anything in system processes. 

[DDH69]

The issue that this thread relates to was never pursued to conclusion since Outhere took another path.