Project properties signature error w/CAN device

[jsiedlicki]

Using TS 3.0.10; MS3-Pro v1.5 Alpha 4; TinyIOx v 0.2.0

When online with the controller I get the following error opening the project properties and clicking on the TinyIOx CAN device.

properties_error.PNG

I did check the TinyIOx signature file as the dialog suggests and it is correct.
This happens with firmware 1.4.1, 1.4.2. beta 1, and 1.5 alpha 4.

[Alfagta]

I have noticed the same issue.

I think TS is asking for the version info rather then signature.
It should ask for the signature.

The issue exist since a while.

BR

[LT401Vette]

TunerStudio is giving you both the Firmware version and the serial signature.. You need to do as the dialog says and browse to the ini for the TinyIOx ini file..
Not the ini for your MS3, the ini for the IOx as the dialog says.

[jsiedlicki]

I have browsed for the TinyIOx file and get the same issue. Jean has also verified I am using the correct TinyIOx ini file and firmware version.

Any other ideas?

[racingmini_mtl]

The ini file asked for by TS is already in the project and contains the correct signature. I don't see why TS is asking for a new one.

Maybe a comm debug log would help out.For that you would need to go to the TunerStudio directory and delete the TunerStudioAppDebug.txt file then start TunerStudio, enable the comm debug log option under the Communications menu and then load your project. The newly created TunerStudioAppDebug.txt file should have useful information so either post it here or send it to Phil.

Jean

[jsiedlicki]

Great idea. Debug log posted below.

[jsmcortina]

I had a quick look. Seems like you forgot to enable the "comm log debug". What's the deal with the unresponsive GPS on COM5 ?

Did that show an error? There are no errors with the TinyIOx reported that I could see.

James

[jsiedlicki]

That might help, sorry. Here is a debug file with the com log debug enabled.

The GPS messages are from a bluetooth GPS I have on the laptop that is not currently in range. I disabled the GPS in TS so that error is not there anymore.

[LT401Vette]

Comm Debug is still not on...

If I am getting you right, you are not getting an error when going online, just when you open the Project Properties dialog while it is online.
I'm not in a place where I have any CAN hardware to try it out, that will be at least Monday.

[jsmcortina]

I tried here with an MS3 and an IO-x with an older firmware. It wasn't misbehaving?

James

[jsiedlicki]

Comm Debug is still not on...

Sorry about that, I did not know that the setting does not persist between TS sessions. I have attached the debug log below.

If I am getting you right, you are not getting an error when going online, just when you open the Project Properties dialog while it is online.
I'm not in a place where I have any CAN hardware to try it out, that will be at least Monday.

Correct, the error only occurs when online with the ECU and checking the properties dialog box.

[jsiedlicki]

I tried here with an MS3 and an IO-x with an older firmware. It wasn't misbehaving?

James

Perhaps Jean can try it out with the latest firmware that I am using to see if he can reproduce the error?

[Alfagta]

Hello at all,

i have played a liitle bit with this part.
It seems that in TS its hard coded to request the signature at Table 15 an the version at table 14.
When the project is opend TS is looking for the tables in the ini file, but at the can devices settings page and the read for connected devices ts is requesting
signature at table 15 and version at table 14 with fix 20 and 60 bytes...
Now i know to take care about this...
It's not covered anywhere that TS is using this precedure..

BR

[jsiedlicki]

...It seems that in TS its hard coded to request the signature at Table 15 an the version at table 14.

Is this not the way it is supposed to be querying for the signature and version?

Any progress on why this is happening and does it effect proper operation?

[LT401Vette]

...It seems that in TS its hard coded to request the signature at Table 15 an the version at table 14.

Is this not the way it is supposed to be querying for the signature and version?

Any progress on why this is happening and does it effect proper operation?

That is how to query the signature in the MS CAN protocol.

The issue where TS keeps requesting the ini should be resolved in the current release.