Jump to content

Forced_Firebird

Members
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Forced_Firebird's Achievements

  1. Thanks a million. The reasons and explanation you listed is why I stayed with MaterCam 8 until running virtual machines on XP became a pain. The native keyboard shortcuts made for quick programming out of the box -9 and 10x+ had drop down menus.
  2. Got the Link connected and the car running. The m50 is in an e30 with a Holset hx55, and just has a modified stock chipped ECU, stock injectors, 4psi WG spring. The o2 feedback tot he stock ECU was/is non-functional as it sits, so there is no narrow-band, even at the moment. Already installed is an AEM 35-8560 Failsafe just being used to monitor boost/AFR. The e36x pinout shows that AN Volt 3 is already set up for oxy sensor, so is it just as simple as running the 5v reference from the AEM to the stock o2 input? Also, the stock m50 has a cheesy IAT in the intake manifold. I'd like to put a new one in the charge pipe, so this should be another easy one? Swap the pigtail for the sensor connector, change the settings in Link? Just want to make sure before poking around. Thanks!
  3. Success! Dealer gave a new code last night, came in this morning and hooked up lappy to Link, but the PC still wasn't finding it. Went in device manager and could see Link connected to USB (with the warning triangle), but not COM. Ran through yesterday's procedure in my memory and realized I had done a safe start (f8 on boot), and turned off "windows forced driver signing", started up and BAM! I get the little "successfully installed Link" bubble window. Put the new code in and all is good. This is a new system to me, so the interface will take a little getting used to, but it seems like very capable software. Thanks all for the help. Now for the learning curve for new software, lol. I was using HPTuners yesterday, Link today, and have a Megasquirt project tomorrow. At least it's not like the old days of winOLS and map hunting....
  4. Typo. I sent a pic to the dealer, now he says the system is glitching and he has to contact Link, so wait yet again. ^^this is the pic that was sent to me of the code. Underneath the box in the photo "do not include any leading zeros", right below a box with a leading zero. Sent him this pic so the number with the first generated code, so the number would not get confused: Today, got to the shop, entered the code sent, took a pic and sent it to the dealer: I get this: Dealer said something is wrong with the system and must wait until he talks with Link.
  5. Yes! Came in this morning, hooked it up, opened device manager and saw "Link Engine Management LTD (COM3), tried connecting to the ECU and it worked. Dealer sent a new code, and that's bad too. He was very difficult to get a hold of yesterday, plus he is multiple time zones away, so cannot even call until afternoon. Serial is 600453 and the code sent 089158c7ea84361d "Failed to unlock the feature in the ECU with error: Function Failed"
  6. I get checks for two drivers, same thing happens when trying to connect.
  7. Thanks! After poking around and looking at what the dealer put in as a serial was in fact the "0707429", so even if that were the serial, from what I am reading the "0" at the beginning would have caused an issue. Waiting to hear back from them. I Error when running the _x86: "You have to run the 64-bit version of DPInst.exe on this machine. Contact the vendor you provided"
  8. Serial number in the Link isn't matching whats on the sticker on the PCB. PCB S/N: 707429 When opening link management: 600543 without the ability to change
  9. Hooked up a win10 laptop (not the one for tuning), and was able to connect right away. Now it's rejecting my unlock code "failed to unlock the feature ECU with error: Function failed".
  10. This is annoying. I've always been able to grasp communications for devices. Went in device manager, uninstalled the g4x, scan for hardware changes, and it automatically tries to install as USB. Manually set to com port 1, tried reconnecting everything, same gig. Manually set my baud rates and com port to 19200, 8, none, 1, none to match the link (set to manual connect), and still get error 1005
  11. Wasn't sure if I should start another thread or rely to others, but seems a common issue for people to connect the first time. Anyways, laptop is Toughbook CF-31 running win 7 pro. The laptop has a native rs232 com port, USB ports, and have had drivers installed for the COM/USB (ftdi) etc. After reading the forums, tried installing earlier versions for g4+, reinstalling g4x without drivers, etc, but I keep coming across the same problem. Went in my regedit, reset all the com ports, and dedicated com1 to be open. Uninstalled/reinstalled several times, and I cannot get a connection. I can see when the Link is plugged in, it's just staying on USB and get a windows driver installation error.... Thanks for any advice
×
×
  • Create New...