Quote from EQ Worry :

The error you mention is interesting, but showing AIRIO ERROR lines from Airio log.txt file would be much more helpful.

Yeah thats now my point, got no access to the server. All communication is via e-mail. Well i´ll check the serveradmin for a ftp-access, so I can check all optons by myself...

Its not my first Server including AIRIO I set up, but the guy who makes it now has no clue about getting started...

Thanks for the support. I´ll let you know if this will help.

Regards, Tomasz

Hey guys,

progress is made. I have now a Code to feed the Arduino with data from LfS and parse it through to the cluster.
When my cluster will be delivered, I will make a vid and post the link.

At this point I can just say, that it is possible to drive parts of the cluster directly, other air-cores need a h-bridge. Depends all on thecluster ant the internal hardware used.

Regards,
Tomasz

Hi there,

I got a little problem, setting up a brandnew server with a brandnew AirIO.
Getting following error: ERROR : 10.07.27 23:47:38 - Got 87


Another problem is that my mate, who hosts the server lives in the the states for a year so just have contact by mail.


Can someone tell me about the error an how it can be solved? I guess it is just a setting of IP or Port, but he has no clue working with the server or lapper files so I won´t bother him and just wanna give hi the right files so he can just upload them and start with SSH-service.


Kind regards,
Tomasz

Hi there,

just made a small step ahead. Bought a dashboard from a ´97 Mitsubishi Galant.
Makes 8000RPM and 160mph. In a few days I will start some hardware testing, if possible.
Maybe someone of you has a clue how to connect to the dash. At the moment I havent coped with that...

If anything else happens, I´ll write soon as possible!


Kid regards, Tomasz

Last edited by FW-05, Thu 22 Jul 2010, 07:04.

Hi Dustin,

the InSim.txt file explains everything that has to do with LfS concerning OutGauge. All other documentations should be made, imho, by the developers of the OutGauge tools. Regarding my abilities in programming, I would favour a transscripted source code, so I can reconstruct the steps a programm makes...

The link you posted is very usefull, if it comes so far that I have to drive some air-cores.

Do you have any progress? I have to write some exams, after that I can spend more time for the project.


Kind regards,
Tomasz

Last edited by FW-05, Sun 18 Jul 2010, 07:38.

Quote from Degats :

All the OutGauge documentation you'll need is at the bottom of /your_lfs_directory/docs/insim.txt

Yeah right! This is what is written in the InSim.txt:
(just to have quick access to the content)

Quote :

// OutGauge - EXTERNAL DASHBOARD SUPPORT
// ========

// The user's car in multiplayer or the viewed car in single player or
// single player replay can output information to a dashboard system
// while viewed from an internal view.

// This can be controlled by 5 lines in the cfg.txt file :

// OutGauge Mode 0 :0-off 1-driving 2-driving+replay
// OutGauge Delay 1 :minimum delay between packets (100ths of a sec)
// OutGauge IP 0.0.0.0 :IP address to send the UDP packet
// OutGauge Port 0 :IP port
// OutGauge ID 0 :if not zero, adds an identifier to the packet

// Each update sends the following UDP packet :

struct OutGaugePack
{
unsigned Time; // time in milliseconds (to check order)

char Car[4]; // Car name
word Flags; // Info (see OG_x below)
byte Gear; // Reverse:0, Neutral:1, First:2...
byte SpareB;
float Speed; // M/S
float RPM; // RPM
float Turbo; // BAR
float EngTemp; // C
float Fuel; // 0 to 1
float OilPressure; // BAR
float OilTemp; // C
unsigned DashLights; // Dash lights available (see DL_x below)
unsigned ShowLights; // Dash lights currently switched on
float Throttle; // 0 to 1
float Brake; // 0 to 1
float Clutch; // 0 to 1
char Display1[16]; // Usually Fuel
char Display2[16]; // Usually Settings

int ID; // optional - only if OutGauge ID is specified
};

// OG_x - bits for OutGaugePack Flags

#define OG_TURBO 8192 // show turbo gauge
#define OG_KM 16384 // if not set - user prefers MILES
#define OG_BAR 32768 // if not set - user prefers PSI

// DL_x - bits for OutGaugePack DashLights and ShowLights

enum
{
DL_SHIFT, // bit 0 - shift light
DL_FULLBEAM, // bit 1 - full beam
DL_HANDBRAKE, // bit 2 - handbrake
DL_PITSPEED, // bit 3 - pit speed limiter
DL_TC, // bit 4 - TC active or switched off
DL_SIGNAL_L, // bit 5 - left turn signal
DL_SIGNAL_R, // bit 6 - right turn signal
DL_SIGNAL_ANY, // bit 7 - shared turn signal
DL_OILWARN, // bit 8 - oil pressure warning
DL_BATTERY, // bit 9 - battery warning
DL_ABS, // bit 10 - ABS active or switched off
DL_SPARE, // bit 11
DL_NUM
};

//////

Last edited by FW-05, Tue 13 Jul 2010, 11:48.

Hello boycey,

I´m quite happy, that someone else wants to connect an Arduino to LfS.
Your post makes me feel sick, because I can´t deal with any programming language. But it is not a reason for me to quit my project. I´m studying with a lot of nerds in programming so maybe they could help me.

How far is your sourcecode? Is something working right now. Maybe you could pass your code, because I wanted to work through some tutorials and maybe in a while, I could help you out.

Concerning the instrument you said, that a true air-core instrument could be driven by the PWM channels. How could I check out whether its a air-core or just a ammeter. Is it depending on model and year?

I guess the option with the servos should be more easier, becaue the servo library is already written and there is no additional hardware (h-bridges, transistors, potentiometers; and of course soldering) needed, just the servos.

I´ll let you know if I got any progress.


Kind regards, Tomasz


PS: nice to see, that my thread moved you to write your first post! =)

Hi there!

I´m working for some time on a way to make the Arduino Duemilanove µC handle a real tachometer. But i am still in the beginning, so only the µC is bought, tachometer comes up in some days or so, depending on my income.

But let´s start in the beginning. Some weeks ago I was browsing uTube and some vids catched my eye. People had a real tachometer connected to LfS or rFactor. Looked great so I checked out some electronics forums and a user from a german LfS-Board recommended the Arduino µC (see the datasheet http://www.atmel.com/dyn/resou ... rod_documents/doc8161.pdf). I was impressed because it can handle six PWM channels.

Now my lack of programming skills comes up. I have no clue how to get out the values of speed, RPM, Temp, pressure, fuel out of LfS in a form so I can feed the µC with it. I know, that thats the part of OutGauge.

Has anybody an idea how it could make it work? Maybe there is another way, without using OutGauge but X-Sim, but I want to try it first with the build-in LfS feature.

I think the worst problem is to adress the data from LfS over USB-port to the Arduino. The output of the values should be realized by (depending on the kind of tachometer I could get) using the internal motors (which are infact ammeters I guess) or some RC-servos I have here laying around.

Well guys, thats what I am working now on. Progress will be updated.


PS: sorry for language, if there are any missunderstandings, please ask...