Scott,
I can take a look. I was more interested in the 25 pin PCB connector to put in an MS-II adapter board at the time, but I know the terminals can be had, so I’m sure the cable connectors can as well. We’d also need a little board to plug our logger into but that wouldn’t be a problem. It can be a temporary solution if you’re only interested in solving a specific problem & then going back to the simpler solution.
I’ve been looking at video/data logging systems & the comments about them on this forum. I’m sure the Traqmate & similar systems are excellent for learning to drive, but in my opinion they’re not really adequate for total health monitoring. Specifically, the Traqmate only has 4 analog inputs & 2 digital I/O, which isn’t going to go far enough to getting meaningful data unless you’re willing to pick only a few I/O to observe at a time. Plus you’d lose your shift light, oil pressure & temp, etc if you want to monitor engine parameters. I believe that 8 analog inputs is the practical minimum for such a system if you’re looking for a single logger solution.
The other issue is sample rate. I was told this weekend at the track (but didn’t verify) that it only samples the inputs & the accelerometer at 10 Hz (the same rate as the GPS chipset produces an NMEA sentence). I’m sure the ‘race’ loggers are similar in this respect. The GPS location data is only accurate to 3-10m, so the error in position data in that time is negligible but in 0.1 seconds, some of the engine parameters we’re interested in have changed dramatically. Specifically crank position signal at 6500 RPM sampled at 10Hz is going to be worse than useless. If this seems elementary, please understand that I’m trying to make it clear for the non-engineer. Of course, sifting through all the resulting data may be more technical than most want to handle and I wouldn’t blame them.
The only potential issue that I would point out is sampling sensors that are used by the DME & ensuring a reliable ground is maintained on the adapter board. If piggybacking of existing sensors is done incorrectly, you can affect the value that the DME measures, making it think a sensor is reporting a different value than it is, and clearly adding to your problems. This isn’t always trivial as evidenced by the army (2 or 3 to read essentially the same thing) of coolant temperature sensors on the M20B27 thermostat housing. One goes to the DME, one to the instrument cluster so as not to interfere with each other. However, most all of these issues have been solved before in the Megasquirt community and there is documentation on how to handle dual use of the same sensor, so we can apply the same approach successfully. Once the correct circuit values have been determined & verified, they can be used for all of our cars. Again, all of this could be built into a board on this adapter & then a cable run directly to the logger of your choice which would sample at an appropriate rate for each of the lines in question.
Phew. Let me look into the connector situation & we can discuss.