Jump to content

Cameron Bradley1436215391

Members
  • Posts

    9
  • Joined

  • Last visited

    Never

Everything posted by Cameron Bradley1436215391

  1. Drop me an email. [email protected] I have an EZ30R base map I'm willing to part with. Currently there is no way to use the MAF sensor for fuel calculations, however I've been working with Link on getting this sorted as I intend to use the MAF for smoother running and ease of tuning.
  2. If its a G4 we're talking about it should use a USB not serial cable?
  3. So this will allow a reasonable range for those that were just incorrectly ranged, or have only the '0 and 0' ones been fixed? I don't honestly understand the point of setting these ranges narrower than either the limits of physics or the scope of the datatype used to hold them as it can be, to say the least, extremely frustrating.
  4. This is driving me a wee bit insane. I've encountered a fair few bugs (and they're definitely not features) in my time working with PC-Link (and it has been short so far). These issues have, honestly, had me looking for alternative engine management as it would be an understatement to say I am a bit disappointed. Fuel table axes: why allow people to select MAF sensor values as axes to a table if you're not going to let them set it up properly. They all stipulate 'Y axis values must be between 0 and 10' or similar, which makes it impossible to configure a fuel table that'll actually run an engine. (I'm not questioning that this stuff is primarily intended for speed-density, but don't _offer_ MAF options if they don't work) Transient Ignition Retard: Initialising the table to defaults results in an error regarding min=0 and max=0 with regards to row headers, this doesn't make any sense until you go to set up the table and initialise the axis with TPS Delta as the variable. This results in an error when applying: 'Y axis values must be between 0 and 0' (REALLY?!). Permitting it to set it up with a single row of '0', results in a mass of 'Invalid Floating Point Operation' errors when you touch the throttle pedal. (The attached image shows just the first error, this machine is not attached to the vehicle so is unable to replicate the rest of the errors) My thoughts on the above are: - If this software was not properly bug-tested before release, what were the testing engineers doing? If you aren't able to set something up a certain way by design, make this clear, don't throw a meaningless error (or crash the program as sometimes occurs). - If it is not worth the time to develop all these addons that may only suit a few people out of the thousands of customers, perhaps open-source the communications protocol to allow people to develop their own software and extensions for their own application. As an aside: Why all the proprietary hotkeys? Anyone coming from a background of using computers on a daily basis expects Ctrl+O to open, Ctrl+S to save, etc. It's honestly a bit odd to expect people to memorise a complete set of different hotkeys just for your application and quite frankly a bit user unfriendly. Version in use: 4.9.2.1175
  5. I'm using Knk Internal. I have switched the sensor out for one from a 1990 Legacy which seems to have caused some improvement, however I'm still not seeing readings over ~77 (with gain x1.5, the max for the Xtreme) for what I assume is severe knock. And I still see nothing recorded at Low RPM/High Load, despite being able to hear the clattering. Based on the above information I'll replace both sensors with earlier ones and wire them in properly. However this still doesn't answer my question about the frequency filtering.... Which setting is best for a 6.4khz knock frequency (i.e. what are the attenuation slopes on those filters)
  6. Hi Guys. I'm having a bit of an issue with the knock detection/control setup on my early-model G4 Xtreme (5100-series serial number) When I go to configure it both the options for the Xtreme and other ECUs show up rather than only showing up the relevant ones, this is somewhat confusing and probably a bug. My second dilemma is that the engine in question is a Subaru EZ30D (05-06), I'm not sure if these knock sensors are compatible, however the calculated estimated knock frequency is around 6400Hz. This is nowhere near any of the available settings on the Xtreme, which would be best pick? With either 5500Hz or 7000Hz I'm picking up knock where I believe the engine is not knocking, and not even getting the slightest change in the level when I intentionally induce low RPM/high load knock. Your thoughts are awaited with anticipation. Cam
  7. On a side note, i cant log back in or reset my password, i have to create a new user-id every time the session is reset, password resets say they cannot find the username, logins fail, and registration claims the u/n already exists if it try to reuse it.
  8. I am having a deeper issue which i may have to call you guys about tomorrow (couldnt get it fired today). Basically (bearing in mind i have only just realised i should be using the map that came with pc-link not the one on the ECU) the problem is that I cannot get the ECU to fire the main relay, and hence its reporting a low-battery condition. whenever i connect pc-link it complains 'ECU Hold Power Active: Engine has been shut down', it will not turn the relay on at any time, nor will it attempt to fire the injectors, ever. it does however have spark (which doesnt cease when you stop cranking, despite 0rpm) If you could offer a solution would be absolutely brilliant. I am using the map that came pre-programmed on the ECU, I will download the EVO-5 base-map that came with pc-link before attempting another start tomorrow to see if it makes a difference.
  9. Hey. got a bit of a situation here, I have to fire up a car tomorrow, instead of the usual 560cc injectors it has 800's, I have re-scaled the fuelling map to 70% of the original, this should assumedly be sufficient? it will be being professionally tuned straight away, just need it to run to get it to them
×
×
  • Create New...