Openport Stand-Alone Logging Beta

[cboles]

SSM RAM parameters do not work via CAN because the ECU does not support them. I have a ROM patch for this - I am integrating it into EcuFlash now.

Ok here is my update.

The 4byte stuff does not work. Its won't even create a log file if a 4-Byte parameter is called out.

[cboles]

Yes - the current log timer is 32-bit, and in microseconds. I will need to check the logic to see why it cut your file though - it shouldn't do that as all of the time comparisons in the code should be rollover protected, and the OP2 generally doesn't care about that timer anyway. At present, the timer starts at 0 when the OP2 boots up (has power applied). I can easily make each file start at 0, but I find it somewhat useful to know how much time has elapsed between logs, for example.

Colby - I think I found a bug.

time cannot go higher than MAXINT - ie 4290 ish seconds.

Fix that and that should hopefully fix LONG trip recordings

In fact I am not even sure how "time" is meant to work, this morning (after leaving the car OFF for 16 hour) my time started at 2000ish seconds.

The ignition was off, but the car was NOT locked (I had the keys in the car) maybe the car detected the keys (Evo FastKey here) and kept the car awake?!?!?

[Tephra]

hrmm well something funny is going on.

maybe its an EvoX thing but sometimes I get into the car and the timer will start at 2700seconds... or whatever...

maybe the power is only cut when you turn on the immobiliser...(ie lock the car)

eitherway the rollover thing needs a quick dbl check...

[mdedwar]

Hi Colby,

Are you able to check that the LC-1 code still works under the latest beta? my LC-1 logs fine in RR but has stopped logging correctly in sd logging. It did work in a previous version.

Cheers,
Matt.

[cboles]

If you have the OP2 plugged into your OBD port, it is on. The OBD port is unswitched on pin 16 (VBAT) - that is how the standard works.

hrmm well something funny is going on.

maybe its an EvoX thing but sometimes I get into the car and the timer will start at 2700seconds... or whatever...

maybe the power is only cut when you turn on the immobiliser...(ie lock the car)

eitherway the rollover thing needs a quick dbl check...

[Tephra]

Hi Colby,

FYI - I permanently leave the OP20 plugged in.

I will do a test tonight - I have a funny suspicion I would like to confirm.

This will probably be a moot point once you use (milliseconds / 1000) and store than in the "time" uint.

Not sure if you need any more resolution that 1/1000 of a second

Cheers
D.

[ladams00]

Has anyone seen this error at the end of your logcfg.out? I'm using the sample subaru k-line adc with lc-1 logcfg.txt:

Code: Select all

141: ;-------------calculated parameter---------------
142: ;
143: ; you can derive calculated parameters from other parameters
144: ; using RPN expressions
145: ;
146: type = calc            
  : name[type,8] value[calc,0,0.000000]
max channels exceeded at line 146

The last line, I suppose, is where it gives up.

This is with latest firmware and latest sample file (just renamed to logcfg.txt).

--edit--
I noticed in the sample config file there are 24 total parameters and 4 types. I wonder which is limited...either type at 3, or paramname at 23...or there were instructions in the sample file I missed.

[altaic]

I hear you on the OSX library. My dev Mac kicked the bucket a couple of weeks back and I need to fix the power supply to get back to that machine. I should be set up for a pretty quick port of op20pt32.dll though. The only big issue on OSX at the moment is that there is some goofiness with USB composite devices that have communication device class (CDC) devices as one of the devices. This means that you can't have the SD card plugged in and have the OP2 work on a Mac right now. I have someone at Apple that has already made a fix to their CDC driver, but it never seems to make it into any of their releases.

...and yes, you can operate all physical buses on the OP2 simultaneously. You can even tee CAN and ISO15765 data and analyze it via both protocols as well.

That's great that it can handle both busses at once. I'd hate to have to go to the dealer twice to have them do the TPMS.

Seems like there are a fair number of bugs like the one you mentioned that go under the radar at Apple. At least it's not really a show stopper for the OP2, though, considering the SD logging functionality is just beta right now and most users haven't even tried it.

I hear you about dev machines kicking the bucket... My laptop bit it this week and I had to replace it (it was ~4 years old). If you'd like I can test the mac op20pt32 port for you. I develop a lot for the mac, and I'm happy to offer any assistance towards getting it ported.

