Software / API Bindings / JavaScript / API Reference and Examples / Bricklets / RS485 Bricklet

JavaScript - RS485 Bricklet¶

This is the description of the JavaScript API bindings for the RS485 Bricklet. General information and technical specifications for the RS485 Bricklet are summarized in its hardware description.

An installation guide for the JavaScript API bindings is part of their general description.

Examples¶

The example code below is Public Domain (CC0 1.0).

Loopback (Node.js)¶

Download (ExampleLoopback.js)

var Tinkerforge = require('tinkerforge');

// For this example connect the RX+/- pins to TX+/- pins on the same Bricklet
// and configure the DIP switch on the Bricklet to full-duplex mode

var HOST = 'localhost';
var PORT = 4223;
var UID = 'XYZ'; // Change XYZ to the UID of your RS485 Bricklet

var ipcon = new Tinkerforge.IPConnection(); // Create IP connection
var rs485 = new Tinkerforge.BrickletRS485(UID, ipcon); // Create device object

ipcon.connect(HOST, PORT,
    function (error) {
        console.log('Error: ' + error);
    }
); // Connect to brickd
// Don't use device before ipcon is connected

ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
    function (connectReason) {
        // Enable full-duplex mode
        rs485.setRS485Configuration(115200, Tinkerforge.BrickletRS485.PARITY_NONE,
                                    Tinkerforge.BrickletRS485.STOPBITS_1,
                                    Tinkerforge.BrickletRS485.WORDLENGTH_8,
                                    Tinkerforge.BrickletRS485.DUPLEX_FULL);

        // Enable read callback
        rs485.enableReadCallback();

        // Write "test" string
        rs485.write('test'.split(''));
    }
);

// Register read callback
rs485.on(Tinkerforge.BrickletRS485.CALLBACK_READ,
    // Callback function for read callback
    function (message) {
        // Assume that the message consists of ASCII characters and
        // convert it from an array of chars to a string
        console.log('Message: "' + message.join('') + '"');
    }
);

console.log('Press key to exit');
process.stdin.on('data',
    function (data) {
        ipcon.disconnect();
        process.exit(0);
    }
);

Modbus Slave (Node.js)¶

Download (ExampleModbusSlave.js)

var Tinkerforge = require('tinkerforge');

var HOST = 'localhost';
var PORT = 4223;
var UID = 'XYZ'; // Change XYZ to the UID of your RS485 Bricklet

var ipcon = new Tinkerforge.IPConnection(); // Create IP connection
var rs485 = new Tinkerforge.BrickletRS485(UID, ipcon); // Create device object

ipcon.connect(HOST, PORT,
    function (error) {
        console.log('Error: ' + error);
    }
); // Connect to brickd
// Don't use device before ipcon is connected

ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
    function (connectReason) {
        // Set operating mode to Modbus RTU slave
        rs485.setMode(Tinkerforge.BrickletRS485.MODE_MODBUS_SLAVE_RTU);

        // Modbus specific configuration:
        // - slave address = 17
        // - master request timeout = 0ms (unused in slave mode)
        rs485.setModbusConfiguration(17, 0);
    }
);

// Register Modbus slave write single register request callback
rs485.on(Tinkerforge.BrickletRS485.CALLBACK_MODBUS_SLAVE_WRITE_SINGLE_REGISTER_REQUEST,
    // Callback function for Modbus slave write single register request callback
    function (requestID, registerAddress, registerValue) {
        console.log('Request ID: ' + requestID);
        console.log('Register Address: ' + registerAddress);
        console.log('Register Value: ' + registerValue);

        if (registerAddress != 42) {
            console.log('Requested invalid register address');
            rs485.modbusSlaveReportException(requestID, Tinkerforge.BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS);
        } else {
            rs485.modbusSlaveAnswerWriteSingleRegisterRequest(requestID);
        }
    }
);

console.log('Press key to exit');
process.stdin.on('data',
    function (data) {
        ipcon.disconnect();
        process.exit(0);
    }
);

Modbus Master (Node.js)¶

Download (ExampleModbusMaster.js)

var Tinkerforge = require('tinkerforge');

var HOST = 'localhost';
var PORT = 4223;
var UID = 'XYZ'; // Change XYZ to the UID of your RS485 Bricklet

var ipcon = new Tinkerforge.IPConnection(); // Create IP connection
var rs485 = new Tinkerforge.BrickletRS485(UID, ipcon); // Create device object

var expectedRequestID = 0;

ipcon.connect(HOST, PORT,
    function (error) {
        console.log('Error: ' + error);
    }
); // Connect to brickd
// Don't use device before ipcon is connected

ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
    function (connectReason) {
        // Set operating mode to Modbus RTU master
        rs485.setMode(Tinkerforge.BrickletRS485.MODE_MODBUS_MASTER_RTU);

        // Modbus specific configuration:
        // - slave address = 1 (unused in master mode)
        // - master request timeout = 1000ms
        rs485.setModbusConfiguration(1, 1000);

        // Write 65535 to register 42 of slave 17
        rs485.modbusMasterWriteSingleRegister(17, 42, 65535,
            function (requestID) {
                expectedRequestID = requestID;
            }
        );
    }
);

// Register Modbus master write single register response callback
rs485.on(Tinkerforge.BrickletRS485.CALLBACK_MODBUS_MASTER_WRITE_SINGLE_REGISTER_RESPONSE,
    // Callback function for Modbus master write single register response callback
    function (requestID, exceptionCode) {
        console.log('Request ID: ' + requestID);
        console.log('Exception Code: ' + exceptionCode);

        if (requestID != expectedRequestID) {
            console.log('Error: Unexpected request ID');
        }
    }
);

console.log('Press key to exit');
process.stdin.on('data',
    function (data) {
        ipcon.disconnect();
        process.exit(0);
    }
);

Loopback (HTML)¶

Download (ExampleLoopback.html), Test (ExampleLoopback.html)

<!DOCTYPE html>

<!-- For this example connect the RX+/- pins to TX+/- pins on the same Bricklet
     and configure the DIP switch on the Bricklet to full-duplex mode -->

<html>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <head>
        <title>Tinkerforge | JavaScript Example</title>
    </head>
    <body>
        <div style="text-align:center;">
            <h1>RS485 Bricklet Loopback Example</h1>
            <p>
                <input value="localhost" id="host" type="text" size="20">:
                <input value="4280" id="port" type="text" size="5">,
                <input value="uid" id="uid" type="text" size="5">
                <input value="Start Example" id="start" type="button" onclick="startExample();">
            </p>
            <p>
                <textarea readonly id="text" cols="80" rows="24" style="resize:none;"
                          >Press "Start Example" to begin ...</textarea>
            </p>
        </div>
        <script src="./Tinkerforge.js" type='text/javascript'></script>
        <script type='text/javascript'>
            var ipcon;
            var textArea = document.getElementById("text");
            function startExample() {
                textArea.value = "";
                var HOST = document.getElementById("host").value;
                var PORT = parseInt(document.getElementById("port").value);
                var UID = document.getElementById("uid").value;
                if(ipcon !== undefined) {
                    ipcon.disconnect();
                }
                ipcon = new Tinkerforge.IPConnection(); // Create IP connection
                var rs485 = new Tinkerforge.BrickletRS485(UID, ipcon); // Create device object
                ipcon.connect(HOST, PORT,
                    function(error) {
                        textArea.value += 'Error: ' + error + '\n';
                    }
                ); // Connect to brickd
                // Don't use device before ipcon is connected

                ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
                    function (connectReason) {
                        // Enable full-duplex mode
                        rs485.setRS485Configuration(115200, Tinkerforge.BrickletRS485.PARITY_NONE,
                                                    Tinkerforge.BrickletRS485.STOPBITS_1,
                                                    Tinkerforge.BrickletRS485.WORDLENGTH_8,
                                                    Tinkerforge.BrickletRS485.DUPLEX_FULL);

                        // Enable read callback
                        rs485.enableReadCallback();

                        // Write "test" string
                        rs485.write('test'.split(''));
                    }
                );

                // Register read callback
                rs485.on(Tinkerforge.BrickletRS485.CALLBACK_READ,
                    // Callback function for read callback
                    function (message) {
                        // Assume that the message consists of ASCII characters and
                        // convert it from an array of chars to a string
                        textArea.value += 'Message: "' + message.join('') + '"\n');
                        textArea.scrollTop = textArea.scrollHeight;
                    }
                );
            }
        </script>
    </body>
