Jump to content


Photo

Shout Out To Mems_Diag


  • Please log in to reply
35 replies to this topic

#31 AeroNotix

AeroNotix

    Mini Mad

  • Noobies
  • PipPipPipPip
  • 267 posts
  • Location: Krakow (Blackpool, originally)

Posted 25 August 2017 - 11:51 AM

Not sure what your objective is ?

You want to know so you don't have to purchase something that someone else has spent time and money to develop?

Or from a technical interest point of view?

I'm guessing here but the earlier protocols could probably be worked out from analysing a proprietary code reader or if you were that way inclined reading the software code on the units EPROMs (which could be an infringement of the owners copywrite)

FS

 

 

I personally don't believe it's in the entire community's interest to have the protocols hidden behind what are essentially paywalls.  I understand why the people who have developed the software and hardware have done it, I personally wouldn't have but I understand the motives.

 

Obviously that's how you dump the protocol. You need an existing reader and a couple pieces of equipment to read the protocol as it's going over the wire. The thing is, the investment into a) getting a reader and b) the debugging equipment is quite expensive and you end up with a reader any way.

 

I also question the legality of what pscan.eu et al have done themselves any way. Surely reverse engineering the protocol that the various readers have done is infringing some part of the T&C that was agreed upon purchasing those readers, selling that on as a product might be questionable.

 

I very much doubt it's a worthwhile endeavour to try to dump the EPROMS or any code from the ECU itself an easier method is simply to capture the traffic going through the proprietary readers and figure out what's going on there.

 

EDIT: 

 

Not to mention that the tools that pscan gives you are quite limiting according to the website you can only use the scanner on two computers and to change this you need to contact pscan. You *must* use their software to view the data. It all sounds very limited and creates an artificial barrier to people building more complex and useful features around simply talking to the mini's ECU. Look at the applications available for ODBII-based diagnostics on modern cars. There's a whole raft of apps and dashboards and interesting things you can do with it. That's all down to the fact that the protocol is standardized and not intentionally hidden away behind paywalls.

 

Please, I totally understand the argument that someone has done work to reverse engineer the protocols and provide a product to solve one of the needs. However, what pscan has done is simply add to the existing number of readers available and not hugely expanded the possibilities of being able to use the mini's ECU. 


Edited by AeroNotix, 25 August 2017 - 11:59 AM.


#32 FlyingScot

FlyingScot

    Up Into Fourth

  • TMF Team
  • PipPipPipPipPipPipPipPipPip
  • 2,660 posts
  • Location: Inverclyde Scotland
  • Local Club: Mini Cooper Register

Posted 25 August 2017 - 01:25 PM

Sorry I don't buy your reasoning.
The code was paid for and developed by Rover and wasnt intended to be open to others unlike the EOBD and later protocols.
In any case in the later protocols only some of the features are common, there are still specific model features which need custom devices which cost.
What you want is help to know how to do it without any effort on your part; citing cost of code readers, data analysis equipment etc as a barrier. Then complaining that other companies who have created options and had to buy and pay for the same equipment and spend their time to do it want to charge for it.

You don't know how pscan or others have developed their system so take care saying it's reverse engineering...
So we are clear I am nothing to do with either of the developments you cite but I have bought with my money and tried in my time most of the proper code readers which work on our cars - this is listed in the pinned section

FS

Edited by FlyingScot, 25 August 2017 - 01:28 PM.


#33 AeroNotix

AeroNotix

    Mini Mad

  • Noobies
  • PipPipPipPip
  • 267 posts
  • Location: Krakow (Blackpool, originally)

Posted 25 August 2017 - 02:06 PM

Sorry I don't buy your reasoning.
The code was paid for and developed by Rover and wasnt intended to be open to others unlike the EOBD and later protocols.
In any case in the later protocols only some of the features are common, there are still specific model features which need custom devices which cost.
What you want is help to know how to do it without any effort on your part; citing cost of code readers, data analysis equipment etc as a barrier. Then complaining that other companies who have created options and had to buy and pay for the same equipment and spend their time to do it want to charge for it.

You don't know how pscan or others have developed their system so take care saying it's reverse engineering...
So we are clear I am nothing to do with either of the developments you cite but I have bought with my money and tried in my time most of the proper code readers which work on our cars - this is listed in the pinned section

FS

 

I'm not saying I don't want to put effort into reverse engineering the protocol. I am saying that there's a barrier to entry that is quite high. Not saying I am not debating doing it. I think in the long run it could be worth while. I am asking for any help people may have. Why wouldn't I? If there's someone around that could provide any information whatsoever, it would be appreciated. I'm sure any one who reverse engineered these protocols did some preliminary searching for what else exists. It's just logical to do that.

 

I do know how pscan has implemented it. Over on the rover-tech forums the pscan.eu account has mentioned several times that in order to implement support for specific ECUs they need an original code reader to reverse engineer.

 

In any case, even if pscan didn't mention that. What other methods would there be? There's not much left that's within reason.



#34 Carvell

Carvell

    Speeding Along Now

  • Members
  • PipPipPipPipPip
  • 316 posts
  • Location: North West

Posted 26 August 2017 - 05:38 PM

Out of interest what is the difference between what pscan does and what an Sykes ACR4 can do?

#35 AeroNotix

AeroNotix

    Mini Mad

  • Noobies
  • PipPipPipPip
  • 267 posts
  • Location: Krakow (Blackpool, originally)

Posted 27 August 2017 - 03:17 PM

Pscan can talk to a few ECUs without different software and you use your computer to talk to it rather than a small lcd.

#36 tmsmini

tmsmini

    One Carb Or Two?

  • Members
  • PipPipPipPipPipPipPip
  • 709 posts
  • Local Club: MOASF

Posted 28 August 2017 - 02:18 PM

There are different functions with the various SP ACR combinations of handset and pod, so it is difficult to make a direct functional comparison.

FlyingScot's breakdown in the pinned topic gives a good overview for the SP tools.

 

I do not have experience with Pscan, but they do share some screenshots on their site.

MPi:http://pscan.eu/features/mems2j.html

 

 

Reading live data on a PC screen would be a benefit compared to the SP ACR LCD that requires scrolling.

It is not clear to me if the data can be logged.

Terry






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users