mattj

Yeah, you guys already did that with me. Your team couldn't find the issue. It was suspected to have something to do with the layouts, but nobody on your team wanted to spend any more time trying to figure it out. I'm sure there are notes on the case. I might even be able to dig up the old case numbers.

Answering the phone and talking to me about a problem that requires a software update to solve is NOT considered support in my book. Had I been told there was no more software updates for this product, I would likely not have purchased it. I would be more than happy to package up my laptop, power cord, monitor and any other supporting devices and send them to NZ if I thought Link cared even a little bit about solving this issue. I understand that companies need to allocate resources, but I do feel neglected as your customer and responses such as this...that suggest that the problem is rare, doesn't show the genuine care I would have hoped for. I BOUGHT 4 LAPTOPS trying to solve this issue. Clearly, I care about the issue.

Yep. No solutions either. Yeah, Link abandoned this product long ago. Shame on them. I'm on to my fourth laptop. And still have the same issue. It's better with Windows 11 (less frequent, but still occurs), but I still can't count on the program staying running, and have to work around it. Not sure WTF is happening. When did you buy you Thunder? Frankly, I don't appreciate this comment. Simply because YOU haven't seen and YOU can't reproduce it, doesn't mean it's not happening. None of this is related to monitors sleeping. I could fill your tech support people with info, but none of them care OR have the experience to handle this level issue. It needs an engineer and it needs Link's willingness to solve this problem. Perhaps they are buried in the G5 that still hasn't surfaced. I understand that it doesn't make financial sense to spend time on an old product, but I still feel like I was left in the cold on this. Perhaps you, after years of this BS, can ask your tech team to reach out to us and try to solve this issue. I would appreciate some attention to this issue.

Try this again... The problem I'm having is that the system does not disable. When set to Single Launch RPM, the "Disarming Speed" attribute is not available. When using the Single Launch RPM feature, the setup defaults to using an attribute called "Arming Time" instead. I tried playing with that, but either way, it doesn't disarm. The Help File, under the Single Launch RPM section, says that the system should disarm once the vehicle exceeds 0.0 kph, but I'm not finding this to be the case. It does seem to work with 2D RPM Launch RPM Table mode though. But, I have to enter the desired launch RPM in the "0" speed cell for the Non Driven Wheel Speed table, and then enter an RPM, like 10,000 in all the other fields for additional speeds of Non Driver Wheel Speed, to keep it from activating at other speeds (I won't reach 10000 RPM). Does that make sense?

thanks. Still can't get much through here. I called Link. They verified the possible issue using Single RPM Launch mode. Work around is the 2D Table mode.

Thanks for the reply! Yes, that's exactly what I'm trying to set up. Basic single drag launch. Sorry, I have to enter just a few words at a time to get this site to post my reply. Dang, I can't get it to post anymore of my message. d

I'm trying to understand the intended design of the Single Launch RPM feature. Should I simply be able to enable this feature, using a throttle position and have it disable once the vehicle exceeds 0.0 kph, like the help file says? It won't let me upload a pic right now.

Oh! I just saw it. Thanks! I really appreciate it. This works well!

Thanks Adam. I was simply trying to determine the best way to install wires into the back of the ECU plug (connectors). I couldn't find any documentation on assembling the connectors. Is there something in the help files about this? I finally found a video on a Haltech connector assembly. Looks like you just push the assembled wire/terminal through the back of the plug. Is that the correct procedure for these?

Is there any information in the help file/program about how to best install new pins/terminals in the connectors (plug C and D)? I have difficulty doing it with regular ease and figure I'm doing something wrong.

I figured it out. I had the pullup resistors wired incorrect.

