Rumble and wireless assistance

[richw]

Excellent, thanks Jon. I was starting to wonder if a BASIC program would be helpful - just asking you to try things, then press a key etc. But maybe this is is workable-ish as-is.

Can you try the attached version? I've put in a retry mechanism to try and cope with the 'stall' situation. It looks like USBDriver and EtherUSB do similar. So far, I've been mainly doing USB reads, which are dead easy, and it seems that certain writes are not so straightforward. It should capture in Reporter if it's failing, and what's going on with retries/stalls. This is applied to all comms (apart from the basic 'read inputs', which has been there since day 1) so maybe things like the device product/manufacturer strings will return correctly now?

The player LED/ring should also now be automatic. After you attach a controller, it should be 'player 1', another will be 'player 2' etc. Does that work? It will spit out stuff in Reporter as it goes.

Does the rumble command work properly? Is the first motor the big one, and the second the small one? (it is on my PSX pad) Does it still work if you disconnect and later re-connect a controller?

If anyone here has a PS3 pad, it would be nice to know if that works.

[richw]

Ah, I've spotted an off-by-one error in the PS3 pad detection, which might explain why they don't work. A possible fix is in this build.