Copyninja Posted June 16 Report Share Posted June 16 Hi, I setup flat shift and it worked in line with the g4x gear shift logic in line with the below. 3700rpm shifting up at 4500rpm at WOT, clutch shift detected and ign cut came in as expected. However, when i tried at 6700rpm to do the same it failed terribly and the rpm limit saved the day. Phew! Log file attached. Upshift switch activated but ign cut did not. Doesnt make sense why it wont activate at higher rpm? Log file attached. Quote Link to comment Share on other sites More sharing options...
Vaughan Posted June 16 Report Share Posted June 16 Looks like it went straight to reactivation timeout so need a copy of your tune to see how you have it setup. Copyninja 1 Quote Link to comment Share on other sites More sharing options...
Copyninja Posted June 16 Author Report Share Posted June 16 hey vaughan, see attached. Yes not sure why its going to reactivation mode. It was working fine minutes before. Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 16 Report Share Posted June 16 I would say the only way that could happen would be if there was a "bounce" on the clutch pedal. Increase the start shift validation to about 20ms should be enough to mask most bounce and I would also log the DI and gear shift status at say 500Hz for the next test to get a better picture of what is going on. Also, unrelated to your current problem but something I want to mention in case it does affect you in the future - it has been recently discovered there is a bit of an oversight in our "digital input" end shift mode: There is currently no "maximum shift duration" function, so be aware if you do push in the clutch at high RPM/TP, then the cut will stay active the whole time the clutch is depressed. I suspect this is probably not usually going to happen during normal driving/racing, but one user did find on the dyno because he pushed in the clutch at the end of a ramp run and kept it in for some time, the gear cut would stay active and stall the engine. This is on the fix-it list, and there is a relatively simple workaround if needed in the meantime. Copyninja 1 Quote Link to comment Share on other sites More sharing options...
Copyninja Posted June 16 Author Report Share Posted June 16 Thanks so much Adam. I will try the start shift validation to 20ms instead of the current 4ms. Will also reduce the Rpm limit to 7krpm when i test it again as dont want rpm to flare to 9krpm as it did on this run. Quite scary, thank goodness for the rpm limit which saved the day. hoping the 20ms validation time resolves the bounce. Is this the actual physical clutch switch having a bounce issue? The workaround would be great thanks just to know when i get out there and test again. I highly doubt it will remain depressed for more then 200-300ms. 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.