Does the U7135 support the cmr_dat protocol that the older cmr_dat.exe and I think the Logworks Predator Plugin use?
I am trying to view a list of the PIDs using cmr_dat.exe but not able to get the list. Does the DataViewer application have a way to view the raw PID numbers?
U7135 SRT8 and the Innovative Logworks Predator Plugin
Moderator: mikel
RE: U7135 SRT8 and the Innovative Logworks Predator Plugin
The newer Predators use a new log file format that innovate does not yet support. They have been provided with the new format specs, I suggest you contact them for an update.
johnc <at> diablosport.com
Re: RE: U7135 SRT8 and the Innovative Logworks Predator Plug
FWIW, The problem in question involves only live streaming, not logged data. The problem appears to be that the Predator does not reply in the affirmative to the PID available command (0x66... is responding 00 (or not responding)).johnc wrote:The newer Predators use a new log file format that innovate does not yet support. They have been provided with the new format specs, I suggest you contact them for an update.
The Predator is responding to the Start Live Data command (0x11), or the error message the user is receiving would be different.
We have noted that this behavior is seen when a Predator is powered up but not connected to an ECU (all PIDs report 0x00). However, the user assures us that this is not the case. We have also suggested debugging the unit with CMR_DAT.exe and reporting the results to you (since our communication with the unit is virtually identical).
Also, we have already incorporated the log data format change reported to us.
Best Regards.
RE: Re: RE: U7135 SRT8 and the Innovative Logworks Predator
Looks like we have more work to do. Sending you an email.
johnc <at> diablosport.com
RE: Re: RE: U7135 SRT8 and the Innovative Logworks Predator
Will the U7135 affirmative response to the PID available command make it into the next release? Any ETA?
I tried r18 but no luck.
I tried r18 but no luck.