</html>

Modbus Slave (HTML)¶

Download (ExampleModbusSlave.html), Test (ExampleModbusSlave.html)

<!DOCTYPE html>
<html>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <head>
        <title>Tinkerforge | JavaScript Example</title>
    </head>
    <body>
        <div style="text-align:center;">
            <h1>RS485 Bricklet Modbus Slave Example</h1>
            <p>
                <input value="localhost" id="host" type="text" size="20">:
                <input value="4280" id="port" type="text" size="5">,
                <input value="uid" id="uid" type="text" size="5">
                <input value="Start Example" id="start" type="button" onclick="startExample();">
            </p>
            <p>
                <textarea readonly id="text" cols="80" rows="24" style="resize:none;"
                          >Press "Start Example" to begin ...</textarea>
            </p>
        </div>
        <script src="./Tinkerforge.js" type='text/javascript'></script>
        <script type='text/javascript'>
            var ipcon;
            var textArea = document.getElementById("text");
            function startExample() {
                textArea.value = "";
                var HOST = document.getElementById("host").value;
                var PORT = parseInt(document.getElementById("port").value);
                var UID = document.getElementById("uid").value;
                if(ipcon !== undefined) {
                    ipcon.disconnect();
                }
                ipcon = new Tinkerforge.IPConnection(); // Create IP connection
                var rs485 = new Tinkerforge.BrickletRS485(UID, ipcon); // Create device object
                ipcon.connect(HOST, PORT,
                    function(error) {
                        textArea.value += 'Error: ' + error + '\n';
                    }
                ); // Connect to brickd
                // Don't use device before ipcon is connected

                ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
                    function (connectReason) {
                        // Set operating mode to Modbus RTU slave
                        rs485.setMode(Tinkerforge.BrickletRS485.MODE_MODBUS_SLAVE_RTU);

                        // Modbus specific configuration:
                        // - slave address = 17
                        // - master request timeout = 0ms (unused in slave mode)
                        rs485.setModbusConfiguration(17, 0);
                    }
                );

                // Register Modbus slave write single register request callback
                rs485.on(Tinkerforge.BrickletRS485.CALLBACK_MODBUS_SLAVE_WRITE_SINGLE_REGISTER_REQUEST,
                    // Callback function for Modbus slave write single register request callback
                    function (requestID, registerAddress, registerValue) {
                        textArea.value += 'Request ID: ' + requestID + '\n';
                        textArea.value += 'Register Address: ' + registerAddress + '\n';
                        textArea.value += 'Register Value: ' + registerValue + '\n';

                        if (registerAddress != 42) {
                            textArea.value += 'Error: Invalid register address\n';
                            rs485.modbusSlaveReportException(requestID, Tinkerforge.BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS);
                        } else {
                            rs485.modbusSlaveAnswerWriteSingleRegisterRequest(requestID);
                        }

                        textArea.scrollTop = textArea.scrollHeight;
                    }
                );
            }
        </script>
    </body>
</html>

Modbus Master (HTML)¶

Download (ExampleModbusMaster.html), Test (ExampleModbusMaster.html)

<!DOCTYPE html>
<html>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <head>
        <title>Tinkerforge | JavaScript Example</title>
    </head>
    <body>
        <div style="text-align:center;">
            <h1>RS485 Bricklet Modbus Master Example</h1>
            <p>
                <input value="localhost" id="host" type="text" size="20">:
                <input value="4280" id="port" type="text" size="5">,
                <input value="uid" id="uid" type="text" size="5">
                <input value="Start Example" id="start" type="button" onclick="startExample();">
            </p>
            <p>
                <textarea readonly id="text" cols="80" rows="24" style="resize:none;"
                          >Press "Start Example" to begin ...</textarea>
            </p>
        </div>
        <script src="./Tinkerforge.js" type='text/javascript'></script>
        <script type='text/javascript'>
            var ipcon;
            var textArea = document.getElementById("text");
            function startExample() {
                textArea.value = "";
                var HOST = document.getElementById("host").value;
                var PORT = parseInt(document.getElementById("port").value);
                var UID = document.getElementById("uid").value;
                if(ipcon !== undefined) {
                    ipcon.disconnect();
                }
                ipcon = new Tinkerforge.IPConnection(); // Create IP connection
                var rs485 = new Tinkerforge.BrickletRS485(UID, ipcon); // Create device object
                ipcon.connect(HOST, PORT,
                    function(error) {
                        textArea.value += 'Error: ' + error + '\n';
                    }
                ); // Connect to brickd
                // Don't use device before ipcon is connected

                ipcon.on(Tinkerforge.IPConnection.CALLBACK_CONNECTED,
                    function (connectReason) {
                        // Set operating mode to Modbus RTU master
                        rs485.setMode(Tinkerforge.BrickletRS485.MODE_MODBUS_MASTER_RTU);

                        // Modbus specific configuration:
                        // - slave address = 1 (unused in master mode)
                        // - master request timeout = 1000ms
                        rs485.setModbusConfiguration(1, 1000);

                        // Write 65535 to register 42 of slave 17
                        rs485.modbusMasterWriteSingleRegister(17, 42, 65535,
                            function (requestID) {
                                expectedRequestID = requestID;
                            }
                        );
                    }
                );

                // Register Modbus master write single register response callback
                rs485.on(Tinkerforge.BrickletRS485.CALLBACK_MODBUS_MASTER_WRITE_SINGLE_REGISTER_RESPONSE,
                    // Callback function for Modbus master write single register response callback
                    function (requestID, exceptionCode) {
                        textArea.value += 'Request ID: ' + requestID + '\n';
                        textArea.value += 'Exception Code: ' + exceptionCode + '\n';

                        if (requestID != expectedRequestID) {
                            textArea.value += 'Error: Unexpected request ID\n';
                        }

                        textArea.scrollTop = textArea.scrollHeight;
                    }
                );
            }
        </script>
    </body>
</html>

API¶

Generally, every function of the JavaScript bindings can take two optional parameters, returnCallback and errorCallback. These are two user defined callback functions. The returnCallback function is called with the results as arguments, if the function returns its results asynchronously. The errorCallback is called with an error code in case of an error. The error code can be one of the following values:

