The order of devices connecting to an unspecified channel is not guaranteed. If you want to connect to a specific Phidget, you will need to be specific in your addressing parameters (e.g. setDeviceSerialNumber). The only time you can reasonably expect to connect to the right device without specifyin...
As implemented, DC Motor baking strength only applies when Velocity = 0 The velocity parameter is a target duty cycle, which will by definition apply power in one direction or another when Velocity is non-zero. Braking Strength is the fraction of time the motor will be shorted to itself once it has ...
Sounds like you're looking for the Phidget Manager. It will detect any Phidgets that are connected and disconnected from your PC (and network, if configured). https://www.phidgets.com/docs/Phidget_Manager You can check the Hello World examples from the Code Samples page for an example of how to use ...
We've looked into it, and it looks like there is indeed headroom to get VCP1002 to go faster, with an expected new minimum interval between 10-20ms. Expect an update in the coming weeks.
To measure 2kg on a 500kg load cell, you are using 0.4% of its full scale range. This would be equivalent to trying to accurately measure weights up to 20g on a 5kg load cell. Possible? Technically, but you're approaching the point where many other small effects could skew the results significantly ...
MOT0109 and MOT1102 are your real options if you want orientation calculated for you.
MOT0109 features temperature compensation and more accurate sensors for applications that need them, but it sounds like the MOT1102 should be good enough for your purposes.
Which Spatial 3/3/3 are you looking at? The ones with AHRS support will give you a tilt-compensated Heading from the algorithmData outlet, alongside Pitch and Roll. If all you need is an attitude-adjusted compass, I'd recommend going with an MOT1102 (which needs a VINT Hub, but still comes out cheap...
That actually sounds a lot like a crash related to the compass calibration program itself that we fixed a while ago, where the program would crash if the calibration took too long. Try updating you control panel (and by extension the compass calibrator) to the latest version, and let us know if that...