new $EE tuning thing!

**fbody_Brian** · 12-31-2015

Originally Posted by steveo

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** · 12-31-2015

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** · 12-31-2015

Originally Posted by 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.

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.

**fbody_Brian** · 12-31-2015

compiled against 5.6. It works on linux!!!!

I compiled eehack 3.5 and it connected with no error.

I'd like to try to compile 4 if at all possible.

**steveo** · 12-31-2015

compiled against 5.6. It works on linux!!!!

holy $#*()^ brian!!! awesome!

there's like zilch for tuning tools in linux besides megasquirt afaik, this is groundbreaking, since tunerpro non-rt runs so well in wine, it's likely that full-time linux users can tune their LT1s now.

im a bit worried about delay timing since i've 'tuned around' windows timers being shoddy, so i'll be interested to see if everything works alright.

how does it look appearance-wise? can you screenshot it?

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.

so this thing is totally independant of the tcc enable routine that sets the flag. this is no big deal, im going to release with a note in the tooltip informing the user. i've decided i dont want to 'light up the light' falsely, since that wont match what's in the log, and wont play back properly. i'd have to falsify data in the datastream, which i can do, but is against my design principles, i want my data to be saved to disk completely unmodified.

so is what it is until i patch it later, but no more patches in this release.

**fbody_Brian** · 12-31-2015

Originally Posted by steveo

holy $#*()^ brian!!! awesome!

there's like zilch for tuning tools in linux besides megasquirt afaik, this is groundbreaking, since tunerpro non-rt runs so well in wine, it's likely that full-time linux users can tune their LT1s now.

im a bit worried about delay timing since i've 'tuned around' windows timers being shoddy, so i'll be interested to see if everything works alright.

how does it look appearance-wise? can you screenshot it?

I will
it's 3.5, which doesn't look as good as 4.
some of the text doesn't fit properly, but it's minor stuff.

Originally Posted by steveo

i've decided i dont want to 'light up the light' falsely, since that wont match what's in the log, and wont play back properly. i'd have to falsify data in the datastream, which i can do, but is against my design principles, i want my data to be saved to disk completely unmodified.

yeah, the more I thought about it the more I think that you're absolutely correct with that decision.

**fbody_Brian** · 12-31-2015

trying to compile 4, but It's currently failing

Code:

 -I. -I. -I../../Qt5.6.0/5.6/gcc_64/mkspecs/linux-g++ -o flash_routine.o flash_routine.cpp
In file included from datastream.h:7:0,
                 from mainwindow.h:12,
                 from flash_routine.cpp:3:
config.h:35:0: warning: ignoring #pragma warning  [-Wunknown-pragmas]
 #pragma warning(disable: 4100)
 ^
flash_routine.cpp: In member function ‘void mainWindow::writeflash()’:
flash_routine.cpp:343:3: error: jump to label ‘FLASH_WRITE_CLEANUP’ [-fpermissive]
   FLASH_WRITE_CLEANUP:
   ^
flash_routine.cpp:84:12: note:   from here
       goto FLASH_WRITE_CLEANUP;
            ^
flash_routine.cpp:94:7: note:   crosses initialization of ‘int write_post_delay’
   int write_post_delay = 70;
       ^
flash_routine.cpp:91:8: note:   crosses initialization of ‘bool enable_compression’
   bool enable_compression = ui->flash_compress->isChecked();
        ^
flash_routine.cpp:343:3: error: jump to label ‘FLASH_WRITE_CLEANUP’ [-fpermissive]
   FLASH_WRITE_CLEANUP:
   ^
flash_routine.cpp:66:10: note:   from here
     goto FLASH_WRITE_CLEANUP;
          ^
flash_routine.cpp:94:7: note:   crosses initialization of ‘int write_post_delay’
   int write_post_delay = 70;
       ^
flash_routine.cpp:91:8: note:   crosses initialization of ‘bool enable_compression’
   bool enable_compression = ui->flash_compress->isChecked();
        ^
flash_routine.cpp: In member function ‘void mainWindow::readflash()’:
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
   FLASH_READ_CLEANUP:
   ^
flash_routine.cpp:439:10: note:   from here
     goto FLASH_READ_CLEANUP;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
   FLASH_READ_CLEANUP:
   ^
flash_routine.cpp:435:10: note:   from here
     goto FLASH_READ_CLEANUP;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
   FLASH_READ_CLEANUP:
   ^
flash_routine.cpp:426:10: note:   from here
     goto FLASH_READ_CLEANUP;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
   FLASH_READ_CLEANUP:
   ^
flash_routine.cpp:422:10: note:   from here
     goto FLASH_READ_CLEANUP;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
   FLASH_READ_CLEANUP:
   ^
flash_routine.cpp:417:10: note:   from here
     goto FLASH_READ_CLEANUP;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
   FLASH_READ_CLEANUP:
   ^
flash_routine.cpp:409:10: note:   from here
     goto FLASH_READ_CLEANUP;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:520:3: error: jump to label ‘FLASH_READ_CLEANUP_NO_RST’ [-fpermissive]
   FLASH_READ_CLEANUP_NO_RST:
   ^
flash_routine.cpp:406:10: note:   from here
     goto FLASH_READ_CLEANUP_NO_RST;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:520:3: error: jump to label ‘FLASH_READ_CLEANUP_NO_RST’ [-fpermissive]
   FLASH_READ_CLEANUP_NO_RST:
   ^
flash_routine.cpp:402:10: note:   from here
     goto FLASH_READ_CLEANUP_NO_RST;
          ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
flash_routine.cpp:520:3: error: jump to label ‘FLASH_READ_CLEANUP_NO_RST’ [-fpermissive]
   FLASH_READ_CLEANUP_NO_RST:
   ^
flash_routine.cpp:393:12: note:   from here
       goto FLASH_READ_CLEANUP_NO_RST;
            ^
flash_routine.cpp:451:7: note:   crosses initialization of ‘int read_floor’
   int read_floor = 0x0D80;
       ^
Makefile:10022: recipe for target 'flash_routine.o' failed
make: *** [flash_routine.o] Error 1
brian@linux-w1cw:~/Downloads/eehack-master>

I get the same error compiling 4 with both qt5.5 and 5.6