Difference between revisions of "Using BiSS encoder"
[checked revision] | [checked revision] |
(Tag: VisualEditor) |
|||
Line 19: | Line 19: | ||
* No data CRC verification. Suggested workaround is to apply sensible tracking error limits. | * No data CRC verification. Suggested workaround is to apply sensible tracking error limits. | ||
* No daisy chaining encoders is supported. Only one encoder may be connected to a drive. | * No daisy chaining encoders is supported. Only one encoder may be connected to a drive. | ||
− | * No cable delay compensation implemented. Less than 5 meter cable is recommended | + | * No cable delay compensation implemented. Less than 5 meter cable is recommended. |
== List of tested BiSS encoders: == | == List of tested BiSS encoders: == |
Latest revision as of 18:05, 12 January 2021
BiSS Interface is an open standard used by many encoder feedback device manufacturers. IONI Pro servo drive supports BiSS encoders starting from firmware version 1.6.0.
Contents
BiSS support details[edit | edit source]
As BiSS is quite wide standard supporting large number of different setups and device types, it is important to acknowledge the properties BiSS interface in GD drives. In current firmware, following properties apply:
- Support BiSS B and BiSS C devices
- Read of multi-turn (MT) and single-turn (SD) data from encoder
- Resolution
- Single-turn resolution from 6 to 30 bits (however, higher than 30 bit resolution is still compatible, lowest bits are just ignored)
- Multi-turn resolution from 0 to 16 bits
- The sum of ST+MT bits must be between 6 and 32 bits
- Error detection by the means of
- No response from encoder. Drive sets timeout or loss of connection error if encoder does not respond with a "start bit" in 20 µs.
- Bit transfer error occurred causing large position jump to trigger tracking error
- Clock rate 5.1 MHz
- Support utilizing absolute position information from the encoder
- To skip axis homing procedure
- To initialize rotary motor immediately (no Phasing needed)
Current firmware version limitations:
- No data CRC verification. Suggested workaround is to apply sensible tracking error limits.
- No daisy chaining encoders is supported. Only one encoder may be connected to a drive.
- No cable delay compensation implemented. Less than 5 meter cable is recommended.
List of tested BiSS encoders:[edit | edit source]
Manufacturer | Model | Notes | Test result |
---|---|---|---|
RLS | Orbis BR10DCA14B12BD00 | 14 bits absolute (no multiturn data) | All OK |
Hengstler | AD36/1219AF.0XBI0:5653 | 19 bits absolute encoder with 12 bits multi turn | All OK |
Renishaw | Resolute RL32BAS001C30F | 32 bits absolute encoder | All OK |
Baumer | EFL360 - BL6.2M6B.21000.4 | 21 bits absolute encoder (no multiturn data) | All OK |
If you have tested another kind of encoder, please help us to inform the community by letting us know your encoder model and result by dropping a message into Granite Devices support.
SimuCUBE supports BiSS encoder resolutions up to 21 bits (2M counts/rev). |
Wiring BiSS encoder[edit | edit source]
BiSS encoder typically has 6 mandatory wires consisting:
- Power supply lines (2 wires)
- Clock input (2 wires)
- Data output (2 wires)
Connection to IONI Pro drive by following table:
BiSS wire | IONI drive pin | IONICUBE D-Sub 15 pin number | Remarks |
---|---|---|---|
Cable shield | Connector shell | ||
GND | GND | 10 | |
5V input | 9 | Pin 9 is 5V supply output from IONICUBE to encoder | |
Clock+ / MA+ | GPI2 | 12 | |
Clock- / MA- | GPI3 | 11 | |
Data+ / SLO+ | C+ | 15 | |
Data- / SLO- | C- | 14 |
Refer to IONI & IONICUBE user guide for more info on wiring encoders.
Cable termination resistors may be necessary for reliable operation, for more details, see Terminating differential encoder lines. |
Configuration[edit | edit source]
To configure BiSS, use Granity version 1.11.0 or later. Configuration steps: