TunerStudio lock file on Linux

[drummingpariah]

Appears to be discussing the same issue, but I don't see a resolution to it: http://www.msextra.com/forums/viewtopic ... 22&t=35041

I have successfully connected and tuned another one of my laptops to this Megasquirt (PnP Miata 1.6) ECU, but can't get this newer Linux installation to work. I'm beginning to suspect that this is related to why ShadowDash isn't connecting like I would like it to, but until I can put together some conclusive evidence that that's the case, I'm going to continue troubleshooting them as if they're separate issues (http://www.msextra.com/forums/viewtopic ... 33&t=55812).

Running Ubuntu 14.04:

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.1 LTS
Release:	14.04
Codename:	trusty

When I try to launch tunerstudio (just a symbolic link to the actual executable so it's in my PATH)

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ tunerstudio 
Jar Name:TunerStudioMS.jar
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists

I'm in the uucp group, so my user should be able to manage lock files without any issues.

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ groups
jobrien adm uucp cdrom sudo dip plugdev lpadmin sambashare

I'm fed up with trying to fight these issues, so I 777'd the entire /var/lock/ (symlink to /var/run, btw) directory and its contents

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ ls -alh /var/lock/
total 8.0K
drwxrwxrwx  3 root     root     100 Sep  8 17:31 .
drwxr-xr-x 23 root     root     760 Sep  8 17:02 ..
-rwxrwxrwx  1 jobrien  jobrien   11 Sep  8 17:23 LCK..OM1
-rwxrwxrwx  1 jobrien  jobrien   11 Sep  8 17:30 LCK..tyUSB0
drwxrwxrwx  2 whoopsie whoopsie  60 Sep  8 17:01 whoopsie

Even if I constantly overwrite permissions in that lock folder:

Code: Select all

watch "sudo chmod 777 /var/lock/* -R"

or clear out the folder entirely:

Code: Select all

watch "sudo rm -r /var/lock/*"

I get the same results when running tunerstudio.

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ tunerstudio 
Jar Name:TunerStudioMS.jar
RXTX Warning:  Removing stale lock file. /var/lock/LCK..tyUSB0
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists

Even root can't override this permissions issue.

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ sudo tunerstudio 
Jar Name:TunerStudioMS.jar
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..tyUSB0: File exists

I definitely have a working USB -> Serial adapter

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ lsusb
Bus 002 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I definitely have Java installed and running (that wasn't really ever a question though, I wouldn't even GET this error without Java.

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ dpkg-query -l | grep java
ii  ca-certificates-java                                  20130815ubuntu1                                     all          Common CA certificates (JKS keystore)
ii  gir1.2-javascriptcoregtk-3.0                          2.4.3-1ubuntu2                                      amd64        JavaScript engine library from WebKitGTK+ - GObject introspection data
ii  java-common                                           0.51                                                all          Base of all Java packages
ii  libatk-wrapper-java                                   0.30.4-4                                            all          ATK implementation for Java using JNI
ii  libatk-wrapper-java-jni:amd64                         0.30.4-4                                            amd64        ATK implementation for Java using JNI (JNI bindings)
ii  libjavascriptcoregtk-3.0-0:amd64                      2.4.3-1ubuntu2                                      amd64        JavaScript engine library from WebKitGTK+
ii  tzdata-java                                           2014e-0ubuntu0.14.04                                all          time zone and daylight-saving time data for use by java runtimes

[LT401Vette]

A couple things to try...

In Comm Settings try switching to the JSSC driver under USB and Wireless.

Or if you can find an RXTX driver compiled with the no-lock option on. I was just looking and didn't find it, but have in the past.

[drummingpariah]

A couple things to try...

In Comm Settings try switching to the JSSC driver under USB and Wireless.

Or if you can find an RXTX driver compiled with the no-lock option on. I was just looking and didn't find it, but have in the past.

I don't see a USB and Wireless option in my installation, am I looking in the wrong place or is this because I'm using the Lite version? If upgrading would address this issue (partially or completely) just show me where to pay.



I'll see what other versions of RXTX I can get running on this. There may be a flag I can set when RXTX is called to disable/ignore lock files, assuming that's actually the problem here.

Code: Select all

jobrien@x220:~/bin/TunerStudioMS$ tail -f debug.log 
9/8/14 6:32:11 PM :Debug: Command Non-VolatileBytes for f resolved to: x66                                                                   f
9/8/14 6:32:11 PM :Debug: App Name:TunerStudio, appEdition:MS Lite!
9/8/14 6:32:13 PM :Debug: Time to retreive font name list: 7 ms.
WARNING:  RXTX Version mismatch
	Jar version = RXTX-2.2pre1
	native lib Version = RXTX-2.2pre2
9/8/14 6:32:14 PM :Info: Initialized RXTX driver: 11ms.
No check, last update check=Mon Sep 08 16:55:31 EDT 2014
MSmain: No check, last update check=Mon Sep 08 16:55:31 EDT 2014
MSad: No check, last update check=Mon Sep 08 16:55:58 EDT 2014
9/8/14 6:32:32 PM :Debug: Time to load ini list: 18ms.
9/8/14 6:32:35 PM :Debug: Created CheckThread
9/8/14 6:32:35 PM :Info: Opening port: COM1
9/8/14 6:32:35 PM :Debug: RXTX ControllerInterface Close Connection currentPort == null
9/8/14 6:32:35 PM :Info: RXTX: Port:COM1, Baud:115200 Controller not found
9/8/14 6:32:36 PM :Info: Opening port: COM1
9/8/14 6:32:36 PM :Debug: RXTX ControllerInterface Close Connection currentPort == null
9/8/14 6:32:36 PM :Info: RXTX: Port:COM1, Baud:9600 Controller not found
9/8/14 6:32:38 PM :Debug: Device not found
9/8/14 6:32:38 PM :Debug: goOffline Starting, Time:0
9/8/14 6:32:38 PM :Info: Deactivated Turbo Baud, goOffline
9/8/14 6:32:38 PM :Debug: goOffline about to stopProcessing, Time:9
9/8/14 6:32:38 PM :Debug: goOffline closed port, Time:10
9/8/14 6:32:38 PM :Debug: goOffline comm thread stopped, Time:10
9/8/14 6:32:38 PM :Debug: No Remaining Queue Write instructions
9/8/14 6:32:38 PM :Debug: CheckThread exiting
9/8/14 6:32:44 PM :Debug: Cancel Wizard
9/8/14 6:32:46 PM :Info: closeApp Called
9/8/14 6:32:46 PM :Info: Finalizing Sensors
9/8/14 6:32:46 PM :Info: closed Called
TunerStudio shutdown: Mon Sep 08 18:32:46 EDT 2014
##############################################################

[piledriver]

On most recent versions of Linux (release in last year or so), using systemd, the /var/lock dir is a symlink to /run/lock, which is owned by the lock group. The rxtx-nolock patches are in rxtx mainline now, apparently.
Make the user a member of lock, and it should work.
(you have to logout/login again to make the change active)

Also, if you are trying to use a meatspace 9 pin comm port w/16550a, the kernel serial driver needs a mod to only use 1 byte of fifo or you will lose data consistently when talking to anything over 3 wire serial.(no hw handshake aka xon/xoff). it's a 3 second edit but you still have to compile/install the module etc. You can/should set this in Windows serial driver setting in the control panel...

A good USB adapter is a huge improvement.

[drummingpariah]

On most recent versions of Linux (release in last year or so), using systemd, the /var/lock dir is a symlink to /run/lock, which is owned by the lock group. The rxtx-nolock patches are in rxtx mainline now, apparently.
Make the user a member of lock, and it should work.
(you have to logout/login again to make the change active)

Also, if you are trying to use a meatspace 9 pin comm port w/16550a, the kernel serial driver needs a mod to only use 1 byte of fifo or you will lose data consistently when talking to anything over 3 wire serial.(no hw handshake aka xon/xoff). it's a 3 second edit but you still have to compile/install the module etc. You can/should set this in Windows serial driver setting in the control panel...

A good USB adapter is a huge improvement.

I recently decided to revisit this endeavor, but am still receiving no love. I've tried 6 different adapters at this point, and I'm not sure which ones are 'good' or which are 'bad'. I'm currently using http://www.amazon.com/gp/product/B00425S1H8, which is the last adapter I know I had working.

On Ubuntu 14.04.2, there is no 'lock' user. /run/lock is owned by root:root, and I've tried running TunerStudio with sudo escalation as well as from a dedicated user in the (manually created) lock group, just in case there's something critical that I was missing.

I'm unfamiliar with 16550a, I'm assuming that's 9pin to 9pin?

I have no Windows machine. Is that an absolute necessity for dealing with MS?

I definitely have a connection, but Java/RXTX just isn't playing nicely.

Code: Select all

Device: /dev/ttyUSB0

Signal  Pin  Pin  Direction  Status  Full
Name    (25) (9)  (computer)         Name
-----   ---  ---  ---------  ------  -----
FG       1    -      -           -   Frame Ground
TxD      2    3      out         -   Transmit Data
RxD      3    2      in          -   Receive  Data
RTS      4    7      out         1   Request To Send
CTS      5    8      in          1   Clear To Send
DSR      6    6      in          0   Data Set Ready
GND      7    5      -           -   Signal Ground
DCD      8    1      in          0   Data Carrier Detect
DTR     20    4      out         0   Data Terminal Ready
RI      22    9      in          0   Ring Indicator

[piledriver]

You are running an old version of Ubuntu then, user MUST be a member of dialout and uucp groups IIRC.
(you have to log out and log back in after changing group info)

Don't use RXTX or the basic serial if you have a registered version of TS: JSSC works extremely well.

Since you have IIRC MS3, the only thing you need is a decent quality USB cable that plugs in,use the JSSC drivers.
I have never had any luck on Linux with the FTDI driver, but JSSC works fine.
(FTDI works well on Windows)

Windows in not a requirement or even particulary helpful, unless you are using a real 16550a chip built into the motherboard, you have driver options that are useul on Windows tht are not runtime settable on linux w/o recompliling the serial driver, but zero issues w/usb.(with "real" 16550a serial port FIFO size must be set to 1 or data will be lost when it switches from RX to TX, MS uses a 3 wire setup w/no hardware flow control---but all that means nothing if you are using USB.)

If it doesn't work as root you may have hardware issues.

sudo bash, then run the firmware loader (using recent firmware) it has much better luck finding the port than TS does IME.
If that works, try to set up a new project under Linux, it may work better there.

If you have not yet saved your tune, you can copy the files from XP over., IIRC the tunerstudioprojects dir is in "My Documents" on Windows.
Setup the new project under Linux and import the tune afterwards.

Make sure you only have ONE serial adapter connected: The internal MS3 USB serial adapter counts as one if the USB cable is plugged in on both ends.

[drummingpariah]

You are running an old version of Ubuntu then, user MUST be a member of dialout and uucp groups IIRC.
(you have to log out and log back in after changing group info)

Don't use RXTX or the basic serial if you have a registered version of TS: JSSC works extremely well.

Since you have IIRC MS3, the only thing you need is a decent quality USB cable that plugs in,use the JSSC drivers.
I have never had any luck on Linux with the FTDI driver, but JSSC works fine.
(FTDI works well on Windows)

This is the first time I've heard that there is an alternative to RXTX. This car is running mspnp so no direct USB. I really regret not just buying MS3 for this and rewiring the engine harness myself, like I did for my Datsun.

I've tried loading my previous project that was working as well as creating a new project. Whenever TS tries to connect to the usb->serial adapter, RXTX barfs to stdout, and TS can't find Megasquirt. If purchasing the registered version will help me get this ECU working, I'll happily throw money that way. Otherwise, I'm just paying money for an application that doesn't serve any of my needs. I'll dig in again tomorrow, but right now I feel a bit defeated. I feel like I've tried everything I can, and I can't help but think this is a hardware issue (which would have been solvable, but the support from diyautotune when the problem first presented itself was less than helpful).

[LT401Vette]

There is an alternative to RXTX in the registered version under USB and Wireless, a JSSC driver.
For the next major release, that is the primary RS232 driver.

[drummingpariah]

There is an alternative to RXTX in the registered version under USB and Wireless, a JSSC driver.
For the next major release, that is the primary RS232 driver.

Purchased. I'll give it a go tomorrow morning, hopefully I can actually connect!

[piledriver]

Try the firmware loader first: If it can't connect, TS can't either: then its hardware diags time.
Borked firmware can cause comms issues as well.

As long as you have a saved tune you can import it later.

I suspect you'll find registering TS will pay for itself in fuel/time pretty quickly.

[drummingpariah]

Try the firmware loader first: If it can't connect, TS can't either: then its hardware diags time.
Borked firmware can cause comms issues as well.

As long as you have a saved tune you can import it later.

I suspect you'll find registering TS will pay for itself in fuel/time pretty quickly.

I wish I had known about this when it first started happening, then I probably could have just returned it. Unfortunately, I'm pretty stuck at this point, as it looks like it's hardware, so I just won't get to re-tune this car. Disappointing, since I just rebuilt one of the turbos and started welding together a manifold for it.

I just tried this on three different laptops (two x61s' and an x220) on Ubuntu 12.04 and 14.04, and using three different USB->Serial adapters. Just to be on the safe side, I rebooted between each variable change to make sure the kernel was aware of the current adapter. I'm certainly happy to try any further troubleshooting steps you fellas can come up with, but the whole reason I purchased a diyPNP kit was so I wouldn't have to buy more electronics tools (like a soldering iron, for instance).

Each adapter and each laptop produced the same results: nothing could connect to the MS unit.

Code: Select all

Debug message Level:
1: Normal
2: More detail
3: + serial comms
4: + the s19 file as parsed
Selection (default: 1): 3

Do you want to scan your serial ports automatically? (y/n default y)y

#Comm port already closed
Trying: /dev/ttyUSB0 ..#Opening comm port /dev/ttyUSB0
couldn't open port
#Comm port already closed
Trying: /dev/ttyS0 ..#Opening comm port /dev/ttyS0
couldn't open port
#Comm port already closed
Trying: /dev/ttyACM0 ..#Opening comm port /dev/ttyACM0
couldn't open port
#Comm port already closed 
...
Trying: /dev/ttyACM8 ..#Opening comm port /dev/ttyACM8
couldn't open port
#Comm port already closed    


WARNING!!!
No valid ports or ECUs found. Cannot load firmware without communications.

Common problems:

- Something is hogging the serial port. 
 e.g. TunerStudio, modem or mobile phone cable software.
 Be sure to close/exit those applications.

- USB-serial cable on high COM port number, use Device Manager to re-assign
 it to say COM1.

- ECU not powered up, be sure there is fused power applied. Use a mains
adapter or vehicle battery. PP9 batteries are too feeble.

- Serial cable not connected correctly

- Software driver problems

Check the above.  Do you want to try probing again? (y/n default = y) ^[[B

With sudo, I had more encouraging results.

Code: Select all

Do you want to scan your serial ports automatically? (y/n default y)y

#Comm port already closed
Trying: /dev/ttyUSB0 ..#Opening comm port /dev/ttyUSB0
TX: 51
51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   Q...............
00 00 00 00 .. .. .. .. .. .. .. .. .. .. .. ..   ....
 (20 bytes)
Sent Q and got 20 bytes back.
#Closing comm port
Trying: /dev/ttyS0 ..#Opening comm port /dev/ttyS0
TX: 51
Error: probe_port(): Could not execute command Q
Sent Q and got -1 bytes back.
#Closing comm port
Trying: /dev/ttyACM0 ..#Opening comm port /dev/ttyACM0
couldn't open port
#Comm port already closed
Trying: /dev/ttyUSB1 ..#Opening comm port /dev/ttyUSB1
couldn't open port
#Comm port already closed
Trying: /dev/ttyS1 ..#Opening comm port /dev/ttyS1
TX: 51
Error: probe_port(): Could not execute command Q
Sent Q and got -1 bytes back.
#Closing comm port
Trying: /dev/ttyACM1 ..#Opening comm port /dev/ttyACM1
couldn't open port
#Comm port already closed
Trying: /dev/ttyUSB2 ..#Opening comm port /dev/ttyUSB2
couldn't open port
#Comm port already closed

I'm going to have to do some research as to what it is and why it exists, but the Mini-Term was responsive (loose echo) on /dev/ttyUSB0. Is there a way to flash the MS unit without having to fight with a Serial connection, somehow? I certainly appreciate all the work that's gone into this on the software side, but all my efforts are completely crippled by having to work with such an archaic data transfer method.

[piledriver]

It may be archaic but it has been a standard for >30 years, and is still widely used in industry.
It can be frustrating to deal with at times, but once you figure out what you did wrong, it works, and tends to work well from then on.

The next "evolution" would be a direct CAN connection or such, but that has its own basket of issues and still uses two wires.

I recommend you send it back to the vendor or like to sort out.

DIYAutotune has a good rep and very reasonable repair prices.

Short of that all I can suggest is carefully running through the serial port diags steps in the manual as if you had built the board.
All it takes is one switched wire and there will be no comms.
(it only uses 3)

I know nothing of the diypnp deals, except that if it has a tune in it, it worked at least once.
Perhaps go back to the XP based setup for a sanity test?


9 times out of 10 the reeeealy tough to diagnose issues are due to something simple, stupid, and overlooked.
(This is probably a universal truth)

[drummingpariah]

That's really my isue; It's difficult to develop a hassle-free product that doesn't require end-user understanding. I'm an end-user that doesn't want to have to understand it.

I really can't send it back to DIYAutotune, this is my only street-legal vehicle. I had this working for the first month or so of ownership, and collected plenty of data logs during around 10 hours on the dyno. The problem started sometime after that (no facts worth sharing). diypnp is just a preconfigured megasquirt ecu with a connector that adapts directly to the factory wiring harness.

I guess I'll have to dig up another laptop that I can throw Windows on. I really don't know where else to start troubleshooting, and don't have quite enough free time to start going through the manual right now.

[piledriver]

Well, if you can't send it off to let someone else deal with it, you are left with no choice but to understand it.

It typically just works, thus the deafening silence from lack of "mee too" posts.
There is precious little to go wrong, physically.
Some folks step in something at first, but once they figure it out it just works.

There are 3 wires for serial comms used by MS and one of them is a ground.
They are connected to an RS232 driver chip, other side is the CPU itself.
The diagnostic instructions in the manual are detailed and thorough.

Of course it could still be software related.
Where are you?

Many folks have gotten TS working from a Linux boot iso dumped to a USB stick.
Even the setups that don't support "persistence" allow you to partition the stick to store files and install software to the "live" in-memory filesystem. (windows won't see the second partition but thats its own fault)

A Knoppix live DVD setup will work great , it can be dumped to a "persistent" USB setup that can store files and "install" soiftware on. like a portable PC that works on any PC. (Even microsoft is pushing this "invention" lately after ~15 years of folks doing it on Linux)

It's debian based so you should feel right at home.
Try the KDE deskop (default IIRC) he does a decently integrated desktop setup.

This could become an issue if you are using registered tuner studio on many machines as 3 "installs" at a time is a limit, but if you use it all the time on one machine it won't be an issue.