I just installed 4 new temp sensors on my engine and connected to the Thunder channels An Volt 13-16. I get Error Low value (# 105, 108, 111, and 114) on all four channels. I've checked the sensors and all the wiring and it's good. I put a volt meter on one of the wires coming from the D plug (An Volt 14) and checked voltage relative to sensor ground and get 0V. Is there some additional switch that has to be turned on in the software to get these channels to turn on?

Yeah. I tried to do that yesterday. I'm no rookie to upgrading drivers, but I LITERALLY cannot find support for my laptop anywhere on Intel's site. Even Dell's program to auto-find drivers for you said it found one, I went to install it. It said it failed, and then all of sudden said there were no updates available. WTF?! This isn't rocket science. What is Link's future plan for support on the G4+ platform. They have not updated this software for two years and I'm ready to abandon Link at this point. I found a driver (manually) on the Dell website (not Intel), but it's the same version as the driver I have. I don't see any option to change/modify OpenGL settings either. What is happening when when I load a layout file? Is there another options file that gets modified to "remember" that layout, and auto-load it next time the software starts? FURTHER UPDATE: I just reloaded the Link software. Didn't mess with any layout file. Used what ever is default. Already had the external monitor connected. Opened the software. Opened my tuning map file. Opened a logfile. switched Display mode to Log Analysis. Move the program window to the larger monitor (extended displays)...waited a minute. CRASH! Ugh!!!

No. I load a layout just after starting the G4+ software program. Then I start logging and driving. Most often, it crashes before I can even stop and save the log file.

It’s not just that. It still crashes while I’m driving around logging data. No monitor changes RE there. Must be related to loading layout files. I’ll try it without loading a layout file and see what happens.

Just found something interesting...it actually holds pretty stable until I load a new LAYOUT file. Appears to be any layout file. Then, as soon as I disconnect/reconnect the HDMI external monitor, it crashes.

Update. New laptop all together. Still crashing. Freshly install of the software. I did copy over my options file though. I was out driving around and logging some data. Crashes before I can even save the log file. Pull back into the shop...and I noticed as soon as I plugged in the external monitor, via HMDI, to the laptop...the software crashed again. I'm testing now to see if it will just crash with nothing attached to the laptop, other than a USB mouse and the power cord. Also, I brought the laptop home and plugged into a different external monitor, also via HDMI, and it crashed on the home external monitor too. EDIT: While the laptop just sits here with the program open, no external monitor connected, and viewing a log file...it crashes.

Is there a reason GP Speed cannot be displayed in MPH?? I want to use all four wheel speed sensors for other reasons, and I want to use the GP Speed parameter for displaying the speed from my VSS on my manual transmission, displaying them all in MPH. Can this be accomplished?

Ok. What is the difference between Exhaust Pressure and Crankcase Pressure here? Both are listed in the pick list of choices for an analog input, but Exhaust Pressure is “defined” and “Crankcase Pressure” is not.

Gotcha. Turns out I have both coolant temp sensors assigned to "Engine Coolant Temp". What happens when I do that? If I set the second coolant temp sensor to GP Temp, I don't have an option to select the GP Temp as a Function to monitor. Still says "AN T3 - {"my custom Label"}. It does this for my added sensors for other pressures too, except there is a built-in function for exhaust pressure (this one shows up correctly and displayed in PSI as expected), and a built-in function for "Crankcase Pressure - but this one doesn't display as crankcase pressure...just AN 4 - "my custom Label". I can show you in another video if that helps.

Here is a video link hosted on google. I can't get a video under the 5MB limit. How in the heck did you do that? https://drive.google.com/file/d/1l88Q93Dc6240WLKgHAUUFCVaeOxzzxij/view?usp=sharing

I can't figure this one out... I'm using the AN Temp 3 and 4 with sensors for both coolant and oil. When I use the Deg F for output units in either Cal Table 1-3 or Cal Tables 7-10, I get temps that appear to be in Deg C. When I switch the Cal Table Output Units to Deg C, I get temps that appear to be in Deg F! What is happening here?

Sweet!!! That's awesome! Such a well thought out software program. I wasn't understanding it's function correctly. Thanks!!

Oh, gotcha. You mean when I have a logfile open and then I open a layout file, it will pertain to the Log Analysis mode? Then, if I load my basemap, and then load a layout file, it will pertain to the ECU layout?

That makes sense. Do the new layouts that were posted recently still use the Log Analysis views? I figured out the Log Analysis screens work with the old original layouts. They don't do anything with the new layouts. Could that be possible? I'll have to see if I have software that can record the screen still.