kevin bates
Hi (first first time post)
I have an ICD dash on our car and when trying to communicate using the Pi Toolset i get the following error
Unable to understand the contents of this setup. Please contact your support representative.
click OK and in the top left where the ICD1346 icon is the rotating circle indicating busy is constantly there no matter how long you wait
The toolset does appear to recognise the das as I get the following version info displayed
Bootloader- CHP55xx Boot Loader 4.0 Apr
Operating system - Theta 6.18.2 (Relaease)
Application - 10.6.2
Display - 1.1.1.0
Dash - Dash 1.7.92.4
Setup Manager - Setup Manager 1.7.92.4
Code Loader - Code Loader 1.0.52.0

The device data shows the following
Metadata - 10.00
Variant 6.3

Has anyone any pointers?

Quote 0 0
Rob_Jarvis
Hi Kevin,

Welcome to the site!

I presume you get the "Unable to understand the contents of this setup" message when you try and read the setup from the device?

Thank you very much for providing the code versions etc of the ICD, could you also please let us know what version of Toolset you are using?

Typically this message is shown when an older version of Toolset is being used with a newer version of ICD / Other CHP device code. Therefore Toolset doesn;t understand the device because one is newer than the other.

Many thanks and best regards,

Rob

Cosworth Support
Cosworth Electronics 

Quote 0 0
kevin bates
Hi Rob,

Thanks for the reply, hecking on the laptop I am running PiToolset4.7_1754.0

Is there a newer one than this that I can update to?

Cheers

kev 
Quote 0 0
Rob_Jarvis
Hi Kevin,

Apologies for the delayed response. I would expect that version of Toolset to normally be ok. Is this a Toolset setup you have used before or one that somebody sent to you?

Many Thanks,

Rob

Cosworth Support
Cosworth Electronics 

Quote 0 0
kevin bates
Hi Rob,

Bottomed the issue, on the laptop I was using hit had 2 versions of toolset (was unaware of this) used the later version 5.2 and communicated straight away
Thanks for your help
Quote 0 0
kevin bates
Rob,

To continue on this topic I have as mentioned communicated to my dash, however since making a minor change to 1 display value and sending it back to the device, after the sucessful message displayed in Toolset I now have a dash with no readings displayed, no extra page/dash displays etc As if it is an unconfigured dash.
If i switch off and restart and read from active device al the dash is showing correctly in Toolset and I can make changes here, but yet the actual dash doesn't change

Any ideas?
Quote 0 0
Rob_Jarvis
Hi Kevin,

Glad to hear you got the setup communications working. I expected it would be something like this, that your setup was compiled with a newer version of Toolset with a different major version which isn't backwards compatible.

With regards to your other enquiry. What was the change that you made? If you revert the change back does it fix the issue? Does the ICD still show the channels etc but just zero's or default vale? Or do you just get the Cosworth screen which means there are no active display pages?

Again if you are able to upload pics this might be easier to identify.

The fact that you are still getting the correct data etc in Toolset would indicate that the ICD is receiving the information ok. Sounds like a display setup configuration based on your description but if you are able to provide the info mentioned I'll have a better idea.

Many thanks,

Rob

Cosworth Support
Cosworth Electronics 

Quote 0 0
kevin bates
Hi Rob,

The changes I made were as follows.
I changed the vehicle voltage reading to indicate 1 decimal point instead of 2 as shown in the image below after alteration and
The data transmission was succesful but the screen refreshed and after a cycle with the cosworth screen the values in the main screen read either zero or default values 040.JPG 

What is even stranger, I have just repeated the sending the nfo to the device process again and this time it has loaded ok. I haven't changed anything with the dash or Laptop.
Guess a bug or something but all working ok again.

Quote 0 0