Logging with the (Beta) Standalone Tactrix Cable Logger (No More Computer!)
Hi Guys,
Been in contact with Colby re issue with support for previous version of serial protocol and integration to support the LM-1 on the standalone logging. Very grateful for his help and assistance but at present we're a little stuck.
What he requires is an LM-1 unit to do some testing and even though I'd be happy to send him mine, it could be expensive with carriage costs and re-import charges.
If anyone in the USA has a LM-1 unit and would be willing to pass to Colby to try and get this issue sorted, I'd be very thankful, and willing to cover your carriage costs for sending to him, think its Seattle he's based.
Hoping someone can help
Been in contact with Colby re issue with support for previous version of serial protocol and integration to support the LM-1 on the standalone logging. Very grateful for his help and assistance but at present we're a little stuck.
What he requires is an LM-1 unit to do some testing and even though I'd be happy to send him mine, it could be expensive with carriage costs and re-import charges.
If anyone in the USA has a LM-1 unit and would be willing to pass to Colby to try and get this issue sorted, I'd be very thankful, and willing to cover your carriage costs for sending to him, think its Seattle he's based.
Hoping someone can help
Has anybody seen if live logging through evoscan is possible if the LC1 or any wideband for that matter is connected to the OP2.0 instead of the computer?
There is the Rear O2 route, but I don't wanna take it unless absolutely necessary.
There is the Rear O2 route, but I don't wanna take it unless absolutely necessary.
The OP2 will not log while it is plugged into to you computer via USB. It will only log when plugged into your car and the proper trigger conditions have been met.
This is the only thing holding me back from upgrading right now.
Also, semi OT:
Does the beta include definitions for cranking enrichment? If so can someone PM/post them for me?
Thanks!
Thread Starter
Evolved Member
iTrader: (4)
Joined: Feb 2008
Posts: 610
Likes: 0
From: Edmonton, Alberta
^ No, what it means is that if you're using EvoScan or anything else that requires the cable to be connected to the computer, the computer has priority. The OP2 standalone logger will not be active until you disconnect the cable. You can use EvoScan and such as you wish.
^ No, what it means is that if you're using EvoScan or anything else that requires the cable to be connected to the computer, the computer has priority. The OP2 standalone logger will not be active until you disconnect the cable. You can use EvoScan and such as you wish.
I'm not pushing or trolling by saying this, I swear... but does anyone know what is taking so long? Its been ~9 months since the original beta for this was released!
So I loaded up the new ecuflash and firmware last night. Logging to SD is working well, but now Evoscan won't find the OP2.0 cable. I'm on 2.7b5. Do I need 2.7b0046?
I had this problem with the latest beta. You need to pop out the SD card, and unplug the Openport 2.0 from both the USB cable and the odb2 port, then plug it back in w/o the SD card. I'm just getting my feet wet so I wasn't sure if this was normal or not, haven't stopped back in here yet.
I had this problem with the latest beta. You need to pop out the SD card, and unplug the Openport 2.0 from both the USB cable and the odb2 port, then plug it back in w/o the SD card. I'm just getting my feet wet so I wasn't sure if this was normal or not, haven't stopped back in here yet.
I'll try a full disconnect and see what happens.
Thanks!
Thread Starter
Evolved Member
iTrader: (4)
Joined: Feb 2008
Posts: 610
Likes: 0
From: Edmonton, Alberta
Nope. The new beta uses a different OP driver. EvoScan had a copy of the old one. Delete the op2 something .dll from the evoscan folder and it will smarten up. The new betas of evoscan wok out of the box.
Does anyone know the symbol for divide in the scaling? I don't see anything using it yet and didn't want to throw a slash at it since that may be a special character.
Does anyone know how to set multiple conditions? I'd like this to say log only with cruise switch and engine on, but stop if cruise off or RPM less than 2500:
Code:
conditionrpn = CruiseLight,1,==,&&,RPM,2500,> action = start conditionrpn = CruiseLight,0,==,||,RPM,2500,< action = stop ; only log when the engine is running ;conditionrpn = RPM,0,> ;action = start ; ;conditionrpn = RPM,0,== ;action = stop ; start logging to a new file when the throttle goes from previously below 95 to above 95 ; #throttle refers to the previous throttle sample conditionrpn = TPS,80,>,#TPS,80,<=,&& action = newfile
Code:
conditionrpn = CruiseLight,1,==,RPM,2500,>,&& action = start conditionrpn = CruiseLight,0,==,RPM,2500,<,|| action = stop
I've been using '/' just fine. Hamish codes in C++ (or so it seems), so all C++ style operators work for me. If you are doing the conditional logging, '==' is the equal comparitor, '<' less than, '<=' less than or equal to, '>' greater than, '>=' greater than or equal to, '&&' logical and, '||' logical or... and so on.
Code:
--- storage info --- log channels: 2 log parameters: 9 log stringlist: 124 chars log floatlist: 12 floats 9 mrmacan requests per cycle (worst case), taking 100000us per cycle (95000us is fastest possible) logging interval will be 100000us
I haven't been able to get the rear02 logging to work for a long time. 0x80934e is the address I'm using, but I notice the OP is in Canada... is there a different one for USDM? I found tephra saying 0x80834e one time but it failed testing. 0x80934e shows 0-3, but usually just 0 for me. Not sure if this is because of 5268022 or what.
EDIT: Nevermind, I was using 1 byte and a 1 byte formula. The equation for AEM UEGO 0-5v on 2 byte is 1.9987 * ( x / 204.6 )) + 10
EDIT: Nevermind, I was using 1 byte and a 1 byte formula. The equation for AEM UEGO 0-5v on 2 byte is 1.9987 * ( x / 204.6 )) + 10
Last edited by fostytou; Aug 9, 2010 at 10:59 PM.





