RomRaider

Hello,

I'm trying to get a Tactrix 2.0 Openport to log on my 2009 OBXT. The ECU ID is: 5212525107 and the Cal ID is: A2TBOO1C. I can log with Romraider, but it would be sweet to be able to log when I want without the laptop.

The orange and green lights are flashing when plugged into the OBDII port, but the red and blue light don't come on. I've tried adding triggers, disabling triggers, and nothing seems to work.  The SD card is formatted as 32FAT.

Below is the code I have saved in the logcfg.txt file. I would appreciate any ideas here. 

type = ssmcan

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

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

paramname = Vehicle_Speed
paramid = 0x000010
databits = 8
scalingrpn = x,0.621371192,*

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

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

paramname = SI-Drive_Mode
paramid = 0x00016A
databits = 8
scalingrpn = x

paramname = CL/OL_Fueling*
paramid = 0xFFA44D
databits = 8
scalingrpn = x,6,+

paramname = Target_Boost_(4-byte)*
paramid = 0xFF63EC
databits = 32
scalingrpn = x,760,-,0.01933677,*

paramname = Target_Throttle_Plate_Position*
paramid = 0xFF8308
databits = 32
scalingrpn = x,.84,/

paramname = Gear_(Calculated)*
paramid = 0xFF701D
databits = 8
scalingrpn = x

paramname = Engine_Load_(2-byte)**
paramid = 0xFF7044
databits = 16
scalingrpn = x,.00006103516,*

paramname = Target_Boost_(2-byte)**
paramid = 0xFF7056
databits = 16
scalingrpn = x,760,-,0.01933677,*

paramname = A/F_Sensor_#1_(4-byte)*
paramid = 0xFF6D78
databits = 32
scalingrpn = x,14.7,*

paramname = Manifold_Relative_Pressure_(4-byte)*
paramid = 0xFF6A78
databits = 32
scalingrpn = x,0.01933677,*

paramname = Knock_Sum*
paramid = 0xFF7FEC
databits = 8
scalingrpn = x

;-------------triggers---------------
;paramname = defogger_sw
paramid = 0x64
databits = 1
offsetbits = 5
isvisible = 0

;conditionrpn = defogger_sw,1,==
action = start

;conditionrpn = defogger_sw,0,==
action = stop

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

;cruise set signal
paramname = cruise_set_coast
paramid = 0x000121
databits = 1
offsetbits = 5
isvisible = 0

;cruise cancel signal
paramname = cruise_cancel
paramid = 0x0000D7
databits = 1
offsetbits = 0
isvisible = 0

;start action,
conditionrpn = cruise_set_coast,1,==
action = start

;stop action
conditionrpn = cruise_cancel,1,==,Engine_Speed(rpm),100,<,||
action = stop

conditionrpn = Engine_Speed,0,>
action = start

conditionrpn = Engine_Speed,0,==
action = stop

Do you have the Extended Ram Parameter patch applied in EcuFlash?

I never did apply a patch. I can log the extended parameters with the Romraider logger without a problem though.

I attached a file that I converted to a text file. Originally it was the logcfg.out file that the ECU seems to generate. I converted it to .txt so I could view it and hopefully interpret it, but I don't know enough about it to tell if anything is wrong.

Thanks for looking.

Are you using CAN mode in RR?
If you log via CAN "type = ssmcan" then you need to apply the patch.
The other option is to use ssmk which is the default for RR.

And for float values you don't use databits = 32 you use isfloat = 1
Follow the examples in the C:\Program Files (x86)\OpenECU\EcuFlash\samples\logging\
directory.

OK. Good info!

Where can I find the patch to flash?

Thanks for the help.

In looking at my logcfg.txt file (generated by the online configuration tool) vs the ECUFlash samples, mine seems to have paramid addresses like 0x000010 vs 0x10 in the sample file. I wonder if the configuration tool is giving me the wrong code.

Leading zeros are ignored so that's not an issue.
The patch, if compatible is in the table list, last item in EcuFlash.

Alright, so the patch does not appear in the list of items in ECUFlash. However, with RomRaider I can log the extended parameters, so my ECU is supported. When trying to log with the Standalone Tactrix onto an SD card, it will not allow me to log extended parameters.

I might just say screw it and only log with the laptop and RomRaider since that works.

Switch to kline logging then.

You might also want to focus on only one start/stop action and remove or comment out the rest to make sure they are not fighting. Check the examples.