Overview
The SDM-SIO2R is a digital sensor expansion module that expands the serial I/O interface via Synchronous Device for Measurement (SDM) communications on a data logger. The serial I/O functionality is identical to the SDM-SIO1A One-Channel Serial I/O Module and the SDM-SIO4A Four-Channel Serial I/O Module, except it has two channels. The SDM-SIO2R also has terminals to connect sensor power and sensor heater power, which are controllable via the SDMGeneric instruction in CRBasic.
Read MoreBenefits and Features
- Hot swappable in the field
- Modular design
- Expandable as needed
- Removable terminals
- Power control ability for each individual sensor
Images
Technical Description
The SDM-SIO2R features a connector bus system that connects multiple SDM-SIO2R modules on a DIN rail without having to wire each individual unit. C1, C2, C3, 12V, V+, and G are all bussed between multiple units, making it easy to expand sensor count. Up to eight units can be bussed together with up to 15 sensors. This is the maximum number of SDM addresses available.
Specifications
| Function | Expands the serial I/O interface via Synchronous Device for Measurement (SDM) communications on a data logger |
| Number of Channels | 2 |
| Supported Data Rates | 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200 bits/s |
| Supported Modes of Operation |
|
| Supported Data Formats |
8, seven-bit data size*; none, odd or even parity; one or two stops bits *In seven-bit mode with no parity, the user must ensure that the characters received by the SDM-SIO2R have a delay of at least one bit period between them. This does not affect any other configuration and does not affect transmissions out of the SDM-SIO2R. |
| Auto Baud Rate Detection | Not supported |
| PakBus Communications | Use of the serial port for general PakBus communications is not currently supported. |
| Operating Voltage |
|
| Operating Temperature | -40° to +70°C |
| Standard Humidity Range | 0 to 95% (non-condensing) |
| Dimensions | 133.35 x 76.2 x 19.05 mm (5.25 x 3 x 0.75 in.) |
| Weight | 108.5 g (3.8 oz) |
Buffer Sizes |
|
| -NOTE- | Both transmit and receive buffers are fill and discard type. That is, after the buffers become full, no new information is accepted. All further data is discarded until space is made when the data logger requests data from the SDM-SIO2R. |
| Transmit Buffer Size | 767 bytes (buffer from the data logger to the sensor) |
| Receive Buffer Size | 6143 bytes (buffer from the sensor to the data logger) |
Current Consumption |
|
| Standby Current (12V & V+ ON) |
|
| Standby Current (12V & V+ OFF) |
|
Compatibility
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
Dataloggers
| Product | Compatible | Note |
|---|---|---|
| CR1000 (retired) | ||
| CR1000X | ||
| CR200X (retired) | ||
| CR211X (retired) | ||
| CR216X (retired) | ||
| CR300 | ||
| CR3000 (retired) | ||
| CR310 | ||
| CR350 | ||
| CR5000 (retired) | ||
| CR6 | ||
| CR800 (retired) | ||
| CR800 (retired) | ||
| CR850 (retired) | ||
| CR850 (retired) | ||
| CR850 (retired) | ||
| CR850 (retired) | ||
| CR9000X (retired) |
Miscellaneous
| Product | Compatible | Note |
|---|---|---|
| Granite 10 | ||
| Granite 6 | ||
| Granite 9 |
Additional Compatibility Information
The SDM-SIO2R requires a desiccated, non-condensing environment; a Campbell Scientific enclosure is recommended. The SDM-SIO2R is DIN rail mountable and will not mount to a typical Campbell Scientific one-inch diamond grid pattern back panel without the use of a DIN rail, which is sold separately.
The SDM-SIO2R does NOT support auto baud rate detection nor the use of the serial port for general PakBus communications.
Related Documents
Downloads
SDM-SIO2R Example Program v.1 (3 KB) 05-10-2023
In this example program, a SDM-SIO2R will read a visibility measurement from the CS120A. If the SIO2R does not get data from the CS120A three consecutive times, the SIO2R will turn off power to the sensor for 10 seconds and then turn power to the sensor back on and try communicating with it again.