VERSION 1.2.54
WINXP
Nistune won't change the K multiplier, have not tried anything else.
Logging, reading, uploading works.
Can we please have a big fat error message/requester/alert for critical errors?
(Or flash the screen red)
The tiny text in the left lower quadrant is not easy to spot.
Attempted write failed?
Moderator: Matt
Attempted write failed?
- Attachments
-
- nistune-0216-1528.log
- (2.54 MiB) Downloaded 119 times
Re: Attempted write failed?
The error is a bug, the status is a warning for recording to the log
It should not happen. The log shows
"Attempted write failed (ECU valid range) at 97E52609"
I did see this here once with that build but have not been able to repeat it since. The address is not valid and should be between 0000-FFFF (16 bit number). I tried to repeat with your board 41P03 Z32 with 1.2.56
Please try this version and let me know if you still see the issue
It should not happen. The log shows
"Attempted write failed (ECU valid range) at 97E52609"
I did see this here once with that build but have not been able to repeat it since. The address is not valid and should be between 0000-FFFF (16 bit number). I tried to repeat with your board 41P03 Z32 with 1.2.56
Please try this version and let me know if you still see the issue
Re: Attempted write failed?
Thanks Matt,
Interesting that the address range is out range.
Is it possible to have a requester pop up for any kind of critical error?
I was really wondering when I altered K and the engine was just not reacting as it should.
(Because I initially did not spot that message)
Will check the newer build.
Interesting that the address range is out range.
Is it possible to have a requester pop up for any kind of critical error?
I was really wondering when I altered K and the engine was just not reacting as it should.
(Because I initially did not spot that message)
Will check the newer build.
Re: Attempted write failed?
When it is an error (bug) it is unexpected, so there is not a pop up as such for this particular problem. Let me know how the newer version goes. I suspect is is a build error rather than code bug (since cannot be reproduced in later versions)