A lot of work went into solving the issue of getting no response from the ECU in the NefMoto flashing software.
In my experience, many different situations can cause the ECU to not correctly receive or respond to a request. All you can do is try to make the logging software recover when something goes wrong.
Yes, I believe the error recovery must have been really a lot of work.
For the logging, there is not much recovery support during the
setup phase -
if the ecu would not respond correctly to a message, the startup would fail.
But once the logging is running, it can recover from errors which are "recoverable":
the logger sends a log request and expects an answer message from the ecu.
If the ecu sends an incorrect answer or does not answer at all, the logger will
give a short pause time (about 55ms), clear all input buffers and then send
again a request. Only after a certain amount of repeated requests with no further data
received the logger will give up.
I think what Carlossus is facing (and what I faced in my setup initially) is that the ecu just stops
talking "forever", and the only recovery here would be to restart the complete communication.
An automatic reconnect feature could do that, but I prefer seeing a stopped logging session
over a log with a hole in it lasting several seconds.
