Jagdave
Hi Cosworth,

I have a customer with a powerboat running four engines, each with their own SQ6 ECU.  Three of the ECUs are down due to salt water ingress and I need to pull the map from the fourth, healthy ECU, before sending them for repair.  Once they are back with me I shall need to program all of them with the existing map.
My question is this, what do i need to accomplish this?  I have downloaded Pi CalTool and understand the ECU connects to the laptop via Ethernet.  Do I need a subscription, dongle or other software to be able to connect to the ECU?  If so how do I go about getting what is necessary?
The ECU label has the following information:
PECTEL SQ6M
01E-500720
S/N 317 Iss 2/7
Tested HAN Nov06
I really appreciate your taking the time to help with my request.

Regards,

David Glanfield
Quote 0 0
littleozfella
Hi David,
              Firstly you need a personality, which is on the forum, this allows the software to operate to keep it simple.  you install the personality in a Folder in Caltool folder and just click on it before opening caltool.  Easy bit..  Next you need to try to connect to the ecu. You will not be able to connect fully, but when you get comms the system will tell you what level of code is in the ecu.. then somebody has to send you either a metafile, or a base dataset (Calibration map) so you can get access, IF the ecu is not locked, or on a factory Developer (this is where personalities come into play)  ECU pinouts and info are on Cosworth web..
Quote 0 0
Jagdave
Thanks for the prompt response.  The ECUs are en route from Florida, I'll no doubt be in touch again once they are here.
Quote 0 0
Jagdave
Hi,

I now have the ECUs in my hands.  Perhaps it's a basic question but - how do I connect to my laptop?  I was under the impression the connection is made via Ethernet but I do not see any access port on the ECU.  Do I need a dedicated cable/harness for this job?
Cheers,
David
Quote 0 0
littleozfella
Hi.. Yes. I sent you datasheets through Dropbox with the pin outs.. But without the original car loom you will need to purchase AS connectors to make a bench top loom.. 
Quote 0 0
Jagdave
Hello again,

I have made a harness and successfully established communications with one of the ECUs, the results are below
.2019-02-06 18_03_44-SQ6M_Report.docx - Word.png 
Doesn't look too promising does it?
Is there anything that can be done to recover this ECU through software?

The second ECU is not even showing up in Caltool, I have opened it up and cannot see anything obvious apart from some power transistors that have obviously been changed and the internal battery is completely discharged.  Any suggestions as to how to wake up this unit?

Cheers,

David
Quote 0 0
CosworthSupport
Hi David,

That message looks fine, it suggests that it doesn't have a dataset loaded into it so loading in a Caltool dataset should get you up and running.

The second one, it sounds like it either has an issue or could be developer locked. Did you try connecting with both serial and ethernet? Have you got a screenshot of the Caltool journal when set to Information filter level? If you can provide the full part number and serial number I can see if we have any history of this unit.

Had this ECU been opened up previously and the tamper proofs broken?

Unfortunately, as the ECU has been opened it will be classed as a major repair if it is sent back for us to investigate and will cost significantly more than it would if it hadn't previously been opened as we have no guaranty that further damage hasn't been caused as part of this process such as EMC static charge issues etc when it has been handled as an example.

I wouldn't expect the internal backup battery to affect connection to the unit.
Cosworth Support
Cosworth Electronics
Quote 0 0
littleozfella
Hi Support.
                 This is what I have been finding with ALL SQ* family ecu's ( and have reported) The older ecu's if left with a flat battery loose the calibration file,  More so the ecu seems to loose the base code, ie the firmware code, which will then result in the dataset being lost of course. I don't see how this is possible as this should be non volatile memory, but this does happen. If you resend the firmware code then send a dataset the ecu will hold this until the unit is power cycled. The ecu will then loose the code again depending on how long you have had the ecu powered up. Sometimes instantly, sometimes after an hour or so..  Change to new battery and all works fine again.  
Quote 0 0
Jagdave
Thanks guys, I really appreciate your taking the time to help me with this.
For what they cost, it is worth me changing the batteries first.  After that is done I will, hopefully, be able to communicate with the ECUs and load the firmware/dataset.
@Support  When I received the units they had already been opened and had some work done (replacement power transistors) so if they cannot be recovered then I understand what must be done!  I will attempt to communicate with serial as well as Ethernet as you suggest.
For information the model and serial numbers are as follows:

01E-5007230
S/N 300 Iss 2/17
Tested GW Aug.13

01E-500720
S/N 317 Iss 2/7
Tested HAN Nov06
Quote 0 0
CosworthSupport
Hi David,

From what I can find out #300 is unlocked with the standard Pectel External developer.

#317 I can't find any build records it at present. I suspect as we haven't seen it for ~13 years it out dates this current office. Looking at who it was sold to, there is a potential that it could be developer locked as I know the customer it was sold to originally, does now use their own developers.
Cosworth Support
Cosworth Electronics
Quote 0 0
Jagdave
Okay, so i fitted new batteries to the ECUs but the result is the same.  I have attached a screen shot from the only ECU with some kind of communication.  I can see the message in red "No dataset loaded; No dataset present on device" and also at the very bottom of the screen (SQ6M empty).  In the journal I can see a record stating "Failed to load dataset from device".  I am guessing this is not good, correct?  The personality in use is Pectel External (Customer).
Does all this mean simply that there is no map stored in the ECU?

The other ECU is not recognised at all by PiCalTool, is there a different means of communicating available, serial perhaps?

I am sure these are very basic questions to you all but I would appreciate it if you would bear with me!

Cheers,

David
Quote 0 0
littleozfella
Hi mate
              Yes that is because there is no dataset in the ecu, it is blank. I would recommend you update the ecu to latest version (you do this on the benchtop using RS232) for both ecu's. then send a startup file I have sent you on dropbox..  unfortunately there is no way to recover old files.. 

Cheers..
Quote 0 0