Announcement

Collapse
No announcement yet.

Help! having issues connecting to the ecu with winlog for dataloging

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Help! having issues connecting to the ecu with winlog for dataloging

    Hey all! Attempting to get some datalogs for my tuner. Have all the tunerproRT, winlog and github downloaded and setup per the wiki, i thought. I cant seem to connect to the car though. Tried on two different computers with the same outcome.Tries to connect but wont. Has anyone experienced this? Any ideas? What did i do wrong...
    Reading ottowa coupes recent post, need to verify the map sensor is correct. pretty sure it is but still.
    Any help would be greatly appreciated. thanks all

  • #2
    What's the issue exactly? You have converted the ECU hardware wise like wiki describes? Is your car stock? Have you used the files provided by wiki, written them onto chips? Chips installed in the ECU? Does the car start and run, but you have problem connecting Winlog to ECU?

    Comment


    • #3
      trying to get a solid tune on this car. tuner said we can log then sent me the m232.org and said read the winlog part. So, that said, im assuming he's using all this stuff. Car runs, but tune is way off. Not stock, speed density kkk24-7400 with siemens 630 injectors. Im now trying to do said logging and have followed the wiki for setup. all seems to be working. but yes, my issue is the winlog or tunerpro wont connect to ecu. when it stops raining I'm going to try turning off fast diag to see it will connect.
      He is a reputable tuner in this community here in the states. Dont want to names names out of respect....

      Comment


      • #4
        Assuming you are using blue VAG KKL cable, there is not much I can suggest really. If you are running Windows 10 then drivers for the cable should be installed automatically and you need to select correct COM port for your cable in the Winlog device configuration screen. Click on M2.3.2 Fast Logger and then click on settings on the right. Type in correct COM port for your cable (you can check it in Windows Device manager, by unplugging and plugging it back in) and select your MAP sensor from the list and press OK.

        Comment


        • #5
          I am using an older blue vag cable assume its a kkl. We've done that in our trials yesterday. when selecting the map, it wouldn't hold setting in the window either. not sure if its supposed to or not. The computers see the cable in the usb ports. Tunerpro starts trying but instantly fails to connect. winlog just does nothing

          Comment


          • #6
            MAP selection disappears from the selection box after you click OK, that's normal. If the COM port typed in the dialog box is correct then it should work. Make sure you are using one program at a time. Launch Winlog, turn the ignition on and you should see data streaming. If not, it's either a driver issue or cable not compatible etc. Try using VCDS with the cable, see if it works. Just make sure you hold the throttle WOT while turning the ignition on, otherwise VCDS won't work.

            Comment


            • #7
              OOOOOO!! I did have both programs open at the same time.. without thinking about the splitter being needed. Duh! Will be Attempting as soon as the rain stops. You may have figured it out. fingers crossed. If not the case a new cable will be coming to try asap. Ill also attempt to use the VCDS with fast logging turned off. Awesome advise! Really appretiate the help. I'll keep ya posted here. Could be tomorrow

              Comment


              • #8
                Originally posted by booested4door View Post
                I am using an older blue vag cable assume its a kkl. We've done that in our trials yesterday. when selecting the map, it wouldn't hold setting in the window either. not sure if its supposed to or not. The computers see the cable in the usb ports. Tunerpro starts trying but instantly fails to connect. winlog just does nothing
                If you have an S6, you need to connect the two green wires on the immobilizer unit.

                Comment


                • #9
                  it is an s6 harness but in a 4000q. Did the US cars even have immobilizer yet? Haven't had to deal with it to this point

                  Comment


                  • #10
                    update: still not working. Closed all programs and reopened winlog to the same results. Just says awaiting to sync. Ecu has a flex map sensor with 4 written on it. I assume its a 4 bar. Maybe its my cable. looks different then the pics and doesnt say "vag kkl"
                    Tried VCDS lite, it works with this cable. it aslo works without holding throttle to the floor upon key on. If i DO hold throttle WOD and key on, VCDS works the same but has another code to .. 00516. Shareware version- to deactivate all DTC's 30-00 please register/activate
                    so.... not real sure what/why...

                    Comment


                    • #11
                      Couple of posts back I asked specifically: "You have converted the ECU hardware wise like wiki describes?" Judging by your latest post, you don't even know what's the hardware inside ECU. If your cable works with VCDS then it's very likely going to work with Winlog too. The fact that VCDS works even without holding throttle to WOT means that your are not running prjmod. The code it throws for TPS switch is normal.

                      So, is the hardware inside the ECU converted like it's instructed in m232 wiki?

                      Comment


                      • #12
                        i didnt know what map was in the ecu. I didnt set ecu up, the tuner did. ive since opened it.. i have a flex map in there. Definitely different then the one in the wiki. Have an emil into tuner about this.
                        Just tried old vagcam cable with usb pass through and it didnt work either.
                        No tps code. and vcds does work without WOT. Im going to be real mad if my tuner lead me to a dead end on this. he's really vague about it all

                        Comment


                        • #13
                          Hard to judge from distance really, information is so conflicting. If the car runs and your tuner directed you to wiki, I would assume he did the conversion and used basefiles to do you a software, but for some reason used different MAP sensor and you still have a problem with connection to ECU. It might be because of immo as jonn48 suggested. Next logical steps would be to read "Immobilizer bypass" section in wiki and since you already opened ECU, check if the resistor is gone and additional wire is soldered from one board to another as per wiki.

                          Comment


                          • #14
                            update: Tuner finally checked his records.. turns out my file isnt M232. So no wonder i cant get this to work. lol. Hes sending me new M232 files in a weekish. Well go from there. Thanks for all the help guys, really appreciate it.

                            Comment


                            • #15
                              So now your tuner uses basefiles from wiki and does you new software/sends you new chips, but at the same time you have some random MAP sensor inside your ECU and you still didn't confirm is the resistor removed and wire soldered or not? And you're expecting it to work? Isn't it more logical to ship your ECU to tuner and tell them to do all the hardware mods required and install chips with the correct baseline software at the same time? This way you have higher probability to end up with a working solution that can use fastlogging too but only IF you overcome the hurdle of those 630cc Deka's which won't work with this ECU very well. See ottawa coupe thread for more info on that.
                              Oh and the hurdle of the need for 2 emulators with the associated wiring and boost board etc to get the ECU mapped properly, but your "reputable tuner" should know that already.

                              Comment

                              Working...
                              X