Jump to content

senordos

Members
  • Content Count

    11
  • Joined

  • Last visited

  1. Hi Gerard, Changing scaling didn’t work for me. I installed the latest Intel graphics driver (it said it wasn’t supported (yet) for my laptop, so it was a bit of a pain to get on there - but it should be mainstream now). Since doing this it’s been fine. Cheers, Christian
  2. Hi Dave, Sounds good! When is 5.6.6 coming out? ...and what does it fix? Cheers, Christian
  3. Mine is also slow for the first, day, 30 seconds... then it picks up. I’m assuming this is the software just loading itself up?
  4. Hi Richard, I'd tried that before, but had "this software is not verified by your manufacturer", or something to that effect. However, your response prompted me to try again and force it on, old skool. The PCLink Software appears to be responding better now - so fingers crossed it was the driver. Seems odd for a brand new machine, but so long as it works for now. I'll keep playing and see what happens. Thanks for the tip. Christian
  5. Hi Adam, Thanks for that, but I'm afraid my display is already set to 100%. Everything there is on the recommended settings. The problem remains :-( Christian
  6. Hi, I'm having a problem with the PCLink software. When I change the layout - or even switch from fuel to ignition maps, the tables / graphical views fail to refresh properly, leaving images of whatever was there before in place. It works when I first load the view, but if I change anything it fails. I've searched for forum and I can't find any resolution to this (I've seen that there was another thread where people were experiencing slowdown). I'm using a brand new Lenovo laptop bought specifically for the purpose of mapping a car - this is the only software running on the machine. It's Windows 10 and the latest version (2017?!) of the PCLink software I can find. The PCLink Version Information says the following: Version: 5.6.5.3338 Build Date: 09:44:11 Feb 15 2017 DLL Version: 3372 Build Date: 15:09:01 May 16 2017 OpenGL Version: 4.5.0 - Build 22.20.16.4815 Renderer: Intel(R) HD Graphics 610 Vendor: Intel I've attached a screenshot of the issue... the right hand corner window is completely inoperable. I've reinstalled the software with no benefit. Any help greatly appreciated - I need this to work in Jan to get the car mapped and ready for the race season. Thanks, Christian
  7. Thanks Adam, If it's OpenGL 2.1 it needs, then I think you're right. I've done some further research (googling) on this too and it seems many others have struggled with OpenGL after 1.1 on VirtualBox. No problem - thanks for the info.
  8. Hi, I'm having an issue with the graphics view (see attachment) - the text appears simply as a white box. Has anyone experienced this before? I'm running on Windows 10, but in Virtualbox on a Mac. Cheers
  9. Hi all, Thanks for your help on this. I've bitten the bullet and gone with the Fury... why not! Cheers.
  10. Thanks everyone. Seems that the Monsoon does pretty much all I need it to, the closed loop lambda, closed loop boost control. The question is, do I want to run the knock control? For this, do I just need to wire the donut style sensor direct into the ECU (Fury) or do I need a controller for this between the donut and the ECU? Also, with the research I've done, I see that other ECUs (like the Haltech) make minor updates to a second ignition map if knock is detected, essentially reducing timing over time if knock continues to be sensed. Does the Link do something similar with its knock control (and for that matter, the lambda and the boost if off target)? Presumably it's possible to see in the logs that it happened anyway? Thanks.
  11. Hello, I'm looking at purchasing a Link ECU. I've been recommended the Monsoon, but I want to understand the features I'll be missing. I have tried to understand this from reading their forums and manuals, but welcome any tips from HP Academy. From what I see, there are sufficient inputs and outputs for my needs. The car runs a single coil on a distributer, so I actually receive 3 additional outputs. Question 1: I want to wire in the lamdba from my AEM Lambda controller... but my understanding of the spec sheet suggests that I wouldn't be able to run "closed loop lambda" (I think Link call this Closed Loop Lambda Auto Mode). This is something I was interested to play with - but I've managed without before. The Storm or the Fury are a good few £££ extra, so not sure it's worth it. Am I right that the Monsoon does not have closed loop lambda. Question 2: I've previously also experimented with closed loop boost control. Is this feature available on the Monsoon? Question 3: The Monsoon has a CAN bus which I intend to use for my Race Technology Dash2... the spec sheet warns that I'd need additional inputs for a 2nd CAN bus... is there any reason I'd need a 2nd CAN bus? Question 4: Knock control. The Monsoon does not have this. The advice I've received is that, as a hobbiest tuner, this would require a lot of work to setup right. They suggested I'd be better with the separate Knocklink light. I also have a KX-3, although I've only had varying success in setting this up. Ideally, it it's simple enough, I'd like something on the car to tell the ECU if there is knock, although I've managed for many years without this, so it's probably not a must have. Thanks for any tips... I simply want to make sure I make the most efficient use of my budget. Cheers
×
×
  • Create New...