redmist

Looks like its something as simple as my confusion. Its been so long since I've setup ECU logging that I thought the RPM switch was an enable trigger. I've since set my 4k RPM switch to something that I'm not constantly rocking over.

I've just downloaded the first set of logs from my G4+ Xtreme and although there is no interruption to the data it's full of vertical red lines (record start/stop) that simply don't allow me to read the data without a serious zoom in. I've checked voltage around the stop/start and it's sitting at 13.2v, I have noted that the max temp of the ECU is of concern at 150. It's encased in NZEFI's standard encasement with 10 micro relays in said case. Any ideas? Regards, Daniel.

Thanks Scott, I am using the generic dash stream. Using the OilT parameter is an interesting solution and I'll certainly give it a try. Thank you.

I've an AIM Evo 4 that I'm successfully reading CAN bus data from my Link G4+ Xtreme. However Race Studio only allows me to configure the ECU as a Link G4, and will only display a very limited set of parameters. I'm specifically attempting to display my Trans Temperature (AN Temp 4) however Race Studio has no such parameter. The only channel that appears close in Race Studio is "Channel 4" which appears to relate nothing when configured as a G4 and possibly AN Volt 4 when configured as a VIPEC. Any ideas before I attempt to get AIM to release a new version of Race Studio? Cheers, Daniel.

Think I have it. My transmit rate was off. The AIM appears to expect 10hz (which is not what the AIM website states). I'll have to fully configure the dash tomorrow, log data and see if I can build up some oil pressure (or something) to log. Connecting the AIM logger certainly drags down my tuning port. I've yet to try it with terminating the floating RS232.

Dave, thanks for the reply. Have attempted to use both ports (G4 xtreme plus) without success. Suspect it's the fact that I haven't configured a frame. However without specifics on what the parameters and bit length that the AIM is attempting to receive I simply can't configure the Link. It's interesting that it downs the USB connection once the aim loom is connected. I've heard rumors of issues with leaving RS232 floating, however seems weird that even Link supply a USB extension cable that must leave RS232 floating on USB disconnect. Which would indicate that you can't run an extension to a bulkhead and leave it floating, while running a CAN dash. I need to investigate this further.

I've a AIM Evo 4 to which I've wired the CAN high to CAN+, CAN Low to CAN-, and the earth. However I'm not receiving any CAN data to the AIM datalogger. In addition the connection of the CAN cabling appears to drag down the controller (I can't connect PCLink to the remaining connection). Wondered if I'm screwing up something simple. Like not having the RS232 lines terminated, or as I suspect, that there is something more critically wrong with my configuration. I've configured Race Studio for Link CAN_Bus_Base_LLC I've configured PCLink to CAN 1 User Defined, 1mbib/s, OBD off. Transmit Generic Dash, 20hz, CAN ID 1000. Normal. Race Studio doesn't show the link on CAN_Bus Info. (does show both the dash and Evo 4) Cheers, Daniel.

Kerem, I'm doing something similar with a Raspberry Pi (to be ported to a Banana Pi). Don't forget that the Arduino doesn't support RS232 on the board (much as the Pi doesn't, the Banana Pi has CAN). You'll need a shield or an external MAX232 (or similar).  Â

