Try the newer version here: jbperf.com ? View topic - Port scanner

 

Ok I figured it out, it's ID 0.

 

That shouldn't be possible. If they are both ID 0 then you will get weird conflicts.

 

Now it's not giving the CAN ID error, but it is saying "failed to communicate, settings changed will not be saved" blah blah blah.

 

Yeah. if both devices are 0 it won't work. You could try changing the Master ID to something besides 0. But I've never done that before.

You would have to change it in the CAN Parameters too.

No idea how to change the WBO2 module device id.

 

The CAN module ID is always 9.

How old is this module?

 

Purchased from Trackspeed in April of 2016

 

This is the exact same problem I had. I was unable to resolve it through emails with Rev. When I sent the whole shebang to Greece it was "verified working properly " but I have been unable to test since. I'm just using regular analog input.

 

It was working fine as of January when the motor was pulled.

I sent my last tune over to Martin, maybe you can compare settings and see if that helps?

 

After reading it, I should amend my post. I am *currently* using regular old wbo2 input just to make the car run.

 

I managed to get this working, combination of proper protocol and selecting CAN ID 9 from the project properties drop down menu.

 

Where is the protocol selection. (or which one are you talking about)

 

It's in the CAN module config menus. You can select whether you have an Innovate MTS, AEM serial, AEM CAN, Zeitronix serial or PLX iMFD (experimental support).

 

This is what I like to call "super ******* frustrating" I have vteckiller's exact ECU. As in the physical set of atoms, 100%. Bought it from him. I didn't know this problem existed until I could not establish CAN communication with this hardware and bumbled into this thread. My indicated o2 reading on the innovate gauge is close to full lean (16-22) and the TunerStudio reading is full rich (7.40 or 9, depending on the mood).

My setup is a used Innovate MTX-L purchased from some local guy who parted out his turbo car, and (formerly) vteckillers MSLabs MS3 Basic with CAN module. Reverant confirmed that my ECU is a standard build via email/serial #, I have flashed the Megasquirt with firmware 1.4.0, and according to vteckiller2000's posts in here, the whole shebang had been sent to Greece to be checked out by the man himself.

Can anyone spoonfeed me instructions, preferably step by step, to check all possible software/firmware issues this could be related to? Here is what I have done so far:

1. Reflashed MS3 firmware to 1.4.0 as Rev stated was appropriate. Done weeks ago.
2. Reflashed to appropriate base calibration for 2001 Miata, emailed to me by Rev. Set timing to known value from previous start attempts, calibrated pedal sensor.
3. Followed CAN module instructions to establish connection. No dice.
4. Set “Enable CAN receiving” to on through CAN receiving menu. Not in instructions, but seems appropriate.
5. Project properties -> CAN Devices, set wideband to CAN ID: 9.


At this point the ECU reinitializes and gives this error. (Filename says narrowband - it's not, just an old name)


On a previous tune attempt, I flashed the "CAN Wideband Module V102.ini" file. Then I read a post here saying that flashing the wrong firmware may "Break things" per Rev. So I'm not in the mood to go try random firmwares. That absolutely should be called out in the instructions.
.
I took apart the CAN module - it's a version 2.1 from 2016. Red and yellowgreen lights are on, blue lights will flash when the ECU is keyed on. Apparently that's important.




Using the port scanner utility aidan linked, I was able to confirm that the system is at least present, and on channel 00



Halp?

 

I'll try to get a screenshot of my CAN settings tonight for you if you don't get it figured out before then.

 

Your settings show an ID of 1 for the module, not 9.

 

I have set it to 9 previously, as I said it will shut down any communication with the ECU in that setting until I remove that CAN device in the same project properties window. That is just a screenshot from when I reset it back.

Is 1.02 or 1.04 the appropriate firmware for a 2016 year version 2.1? A list of versions/dates and the appropriate firmware along with warnings would be a useful addition to the instructions. I don't have the original instructions that would have shipped with this, I bought it used so I got instructions off TSE.

Did I break things by using v1.02 as this link states I may have? Red and green lights are on full time, blue lights are flashing. https://www.miataturbo.net/ms-labs-m...e-78449/page2/

 

1.0.4. is the correct version for a V2.1.

If the blue CAN is flashing, that means there's correct communication with the ECU. If the Serial blue led is flashing, the module is communicating properly with the wideband.

 

V1.04 uploaded, TS automatically moved it to its own folder and renamed the file. Both red and green lights are on solid, both blue lights are flashing. Still shows no device found on any channel.



CAN EGO Settings as per instructions.


CAN Receiving set to on, no other changes in this menu from default.


AFR/EGO settings as per instructions


Lambda averaging lag factor set to 100 as per instructions.



Tunerstudio still shows AFR pegged at 9, Innovate MTX still shows AFR pegged at 22.4.

Any other settings I can change? .msq attached.

 

SUCCESS!

Went to Devices (Pink arrow), changed to wideband, clicked on CAN Wideband Module Setup for a drop down menu (Purple arrow), and changed the wideband from AEM to Innovate (Yellow arrow). No idea why it would default to this, but it do.



Hope this helps someone else! Thanks to everyone for the replies.