Please wait. Due to its content this page might take a while to load...
A Phidgets Stepper device is a controllable motor and can be connected either directly or via a Hub.
To add a Phidgets Stepper device, open the Devices menu and select Phidgets Device > Stepper Device. This opens the Configuration dialog. Alternatively, you can add a new device in the Configuration dialog with the "+" button.
On the right side, you can name, dis-/enable the device or configure it as explained in the next paragraph.
The name is the unique identifier for this Phidgets Stepper object in WD and the general rules for naming objects apply here as well (only letters, numbers and underscore are allowed, the first symbol must be a letter).
If you like, you can change the default name to a more descriptive one. When scripting, enter the name to access available members as described further down.
The "Enable" check box is ticked per default. On the left side, you should see that the icon in front of your Phidgets Stepper is a filled blue circle. An empty blue circle indicates an enabled device which is not connected. An empty gray circle indicates a disabled device.
You can close the dialog at any time. The newly created device will also be added to the Devices menu > Phidgets Device > Stepper Device and can be opened from here or with Devices menu > Configuration.
Select the Serial number of the connected device from the drop-down. If your device is connected to a Hub, use its serial number respectively.
Fill out Hub Port, Channel and Is Hub Port Device according to the Phidget Addressing Information dialog.
After the connection is established, the parameter fields will be displayed and updated as soon as a change is registered.
Before a Stepper motor can be used, it must be set to "Engaged", using the respective Script described below!
Please also make sure to not exceed the connected motor's capabilities.
After adding a Phidgets Stepper, you can also use it via scripting which allows to perform actions on the device as well as retrieve information from it.
To send commands to the device, first create a CustomScript button or use the Macro editor or anything else with a scripting field. If you enter the device's identifier name into the script field (per default that is e.g. "Phidgets_Stepper1"), Script Assist will offer you a list of all available members.
Before data transmission can be started, the device needs to be engaged using the following command:
After the device is engaged, you can for example set the Stepper to move continuously:
You can also retrieve specific values via scripting in the same way as from other widgets:
vbool = Phidgets_Stepper1.isMoving
The scripting structure for Phidgets provides two different approaches for setting and retrieving values.
If you are already familiar with the object-based notation and using properties, all device properties can be used like any other object property you have already encountered:
Phidgets_Stepper1.RescaleFactor = 2
Label5.Text = "Rescale: " + Phidgets_Stepper1.RescaleFactor
If you prefer a command structure that distinctly implies the action to be performed, you can use the "Set..." and "Get..." members:
Label5.Text = "Rescale: " + Phidgets_Stepper1.GetRescaleFactor
Both approaches can be used interchangeably.
Please keep in mind that some properties are read-only properties, e.g. "Velocity" or "TargetPosition", and do not provide a "Set..." member.
Furthermore, the higher-level properties of the device itself, like the Serial number or the Enabled state, need to be scripted as properties and do not provide the "Set..." and "Get..." members.
For a list with all available members and commands with examples and descriptions, please refer to the chapter Phidgets Stepper Members.
Event Listeners can be added to the Configuration dialog and provide a simple way of listening to triggers from connected devices.
Please see the chapter Event Listener for a detailed description of its functionality and the Phidgets Stepper Events chapter for a list (with examples and description) of the possible events raised by this device type.