how do I install scantool proram

[koshari]

cant just use a symlink like stated here?

http://www.mp3car.com/vbulletin/linu...ux-odb-ii.html

[jlac]

With this patch dzcomm is not necessary, scantool uses termios instead.
We don't need to make symlink, /dev/ttyUSB? is detected by scantool_net.

Get the ScanTool.net package here (http://www.scantool.net/scantool/dow..._net121src.zip)
Get this patch scantool_net121-linux-termios.patch.gz

sudo apt-get install liballegro4.2-dev liballegro4.2
mkdir scantool
cd scantool
unzip ../scantool_net121src.zip
zcat ../scantool_net121-linux-termios.patch.gz | patch
make
./ScanTool

[phil.lxnet]

@ Jlac

Thanks, that worked a treat. Had segfaults on startup and much frustration prior to that.

Is this your patch, if so well done. Even removed that irritating show stopper of refusing to work with certain chips.

Much appreciated and nice clear instructions.

[marfal]

With this patch dzcomm is not necessary, scantool uses termios instead.
We don't need to make symlink, /dev/ttyUSB? is detected by scantool_net.

Get the ScanTool.net package here (http://www.scantool.net/scantool/dow..._net121src.zip)
Get this patch scantool_net121-linux-termios.patch.gz

sudo apt-get install liballegro4.2-dev liballegro4.2
mkdir scantool
cd scantool
unzip ../scantool_net121src.zip
zcat ../scantool_net121-linux-termios.patch.gz | patch
make
./ScanTool

My profound thanks for this fix. I have an ELM327 but couldn't get it to work properly. Thanks to your post I managed to switch orange warning light off in my car last night (Catalyst not efficient - or something) using my trusty Eeepc 701 running Lucid 10.04

[bestpato]

I just followed this thread and everything worked ok!
I just checked my car with scantool_net121 compiled for linux, with a USB obd2 interface.
Thanks!!!

[lkraemer]

I too tried to compile, but I couldn't get Scantool.net to recognize my
USB to Serial Adapter. So I kept searching........and trying things.

How to enable USB-Serial Port adapter (RS-232) in Ubuntu 10.04 (Linux)
for the ELMSCAN5 Serial Version ODBII Code Reader.
Part Number: 46001
Controller: ELM327
Hardware Revision 2.2
Firmware Revision 1.2A
MFG Date: 18 Oct 2007

SERIAL PORT or USB Converter:
If you don't have a serial port on your Laptop, or want to use a USB
port Converter check out the following:

The USB to Serial Converter is from www.newegg.com and is
a N82E16812156008 SABRENT 1 ft. USB to Serial db9 Male RS-232 (9-pin)
Converter Model SBT-USC1M - Retail @ $10.99.

These work wonderful with wvdial, modems, and the Serial ELMSCAN5.


INSTALL REQUIRED SOFTWARE FOR COMPILE:
Typically you need to install build-essential and the headers for the
kernel you are running, if you are going to compile code.

uname -r

will tell you the kernel you are currently running.

sudo apt-get install build-essential linux-headers-$(uname -r)

will install the software needed to compile your code.


TYPICAL COMPILE STEPS: (from within your source directory)

./configure
make clean
make
sudo make install

"make clean" won't remove anything on the first compile, but will clean up
on a successive compile.

You can also use checkinstall to build a deb file.

REF:
http://ubuntuguide.org/wiki/Ubuntu:Lucid


DETECT THE DEVICE - USB
Open a Linux Terminal window and cut/paste the following commands with
the USB to Serial Adapter unplugged from a USB port.

dmesg | tail
lsusb

larry@ubuntu:~$ dmesg | tail
[10797.964432] domain 0: span 03
[10797.964434] groups: 01 02
[10797.964436] domain 1: span 03
[10797.964438] groups: 03
[10797.964440] CPU1 attaching sched-domain:
[10797.964441] domain 0: span 03
[10797.964443] groups: 02 01
[10797.964446] domain 1: span 03
[10797.964447] groups: 03
[12071.044928] usb 6-1: USB disconnect, address 3

larry@ubuntu:~$ lsusb
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 003: ID 04f2:b091 Chicony Electronics Co., Ltd
Bus 007 Device 002: ID 0bda:0158 Realtek Semiconductor Corp.
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Then plug in the USB-Serial Port adaptor to one of your USB ports. (REMEMBER to
ALWAYS use this same port for when using your ODBII Scanner) Wait for about
15 seconds, then cut and paste the following command in your Linux Terminal Window:

dmesg | tail
lsusb

You should see these messages.
larry@ubuntu:~$ dmesg | tail
[10797.964440] CPU1 attaching sched-domain:
[10797.964441] domain 0: span 03
[10797.964443] groups: 02 01
[10797.964446] domain 1: span 03
[10797.964447] groups: 03
[12071.044928] usb 6-1: USB disconnect, address 3
[12091.200574] usb 6-1: new full speed USB device using uhci_hcd and address 4
[12091.358706] usb 6-1: configuration #1 chosen from 1 choice
[12091.363887] /build/buildd/linux-2.6.24/drivers/usb/class/cdc-acm.c: This
device cannot do calls on its own. It is no modem.
[12091.363914] cdc_acm 6-1:1.0: ttyACM0: USB ACM device

My device is /dev/ttyACM0

larry@ubuntu:~$ lsusb
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 003: ID 04f2:b091 Chicony Electronics Co., Ltd
Bus 007 Device 002: ID 0bda:0158 Realtek Semiconductor Corp.
Bus 007 Device 001: ID 0000:0000
Bus 006 Device 003: ID 058f:9720 Alcor Micro Corp. USB-Serial Adapter
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Now, cut and paste the following command in your Linux Terminal Window:

lsusb -v -d 058f:9720

Bus 006 Device 003: ID 058f:9720 Alcor Micro Corp. USB-Serial Adapter
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x058f Alcor Micro Corp.
idProduct 0x9720 USB-Serial Adapter
bcdDevice 0.00


DOWNLOAD & COMPILE:
Download scantool_net121src.zip referenced above.
Download the patch, scantool_net121-linux-termios.patch.gz referenced above.

Create a subdirectory named scantool, and move both downloaded files there.

Open a Terminal Window (Console), and while connected to the Internet, do:

sudo apt-get install liballegro4.2-dev liballegro4.2
cd ~/scantool
unzip scantool_net121src.zip
zcat scantool_net121-linux-termios.patch.gz | patch
make

This will compile the code. We just need to check out the COMM Ports.


LINKING the COMM PORT: SYMBOLIC vs HARD
To locate the possible COMM PORTS in Ubuntu, cut and paste the following commands
with the USB to RS-232C Adapter plugged in.:

ls -l /dev/ttyS*
ls -l /dev/ttyU*

Notice that ttyS0 through ttyS3 are detected as shown. You may have
/dev/ttyUSB0 if it was properly detected. Mine was NOT, because it
was a Sabrent SBT-USC1M USB to Serial Converter..

crw-rw---- 1 root dialout 4, 64 2009-11-27 15:26 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2009-11-27 15:26 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 2009-11-27 15:26 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 2009-11-27 15:26 /dev/ttyS3

I couldn't make a symbolic link work, so I decided to create a
hard link, replacing /dev/ttyS3. First remove /dev/ttyS3.

sudo rm /dev/ttyS3
sudo ln /dev/ttyACM0 /dev/ttyS3

Running the command again:

ls -l /dev/ttyS*

gives:
crw-rw---- 1 root dialout 4, 64 2010-11-10 11:59 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2010-11-10 11:59 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 2010-11-10 11:59 /dev/ttyS2
crw-rw---- 2 root dialout 166, 0 2010-11-10 12:59 /dev/ttyS3
If you don't have rw priviledges remove /dev/ttyS3 and create it again.

We can determine the Baud rate of the Port:

stty -F /dev/ttyS3 -a

and to change it to 9600:

stty -F /dev/ttyS3 9600
stty -F /dev/ttyS3 -a

If you connect to a modem for testing you can transmit out an "ATZ"
causing the Modem to flash the lights and reset with:

echo ATZ > /dev/ttyS3

Which proves characters routed to /dev/ttyS3 get sent to /dev/ttyACM0,
the USB to Serial Converter.

All that remains is to connect the ODBII Cable to the Vehicle, Connect the
Serial cable to the ELMSCAN5, run the Software, configure Scantool for COMM 4 at 9600 baud.
Run the Software with:

./ScanTool

I use the underlined characters to move around the menu's, and left click on an item, then
turn it OFF/ON with the Space Bar. It is a bit confusing, but it works.

Now to make a batch file to automate things a bit.
In your home directory, create a small shell file called st.

#!/bin/sh
sudo rm /dev/ttyS3
ln /dev/ttyACM0 /dev/ttyS3
cd ~/scantool
./ScanTool

Make it executable.

chmod u+x st

Plug the device into the OBD-II port in your car and turn the ignition on (but do not start the engine). Run ScanTool.

./st

ScanTool will default to /dev/ttyS0 (COM1). Change it to /dev/ttyS3 (COM4) & 9600 Baud.
Also change to Windowed interface.

I hope this helps...........

LK


Ref:
http://wiki.eeeuser.com/howto:scantool
http://ubuntuforums.org/showthread.p...light=scantool

[lkraemer]

HOWTO: UPDATE Ver 1.15 SCANTOOL.NET to Ver 1.21 Without the SERIAL PORT
Changes for UBUNTU 10.04


This morning I had a wild thought.....Why not update Version 1.15 to
the latest code (Ver 1.21 without the Serial Communication Port changes...)

Here are the details of what I did and the Linux (Ubuntu 10.04) ScanTool
file is attached in the ZIP file along with the modified files.

I started with the Version 1.21 Source, along with the scantool_net121_linux-terminos.patch.gz file.

Here are the steps I executed to get the source to compile:
1. Applied the terminos.patch file to the Scantool.net Ver 1.21 source.
2. Unzipped the Version 1.15 Source to a folder named 115.
3. Compared all the 1.21 files with 1.15 and modified the files that needed updates.
The following files were modified and then zipped:
about.c
error_handlers.c
main.c
makefile
options.c
reset.c
sensors.c
serial.c
serial.h
version.h
codes.dat *just copied the version 1.21 file
scantool.dat *just copied the version 1.21 file
ScanTool *Compiled Ubuntu 10.04 Linux File

If you want to have the same files as my subdirectory named 115, just
unzip the scantool_net115src.zip file, and then overwrite those files
with the ones in the attached zip. You should be able to compile the
source, or execute the ScanTool file in Ubuntu. (You need to search for
"TERMINOS" in each file, and change that to "LINUX" before the compile.


SYMBOLIC LINKING the COMM PORT:
To locate the possible COMM PORTS in Ubuntu, cut and paste the following commands with the USB to RS-232C Adapter plugged in:

ls -l /dev/ttyS*
ls -l /dev/ttyU*

Displays:
crw-rw---- 1 root dialout 4, 64 2010-11-11 05:18 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2010-11-11 05:18 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 2010-11-11 05:18 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 2010-11-11 05:18 /dev/ttyS3

Create the symbolic link for the unused port #5:

sudo ln -s /dev/ttyACM0 /dev/ttyS4
ls -l /dev/ttyS*

Displays:
crw-rw---- 1 root dialout 4, 64 2010-11-11 05:18 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2010-11-11 05:18 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 2010-11-11 05:18 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 2010-11-11 05:18 /dev/ttyS3
lrwxrwxrwx 1 root root 12 2010-11-11 10:57 /dev/ttyS4 -> /dev/ttyACM0

Execute ScanTool 1.21-Linux without Serial Upgrade with:

 ./ScanTool

and set the Baud Rate.


CREATE BATCH FILE FOR EASY EXECUTION:
Now create a batch file to automate things a bit.
In your home directory, create a small shell file called st.

#!/bin/sh
sudo ln -s /dev/ttyACM0 /dev/ttyS4
cd ~/Downloads/ScanTool-Windows/115
./ScanTool

Make it executable.

chmod u+x st

Plug the ELMSCAN5 into the OBD-II port in your car and turn the ignition on (but do not start the engine). Run ScanTool:

./st

ScanTool will default to /dev/ttyS0 (COM1). Change it to /dev/ttyS4 (COM5) & 9600 Baud.
It should default to a Windowed interface.

This should make it easy for all the Linux Users.

lk

[namiller]

Hello, all!
I'm a newcomer to the Ubuntu world, but have run 10.04 since its introduction and have successfully compiled and installed a program (VLC 1.1.4.1) and so have a rudimentary idea of the necessary steps involved. However, I have the most minimal knowledge of the command line and what the commands actually mean - at this point I'm at a "copy-and-paste" or "follow instructions to the letter" level of understanding.
I purchased an ElmScan5 tool and wish to install the scantool.net program. I do not have the USB-to-serial adaptor that lkraemer referenced; I wish to use the USB port directly if that's feasible; trying to "read between the line" I gather it is. I have downloaded the net121src.zip package along with the termios.patch.gz file that jlac linked, as it appears that these are the only files that I need that are specific to the scantool application. I have not yet installed liballegro but I'm pretty sure I can handle that either from the command line or from Synaptic, as I see the packages are there.
As one rather new to Linux, what I would like is a step-by-step set of instructions on how to install this software. From what I can see, jlac's patch instructions do not include the compiling of the software:
Code:
sudo apt-get install liballegro4.2-dev liballegro4.2
mkdir scantool
cd scantool
unzip ../scantool_net121src.zip
zcat ../scantool_net121-linux-termios.patch.gz | patch
make
./ScanTool
Where do I "insert" jlac's instructions into the whole compile scheme? For example, where is the "./configure" step I've read about and followed elsewhere? What does it mean to "apply a patch" as lkraemer mentioned in his post, i.e. what are the steps to accomplishing that - I'd guess that the "zcat" line in jlac's code is supposed to do that, but I'm simply not confident enough to poke around and give it a go in the blind. And then how is it to be run - do I need to run it from the command line, or can I just do it from the Applications list? These are some of the questions that come to mind; these should give an idea of where I stand (lack of) knowledge-wise here. I realize that a lot of these steps are very simple, but it is often the very simplicity that moves a beginner like me to wonder, " .... you mean that's ALL???"
I considered asking this in the dept. of Absolute Beginner Talk, and I still wonder. However, although my questions have general application, they are applying to a very specific (and definitely non-mainstream) piece of software - I thought it might be more effective to post directly where the action is. My apologies in advance if I have overstepped any bounds here.
I'd appreciate any help possible, and I thank you all in advance!

[lkraemer]

Well.........I'm speechless.

I thought jlac had specific step by step instructions..........and
I thought mine were well written too!

lk

[namiller]

Yes, I'm sure you're being very clear - but now you see what a raw beginner I am!

Let me try to be more specific if I can - on the only previous compilation I've done, the BIG step was the ./configure script that was run after decompressing the tarball. I understand that this part of the compilation scheme is something that is always done, and I didn't see it mentioned here. This left me guessing - where do I fit jlac's or lkraemer's instructions into the larger general compilation scheme that I've seen outlined elsewhere? Or maybe I'm looking for something that's really right in front of my eyes?

I know reading jlac's instructions left me with the thought - is this all there is to it (seems too easy to be true), or are there other steps that are assumed and left out for brevity? Or maybe I'm trying to think too hard - that last line that reads "./ScanTool" might be in place of "./configure," since it would seem that instead of "configure" the script file might be named anything the author chooses.

Your exasperation notwithstanding, lkraemer, and with somewhat embarrassed apologies for raising your stress level, I do appreciate your getting back on this so soon. Like a lot of people coming from Windows, I do not read code (although I intend to learn more), and I'm just having a hard time deciding if I should be assuming that there are other lines of code required for the compilation and installation that are understood but not mentioned here because they are obvious to others. Reading your response with a cup of morning coffee, I'm somewhat inclined to think that the instructions were essentially complete, and I just need to go ahead and follow jlac's code to the letter and all should be well.

Honestly, I'm not really that dense - merely cautious and a bit confused! Again, thanks for your quick response!