Multiecuscan

Subject to the version 2.7.0.0 was all right now, your new version of me by mistake andI can not get inside CAN Setup / PROXI Alignment Procedure will post photos of the error everything works but does not work CAN Setup / PROXI Alignment Procedure






I await a response with exchange installed the 2.7.0.0 version anyway!

angelootacon wrote:Subject to the version 2.7.0.0 was all right now, your new version of me by mistake andI can not get inside CAN Setup / PROXI Alignment Procedure will post photos of the error everything works but does not work CAN Setup / PROXI Alignment Procedure

I await a response with exchange installed the 2.7.0.0 version anyway!

This is a special function which I implemented after version 2.7... It does not allow you to do PROXI programming if the ELM interface does not read correct data from the Body Computer. It happens with some ELM interfaces.
This function was implemented to protect users from damaging their car!

The program shows error "Unreliable communication detected" when it detects this kind of problem.
Try with another ELM interface.

I tried to do proxy-alignment of my 2005 Stilo using version 2.8.1

Said it had completed so I checked only to find it hadn't done it.

Does 2.8.1 allow proxy-alignment of a Stilo Climate Control Node?

Log file
Climate Control Node (NCL)
Passenger Door Node (NPP)
CAN MODULES THAT REQUIRE EOL PROGRAMMING:
Body Computer Node (NBC)
Dashboard Node (NQS)
Climate Control Node (NCL)
04/05/2011 17:25:30
CONNECTED TO:
FIAT STILO 1.9 JTD
CAN Setup / PROXI Alignment Procedure
--------------------------------------------------------------

CURRENTLY CONFIGURED CAN MODULES::
Body Computer Node (NBC):
Engine Control Node (NCM):
Electric Steering Node (NGE):
Dashboard Node (NQS):
Steering Wheel Controls Node (NVO):
Brake System Node (NFR):
Info-Telematic/Convergence Node (NIT/NCV):
Driver Door Node (NPG):
Boot Node (NVB):
Climate Control Node (NCL):
Passenger Door Node (NPP):
:
CURRENTLY AVAILABLE CAN MODULES::
Body Computer Node (NBC):
Engine Control Node (NCM):
Electric Steering Node (NGE):
Dashboard Node (NQS):
Steering Wheel Controls Node (NVO):
Brake System Node (NFR):
Info-Telematic/Convergence Node (NIT/NCV):
Driver Door Node (NPG):
Boot Node (NVB):
Climate Control Node (NCL):
Passenger Door Node (NPP):
:
CAN MODULES THAT REQUIRE EOL PROGRAMMING::
Body Computer Node (NBC):
Dashboard Node (NQS):
Climate Control Node (NCL):

EXECUTING ADJUSTMENT...
PROXI Alignment Procedure
Writing CAN configuration data ...
Writing to module: Body Computer Node (NBC)SUCCESS!
Writing to module: Dashboard Node (NQS)SUCCESS!
Writing to module: Climate Control Node (NCL)SUCCESS!
COMPLETED

Shadeyman wrote:I tried to do proxy-alignment of my 2005 Stilo using version 2.8.1

Said it had completed so I checked only to find it hadn't done it.

Does 2.8.1 allow proxy-alignment of a Stilo Climate Control Node?

Does you ELM interface have a setting for "Latency"?
If yes, then set it to minimum and try again.

Please note that if you are using a Bluetooth ELM then the PROXI procedure will NOT work on Stilo Climate Control Node. It is a limitation of the Bluetooth interfaces!

yani wrote:

Shadeyman wrote:I tried to do proxy-alignment of my 2005 Stilo using version 2.8.1

Said it had completed so I checked only to find it hadn't done it.

Does 2.8.1 allow proxy-alignment of a Stilo Climate Control Node?

Does you ELM interface have a setting for "Latency"?
If yes, then set it to minimum and try again.

Please note that if you are using a Bluetooth ELM then the PROXI procedure will NOT work on Stilo Climate Control Node. It is a limitation of the Bluetooth interfaces!

Yes I'm using a Bluetooth interface, I'll try again with a cable interface.

Thanks Yani

Service coupons function for alfa 159 jtdm is supported?

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

************** Exception Text **************
System.InvalidProgramException: Common Language Runtime detected an invalid program.
at .()
at  .(Object , EventArgs )
at System.Windows.Forms.Form.OnShown(EventArgs e)
at System.Windows.Forms.Form.CallShownEvent()
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Multiecuscan2
Assembly Version: 2.8.1.0
Win32 Version: 2.8.1.0
CodeBase: file:///F:/Programmi/Multiecuscan/Multiecuscan2.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.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.

I have tested the software on different systems.
Here I noticed that the startup fails on systems with less than 2GB of RAM. It does not matter which version of .net Framework is installed.

Fishbone222 wrote:I have tested the software on different systems.
Here I noticed that the startup fails on systems with less than 2GB of RAM. It does not matter which version of .net Framework is installed.

What happens when you have more than 2GB? Program crashes? Doesn't connect?

I don't think that there is any problem with the memory requirements. I regularly test with my ASUS 900HA Netbook which is running Vista and has only 1GB of memory. I've NEVER had any problem with it. I also test with an old DELL Latitude which is running XP and has only 256MB of memory. Never had any memory problems with it either.

yani wrote:

angelootacon wrote:Subject to the version 2.7.0.0 was all right now, your new version of me by mistake andI can not get inside CAN Setup / PROXI Alignment Procedure will post photos of the error everything works but does not work CAN Setup / PROXI Alignment Procedure

I await a response with exchange installed the 2.7.0.0 version anyway!

This is a special function which I implemented after version 2.7... It does not allow you to do PROXI programming if the ELM interface does not read correct data from the Body Computer. It happens with some ELM interfaces.
This function was implemented to protect users from damaging their car!

The program shows error "Unreliable communication detected" when it detects this kind of problem.
Try with another ELM interface.

prejudice today, or try 2 interfaciue elm does not work and gives the same error ELM 327! Original!