OBDLink MX+
-
- Posts: 16
- Joined: Mon Apr 05, 2021 12:04 pm
- cars: I have 4 w-body’s 2 Silverado’s 1 Yukon 2 cavaliers
OBDLink MX+
Keeps showing this one is not supported.
- antus
- Site Admin
- Posts: 8258
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: OBDLink MX+
Scantool keep changing their products. They know pcmhamer exists and they gave us details for their products when we wrote it but we cant keep up and we get nothing from this. We put a catchall in there so it'll work with unknown scantool interfaces but if you want it work faster you'll need to test and update pcmhammer yourself (and submit your improvements so we can put it in the tool for everyone), or lean on scantool and see if they'll update it, or just use it as is. scantool have not been a good company to work with and personally im done with putting more effort in for their profits. Anyone can get the source code, look at the scantool init code, add add new variations of interfaces and test larger packet sizes.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
-
- Posts: 16
- Joined: Mon Apr 05, 2021 12:04 pm
- cars: I have 4 w-body’s 2 Silverado’s 1 Yukon 2 cavaliers
Re: OBDLink MX+
It won’t let me use it at all I’ve tired all day. Should have just bought the corded one only got this because it showed it works with ford to. But I seen others posting that the OBDLink MX+ worked for them but that was 2 years ago.
-
- Posts: 16
- Joined: Mon Apr 05, 2021 12:04 pm
- cars: I have 4 w-body’s 2 Silverado’s 1 Yukon 2 cavaliers
Re: OBDLink MX+
Does the OBDLink SX still work ?antus wrote:Scantool keep changing their products. They know pcmhamer exists and they gave us details for their products when we wrote it but we cant keep up and we get nothing from this. We put a catchall in there so it'll work with unknown scantool interfaces but if you want it work faster you'll need to test and update pcmhammer yourself (and submit your improvements so we can put it in the tool for everyone), or lean on scantool and see if they'll update it, or just use it as is. scantool have not been a good company to work with and personally im done with putting more effort in for their profits. Anyone can get the source code, look at the scantool init code, add add new variations of interfaces and test larger packet sizes.
- antus
- Site Admin
- Posts: 8258
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: OBDLink MX+
BT is hard on windows. Its probably showing up as 2 ports and probably the other one will work. Which one works is random when they hook up to windows and it changes. I can no longer vouch for scantool. I can say i'd expect the wired one to work but I have no way to test it. You're better off with an obd xpro or a vcx nano in that price range.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
-
- Posts: 16
- Joined: Mon Apr 05, 2021 12:04 pm
- cars: I have 4 w-body’s 2 Silverado’s 1 Yukon 2 cavaliers
Re: OBDLink MX+
Yeah shows 2 coms but only one will connect just to say this scan tool device is not supported. And com 4 just freezes the software. Guess I’ll send this one back.
Re: OBDLink MX+
The only part I agree with Antus on is Blue Tooth and Windows do not work well together!
A Debug log would be very helpful, without it, it's only guess work!
I have gotten the MX+ to work for others, and I would like to at least know the chip id on that MX+, it would be in a PCMHammer debug log.
One created when PCMHammer reports: This device is not supported!
Thank you!
-Enjoy
A Debug log would be very helpful, without it, it's only guess work!
I have gotten the MX+ to work for others, and I would like to at least know the chip id on that MX+, it would be in a PCMHammer debug log.
One created when PCMHammer reports: This device is not supported!
Thank you!
-Enjoy
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
-
- Posts: 16
- Joined: Mon Apr 05, 2021 12:04 pm
- cars: I have 4 w-body’s 2 Silverado’s 1 Yukon 2 cavaliers
Re: OBDLink MX+
I’ll see if I can find it but I deleted it all and reinstalled it 3 times to see if that was the problem. How did you get it to work for the others ?Gampy wrote:The only part I agree with Antus on is Blue Tooth and Windows do not work well together!
A Debug log would be very helpful, without it, it's only guess work!
I have gotten the MX+ to work for others, and I would like to at least know the chip id on that MX+, it would be in a PCMHammer debug log.
One created when PCMHammer reports: This device is not supported!
Thank you!
-Enjoy
- antus
- Site Admin
- Posts: 8258
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: OBDLink MX+
when it says its unsupported its talking to the obdlink ok, and will work. if the blutooth is disconnected and brought back up and you dont get that warning when you initialize then its on the wrong port. if its talking to the obdlink the problem is car / bench side. ignition not on or another electrical problem.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
-
- Posts: 16
- Joined: Mon Apr 05, 2021 12:04 pm
- cars: I have 4 w-body’s 2 Silverado’s 1 Yukon 2 cavaliers
Re: OBDLink MX+
[10:17:43:867] Loaded credits.html from network.
[10:17:43:898] Loaded help.html from network.
[10:17:44:007] Loaded start.txt from network.
[10:17:44:007] Thanks for using PCM Hammer.
[10:18:02:220] ElmDevice initialization starting.
[10:18:04:675] TX:
[10:18:04:706] TX: AT Z
[10:18:05:620] AT Z ELM327 v1.4b
[10:18:05:620] TX: AT E0
[10:18:05:635] AT E0 OK
[10:18:05:635] TX: AT S0
[10:18:05:651] OK
[10:18:05:651] TX: AT RV
[10:18:05:651] Voltage: 12.1V
[10:18:05:651] TX: AT I
[10:18:05:667] Elm ID: ELM327 v1.4b
[10:18:05:667] Initializing PcmHacking.AllProDeviceImplementation
[10:18:05:667] TX: AT #1
[10:18:05:682] This is not an AllPro device.
[10:18:05:682] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[10:18:05:682] TX: ST I
[10:18:05:689] ScanTool device ID: STN2256 v5.6.24
[10:18:05:689] This ScanTool device is not supported.
[10:18:05:689] Please check pcmhammer.org to ensure that you have the latest release.
[10:18:05:689] We're going to default to very small packet sizes, which will make everything slow, but at least it'll probably work.
[10:18:05:704] TX: STPTO 3000
[10:18:05:704] OK
[10:18:05:704] TX: AT AL
[10:18:05:720] OK
[10:18:05:720] TX: AT SP2
[10:18:05:720] OK
[10:18:05:720] TX: AT DP
[10:18:05:736] SAE J1850 VPW
[10:18:05:736] TX: AT AR
[10:18:05:736] OK
[10:18:05:736] TX: AT AT0
[10:18:05:736] OK
[10:18:05:751] TX: AT SR F0
[10:18:05:751] OK
[10:18:05:751] TX: AT H1
[10:18:05:751] OK
[10:18:05:751] TX: AT ST 20
[10:18:05:767] OK
[10:17:43:898] Loaded help.html from network.
[10:17:44:007] Loaded start.txt from network.
[10:17:44:007] Thanks for using PCM Hammer.
[10:18:02:220] ElmDevice initialization starting.
[10:18:04:675] TX:
[10:18:04:706] TX: AT Z
[10:18:05:620] AT Z ELM327 v1.4b
[10:18:05:620] TX: AT E0
[10:18:05:635] AT E0 OK
[10:18:05:635] TX: AT S0
[10:18:05:651] OK
[10:18:05:651] TX: AT RV
[10:18:05:651] Voltage: 12.1V
[10:18:05:651] TX: AT I
[10:18:05:667] Elm ID: ELM327 v1.4b
[10:18:05:667] Initializing PcmHacking.AllProDeviceImplementation
[10:18:05:667] TX: AT #1
[10:18:05:682] This is not an AllPro device.
[10:18:05:682] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[10:18:05:682] TX: ST I
[10:18:05:689] ScanTool device ID: STN2256 v5.6.24
[10:18:05:689] This ScanTool device is not supported.
[10:18:05:689] Please check pcmhammer.org to ensure that you have the latest release.
[10:18:05:689] We're going to default to very small packet sizes, which will make everything slow, but at least it'll probably work.
[10:18:05:704] TX: STPTO 3000
[10:18:05:704] OK
[10:18:05:704] TX: AT AL
[10:18:05:720] OK
[10:18:05:720] TX: AT SP2
[10:18:05:720] OK
[10:18:05:720] TX: AT DP
[10:18:05:736] SAE J1850 VPW
[10:18:05:736] TX: AT AR
[10:18:05:736] OK
[10:18:05:736] TX: AT AT0
[10:18:05:736] OK
[10:18:05:751] TX: AT SR F0
[10:18:05:751] OK
[10:18:05:751] TX: AT H1
[10:18:05:751] OK
[10:18:05:751] TX: AT ST 20
[10:18:05:767] OK