PC 2.0 Idle Pulsing Accent LED Issue

[DarkarNights]

I just got my PC 2.0 today and got everything wired up and started testing everything. I opened up R.I.C.E. and got it working and everything is working as it should except one little weird issue. I have the LED ring on my anti vandal switch wired to Accent LED pad 1 (it's a pre-wired MWS PC 2.0 by the way), and when I adjust the idle pulse setting to 30, which is supposed to be always on, the LED continues to pulse in idle as if it was set to 29. When set to 0 it goes off completely, and reacts to every speed from 1-29, so I know it's reading that parameter of the config file properly, I just can't get it stay always on with the 30 setting. I have tried adjusting the setting through R.I.C.E. and directly on the SD by editing the text and both attempts produce the same results. Does anyone have an idea why this is behaving this way?

[erv]

good point, thanks a lot for posting this. Actually, I realize a while ago that the time base requires to put 40 to get it on all the time, no 30. I corrected this in the manual (at least for CFV5) but it seems it stayed in the R.I.C.E. app.
it's not anything with the firmware, just the computer software, I'll make an upgrade this afternoon. In the meanwhile, you can manually change the idlepulsing value in your configuration file to 40 to solve the issue.

hope that helps !

[DarkarNights]

Awesome, Thanks!

[DarkarNights]

Ok, now I'm having an entirely different problem with my R.I.C.E. cable. Yesterday everything worked perfectly. Today the drivers won't work, when I go into Device Manager and look at the Cable it has one of those warning triangles and in the properties displays this message "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)". I have tried uninstalling and reinstalling the drivers to no avail. I have no clue what the problem could be, especially since yesterday it worked flawlessly.

[erv]

either a windows problem : uninstall peripheral, un install drivers, start over.. (never got that issue on any of my computers though)
or you have a short in your wiring and the cable cannot be enumerated by the USB port, resulting of an unknown peripheral. Try connecting it alone, not connected to the sound board first.

[DarkarNights]

It has the same results when not connected to the PC2.0

[DarkarNights]

Found the solution to the issue here http://www.chinstruments.com/USB_416.shtml. The problem was that the new version of the driver has compatibility issues with older hardware. Installed version 4.40 of the driver (since I have 64 bit Win7) and now it's working for me.

[erv]

where did you get your drivers initially ? the ones from silabs work just fine.

updated the version of RICE for the PCv2,
the CF version will be updated as well in 5 minutes.

[DarkarNights]

From the scilabs link on the store R.I.C.E. page. The drivers work fine, but there seems to be compatibility issues with USB ports on older computers, particularity laptops. As per the info in the link I provided, the issue was non-existant on older versions of the driver. Thankfully this issue was prevalent enough that it didn't take much time to find the solution just using Google-Fu.

[erv]

excellent ! thanks for sharing that tip with us !