[cbrown9064]

Stuck...I cannot get Binary Editor to "see" my MTX-L. I double checked the com port and it matches. Even changed it to a lower number (com2) without any change.

Installed LogWorks and that can communicate with the gauge just fine. Reinstalled BE and EECA and still no joy.

Using the USB to serial adapter from Innovate. What the heck. Any ideas? Help! ;)

[cbrown9064]

Stuck...I cannot get Binary Editor to "see" my MTX-L. I double checked the com port and it matches. Even changed it to a lower number (com2) without any change.

Installed LogWorks and that can communicate with the gauge just fine. Reinstalled BE and EECA and still no joy.

Using the USB to serial adapter from Innovate. What the heck. Any ideas? Help! ;)

For future searches. This post was a lot of help...

http://www.eectuning.org/forums/viewtopic.php?p=93953

But, for whatever reason the Innovate does not go green in the Hardware tab of BE like the QH does. For some reason I was expecting this and spent a couple hours trying to get it to go. However, when Channel 1 of the Innovate is enabled with a label, and you start to datalog, it will pull the MTX-L data into the datalog along with all the other sensors from the EEC.

So, it works, but just not like I thought it would with the light next to it going "green" when enabled and the MTX-L was on. I suppose if you had an LM-2 with a USB connection that is a different story.

[TrueMetalGeek]

Yeah that kind of threw me for a second too when I first got the gear.
The QH lights up but the MTX doesn't communicate or something until it is polled when you datalog. It's likely just because BE only needs to be connected to the QH so you can read,write or update the tune whereas the accessories like the MTX are only needed when you log.

The thing that got me was that it is simply named NONE until you rename it in the hardware settings.
Then in your DASH displays you need to set it up to that name so it accesses it.