The Launch Crecorder is a plug-and-play OBD-II tool that records up to 24 hours of engine data for analysis, effectively diagnosing intermittent issues during real-world driving. While users praise the software's user-friendly interface for generating reports, some reviews note limitations in the sampling rate and rigid, non-adjustable plot scales. For more technical details on the device, see the OBDII Data Recorder Instructions www.oemys-performance.com OBDII Data Recorder Instructions
Www.crecorder.com Software Online
The Launch Crecorder is a plug-and-play OBD-II tool that records up to 24 hours of engine data for analysis, effectively diagnosing intermittent issues during real-world driving. While users praise the software's user-friendly interface for generating reports, some reviews note limitations in the sampling rate and rigid, non-adjustable plot scales. For more technical details on the device, see the OBDII Data Recorder Instructions www.oemys-performance.com OBDII Data Recorder Instructions
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.