This is awesome. Is there a release notice about the MS-ALLOFIT that I missed? I shall search.

 

If I could dream I would like a BT sender on the board, sending all the channels in a protocol readable from RaceChrono.
This can of course be done by a OBD-II BT sender, already available and working (unsure about fishy parameters).
I have a RaceDAC, but that's a nightmare to set up (someone have made an app though), and requires additional harness hacking.

 

Yes, that can be done with the OBD-II BT sender, although I need to purchase a few more to test and make sure it is an issue with the specific el cheapo sender I have.

Btw there's no speed restriction on the CAN-bus OBD-II. If your device supports fast refresh rates, you'll get them.

 

Are you planning a model that would work with the MS2PNP? IE one that doesn't have a db9 connector?

 

This module works with ANY MS2 or MS3 ECU.

 

Is it possible to piggyback CAN modules? For instance, is it possible to connect both this and your WB02 module to the MS3?

Can you help me understand how getting OBD-II data via the CAN interface is different/better than connecting an Android tablet to the MS3 via USB?

 

You can connect up to 15 different modules on an MS2/MS3 via the CAN bus.

With OBD-II, you can connect ANY device that uses OBD-II to the ECU, not just a tablet with ShadowDash. For example I like the ScanGauge as it is easy to integrate, provides many different readings, works reliably and I can swap it between cars.

 

See, that's my thing. I've got a ScangaugeII and I'd love to be able to use it, but I'm not sure I want to add another device to the system. Maybe I'll just hardmount it to the Subaru and not think about it

 

Thanks Rev! Something for me to consider when I've got some extra cash :-) This '99 motor swap is bleeding me dry thanks to all the "While I'm in there I might as well do X also" thinking.

 

When you install this device, do you have to change a section of code in the ECU to output the OBDII signals to this bridge module? Or do the Megasquirt ECUs already stream out all of their channels and this bridge takes that data and reformats to the OBDII message protocol?

 

No changes or setup required. All you need to do is literally to connect the two CAN bus wires (CANH, CANL) from the module to the ECU and then provide 12V and ground to the module. That is it.

 

Very Nice. I'm curious... why do you call channels PIDs? I'm not familiar with that acronym.

 

Because that's what they are called in ISO 14230, Part 3.

Specifically, they are called "Parameter Identifiers", or PIDs.

 

Got it. Wasn't familiar with that one but it confused me with PID controllers and I was wondering if they were somehow related.

 

Yeah, that would explain the confusion.

 

Thinking about this route vs pulling my cluster and swapping the factory gauges for quality gauges.

Cost would be nearly the same.

You'd have to walk me through the wiring: (attach the green wire to the red one) and I'm definitely out if I need to solder anything to a board (we all have our limits). But if its a simple install and the factory sensors are accurate it could be a very sano install. Are the temp readings accurate?

I'd probably go with the Scangauge but do have a spare Android with Torque already installed...

 

You only have to solder 4 wires from the module to the DB-37 connector on the rear of the ECU: 12V, ground, CANH, CANL.

 

Ok. But will the factory sensors give me accurate information. IE tell me the actual coolant temp?

 

Yes, they do.

 

Got this gizmo today. Bear with me.

Red and black wires- 12v and ground?
Back and white? Are these the CANH and CANL? Which is which and where do they go?
On the back of the box is what appears to be a serial connector. What does this go to?

I picked up a WIFI dongle- it will send the info to my iPhone where I've installed dash command- an app that works with the Panasonic DVD player in the dash. All of this will allow any combination of gauges I'd like. Pretty cool stuff.