Manual:Support

From rusEfi
Jump to: navigation, search
This page contains changes which are not marked for translation.

Summary

So you have started a project using rusEFI, but have hit some kind of bump in the road. Below are some FAQ items that will hopefully answer questions before you need to inquire in a forum.

Support option 1 --- forum request

-- Please collect the below information before requesting support in the forums. Also please include this each time you post about a problem. This can all be collected in a zip file, or done as individual files and attached to your forum support request. Please keep in mind that you are seeing this and you have allot of information which those of us in the forum do not have. Things that may seem simple to you may be complicated for those of us who have not physically seen what you have, or have not see the steps you have taken to get to the problem you are faced with.

-- What is the basic problem? This would be something like, engine does not start, cannot connect Tuner Studio, Magic smoke has come out, or something similar. A video can be helpful for this as well.

-- Please provide a picture of the rusEFI console. This tells us allot about what firmware you are using, and the status of your software. Also please include the console's border as that indicates information as well.

-- Please provide a picture of Tuner Studio. Just like the console, this indicates allot about your setup and which pieces of software you are using. Also please include the Tuner Studio border as that indicates information as well.

-- Please provide a picture of your physical setup. Seeing how the wires are connected tells us allot about how the hip bone is connected to the leg bone, etc. It also tells us if you have connected the leg bone to the shoulder bone.

-- Please provide a copy of your logs, or specify NA for this.

-- Please provide a copy of your tune, or specify NA for this.

-- Please tell us if you have updated your discovery firmware with the STLink tool. This is not the rusEFI firmware, but the discovery firmware.

-- Please tell us if you have installed the VCP drivers.

-- Please indicate your software pieces, commonly as noted below. The most common platform and the platform used by the primary software developer is Windows, so you are most likely to get the best support with a native Windows environment.

Windows 10, 32bit, USB cable to STM Discovery programming port (VCP), no hardware board attached.

Windows 10, 32bit, USB cable to Frankenso FTDI USB, Frankenso attached to discovery board.

Windows 7, 64bit, USB cable to STM Discovery programming port (VCP), no hardware board attached.

Linux, 32bit, USB cable to STM Discovery programming port (VCP), no hardware board attached.


Tell us about your engine setup. Something like the below.

Engine setup has this many cyl's

1

2

4

6

8

12

Injectors are

port

batch

direct

not fuel

other

Ignition

DISy

COP

CNP

not spark

wasted spark

other

Fuel is

gas

diesel

propane

ethanol

other

Intake is pressurized via

turbo

super charger

NA

other

Support Option 2 --- FAQ

Protoboard does not show the ON light

Isolate to only USB power by disconnecting from vehicle and plugging in to USB power. If that helps. There is probably a problem with the 12V power supply. Check the 3.3V LED

ON light is bright, but can not communiate over USB

Check that the FTDI driver is installed and that you find your COM port.

Can't open Java console

Make sure you have JAVA installed and are opening with JAVA.