IPConnection.ERROR_ALREADY_CONNECTED = 11
IPConnection.ERROR_NOT_CONNECTED = 12
IPConnection.ERROR_CONNECT_FAILED = 13
IPConnection.ERROR_INVALID_FUNCTION_ID = 21
IPConnection.ERROR_TIMEOUT = 31
IPConnection.ERROR_INVALID_PARAMETER = 41
IPConnection.ERROR_FUNCTION_NOT_SUPPORTED = 42
IPConnection.ERROR_UNKNOWN_ERROR = 43
IPConnection.ERROR_STREAM_OUT_OF_SYNC = 51
IPConnection.ERROR_NON_ASCII_CHAR_IN_SECRET = 71
IPConnection.ERROR_WRONG_DEVICE_TYPE = 81
IPConnection.ERROR_DEVICE_REPLACED = 82
IPConnection.ERROR_WRONG_RESPONSE_LENGTH = 83
IPConnection.ERROR_INT64_NOT_SUPPORTED = 91

The namespace for the JavaScript bindings is Tinkerforge.*.

Basic Functions¶

new BrickletRS485(uid, ipcon)¶

Parameters:	uid – Type: string ipcon – Type: IPConnection
Returns:	rs485 – Type: BrickletRS485

Creates an object with the unique device ID uid:

var rs485 = new BrickletRS485("YOUR_DEVICE_UID", ipcon);

This object can then be used after the IP Connection is connected.

BrickletRS485.write(message[, returnCallback][, errorCallback])¶

Parameters:	message – Type: [char, ...], Length: variable
Callback Parameters:	messageWritten – Type: int, Range: [0 to 2¹⁶ - 1]
Returns:	undefined

Writes characters to the RS485 interface. The characters can be binary data, ASCII or similar is not necessary.

The return value is the number of characters that were written.

See setRS485Configuration() for configuration possibilities regarding baudrate, parity and so on.

BrickletRS485.read(length[, returnCallback][, errorCallback])¶

Parameters:	length – Type: int, Range: [0 to 2¹⁶ - 1]
Callback Parameters:	message – Type: [char, ...], Length: variable
Returns:	undefined

Returns up to length characters from receive buffer.

Instead of polling with this function, you can also use callbacks. But note that this function will return available data only when the read callback is disabled. See enableReadCallback() and CALLBACK_READ callback.

BrickletRS485.setRS485Configuration(baudrate, parity, stopbits, wordlength, duplex[, returnCallback][, errorCallback])¶

Parameters:	baudrate – Type: int, Unit: 1 Bd, Range: [100 to 2000000], Default: 115200 parity – Type: int, Range: See constants, Default: 0 stopbits – Type: int, Range: See constants, Default: 1 wordlength – Type: int, Range: See constants, Default: 8 duplex – Type: int, Range: See constants, Default: 0
Callback Parameters:	undefined
Returns:	undefined

Sets the configuration for the RS485 communication.

The following constants are available for this function:

For parity:

BrickletRS485.PARITY_NONE = 0
BrickletRS485.PARITY_ODD = 1
BrickletRS485.PARITY_EVEN = 2

For stopbits:

BrickletRS485.STOPBITS_1 = 1
BrickletRS485.STOPBITS_2 = 2

For wordlength:

BrickletRS485.WORDLENGTH_5 = 5
BrickletRS485.WORDLENGTH_6 = 6
BrickletRS485.WORDLENGTH_7 = 7
BrickletRS485.WORDLENGTH_8 = 8

For duplex:

BrickletRS485.DUPLEX_HALF = 0
BrickletRS485.DUPLEX_FULL = 1

BrickletRS485.getRS485Configuration([returnCallback][, errorCallback])¶

Callback Parameters:	baudrate – Type: int, Unit: 1 Bd, Range: [100 to 2000000], Default: 115200 parity – Type: int, Range: See constants, Default: 0 stopbits – Type: int, Range: See constants, Default: 1 wordlength – Type: int, Range: See constants, Default: 8 duplex – Type: int, Range: See constants, Default: 0
Returns:	undefined

Returns the configuration as set by setRS485Configuration().

The following constants are available for this function:

For parity:

BrickletRS485.PARITY_NONE = 0
BrickletRS485.PARITY_ODD = 1
BrickletRS485.PARITY_EVEN = 2

For stopbits:

BrickletRS485.STOPBITS_1 = 1
BrickletRS485.STOPBITS_2 = 2

For wordlength:

BrickletRS485.WORDLENGTH_5 = 5
BrickletRS485.WORDLENGTH_6 = 6
BrickletRS485.WORDLENGTH_7 = 7
BrickletRS485.WORDLENGTH_8 = 8

For duplex:

BrickletRS485.DUPLEX_HALF = 0
BrickletRS485.DUPLEX_FULL = 1

