JMP
-
Posts
329 -
Joined
-
Last visited
-
Days Won
16
Reputation Activity
-
JMP got a reaction from Steven100 in Jzx100 wiring in a mac valve to expansion loom
I'd wire it to INJ8
-
JMP got a reaction from Steven100 in Jzx100 wiring in a mac valve to expansion loom
Feed one wire on the mac valve with ignition switched 12V, then connect the other wire to one of your spare Aux out's
-
JMP reacted to DO1023 in Idle Up when in Gear
Actually I think I figured it out. I did a static GP idle Offset by a GP Output that has conditions
Cond 1 or 2 or 3
Gear == R
Gear == 1
Gear == 2
Offset idle by x
Where x is a static RPM number.
This seems to have worked
-
JMP reacted to Confused in Long Term Fuel ignores Closed Loop ECT Lockout?
Your Warmup may well be "tuned" - but it's "tuned" based on the operating temperature fuelling table - which CLL and LTFT are indicating are incorrect.
So - with CLL and LTFT Learning enabled, you are slowly correcting your underlying fuelling table.
Remember that the Warmup stuff is making modifications on top of the underlying fuel calculations from the fuel table - you've baked in errors here - so your now "tuned" warmup needs re-tuning based upon the corrected values in the main fuelling tables.
-
JMP reacted to 2.0L_turbo in mounting bolt size
Glad I could help man mine definitely had me running around till I thought to try a pitch gauge and realized it wasnt metric lol
-
JMP got a reaction from 2.0L_turbo in mounting bolt size
My
Mine is the same, was doing my head in trying to figure out what thread it was meant to be
-
-
JMP got a reaction from Dave Kriedeman in PCLINK crashes regularly still
Is anything recorded in Windows Event Logs when it crashes? I'd expect something to be logged in either the Application or System Event logs which will point you in the right direction
-
-
JMP reacted to OzoneNZ in Apple M1 (silicon) and Windows ARM USB Drivers
Just came across this issue today with a new ARM64 MacBook Pro 14" and thought I'd have a crack at trying to build a customised driver for it before I found this thread
The latest Silicon Labs universal driver for the CP210x chips (10.1.10.103) supplies binaries for x86, x86_64 and ARM32 / ARM64
The driver bundled with PCLink appears to be the slightly older 10.1.3.2130 and only supplies x86 and x86_64 binaries as stated
I modified the 10.1.10.103 driver manifest to include the Link USB vendor/product IDs and disabled Windows driver signing and it seems to work like a charm, though I only played around with it for 5 minutes
Picture of PCLink running on Windows 11 ARM64 virtualised under MacOS Monterey 12.0.1 attached
@Adamw I know that MacOS support has specifically been ruled out, but is there any chance of the universal Silicon Labs CP210x driver version 10.1.10.103 being rolled out with a new PCLink release?
Having the driver properly signed would be awesome and make the process painless, as well as adding support for real Windows ARM64 devices which are bound to become more prevalent in the next few years
-
-
JMP reacted to Vaughan in Moristech P30 PDM CAN Integration
The PCLink CAN ID is in Decimal, use 1024 for 0x400
-
JMP reacted to Adamw in Moristech P30 PDM CAN Integration
Yeah what you have there will just about work (except the offset) by the looks but I would do it slightly different - just to make it clearer. In the Link frame setup, set the ID position to none (only used for compound messages). This then allows you to use all 8 bytes if you want to. I would use MS first (I find it easier to understand), and the offsetr needs to be -1 (this is because in G4+ the aux status "off" is sent as a 1 and "On is sent as a 2. The -1 offset will change this to 0=off, 1=on as the blackbox expects.
So Link set up like this:
PDM fuel pump like below, fan will be the same except message byte number Byte 1.
-
JMP reacted to Vaughan in 2GR-FE Wiring
one pin to switched power, one to an Aux, doesn't matter which way around the pins are, I used Aux1-4 but any of Aux1-10 and any spare inj or ign pins will suit from memory.
I ran Bank 1 Inlet (rear bank) to Trigger 2 and used DI1-3 for the other 3 banks, DI4 can be also be used but you do need to connect Trig2 to one of the cams.
I can't remember which way round I wired it but one of the crank pins to Trig 1 and the other to signal ground, it is quite easy to tell from a triggerscope whether or not you have these two the right way around, they do have to be a particular way.
I just used the Link Looms so Shielded Trig 1&2 but not the other cam sensors.
I've attached a copy of my basemap from a while ago, my engine has Cams and slightly bumped compression and there are a few other things setup in there like the ECU controlling the temperature gauge and speedo. That being said it should be fine for figuring out the basics and getting the engine started.
2GR 309whp.pclx
Have just realised that this is in the G4+ forum, your setup will be slightly different again if you are using a G4+ but the gist of it is the same
-
JMP reacted to Adamw in Ecu to pdm via can
Yes you can do this a couple of different ways.
One option is; In the ECU you still assign the function you want to an auxiliary output - lets say as an example we set up engine cooling fan on Aux output 1. You dont physically connect any wires to aux 1. You then use the "A1 (status)" parameter to send to your PDM over CAN. The Aux status parameters are sent as follows: 0 = OFF, 1 = OFF, 2 = ON, 3 = FAULT. You can use the Multiplier/divider/offset to scale that into numbers that your PDM wants. For instance if your PDM wants 0=off, 1=on, then you use an offset of -1 to get that.
Heres an example:
An alternative option is very similar to option 1 but use a Virtual auxiliary rather than a real auxiliary - this allows you to keep the real auxiliary output free for doing other stuff (you only have a max of 8 virtual auxiliaries however). Set up the virtual auxiliary just like you would set up the normal auxiliary, then send parameter "VA1 (Status)" to the PDM.
Here is an example for a Virtual aux set to fuel pump. (note the ECU will still handle the normal fuel pump prime logic etc):
-
JMP reacted to wastegate in Link user CAN help
Update, HGM fixed the firmware and now have gear change request.
Thanks Adam on the torque reduction strategy, works a treat. Just need to fine tune it. I've reduced the IGN trim retard a little as I don't have 20 degrees of timing in some spots and it's getting retarded too much and seems to spike boost.
-
JMP got a reaction from Dave Kriedeman in Introducing RealDash - A Dashboard App for Android & Windows
you should contact the realdash developer to get it addressed, you can find the datastream layout in the link help file under "Technical Terms and Reference > Communications" where it states DI1 through DI6 speed streams are transmitted in KPH. Gear position is also sent in the stream so it's up to the developer to get it sorted, not Link Support
-
JMP reacted to remski2 in Engine wont rev to redline under load
Your TP voltage is spiking to 11V at your 110% TP.
Most TP systems operate a bit below 5V.
-
JMP got a reaction from Nate in 2jz gte vvti in G35
The missing tooth looks to be in the same position as the retaining tab when the keyway is facing straight up
-
JMP got a reaction from Nate in 2jz gte vvti in G35
kind of common for people to damage the teeth on JZ crank sprockets when they remove them but dont remove the tab on the intake side of block first, usually ends up ripping the trigger wheel off the back of the sprocket
-
JMP reacted to Adamw in Too high VE issue
I dont see much wrong with the set-up. As above, turn off IAT trim and the 4D table as a start but I dont think these will solve the problem.
If it were mine the next step I would take is a basic flow test on an injector to confirm it is actually 1000cc. You can get a pretty good idea just by connecting an injector direct to a battery and holding it open for say 30seconds and measure how much fuel you get. You can usually just hose clamp them in a piece of hose, dont need the rail etc.
And I would try to confirm the fuel pressure with a gauge or similar - just to confirm the sensor is reading correctly. I have had mislabeled sensors before.
-
JMP reacted to MichaelR32GTR in Link fury wideband issue
Problem solved !
new “resistor” spark plugs went in
ecu logging is off aswell
and wideband doesn’t drop out and works perfectly
thanks once again !
-
JMP got a reaction from MichaelR32GTR in Link fury wideband issue
wouldn't happen to be running non-resistor spark plugs?
-
JMP got a reaction from Adamw in Link fury wideband issue
I'll bet that's your problem, tons of EMI from non resistor plugs
-
JMP got a reaction from TechDave in Mixture Map
my understanding is Overrun Fuel cut > 0.5 will only show cells where overrun is active. I usually set mine to show Overrun Fuel Cut < 1