Efilive 7 5 Keygen Mac
5 inch flo pro all the way back no muffler. Airbus A380 Flight Manual - Free Software And Shareware. The aisin doesn't need tuning, it's a hell of a lot stronger then the 68 and can handle the power. There's guys are the cutting edge on tuning these trucks in both engine and trans tuning and offer both EfiLive and EZLynk. Installer crapped out 3 times before I figured out it needed an old version of.net that was officially deprecated 5 years ago. If you want to tune your own fuel and spark curves, buy EFIlive and learn that tuning is 25% software knowledge, and 75% engine performance knowledge.
Hej Hope this is the correct area for ALDL 8192 (GM ODB-I) (Assembly Line Diagnostic Link) was a proprietary on-board diagnostics system developed by General Motors prior to the standardization of OBD-I and is therefor the connection to my Pontiac Trans Sport 2.3l engine. As a Rasberry Pi (Bilberry Rasp) will be put into my car, I need to start preparing for interfacing to ALDL. A usual pcALDL looks qute often uses a max chip like However, the earlier 160 baud ALDL interface can be made with just a few transistors: 8192 baud needs a bit more seems 'nice'. Seems like the Bilberry Rasp might become something.
ALDL 8192 baud Hardware There have been a number of designs published (none by GM) to enable the GM proprietory ALDL data stream to be tapped into. Our design uses a MAX232 (or MAX233) because this is the simplest way to do it. We also avoid using a separate power supply by powering the MAX chip from the PC's serial port (DTR and RTS signals must be set to +ve). This circuit can also be used to read older ECU's 160 baud ALDL signals. Here's our circuit using the MAX232 (or MAX232A). Vehicle signals are on the left, PC signals on the right, with DB9 (and DB25 in brackets) pin assignments shown (pin N on DB9 is N/9, etc.).
Note that the 3.3 uF capacitors (C1-C4) may be reduced to 1 uF if these are readily at hand, or to 0.1 uF if you use the MAX232A. If you use a MAX233, which has a different pinout to the MAX232, you don't need to use any of the capacitors C1-C4, but the regulator still requires C5 and C6. More information is available from Maxim, or you can download the data sheets for their 5 Volt Interface Products. As well, get the 78L05 data sheet from Natsemi, and the IN914A data sheet from Fairchild. Early ECUs produced a fixed 8192 ALDL data stream when the user placed a 10k ohm resistor between ALDL connector pins A and B. Later ECUs added internal receive circuitry (the SXR Delco/Delphi transceiver chip). For enhanced capabilities, and their firmware was upgraded too.
Software can be used to enable the 8192 ALDL data stream from these later ECUs. The 8192 baud Rx and Tx data to/from the PC is combined with a diode and resistor (D3, R1) before being sent to the ECU. The 160 baud data is sent to the PC and appears as a toggling CTS signal. Thus no mechanical switching is required to select either 160 or 8192 baud data streams.
The diagnostic sense resistor R3 may not be required for later ECUs where software controls the ALDL data. The power supply uses two signal lines (RTS and DTR) from the PC to provide a positive voltage for the MAX chip. The two diodes (D1 and D2) are used to ensure power is available even if only one signal line is positive. Capacitor C6 ensures the low power 78L05 regulator is stable in operation.
Capacitor C5 provides decoupling and filtering from the PC. C1 through C4 are the charge pump and inverter capacitors - their orientation (assuming you use tantalum types) should be double checked. Here's a few dodgy pics of my rpi ALDL logger. It's written in Perl and uses an ebay 20x4 LCD connected to the GPIO port. The switch on top of the case is a double throw momentary with center off, connected to 2 GPIOs.
Switch left to cycle through the different screen modes, and right to change the objects being displayed on that screen. The ALDL message and parameter formats are read from a Tuner Pro ADX file (XML format), and data is logged to csv and also streamed over TCP for accessing remotely. It also does a few other things like lap timing because I built it for a track car. It's not quite finished and I haven't touched it in a few months, too many other projects getting in the way. Did you use the schematics posted here?
No, the 1227808 hardware only supported 160bps aldl so I wired a cp2102 TTL module to the processor's UART, so my ECM has it's own USB port. The only difference from a protocol perspective is that I don't have the tx->rx echo like a normal 1 wire ALDL connection does. But handling echo is pretty straight forward, I only did it this way because it was cheaper and easier than adding a true 1 wire ALDL port to the ECM. Using one of the schematics in this thread should work fine (except I think the diodes are backwards in two of them, and probably unnecessary anyway) but you'd then have to get the RS232 level signals into the rpi. You could feed it into a USB-serial adapter, or a MAX3223 (3.3v version of the MAX232) to bring the levels down to 3.3v for the rpi's GPIO UART. Or - just use a USB TTL UART module (about $5 on ebay) and hook both it's TX and RX pins to the ALDL port's data line and ground->ground, and as long as you use a USB module that supports 8192 baud you should have a very simple ALDL connection.