MicroSquirt.com read only forum (Jan.15,2018)

I purchased a serial ECU/DL1 logger adaptor from Race Technology to suit the MS3, but the EFI will not run with the adaptor connected (no prime pump, no start). Disconnecting the adaptor allows the engine to start and run normally.
They state on their website that . . . "The Megasquirt MS2 serial interface is designed to work with the Megasquirt MS2 hardware, with the serial port operating at 115.2kbaud. It has been tested with Megasquirt-2 (MS2/Extra) 3.2.5 and will also work with Megasquirt-2 (MS2/Extra) 3.3.2 and above Megasquirt-3 1.3.1 and above "
Has anyone had success running the DL1 with a Microsquirt 3? I really want to enable serial logging of the MS3 data stream, rather than duplicating sensors.

I have nothing intelligent to say on your actual inquiry, but I will toss out two things to reduce confusion. First, all the MicroSquirts are MS2 based; MS3 means "MegaSquirt 3" and is a very different beasty than the little uS V3.

Second, if you're using the extra code, you need to discuss it over on the Extra forum (click the link at the top of the page). The B&G code is quite different from the Extra code, and they are discussed on different sites.

So, to clarify, I have a uS V3 that I want to use with the DL1. I am using the original code, and not using Extra code. Hope that helps someone chime in.

Hi

I don't think you'll have much luck with the serial RX/TX, but the CAN interface looks suitable. I haven't trawled the manuals to establish what the CAN addresses are, but the DL1 can do 11 & 29 bit addressing.
Here's the link here, and it uses a 29 bit address, so that suggests there is compatability.
However, I think CAN comms are not for the faint hearted, as quite a lot of folks struggle with it.

Mike

Feedback from RT is that I would have to run MS2/Extra code for their adaptor to work (if that is indeed the case), so I am none the wiser. Maybe future B&G code for the uS V3 could have the same serial code embedded so that these comms systems are standardised? At the moment it looks like I am duplicating sensors, and have a very expensive comms adaptor sitting on the shelf.
And yes, I could go to Extra code, but I am quite happy with 3.830, and the engine works sweet now!

wombat258,

I had a quick look, and I'm not even able to do it, but CAN is the way to go. There is no reason why data from the MicroSquirt v3 can't be polled into the DL1, as long as you use the right CAN address. I can't help you, because I don't have a RT unit, nor a running v3 at the moment, but I think RT are wrong after a brief skim of their manual, and the Megasquirt 2 manual.

Mike

Thanks Mike,

I am eventually going turbo with these ITB's, so it may be opportune then to upgrade to the MS2Extra code. How hard can it be to transfer a working setup from 3.830 to MS2Extra 3.3.1?

The RT CAN adaptor costs as much as the ECU adaptor, and can't see a point if there is a high chance it will not work either.

Cheers, Stephen in Oz

wombat258 wrote: ...How hard can it be to transfer a working setup from 3.830 to MS2Extra 3.3.1?

I've converted from an earlier version of the B&G code, because my tooth pattern wasn't supported, but to be honest, as the RT adaptors are a similar price, maybe one of the gurus might chime in and explain the CAN option some more.
You can always try, and get a base setting, and revert back to your known working version.
I also know that the other forum generally has much more activity, so I'd watch the CAN threads over there, because one or two people are trying to make dashes work etc, and the lessons learned should help.
I imagine the CAN addresses are different for the two firmwares, but the underlying principle will be the same, as they use the same microprocessor.

Mike

RT's response was to give me new firmware that they were adamant would work with the serial adaptor. It took a while for me to try the ECU adaptor on the Microsquirt with the new firmware from RT. The end result was a corruption of the Microsquirt firmware, requiring a complete reload. Fortunately nothing permanent, but a confirmation that the ECU serial adaptor will not work with the Microsquirt. Duplicating sensors to allow logging is the only way.

Now I am ticked off. It appears that something has has gone wrong as the Microsquirt no longer reads AFR from my Techedge WB. Reads a constant 19:1, even when shorting the O2 wire to ground. No wiring issues. Tried many reflashes with no luck. No obvious damage or shorts on the board. It worked perfectly before the RT was hooked up to it, and now I gather the unit is toast . . . I am not happy at all.