Page 1 of 1

Openport 2.0E read OK, no datalog

PostPosted: Tue Nov 24, 2009 12:49 am
by pavlik1
Hello,

May be someone can help.

with my old vagcom I can log the data using RomRaider logger and Ecuexplorer, Learning view also work. I cannot read the rom (normal)

with Openport 2.0E I can reed the rom, but NOT able to log with RomRaider logger and Ecuexplorer, Learning view also DO NOT work????

I also got his message: "ecu id of faeb802bc1 not found"

All old drivers was removed, installed ecuflash_1422595_win.exe, so far only EcuFlash work.

LearningView_LOG.txt
[21:55:56.2342480] PassThruOpen returned 0 and DeviceID 5
[21:55:56.2342480] PassThruReadVersion returned 0
[21:55:56.2342480] Device firmware version: 1.10.2658
[21:55:56.2342480] DLL version: 0.50.2598 Jun 26 2009 15:02:29
[21:55:56.2342480] API version: 04.04
[21:55:56.2342480] PassThruConnect returned 0 and ChannelID 7
[21:55:56.2442624] PassThruStartMsgFilter returned 0
[21:55:56.2442624] ECU Init
[21:55:56.2743056] PassThruWriteMsgs returned 0
[21:55:56.2743056] WRITE 6 bytes: 80 10 F0 01 BF 40
[21:55:56.3444064] PassThruReadMsgs returned 0
[21:55:56.3544208] READ 0 bytes
[21:55:56.4445504] PassThruReadMsgs returned 0
[21:55:56.4445504] READ 62 bytes: 80 F0 10 39 FF A2 10 0F 1B 44 58 05 05 73 FA EB 80 2B C1 02 AA 00 10 00 60 CE 54 F8 B0 60 00 00 E0 00 00 00 00 00 DC 00 00 55 10 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 67
[21:55:57.6162352] ECU ID of FAEB802BC1 not found in definitions
[21:55:57.6262496] PassThruDisconnect returned 0
[21:55:57.6362640] PassThruClose returned 0

ecuexplorer log.txt
21:54:28.047 - list column added - Historic Trouble Code Description
21:54:28.057 - resource tree item added - trouble code reader...
21:54:28.728 - resource tree build complete...
21:54:28.808 - serial view build complete...
21:54:28.808 - using comm port 5 [\\.\COM5]
21:54:28.808 - Comms Error - Start [CreateFile] : 2 [0x2]
21:54:30.410 - comms modules started...
21:54:42.307 - Comms Error - Stop [EscapeCommFunction(CLRDTR)] : 6 [0x6]
21:54:42.307 - comms modules stopped...
21:54:42.317 - label data memory released...
21:54:42.317 - data item memory released...
21:54:42.317 - dtc item memory released...

Also the logging to the microsd does not work. I have the file LogCfg.txt in the root folder of the card, but when pressing the defog no log file is generated

type=ssmk

paramname = Engine_Load_(Relative)(%)
paramid = 0x000007
databits = 8
scalingrpn = x,100,*,255,/

paramname = A/F_Correction_#1(%)
paramid = 0x000009
databits = 8
scalingrpn = x,128,-,100,*,128,/

paramname = Manifold_Absolute_Pressure(bar)
paramid = 0x00000D
databits = 8
scalingrpn = x,37,*,255,/,14.50377,/

paramname = Engine_Speed(rpm)
paramid = 0x00000E
databits = 16
scalingrpn = x,4,/

paramname = Throttle_Opening_Angle(%)
paramid = 0x000015
databits = 8
scalingrpn = x,100,*,255,/

paramname = Front_O2_Sensor_#1(V)
paramid = 0x000016
databits = 16
scalingrpn = x,200,/

paramname = Rear_O2_Sensor(V)
paramid = 0x000018
databits = 16
scalingrpn = x,200,/

paramname = Front_O2_Sensor_#2(V)
paramid = 0x00001A
databits = 16
scalingrpn = x,200,/

paramname = Knock_Correction_Advance(degrees)
paramid = 0x000022
databits = 8
scalingrpn = x,128,-,2,/

paramname = Manifold_Relative_Pressure(bar)
paramid = 0x000024
databits = 8
scalingrpn = x,128,-,37,*,255,/,14.50377,/

paramname = Primary_Wastegate_Duty_Cycle(%)
paramid = 0x000030
databits = 8
scalingrpn = x,100,*,255,/

paramname = Gear_Position(gear)
paramid = 0x00004A
databits = 8
scalingrpn = x,1,+

paramname = Exhaust_Gas_Temperature(C)
paramid = 0x000106
databits = 8
scalingrpn = x,40,+,5,*

paramname = Boost_Error*(bar)
paramid = 0x20DFE
databits = 16
scalingrpn = x,32768,-,.001333224,*

paramname = Target_Boost*(bar_relative_sea_level)
paramid = 0x20E02
databits = 16
scalingrpn = x,760,-,0.001333224,*

paramname = defogger_sw
paramid = 0x64
databits = 1
offsetbits = 5
isvisible = 0

conditionrpn = defogger_sw,1,==
action = start

conditionrpn = defogger_sw,0,==
action = stop

Re: Openport 2.0E read OK, no datalog

PostPosted: Sun Nov 29, 2009 3:10 pm
by mohammadov
Whats ur car model?
heres what RomRaider logger works with:
http://www.romraider.com/Documentation/SupportedECUs

Re: Openport 2.0E read OK, no datalog

PostPosted: Mon Nov 30, 2009 3:46 am
by pavlik1
hi,

The logging work perfect with my old VAGcom cable, the ecu is A4SE900D - suported, so small summary:

with VAGcom - Romrider logger - OK, LearningView - OK, read/write ecu - NO cost me less than 10 USD
with openport2.0 - Romrider logger - NO, LearningView - NO, read/write ecu - OK, microSD logging - NO cost me over 250 USD

can you send me working LogCfg.txt

Thanks

Re: Openport 2.0E read OK, no datalog

PostPosted: Mon Nov 30, 2009 6:05 am
by merchgod
as far as learning view is concerned, you are using an old version that will not work with the newer op 2.0 firmware update. Download the latest version of learning view. This was also the case with RomRaider, you need to download and install the newest version of RomRaider.

Re: Openport 2.0E read OK, no datalog

PostPosted: Fri Dec 04, 2009 1:10 pm
by pavlik1
after some test , I got all the time the same error:

01: type=ssmk
: name[type,8] value[ssmk,0,0.000000]
02: paramname = Engine_Load_(Rel)(%)
: name[paramname,16] value[Engine_Load_(Rel)(%),0,0.000000]
03: paramid = 0x000007
: name[paramid,17] value[0x000007,7,0.000000]
04: databits = 8
: name[databits,22] value[8,8,8.000000]
05: scalingrpn = x,100,*,255,/
: name[scalingrpn,0] value[x,100,*,255,/,0,0.000000]
unrecognized option [scalingrpn] at line 5

the other idea is to have parameter names with increasing number of characters, so if length problem occurs, it will be clear what is the critical length.
like
paramname = 1234567891234567891
paramid = 0x00000E
databits = 16
scalingrpn = x,4,/

paramname = 12345678912345678912
paramid = 0x000010
databits = 8
scalingrpn = x

paramname = 123456789123456789123
paramid = 0x000011
databits = 8
scalingrpn = x,128,-,2,/

Please help to resolve :unrecognized option [scalingrpn] at line 5