Microsoft.net framework crash

Friends, help me find a mistake in the 2dof.

I do as directed by the instructions, but when I run SimTools signal to the motor does not go.

My print settings screens SimTools:

I start the engine test - the engine is not running.



include tests -Engine does not rotate (



I used this code to Arduino:
2DOF_Racingmat_Arduino_Code_and_Presets.zip


So I connected:

Arduino /..Motomonster
....GND <-> GND pin
.........5V <-> 5V
.....pin 4 <-> pin 4 inA motor1
.....pin 5 <-> pin 5 pwm1
.....pin 6 <-> pin 6 pwm2
.....pin 7 <-> pin 7 inA motor2
.....pin 8 <-> pin 8 inB motor1
.....pin 9 <-> pin 9 inB motor2

.....pinA0 <-> center pin of pot 1
.....pinA1 <-> center pin of pot 2
.....pinGND <-> 0 ohm's pin potentiometer 1 & 2
.....pin 5V <-> 10k ohm's pin potentiometer 1 & 2


Please tell me what I'm doing wrong?

EDIT by Pit: please do not upload any Arduino sketch to any of your postings, thank you.

Hi.

Test in Interface - Output L<Axis1a>R<Axis2a>

thanks) test run - the motor is running!

I launch the game (LFS), I see the error (

Thread title edited and moved.

Thanks for the help.

Code:

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

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): Запрос ReadProcessMemory или WriteProcessMemory был выполнен только частично
  at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
  at System.Diagnostics.ProcessManager.GetModuleInfos(Int32 processId)
  at System.Diagnostics.Process.get_Modules()
  at SimTools_GameManager.frmMain.tmr_IsGameRunning_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.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
SimTools_GameManager
  Assembly Version: 0.2.1.0
  Win32 Version: 0.2.1.0
  CodeBase: file:///C:/Program%20Files%20(x86)/SimTools/SimTools_GameManager.exe
----------------------------------------
xdFZySjlJvJuSyJCrKNFqiOVuiS
  Assembly Version: 0.0.0.0
  Win32 Version: 0.2.1.0
  CodeBase: file:///C:/Program%20Files%20(x86)/SimTools/SimTools_GameManager.exe
----------------------------------------
Microsoft.VisualBasic
  Assembly Version: 10.0.0.0
  Win32 Version: 14.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
Game_PluginAPI
  Assembly Version: 1.0.0.0
  Win32 Version: 1.0.0.0
  CodeBase: file:///C:/Program%20Files%20(x86)/SimTools/Game_PluginAPI.DLL
----------------------------------------
System.Management
  Assembly Version: 4.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
LiveForSpeed_GamePlugin
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.0.0
  CodeBase: file:///C:/Users/Oculus/AppData/Local/SimTools/GamePlugins/LiveForSpeed_GamePlugin.dll
----------------------------------------
Microsoft.GeneratedCode
  Assembly Version: 1.0.0.0
  Win32 Version: 4.6.1055.0 built by: NETFXREL2
  CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** 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:

<configuration>
  <system.windows.forms jitDebugging="true" />
</configuration>

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.
===================================================================