Jump to content

Josh Colombo

Members
  • Posts

    41
  • Joined

  • Last visited

    Never

Everything posted by Josh Colombo

  1. I took a video of the MAP upload process that shows what is going on. http://www.youtube.com/embed/6GkeNb92dPQ' width='425'>
  2. Found the thread. Â It has some more details and information in it. http://www.linkecu.com/forums/G4Forum/366050229
  3. I just thought I'd bump this thread since this bug is still present, and it'd be nice to try and get it fixed. Here is a recent post with the same issue. http://www.linkecu.com/forums/G4Forum/92137685 Â Thanks JoshÂ
  4. I am running the latest firmware & PCLink with my G4 and get the same result. Â I've experienced this issue for years! Â I'd have to go back and look through old posts and emails to see which version it first started happening. Josh
  5. I'll second this request. With the current export option, the table does not come over to Excel cleanly.
  6. Jurgen, I have to chuckle about this.... The back story is that I have a LinkPlus G3 that has been running G4 firmware for over two years. I rebuilt the motor in my Legacy, so the car was down for a long time, and when I finally got the engine back up and running, I updated the firmware to the latest version. Upon doing that, it was discovered that the new firmware version with CAN would not allow me to simply unplug the Display Link connector from the cord plugged into the ECU so I could connect via PCLink. This is what I had to do previously, and I was ok with it. What I was told is that I could not have the cord plugged into the CAN port on the ECU, I would have to unplug it at the ECU. Since my ECU is under the carpet in the passenger footwell, doing that every time I want to connect via PCLink wasn't a workable solution. I was told that there was a hardware upgrade that could be performed to my G3 that would allow both the Display Link and the PCLink to communicate at the same time. So I sent my ECU to NZ to get upgraded. When I got it back, I still couldn't connect via PCLink & have the Display Link connected. After talking with Link some more I was told the Display Link needed to have hardware upgraded as well. This unfortunately was missed the first time around, which could have saved time and money.  I was able to work with one of the US dealers and he was able to give my Display Link to someone at Link during the SEMA show. I received the Display Link two weeks or so ago and am now able to connect both the Display Link and PCLink. But now you're telling me that I can't configure what options I want to come across using CAN. I'm a little frustrated with this whole situation. I'm not sure what the difference between the Vipec and Link products are, but if it's just a software change, I would encourage Link to allow the Display Link settings to be configurable on Link ECU based products Thanks Josh
  7. I was wondering if there is a way to add or change the data that goes to the Display Link. Specifically, I would like to add EGT values so I can monitor them on the Display Link. I recently had the Display Link & ECU hardware upgraded so it can communicate through CAN. From what I can tell, everything is working correctly with the CAN communications, I just would like to be able to see EGT values on my Display Link. Thanks Josh
  8. Well I just got done comparing two maps and I will say that the new feature of holding down ctrl while clicking on the main headings to display all the sub headings makes a world of difference! With this new feature and having two instances of PCLink open, it wasn't too bad comparing the two maps with a high resolution display. If anyone else has other ways they do it, feel free to share. Thanks Josh
  9. I was wondering if there was a way to compare two different map files to determine what the differences are between each. I can open two instances of PCLink and try to go line by line, but that's very time consuming. When you could print the MAP's out, I would print them out or PDF them and then compare the MAP's. it would be nice to have something like this again. Any other thoughts on how to do this more efficiently other than opening two instances of PCLink? Thanks Josh
  10. Scott, Thanks for the explanation. Yeah my ECU is a Link Plus G3 that has been upgraded to the G4 firmware and has received the CAN hardware upgrades. I'll do the work around for the time being, but will provide feedback on future firmware releases to let you know if this bug is fixed for my ECU type. Josh
  11. Ok, I tried making a small change to the map, (knock target values) and uploaded the map to the ECU. The same problem occurred, the knock system was disabled, and I could not re-enable it. I power cycled the ECU, and then was able to re-enable the knock system. I've attached a copy of my map. If you'd like any additional information, let me know. Josh
  12. Well I tried uploading a modified offline map again and it still disabled the knock system. The one thing to note though is that I upgraded the firmware to 4.8.81 and then uploaded a map that was modified when the ECU was running fw 4.8.5.  I'm not sure if that matters. I can try saving the map now that the firmware is at 4.8.81, make a small change and then upload it to see if the problem is still there.
  13. Thanks for the feedback Jurgen & Ashley. I confirmed this issue last night as I did another full offline map upload. I could re-enable the knock system after only driving for about 5 minutes. I will try the latest version 4.8.81 and see if this issue still remains. Thanks Josh
  14. I've got an odd issue, which I'm not sure is a bug or is by design since I've not experienced it before. I was making changes to a map file offline and then uploaded the map to the ECU. After the map was uploaded I noticed the knock system was disabled/off. I tried to turn it back on, but it would not let me. The selection went right back to off. The knock system was enabled and working before I uploaded the offline map. Once I drove the car for a little bit and got it up to operating temp I was then able to turn on the knock system. This ocurred this past weekend. I am running ECU firmware & pc link version 4.8.5. I have not tried to reproduce this issue yet, but will most likely be making some additional changes to the map offline and will see if I get the same behavior with the knock system being disabled. Thanks Josh
  15. Scott, Thanks for the reply and information. I will keep an eye out for the next release version to see if the fix is included in that version. Josh
  16. Just saw that a new version of PC Link has been released that looks like it should address this issue. Here are the release notes for the latest version, 4.8.8 (rev 1122). I'll try it this evening and see if it works.  Release Version 4.x.x.1112  New Features · Logging sample history.  PC Logging now keeps a rolling history of all parameters selected for PC Logging.  This allows snake trails to be displayed on all tables (previously only displayed on tables being viewed). · Pre-pend history to log file.  The sample history can be automatically added to the start of PC log files.  Eg if a glitch happens when not logging, can press F8 and catch it in the history. · Surface graph position and reverse bottom axis setting is now remembered for each table. · Table snake trails can now be globally turned on, off or paused with a single key (F6). · Log views now show status type parameters as their actual text labels (eg ON or OFF instead of 1 or 0). · An option has been added to PC Logging Setup to select either a zoom all or zoom to shortest section upon opening a log file. · A new option has been added to the log parameter select window to only list parameters actually contained in the current log file. · An all new axis setup form. · Settings groups can now be opened from the ECU Settings Menu by pressing Ctrl while clicking on a heading.  Eg This allows all Aux Outputs to be listed in a single settings view rather than clicking Aux1, Aux 2 etc.  Or, viewing of all fuel corrections in one settings tree.  Fixes · GP Aux Output switching condition values could not go below 0 when using temperature as a condition. · The save file name was not reset when changing from one ECU to another that were exactly the same type and FW version but different serial number. · Extrapolate function did not work correctly on tables. · Launch Control ignition trim could not go to positive numbers. · Many memory leaks that could cause excessive memory use when the application is open for extended periods.
  17. Jurgen, Any update on this issue? Is this something that will be fixed?
  18. I tested a fresh installation of PCLink on a new partition of windows 7 last night and just tested the log play back on my work computer and got the same results as noted above. So I'm pretty confident it's not related to my specific computer. Josh
  19. Thanks for confirming the limitations of the wasted spark setup. I have thought of converting to the individual coil setup, but haven't done much research on what I can shoe-horn in there. Unfortunately, the first generation Subaru turbo legacies in the US were setup with wasted spark ignitions vs. individual coils. Thanks Josh
  20. Hi Jurgen, The log that I am playing back was definitely captured with the PCLink. As for 'Log All', I am pretty sure that I clicked add all button below the logged parameters in the Setup PC Logging. I think the only thing I might not have added was some of the CAN bus stuff. I've gone back and clicked the 'Log All' button just in case. I don't believe it's the 'Log All' button issue because I had one of the Link tuners send me a log to playback and it did the same thing. This was a log that was recorded from a completely different computer. What I will try is installing PCLink on a fresh partition of my laptop and see if it exhibits the same behavior. The only difference would be the current OS is Windows XP, while the test/new partition would be Windows 7. I'll let you know what I find out. Thanks Josh
  21.  I am running the most current PCLink software (4.8.5.1078) & firmware (4.8.5) and am experiencing an odd behavior during playback of recorded log files that were recorded via the PCLink software. I can playback the log files ok, and the parameters I've setup in the Logging tab are displayed correctly. However when I go to the tuning tab, none of those values or table show any active movement. The same thing occurs when I go to the various tables in the Config tab. It appears that only tables that are more than one row show active tracking of where the data was recorded.   I do not know if this is normal behavior, but in the older versions of the PCLink software I could go to the various config data and the active tracking window would be displayed based upon the logged data. If this is normal behavior, is there a way to change it so the various tables and parameters are displayed correctly and based upon the recorded log file?   I have taken a screen capture video during playback of the log file to demonstrate what I'm talking about. Any help or suggestions are appreciated.  http://youtu.be/N_touARn2DE   Thanks Josh       Â
  22. I wanted to confirm that the knock control is setup this way for wasted spark ignitions.....based on the help file, the most I can get is knock detection on paired cylinders? So for a 4-cyl boxer engine, cylinders 1 & 2 share the same coil, as do cylinder 3 & 4. The firing order is 1-3-2-4. I'm assuming cylinders 1 & 2 share the same trim table, and cylinders 3 & 4 share the same trim table. Is this correct? What happens if you set each cylinder to have its own trim table? Do cylinders 2 & 4 just not have knock control on them, or does the knock control in general just not work? In previous PC Link/firmware revisions, several years ago, I could have sworn the individual trim tables for each cylinder worked with the wasted spark setup. Any feedback on past knock control? Thanks Josh
  23. Well after trying a bunch of different combinations of things and talking with one of the US Link Dealers we got it figured out. It turned out to be an issue with the upgrades to the CAN system and the fact that I had the DisplayLink cable plugged into the ECU, even though it wasn't connected to the DisplayLink. PCLink version 4.6.0.601 is last version before the CAN system got a major overhaul. This version of PCLink & firmware worked with my ECU after downgrading the firmware. Once I went any higher, I couldn't connect. We finally determined the DisplayLink cable being plugged in was the cause. Once I removed the cable from the ECU, I could connect to the ECU with the latest version of PCLink, 4.8.1.1033. The Link Dealer indicated that there is a hardware upgrade that can be made to my G3 ECU as well as other G4 ECU's that have similar issues that will allow the ECU to communicate with the DisplayLink and PCLink at the same time. So I just sent the ECU back to Link for the upgrades. Hopefully this well help someone else in the future. Josh
  24. Continued here http://www.linkecu.com/forums/G4Forum/386128839
  25. I updated the firmware to the latest version 4.8.1.1033 from version 4.4.3. It succeeded successfully, but once it completed the update I’m now not able to connect to the ECU any more. I tried uninstalling and reinstalling PC Link and the USB drivers. The USB drivers detected the ECU on initially being connected but I still can’t connect to the ECU, neither with PC Link or the firmware updater.  I even tried a different laptop, and got the same response, 'Unable to connect to ECU'. When I get a little more time, I will check the power going to the ECU, but I believe it's fine because the tach sweep is still completed when I turn the ignition to the 'ON' position (This is controlled via the ECU), so I would believe the ECU is still working. Other notes is that I have the Display Link wiring hooked up to the ECU, but the Display Link is not plugged into it. Also this is a G3 Link Plus ECU that has been running G4 firmware without any issues in the past. Any ideas or help would be greatly appreciated? Thanks Josh
×
×
  • Create New...