Galletto 1260 Drivers Windows 7

 
Galletto 1260 Drivers Windows 7 Average ratng: 8,0/10 4763 reviews
  1. Galletto 1260 Drivers Windows 10
  2. Galletto 1260 Software Download

Re: Galletto boot mode and 64bit win7 « Reply #8 on: June 27, 2012, 03:54:09 PM » no better luck on the xp machine so i am convinced that my 'boot mode inactive' prompt is a bunch of bs. And I know the ecu goes into boot mode because I can read the 95040 chip with argdubs command prompt tool. May 24, 2013  GALLETTO 1260 Download GALLETTO 1260 Drivers Download GALLETTO 1260 User Manual 1260. Thanks mate, you have saved me from smashing up my laptop LOL!!! I've used a laptop with windows 7 64 bit and one with windows XP on it.

Galletto 1260 is an affordable and easy-to-use ECU programmer for DIYer. But sometime errors occur when using the cable. Diyobd2.fr gathers some frequently asked questions and solutions of Galletto 1260 EOBD1260 ECU remapping tool.
Error 1: “Turn off dash, wait 10s then turn on”

Galletto 1260 Drivers Windows 10

Installing EOBD1260 on Windows 7 to remap Honda Civic V2.2 ECU edc16 c31, after click write ECU data button, the system displays an error message: “Turn off dash, wait 10s then turn on”.
Galletto 1260 requires a minimum car battery voltage to operate properly. Otherwise it will fail to read ECU. Make sure your battery is fully charged. Besides, better to install EOBD1260 software on Win XP system.
Error 2: “Speed Change”
When trying to read ECU of Audi A3 1.8T 180hp 2002 ECU with 1260, the Galletto display an error message “SPEED CHANGE”. It is the ME751 or ME755 29F400BB 29F800BB, in several places I read say the ECU’s 180hp is 29F800BB I tried to read with the driver ME751 29F400, but the error occurred SK1-SeedKey error.
You cannot change the speed in clone galletto 1260. Pull the ECU out of the cat and try on the bench. If it doesn’t work on the bench, look for other tuners, like KESS V2, FgTech Galletto 4 master that won’t kill your car. .
Error 3: Cannot read ECU
Follow the instruction on video to install the EOBD1260 software, try both on Windows XP and Windows 7, but still fail to get the ECU read.
The galletto 1260 is aimed at the Bosch EDC16C31 ecu which stamped on the label outside the ECU. If you want to program other ECUs, this cable will not work.
If galletto is able to program your ECU, then the driver is faulty or misconfigured or the cable is bad or user error.
Make sure you setup the cable to use com1 under derives in windows 7.
Make sure the drivers are good.
Connect the cable to the laptop away from the car and install the latest drivers.
Error 4: Laptop issue
Plug the galletto 1260 cable into the vehicle OBD port, the red light flashes, then connect the USB to a rather old laptop and configure the device. When try to read ECU, the system report an error after 4 minutes.
Make sure you use the same port on the laptop that you first used when installing EOBD1260. You probably need to install the latest FTDI drivers.
Error 5: “ERRORE SET_ECU”
Windows
After install the FTDI drivers, trying to ECU ID the program starts to read but nothing other happens. The process stands at 0 % and after some minutes the error “ERRORE SET_ECU” appears.
Make sure the driver is correct installed and the COM port is set to COM1.
Problem:
When try to read out Alfa 2.5V6 ME 2.1 ECU, the system display error message: “ATTENSTION BEFORE TO CONTINUE:REMOTE FEEDING,PUT PIN 24 FLASH EPROM TO MASS GIVE FEEDING AND REMOTE TO MASS PIN 24 FLASH, END TO CONTINUE. SEE THE PDF FILE IN FOLDER DECOMENT”

Galletto 1260 Software Download

Set the COM1 on windows. Need to connect PIN 24 on the ECU itself to the ground. Not OBD pin. Look at ECU, there are 2 big connectors. You need to find the right connector and then plant a wire on pin 24 and ground it.

Ceci est du support technique du site WebOBD2 Outil de diagnostic:Galletto 1260 ECU remapping tool errors and solutions

