Crazy DSP problems

[Redbowties88]

Well for starters just to let everyone know i switch tunes via v2 not a switch. ive been doing so for some time now and never had a problem.

so the story begins, i was making a routine change to one of the DSP folders (#1 to be exact) and i go to do a calibration flash. once the sequence starts i get an error. i forget what it said word for word but basically it said i cannot unlock the ecm. so i try again, this time with alt keys. works fine like usual and truck runs great. i go to change tunes to the new one to try it out and it wont let me. it says "tune switching is not supported in the modules calibration" stumped at this i check the tune, all is well. then i loaded an old tune (again one that i know works) and i did it via full reflash. this didn't work same thing happened. then i tried making a new DSP tune from scratch and that didn't work either. all the times loading worked fine without using alt keys except one. it gave me the same message as the first one. but ive loaded more tunes since then and they have loaded fine.

sorry for the novel but this is some wacky stuff...and i cant figure it out. EFI support or anyone heard of this before?

 

[EFI Support]

What happens when you flash a "standard" tune (ie non DSP) back into your truck?

What software/firmware are you using?

Cheers
Cindy

 

[Redbowties88]

Cindy I flashed a normal tune to the truck without problem. Then reflashed to dsp5 and the problem continued.


My software and firmware were last updated about a month ago

 

[EFI Support]

read out your tune and email it to support at efilive dot com and Ross will take a look.

Cheers
Cindy

 

[Redbowties88]

read out your tune and email it to support at efilive dot com and Ross will take a look.

Cheers
Cindy

10-4. Thank you Cindy.

 

[Redbowties88]

my dumb ass sent the email with the attachment so here comes another email

one more thing to add..this could be normal and ive always has this problem but it seems lately it has gotten a little worse. probably has nothing to do with my tune switching problem but who knows.


well i run the v2 plugged in all the time while driving to monitor data. well often when i go to begin to display data it connects then only shows 0 for every PID as the frames count. sometimes i have to disconnect and reconnect 3-4 times or more before it will give me a readout....

 

[Redbowties88]

and today the problem randomly corrects itself???

maybe something in the ECM had to reset after the failed flash attempt? or maybe the v2 itself is acting up?

ill keep an eye on it and post again if it re-recourse

 

[EFI Support]

There are some odd things in your file that may have caused your issue. Do you have any history on what may have happened with your truck's ECM? Have you ever had GM reflash your truck? It looks like some strange TIS error/corruption.

Cheers
Cindy

 

[Redbowties88]

There are some odd things in your file that may have caused your issue. Do you have any history on what may have happened with your truck's ECM? Have you ever had GM reflash your truck? It looks like some strange TIS error/corruption.

Cheers
Cindy

Cindy, the ecm was was replaced under warranty about a year ago. this was before i got EFIlive...first they "fried" the factory one then had all kinds of issues flashing this one and getting it to run. all in the process of trying to install a new radio (to vin unlock it). they told me the used radio i had brought them caused the problems so i ditched it and since then haven't had any problems.

sorry for my ignorance but what is TIS?

 

[Redbowties88]

ok well the flashing problem reared its ugly head again today while doing a calibration flash.

second time flashing (using alt-keys) worked fine..ive yet to try and see if i can change my dsp tunes yet though

this time i saved the readout so you can take a look

14:16:57.953: Scanning for EFILive FlashScan V2 USB
14:16:57.984: Autodetect interface ...
14:16:59.765: Interface not detected
14:17:00.421: Scanning for EFILive FlashScan V2 HAPI
14:17:00.453: Autodetect interface ...
14:17:00.609: Interface firmware version: 2.6.21
14:17:00.625: Connection to [FSV2] interface is OK
14:17:00.671: Interface firmware model: FSV2
14:17:00.703: Interface firmware version: 2.6.21
14:17:00.718: Interface firmware date: Dec 20, 2009
14:17:00.750: FlashScan serial number: 003781946729
14:17:00.781: FlashScan license number: 003781946729
14:17:00.828: Disconnecting ...
14:17:01.250: CAN-VPW Bridge Deactivated
14:17:01.265: Disconnected
14:17:01.937: Scanning for EFILive FlashScan V2 USB
14:17:01.968: Autodetect interface ...
14:17:03.750: Interface not detected
14:17:04.421: Scanning for EFILive FlashScan V2 HAPI
14:17:04.453: Autodetect interface ...
14:17:04.609: Interface firmware version: 2.6.21
14:17:04.625: Connection to [FSV2] interface is OK
14:17:04.656: CAN-VPW Bridge Activated
14:17:04.734: Current protocol set to: "SAE J1850 VPW"
14:17:04.750: Autodetect PCM...
14:17:04.812: Connection to PCM is OK
14:17:04.828: Autodetect TCM...
14:17:04.890: Connection to TCM is OK
14:17:04.921: Current protocol: "SAE J1850 VPW"
14:17:04.953: Interface firmware model: FSV2
14:17:04.984: Interface firmware version: 2.6.21
14:17:05.015: Interface firmware date: Dec 20, 2009
14:17:05.046: FlashScan serial number: 003781946729
14:17:05.078: FlashScan license number: 003781946729
14:17:05.171: Getting status...
14:17:05.218: Status: OK.
14:17:06.000: Bootloader version: DLLY_v1.4C (06F0-035F)
14:17:06.015: Preparing ECM for reflash...
14:17:06.078: ECM seed is: $187C
14:17:06.093: Unlock attempt 1 of 1
14:17:34.687: ECM is in an unknown state.
14:17:36.812: Clear emisison related DTCs...
14:17:36.859: Clear DTCs for all modules...
14:17:37.156: Disconnecting ...
14:17:37.546: CAN-VPW Bridge Deactivated
14:17:37.578: Disconnected
14:17:37.593: Data transfer was interrupted.
14:17:44.718: Done!

 

[EFI Support]

Cindy, the ecm was was replaced under warranty about a year ago. this was before i got EFIlive...first they "fried" the factory one then had all kinds of issues flashing this one and getting it to run. all in the process of trying to install a new radio (to vin unlock it). they told me the used radio i had brought them caused the problems so i ditched it and since then haven't had any problems.

sorry for my ignorance but what is TIS?

Radio's on LLY's are always an issue, even for GM. That aside, TIS is the term referred to for GM's programming system, where the dealer programs in the latest factory updates.
Just like any programming system it also has problems occasionaly, we've seen mostly on LB7's when TIS programs these it corrupts an important part of the ECM, this unfortunately is the same area we store the DSP tune you last selected.
For the ECM to stop responding to the command from the V2 to switch it may indicate an issue with the communications bus on the truck, or a problem with the V2 itself.
When we see this message:
14:17:34.687: ECM is in an unknown state.
It is generally because it's lost communication with the ECM.
Because the LLY radios can cause problems, just as a test why don't you pull the radio fuse and see if things behave differently.

Cheers
Cindy

 

[DMAX403]

ok well the flashing problem reared its ugly head again today while doing a calibration flash.

second time flashing (using alt-keys) worked fine..ive yet to try and see if i can change my dsp tunes yet though

this time i saved the readout so you can take a look

14:16:57.953: Scanning for EFILive FlashScan V2 USB
14:16:57.984: Autodetect interface ...
14:16:59.765: Interface not detected
14:17:00.421: Scanning for EFILive FlashScan V2 HAPI
14:17:00.453: Autodetect interface ...
14:17:00.609: Interface firmware version: 2.6.21
14:17:00.625: Connection to [FSV2] interface is OK
14:17:00.671: Interface firmware model: FSV2
14:17:00.703: Interface firmware version: 2.6.21
14:17:00.718: Interface firmware date: Dec 20, 2009
14:17:00.750: FlashScan serial number: 003781946729
14:17:00.781: FlashScan license number: 003781946729
14:17:00.828: Disconnecting ...
14:17:01.250: CAN-VPW Bridge Deactivated
14:17:01.265: Disconnected
14:17:01.937: Scanning for EFILive FlashScan V2 USB
14:17:01.968: Autodetect interface ...
14:17:03.750: Interface not detected
14:17:04.421: Scanning for EFILive FlashScan V2 HAPI
14:17:04.453: Autodetect interface ...
14:17:04.609: Interface firmware version: 2.6.21
14:17:04.625: Connection to [FSV2] interface is OK
14:17:04.656: CAN-VPW Bridge Activated
14:17:04.734: Current protocol set to: "SAE J1850 VPW"
14:17:04.750: Autodetect PCM...
14:17:04.812: Connection to PCM is OK
14:17:04.828: Autodetect TCM...
14:17:04.890: Connection to TCM is OK
14:17:04.921: Current protocol: "SAE J1850 VPW"
14:17:04.953: Interface firmware model: FSV2
14:17:04.984: Interface firmware version: 2.6.21
14:17:05.015: Interface firmware date: Dec 20, 2009
14:17:05.046: FlashScan serial number: 003781946729
14:17:05.078: FlashScan license number: 003781946729
14:17:05.171: Getting status...
14:17:05.218: Status: OK.
14:17:06.000: Bootloader version: DLLY_v1.4C (06F0-035F)
14:17:06.015: Preparing ECM for reflash...
14:17:06.078: ECM seed is: $187C
14:17:06.093: Unlock attempt 1 of 1
14:17:34.687: ECM is in an unknown state.
14:17:36.812: Clear emisison related DTCs...
14:17:36.859: Clear DTCs for all modules...
14:17:37.156: Disconnecting ...
14:17:37.546: CAN-VPW Bridge Deactivated
14:17:37.578: Disconnected
14:17:37.593: Data transfer was interrupted.
14:17:44.718: Done!

What ended up happening with this? I am getting the same "data transfer was interrupted" message when trying to read my current dsp5 tune (so I can save it). Can anyone help me out what I'm doing wrong.

 

[Redbowties88]

My problem has gone away for the most part. As stangely as it began it just stopped on it's own not after any particular update or anything. It still happens once in a blue moon but always seems to work the second time around

 

[EFI Support]

What ended up happening with this? I am getting the same "data transfer was interrupted" message when trying to read my current dsp5 tune (so I can save it). Can anyone help me out what I'm doing wrong.

Your problem is that we write to other parts of the ECM, not just flash memory so DSP tunes on LMM cannot be read out.

You'll either need to find the tune that you flashed into your truck on your V2/Laptop or start over.

Cheers
Cindy

 

[DMAX403]

Your problem is that we write to other parts of the ECM, not just flash memory so DSP tunes on LMM cannot be read out.

You'll either need to find the tune that you flashed into your truck on your V2/Laptop or start over.

Cheers
Cindy

My vehicle is set up as an LBZ though, with an lbz ecm and standalone harness, lbz tranny, and so on, so does that still mean the same problem as you've stated above.

Thanks for your help,

 

[EFI Support]

My vehicle is set up as an LBZ though, with an lbz ecm and standalone harness, lbz tranny, and so on, so does that still mean the same problem as you've stated above.

Thanks for your help,

LBZ is the same - we write to non-readable memory, so the DSP tune files cannot be read out.

Cheers
Cindy

 

[DMAX403]

LBZ is the same - we write to non-readable memory, so the DSP tune files cannot be read out.

Cheers
Cindy

No worries, thanks for your help.

 

[codylbz]

Yes the LBZ cannot read the dsp tune, same as the LMM.