Hey Colby, have you tested to see if that composite USB device bug has been fixed in Snow Leopard? I've recently been working with USB webcams for a computer vision project, and I've noticed some changes since OS X 10.5. The higher-level QTKit API... leaves something to be desired... so I have had to resort to low level access. It's actually worked out pretty well-- once I discovered USB Prober.app, anyway.

[cboles]

At present, the number of "channels" is limited to 3, and the calculated parameters and adc channels also count towards these. In the next version they should not, and then this problem would go away. Just get rid of the adc channel for now and you should be OK.

Has anyone seen this error at the end of your logcfg.out? I'm using the sample subaru k-line adc with lc-1 logcfg.txt:

Code: Select all

141: ;-------------calculated parameter---------------
142: ;
143: ; you can derive calculated parameters from other parameters
144: ; using RPN expressions
145: ;
146: type = calc            
  : name[type,8] value[calc,0,0.000000]
max channels exceeded at line 146

The last line, I suppose, is where it gives up.

This is with latest firmware and latest sample file (just renamed to logcfg.txt).

--edit--
I noticed in the sample config file there are 24 total parameters and 4 types. I wonder which is limited...either type at 3, or paramname at 23...or there were instructions in the sample file I missed.

[cboles]

I haven't checked, but IIRC I asked the developer I am in contact with at Apple and he had said no.

Hey Colby, have you tested to see if that composite USB device bug has been fixed in Snow Leopard? I've recently been working with USB webcams for a computer vision project, and I've noticed some changes since OS X 10.5. The higher-level QTKit API... leaves something to be desired... so I have had to resort to low level access. It's actually worked out pretty well-- once I discovered USB Prober.app, anyway.

[cboles]

If you can plug in a OP2 with a SD inserted and the drive shows up, then yes, it has been fixed...

I haven't checked, but IIRC I asked the developer I am in contact with at Apple and he had said no.

Hey Colby, have you tested to see if that composite USB device bug has been fixed in Snow Leopard? I've recently been working with USB webcams for a computer vision project, and I've noticed some changes since OS X 10.5. The higher-level QTKit API... leaves something to be desired... so I have had to resort to low level access. It's actually worked out pretty well-- once I discovered USB Prober.app, anyway.

[altaic]

If you can plug in a OP2 with a SD inserted and the drive shows up, then yes, it has been fixed...

I just tried it on 10.6.1-- it worked!

[cboles]

If you can plug in a OP2 with a SD inserted and the drive shows up, then yes, it has been fixed...

I just tried it on 10.6.1-- it worked!

Is the serial port there as well? If you open it an send "ati\r\n" (where \r and \n are CR LF) do you get anything back?

[ladams00]

I have this same problem now. Upon plugging in the OP2 into the ODB port with car on or off...I see the blue/green light up momentarily, then switch to red for a couple seconds, then 3 color cycling pattern.

No logcfg.out is generated.

I tried formatting the sd card again (FAT16), same deal. Using the sample k-line subaru with lc-1 (and have commented out the ADC stanza because of the type limit).

--edit--
n00b shit false alarm
/me sighs

logcfg.txt.txt double extension garbage was my fault. I just switched to Windows 7 and haven't change the folder options to display known extension types.

Works better now

Awesome, thanks. I did not realize that.

Now my Tactrix won't respond when plugging it in. The leds just slowly fade in and out of colors rather than the green and red lights flashing. Not sure why. Car is running and its plugged in to the OBD port, and not plugged into USB.

[cboles]

I'm not sure what is going on there, but it seems like the OP2 is having trouble reading or writing the SD card. If you plug the OP2 into the PC with the card inserted, can you access it OK?

I have this same problem now. Upon plugging in the OP2 into the ODB port with car on or off...I see the blue/green light up momentarily, then switch to red for a couple seconds, then 3 color cycling pattern.

No logcfg.out is generated.

I tried formatting the sd card again (FAT16), same deal. Using the sample k-line subaru with lc-1 (and have commented out the ADC stanza because of the type limit).

--edit--
n00b shit false alarm
/me sighs

logcfg.txt.txt double extension garbage was my fault. I just switched to Windows 7 and haven't change the folder options to display known extension types.

Works better now

Awesome, thanks. I did not realize that.

Now my Tactrix won't respond when plugging it in. The leds just slowly fade in and out of colors rather than the green and red lights flashing. Not sure why. Car is running and its plugged in to the OBD port, and not plugged into USB.