Toyota Techstream softwareis verified to work no issues on 64 bit operation systems incl. Windows 7, Windows 8, Windows 10.

FYI, Techstream Windows 64 bit is tested by users, not pros working for obd2diy.fr.

Here you go.

Techstream Windows 7 64 bit:

Quick note on techstream 10.x with windows 7 or greater x64 with the 1.4.1 (and possibly the 2.0.1) Mini VCI cable. I was having absolute fits trying to get the driver recognized. Turns out the cable was being recognized as a Broadcom Bluetooth 3.0 Chip. If you select that device, Select Update driver, Select Let me Pick From a list of device drivers on my computer (letting windows scan a specific location doesnt work), then click have disk and browse to the location of your MCVI drivers (Should be C:Program Files (x86)XHorse ElectronicsMVCI Driver for TOYOTA TIS) and go to the ftdibus directory and select the ftdibus.inf file. This will get the correct drivers in place for the bus. The COM drivers will install automatically after you get the bus driver in place.

Hopefully the search engines pick this up and it is helpful for someone else.

Techstream Window 8 64 bit:

Got my Techstream (10.30.029) cable and software working on Windows8 64-bit laptop. Here’s what I did.

  1. I ordered this cable/software from Amazon. Was $15 with slow boat shipping, took 2.5 weeks to get.
  2. Load this page since I used this for most of my steps, http://blog.obd2diy.fr/2015/08/12/how-to-install-techstream-v10-10-018-in-windows-78-64bit-os/
  3. First thing you need to do is install the driver for the USB/OBDII cable. Follow the steps outlined in”Installing MVCI Driver for TOYOTA” of the ft86club post. I used the “Mini VCI Driver for TOYOTA.msi” in the 10.30.029 folder that came on the CD from Amazon
  4. After drivers are properly installed and you verify you can see the device connected on the XHorse Firmware Update Tool, you’re GTG
  5. Next up is the Techstream software, from the included CD I ran the “Toyota Techstream 10.30.029.exe”. After installation I went into the C:Program Files (x86)Toyota DiagnosticsTechstreambin folder and replaced the “MainMenu.exe” file with the one found on the CD.
  6. You should be able to load up the Techstream link that was installed on your desktop. When it asks to register with a new key, use the key found in the “serie.txt” on the CD.
  7. Next you’ll need to update your registry, on the ft86club post there’s a Dropbox link and with a “mvci-x64.reg” file, download this and run it.
  8. Open up Techstream, go to Setup menu, VIM Select, and choose the XHorse – MVCI. This will have Techstream use the XHorse – MVCI cable.
  9. If you try to Connect to Vehicle you’ll get a message that forces you to update the software. To get around this disable your internet connection (turn off wifi and/or unplug your ethernet cable). Now you can start and use Techstream without the force update check.
  10. When you connect there’s a counter in Techstream that only allows 30 connections to your car without an internet connection. To get around this go to the C:Program Files (x86)Toyota DiagnosticsTechstreamEnv folder and open the “IT3UserCustom.ini” file. Towards the bottom there’s a “ConnectionCount” variable, just update this to 1 when you get close to 30 connections.

This worked for me… hopefully this will save everyone some time/hassle. I would be careful of what you try to update in Techstream. I just updated the unlock so a single press will unlock all the doors. I also viewed some data on the TPMS stuff.

Techstream Windows 10 64 bit:

This link describes the installation process, possibly with link to the software.
https://goo.gl/1wGRR9

I think the first requirement is that your miniVCI cable hardware is capable of 32 and 64 bit, I think some of the earlier cables may be 32-bit (XP) only. If capable of 64-bit, then they give you a small CD with some special files “XHorse” and it takes a little bravery to mess with your Registry etc.

Btw, Many people will not be able to follow the instructions to install the necessary cominents. No judgement here, it is just reality.

Which is why I up telling people to stick with using an XP laptop instead.

That would be great if you have an XP laptop (or desktop) available…it is definitely a much easier install. But going forward I presume that’ll be harder to find. I thought the Win10 instructions were a little confusing but I worked thru it.

Qui ont consulté cet article ont également consulté: