new $EE tuning thing!

[steveo]

TCC indicator is backwards when selected manually, but correct when on auto.

that shoulda been fixed in the latest beta..? maybe i reversed my already accidently reversed reversal or whatever. programming is hard.

[fbody_Brian]

see you're taking advantage of the beer money...

lmao j/k


latest beta 4 tested this evening

[sherlock9c1]

If anyone hasn't donated something to Steveo, now's the time. There's an ebay auction for some repair parts his car could really use.. ending in the next 18 hours. If you can throw $50, 20 or even $10 his way, do it soon.

[fbody_Brian]

Definitely deserving!

[steveo]

TCC indicator is backwards when selected manually, but correct when on auto.

can you confirm that this is still the case with latest beta?

so if you click: On the converter is locked, but the indicator is OFF?
and if you click OFF converter the is unlocked but the indicator is ON?

or is it something else

im flying blind with this one

[fbody_Brian]

That's exactly what I saw yesterday.
I will try to confirm asap

[steveo]

appreciate it buddy, thanks. im hoping 94 and 95 don't react differently, can someone with a '95 trans/ecm confirm too?

[fbody_Brian]

on a side note, been desperately trying to get this working on nix. I've posted on qt forums and posted on qtbug for qtserialport.

here's some of the conversation:

I'm setting to 8192, I get the error:
"Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8192 :divisor 2929.687500 unsupported"
Yet it works in windows, and in emulation under linux, so the hardware does work at this baud rate.
If I set it to 8193 baud i get this error, which is strange:
Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8193 :divisor 2929.329834 unsupported
Baud rate is set to 8193 instead of 8193
I'd really like to get this working
thank you

Denis Shienkov added a comment - 7 hours ago - edited

@Brian Labbie ,
in your case it is not an error! it was already explained to you at a forum

in this case your device got 8193 baud instead of 8192.
UPD: You can also try 5.6.0 branch.




Brian Labbie added a comment - 1 hour ago

Not sure how it was explained to me...
I got no real answer on this.
"in this case your device got 8193 baud instead of 8192. "
then why if I set to 8193 do i get the error:
Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8193 :divisor 2929.329834 unsupported
it makes no sense!




Denis Shienkov added a comment - 1 hour ago

> Baud rate of serial port /dev/ttyUSB0 is set to 8193 instead of 8193 :divisor 2929.329834 unsupported
it is just incorrect output of the debug information, where the fractional part of real baud rate is lost.. should be like:

Baud rate of serial port /dev/ttyUSB0 is set to 8193.blablabla instead of 8193 :divisor 2929.329834 unsupported

Instead of:
if (serial.custom_divisor * baudRate != serial.baud_base) {
qWarning("Baud rate of serial port %s is set to %d instead of %d: divisor %f unsupported",
qPrintable(systemLocation),
serial.baud_base / serial.custom_divisor,
baudRate, (float)serial.baud_base / baudRate);
}


should be:
if (serial.custom_divisor * baudRate != serial.baud_base) {
qWarning("Baud rate of serial port %s is set to %f instead of %d: divisor %f unsupported",
qPrintable(systemLocation),
(float)serial.baud_base / serial.custom_divisor,
baudRate, (float)serial.baud_base / baudRate);
}


and I repeat again: this debug output does not matter to your issue, because the method does not returns an errors!

So even though it hangs with that debug output, it's not an error.
I'll just keep rebooting into win7 to log and flash, unless you have some idea.

EDIT:
the latest:
"Maybe the linux drivers of your device do not support using of custom divizors... try 5.6.0 branch, where are used the new 'termios V2' feature instead of old 'serial_struct', maybe it will work.."

So I'll probably muck around with it tonight.
would be so awesome to have a native linux app for this

[steveo]

we can do it. do you use debian/ubuntu or something else? i need a distribution to make an official port/package for to start with.

[fbody_Brian]

can you confirm that this is still the case with latest beta?

so if you click: On the converter is locked, but the indicator is OFF?
and if you click OFF converter the is unlocked but the indicator is ON?

or is it something else

im flying blind with this one

Latest beta:
Driving with torque converter set to auto:
torque converter works as expected, indicator works as expected.

set torque converter to off:
torque converter stays unlocked, indicator light stays off until the normal lockup mph is reached then the light turns on, even though torque converter is unlocked.
drop below the normal speed and indicator goes off, above the speed and it comes on. Light has the same behavior as if it's set to auto.

set torque converter to on:
torque converter is locked, works in any gear, light never indicates a locked condition

[steveo]

so the indicator light doesn't function at all with mode4 tcc enable. i can live with that.

so what i'll probably do in this release is just force the light to be on/off to not confuse people, then in the next release i'll try to patch it so the mode4 override also sets/unsets the status bit.

[fbody_Brian]

so the indicator light doesn't function at all with mode4 tcc enable. i can live with that.

so what i'll probably do in this release is just force the light to be on/off to not confuse people, then in the next release i'll try to patch it so the mode4 override also sets/unsets the status bit.

a patch would work. Another option would be to have the indicator work from the status bit when on auto, but if you click the tcc on button it overrides and turns the indicator on and vice versa for the tcc off button.