Don't know why this wasn't responded to. However you can already easily do so (although in a race car it's hard to trigger as you are busy). I switch a DI on or off to show issue with performance, then simply search through the datalog for a change in state.

I run a Jimco offroader in NZ. I have my G4 Extreme enclosed in a junction box that has a little room to move and foam padded (simply to protect it from high frequency, high G, Â vibrations). As added protection I run the Marine version, which simply has the Link box filled with a special resin.

I'm attempting to get the onboard logs to be displayed with Trackvision (a data video overlay). I can latch the data to the video sucessfully. However after after a minute or so of video the sync is obviously out by a half second or so. I would estimate that I'm loosing about 4-5 seconds of data sync every 10 minutes of gopro footage. I wondered how the clock worked with the onboard logging. Simon thought that it was based on an iterative cycle and excessive load on the ECU could see the clock thrown out. However I've seen 'stalls' in data that would indicate that when the ECU is busy, data isn't logged the clock still functions. If it is a constant clock error I can allow a slip in trackvivion. (I gather the processor is either slightly under or over clocked??) However if it is as Simon stated based on ECU load and in iterative process count, then there is no way I can predict where and when I need to allocate additional 'slip'.

The question was obviously too simple. As such I'll add a layer of complexity (that I had honestly forgotten about) in an effort tax you. The Xtreme in the new car is also connected to an AIM Evo4 datalogger/dash. I gather this would preclude me from running any direct wireless connection to the link as I'll already be utilising either the CANbus or Serial port and I understand the two ports are not able to be used simultaneously?

Ewan, there are plenty of cheap windows based tablets. I use an EXOPC which is perfectly suited to use with PCLink.

Anyone created, or know of, a wireless Link connection. Ultimately I'd like to connect to my G4 Xtreme for data retrieval via a 802.11 link, bluetooth or even radio (for telemetry). The reason for this being I run an offroad race car through extreme conditions and the Link ECU is well secured in a custom sealed box that requires approximately 5 minutes to dismantle. It means that I only have the ability to retrieve data at the end of the day where it would be benefical to retrieve it as soon as I pull into the pits (within range of the wireless connection). If anyone has a solution, could point me in the direction of a RS232 ->wireless solution it would be most appreciated. Cheers, Daniel.

By the way there is a pinout comparison in the manuals. Start by trying to generate a pinout of your requirements. By venturing over the specs of one ECU you'll venture into the specs of the next. I suspect that the Storm is what you'll require, however if you have a very technical installation and wish to log temps/pressures left and right the Xtreme may be the way to go. I own a Storm on a Celica ST185 Rally car, an Xtreme on my Cosworth V6 twin turbo offroader. Both are very well suited to thier task and I've pushed the boundaries of both with extremely technical installations.

Tom, don't know why this hasn't been picked up by link tech. I'll try to answer to the best of my knoledge. Â 1. The extreme has an external map sensor. It can be purchased with either a 2.5bar or 5 bar map sensor. The storm has a 4 bar internal (early ones had a 2.5) and the atom a 2.5 bar. 2. The extreme silver case can. The extreme red case can't. 3. I run dual maps in my offroader, one spring pressure, one boost control... however I must admit that I've never switched on the fly, although I suspect it'll do so without issue. 4. I think this one is application dependant. I can't run knock because the sensors are either often confused by rocks hitting the block or they die in short order in the extreme environment my car runs in. However I believe the knockblock to be far superior to knock detection included in any of the EUC's. Do you need it? I suspect not.

Most appreciated Ashley!

I've garnered these logs from the onboard logging during last weekends race. Unfortunately we didn't pick up on these issues as it only appears at low throttle utilisation and non steady state. The onboard logging doesnt log and VVT parameters other than cam actuals. Cams are Cosworth ZK2 270 degree ramp to ramp, 10.65mm lift. Ground from billet. Haven't checked the pressure to the solinoids. However ramp rates both up and down can match, but intermittently don't even try. If this were to be a hardware issue it would appear that they sometimes ramp perfectly and other times have the ability to ramp (you can see the jagged lines as the solinoid duty cycle is increased then decreased again) but for some reason don't. The heads, pistons, rings, rods, cams, bearings, oil pump, hardware are all Cosworth. Block and crank are modified Nissan 350z.

Unfortunately the onboard logging doesn't log VVT error counters. (or at least I haven't found them). Both VVT solenoids have been replaced. We've always experienced some form of VVT inbalance between banks however it's more observable given on board data logging (it tends to be worse in low RPM low throttle situations that weren't tested on the dyno). It's also more critical given the huge investment in the new Cosworth/Nissan engine. I'm no VVT expert. But I would think that given VVT's simplistic nature that if it traced both ramp up and down correctly in other advance requests (as it often does) then it should function in a consistent manerism for all advance/retard requests. I would guess that my next step is to log runs to a solid state device via PC Link to get error counters?

Having problem with VVT inlet cam activation. On a V6 engine both cams are in sync for a good percentage of the time however on the outskirts of the VVT table where interpolation is biggest they become wildly out of sync by up to 22 degrees. PID setup is default. Cam control mode is VQ35. I've included a snapshot of the issue (my logs are over 10mb each).

I've just employed two new Garret GT2871's to replace my GT2560r-4's. We retuned for one more PSI of boost, however I've seen my IAT's increase and my compressor temp also leap. I wondered if 99 degrees C (in a very short run. I suspect much greater when racing) was common for a sensor placed at the turbo compressor outlet on only 16 psi of boost. Cheers, Daniel.

I agree that the latest version of PC Link is very powerfull for datalogging. However without a movie like trim ability irrelivant data skews most of the displays (other than time plot where data can be ignored). The only experience I've had with datalogging is my own Java app which stored parameters in plain text and AIM Race studio. Both are easy to trim.

The X/Y plots, histograms, statistic logging display features are fantastic. However useless if you can't manipulate the data by removing warmup and cooldown. Triggering the log features the instant the green flag drops and the checkers are unfurled isn't an option automatically when warmup reaches race pace. Manual triggering also isn't an option (I'm not that regimented). As such it would be very useful to be able to trim a log to the duration of a race. The ability to trim a log would also give you the ability to concentrate statistics on one lap only or any period where statistics, histograms, X/Y Plots, etc were necessary.

The new data analysis features in the G4 PCLink are a fantastic to allow a basic understanding of engine parameters. However histograms and statistics are useless without the ability to trim staging/ warming up or cooldown of the engine from the logs. It's not alwasys feasable to switch a DI while attempting to launch. I wondered if I'm missing something and there is the facility to trim both warmup and cooldown from the logs, or if this is something I should add to the wishlist? Regards, Daniel.

I've heard rumours of a new datalogging/ analysis application. I wondered if it were possible to integrate an auto-reconnect into the software such that if the car is restarted the logging software would reconnect. This would allow common use of something like a solid state laptop to record data from racing events. It's simply impossible to run through a series of mouse clicks in order to reconnect while staging or racing.