If this has already been addressed, I apologize. I didn't see it anywhere.
I'm trying to run the OP2 standalone on my 94 3000GT. It initializes and starts logging just fine, but eventually drops the connection after a few minutes of driving. It doesn't seem consistent as to when it drops. After it does, the yellow light flashes like it's trying to re-initialize, but it never does. If re-plug the OP2 while I'm driving along, it reconnects but eventually drops again. I've trimmed my log config down to about a dozen parameters, and it doesn't seem to be making a difference.
I've tested this using a spare bench ECU, and it logged 24 parameters for 2.5 hours without issue (and generated a 7.5MB log file). So the problem seems to be with the fact that it's on a live car. However, EvoScan doesn't seem to have any such problems. So I'm less inclined to believe it's some quirk of the older style ECUs. But I'm not ruling it out either. This behavior has been duplicated on a friend's car as well.
I know the OP2 was tested and developed with the newer cars in mind, so I'm open to the possibility the older ones may have some strangeness. What I really am looking for is some guidance in troubleshooting this issue. I'd like to get it working properly if possible.