Advice on Controller Vibration

Hello,
I am looking for some guidance on best practices for vibration effects. I don't want to ruin anyones hardware or burn out motors by using settings that aren't friendly to the controller.

I have a couple of questions:

1) Is it acceptable to use "pulsed" effects by calling GamePad.SetVibration() every Update() to change slightly change the motor settings, creating the feeling of "punches."

2) Can that pulsing include complete stops of the vibration?

3) Is there any guidance on maximum suggested duty cycles for using the vibration? (Not that I plan to leave it on much, but should I be intentionally limiting the duty cycle if the player engages in non-game behavior like punching all the time for 10 minutes?)

4) Is there any guidance on minimum period of on-off-on cycles?

Basically I want to know if:

a) I can hurt this thing by not following some rules I don't know about, or,
b) The API is watching my back and not passing on dangerous commands to hardware / applying some kind of low-pass filter, or,
c) The hardware can handle whatever this API can throw at it.

Thanks in advance for any advice on these issues.

[1179 byte] By [DouglasMcClean] at [2007-12-24]
# 1

1. I don't see why not, although every Update might be a little much since you'll be calling it every 15 ms or so at a minimum.

2. Again, I don't see why not.

3/4. I'd say 4c is the most likely possibility. When you start trying to force player behavior you're not headed in a good direction IMO.

JimPerry at 2007-10-8 > top of Msdn Tech,Game Technologies: DirectX, XNA, XACT, etc.,XNA Framework...
# 2
Sounds good.
I certainly don't want to limit players, I just don't want to be blamed for killing their hardware :).

I'll operate on the assumption that there really aren't any unwritten rules.

Thanks.

DouglasMcClean at 2007-10-8 > top of Msdn Tech,Game Technologies: DirectX, XNA, XACT, etc.,XNA Framework...
# 3
More of a personal view here, while I think the hardware will be fine I would avoid any kind of constant controller vibration while playing a game. Based on experience I've heard from other game devleopers when we were working on games this can lead to numbness in your hands and that's usually unpleasant :-)
MichaelKlucher-MSFT at 2007-10-8 > top of Msdn Tech,Game Technologies: DirectX, XNA, XACT, etc.,XNA Framework...
# 4
We've accidentally left controllers on stuck in vibration mode overnight and have never seen any ill effects on the hardware. I don't think you have to ever worry about breaking the motors, but do be considerate of your players.
AaronLeiby at 2007-10-8 > top of Msdn Tech,Game Technologies: DirectX, XNA, XACT, etc.,XNA Framework...
# 5
Sorry if I gave a mistaken impression. I don't intend to leave it on for long (more than about a second or two), but if the player decides to take certain (useless, but permitted) repetitive actions he/she could cause it to be on indefinitely with a high duty cycle (> 90%).

I agree that long term vibrations are not a very good thing.

Thanks everyone for your help.

DouglasMcClean at 2007-10-8 > top of Msdn Tech,Game Technologies: DirectX, XNA, XACT, etc.,XNA Framework...