jmccorm
Well-Known Member
- Thread starter
- #601
That didn't take long.Getting Close to Write Data by Identifier (WID)
I'm pretty sure we've discussed this before, but I was giving myself a refresher before finally trying to implement it this weekend.
I told ChatGPT the following five things:
- Instead of restricting the data argument to a size of two bytes, allow the argument to be anywhere from 1 to 65535 bytes long.
- Instead of an InputOutputbyIdentifier, modify the script to perform a WriteDatabyIdentifier.
- Using the function that enters an extended diagnostic session as a template, allow a new optional argument of -r to be called to perform an ECU reset.
- If send_ecu_reset should be called, it needs to be called after send_write_data_by_identifier has a successful response.
- Add an optional -y argument, and when it is not specified, the program should exit immediately saying, "You don't seem very sure. Use the -y argument when you're ready." [This is to prevent accidents, given how similar some of these names (rid, wid, ioid) and arguments are.]
From there, I manually adjusted some of the timeout values by hand to make them more liberal. The code is ready to test, but at the very least, I'm going to hold off until tomorrow to test it when I'm fresh.
If anyone has any ideas of a BCM (or other ECU) value somewhere that I can change that doesn't blow anything up, and that results in some change that could be visibly confirmed, I am absolutely open to suggestions here.
It's going to be critical to have a good test.
Right now, I don't have one!
Sponsored
Last edited: