Romraider on Raspberry PI

ride5000 · **Joined:** Thu Aug 03, 2006 10:40 am **Posts:** 1934

Cool project

A step by step for dummies like me would go a long way!

discomfort · **Joined:** Fri Aug 10, 2012 4:44 pm **Posts:** 54

dschultz wrote:

That seems to run well.
Do yourself a favour and launch the Logger with a shell script. This is what is provided for Linux systems as part of the distribution (all one line).

Code:

java -Djava.library.path=lib/linux -Dawt.useSystemAAFontSettings=lcd -Dswing.aatext=true -Dsun.java2d.d3d=false -XX:-UseParallelGC -XX:CompileThreshold=10000 -jar RomRaider.jar -logger

-Djava.library.path=lib/linux this is the part that tells Java where to find your libraries which you didn't type and is most likely the reason you had to put the rxtx files in the Java directory.
And if you don't have any External sensors you can remove all the entries from the plugins directory (if you didn't do that yet) to save some time and memory.

If I run it via the shell script it will not open any of the def files or cars.xml... not sure why this is at the moment it just shows at the bottom of the RR windows "files does not exist" even tho I pointed to where it was.

I've alreayd removed the plugins folder (well renamed it) to help speed up the loading, I have had to disbale fast polling as this seem to "choke" it and causes a 2-5 second delay in the data recived.

discomfort · **Joined:** Fri Aug 10, 2012 4:44 pm **Posts:** 54

ride5000 wrote:

Cool project

A step by step for dummies like me would go a long way!

This is somthing I may add later, I cannt say I am an expert with the Pi yet as this is the only thing I bought it for so learning alot myself, I'm not very Linux savvy so there proberly better ways to do things.

dschultz · **Posted:** Mon May 20, 2013 4:29 pm

discomfort wrote:

If I run it via the shell script it will not open any of the def files or cars.xml... not sure why this is at the moment it just shows at the bottom of the RR windows "files does not exist" even tho I pointed to where it was.

You need to store the settings.xml file in:
$HOME/.RomRaider/settings.xml

The next version of RR will also look in the starting directory for settings.xml.

discomfort · **Joined:** Fri Aug 10, 2012 4:44 pm **Posts:** 54

Thanks I will try this tomorrow!

zavier · **Posted:** Wed Oct 16, 2013 2:53 pm

Would this help? Oracle Java on Raspberry Pi

zavier · **Posted:** Thu Oct 17, 2013 10:42 am

What are all the binaries needed?

85z18 · **Joined:** Sun Nov 24, 2013 9:03 pm **Posts:** 15

Bump?

drischnie · **Joined:** Wed May 07, 2008 8:01 pm **Posts:** 36

tmacedo · **Posted:** Mon Sep 08, 2014 1:22 pm

and bump

drischnie · **Joined:** Wed May 07, 2008 8:01 pm **Posts:** 36

makem · **Joined:** Fri May 30, 2014 5:18 pm **Posts:** 4

I just installed Romraider on my new pi 2 and it was quite easy with help from this thred. The latest version on Raspbian comes with Java 8 already installed.
Here are some instructions to get Romraider running on pi 2:

- Install Romraider:
1. Download Romraider Linux install package from romraider.com
2. Install it by running command: java -jar RomRaider0.5.8RC1-linux.jar
3. Done

- To get the KKL/Vag-com OBD cable working you need RXTXcomm.jar and librxtxSerial.so, which are java version and arm version specific. I have java 8 and pi 2 (arm7) and could't find the right version of the files so I needed to compile them myself.
This was easy with these instructions: https://blogs.oracle.com/jtc/entry/java ... _revisited. I have attached the compiled files in a zip-file if anyone needs them. These should work if you have pi 2 with java 8.
1. copy RXTXcomm.jar to folder /home/pi/RomRaider/lib/common
2. copy librxtxSerial.so to folder /home/pi/RomRaider/lib/linux

toddaround · **Joined:** Sun May 24, 2015 12:34 pm **Posts:** 2

Hi makem,
Great job at making this a straight forward install. I was able to get the program up and running. I am very new to Linux. How do you get the RPI2 to see the two custom files you created? I placed them in the correct directories but on booting Logger the "Com Port: ..." has no com ports that I can select. I have a vagcom type OBD2 that works with windows Romraider. It has a FTDI com chip. I have also tried this with my Tactrix Openport2. Thanks for your help.

dschultz · **Posted:** Sun May 24, 2015 10:58 pm

What serial device name does the VAG-COM show up as when you plug it in, dmesg should show this info.
Does your User account have rights to read/write that serial device, if not add your User name to the group that the serial device is part of ls -l the /path_to/device_name.
You cannot use the Openport 2 with Linux as there is no driver for it and it is not a serial device.

toddaround · **Joined:** Sun May 24, 2015 12:34 pm **Posts:** 2

Hi dschultz,
Thanks for your help. I used the dmesg command and received the following related to my VAG-COM style OBD2 port adapter. I am using a fresh install of Raspian from noobs. I only set the software to start in the graphical environment. No login and no name or account changes. I have not added any FTDI com port drivers. I understand that they are already in raspian.

With the information that I give you could you show me how to make sure my user has access to the serial port required. I am very new to Linux and have no idea how to check this stuff. Please layout for me the commands I will need to answer if you have some time.

"
[ 104.007930] usb 1-1.2: new full-speed USB device number 7 using dwc_otg
[ 104.123911] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
[ 104.123940] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 104.123958] usb 1-1.2: Product: USB <-> Serial
[ 104.123974] usb 1-1.2: Manufacturer: FTDI
[ 104.166167] usbcore: registered new interface driver usbserial
[ 104.166324] usbcore: registered new interface driver usbserial_generic
[ 104.166447] usbserial: USB Serial support registered for generic
[ 104.177426] usbcore: registered new interface driver ftdi_sio
[ 104.177617] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 104.179185] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[ 104.179410] usb 1-1.2: Detected FT232BM
[ 104.180583] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
"

RomRaider

Forum rules

Romraider on Raspberry PI

Who is online