Any of you that have the LC-1 and have been patiently waiting on the plugin to work with your Predator, can you please post your desire here.... http://www.innovatemotorsports.com/forums/showthread.php?t=7548&page=10 Maybe if they get more people asking about it, they will finally push up the priority on it. thanks
Send it back and buy a Zeitronix, they log RPM right out of the box. I'm not trying to be rude. I have an Innovate that I bought 6 months ago sitting in a box in my living room. I would have loved to have used it, but I need good logging now...
Dahahaha. Reminds me of work in my previous life. I worked on developing what came to be Turner's Roadrunner service. They used Motorola cable modems which didn't have network management. So all the modems sit in little brick buildings in each neighborhood. We go to Akron OH (live test area). In operations there's this room with racks of TVs in it. "What's that?". "We got a camera in each remote building pointed at the modem racks. If you see a red light go on a modem you send somebody out to fix it" ...I guess you had to be there...
I just figured if they saw some posts for more users than me, they might get a clue. Oh well, worth a shot.
Well I would love to have it cause it would make tuning very easy to do I would have to think everyone here would like this to happen
No doubt. Here's my thoughts on this. Integrated OBD and AFR (and some other wideband sensors) logging is sorely needed for tuning. You can sort of do some "ballparking" by checking your AFR independently but you have to have it integrated to do any sort of fine tuning or see exactly what's going on where. Everybody already knows this. The problem is OBD devices connect to the diag port and talk OBD protocol messages over the interface. Wideband controllers output a 0-5v analog signal or some proprietary message protocol over a serial link. The problem is aggregating the two for display monitoring or logging. DashHawk was planning on addressing this with a extra piece of hardware. The HawkEye was going to accept a 0-5v analog input and convert it to "OBD" type messages. This would sit inbetween the scanner and the OBD diag port. Only incremental changes would be required to the scanner since the wideband would look like just another parameter to be polled on the bus. You could monitor everything on the display of the scanner and also utilize the existing logging capabilities. Another approach might be to address logging only. Each device currently does logging. You just need to merge the two. There are couple of ways you could do this. If you could synchronize the clocks in the two devices and utilize time stamps in the log entries then the separate logs could be merged "offline". Without that, you could have each device log to a common device that would merge and log the real time inputs. I'm unclear what Diablo had in mind for a solution. I suspect it may have been to use the live logging feature of both. Both the Predator and Innovate will do live logging to a PC. You still need some way of inputting both feeds to the PC logging client and the logging client needs to understand both. For the logging client to understand both inputs it will need some internals information. Items supported, polling rates, proprietary communication protocol, proprietary message formats, etc. So probably a partnership with some sharing of confidential information. Quite some time ago if you asked Diablo they said they were waiting on Innovate. If you asked Innovate they said they were waiting on Diablo. I don't think the waiting was for work to be done. I think it was for information. I got the impression that the partnership wasn't as open as needed and may have broken down with respect to the project. Pure speculation on my part. PLX has their own OBDII module (no mfg specific parameters) which integrates into their system with their other sensor modules. DashDAQ will accept a generic 0-5v analog signal (you apply a function to map that to whatever values it represents) and also has some drivers that directly accept the "serial" output of a few sensor mfgs. But those are not tuner devices. Surely it would be ideal for a tuner device to have full scanner and sensor integration. ...then there is the marketing priority that would drive an effort like this. The Predator has very limited tuning capabilities. It's primarily a handheld device to apply tunes to a car with some basic tweaking and preference setting capabilities of it's own. You sell to the masses with a plug-n-play unit and you sell a mechanism to apply and log CMR tunes. There is that very low volume area where a few people are going to want to do something inbetween. When you think about it the tool doesn't really have those capabilities. Take AFR for example. The Predator only allows wholesale adjustments to 3 ranges covering the entire RPM band. You could use it to identify events at more specific points but you're not going to be able to address them with the handheld. If it's resources to commit to the project, browse the DS forum. The vast majority don't have a clue. And there are a boatload of hemi truck guys and lx v6 guys screaming for when they're going to be supported. haha, just read a post where some guy says he has an SXT with JBA headers and blastin bob's (1.25"). He says it sounds hollow at idle and he assumes it's the lack of backpressure with the tune. He wants to know what fuel and timing adjustments he should make with his Predator to fix that.
