Tech Edge WBO2 Forum

[bike_tuner]

Hello,

When I plug the 2J1 into my laptop, Plug N Play kicks in, sees it as a Microsoft Serial ballpoint mouse, and auto installs the mouse drivers. It does not see it as a WBO2 controller. When I try to do a manual hardware install windows has no idea what it is, so I point to the drivers (the two *.INF files) that I downloaded from this site, it will not accept them, because it thinks it's a mouse and those aren't mouse drivers.

My USB to serial connector is installed and functioning. The 2J1 is of course connected to a 12v battery and fully operational. I've tested it with the small display that it came with, and it worked fine. Puffed a little butane from a lighter into the lambda sensor and it registered fine.

I've tried disabling that mouse driver in Device Manager, but to no avail. Tried re-booting with the 2J1 plugged in, nothing happens. Tried re-booting with it not plugged in, then plugging it in, and nothing happens. Tried disabling plug and play on the computer. Tried uninstalling the serial mouse driver. Tried every combination of these things that I could imagine.

Sometimes when I'd plug the 2J1 controller in, Windows would spaz out and the cursor would jump all over the screen like a demon possessed. Apparently this is a known bug- it happens to GPS users as well.

I've owned the 2J1 for over a year now, I ran into this problem when I got it, was stymied and put it on a shelf. Now I have need to datalog and tune a couple of bikes, and I need it. It was too expensive to use as a paperweight.

Windows gurus, please help. At least give me the bullet points on how you successfully got it to work on your machine.

Thanks.

[Thomas]

Hi.
I ran into this trouble some time ago as well. I choose in Device Manager "show inactive devices" (or whatever it is called in the English version of XP). Then the serial Ballpoint appears and I disabled it. As far as I remember, it worked, then.
Also look at http://wbo2forum.com/viewtopic.php?t=1635
Thomas

[bike_tuner]

So I seem to have gotten past that issue- the ballpoint mouse bug.

However, the response that I'm getting from the unit is really confusing.
I should preface this all by saying that I'm testing the unit on the bench, by connecting it to a fully charged 12v motorcycle battery, and the O2 sensor. No other logging inputs (0~5v user inputs) are connected to anything.

The serial to USB adaptor I'm using (IOgear) has a little yellow LED that flashes when data goes through it. There is no explanation in the instructions as to what those flashes mean, but as near as I can tell, no light means nothing is happening, a steady flash means connection error, and a rapid flash means that data is passing. I have seen it with the yellow light lit constantly as well, no clue what that means.

Again, I have tested the unit (2J1) itself, but connecting the display, holding a butane lighter in front of the O2 sensor, and seeing it go from "lean" to numeric readings from 20.00 to below 10 to "rich" that would indicate that it is all working (2J1, wiring, O2 sensor).

I downloaded the Tech Edge utility program, and all indications are that the program is seeing the 2J1 and O2 sensor. Those indications are, that in the terminal window, there is a constant stream of numeric data scrolling, if I hit the CLS button, it deletes it, but then continues to scroll data. If I unplug the unit, that scrolling stops, then re-starts when I plug it back in.
In the calibrate screen, if I hit the Start button, the data light on the serial/ USP adapter flashes rapidly and it proceeds to give a reading in the light blue box, but will stop and beep if I unplug either the O2 sensor from the loom, or the 2J1 from the serial connector. If I hit the Start button with nothing connected, nothing happens.
Also, in the WB tables page, if I hit the "read" button, the yellow cursor scrolls down through the "data" column, to the bottom and stops. If I try that with the unit disconnected, nothing happens.
All of this indicates to me that the 2J1 is connected to the computer, and the WB Util application is communicating with it.

The problem is, that when I open either Winlog or TEWBlog, though I don't get an connection error message, neither of those programs will show an A/F lambda reading change when I puff butane gas from a lighter into the O2 sensor.
Am I misunderstanding something here? Shouldn't both of those programs show a change in the indicated A/F display from "10.1" to something else if I send butane into the sensor, as happens with the small display that came with the unit?
Is there some set-up parameter in those two programs that I'm missing? I have them configured to the correct COM port and wideband version 1.5.

I should note as well, that in TEWBlog, there is a very small red square in the very top left corner of the window that flashes when the unit is connected, but stops flashing when it's disconnected. That gives me hope that there is a connection there, but that something is just configured wrong.

I want to get the unit completely working and de-bugged here on the bench before I take it outside and start connecting it to my motorcycles.

Any help in clearing this up is greatly appreciated.

[KJ16V]

Hi. In Winlog/Tewblog, if you click on the AFR window is Data Source set to TechEdge Wideband o2 - lambda1?

Are all your configurations setup in the View menu?