SoDiezl350 wrote:Just wanted to come in here and give a big thanks to everyone who contributed to this tool's development.
I also wanted to confirm what another member posted regarding being unable to get a VCX Nano (GM MDI/GDS2) to connect to my bench E67, despite the tool appearing to have initialized successfully.
On the bright side, I was able to read and write both stock and modified calibrations using an Amazon SM2 Pro clone without issue.
How did you manage to get initial connection to tool. Did you fake it it was mdi or some other way. I tried to configure it for other devices, but only mdi and dice are available for selection.
kur4o wrote:
How did you manage to get initial connection to tool. Did you fake it it was mdi or some other way. I tried to configure it for other devices, but only mdi and dice are available for selection.
Not sure if this is what he did but you can point the J2534 selection to point at a different dll.. I tried the mdi2 dll and If I remember right ti failed. I don't have any other j2534 device to try besides the gm mdi..
Was curious and download it
I have ObdLink SX
Got it after choosing com port
_________________________________________
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at PowerPCM_Flasher.Hauptfenster.comboBoxToolArg1_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.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.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** 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.
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.
Clones are clones, even if someone got one that worked you cant tell what the next one will be. You can try it, but you never know. Even the genuine ones wont do VPW/PWM protocol, but this is CAN so it might be ok.
Sorry if it been mentioned before but i had a look over this post and didn't see it mentioned, when i select the .dll location than try to Initialize the j2534 tool the program shuts down. iam using the obdx pro gt that might be reason ?
mechfab wrote:Sorry if it been mentioned before but i had a look over this post and didn't see it mentioned, when i select the .dll location than try to Initialize the j2534 tool the program shuts down. iam using the obdx pro gt that might be reason ?
What windows OS are you running ? (7,10, 11?) and is it 32bit or 64bit?
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
mechfab wrote:Sorry if it been mentioned before but i had a look over this post and didn't see it mentioned, when i select the .dll location than try to Initialize the j2534 tool the program shuts down. iam using the obdx pro gt that might be reason ?
What windows OS are you running ? (7,10, 11?) and is it 32bit or 64bit?
Os 10, 64bit if i recall correctly. Would need to double check..
Maybe this has been mentioned already, but is there a GitHub page for this great program so I know I have the most up to date? I might have an E67 in a 2008 Trailblazer 4.2L to experiment with.
