The module is intended for use in control and recording systems, digital signal processing systems with high demands on speed, volume of processed data, reliability and fault tolerance as a universal data converter RS-485 (ModBus-RTU) and CAN 2.0V
- bidirectional communication between two RS-485 interfaces and one CAN.
- data exchange between two RS-485 interfaces and one CAN via certain ModBus registers (ModBus RTU protocol).
- in RS-485 networks, the module is a slave.
- in RS-485 networks, the possibility of writing and reading up to 64 ModBus registers in one message is realized.
- transmission of up to 16 CAN messages having different identifiers to the CAN simultaneously and an unlimited number of CAN messages transmitted consecutively one after another.
- Receive from the CAN network up to 28 CAN messages with different identifiers.
- CANopen is implemented in the CAN network (in this case the module is a master, receiving messages synchronous) and other messaging protocols (for example CAN BUS protocol).
- in the CAN network, the standard identifiers 2.0A and 2.0B are used.
- For the CANopen protocol, communication control with the connected modules is implemented.
- the configuration of the exchange parameters is possible as a special software supplied with the module, as well as other programs using the ModBus RTU protocol via one of the RS-485 interface modules.
- saving the configuration of the exchange parameters in the module’s non-volatile memory.
- galvanic isolation on all interfaces.
- processor type: microcontroller C8051F061 (Silicon Laboratories).
- the processor clock speed is 24 MHz.
- the amount of internal ROM (Flash) — 64 KB.
- the amount of internal RAM (RAM) is 4352 bytes.
- data bus width is 16.
- the address bus is 16.
|Supply voltage||18 ... 36 V
(rated voltage 24 V)
|Power consumption, W, not more than||5|
|Electrical insulation resistance of galvanically isolated circuits between themselves and relatively galvanically isolated circuits||At least 40 MΩ at a voltage of 500 V DC|
|Galvanically isolated||RS-485 – 2 pc.|
|Galvanicheki insulated||CAN 2.0B – 1 pc.|
|Degree of housing protection||IP20|
|Overall dimensions, mm||100х22,5х115|
|Weight, kg, no more than||0,2|
|Installation||To DIN rail|
|Average service life, years, not less than||20|
Connection to the contacts of the module by plugs with spring terminals type FKCT 2,5 / 4-ST from PHOENIX CONTACT (it is allowed to connect single-core and stranded wires with a cross section from 0.2 to 2.5 mm2). The necessity of completing the module with plugs is specified when ordering.
To connect a CAN termination resistor, a jumper must be installed between pins 6 and 7.
To connect a RS-485-1 resistor, a jumper must be installed between pins 14 and 15.
To connect a RS-485-2 resistor, a jumper must be installed between pins 10 and 11.
Connectivity to the exchange network via two RS-485 and one
Example of a network connection using the CANopen protocol:
An example of connecting to a CAN network for normal exchange or listening mode:
To configure and configure the exchange parameters, free software is used. This software is fully Russified and every user action is accompanied by detailed prompts. The software comes with a module and is freely available on the site.
The software is installed on the computer. It requires a computer to be connected to one (any) RS-485 interface (any converter, for example, USB-RS485) can be used to interface the module and the computer.
The configuration program allows you to:
- change parameters of two RS-485 interfaces by ModBus (network address, speed, parity, number of stop bits for each interface);
- change the CAN speed;
- identify the identifiers of received and transmitted CAN messages;
- determine when using the CANopen protocol SDO table indices for the CAN messages received by the module;
- Save the configuration of 12 received and 2 transmitted CAN messages in the module’s non-volatile memory.
The configuration program allows you to perform in real time:
- Monitoring of ModBus registers, which are filled with data of messages received from CAN;
- Filling ModBus registers with data for transmission to CAN messages;
- Generation and transmission to the CAN network of any number of operational messages by entering identifier and data into certain ModBus registers (after the message is transmitted these registers are discarded and the next operative message can be transmitted);
- Control the number of messages received via CAN.