jdniss

Yeah based on old XRC5964S specs, it looks to be roughly GTX3576R sized? But this 5964S compressor will flow 90lb airflow somewhat similar to the compressors in both the GTX3584RS or G35-1050.. I fully expected the 0.64 rear A/R to choke up top - seems way too small from typical convention - but these are seemingly beneficial over the prior 0.82 results.. Be interesting to see if he comments on the EFR question in that thread - he mentioned in a prior video that BW EFR's were the "cats pajamas 10 years ago", but by the sounds of things all his kits have been using Xona for quite a while now.

Potentially some interesting data for some of you here; Hank Iroz from Iroz Motorsport testing a new Xona Rotor 5964S on a Audi RS3 2.5L DAZA motor. https://facebook.com/share/p/14EU18MyDqZ/ Cliff Notes: Turbo has the new Xona XRE compressor aero with an X4C compressor cover, reportedly 0.64 rear housing. 900whp (670kw) @ 37psi, 170k shaft speed, motor is making 2bar (29psi) boost by roughly 3800rpm, 500lbft (670nm) torque by 3500rpm. They overlaid a stock RS3 on USA 91 fuel (red), and a "Stage 2" RS3 on E85 (yellow), and this 5964S (blue) - the 5964S isn't losing any ground to either. Apparently out-flowing their prior tests with a Xona 8264S (green), and this 5964S (white) also has a smaller A/R than that did.

Slightly off topic - I've just wired oil pressure sensor into my LinkECU as well - I tapped into the existing dash cluster oil pressure light wiring, and fed that back into an Auxiliary output in the ECU. That now lets me control the original dash oil pressure light based on a range of conditions triggered by the LinkECU - means the factory light isn't entirely redundant now that the factory oil pressure switch is no longer installed.

I've heard several stories where 4-ports were ditched due to poor boost control resolution, both external gate and twin-port internal gate (including a number of tuners) - I bought one myself to replace a 3-port but never installed it. Stephan Papadakis mentioned they use dual solenoids per wastegate on their Supra drift car as opposed to a single 4-port ~ around the 11min40 mark, should be timestamped:

Andre from HPA suggested in a webinar targeting a slightly lower than 100% TP target as not to smash the E-Throttle blade into the stop and run the risk of snapping it ~ something like a 98-99% target instead; Though the max e-throttle clamp in this tune is 99% DC - so maybe that achieves the same thing? -Same here, I don't have an E-Throttle to compare against, just guessing 😄 Yeah it'd be really nice to see a full WOT log past 6000rpm with a heap more parameters enabled, or the laptop plugged in doing all the logging @CowsWithGuns. Might rule out whether VTC switch on/off point or E-Throttle target or RPM/MAP limiter is playing a factor in the low power.

Is there supposed to be a "hole" in the E-Throttle target table from 6000~7000rpm below 100% TP? Theoretically you wouldn't hit it under 100% WOT, but seems odd

This popped up as a "similar thread", if its suitable for you @Adz2332, and/or still available:

The AtomX has even less inputs/outputs than a MonsoonX @Adz2332 https://linkecu.com/products/ecu-comparison-chart/ The PluginX ECU (based on the XtremeX board as Robbo mentioned) has dropped as low as $1,915AUD on sale, and the last generation G4+ Plugin ECU's dropped as low as $1,320AUD on sale

Just an FYI @Borci88 - try not to be too rough with the USB end of these adapters - I've just had the USB connector snap off the board internally, taking the solder pads with it - I suspect due to vibration in the car, over 24 months. Have since found the 'MeatPi WiCAN' that looks to be almost identical - however also features Bluetooth, WiFI and can be powered off a 12V source, rather than USB powered like the SeeedStudio adapter. https://www.meatpi.com/products/wican There also looks to be a USB-C version without Bluetooth and WiFI: https://www.tindie.com/products/meatpi/meatpi-usb-dual-can-adapter/

There is a forum - not a whole lot of useful info RE: Haltech though. https://www.realdash.net/forum/viewtopic.php?p=7176&hilit=haltech#p7176

It looks to be the generic "CAN Definition" pre-loaded into RealDash to connect to a specific Haltech CAN stream. In RealDash you'd load this file via Garage > *Door* > Dashboard > Connections > CAN Definition File > Haltech > CAN V2; Then assuming you had the matched CAN Config loaded into the Haltech - it should start transmitting data to RealDash. Not sure what that would be though - nothing jumps out at me in ESP/NSP. In the Link ECU world the matching CAN Stream is for memory "Generic Dash" - then you'd select the corresponding "Link Short CAN" Definition file within RealDash to read/display the CAN data within that stream, on the RealDash side. Nothing gets installed onto the CAN Analyzer per-say - you configure a CAN Bit Rate (ie. 1Mbits) and CAN ID (ie. 1000) once, via the provided Seeedstudio software - this must match the CAN Setup on the ECU side, otherwise it won't work at all.

The developer has a full Haltech XML up on his Github, some of the commands down the very bottom look pretty close to my current CAN "Send Button" toggle actions to the Link - the startbit and bitcount data matches those functions - so it may be possible.. https://github.com/janimm/RealDash-extras/blob/master/RealDash-CAN/XML-files/Haltech/haltech_v2_can.xml Github Haltech XML My Link XML

Just warm up enrichment percentage - I was chasing my tail on a few things and it was using it shortly for troubleshooting, but never got around to swapping it out for a different parameter. It also had a 'VTC/NVCS Active' light for a while, along with current 4D Ignition value - but swapped them out for "CLL Fuel" Closed Loop Percentage and AFR Target. The current config is sending across roughly 35 different parameters from the ECU - but only displaying 10 or so on that first page. Yeh, at least with a Link ECU - this is being used on an Android phone currently - just to toggle different Boost Maps via CAN on that first page - you could create a whole page of buttons and replicate a keypad. Effectively any ECU function that be toggled via CANBus, should be possible to toggle from RealDash ~ Launch Control activation, Intercooler/Water Spray, NOS activation, Fan activation, etc. I don't have a Haltech ECU to test with, so couldn't tell you 100%; Might be worth asking the question on the Realdash Forum - https://www.realdash.net/forum/index.php

Depending on the generation of Link ECU - G4+ vs G4X, the G4+ will transmit data to RealDash via the Link USB Tuning cable and an ECU configured 'Serial Datastream' https://www.realdash.net/forum/viewtopic.php?t=21 Unfortunately the Serial Datastream > RealDash function isn't available in the G4X and is somewhat limited in parameters anyway. That said - the CAN Analyser method Duncan suggested is definitely the way to go; Not only because it opens endless possibilities with fully customizable CANBus Streams - allowing you to send almost any parameter from the Link ECU you want, but due to RealDash having the ability to both send and receive CAN Data - RealDash can be setup as a CAN Keypad as well via triggers or onscreen "buttons"

Looking through the various Instagram comments; G25-660's 0.72AR, VP Racing Fuel, AMS Alpha 4.0L BC stroker VQ, high comp JE Pistons, nitrous, Motec M150. 812rwhp and 676rwtq @ 22psi