|
Title: setting a bit to 0 or 1 Post by: littco on November 12, 2012, 03:27:47 AM looking at CWMDAPP and CWDMFAB and in the FR and translated texts it states you must set bit 0 to 1 or in the case of CWDMFAB set bit 0 to 0. Could some just confirm how this would be done as looking at winols and tunerpro ..Just looking at CWDMFAB its showing in Winols as a 255 value which is FF ( obviously) . is it just a case of changing say Bit 0 to 01.
the reason I ask is that whilst trying to disable TQM i set the relevant maps and as soon as I change CWMDAPP to 1 it send the idle haywire.. Now I was doing this in tuner pro and changine the variable value from 0 to 1 but wanted to check if this was correct. Title: Re: setting a bit to 0 or 1 Post by: rajivc666 on November 12, 2012, 04:29:35 AM Bit 0 is the right most bit so 255 is 0x1111 1111b, so to set bit zero to 0 it will be 0x1111 1110b or 0xfeh or 254 decimal.
Title: Re: setting a bit to 0 or 1 Post by: littco on November 12, 2012, 05:01:39 AM Thanks for the reply, with regards cwmdapp that's in winols is it just a case of switching the 0 to 1 then that's shows up in the map?
Title: Re: setting a bit to 0 or 1 Post by: littco on November 12, 2012, 05:18:57 AM Answered my own question now, thankyou anyway.
Just need to find out why setting cwmdapp to 1 sends idle erratic! Title: Re: setting a bit to 0 or 1 Post by: masterj on November 12, 2012, 05:38:13 AM Answered my own question now, thankyou anyway. Just need to find out why setting cwmdapp to 1 sends idle erratic! if you disable torque management, then you WILL have bad idle, because IIRC KFPED is then your main load target multiplied by some multiplier (another map, can't remember now). So you would have to edit KFPED so low load would be same as actual engine load for idle (~20-30%) Title: Re: setting a bit to 0 or 1 Post by: littco on November 12, 2012, 06:01:05 AM Thankyou, makes sense! I will take a look at that this afternoon
Title: Re: setting a bit to 0 or 1 Post by: Rick on November 13, 2012, 01:36:21 AM Yes, disabling torque monitoring will make it run horribly.
Title: Re: setting a bit to 0 or 1 Post by: littco on November 13, 2012, 06:36:47 AM Cheers Rick
I adjusted Kfped and it's idling fine now and running pretty smoothly. Plus timing swings have gone from 15 degrees to 3 degrees... Title: Re: setting a bit to 0 or 1 Post by: phila_dot on November 13, 2012, 08:42:33 AM You shouldn't keep torque management disabled.
Your timing swings because you screwed something up. If you tune the car properly there is no intervention. And I don't mean by FF'ing a bunch of tables either. Title: Re: setting a bit to 0 or 1 Post by: littco on November 13, 2012, 09:09:17 AM I understand, but are you saying that with perfect mapping you can get better results with Tm enabled than with it off? Because I'm not sure I agree with that. Surely a more predictable and smoother ignition curve is better a zigzag affair than the me7 seems to like when TM is active. I maybe wrong
Title: Re: setting a bit to 0 or 1 Post by: phila_dot on November 13, 2012, 11:10:58 AM I understand, but are you saying that with perfect mapping you can get better results with Tm enabled than with it off? Because I'm not sure I agree with that. Surely a more predictable and smoother ignition curve is better a zigzag affair than the me7 seems to like when TM is active. I maybe wrong Yes, there are times when intervention is necessary. If the car is tuned properly, then MD will not interfere with acceleration and there will be no timing swings. Title: Re: setting a bit to 0 or 1 Post by: prj on November 13, 2012, 11:16:44 AM If the car is tuned properly, then MD will not interfere with acceleration and there will be no timing swings. Could not agree more... |