This is the description of the Modbus protocol for the Industrial Digital Out 4 Bricklet 2.0. General information and technical specifications for the Industrial Digital Out 4 Bricklet 2.0 are summarized in its hardware description.
A general description of the Modbus protocol structure can be found here.
BrickletIndustrialDigitalOut4V2.
set_value
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the output value of all four channels. A value of true or false outputs logic 1 or logic 0 respectively on the corresponding channel.
Use set_selected_value
to change only one output channel state.
All running monoflop timers and PWMs will be aborted if this function is called.
For example: (True, True, False, False) will turn the channels 0-1 high and the channels 2-3 low.
BrickletIndustrialDigitalOut4V2.
get_value
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the logic levels that are currently output on the channels.
BrickletIndustrialDigitalOut4V2.
set_selected_value
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the output value of a specific channel without affecting the other channels.
A running monoflop timer or PWM for the specified channel will be aborted if this function is called.
BrickletIndustrialDigitalOut4V2.
set_channel_led_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Each channel has a corresponding LED. You can turn the LED off, on or show a heartbeat. You can also set the LED to "Channel Status". In this mode the LED is on if the channel is high and off otherwise.
By default all channel LEDs are configured as "Channel Status".
The following meanings are defined for the elements of this function:
For config:
BrickletIndustrialDigitalOut4V2.
get_channel_led_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the channel LED configuration as set by set_channel_led_config
The following meanings are defined for the elements of this function:
For config:
BrickletIndustrialDigitalOut4V2.
set_monoflop
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
The first parameter is the desired state of the channel (true means output high and false means output low). The second parameter indicates the time that the channel should hold the state.
If this function is called with the parameters (true, 1500): The channel will turn on and in 1.5s it will turn off again.
A PWM for the selected channel will be aborted if this function is called.
A monoflop can be used as a failsafe mechanism. For example: Lets assume you have a RS485 bus and a IO-4 Bricklet is connected to one of the slave stacks. You can now call this function every second, with a time parameter of two seconds. The channel will be high all the time. If now the RS485 connection is lost, the channel will turn low in at most two seconds.
BrickletIndustrialDigitalOut4V2.
get_monoflop
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns (for the given channel) the current value and the time as set by
set_monoflop
as well as the remaining time until the value flips.
If the timer is not running currently, the remaining time will be returned as 0.
BrickletIndustrialDigitalOut4V2.
set_pwm_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Activates a PWM for the given channel.
To turn the PWM off again, you can set the frequency to 0 or any other
function that changes a value of the channel (e.g. set_selected_value
).
The optocoupler of the Industrial Digital Out 4 Bricklet 2.0 has a rise time and fall time of 11.5us (each) at 24V. So the maximum useful frequency value is about 400000 (40kHz).
A running monoflop timer for the given channel will be aborted if this function is called.
BrickletIndustrialDigitalOut4V2.
get_pwm_configuration
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the PWM configuration as set by set_pwm_configuration
.
BrickletIndustrialDigitalOut4V2.
get_spitfp_error_count
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
BrickletIndustrialDigitalOut4V2.
set_status_led_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following meanings are defined for the elements of this function:
For config:
BrickletIndustrialDigitalOut4V2.
get_status_led_config
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the configuration as set by set_status_led_config
The following meanings are defined for the elements of this function:
For config:
BrickletIndustrialDigitalOut4V2.
get_chip_temperature
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
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 bad accuracy. Practically it is only useful as an indicator for temperature changes.
BrickletIndustrialDigitalOut4V2.
reset
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
BrickletIndustrialDigitalOut4V2.
get_identity
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here.
BrickletIndustrialDigitalOut4V2.
CALLBACK_MONOFLOP_DONE
¶Function ID: |
|
---|---|
Response: |
|
This callback is triggered whenever a monoflop timer reaches 0. The response values contain the channel and the current value of the channel (the value after the monoflop).
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletIndustrialDigitalOut4V2.
set_bootloader_mode
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following meanings are defined for the elements of this function:
For mode:
For status:
BrickletIndustrialDigitalOut4V2.
get_bootloader_mode
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current bootloader mode, see set_bootloader_mode
.
The following meanings are defined for the elements of this function:
For mode:
BrickletIndustrialDigitalOut4V2.
set_write_firmware_pointer
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Sets the firmware pointer for write_firmware
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletIndustrialDigitalOut4V2.
write_firmware
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Writes 64 Bytes of firmware at the position as written by
set_write_firmware_pointer
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletIndustrialDigitalOut4V2.
write_uid
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
BrickletIndustrialDigitalOut4V2.
read_uid
¶Function ID: |
|
---|---|
Request: |
|
Response: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.