Jump to content

Vaughan

Moderators
  • Posts

    1,988
  • Joined

  • Last visited

  • Days Won

    69

Everything posted by Vaughan

  1. Vaughan

    350z g4x plugin

    Your E-Throttle is jamming shut, in the 2nd log you do a blip and when it goes to shut the throttle it overshoots and goes all the way to 0% where it stays. A lower minimum clamp would reducer how hard it closes it but I would say you need to visually inspect your throttle to see why it is staying jammed shut even when you are trying to open it as hard as possible.
  2. Vaughan

    Trigger Error

    I would recommend changing Trig 2 edge to Falling and then checking your base timing with a timing light. Also as a side note your firmware is quite old.
  3. Can you attach a copy of your basemap and a trigger scope please
  4. Vaughan

    Speedo correction

    As far as I'm aware it is a hardware limitation on the G4+ ECUs
  5. Vaughan

    Speedo correction

    That is a basemap(.pclr) file not a log (.llg) file, you made the same comment earlier. The Multi of 0.83 I provided earlier was based on your other thread where you said you were doing 120 when it said 100. DI 1 has a calibration value of 200 so 10Hz input is about 18kph and from memory G4+ PWM outputs have a minimum frequency of 10Hz so that would explain why it is jumping to ~20kph immediately.
  6. Vaughan

    Speedo correction

    Help manual explains what each of them do, just single click on one of them and press F1
  7. Vaughan

    Speedo correction

    Shouldn't multi be set to 0.8333, offset to 0Hz and max freq to 4000Hz for now until you know how far it should actually move?
  8. It is the same calibration as the Delphi AC IAT
  9. I have used a Link CAN Lambda with the JST 4 pin plug on newer plugins and it has worked fine.
  10. Which ECU is it, is it powered up, can you see the blue light on it?
  11. The 4 pin JST CAN headers were designed with CAN Lambdas in mind and so should be able to supply enough power for them. Note you may still need the 22uF capacitor if you have heating issues.
  12. Sweet, delete that log then and we will try and replicate and debug it here
  13. There's a bunch of missing data in that log as it is an ECU log not a PC Log, if you press F8 or click on the "PC Log = Off" in the top right of PCLink it will take a PCLog which will have a lot more info in it. I have attached a copy of a G4+ JZX100 basemap that I found in my downlaods folder and I can see that it uses a 16ms Master Fuel value instead of 8ms (using the File -> Compare functionality) where did your 8ms number come from? Does richening up the Fuel mixture make it run better? I'm also a little confused as to why your ECT sensor has had the pullup resistor turned off and it set to a calibration table. TOYOTA JZX100 G4+ Base map, Need to confirm fuel pump and speed control.pclr
  14. If you think you've blown the ECU then crack it open to see if there is anything obviously fried, did you put the jump pack on backwards? Otherwise use a multimeter to start testing power to the ECU. There is a pinout for the JZX90 pnp in the PCLink help manual, pins 99 and 100 are the ECU power with pins 33, 52 and 68 being the power grounds. Note for the ECU to be powered the main relay needs to be switched on and this is controlled by ECU pin 59 which is triggered by pin 85 so not a bad idea to check the main relay is operating correctly before checking the ECU power.
  15. So if you try to connect to the USB option there does it work?
  16. A copy of the tune, a trigger scope taken while cranking and a PCLog of a start and die would be a good starting point please. When setting the timing do you have the "Set Base Timing" window open? Also have you done an ignition test with your direct spark setup to confirm that Ignition 1 is wired to the coil on cyl 1, Ignition 2 to cyl 2, ignition 3 to cyl 3 and so on?
  17. We can't do any debugging from here without the actual ECU with log in it but I'll put a ticket in the system to try and reproduce and the step through the code. Just to confirm does the same log do that every time you try to download it?
  18. I have had a generic CAN Open based 8 button Grayhill keypad working with the Link software and have extrapolated out from that for the 6 button, 12 button and 15 button. I have not made brightness control work yet though. What would worry me with the Motec Keypad is that I am unsure of whether or not the Motec specific keypad would have special firmware in it. A good first step might be to wire it up and see if you can find it with the CAN find devices functionality in PCLink. I have no information on how the Motec PDM 30 CAN stream works but @Adamw might. Do you have any documentation for this? Also as a 3rd note if you are using the Motec keypad with the Motec PDM you would not have the ECU talking to the keypad directly as that would conflict with the PDM but instead you would leave the PDM to control the keypad and have the PDM tell the ECU the state of the buttons that are relevant to the ECU.
  19. I found some information for it here: https://www.turbosmart.com/wp-content/uploads/instructions/TS-0305-1001_datasheet/062106325592.html based on a quick look at it you would need to transmit on CAN ID 272 (0x110) at 100Hz. Assuming you are using the ECU boost control function you would put "WGate DC" in Byte 0/1 as a 16bit number with a multi of 10, div of 1 and offset of 0. Assuming only one EGate leave bytes 2&3 empty. I haven't read the manual enough to know what pass through is but at a guess it looks like the area targets are a linearised against area where the pass through targets are based on % of valve lift so most likely leave these empty. with the 2nd CAN ID (0x111) I would say don't transmit this one.
  20. I'm not familiar with this motor, do you have any information on what pattern the trigger disks have and what type of sensors they use?
  21. It will not read as a speed if you wire it to an analog input. The speed signal is received as a frequency with a higher speed being a higher frequency. The actual analog voltage does not matter as long as it is going above the hardware based 'high' voltage and below the hardware based 'low' voltage. The circuits people commonly add between an inductive wheel speed sensor and an ECU frequency input are used because they allow the ECU to still see speed when the wheel is spinning slow enough that the ECU hardware based 'high' voltage is not met but if you don't need to read speeds this low you do not need extra hardware.
  22. G5 Voodoo Pro is the only ECU in the range at the moment that supports direct injectors, pair this with an appropriate driver box to get the high voltages and peak and hold control (The Link DI Driver box is currently under testing). In terms of controlling a diesel engine it can be done with the current software but it isn't setup in the ideal way for a diesel as of yet. You would only have one table for injection timing control, the fuel equation is based around adding enough fuel to keep up with the air rather than keeping the mixture within lean afr targets and there is currently no setup for multiple partial injections like some modern diesels use. We do have plans to support diesel properly in the future but haven't started writing the software for that yet. Personally I've only gotten as far as making a Toyota 1KZ run (mechanical injectors with electrically controlled pump).
  23. Can you attach a picture of which pins you broke? If they're on the ECU you can send it back and have servicing repair it.
  24. Good to hear it is running properly now. Where is the ECU mounted relative to the engine? I'm not really expecting to have issues due to EMF on factory coils but worth checking. Does it only disconnect while running or while engine is off as well? With the Wifi are you trying AP or Client mode or both? Does it show a connection fail message at the top of PCLink when it disconnects and if so what is it? Also can you attach a copy of your latest tune if possible please. Have sent you a slightly newer PCLink and firmware to see if that helps with the connection issues.
  25. If you've already got the ECU wired up then do a trigger scope and attach it here. Googling suggests the crank is a reluctor and I would hesitantly guess 60-2 but would definitely expect it to be a multi/missing. Cam sensors are probably hall effect and most likely needs to be set as cam pulse window but I would need to see a scope of cams at rest and info on how far they swing or scope of at rest and full movement to determine the window location and length.
×
×
  • Create New...