MicroSquirt.com read only forum (Jan.15,2018)

Hi folks,
I have hooked up my Microsquirt V2 (running MS II 2.886) to a JimStim and there's following problem:

- Created new project in TunerStudio. Specified TechEdge Linear as WB sensor.
- Hooked up the Microsquirt and here was no AFR change when turning the 02 poti.
- Checked O2 Voltage on stim and inside the MS (Pin 34) - it's between 0 and 5 V as it should.
- If I activate Fuel Setup -> EGO Control -> Single Wideband, then I get an AFR reading, but a wrong one. Around 0.5 V the gauge jumps from 12 to 17.

I need the AFR read just for logging, so don't wonder about crazy values for the ego controler ...

Obviuosly a configuration problem (the ECU seems to think a Narrow Band is hooked up), but where ?
Would someone be so kind to have a look into the msq ?

Ok found the right way. I was told to use
Tools Calibate AFR Table
which in IMHO not very intuitive as I'd have searched under Tools Sensor Calibration, but that's not the topic here ..
(Please forgive my ignorance here, as I'm mainly used to MSI before)

Next problem: The burn fails; the table is not being created.
Error from TunerStudio:
Write Failed! Table write failed! Error generating Table write command. Root Problem: For input String""\002""

What it did was to create std_ms2geno2.log in the TunerStudio dir.
The contect looks just like some .inc-content

Can I rename and copy it somewhere to make it usable ?


PS: I'm running TunerStudio on Ubuntu with the Java environment you get from canonial. Can that cause that error ?

PS: I'm running TunerStudio on Ubuntu with the Java environment you get from canonial. Can that cause that error ?

Yes. It used to not run at all with Open Java, but it seems Open Java is making improvements. However, there are still quite a few issues and the Performance it terrible compared to sun Java.

Install the sunJava packages.

Hi Phil, here's the current status.

- Uninstalled Open JDK, Downloaded from Sun again and this time followed the instructions word by word.
(Ubuntu makes a difference from the commands "./xxx.bin" or "xxx.bin" which both work under RedHat. That was the reason for failing to install before)
- Using "which java" indicated that install was successful.
- Starting TunerStudio failed (logfile nagged access failures due to missing permissions)
- Uninstalled Sun Java and installed Open JDK again (to have at least the state from before)
- Starting TunerStudio also failed (logfile nagged access failures due to missing permissions)
- Starting with sudo TunerStudio.sh works, but obviously in root's homedir which is not what I need.
- Tried with to start with gksu -u user -w /home/user/TunerStudio/TunerStudio.sh and that worked as intended
- Table write error still there.
- Uninstalled JDK, reinstalled Sun Java.
- Table issue still occurs

Does anyone else use TunerStudio with their normal user or do you all use sudo/gksu to run with admin privileges ?
If it is a bug, which files do you need to trace/resolve the issue ?
If I f...ed up my installation: How would you create a state that would likely work ?

Phil, as the official state is still a beta version: Does it makes sense to discuss this somewhere else ?


BTW: fixed the issue with using MegaTune on Windoze, so we're just trying to improve an upcoming Software from here ...

MK_Micro wrote:Does anyone else use TunerStudio with their normal user or do you all use sudo/gksu to run with admin privileges ?

Yes. Using TunerStudio with standard user and standard Java install coming with the latest release (11.04/natty) here.

No problems so far and I also wouldn't confirm slowness (running on a 1st gen eee pc) although I only use it for ignition yet.

Where did you install TunerStudio? Did you verify that the directory where you installed is user writable?

When I installed the latest TunerStudio I had the same issue (i.e. no rear/write/exe rights on all files in the TS-directory).
I had to fix it by chmod -R 777 *, but now it works.

And Ubuntu 11.04 is an issue to be discussed.
After installation the default GUI made me pu.... errrrr I mean I needed some time to get used to.
Even after setting back to the classic Gnome desktop my seamonkey was not working (crashed on mail editing) and my wireless card does not work anymore.
So I'm still on 10.04 - the better Ubuntu.