BrickletRS485.setModbusConfiguration(slaveAddress, masterRequestTimeout[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [1 to 247], Default: 1 masterRequestTimeout – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 1000
Callback Parameters:	undefined
Returns:	undefined

Sets the configuration for the RS485 Modbus communication. Available options:

Slave Address: Address to be used as the Modbus slave address in Modbus slave mode. Valid Modbus slave address range is 1 to 247.
Master Request Timeout: Specifies how long the master should wait for a response from a slave when in Modbus master mode.

BrickletRS485.getModbusConfiguration([returnCallback][, errorCallback])¶

Callback Parameters:	slaveAddress – Type: int, Range: [1 to 247], Default: 1 masterRequestTimeout – Type: int, Unit: 1 ms, Range: [0 to 2³² - 1], Default: 1000
Returns:	undefined

Returns the configuration as set by setModbusConfiguration().

BrickletRS485.setMode(mode[, returnCallback][, errorCallback])¶

Parameters:	mode – Type: int, Range: See constants, Default: 0
Callback Parameters:	undefined
Returns:	undefined

Sets the mode of the Bricklet in which it operates. Available options are

RS485,
Modbus Master RTU and
Modbus Slave RTU.

The following constants are available for this function:

For mode:

BrickletRS485.MODE_RS485 = 0
BrickletRS485.MODE_MODBUS_MASTER_RTU = 1
BrickletRS485.MODE_MODBUS_SLAVE_RTU = 2

BrickletRS485.getMode([returnCallback][, errorCallback])¶

Callback Parameters:	mode – Type: int, Range: See constants, Default: 0
Returns:	undefined

Returns the configuration as set by setMode().

The following constants are available for this function:

For mode:

BrickletRS485.MODE_RS485 = 0
BrickletRS485.MODE_MODBUS_MASTER_RTU = 1
BrickletRS485.MODE_MODBUS_SLAVE_RTU = 2

Advanced Functions¶

BrickletRS485.setCommunicationLEDConfig(config[, returnCallback][, errorCallback])¶

Parameters:	config – Type: int, Range: See constants, Default: 3
Callback Parameters:	undefined
Returns:	undefined

Sets the communication LED configuration. By default the LED shows RS485 communication traffic by flickering.

You can also turn the LED permanently on/off or show a heartbeat.

If the Bricklet is in bootloader mode, the LED is off.

The following constants are available for this function:

For config:

BrickletRS485.COMMUNICATION_LED_CONFIG_OFF = 0
BrickletRS485.COMMUNICATION_LED_CONFIG_ON = 1
BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_COMMUNICATION = 3

BrickletRS485.getCommunicationLEDConfig([returnCallback][, errorCallback])¶

Callback Parameters:	config – Type: int, Range: See constants, Default: 3
Returns:	undefined

Returns the configuration as set by setCommunicationLEDConfig()

The following constants are available for this function:

For config:

BrickletRS485.COMMUNICATION_LED_CONFIG_OFF = 0
BrickletRS485.COMMUNICATION_LED_CONFIG_ON = 1
BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletRS485.COMMUNICATION_LED_CONFIG_SHOW_COMMUNICATION = 3

BrickletRS485.setErrorLEDConfig(config[, returnCallback][, errorCallback])¶

Parameters:	config – Type: int, Range: See constants, Default: 3
Callback Parameters:	undefined
Returns:	undefined

Sets the error LED configuration.

By default the error LED turns on if there is any error (see CALLBACK_ERROR_COUNT callback). If you call this function with the SHOW ERROR option again, the LED will turn off until the next error occurs.

You can also turn the LED permanently on/off or show a heartbeat.

If the Bricklet is in bootloader mode, the LED is off.

The following constants are available for this function:

For config:

BrickletRS485.ERROR_LED_CONFIG_OFF = 0
BrickletRS485.ERROR_LED_CONFIG_ON = 1
BrickletRS485.ERROR_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletRS485.ERROR_LED_CONFIG_SHOW_ERROR = 3

BrickletRS485.getErrorLEDConfig([returnCallback][, errorCallback])¶

Callback Parameters:	config – Type: int, Range: See constants, Default: 3
Returns:	undefined

Returns the configuration as set by setErrorLEDConfig().

The following constants are available for this function:

For config:

BrickletRS485.ERROR_LED_CONFIG_OFF = 0
BrickletRS485.ERROR_LED_CONFIG_ON = 1
BrickletRS485.ERROR_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletRS485.ERROR_LED_CONFIG_SHOW_ERROR = 3

BrickletRS485.setBufferConfig(sendBufferSize, receiveBufferSize[, returnCallback][, errorCallback])¶

Parameters:	sendBufferSize – Type: int, Unit: 1 B, Range: [2¹⁰ to 9216], Default: 5120 receiveBufferSize – Type: int, Unit: 1 B, Range: [2¹⁰ to 9216], Default: 5120
Callback Parameters:	undefined
Returns:	undefined

Sets the send and receive buffer size in byte. In sum there is 10240 byte (10KiB) buffer available and the minimum buffer size is 1024 byte (1KiB) for both.

The current buffer content is lost if this function is called.

The send buffer holds data that was given by write() and could not be written yet. The receive buffer holds data that is received through RS485 but could not yet be send to the user, either by read() or through CALLBACK_READ callback.

BrickletRS485.getBufferConfig([returnCallback][, errorCallback])¶

Callback Parameters:	sendBufferSize – Type: int, Unit: 1 B, Range: [2¹⁰ to 9216], Default: 5120 receiveBufferSize – Type: int, Unit: 1 B, Range: [2¹⁰ to 9216], Default: 5120
Returns:	undefined

Returns the buffer configuration as set by setBufferConfig().

BrickletRS485.getBufferStatus([returnCallback][, errorCallback])¶

Callback Parameters:	sendBufferUsed – Type: int, Unit: 1 B, Range: [0 to 9216] receiveBufferUsed – Type: int, Unit: 1 B, Range: [0 to 9216]
Returns:	undefined

Returns the currently used bytes for the send and received buffer.

See setBufferConfig() for buffer size configuration.

BrickletRS485.getErrorCount([returnCallback][, errorCallback])¶

Callback Parameters:	overrunErrorCount – Type: int, Range: [0 to 2³² - 1] parityErrorCount – Type: int, Range: [0 to 2³² - 1]
Returns:	undefined

Returns the current number of overrun and parity errors.

BrickletRS485.getModbusCommonErrorCount([returnCallback][, errorCallback])¶

Callback Parameters:

Callback Parameters:	timeoutErrorCount – Type: int, Range: [0 to 2³² - 1] checksumErrorCount – Type: int, Range: [0 to 2³² - 1] frameTooBigErrorCount – Type: int, Range: [0 to 2³² - 1] illegalFunctionErrorCount – Type: int, Range: [0 to 2³² - 1] illegalDataAddressErrorCount – Type: int, Range: [0 to 2³² - 1] illegalDataValueErrorCount – Type: int, Range: [0 to 2³² - 1] slaveDeviceFailureErrorCount – Type: int, Range: [0 to 2³² - 1]
Returns:	undefined

timeoutErrorCount – Type: int, Range: [0 to 2³² - 1]
checksumErrorCount – Type: int, Range: [0 to 2³² - 1]
frameTooBigErrorCount – Type: int, Range: [0 to 2³² - 1]
illegalFunctionErrorCount – Type: int, Range: [0 to 2³² - 1]
illegalDataAddressErrorCount – Type: int, Range: [0 to 2³² - 1]
illegalDataValueErrorCount – Type: int, Range: [0 to 2³² - 1]
slaveDeviceFailureErrorCount – Type: int, Range: [0 to 2³² - 1]

Returns:

undefined

Returns the current number of errors occurred in Modbus mode.

Timeout Error Count: Number of timeouts occurred.
Checksum Error Count: Number of failures due to Modbus frame CRC16 checksum mismatch.
Frame Too Big Error Count: Number of times frames were rejected because they exceeded maximum Modbus frame size which is 256 bytes.
Illegal Function Error Count: Number of errors when an unimplemented or illegal function is requested. This corresponds to Modbus exception code 1.
Illegal Data Address Error Count: Number of errors due to invalid data address. This corresponds to Modbus exception code 2.
Illegal Data Value Error Count: Number of errors due to invalid data value. This corresponds to Modbus exception code 3.
Slave Device Failure Error Count: Number of errors occurred on the slave device which were unrecoverable. This corresponds to Modbus exception code 4.

BrickletRS485.modbusSlaveReportException(requestID, exceptionCode[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to report a Modbus exception for a Modbus master request.

Request ID: Request ID of the request received by the slave.
Exception Code: Modbus exception code to report to the Modbus master.

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.modbusSlaveAnswerReadCoilsRequest(requestID, coils[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255] coils – Type: [boolean, ...], Length: variable
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to read coils.

Request ID: Request ID of the corresponding request that is being answered.
Coils: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the CALLBACK_MODBUS_SLAVE_READ_COILS_REQUEST callback with the Request ID as provided by the argument of the callback.

BrickletRS485.modbusMasterReadCoils(slaveAddress, startingAddress, count[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 2000]
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to read coils from a slave. This function creates a Modbus function code 1 request.

Slave Address: Address of the target Modbus slave.
Starting Address: Number of the first coil to read. For backwards compatibility reasons this parameter is called Starting Address. It is not an address, but instead a coil number in the range of 1 to 65536.
Count: Number of coils to read.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_READ_COILS_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.modbusSlaveAnswerReadHoldingRegistersRequest(requestID, holdingRegisters[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255] holdingRegisters – Type: [int, ...], Length: variable, Range: [0 to 2¹⁶ - 1]
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to read holding registers.

Request ID: Request ID of the corresponding request that is being answered.
Holding Registers: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the CALLBACK_MODBUS_SLAVE_READ_HOLDING_REGISTERS_REQUEST callback with the Request ID as provided by the argument of the callback.

BrickletRS485.modbusMasterReadHoldingRegisters(slaveAddress, startingAddress, count[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 125]
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to read holding registers from a slave. This function creates a Modbus function code 3 request.

Slave Address: Address of the target Modbus slave.
Starting Address: Number of the first holding register to read. For backwards compatibility reasons this parameter is called Starting Address. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is implicit and must be omitted.
Count: Number of holding registers to read.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_READ_HOLDING_REGISTERS_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.modbusSlaveAnswerWriteSingleCoilRequest(requestID[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255]
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to write a single coil.

Request ID: Request ID of the corresponding request that is being answered.

This function must be called from the CALLBACK_MODBUS_SLAVE_WRITE_SINGLE_COIL_REQUEST callback with the Request ID as provided by the arguments of the callback.

BrickletRS485.modbusMasterWriteSingleCoil(slaveAddress, coilAddress, coilValue[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] coilAddress – Type: int, Range: [1 to 2¹⁶] coilValue – Type: boolean
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to write a single coil of a slave. This function creates a Modbus function code 5 request.

Slave Address: Address of the target Modbus slave.
Coil Address: Number of the coil to be written. For backwards compatibility reasons, this parameter is called Starting Address. It is not an address, but instead a coil number in the range of 1 to 65536.
Coil Value: Value to be written.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_WRITE_SINGLE_COIL_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.modbusSlaveAnswerWriteSingleRegisterRequest(requestID[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255]
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to write a single register.

Request ID: Request ID of the corresponding request that is being answered.

This function must be called from the CALLBACK_MODBUS_SLAVE_WRITE_SINGLE_REGISTER_REQUEST callback with the Request ID, Register Address and Register Value as provided by the arguments of the callback.

BrickletRS485.modbusMasterWriteSingleRegister(slaveAddress, registerAddress, registerValue[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] registerAddress – Type: int, Range: [1 to 2¹⁶] registerValue – Type: int, Range: [0 to 2¹⁶ - 1]
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to write a single holding register of a slave. This function creates a Modbus function code 6 request.

Slave Address: Address of the target Modbus slave.
Register Address: Number of the holding register to be written. For backwards compatibility reasons, this parameter is called Starting Address. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is implicit and must be omitted.
Register Value: Value to be written.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_WRITE_SINGLE_REGISTER_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.modbusSlaveAnswerWriteMultipleCoilsRequest(requestID[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255]
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to write multiple coils.

Request ID: Request ID of the corresponding request that is being answered.

This function must be called from the CALLBACK_MODBUS_SLAVE_WRITE_MULTIPLE_COILS_REQUEST callback with the Request ID of the callback.

BrickletRS485.modbusMasterWriteMultipleCoils(slaveAddress, startingAddress, coils[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] startingAddress – Type: int, Range: [1 to 2¹⁶] coils – Type: [boolean, ...], Length: variable
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to write multiple coils of a slave. This function creates a Modbus function code 15 request.

Slave Address: Address of the target Modbus slave.
Starting Address: Number of the first coil to write. For backwards compatibility reasons, this parameter is called Starting Address.It is not an address, but instead a coil number in the range of 1 to 65536.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_WRITE_MULTIPLE_COILS_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.modbusSlaveAnswerWriteMultipleRegistersRequest(requestID[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255]
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to write multiple registers.

Request ID: Request ID of the corresponding request that is being answered.

This function must be called from the CALLBACK_MODBUS_SLAVE_WRITE_MULTIPLE_REGISTERS_REQUEST callback with the Request ID of the callback.

BrickletRS485.modbusMasterWriteMultipleRegisters(slaveAddress, startingAddress, registers[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] startingAddress – Type: int, Range: [1 to 2¹⁶] registers – Type: [int, ...], Length: variable, Range: [0 to 2¹⁶ - 1]
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to write multiple registers of a slave. This function creates a Modbus function code 16 request.

Slave Address: Address of the target Modbus slave.
Starting Address: Number of the first holding register to write. For backwards compatibility reasons, this parameter is called Starting Address. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is implicit and must be omitted.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_WRITE_MULTIPLE_REGISTERS_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.modbusSlaveAnswerReadDiscreteInputsRequest(requestID, discreteInputs[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255] discreteInputs – Type: [boolean, ...], Length: variable
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to read discrete inputs.

Request ID: Request ID of the corresponding request that is being answered.
Discrete Inputs: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the CALLBACK_MODBUS_SLAVE_READ_DISCRETE_INPUTS_REQUEST callback with the Request ID as provided by the argument of the callback.

BrickletRS485.modbusMasterReadDiscreteInputs(slaveAddress, startingAddress, count[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 2000]
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to read discrete inputs from a slave. This function creates a Modbus function code 2 request.

Slave Address: Address of the target Modbus slave.
Starting Address: Number of the first discrete input to read. For backwards compatibility reasons, this parameter is called Starting Address. It is not an address, but instead a discrete input number in the range of 1 to 65536. The prefix digit 1 (for discrete input) is implicit and must be omitted.
Count: Number of discrete inputs to read.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_READ_DISCRETE_INPUTS_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.modbusSlaveAnswerReadInputRegistersRequest(requestID, inputRegisters[, returnCallback][, errorCallback])¶

Parameters:	requestID – Type: int, Range: [0 to 255] inputRegisters – Type: [int, ...], Length: variable, Range: [0 to 2¹⁶ - 1]
Callback Parameters:	undefined
Returns:	undefined

In Modbus slave mode this function can be used to answer a master request to read input registers.

Request ID: Request ID of the corresponding request that is being answered.
Input Registers: Data that is to be sent to the Modbus master for the corresponding request.

This function must be called from the CALLBACK_MODBUS_SLAVE_READ_INPUT_REGISTERS_REQUEST callback with the Request ID as provided by the argument of the callback.

BrickletRS485.modbusMasterReadInputRegisters(slaveAddress, startingAddress, count[, returnCallback][, errorCallback])¶

Parameters:	slaveAddress – Type: int, Range: [0 to 247] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 125]
Callback Parameters:	requestID – Type: int, Range: [0 to 255]
Returns:	undefined

In Modbus master mode this function can be used to read input registers from a slave. This function creates a Modbus function code 4 request.

Slave Address: Address of the target Modbus slave.
Starting Address: Number of the first input register to read. For backwards compatibility reasons, this parameter is called Starting Address. It is not an address, but instead an input register number in the range of 1 to 65536. The prefix digit 3 (for input register) is implicit and must be omitted.
Count: Number of input registers to read.

Upon success the function will return a non-zero request ID which will represent the current request initiated by the Modbus master. In case of failure the returned request ID will be 0.

When successful this function will also invoke the CALLBACK_MODBUS_MASTER_READ_INPUT_REGISTERS_RESPONSE callback. In this callback the Request ID provided by the callback argument must be matched with the Request ID returned from this function to verify that the callback is indeed for a particular request.

BrickletRS485.getSPITFPErrorCount([returnCallback][, errorCallback])¶

Callback Parameters:	errorCountAckChecksum – Type: int, Range: [0 to 2³² - 1] errorCountMessageChecksum – Type: int, Range: [0 to 2³² - 1] errorCountFrame – Type: int, Range: [0 to 2³² - 1] errorCountOverflow – Type: int, Range: [0 to 2³² - 1]
Returns:	undefined

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 Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.

BrickletRS485.setStatusLEDConfig(config[, returnCallback][, errorCallback])¶

Parameters:	config – Type: int, Range: See constants, Default: 3
Callback Parameters:	undefined
Returns:	undefined

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 constants are available for this function:

For config:

BrickletRS485.STATUS_LED_CONFIG_OFF = 0
BrickletRS485.STATUS_LED_CONFIG_ON = 1
BrickletRS485.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletRS485.STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletRS485.getStatusLEDConfig([returnCallback][, errorCallback])¶

Callback Parameters:	config – Type: int, Range: See constants, Default: 3
Returns:	undefined

Returns the configuration as set by setStatusLEDConfig()

The following constants are available for this function:

For config:

BrickletRS485.STATUS_LED_CONFIG_OFF = 0
BrickletRS485.STATUS_LED_CONFIG_ON = 1
BrickletRS485.STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
BrickletRS485.STATUS_LED_CONFIG_SHOW_STATUS = 3

BrickletRS485.getChipTemperature([returnCallback][, errorCallback])¶

Callback Parameters:	temperature – Type: int, Unit: 1 °C, Range: [-2¹⁵ to 2¹⁵ - 1]
Returns:	undefined

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.

BrickletRS485.reset([returnCallback][, errorCallback])¶

Callback Parameters:	undefined
Returns:	undefined

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!

BrickletRS485.getIdentity([returnCallback][, errorCallback])¶

Callback Parameters:

Callback Parameters:	uid – Type: string, Length: up to 8 connectedUid – Type: string, Length: up to 8 position – Type: char, Range: ['a' to 'h', 'z'] hardwareVersion – Type: [int, ...], Length: 3 0: major – Type: int, Range: [0 to 255] 1: minor – Type: int, Range: [0 to 255] 2: revision – Type: int, Range: [0 to 255] firmwareVersion – Type: [int, ...], Length: 3 0: major – Type: int, Range: [0 to 255] 1: minor – Type: int, Range: [0 to 255] 2: revision – Type: int, Range: [0 to 255] deviceIdentifier – Type: int, Range: [0 to 2¹⁶ - 1]
Returns:	undefined

uid – Type: string, Length: up to 8
connectedUid – Type: string, Length: up to 8
position – Type: char, Range: ['a' to 'h', 'z']
hardwareVersion – Type: [int, ...], Length: 3

0: major – Type: int, Range: [0 to 255]
1: minor – Type: int, Range: [0 to 255]
2: revision – Type: int, Range: [0 to 255]

firmwareVersion – Type: [int, ...], Length: 3

0: major – Type: int, Range: [0 to 255]
1: minor – Type: int, Range: [0 to 255]
2: revision – Type: int, Range: [0 to 255]

deviceIdentifier – Type: int, Range: [0 to 2¹⁶ - 1]

Returns:

undefined

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. There is also a constant for the device identifier of this Bricklet.

Callback Configuration Functions¶

BrickletRS485.on(callback_id, function[, errorCallback])¶

Parameters:	callback_id – Type: int function – Type: function
Returns:	undefined

Registers the given function with the given callback_id.

The available callback IDs with corresponding function signatures are listed below.

BrickletRS485.enableReadCallback([returnCallback][, errorCallback])¶

Callback Parameters:	undefined
Returns:	undefined

Enables the CALLBACK_READ callback. This will disable the CALLBACK_FRAME_READABLE callback.

By default the callback is disabled.

BrickletRS485.disableReadCallback([returnCallback][, errorCallback])¶

Callback Parameters:	undefined
Returns:	undefined

Disables the CALLBACK_READ callback.

By default the callback is disabled.

BrickletRS485.isReadCallbackEnabled([returnCallback][, errorCallback])¶

Callback Parameters:	enabled – Type: boolean, Default: false
Returns:	undefined

Returns true if the CALLBACK_READ callback is enabled, false otherwise.

BrickletRS485.enableErrorCountCallback([returnCallback][, errorCallback])¶

Callback Parameters:	undefined
Returns:	undefined

Enables the CALLBACK_ERROR_COUNT callback.

By default the callback is disabled.

BrickletRS485.disableErrorCountCallback([returnCallback][, errorCallback])¶

Callback Parameters:	undefined
Returns:	undefined

Disables the CALLBACK_ERROR_COUNT callback.

By default the callback is disabled.

BrickletRS485.isErrorCountCallbackEnabled([returnCallback][, errorCallback])¶

Callback Parameters:	enabled – Type: boolean, Default: true
Returns:	undefined

Returns true if the CALLBACK_ERROR_COUNT callback is enabled, false otherwise.

BrickletRS485.setFrameReadableCallbackConfiguration(frameSize[, returnCallback][, errorCallback])¶

Parameters:	frameSize – Type: int, Unit: 1 B, Range: [0 to 9216], Default: 0
Callback Parameters:	undefined
Returns:	undefined

Configures the CALLBACK_FRAME_READABLE callback. The frame size is the number of bytes, that have to be readable to trigger the callback. A frame size of 0 disables the callback. A frame size greater than 0 enables the callback and disables the CALLBACK_READ callback.

By default the callback is disabled.

New in version 2.0.5 (Plugin).

BrickletRS485.getFrameReadableCallbackConfiguration([returnCallback][, errorCallback])¶

Callback Parameters:	frameSize – Type: int, Unit: 1 B, Range: [0 to 9216], Default: 0
Returns:	undefined

Returns the callback configuration as set by setFrameReadableCallbackConfiguration().

New in version 2.0.5 (Plugin).

Callbacks¶

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the on() function of the device object. The first parameter is the callback ID and the second parameter the callback function:

rs485.on(BrickletRS485.CALLBACK_EXAMPLE,
    function (param) {
        console.log(param);
    }
);

The available constants with inherent number and type of parameters are described below.

Note

Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.

BrickletRS485.CALLBACK_READ¶

Callback Parameters:	message – Type: [char, ...], Length: variable

This callback is called if new data is available.

To enable this callback, use enableReadCallback().

Note

If reconstructing the value fails, the callback is triggered with null for message.

BrickletRS485.CALLBACK_ERROR_COUNT¶

Callback Parameters:	overrunErrorCount – Type: int, Range: [0 to 2³² - 1] parityErrorCount – Type: int, Range: [0 to 2³² - 1]

This callback is called if a new error occurs. It returns the current overrun and parity error count.

BrickletRS485.CALLBACK_MODBUS_SLAVE_READ_COILS_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 2000]

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read coils. The parameters are request ID of the request, the number of the first coil to be read and the number of coils to be read as received by the request. The number of the first coil is called starting address for backwards compatibility reasons. It is not an address, but instead a coil number in the range of 1 to 65536.

To send a response of this request use modbusSlaveAnswerReadCoilsRequest().

BrickletRS485.CALLBACK_MODBUS_MASTER_READ_COILS_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants coils – Type: [boolean, ...], Length: variable

This callback is called only in Modbus master mode when the master receives a valid response of a request to read coils.

The parameters are request ID of the request, exception code of the response and the data as received by the response.

Any non-zero exception code indicates a problem. If the exception code is greater than 0 then the number represents a Modbus exception code. If it is less than 0 then it represents other errors. For example, -1 indicates that the request timed out or that the master did not receive any valid response of the request within the master request timeout period as set by setModbusConfiguration().

Note

If reconstructing the value fails, the callback is triggered with null for coils.

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_MODBUS_SLAVE_READ_HOLDING_REGISTERS_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 125]

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read holding registers. The parameters are request ID of the request, the number of the first holding register to be read and the number of holding registers to be read as received by the request. The number of the first holding register is called starting address for backwards compatibility reasons. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is omitted.

To send a response of this request use modbusSlaveAnswerReadHoldingRegistersRequest().

BrickletRS485.CALLBACK_MODBUS_MASTER_READ_HOLDING_REGISTERS_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants holdingRegisters – Type: [int, ...], Length: variable, Range: [0 to 2¹⁶ - 1]

This callback is called only in Modbus master mode when the master receives a valid response of a request to read holding registers.

The parameters are request ID of the request, exception code of the response and the data as received by the response.

Note

If reconstructing the value fails, the callback is triggered with null for holdingRegisters.

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_MODBUS_SLAVE_WRITE_SINGLE_COIL_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] coilAddress – Type: int, Range: [1 to 2¹⁶] coilValue – Type: boolean

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write a single coil. The parameters are request ID of the request, the number of the coil and the value of coil to be written as received by the request. The number of the coil is called coil address for backwards compatibility reasons. It is not an address, but instead a coil number in the range of 1 to 65536.

To send a response of this request use modbusSlaveAnswerWriteSingleCoilRequest().

BrickletRS485.CALLBACK_MODBUS_MASTER_WRITE_SINGLE_COIL_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants

This callback is called only in Modbus master mode when the master receives a valid response of a request to write a single coil.

The parameters are request ID of the request and exception code of the response.

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_MODBUS_SLAVE_WRITE_SINGLE_REGISTER_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] registerAddress – Type: int, Range: [1 to 2¹⁶] registerValue – Type: int, Range: [0 to 2¹⁶ - 1]

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write a single holding register. The parameters are request ID of the request, the number of the holding register and the register value to be written as received by the request. The number of the holding register is called starting address for backwards compatibility reasons. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is omitted.

To send a response of this request use modbusSlaveAnswerWriteSingleRegisterRequest().

BrickletRS485.CALLBACK_MODBUS_MASTER_WRITE_SINGLE_REGISTER_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants

This callback is called only in Modbus master mode when the master receives a valid response of a request to write a single register.

The parameters are request ID of the request and exception code of the response.

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_MODBUS_SLAVE_WRITE_MULTIPLE_COILS_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] startingAddress – Type: int, Range: [1 to 2¹⁶] coils – Type: [boolean, ...], Length: variable

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write multiple coils. The parameters are request ID of the request, the number of the first coil and the data to be written as received by the request. The number of the first coil is called starting address for backwards compatibility reasons. It is not an address, but instead a coil number in the range of 1 to 65536.

To send a response of this request use modbusSlaveAnswerWriteMultipleCoilsRequest().

Note

If reconstructing the value fails, the callback is triggered with null for coils.

BrickletRS485.CALLBACK_MODBUS_MASTER_WRITE_MULTIPLE_COILS_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants

This callback is called only in Modbus master mode when the master receives a valid response of a request to read coils.

The parameters are request ID of the request and exception code of the response.

Any non-zero exception code indicates a problem. If the exception code is greater than 0 then the number represents a Modbus exception code. If it is less than 0 then it represents other errors. For example, -1 indicates that the request timedout or that the master did not receive any valid response of the request within the master request timeout period as set by setModbusConfiguration().

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_MODBUS_SLAVE_WRITE_MULTIPLE_REGISTERS_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] startingAddress – Type: int, Range: [1 to 2¹⁶] registers – Type: [int, ...], Length: variable, Range: [0 to 2¹⁶ - 1]

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to write multiple holding registers. The parameters are request ID of the request, the number of the first holding register and the data to be written as received by the request. The number of the first holding register is called starting address for backwards compatibility reasons. It is not an address, but instead a holding register number in the range of 1 to 65536. The prefix digit 4 (for holding register) is omitted.

To send a response of this request use modbusSlaveAnswerWriteMultipleRegistersRequest().

Note

If reconstructing the value fails, the callback is triggered with null for registers.

BrickletRS485.CALLBACK_MODBUS_MASTER_WRITE_MULTIPLE_REGISTERS_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants

This callback is called only in Modbus master mode when the master receives a valid response of a request to write multiple registers.

The parameters are request ID of the request and exception code of the response.

Any non-zero exception code indicates a problem. If the exception code is greater than 0 then the number represents a Modbus exception code. If it is less than 0 then it represents other errors. For example, -1 indicates that the request timedout or that the master did not receive any valid response of the request within the master request timeout period as set by setModbusConfiguration().

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_MODBUS_SLAVE_READ_DISCRETE_INPUTS_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 2000]

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read discrete inputs. The parameters are request ID of the request, the number of the first discrete input and the number of discrete inputs to be read as received by the request. The number of the first discrete input is called starting address for backwards compatibility reasons. It is not an address, but instead a discrete input number in the range of 1 to 65536. The prefix digit 1 (for discrete input) is omitted.

To send a response of this request use modbusSlaveAnswerReadDiscreteInputsRequest().

BrickletRS485.CALLBACK_MODBUS_MASTER_READ_DISCRETE_INPUTS_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants discreteInputs – Type: [boolean, ...], Length: variable

This callback is called only in Modbus master mode when the master receives a valid response of a request to read discrete inputs.

The parameters are request ID of the request, exception code of the response and the data as received by the response.

Any non-zero exception code indicates a problem. If the exception code is greater than 0 then the number represents a Modbus exception code. If it is less than 0 then it represents other errors. For example, -1 indicates that the request timedout or that the master did not receive any valid response of the request within the master request timeout period as set by setModbusConfiguration().

Note

If reconstructing the value fails, the callback is triggered with null for discreteInputs.

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_MODBUS_SLAVE_READ_INPUT_REGISTERS_REQUEST¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] startingAddress – Type: int, Range: [1 to 2¹⁶] count – Type: int, Range: [1 to 125]

This callback is called only in Modbus slave mode when the slave receives a valid request from a Modbus master to read input registers. The parameters are request ID of the request, the number of the first input register and the number of input registers to be read as received by the request. The number of the first input register is called starting address for backwards compatibility reasons. It is not an address, but instead a input register number in the range of 1 to 65536. The prefix digit 3 (for input register) is omitted.

To send a response of this request use modbusSlaveAnswerReadInputRegistersRequest().

BrickletRS485.CALLBACK_MODBUS_MASTER_READ_INPUT_REGISTERS_RESPONSE¶

Callback Parameters:	requestID – Type: int, Range: [0 to 255] exceptionCode – Type: int, Range: See constants inputRegisters – Type: [int, ...], Length: variable, Range: [0 to 2¹⁶ - 1]

This callback is called only in Modbus master mode when the master receives a valid response of a request to read input registers.

The parameters are request ID of the request, exception code of the response and the data as received by the response.

Any non-zero exception code indicates a problem. If the exception code is greater than 0 then the number represents a Modbus exception code. If it is less than 0 then it represents other errors. For example, -1 indicates that the request timedout or that the master did not receive any valid response of the request within the master request timeout period as set by setModbusConfiguration().

Note

If reconstructing the value fails, the callback is triggered with null for inputRegisters.

The following constants are available for this function:

For exception_code:

BrickletRS485.EXCEPTION_CODE_TIMEOUT = -1
BrickletRS485.EXCEPTION_CODE_SUCCESS = 0
BrickletRS485.EXCEPTION_CODE_ILLEGAL_FUNCTION = 1
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_ADDRESS = 2
BrickletRS485.EXCEPTION_CODE_ILLEGAL_DATA_VALUE = 3
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_FAILURE = 4
BrickletRS485.EXCEPTION_CODE_ACKNOWLEDGE = 5
BrickletRS485.EXCEPTION_CODE_SLAVE_DEVICE_BUSY = 6
BrickletRS485.EXCEPTION_CODE_MEMORY_PARITY_ERROR = 8
BrickletRS485.EXCEPTION_CODE_GATEWAY_PATH_UNAVAILABLE = 10
BrickletRS485.EXCEPTION_CODE_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 11

BrickletRS485.CALLBACK_FRAME_READABLE¶

Callback Parameters:	frameCount – Type: int, Range: [0 to 2¹⁶ - 1]

This callback is called if at least one frame of data is readable. The frame size is configured with setFrameReadableCallbackConfiguration(). The frame count parameter is the number of frames that can be read. This callback is triggered only once until read() is called. This means, that if you have configured a frame size of X bytes, you can read exactly X bytes using the read() function, every time the callback triggers without checking the frame count parameter.

New in version 2.0.5 (Plugin).

Virtual Functions¶

Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.

BrickletRS485.getAPIVersion()¶

Returns:	apiVersion – Type: [int, ...], Length: 3 0: major – Type: int, Range: [0 to 255] 1: minor – Type: int, Range: [0 to 255] 2: revision – Type: int, Range: [0 to 255]

Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.

BrickletRS485.getResponseExpected(functionId[, errorCallback])¶

Parameters:	functionId – Type: int, Range: See constants
Returns:	responseExpected – Type: boolean

Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.

For getter functions this is enabled by default and cannot be disabled, because those functions will always send a response. For callback configuration functions it is enabled by default too, but can be disabled by setResponseExpected(). For setter functions it is disabled by default and can be enabled.

Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.

The following constants are available for this function:

For function_id:

BrickletRS485.FUNCTION_ENABLE_READ_CALLBACK = 3
BrickletRS485.FUNCTION_DISABLE_READ_CALLBACK = 4
BrickletRS485.FUNCTION_SET_RS485_CONFIGURATION = 6
BrickletRS485.FUNCTION_SET_MODBUS_CONFIGURATION = 8
BrickletRS485.FUNCTION_SET_MODE = 10
BrickletRS485.FUNCTION_SET_COMMUNICATION_LED_CONFIG = 12
BrickletRS485.FUNCTION_SET_ERROR_LED_CONFIG = 14
BrickletRS485.FUNCTION_SET_BUFFER_CONFIG = 16
BrickletRS485.FUNCTION_ENABLE_ERROR_COUNT_CALLBACK = 19
BrickletRS485.FUNCTION_DISABLE_ERROR_COUNT_CALLBACK = 20
BrickletRS485.FUNCTION_MODBUS_SLAVE_REPORT_EXCEPTION = 24
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_COILS_REQUEST = 25
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_HOLDING_REGISTERS_REQUEST = 27
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_COIL_REQUEST = 29
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_REGISTER_REQUEST = 31
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_COILS_REQUEST = 33
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_REGISTERS_REQUEST = 35
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_DISCRETE_INPUTS_REQUEST = 37
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_INPUT_REGISTERS_REQUEST = 39
BrickletRS485.FUNCTION_SET_FRAME_READABLE_CALLBACK_CONFIGURATION = 59
BrickletRS485.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
BrickletRS485.FUNCTION_SET_STATUS_LED_CONFIG = 239
BrickletRS485.FUNCTION_RESET = 243
BrickletRS485.FUNCTION_WRITE_UID = 248

BrickletRS485.setResponseExpected(functionId, responseExpected[, errorCallback])¶

Parameters:	functionId – Type: int, Range: See constants responseExpected – Type: boolean
Returns:	undefined

Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.

The following constants are available for this function:

For function_id:

BrickletRS485.FUNCTION_ENABLE_READ_CALLBACK = 3
BrickletRS485.FUNCTION_DISABLE_READ_CALLBACK = 4
BrickletRS485.FUNCTION_SET_RS485_CONFIGURATION = 6
BrickletRS485.FUNCTION_SET_MODBUS_CONFIGURATION = 8
BrickletRS485.FUNCTION_SET_MODE = 10
BrickletRS485.FUNCTION_SET_COMMUNICATION_LED_CONFIG = 12
BrickletRS485.FUNCTION_SET_ERROR_LED_CONFIG = 14
BrickletRS485.FUNCTION_SET_BUFFER_CONFIG = 16
BrickletRS485.FUNCTION_ENABLE_ERROR_COUNT_CALLBACK = 19
BrickletRS485.FUNCTION_DISABLE_ERROR_COUNT_CALLBACK = 20
BrickletRS485.FUNCTION_MODBUS_SLAVE_REPORT_EXCEPTION = 24
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_COILS_REQUEST = 25
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_HOLDING_REGISTERS_REQUEST = 27
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_COIL_REQUEST = 29
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_SINGLE_REGISTER_REQUEST = 31
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_COILS_REQUEST = 33
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_WRITE_MULTIPLE_REGISTERS_REQUEST = 35
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_DISCRETE_INPUTS_REQUEST = 37
BrickletRS485.FUNCTION_MODBUS_SLAVE_ANSWER_READ_INPUT_REGISTERS_REQUEST = 39
BrickletRS485.FUNCTION_SET_FRAME_READABLE_CALLBACK_CONFIGURATION = 59
BrickletRS485.FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
BrickletRS485.FUNCTION_SET_STATUS_LED_CONFIG = 239
BrickletRS485.FUNCTION_RESET = 243
BrickletRS485.FUNCTION_WRITE_UID = 248

BrickletRS485.setResponseExpectedAll(responseExpected)¶

Parameters:	responseExpected – Type: boolean
Returns:	undefined

Changes the response expected flag for all setter and callback configuration functions of this device at once.

Internal Functions¶

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.

BrickletRS485.setBootloaderMode(mode[, returnCallback][, errorCallback])¶

Parameters:	mode – Type: int, Range: See constants
Callback Parameters:	status – Type: int, Range: See constants
Returns:	undefined

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 constants are available for this function:

For mode:

BrickletRS485.BOOTLOADER_MODE_BOOTLOADER = 0
BrickletRS485.BOOTLOADER_MODE_FIRMWARE = 1
BrickletRS485.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

For status:

BrickletRS485.BOOTLOADER_STATUS_OK = 0
BrickletRS485.BOOTLOADER_STATUS_INVALID_MODE = 1
BrickletRS485.BOOTLOADER_STATUS_NO_CHANGE = 2
BrickletRS485.BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
BrickletRS485.BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
BrickletRS485.BOOTLOADER_STATUS_CRC_MISMATCH = 5

BrickletRS485.getBootloaderMode([returnCallback][, errorCallback])¶

Callback Parameters:	mode – Type: int, Range: See constants
Returns:	undefined

Returns the current bootloader mode, see setBootloaderMode().

The following constants are available for this function:

For mode:

BrickletRS485.BOOTLOADER_MODE_BOOTLOADER = 0
BrickletRS485.BOOTLOADER_MODE_FIRMWARE = 1
BrickletRS485.BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
BrickletRS485.BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4

BrickletRS485.setWriteFirmwarePointer(pointer[, returnCallback][, errorCallback])¶

Parameters:	pointer – Type: int, Unit: 1 B, Range: [0 to 2³² - 1]
Callback Parameters:	undefined
Returns:	undefined

Sets the firmware pointer for writeFirmware(). 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.

BrickletRS485.writeFirmware(data[, returnCallback][, errorCallback])¶

Parameters:	data – Type: [int, ...], Length: 64, Range: [0 to 255]
Callback Parameters:	status – Type: int, Range: [0 to 255]
Returns:	undefined

Writes 64 Bytes of firmware at the position as written by setWriteFirmwarePointer() 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.

BrickletRS485.writeUID(uid[, returnCallback][, errorCallback])¶

Parameters:	uid – Type: int, Range: [0 to 2³² - 1]
Callback Parameters:	undefined
Returns:	undefined

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.

BrickletRS485.readUID([returnCallback][, errorCallback])¶

Callback Parameters:	uid – Type: int, Range: [0 to 2³² - 1]
Returns:	undefined

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

Constants¶

BrickletRS485.DEVICE_IDENTIFIER¶

This constant is used to identify a RS485 Bricklet.

The getIdentity() function and the IPConnection.CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.

BrickletRS485.DEVICE_DISPLAY_NAME¶: This constant represents the human readable name of a RS485 Bricklet.