vputz wrote:If you got one of the "production" boards with four holes in a row behind the USB connector, those four holes should be (top to bottom, looking with the USB connector on the left): +5V, D-, D+, GND
So one thing you could try is manually send it the init string.
Luckily, it did happen to the "production" board...I'll have to look up the cable pinouts on a USB port but soldering to those holes is probably a much more viable long term solution.
The prototype board doesn't have these holes, so I'll probably blob some solder onto it and superglue it down for good measure. The USB port in this board version is being held on by basically two solder pads with not much solder because it's reflowed (the latest has a connector w/ mechanical legs that go through holes in the board so no worries w/ that one). For folks who do have the older one, I'd recommend superglue at least if they're not up to soldering...
I did add the init string so it does work.
Should I change the sketch and do another pull request on github or do you want to change this on the official copy?
FWIW, mine looks like this now:
Serial.println("switch 1 (nearest to the serial port) ON, switch 2 OFF");
Serial.println("Serial dump follows:\n");
FWIW, none of my spacemice report any ball movement when using the orbSerial sketch, only button data.
Other than using linux and its drivers
Could you point me at the drivers and any utility to test it?
I loaded the Spaceball 5000 sketch and the values being reported in the Windows joystick settings, make no sense so it seems like the ball may be damaged.
E.g., the x-y-z rotation returns variances of maybe 20 points +- from the neutral value of 512. So you can run the calibration utility to get it mostly work, but it's *very* sensitive as a result. I don't think I should need to run the calibration utility to get the full +-512 values if I crank the ball hard enough