1r09 not the fix for (1) error!

[NolanB]

I have had a Trinity since about May for my 09 Ram Hemi, and I have loved using it, and getting to see the extra power from it. Today, I was going to change the tune, and re-installed the original back-up. As soon as the original back-up was installed on my truck, the "An internal update has been installed that requires a reboot. Please unplug your Trinity briefly to cycle the power." message popped up.

I have cycled it numerous times, unplugging it from my truck and bringing it back into the computer also. Nothing has helped, and this is with the 1r09 update.

I thought that 1r09 was supposed to be the fix for this, but it isn't. I am disappointed to see this happen when this was supposed to be the fix.

When is this really going to be fixed?

[mikel]

did you change vehicle type after restoring the backup?

Thanks

[NolanB]

I didn't get a chance to do anything. After the Original Back-up was re-installed, the Trinity started to do it's power cycle. As soon as it powered back up, it immediately went to the (1) error screen and froze there. There was no change to any other vehicle, nothing could be done.

[mikel]

ok, fill out the rma request form and we'll fix it for you asap.

Thanks

[Mike_Levy]

Nothing you can do. Its gotta either go back to the distributer or back to DiabloSport.

This is happening WAY too much, WAY too soon. Its getting to the point that its really unacceptable. Its come to the point where I dread touching my Trinity. Its not a question of IF its gonna happen, its WHEN its gonna happen.

[Mike_Levy]

It seems to be the ones with the rear Molex connector, not the ones with the bottom iPod connector.

[NolanB]

Levy,
I agree that this seems to be happening a lot. I think that someone needs to step up and figure out what it going on here and get it fixed permanently.

So what needs to be done so that I can get back up and running?

[Mike_Levy]

Thats something Mike Litsch is gonna have to answer. They don't tell me any more then they tell anybody else. Wish they would tell me how to fix this.

[danp129]

At a very minimum DS should work out a way so the customer does not have to send the units back for repair. The customer should just have to hook up the device to USB and join a remote meeting such as TeamViewer for the tech to control their computer and run programs to fix it.

[mikel]

if that were possible, believe me, thats exactly what we'd do.
Please dont assume that we ask you to send it in, then I get it and power it up with USB and fix it, it is not that simple by any means.

[danp129]

So in an ideal world, the next update would have the "Needs to reboot" detection code occur later in the boot strap so that when the message occurs, the USB connectivity is already operational and DSDL can flash it even while the error is visible. If it's hard to move that detection code, keep it and add an OK button but have it set a global flag and continue the boot process. When the boot process is finished it checks the flag and if present it then disables the screen with a new message but the USB should be working at this point for DSDL to re-flash.

Too bad these things don't come with a backup ROM that would re-flash NVRAM/EEPROM like higher end PC motherboards.