2.6.12 problems

[LT401Vette]

FYI Java just updated my 64 bit machine from 8.25 to 8.31.

Do you mean you updated the JRE from 1.8_25 to 1.8_31?
That won't matter on Windows, with 2.6.12, it will use the JRE bundled with it.

[Fueler]

That's what it did.
I guess the issues will still be going on.

[LT401Vette]

Somehow this Thread has been polluted with separate issues which makes it somewhat confusing.

The Burn issue is quite unrelated to your original issue.

Did you ever get the GPS issue squared away?

[Fueler]

Nah, I'm still dealing with crashes and JRE crashes with or without the gps.
Never did find the right combo of uninstall/install to make it stable like it was.
Never saw the page not burned issue though.
I won't be able to get back to fussing with it for a few days.

[LT401Vette]

Something to try....
Go into the TunerStudio install dir and delete the folder runtime

Then it will run on the installed JRE as it always did.
I don't _think_ that is related to your crashes, but I would like to verify.

[Fueler]

Will do and let you know.

[Fueler]

I went ahead on the delete runtime folder.
64 bit machine....TS still opens and runs (not hooked up to ecu)
32 bit machine....TS will not open. Had to reinstall which brings back the runtime folder. So, maybe not an issue there.

Once I have it hooked up I will report back.

[LT401Vette]

For the Burn issue on old firmware, I did just put out a release 2.6.14 that will take care of this.

[Fueler]

Hooked up to the ecu this weekend.
using the 32 bit laptop.
runtime crash every time the bluetooth is attempted.
Detect ports still does not work.
It can't even find the serial cable if I use that. I have to manually select it.

IF I pick the manually selected correct bluetooth port and test it..it crashes.
IF I pick the manually selected correct serial port and test it...it is successful.

I tried uninstalling java 8.31 and reinstalled TS 2.6.14 by it's lonesome.
No joy. still crashes when attempting to connect to the bluetooth.

Sorry Phil, I have tried my best at trying all kinds of combinations.
After all this something has to have gone awry with the communication code since the earlier TS versions.

[LT401Vette]

After all this something has to have gone awry with the communication code since the earlier TS versions.

I don't believe that is the case, these releases are patch releases with very few changes. All real development is in a whole different branch.
I also do not think there is any relationship to the JRE here.

I think it is something on your PC & Bluetooth.

If you think it worked with earlier versions of TS, try installing one of the earlier versions and see if there is any difference.

[Fueler]

I'm willing to try anything but it happens on both the 64 bit and the 32 bit older machine.
It must be tied to java somehow because that is what comes up as the failure reason.
Will try earlier versions again. Don't think I gained anything the last time I tried.

[LT401Vette]

I know you said you tried 2.6.04 and it behaved the same. How far back did you need to go before it didn't have a problem?
2.6.04 has been in stable for quite a while now.

BTW, here is where you can get lots of old versions:
https://www.efianalytics.com/TunerStudi ... dReleases/

[LT401Vette]

Also, is it using BT for either the ECU or the GPS or just one?
It sounds like even trying to open a BT Port for the ECU alone is causing a crash.

Does using JSSC behave the same? ( would guess it does )

[Fueler]

Concentrating on the BT at the moment.
No way to know about the JSSC or any other as the Detect port isn't working. Is that a clue?

[LT401Vette]

No way to know about the JSSC or any other as the Detect port isn't working. Is that a clue?

If you are having crashing problems, you should not be using Detect. It will open the ports that cause a crash. Also Detect sometimes has issues with bluetooth due to the lengthy port open times.

If you have gotten the proper outgoing Ports from the Bluetooth Settings dialog, so you know what ports you should be on, you should it to use those, and click Ok.

To try JSSC, set it to the JSSC driver, select that proper outgoing port and click Ok.

[Fueler]

You did notice that the detect feature can't even find the serial port.
I have been bypassing the detect feature and test feature as they both crash it.

Where is the JSSC thing hidden?

[LT401Vette]

Yes... If a port causes a crash during detecting it is added to the Bad Port List and will not be screened in the future, this is to try avoiding simply crashing each time you try it.
You can re-enable a port from under the Communications Menu.

To use JSSC, in the Communications Settings dialog select:
"USB and Wireless"

then for the Connection Type select: "RS232 Serial (JSSC)"

[Fueler]

ahh, ok. I wondered about all those things on the bad list. Will go try.

[Fueler]

OK, I have news. I think I whipped it.
None of the above tips worked.
I began thinking about all the repeated unloads and loads I did and asked myself what I had not been changed out.
This was during the time that TS, JAVA and Windows all did upgrades BTW.
The answer was perhaps to do a Windows Repair.
No change.
I bought a new usb/BT adapter to replace my 6 yr old piece. Cleaned out the puter of any other bluetooth stuff and installed it.
It croaked after 4 hours. Got another one.
All seems to be working now for a few hours on both computers.
Both TS bluetooth and the GPS seem content for the moment.

However I still don't see the Detect Ports thing working. It used to.
It's not all that critical since the info is available elsewhere.

That's my story for now.....until it changes.

[Michael]

Just downloaded 2.6.14. This fixes the Failed Burn page issues. Thanks very much for quick fix.
Also MLV updated - has a new look and usefully long tails on the table views so you can see recent history more easily. There's probably more that I haven't found yet!

Thanks - Michael