chrislangdon
Hi, I have a Pectel T6 that I'm trying to communicate with via Descpro.  I've managed to get it booted and connected to the ecu via a serial cable and power supply I put together.  No comm wires in car... 
Ecu is recognized by descpro however I get this error when it connects. It will say connecting to ecu and then I get this screen,  See attached picture.

I guess my question would be, is this an issue with the version descpro or the fact that it says no profile loaded at the top.  Or both? 

My end goal is simply to get into the ecu and configure it to function with an AIM device, that's it.  No playing with the maps or anything else. 

If anyone could provide any insight as to what version of descpro I need or could provide the correct profile, it would be immensely appreciated.

Engine is a Cosworth built 2.3L (Duratec?) N/A.

Thanks, Chris  descproerror.jpg 




Quote 0 0
littleozfella
Hi   The ecu is a different developer (not PEXT) so thefore you cannot communicate with it.  IT is probably Mountune or Ford developer. Unless you know somebody with the tools to change it to PEXT then you will not be able to communicate with it.   If you can find out what developer it is and contact the company it would be a start. 
   cheers...
Quote 0 0
chrislangdon
The gentleman who owns the vehicle was informed that the ecu is a Pectel T6. Also, the ecu has Pectel branded on it. Unless it is a Pectel ecu with completely different software on it...which seems a little weird. I will dig further into its origins. The ecu does communicate to some extent as it says connecting to ecu prior to this message appearing.
Quote 0 0
littleozfella
Hi, sorry I will try to explain better...   Yes the ecu is a Pectel, but the software is a different "Developer".  How does this work?? Normally other ecu's have passwords to protect the engineer's calibrations.  While Pectel has this, there is also a more secure method by having different "developer's".  While the firmware is the same and the profile is most probably the same, the developer is effectively different software, the developers are specific software according to the "owner" of the developer. PEXT is a open developer. Being a Ford engine it is probably Mountune, Ford Motorsport or Field MS developer.  This way the software is much better protected as there is no "back door" codes to access the ecu. Using this method the developer owner can then supply the customer with cut down Profiles that allow the customer limited access to such things as coolant fans etc. The customer is free to change these values but cannot see or change the main tables like Ignition. Also if he "owner! of the developer can  can send a new calibration file to the customer to load to the ecu and the customer can change it without a password.  
         While the ecu can have the developers changed back to PEXT, I think at the moment T6 ECU's are not supported at Cosworth so you will need to contact the company that has set the developer..   Hope that makes sense...
Quote 0 0