ECU Manager crashed when open MAP or connect to ECU

Questions about ECU Manager? Ask here.
STarsSerg
Posts: 3
Joined: Sun Feb 26, 2017 10:21 pm

ECU Manager crashed when open MAP or connect to ECU

Postby STarsSerg » Sun Feb 26, 2017 10:28 pm

Good day!
On my new laptop with Windows 10 ECU Manager 1.14/1.13.5 crashed when open MAP or connect to ECU.
Please help me run ECU Manager! All have tried, I can not understand that he is wrong.
Error:
product_name=&name=&email=&description=&exception_type=System.ArgumentException&exception_message=Cannot bind to the target method because its signature or security transparency is not compatible with that of the delegate type.&exception_stack_trace= at System.Delegate.CreateDelegate(Type type, Object firstArgument, MethodInfo method, Boolean throwOnBindFailure)
at System.Delegate.CreateDelegate(Type type, Object firstArgument, MethodInfo method)
at com.Company.ECUManager.Core.ECUMap.Filtering.Filter..ctor(Type classToProxy, Object target, FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Filtering.Filter.GetFilter[T](T target, FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_00.Sport2000_01_00.Sport2000_01_00_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_04.Sport2000_01_04.Sport2000_01_04_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_06.Sport2000_01_06.Sport2000_01_06_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_07.Sport2000_01_07.Sport2000_01_07_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_09.Sport2000_01_09.Sport2000_01_09_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_11.Sport2000_01_11.Sport2000_01_11_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_11.Sport2000_01_12.Sport2000_01_12_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_13.Sport2000_01_13.Sport2000_01_13_IOOptions..ctor(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.Versioning.V_01_13.Sport2000_01_13.Sport2000_01_13_ECUMap.CreateIOOptions(FunctionFilter filter)
at com.Company.ECUManager.Core.ECUMap.OldMap.get_MapResources()
at com.Company.ECUManager.Core.ECUMap.OldMap.get_Settings()
at com.Company.ECUManager.Core.ECUMap.ECUMap.GetSettingDependencies()
at com.Company.ECUManager.SwfUI.MainFrame.DisplayMap(IECUMap ecuMap)
at com.Company.ECUManager.SwfUI.MainFrame.OpenMapFile(String path)
at com.Company.ECUManager.SwfUI.MainFrame.OpenSelected(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run()
at com.Company.ECUManager.SwfUI.Program.Main(String[] args)&exception_type_2=&exception_message_2=&exception_stack_trace_2=&exception_type_3=&exception_message_3=&exception_stack_trace_3=&contactable=0

User avatar
HaltechMatthew
Haltech Staff
Posts: 3010
Joined: Tue Feb 07, 2012 12:45 pm
Location: Sydney, Australia
Contact:

Re: ECU Manager crashed when open MAP or connect to ECU

Postby HaltechMatthew » Thu Mar 30, 2017 4:19 pm

Call us and we can go through it.

STarsSerg
Posts: 3
Joined: Sun Feb 26, 2017 10:21 pm

Re: ECU Manager crashed when open MAP or connect to ECU

Postby STarsSerg » Fri May 24, 2019 11:35 pm

HaltechMatthew wrote:Call us and we can go through it.


Good day Matthew!
A lot of time has passed, used the old laptop! But the problem has returned! Installed the latest Win version 1903 (May 2019), and exactly but the same problem! I can not figure out what's wrong .... To call you is not feasible, I do not speak English well, we do not understand each other)
Maybe tell me what to look for and where to look.

User avatar
HaltechMatthew
Haltech Staff
Posts: 3010
Joined: Tue Feb 07, 2012 12:45 pm
Location: Sydney, Australia
Contact:

Re: ECU Manager crashed when open MAP or connect to ECU

Postby HaltechMatthew » Mon May 27, 2019 10:18 am

There are only a handful of issues that can come up, and keep in mind I am a car guy and not an IT guy:
1. .NET 2 is not installed.
2. DirectX 9.0c is not installed.
3. Windows Security is blocking 3rd party software access to Documents Folder. Try running as Admin.
4. The config file is somehow (very rare) missing or corrupted. It is in a hidden Windows directory.
C:/Users/<your username>/AppData/Local/Haltech then delete the ECU Manager folder. The software will re-create it next time it starts.
5. You have a bad page layout. Remove them all and start fresh.

There was also a Windows drive update that caused issues when Microsoft decided to force update a new driver. Updating the driver from the manufacturer will solve that.
https://www.silabs.com/documents/public ... rivers.zip

STarsSerg
Posts: 3
Joined: Sun Feb 26, 2017 10:21 pm

Re: ECU Manager crashed when open MAP or connect to ECU

Postby STarsSerg » Mon Jun 10, 2019 2:47 am

HaltechMatthew wrote:There are only a handful of issues that can come up, and keep in mind I am a car guy and not an IT guy:
1. .NET 2 is not installed.
2. DirectX 9.0c is not installed.
3. Windows Security is blocking 3rd party software access to Documents Folder. Try running as Admin.
4. The config file is somehow (very rare) missing or corrupted. It is in a hidden Windows directory.
C:/Users/<your username>/AppData/Local/Haltech then delete the ECU Manager folder. The software will re-create it next time it starts.
5. You have a bad page layout. Remove them all and start fresh.

There was also a Windows drive update that caused issues when Microsoft decided to force update a new driver. Updating the driver from the manufacturer will solve that.
https://www.silabs.com/documents/public ... rivers.zip



Good day!
All problems are gone after a complete update of Windows 10. Something happened with the assembly of the distribution kit that I installed...
Thank you.


Return to “ECU Manager”

Who is online

Users browsing this forum: No registered users and 0 guests