I've also just hit the problem with an NVidia chipset (on an Asus A7N8X-E motherobard). In the device manager it appears to be using the standard Windows generic USB chipset driver (see attached). NVidia (or perhaps Asus) should have some more specific USB 2.0 drivers for my motherboard, maybe I never installed them? I'll have a look shortly...

The LEDWiz control panel gives me really random results with this motherboard. To test it out properly, I guess I'd really have all 32 outputs connected to LEDs.For example, when I set 4,5,6,7,8,9 and 30,31,32 to saw and turn them on 30,31,32 will saw but 4,5,6,7,8,9 remain constantly on.Now when I set 1 to saw, but leave it off, 4,5,6,7,8 begin to saw, 9 remains constantly on and 30,31,32 continue to saw.Then I switched 6 to square and 4,5,6,7,8,9 went constantly on, 30,31,32 ocntinued to sawtooth.Switching 6 back to saw does nothing.

I restarted and got the same results.First I tried your first testbench.exe and 4,5,6,7,8,9 sawed really fast, 30,31,32 were constantly on.Then I exited, all leds turned off.I ran your second testbench.exe and all my leds sawed really fast.Then I tried the first testbench.exe again; all my leds sawed really fast.

Does it make any sense to you?

I'm going to have to leave it for tonight (past my bedtime and all that). I hope I was of some help.

Hello, I got 14 hooked up and they seem to be sawing correctly. I now have a headache and eye burn-in watching this stuff. Do you think this is hardware or software related? I would think that it is a hardware issue, but I really have no clue....

I was about to shut down the computer and I thought I'd give it one more test. I restarted and tried the second testbench.exeI got the same results as the first testbench.exe (4,5,6,7,8,9 saw, 30,31,32 are on).

Then I tried the first testbench.exe; same results.

Then I tried the second one again; same thing, 30,31,32 still aren't sawing.

Tried each one a couple more times and eventually the second testbench.exe got them all sawing.

Why are you guys running mame cabs with nvidia anything on them? Haven't you heard us old timers preaching about how nvidia cards/chipsets/whatever suck for mame since oh.... around 1997. Use only ati products or just don't bother.

Heh, maybe true of the graphics cards (I've never used anything but ATI ever since I tried a All-in-Wonder Pro. Ok so 3D on a RagePro was not exactly awesome but that card could do everything) but nforce motherboards are not bad...

I'm please to see progress is made. I've got a LedWiz, although I've not had a chance to hook it up yet. But I do have nforce 2, nforce 2 ultra 400, ati xpress200 and via based chipset motherboards I could set up and test if its needed - although sounds like lots of people are on the case....

Why are you guys running mame cabs with nvidia anything on them? Haven't you heard us old timers preaching about how nvidia cards/chipsets/whatever suck for mame since oh.... around 1997. Use only ati products or just don't bother.

Hope this stuff gets sorted out soon.

FWIW I'm not using my nForce2 based machine in a Mame cab, I'm just trying to narrow down the LedWiz issue for other people out there.

Yes, that is the driver that is giving everyone the problems. FWIW, I decided to use NVIDIA chipsets because my cabs double as a Daphne emulator also. Daphne and ATI don't mix well together. I have not run into any major problems with NVIDIA and Mame...Maybe I should switch to Via chipsets with a NVIDIA video card?

Joymonkey,1. I's not a driver issue. (In reality, I can't say this for sure, but it is highly unlikey to be a driver issue).2. If you have the LEDWiz connected directly to the PC meaning no hub, then it's not connected to the ECHI controller. It's connected to one of the OHCI controllers.

Can we get a list of the specs of the hubs it fails with as well? i.e. 1.1 or 2.0 hubs and if you are really good can you pop the top on the hub and see who makes the chip.

Anyone with a chipset besides Intel, Via or Nvidia? Or using a PCI USB 2.0 card not using a Via Chip?

I plan to put my portable analyzer on it later to see if it is what I think it is, but I may not have time to test every scenario and I may be completely wrong.

MikeQ

Joymonkey,1. I's not a driver issue. (In reality, I can't say this for sure, but it is highly unlikey to be a driver issue).2. If you have the LEDWiz connected directly to the PC meaning no hub, then it's not connected to the ECHI controller. It's connected to one of the OHCI controllers.

Can we get a list of the specs of the hubs it fails with as well? i.e. 1.1 or 2.0 hubs and if you are really good can you pop the top on the hub and see who makes the chip.

Anyone with a chipset besides Intel, Via or Nvidia? Or using a PCI USB 2.0 card not using a Via Chip?

I plan to put my portable analyzer on it later to see if it is what I think it is, but I may not have time to test every scenario and I may be completely wrong.

I've actually have a workaround for the hub issue. One other person had a hub issue too. I need to get them the test to see if it works on their machine/hub. The hub issue appears to have something to do with timing and buffer flushes. The LWZ-PBA command that we are having trouble with is a multi-report command. If I flush the buffers to the controller between reports, the HUB works fine.

It is a usb 2.0 hub. Its is a "Travel Hub" branded by Staples. It is really a Belkin however. I've had it open but don't have the chip id. I can check later.

This didn't appear to fix the Nforce problem though. JoyMonkey needs to retest from a clean boot though.