I never thought about it that way. I am surpirsed about the SD ard support myself, possibly other ECUs may start incorporating it as well.

Here's a crazy question, would this make it easier/possible to add telemetry data?

There are GPS USB antenna's and there are also readily available accelerometers (Wii remote for example). Just an idea from a MS newb.

Chris

It's possible if you're willing to write drivers for it, otherwise one component is speaking moon-language and the other is Sun Ra.

Joe, it's mostly for total nit-pickers. For instance, I'd like to have a couple more rows in the 20-35kpa range, since my light-throttle cruise is forced rich due to a lack of resolution. I've fiddled with it a bunch and could never get it right (and now I don't care). If you're adding another thousand RPM or going beyond 230kpa, it would be nice to have the same resolution as an MSII setup across a wider range.

For many, yeah, it's just unnecessary, but you can always just ignore the top few rows/columns if the dyno clock is ticking a bit quickly.

At the MegaMeet, the developers indicated it would still be 16x16. The presentations they gave are on DIY's site, I believe. Interesting stuff, and looks very promising.

Probably not.

For one, the USB port on the MS3 is a type B receptacle, typically found on client devices (DCE, for you old-timers) such as printers. Such devices typically are incapable of acting as hosts to other peripheral equipment, but only as clients to a host (ie, a PC.) Additionally, my suspicion is that this particular USB device is simply a virtualized RS232 connection. There was talk of implementing it that way at several points in the discussion, and doing so would have reduced its burden on the CPU to almost zero, whereas implementing the full-blown USB protocol in software would have chewed up considerable processor resources, which is not something you want to do in a mission-critical realtime system.

Joe hit the nail on the head. From further reading, its only a simple USB --> Serial connection.

Correct. It's basically a copy of the circuit on the eMS-Pro.

Ok, that explains the physical size of the connector, which I was wondering about. In the past, I've used a device which was packaged as a slightly oversized USB-B connector and integrated the electronics into the package. You spoke to the device in standard RS-232, and it presented itself to the host as an RS-232 port. Saved a tiny bit of board space, as it was only one device instead of two.

I can't really tell from the pictures, are they using one of the FTDI "FT232" series transceivers? Most of those are QFPs, but the only square chip I see is the processor.

I'm pretty sure it is an FTDI.