OK,,, if I get the ot-1,,, how do I get that info into my LM-1 to data log,,, I need to log the boost signal from my Greddy 3bar MAP. I really don't want to buy a DL-32.
Depends on if and how you're currently logging with your LM-1. If you're just using it with the built in display and don't have anything else you'll need some type input device in order to log your external 3 bar sensor. The cheapest is the LMA-2/RPM Converter followed by the LMA-3/AuxBox and then DL-32. The LM-1 has analog outputs and can store (log) data internally but you need one of those inputs devices in order to get your data into it.
If you have a laptop computer you can use in the car you would be able to connect the LM-1 and the OT-1 to it and capture/log that information in the LogWorks software. You won't be able to connect any external sensors like your GReddy 3 bar but you would be able to log the stock MAP sensor via the OT-1 (but if you're running a piggyback or any MAP clamp that reading may not be accurate).
Depends on if and how you're currently logging with your LM-1. If you're just using it with the built in display and don't have anything else you'll need some type input device in order to log your external 3 bar sensor. The cheapest is the LMA-2/RPM Converter followed by the LMA-3/AuxBox and then DL-32. The LM-1 has analog outputs and can store (log) data internally but you need one of those inputs devices in order to get your data into it.
If you have a laptop computer you can use in the car you would be able to connect the LM-1 and the OT-1 to it and capture/log that information in the LogWorks software. You won't be able to connect any external sensors like your GReddy 3 bar but you would be able to log the stock MAP sensor via the OT-1 (but if you're running a piggyback or any MAP clamp that reading may not be accurate).
Eric,
So, without having the laptop in during passes,,, I can't log any of the parameters from the OT-1 right? My only option would be the DL-32?
Right now I log passes with my e-o1,, but I want to start using the logworks to save logs.
Oh,, that "My slips" slip is with AJ - Jerrys engine build, still untuned. At 22psi
One more thing,,, since the OT-1 is USB,,, and the LM-1 is serial,,, can log works use both at the same time?
Ok, had some problems. There are some issues with the communication between the OT-1 and the PCM. I originally thought it was my laptop b/c the windows portion (it 's a Mac with windows via bootcamp) had contracted a virus(of course shitty windows) so I had to do a reinstall of Windows XP. I did this and went back out to the car and WAS able to program the OT-1 with LM programmer. There is a list of drop downs with a number of options as far as what sensors to open communication with. You can log up to 15 but obviously the more you log the slower it is. You can also set a channel as "low priority" to speed other more important channels up.
The instructions don't say AnYTHING about expanded/enhanced capabilities so I don't know if it acutally does anything in that respect. And Knock is NOT on the drop down. I selected RPM, MAP, and Iginition Advance for my test. After allot of restarts ect. I was eventually able to log these three in Logworks. I was not able to get it to accept my LC-1 wideband via the serial in port. It never seemed to be able to find that sensor. I think that will eventually work but right now it's a little up in the air until their tech support is open I'm kind of at a roadblock.
So, without having the laptop in during passes,,, I can't log any of the parameters from the OT-1 right? My only option would be the DL-32?
Right now I log passes with my e-o1,, but I want to start using the logworks to save logs.
Oh,, that "My slips" slip is with AJ - Jerrys engine build, still untuned. At 22psi
One more thing,,, since the OT-1 is USB,,, and the LM-1 is serial,,, can log works use both at the same time? It seems to convert the USB to serial, it's supposed to work via the log chain but I was not able to get it to work.
I got it all working. LC-1 and all. According to Innovate tech support it will only support the inputs that show up in the drop down. And knock isn't one of them.. . Unfortunatly.
However, it is extremly convinent, much more so than they way I was doing it with the SSI-4 box. No wiring, no calibrating, everything is just there. And you COULD feasibly tell if the knock sensor is detecting anything by watching the timing advance. Obviously if it suddenly pulls timing it's detecting knock.
One hook up and your datalogging. Plus the ease of switching cars. And you can't beat the price. Hopefully more will get it so we can have a platform we all understand to share with each other.
I think ojcool answered the question on the log chain and the connection interface. It shows that it's supposed to work so hopefully there aren't a lot of issues. I'm still waiting to see if they answer my tech question but it does appear that the list of supported protocols I posted earlier (taken from their user manual) is all that the OT-1 can do for now. I was trying to find out if they planned to add manufacturer support or not and if they could add a way for custom PID's to be queried. I could probably "find out" what the PID for knock is and that would be about the only thing I'd really like besides the other generic parameters it can already do. Not like I can't pull out the scan tool on the rare occasions I'd need to check on something else.
I was wondering about the laptop connection,,, (usb for the OT-1 and serial for the LM-1) I have one coming,,, just wondering if I will be happy with it. Hmmmmm,, also,,, if you need two OBD ports, try this OBD2Cables.com
It might be interesting to try but I suspect you'd have issues with the splitter cable. The scan tool/gauge/OT-1 sends a request for information and if multiple devices are asking for data then you can't control who is receiving the information and it may confuse them. If the OT-1 was only querying generic OBD-II data via the J1850 bus of the OBD-II connector and you had a higher end scan tool or gauge that was riding only the Chrysler proprietary SCI bus it might work but most of my scan tools establish connection in generic mode first (J1850) before going to the SCI bus. If you have an Aeroforce it might be interesting to contact them and see if they've tested their gauge in such a fashion.
If you get a chance to try it out I'm curious what the logging/sampling rate is going to be. The PCI/J1850 bus that the generic OBD-II information is provided on seems a little slow on some of my scan tools but the faster, SCI bus that the enhanced OBD-II data is provided on isn't too bad. I still haven't heard back from their customer service but after reading the manual I'm pretty certain it will only provide the generic emissions-related data for now which will still be nice but not as useful as full enhanced data support. Hopefully that's something they're looking at adding in the future.
It looks like the J1850-VPW is only 10.4kb/s , the same as ISO 9141 , so i'd might expect the sample rate to be similiar to Innovate's example on pages 13-14.
I'm concerned that the ignition timing will be as inaccurate as the ipw is from the OBD port.
i guess i'll find out, mine arrived Tuesday.
__________________
Quote: Originally Posted by Bell Intercoolers
Regardless of the [Thermal] efficiency, if too much pressure is lost, then the intercooler is either useless or can actually decrease performance...Corky Bell
I was wondering about the laptop connection,,, (usb for the OT-1 and serial for the LM-1) I have one coming,,, just wondering if I will be happy with it. Hmmmmm,, also,,, if you need two OBD ports, try this OBD2Cables.com
Tom
No no, you won't have any problems there. As you stated the OT1 has a USB cable and as long as everything else is connected through the Serial log chain upstream of the OT1 everything will end up logging through the USB on the OT1. So just to clairfiy, You simply hook up the LC-1 or LM-1 to the serial in of the OT1 box and then hook up the USB from the OT1 to the laptop and everything works great.
NOTE: be sure to connect any serial devices you plan on using to the OT1 BEFORE you hook it up to the OBDII port on the vehicle. ie the OT1 needs to be OFF when you hook up serial devices or it wont recognize them.
NOTE: always remember to move the different gauges in logworks around if your missing an input. Often the LC1 or LM1 gauge is hiding behind one of the other ones when you first start up.
NOTE: after you program the OT1 with LM programmer and after you have all your serial devices connected to the OT1 THEN hook it up to the OBDII port with the vehicle ignition OFF. The only LED to be lit will be the Power LED. Then hook up the USB cable to the laptop. THEN turn the ignition ON. The LED to light will be the power, vehicle, and USB will be flashing all weird. Give the OT1 about 20-30 second to interrogate the PCM... THEN start the car. With the car running then you open LogWorks and push the "connect" button, sometime you have to push it twice. Everything should open up and be hunky dory. If you do something out of sequence sometimes you will get the following error. "no serial device found" or "no realtime data detected". Just start over.
just got my OT-1 today... They were out of stock for 2 weeks argh!!! My LC-1 is out of calibration so they say.. it was showing 15.2 afr hahah.. I did the calibration properly the 1st time.. So I need to redo it.. It looks cool.. I will try to update in the next few days on the status of the tune.
AutoForums.com is the premier network of enthusiast-owned
enthusiast-operated automotive communities.
We operate more than 100 automotive forums where our users consult peers for shopping information and advice, and share
experiences and opinions as a community.
Linear Mode
