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

After over a month of blissful efi tuning on the windows laptop, i decided to give mac a go. I finally got tunerstudio to open correctly on my mac, but everytime i go to detect ecu's, i get nothing detected. Using my system profiler, i check for usb port drivers and i do not have a usb that says "serial converter." I have the diy usb to serial cable, and i have installed the damn VCP FTDI driver about 20 times now.... My macbook is ooo so much better than my crappy windows laptop, so i would really like it if i could resolve this driver issue.

Also i might be able to get by if i had the bluetooth driver for tunerstudio, but i can't find that one at all. I can pair to the bluetooth serial adapter, but same problem, can't detect any ecu...

Any help is greatly appreciated.

Thanks!

A little update, i got the device to show up in the hardware profiles, as /dev/tty.usbserial-600*** which im pretty sure is correct, cuz when i remove the cable it goes away. Using this specified port in tunerstudio's comm settings, i still dont detect any ecu's. I can plug the cable into my pc and it works, but still not mac... Now im thinking maybe i somehow am missing the code in my mac's tunerstudio for ms1 extra im running in the ecu.

Sorry for the slow response, I was away last week...

There is nothing additional for MS1..

The main stumbling block in OS X is drivers for the USB to serial cable, there are none in by default. You almost certainly need a cable based on either the FTDI or Prolific chipsets, which most are.... So you will always need to download the appropriate drivers and install them.

Now it sounds like you are seeing a new com port come up, but it still isn't working..
The cause for that is usually that you have a 32 bit only driver and by default TunerStudio will run as a 64 bit app on OS X.

When there is a 32 bit only driver, the port will show up, but a 64 bit app won't be able to use it

To test this out, you can run TunerStudio in 32 bit mode. If you download the Linux tar.gz install and extract it some where on your hard drive, you will see a file named TunerStudio32.sh
run that and it will start TunerStudio in 32 bit mode and it will be able to use a 32 bit driver.

if that doesn't do it.. Test to see if your com port is actually working. Use screen. Open a terminal and type:

$ screen /dev/tty.usbserial-600*** 9600

then you should get a response to the command S

Again, the easy way with OS X is make sure you have a cable based on FTDI or Prolific, they both offer 64 bit OS X drivers.

I have tried reinstalling the 64 bit driver with no change. With both the 32 and the 64 bit, the terminal command comes up with,

"Cannot open the line '/dev/tty.usbserial-A600aWqh 9600' for R/W: Resource Busy
Sorry, could not find a PTY"

It also says the same exact thing for the bluetooth profile i created for my bluetooth adaptor, strange...

I could not open the tunerstudio32.sh file on my mac, xcode wants to open it. Is the tunerstudio.jar file the one i should be using to open tunerstudio?

What driver are you using?

Normally double clicking TunerStudioMS.jar is the right way to run it, but then it will run in 64 bit mode. Starting it with TunerStudio32.sh will force it to run as a 32 bit app.

You need to run that from a Terminal though...

- Open a Terminal
- cd to the TunerStudio dir
- type:
$ ./TunerStudio32.sh

it should fire up.

Then also, if you can send me your TunerStudioAppDebug.txt for the beta or TunerStudioLogFile.txt for 1.006
If not a driver issue, it might be a permissions issue?? There may be more info in there.

The Resource Busy is an interesting message.. Maybe something else on the computer is grabbing the port?

Sorry i haven't the most free time right now with finals sneaking up and all... I tried the 32 bit in terminal, but then i get the unable to locate serial port drivers issue that i used to get prior to deleting all traces of the serial.lib file, then re-installing and placing in my tunerstudio folder. Maybe i could get it to locate the drivers by placing the serial file somewhere else?

Looking at that script, it would be looking for librxtxSerial.jnilib in the lib folder.

This command should also work and work with the files where they are:
java -d32 -jar TunerStudioMS.jar

Ok, after much frustration with the serial port driver error message, i reinstalled TS 1.006. I started the app from the folder it was installed in, and it started much quicker without any errors, so i gave it a shot hooked up. It detected the ecu! I honestly have no idea of the real cause for all of my issues, but i suspect an installation error...

Anyway i also tried the bluetooth connection with my adapter and that works too!!! I can go to sleep happy.

Thanks for your help LT401vette!!

I was having this issue as well and after much frustration I finally found a solution. I use the Sewell SW-1301 which I bought with my Zietronix WBO2, this USB->Serial converter uses the Prolific chipset, there are a bunch of other converters out there that also use this chip set.

I finally found the solution at this website: http://xbsd.nl/2011/07/pl2303-serial-us ... -lion.html

Here is the text just in case someone is looking at this years from now and that site is defunct (I hate it when that happens!). I've also included the .kext file that the site references (again in case it goes away in the future). After the included text I mention the slight differences that I had to do from the directions from the web site.

----------------------------------------------

PL2303 Serial-USB on OSX Lion

Posted on July 24, 2011 by martijn
Here’s a way to get you PL2303-based Serial-USB adapter working with OS X Lion (10.7). Based on the osx-pl2303 project on github, I’ve built a kernel extension that works with OS X Lion. You can grab the kext file here or from the link below.


Installing the kext file can be done in a few easy steps:

download and extract
cd /path/to/osx-pl2303.kext
cp -R osx-pl2303.kext /System/Library/Extensions/
next you need to fix permissions and execute bits:
cd /System/Library/Extensions
chmod -R 755 osx-pl2303.kext
chown -R root:wheel osx-pl2303.kext
cd /System/Library/Extensions
kextload ./osx-pl2303.kext
kextcache -system-cache
Good luck!

http://mpepping.home.xs4all.nl/hosting/ ... 3.kext.tgz

----------------------------------------------

My annotations:

Instead of using the terminal window to do the copy (cp -R osx-pl2303.kext /System/Library/Extensions/) I just opened the Extensions folder in the finder and dragged in the osx-pl2303.kext file into it. If you don't know how to find the Extensions directory then do this, open the Finder window and look at the devices section on the left of the window, your Mac should be there. Click on that and then in the right side of the window you should your hard drive, if you didn't rename it then it should be "Macintosh HD". Click on that, then click on "System", then "Library", then "Extensions". That is where you drop the file.

For the next part you do need the Terminal window so open it and do as the original procedure states, the change here is that I had to preface the commands with "sudo", so you would do this instead:

cd /System/Library/Extensions
sudo chmod -R 755 osx-pl2303.kext
sudo chown -R root:wheel osx-pl2303.kext
cd /System/Library/Extensions
sudo kextload ./osx-pl2303.kext
sudo kextcache -system-cache

During some of these commands it will more than likely ask you for your password, this is normal.

After I did this, I then rebooted the Mac and was able to connect TunerStudio up to my Megasquirt box in the connection settings with the "/dev/cu.PL2303-000012FD" port selection.

Hopes this helps someone else out with a lot less frustration than I had! Everything else on the Mac is so much better, why was this so hard?

Kevin