Tinkerforge::BrickDC - Drives one brushed DC motor with up to 28V and 5A (peak)
This constant is used to identify a DC Brick.
The get_identity() subroutine and the CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.
This constant represents the display name of a DC Brick.
This constant is used with the register_callback() subroutine to specify the CALLBACK_UNDER_VOLTAGE callback.
This constant is used with the register_callback() subroutine to specify the CALLBACK_EMERGENCY_SHUTDOWN callback.
This constant is used with the register_callback() subroutine to specify the CALLBACK_VELOCITY_REACHED callback.
This constant is used with the register_callback() subroutine to specify the CALLBACK_CURRENT_VELOCITY callback.
This constant is used with the get_response_expected(), set_response_expected() and set_response_expected_all() subroutines.
Creates an object with the unique device ID *uid* and adds it to the IP Connection *ipcon*.
Sets the velocity of the motor. Whereas -32767 is full speed backward, 0 is stop and 32767 is full speed forward. Depending on the acceleration (see :func:`Set Acceleration`), the motor is not immediately brought to the velocity but smoothly accelerated.
The velocity describes the duty cycle of the PWM with which the motor is controlled, e.g. a velocity of 3277 sets a PWM with a 10% duty cycle. You can not only control the duty cycle of the PWM but also the frequency, see :func:`Set PWM Frequency`.
Returns the velocity as set by :func:`Set Velocity`.
Returns the *current* velocity of the motor. This value is different from :func:`Get Velocity` whenever the motor is currently accelerating to a goal set by :func:`Set Velocity`.
Sets the acceleration of the motor. It is given in *velocity/s*. An acceleration of 10000 means, that every second the velocity is increased by 10000 (or about 30% duty cycle).
For example: If the current velocity is 0 and you want to accelerate to a velocity of 16000 (about 50% duty cycle) in 10 seconds, you should set an acceleration of 1600.
If acceleration is set to 0, there is no speed ramping, i.e. a new velocity is immediately given to the motor.
Returns the acceleration as set by :func:`Set Acceleration`.
Sets the frequency of the PWM with which the motor is driven. Often a high frequency is less noisy and the motor runs smoother. However, with a low frequency there are less switches and therefore fewer switching losses. Also with most motors lower frequencies enable higher torque.
If you have no idea what all this means, just ignore this function and use the default frequency, it will very likely work fine.
Returns the PWM frequency as set by :func:`Set PWM Frequency`.
Executes an active full brake.
.. warning:: This function is for emergency purposes, where an immediate brake is necessary. Depending on the current velocity and the strength of the motor, a full brake can be quite violent.
Call :func:`Set Velocity` with 0 if you just want to stop the motor.
Returns the stack input voltage. The stack input voltage is the voltage that is supplied via the stack, i.e. it is given by a Step-Down or Step-Up Power Supply.
Returns the external input voltage. The external input voltage is given via the black power input connector on the DC Brick.
If there is an external input voltage and a stack input voltage, the motor will be driven by the external input voltage. If there is only a stack voltage present, the motor will be driven by this voltage.
.. warning:: This means, if you have a high stack voltage and a low external voltage, the motor will be driven with the low external voltage. If you then remove the external connection, it will immediately be driven by the high stack voltage.
Returns the current consumption of the motor.
Enables the driver chip. The driver parameters can be configured (velocity, acceleration, etc) before it is enabled.
Disables the driver chip. The configurations are kept (velocity, acceleration, etc) but the motor is not driven until it is enabled again.
.. warning:: Disabling the driver chip while the motor is still turning can damage the driver chip. The motor should be stopped calling :func:`Set Velocity` with 0 before disabling the motor power. The :func:`Set Velocity` function will **not** wait until the motor is actually stopped. You have to explicitly wait for the appropriate time after calling the :func:`Set Velocity` function before calling the :func:`Disable` function.
Returns *true* if the driver chip is enabled, *false* otherwise.
Sets the minimum voltage, below which the :cb:`Under Voltage` callback is triggered. The minimum possible value that works with the DC Brick is 6V. You can use this function to detect the discharge of a battery that is used to drive the motor. If you have a fixed power supply, you likely do not need this functionality.
Returns the minimum voltage as set by :func:`Set Minimum Voltage`
Sets the drive mode. Possible modes are:
* 0 = Drive/Brake * 1 = Drive/Coast
These modes are different kinds of motor controls.
In Drive/Brake mode, the motor is always either driving or braking. There is no freewheeling. Advantages are: A more linear correlation between PWM and velocity, more exact accelerations and the possibility to drive with slower velocities.
In Drive/Coast mode, the motor is always either driving or freewheeling. Advantages are: Less current consumption and less demands on the motor and driver chip.
Returns the drive mode, as set by :func:`Set Drive Mode`.
Sets a period with which the :cb:`Current Velocity` callback is triggered. A period of 0 turns the callback off.
Returns the period as set by :func:`Set Current Velocity Period`.
The SPITF protocol can be used with a dynamic baudrate. If the dynamic baudrate is enabled, the Brick will try to adapt the baudrate for the communication between Bricks and Bricklets according to the amount of data that is transferred.
The baudrate will be increased exponentially if lots of data is sent/received and decreased linearly if little data is sent/received.
This lowers the baudrate in applications where little data is transferred (e.g. a weather station) and increases the robustness. If there is lots of data to transfer (e.g. Thermal Imaging Bricklet) it automatically increases the baudrate as needed.
In cases where some data has to transferred as fast as possible every few seconds (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn the dynamic baudrate off to get the highest possible performance.
The maximum value of the baudrate can be set per port with the function :func:`Set SPITFP Baudrate`. If the dynamic baudrate is disabled, the baudrate as set by :func:`Set SPITFP Baudrate` will be used statically.
.. versionadded:: 2.3.5$nbsp;(Firmware)
Returns the baudrate config, see :func:`Set SPITFP Baudrate Config`.
Returns the timeout count for the different communication methods.
The methods 0-2 are available for all Bricks, 3-7 only for Master Bricks.
This function is mostly used for debugging during development, in normal operation the counters should nearly always stay at 0.
.. versionadded:: 2.3.3$nbsp;(Firmware)
Sets the baudrate for a specific Bricklet port.
If you want to increase the throughput of Bricklets you can increase the baudrate. If you get a high error count because of high interference (see :func:`Get SPITFP Error Count`) you can decrease the baudrate.
If the dynamic baudrate feature is enabled, the baudrate set by this function corresponds to the maximum baudrate (see :func:`Set SPITFP Baudrate Config`).
Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in your applications we recommend to not change the baudrate.
Returns the baudrate for a given Bricklet port, see :func:`Set SPITFP Baudrate`.
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
* ACK checksum errors, * message checksum errors, * framing errors and * overflow errors.
The errors counts are for errors that occur on the Brick side. All Bricklets have a similar function that returns the errors on the Bricklet side.
Enables the status LED.
The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.
The default state is enabled.
.. versionadded:: 2.3.1$nbsp;(Firmware)
Disables the status LED.
Returns *true* if the status LED is enabled, *false* otherwise.
Returns the firmware and protocol version and the name of the Bricklet for a given port.
This functions sole purpose is to allow automatic flashing of v1.x.y Bricklet plugins.
Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has an accuracy of ±15%. Practically it is only useful as an indicator for temperature changes.
Calling this function will reset the Brick. Calling this function on a Brick inside of a stack will reset the whole stack.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
Writes 32 bytes of firmware to the bricklet attached at the given port. The bytes are written to the position offset * 32.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
Reads 32 bytes of firmware from the bricklet attached at the given port. The bytes are read starting at the position offset * 32.
Returns the UID, the UID where the Brick is connected to, the position, the hardware and firmware version as well as the device identifier.
The position is the position in the stack from '0' (bottom) to '8' (top).
The device identifier numbers can be found :ref:`here <device_identifier>`. |device_identifier_constant|
To install Tinkerforge, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Tinkerforge
CPAN shell
perl -MCPAN -e shell install Tinkerforge
For more information on module installation, please visit the detailed CPAN module installation guide.