Vaughan
-
Posts
2,133 -
Joined
-
Last visited
-
Days Won
74
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by Vaughan
-
-
6 hours ago, Purpleline said:
Seems no response on the knock ctrl even i set gain up to 200 fm deflault at 10. Knock level show nothing jumping... either narrow or wideband nothing happen (at 6 to 10)
Make sure Disable Digital Input is set to off or is inactive, if that doesn't work check the knock status runtime
-
How many pins does it have? You can typically figure out if it has an internal igniter based on the number of pins and by measuring the resistance between certain pins.
-
-
-
-
-
what does the hardware ID show up as when it isn't installed via legacy hardware? (i.e. when it is showing up under other devices)
-
Have you got the tuning cable plugged into the correct port? (the USB port on the side of the Top Board, not either of the CAN ports on the bottom board)
-
-
13 hours ago, Adamw said:
in the next firmware update you have the ability to enable user configurable 3D tables for update rate and gain
When Trim Limit tables is set to 3d tables the update rate is changed to a 3d table
-
A bunch of CAN streams will be included with the next release
-
Could you please attach a copy of your basemap, are you doing this offline or while connected to the ECU?
-
A few notes:
- In G4X set your ethrottle target table to 0% at 0% accel pedal and set the idle base positions to the appropriate tps targets for idle. (G4X uses a clever bit of code to combine ethrottle and idle targets to ensure on exit of idle that the position doesn't dip).
- Closed loop idle only uses Integral control, Ignition idle uses Proportional and Derivative control
- Torque management help hasn't been done yet and that code isn't officially finished yet, I plan to test it more (has already had a decent amount of testing) and write the help for it either this week or next week.
- Accel sens was initially a single value but it was requested that it be made into a table to reduce it's effect "at the top end". I would recommend turning on asynchronous injection (under fuel main) and then seeing if you actually need accel enrichment, I found with my car that asynchronous injection is faster and more precise than a more traditional accel fuel. I'll make sure this help is corrected if I haven't already done so.
- Have a play with that accel fuel axis to see what suits your car the best, any feedback on this is much appreciated.
I've attached a copy of the basemap from my 2GR-FE, It should be a half decent example of an ethrottle idle setup although I am not using closed loop idle, just open loop and ignition.
-
During shifting you should typically hit the TPS Delta lockout meaning no CLL over the shift, when in overrun it is disabled by the overrun fuel cut (if you are using it).
-
gain table should get more aggressive with bigger errors, the setup you have will cause large oscillations at small errors and very little change at big errors, mine looks like this:
-
will be in next release
-
Typically update rate is smaller (like 1Hz) at lower rpms and faster (like 10Hz) at higher rpms, Gain control typically has a smaller gain at smaller lambda errors and a larger gain at larger lambda errors (for my car I use 2,3,6,6,6,6 but have a play to see what suits your car)
-
had a quick look and it happened when you moved from the idle control being locked out by your vehicle speed to being in closed loop idle control, the blip is the 2% idle base position being applied then after 2 seconds the closed loop idle kicks in and pulls the idle speed down.
To fix it consider reducing your ISC Base Position values in the 80-100deg c range
-
12 hours ago, Adamw said:On 6/7/2020 at 3:03 AM, Rozsko said:
Just updated the firmware.
After clearing the fault codes, it seems the ANV4-5 low voltage errors did not come back (and now I have the TGV option in the menu) and the Underflow error is also gone.
However the overflow error (code#8) came back.
Any more suggestion on that?
I might call upon @Vaughan to reply on this one, he may know more than me. I thought this should be fixed in 6.16.27 and I havent seen it on my car.
TGV was only added in a more recent version, make sure you are using the sample map from the newest release (can use the compare function to see changes) as there are some things like the 4D fuel table which is TGV based. Shouldn't be able to get Fault 8 or 9 in the newest release as the code to set it as a fault was removed so please clear it again and see if it comes back (could theoretically show up when loading older base maps as the fault codes are stored in them).
12 hours ago, Adamw said:Played a little more the afternoon and finally connected the rotary switch I mounted earlier.
While doing that, I spotted a small glitch either in the software or in the help file. There is no Label field, but the help says there should be one.
just had a look and yup no labels in the release but they are in the newer stuff and so will be in next release sorry
-
-
You're going to have to explain that a little clearer
-
if the gauge is outputting 9V to the ECU then that gauge output isn't compatible (signal to ECU has to be with 0-5V). 9V into the analog will read as 5V and so will 1.365 Lambda meaning the calibration and analog input are working correctly but the signal you are feeding into the ECU is not correct.
Adam and I were both looking for the voltage value that can be found in the runtime menu (F12) Analog tab next to Analog 5 as that is the voltage that the ECU is reading and passing through the calibration.
-
On 5/31/2020 at 8:51 AM, Adamw said:
What does the runtime how as the voltage on AN Volt 5?
Need to know what the voltage of the analog input is showing, a copy of your basemap and short log might help with this
-
to do the timing on my 2GR we bolted a pointy piece of aluminium onto the timing chain cover behind the crank pulley so we could time it by looking at it from a different angle. This did mean we had to make a different mark on the crank pulley to suit based off of cylinder 4 (was easier to get to than cylinder 1) top dead center.
Engine died while running
in G4+
Posted
18 & 52 are the main grounds I believe, 27 & 28 are sensor grounds and 35 is the trigger ground