Dean Posted December 8, 2020 Report Share Posted December 8, 2020 I've just finished the migration from Fury G4+ to G4X. Traction control was working normally on the previous ECU. When I set the Disable DI to DI 6 it keeps showing up as Knock Table 5 Level and I can't seem to get it to work properly. My DI 6 switch is providing 12V to the pin. Photo and tune file attached. Any help would be appreciated! Cheers. Dean G4X 081220 Updated Firmware.pclx Quote Link to comment Share on other sites More sharing options...
koracing Posted December 8, 2020 Report Share Posted December 8, 2020 So the I/O in the G4x is a bit different. It appears whatever file you started with had that input set up as Knock Table level 5. The simple solution is to create a GP input on the digital inputs called Traction Disable and reassign DI6 to that. I'm not sure how you can actually select Knock Table level 5 as the pin assignment in the software. Ok, I realize now that when you do that it disconnects it from the traction disable... There must be a software bug in the naming of that input when assigned to traction disable. A work around would be to assign it to the GP input as I describe and then set a virtual aux output to be the disable on the Traction control when DI6 is active. I'm not 100% sure that will actually work... Quote Link to comment Share on other sites More sharing options...
Dean Posted December 8, 2020 Author Report Share Posted December 8, 2020 Thanks for the response. Yeah, the only way I could get it to show up normally is the Virtual Aux/GP Input method. I'll give that a try for a bit. Weird that it keeps getting stuck on the knock table. Quote Link to comment Share on other sites More sharing options...
koracing Posted December 8, 2020 Report Share Posted December 8, 2020 The Knock Table Level is the knock level for that cylinder and should be a built in fixed table and not an input - so I think it would probably work fine as is with the wrong label, as I can't see it actually being an input pin assignment, but yeah let us know how it goes. Quote Link to comment Share on other sites More sharing options...
Adamw Posted December 8, 2020 Report Share Posted December 8, 2020 It looks like it is just pulling the wrong label from somewhere, I just tested on the bench and it works fine just how you had it set up originally. I will report the issue to engineering and get it fixed, but for now it does actually work. koracing 1 Quote Link to comment Share on other sites More sharing options...
koracing Posted December 8, 2020 Report Share Posted December 8, 2020 Adam, have you tried any previous firmware/software with this on the bench as well? Quote Link to comment Share on other sites More sharing options...
Adamw Posted December 8, 2020 Report Share Posted December 8, 2020 Im not sure what value there would be in that. I dont think it will be a difficult one to discover since it is obvious and reproducible. Quote Link to comment Share on other sites More sharing options...
Dean Posted December 8, 2020 Author Report Share Posted December 8, 2020 Just had a thought. I'm using a modified version of the custom CAN setup from my G4+ (to communicate with the AIM dash), and I replaced a few of the original Knock Level spots with my digital outputs (logging, traction, launch, boost). Could the CAN setup be messing with labels? Quote Link to comment Share on other sites More sharing options...
Adamw Posted December 8, 2020 Report Share Posted December 8, 2020 No, nothing to do with CAN. BTW, the CAN is quite different in G4X so you will have to rescale lots of parameters. There is a new "configurable generic dash" template in the PC Link CAN folder to give you something to start. Quote Link to comment Share on other sites More sharing options...
Dean Posted December 8, 2020 Author Report Share Posted December 8, 2020 1 minute ago, Adamw said: BTW, the CAN is quite different in G4X so you will have to rescale lots of parameters. There is a new "configurable generic dash" template in the PC Link CAN folder to give you something to start. Yes, I did notice that. I offset the few that need to go negative (temps and MGP) in the Link CAN setup, and the rest (kpa -> psi etc) in the AIM custom CAN. It's been a good journey to really get to know the software back to front! Quote Link to comment Share on other sites More sharing options...
Vaughan Posted December 14, 2020 Report Share Posted December 14, 2020 I've fixed that label thing, will be in the next release. Dean 1 Quote Link to comment Share on other sites More sharing options...
Adamw Posted February 3, 2021 Report Share Posted February 3, 2021 @Dean This fix in the latest release that is available on the Link website now. Dean 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.