Sentrius RM1xx LoRa + BLE Module

End of Life (EOL)

Overview

NEW: Upgrade firmware from your host microcontroller!

The Sentrius™ RM1xx series of modules offer a powerful, convenient solution for long-range Enterprise IoT (EIoT) deployments. Ezurio innovatively combines Bluetooth® v4.1 with LoRaWAN™, the emerging standard in Low Power Wide Area Networks (LPWAN) into one module. RM1xx modules aggregate and transmit data from Bluetooth® Smart (BLE) devices and sensors over LoRaWAN to gateways as far as 15 km (~10 miles) away. This bridges the personal area network to the wide area network in a unique way. The Sentrius RM1xx will be LoRa® Alliance certified and fully interoperable with any LoRaWAN™-adherent gateway.

  • Designed for the EIoT – Innovative combination of BT™ v4.1 and LoRa® makes the RM1xx the bridge between Bluetooth Smart devices and a network that intelligently uses their data.
  • Ultra-low power usage schemes – Allows years of use on a single battery.
  • Ezurio's (formerly Laird Connectivity) unique smartBASIC language – Makes it extremely easy to create event-driven, hostless applications.
  • Upgradable firmware – Prepare for the future with access to feature and security updates.
  • Compliant with FCC, ISED, EU, UKCA regulations – Available as the RM186 (EU/UKCA) or RM191 (FCC/ISED).
  • Download the NEW UwTerminalX as well as the two companion applications: MultiDeviceLoader and TermNotify

 

Specifications

Transmit Power (Max)
Bluetooth LE: 3 dBm (into -1.5 dBi chip antenna)
Transmit Power
Wireless: 1.5 dBm - 13.5 dBm, Bluetooth: -20 dBm (in four dB steps) with smartBASIC command - 3 dBm (into -1.5 dBi chip antenna)
Antenna Options
Dipole antenna with U.FL (IPEX) connector up to 2 dBi
Bluetooth Version
V4.1 – Central OR Peripheral Mode
Chipset (Wireless)
Semtech SX1272 (LoRa), Nordic nRF51822 (Bluetooth)
Compliance
FCC, ISED, EU, UKCA, NCC, AS-NZS
Interfaces - General
Bluetooth v4.1 (Bluetooth LE Central or Peripheral), physical UART, SPI, I2C, GPIO, or ADC.
Protocols
Any that can be implemented using the onboard smartBASIC
Wireless Specification
LoRaWAN 1.01 (End Device) and Bluetooth 4.1
Part NumberAntenna OptionsAntenna TypeBluetooth VersionChipsetChipset (Wireless)ComplianceConnectorData RateDevelopment Kit ContentsDimension (Height - mm)Dimension (Length - mm)Dimension (Width - mm)Frequency Range (Max)Frequency Range (Min)Input PowerLoRa Version ClassLogical InterfacesOS/SoftwareOutput PowerPower Consumption (Rx)Power Consumption (Tx)Product TypeProtocolsRangeReceive SensitivitySystem ArchitectureTechnologyTransmit Power (Max)WeightWireless Specification
DVK-RM186-SM-01
End of Life (EOL)
Dipole Antenna External 4 LoRa: Semtech Sx1272. BLE: Nordic Semiconductor nRF51822 Semtech SX1272, Nordic nRF51822 USB Pluggable LoRa: 250 bps - 50 kbps. BLE: 1 Mbps. Development Kit DVK-RM186 and Free Software Tools 870 MHz863 MHz2.1V - 3.5V Internal DCDC converter. 1.8V - 2.1V Internal LDO. LoRaWAN 1.01 (End Device) Serial, GPIO, SPI, I2C, ADC smartBASIC 2mW and 25mW 12.7 mA 31.4 mA Development Kit LoRa Class A and Bluetooth Low Energy LoRa: Up to 15 km. BLE: Up to 100 m. LoRa: -134 dBm. BLE: -91 dBm. Hostless Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN +13.5 dBm LoRa MAC Class A Specification
DVK-RM191-SM-01
End of Life (EOL)
Buy Now
Dipole Antenna External 4 LoRa: Semtech Sx1272. BLE: Nordic Semiconductor nRF51822 Semtech SX1272, Nordic nRF51822 USB Pluggable LoRa: 980 bps - 21.9 kbps. BLE: 1 Mbps. Development Kit DVK-RM191 and Free Software Tools 928 MHz902 MHz2.1V - 3.5V Internal DCDC converter. 1.8V - 2.1V Internal LDO. LoRaWAN 1.01 (End Device) Serial, GPIO, SPI, I2C, ADC smartBASIC 2mW and 32mW 15.3 mA 45.7 mA Development Kit LoRa Class A and Bluetooth Low Energy LoRa: Up to 15 km. BLE: Up to 100 m. LoRa: -126 dBm. BLE: -91 dBm. Hostless Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN +15.5 dBm LoRa MAC Class A Specification
RM186-SM
End of Life (EOL)
Buy Now
External Semtech SX1272, Nordic nRF51822 CE LoRa: 250 bps - 50 kbps, BLE: 1 Mbps Development Kit DVK-RM186 and Free Software Tools 3.1 mm25.4 mm25.4 mm870 MHz865 MHzSerial, GPIO, SPI, I2C, ADC smartBASIC 12.7 mA 31.4 mA Development Kit LoRa: -134 dBm. BLE: -91 dBm typical Hostless Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN 13.5 dBm 3 grams
RM191-SM
End of Life (EOL)
Buy Now
External Semtech SX1272, Nordic nRF51822 FCC/IC SMT LoRa: 980 bps - 21.9kbps, BLE: 1 Mbps Development Kit DVK-RM1xx and Free Software Tools 3.1 mm25.4 mm25.4 mm928 MHz902 MHzSerial, GPIO, SPI, I2C, ADC smartBASIC 15.3 mA 45.7 mA Development Kit LoRa: -126 dBm, BLE: -91 dBm typical Hostless Bluetooth 4.1, Dual Mode (Classic + BLE), LoRaWAN 15.5 dBm 3 grams

Development Kits

  • 453-00062-K1

    453-00062-K1

    Additional Description
    USB-SWD Programming Kit: Includes mainboard, TC2050-IDC Tag Connect cable, 10-pin flat IDC cable, 1.2 m USB cable, and 2-pin jumper
    Learn More

Documentation

Name Part Type Last Updated
Using BLE and LoRa - RM1xx Series All Application Note 02/28/2019
Using an LCD Keypad Shield - RM1xx Series All Application Note 02/28/2019
Getting Started with Sample Applications - RM1xx Series All Application Note 02/28/2019
Loading and Running Applications with UwTerminalX - RM1xx Series All Application Note 02/28/2019
Connecting to a Multitech Conduit Gateway - RM1xx Series All Application Note 02/28/2019
UwTerminalX Quick Reference Guide All Application Note 02/28/2019
Debug Features - RM1xx All Application Note 02/28/2019
LoRaWAN Keys and IDs Overview All Application Note 02/28/2019
LoRaWAN Range Testing All Application Note 02/28/2019
Upgrading Firmware from your Host Microcontroller All Application Note 10/06/2023
Interfacing with LoRaWAN - RM191 v1.2 All Application Note 02/28/2019
Using DVK-RM1xx with Laird RG1xx Sentrius Gateway and TTN All Application Note 02/28/2019
Key Differences with v4.4.0 Stack – Affects Laird RM191 FW Versions 101.x.x.x and 102.x.x.x All Application Note 02/28/2019
Integrating Cayenne on TTN - RM1xx v1.1 All Application Note 02/28/2019
Upgrading Firmware via UART - RM1xx Series All Application Note 02/28/2019
Interfacing with LoRaWAN - RM186 v1.3 All Application Note 02/28/2019
Application Note - Updating Firmware and Programming RM1xx Modules with the QPK-NRF5x-01 All Application Note 02/28/2019
PCB Notch Antenna Reference Design - RM1xx - v1 0 All Application Note 02/28/2019
LoRaWAN Certification Test Report - RM1xx All Certification 02/28/2019
Bluetooth SIG Certificate - RM1xx All Certification 02/28/2019
User Guide - RM1xx Development Kit All Documentation 02/28/2019
RM1xx Dipole Antenna Datasheet All Documentation 02/28/2019
Release Notes - RM1xx v4.1.0 All Documentation 02/28/2019
Release Notes - RM1xx PE v18-17-1-0 and v17-17-1-0 All Documentation 02/28/2019
Release Notes - RM1xx Central v17 4 1 0 and 18 4 1 0 All Documentation 02/28/2019
Product Brief - RM1xx Series All Product Brief 07/08/2021
Overview - Understanding LoRa All Documentation 02/28/2019
RM1xx BLE Central smartBASIC Extensions Guide v1.1 All Documentation 02/28/2019
RM1xx BLE Peripheral smartBASIC Extensions Guide v1.1 All Documentation 02/28/2019
Release Notes - Peripheral RM186 EU v110.6.1.0 - RM191 US v111.6.1.0 - RM191 AU v112.6.1.0 - RM191 AS v113.6.1.0 All Documentation 02/28/2019
Release Notes - Central RM186 EU v100.6.1.0 - RM191 US v101.6.1.0 - RM191 AU 102.6.1.0 - RM191 AS v103.6.1.0 All Documentation 02/28/2019
Datasheet - RM1xx Series All Datasheet 02/21/2021
RM1xx LoRa smartBASIC Extensions Guide v1.3 All Documentation 02/28/2019
User Guide - smartBASIC Core Functionality v3.5 All Documentation 12/21/2022
RM191 CE US 101.6.1.0-r1.zip All Software 01/17/2019
RM191 PE US 111.6.1.0-r1.zip All Software 01/17/2019
3D Models - RM1xx.zip All Software 01/17/2019
DVK-RM1xx Schematic-V1 All Software 02/28/2019
Release Notes-RM186 Peripheral EUv110.6.1.0-RM191 Peripheral USv111.6.1.0-RM191 PE AUv112.6.1.0-RM191 PE ASv113.6.1.0 All Software 02/28/2019
Release Notes - Central RM186 EU v100.6.1.0 - RM191 US v101.6.1.0 - RM191 AU 102.6.1.0 - RM191 AS v103.6.1.0 All Software 02/28/2019
RM186 CE EU 100.6.1.0-r1.zip All Software 01/17/2019
RM186 PE EU 110.6.1.0-r1.zip All Software 01/17/2019
RM191 CE AS 103.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
RM191 CE AU 102.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
RM191 PE AS 113.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
RM191 PE AU 112.6.1.0-r1 ENGINEERING.zip All Software 01/17/2019
EU Certifications - RM186 All Certification 07/13/2021
FCC and ISED (Canada) Certifications - RM191 All Certification 12/15/2020
AS-NZS Certifications - RM191 All Certification 09/20/2019
NCC Certifications - RM191 All Certification 12/02/2020
UwTerminalX – Serial Terminal Utility All Software 04/27/2020
UwFlashX – Serial Firmware Update Utility All Software 04/27/2020
RoHS 3 - Packaged and Cellular Products All Certification 10/07/2021
Regulatory Information - RM1xx All Certification 01/17/2022
PCN 9B-2021 - RM1xx Series All Documentation 09/07/2021
EOL - Multi/Mass - Sept 21 All Documentation 09/08/2021
EOL Notice - RM1xx - Oct 2023 All Documentation 11/13/2023

FAQ

Is there a difference between Lora and LoRaWAN?

Yes, Lora is a modulation technique using chirp spread spectrum whereas LoRaWAN is a network topology define by the Lora Alliance. While all LoRaWAN uses LoRa, not all LoRa is LoRaWAN.

A LoRaWAN system is comprised of end devices, gateways and network servers and a broadcast from a LoRaWAN end device must be forwarded by a LoRaWAN gateway to a LoRaWAN network server for authentication.

But it is possible to have point to point LoRa devices that use a proprietary protocol that are not interoperable with LoRaWAN.

Laird RS186 and RS191 are LoRaWAN end devices and can only send data through a LoRaWAN gateway to a LoRaWAN network server.

Why does LoRa TX not work when using GpioAssignEvent()?

Some of the internal SmartBASIC events are being shared between certain peripherals and hence limitations apply for certain combinations. On the RM186 the SmartBASIC implementation uses the same mechanism internally to trigger both LoRa TX and GPIO assign events.

Simplest workaround would be using GpioBindEvent() instead of GpioAssignEvent(). However, this comes with a slightly higher power consumption.

Another workaround would be clearing the GPIO assign event before triggering a LoRa TX event and vice versa. To ensure this, the following sequence would be needed:
  • In your GpioAssignEvent() callback function disable the assign event with GpioUnassignEvent() and start a short one-shot timer (e.g. some 10msecs).
  • In the callback of that timer trigger the LoRa TX.
  • On completion of the LoRa TX (either successfully or failed or both, depends on your application) re-enable the GPIO assign event in e.g. one (or more) of the following callbacks: EVLORAMACSEQUENCECOMPLETE or EVLORAMACTXCOMPLETE or EVLORAMACRXCOMPLETE (maybe others could be used too, would depend on your application)

How can a enable/disable particular BLE channels used for advertising/scanning or when in a connection?

The smartBASIC language provides functions for setting a specific set of channels to be used for BLE advertising/scanning or a BLE connection.

  • BleChannelMap(chanMap$) enables or disables data channel usage when in a connection.
  • BleAdvSetCreate(nSetId, nAdvProperties, nPriSecPhy, nFilterPolicy, peerAddr$, chanMask$) can set BLE advert channels.
  • BleScanStartEx(scanTimeoutMs, nPriPhyScan, chanMask$, nFilterHandle) can set channels used for BLE scanning.

The channel map/mask has to be entered as a 5 byte long string for each of the functions and due to the little-endian architecture of the underlying ARM core its composition can be confusing. The below example will show the actual assignment of channel within that string. Furthermore the meaning of a set bit differs among the above functions.

  • BleChannelMap() -> a set bit means channel is enabled!
  • BleAdvSetCreate() and BleScanStartEx() -> a set bit means channel is disabled!

Now let's “visualize” the channel mapping into the five byte string:

channel number:

00000000|11111100|22221111|33222222|xxx33333
76543210|54321098|32109876|10987654|xxx65432
\byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/

So for enabling e.g., channels 9+10 only you would set the yellow bits:

00000000|11111100|22221111|33222222|xxx33333
76543210|54321098|32109876|10987654|xxx65432
\byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/
 0x00     0x06     0x00     0x00     0x00

giving “0006000000” as string.

For disabling channel only 35, i.e. active channels are 0-34 and 36, it would be:

00000000|11111100|22221111|33222222|xxx33333
76543210|54321098|32109876|10987654|xxx65432
\byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/
  0xFF     0xFF     0xFF     0xFF     0x17

giving “FFFFFFFF17” as string.

Further detail is given in the smartBASIC Extension Guides in the documentation section of the product page for each BLE module at Bluetooth Module Portfolio.

How do I buy an RM1xx module with Peripheral firmware?

The RM1xx module is currently only sold with Central role BLE firmware, as it was intended to allow the device to scan for peripheral BLE devices, such as BLE sensors, to enable it to collect the data from those devices and pass it via LoRa to the gateway. However, Peripheral firmware is available to be flashed to the module if this is what the application requires. Peripheral BLE cannot scan for devices, it can only send out advertisements, which can request to connect to central role BLE devices. To clarify, the differences between Central and Peripheral are related to establishing a link between the devices.

As we stated previously peripheral can advertise to let central role devices know they are there, only Central can scan or send a connection request to establish the connection. Some refer to the Central as the Master and the Peripheral as the Slave. With BLE a separate unrelated role to Central and Peripheral is that of the GATT Server and GATT Client. The GATT server is the device that contains the data which can be accessed and read by the GATT Client. Please note, there is no connection between the central/peripheral roles and the GATT Server/GATT client roles. While it is common for a Peripheral to be a  GATT Server and a Central to be a GATT Client , it is perfectly possible to have a Peripheral that is only a GATT Client, or a Central that is both a GATT Server and a  GATT Client. The RM1xx configured as a Central, can be both a GATT Client and a GATT Server., and it would have the ability to scan for IOT peripheral devices in the area advertising that they are there. The BLE role has no bearing on the LoRa connection. Either of roles, Central/Peripheral will be able to connect to a LoRaWAN Gateway.

With the above information in mind, if you still feel that the Peripheral firmware will best meet your application needs, than in order to upgrade the firmware on the DVK-RM1xx-SM-02 it would be necessary to purchase a device for flashing the firmware. We would recommend using our QPK-nRF5x programmer , which includes the J-Link ribbon cable , as it should offer the least expensive and easiest way to upgrade between the Central and Peripheral firmware in following the  Upgrading Firmware via JTAG and QPK-nRF5x (Required for Central to Peripheral) - RM1xx Series  Application Note. If however, you would prefer to use a Segger J-Link Probe or Flasher for flashing the Peripheral firmware feel free to contact support for a list of Segger devices which should work with the RM1xx. However, we do not provide additional support for upgrading with these devices outside of the documentation available on our website (Upgrading Firmware via JTAG (REQUIRED for Central to Peripheral) - RM1xx Series). Additional support for these probes/flashers would need to come directly from Segger.

What is the difference between ABP and OTAA?

LoRaWAN supports two ways for a device connect to the network.

  1. OTAA: Over the air activation
  2. ABP: Activation by personalization

When using OTAA a join action results in a join request being sent from the RM1xx to the network. The network then checks the Application Identifier (AppEUI) and Application Key (AppKey) provided by the RM1xx. If the APPEUI and APPKey are valid, a join accept message is sent back to the RM1xx which triggers an EVLORAMACJOINED event to be thrown in smart BASIC.

When using ABP there is no handshaking between the RM1xx and the network. As soon as the RM1xx performs a join action it can start sending data. The Application Session Key (AppSKey) and the Network Session Key are set once in both the RM1xx and the network server and must match.

OTAA is the recommended method to join an RM1xx to a LoRaWAN network as it more secure, with the session keys being derived from the APPEUI and APPKey on each connection. Whereas the session keys for ABP remain the same throughout the life of the RM1xx.

Can I run an RM1xx as both BLE Central and BLE Peripheral at the same time?

No, the RM1xx can be purchased with either BLE Central role or Peripheral role support but not both. The RM1xx is loaded with either the Nordic S110 peripheral only BLE soft device or the Nordic S120 central only BLE soft device. To support both peripheral and central on the same module we would need to use Nordic's S130 stack, which is not possible when using smart BASIC. Please contact support for more information. 

Can I replace smartbasic in the RM1xx with my own C application using the Nordic SDK?

Laird RM1xx modules are supplied with smartBASIC and have an integrated LoRaWAN stack.Programming the nRF51 directly would mean the loss of the Laird smartBasic engine, the integrated stack and the RM1xx LoRaWAN certification. Please contact support to discuss this further.

What kind of antenna options are available for the RM1xx module and how much do they cost?

What kind of antenna options are available for the RM1xx module and how much do they cost? Will a PCB traced Antenna work? Please reference the certified antenna list in the Datasheet (HIG) for the LoRa/BLE modules.

To get the most range out of the LoRa module it is recommended that an external dipole antenna is used rather than a PCB trace antenna. However, if range is not going to be an issue and none of the approved antennas will work for you application we do offer EMC testing/certification services and could certify any PCB trace antenna you would like through our in-house certifications lab for an additional service fee. As to the cost of the antenna options and/or EMC services, we ask that you contact support or your Regional Sales Representative for that information.

How do I enable the Built-in VSP functionality on the Peripheral role DVK-RM1xx?

In order to enable the built-in VSP functionality on the DVK-RM1xx, SIO_28 must be tied to VCC. There is a jumper, J6, on the DVK-RM1xx board that brings out SIO_28 but it ties it to GND instead of VCC so some alterations must be made.  Using a red jumper cable, connect J6 pin 1 (SIO_28) to J11 pin 3, VCC_LORA, this enables VSP.  Now, select the nAutorun jumper, J12, depending on which VSP mode is needed: nAutorun (SIO_25) == GND (J12 pins 1-2) puts the module into VSP OTA mode which can be used to download smartBASIC scripts OTA to the module.  nAutorun (SIO_25) == VCC (J12 pins 2-3) puts the module into VSP Bridge mode which can be used as a serial cable replacement to transfer UART data.  Now, reset the DVK-RM1xx or power cycle it and it should begin advertising for a VSP connection. If you do not see the advertisements then remove jumpers J10 (DTR) and J5 (RTS) and reset or power cycle the DVK-RM1xx again.  If you are still having issues getting the board to advertise for a VSP connection, please contact support.

Can AS923 and AU915 networks coexist in the same area?

Yes, as long as they are operating on different networks such that AS923 sensors talk to the AS923 gateway and vice versa for AU915 devices. 

Can the RS1xx AS923 (455-00063) work with an AU915 gateway which uses overlapping channels to AS923?

No, an RS1xx AS923 sensor will not work with an AU915 gateway because it cannot receive the downlink packets due to differing bandwidth and frequency plans used and therefore will drop off the network.

Is there a way to extend the shelf life of Laird modules?? If the shelf life cannot be extended in any way, what are the consequences of using modules after shelf life?

The shelf life statements are essentially to prevent mishandling of the product and not storing it properly. If the modules are still sealed in the package, stored at the proper temperature and have not been exposed to moisture they should be fine. However, when working with modules beyond their shelf life you MUST bake the modules before populating the them to your board. Failure to bake the modules could result in the yield rate dropping down lower than expectation due to popcorn or de-lamination on the modules. It is recommended that you follow IPC/JEDEC J-STD-033 which is the general standard for the handling, packing, shipping and use of moisture/reflow sensitive surface mount devices.

Our main concern is around the castellation/pads which solder the module to the board. It is imperative those pads do not get tarnished, as this would cause soldering issues. Humidity can affect solderability as well, as if there is any excess moisture in the solder on the module, during reflow of the module to the board, steam balls can essentially explode the solder and sometimes result in an open circuit (or possibly a short circuit).

As long as all of the moisture handling and temperature guidelines are being followed you will likely have no issues. It is further recommended that when you do the build with modules that have exceeded their shelf life that you start with a handful to perform a test run and do a final test to make sure all is working as expected. As long as there are no issues with the initial test run we would expect that you will not experience any problems.

Become a Ezurio Customer and Gain Exclusive Access to Our Design Services Team

  • Antenna Scans
  • Antenna selection and placement
  • Custom antenna design
  • Worldwide EMC testing / certifications
  • Embedded RF hardware / firmware design
  • Cloud architecture and integration
  • Mobile application development
  • Product & Industrial Design

Talk to an Expert

Buy Now

Distributor Part In Stock Region Buy
Mouser 453-00062-K1 18 North America Buy Now
DigiKey 453-00062-K1 10 North America Buy Now
Avnet 453-00062-K1 0 North America Buy Now
Symmetry Electronics 453-00062-K1 0 North America Buy Now
DigiKey DVK-RM191-SM-01 12 North America Buy Now
DigiKey RM186-SM 0 North America Buy Now
Future Electronics RM186-SM 0 North America Buy Now
DigiKey RM191-SM 976 North America Buy Now
Future Electronics RM191-SM 0 North America Buy Now

Distributors

Distributor Phone Number Region Website
Alpha Micro UK Only +44 1256-851770
EMEA Website
Arrow Electronics 1-855-326-4757
+44 2039 365486
APAC, North America, South America, EMEA Website
Avnet 1-480-643-2000
+44 1628 512900
APAC, North America, South America, EMEA Website
Braemac Australia, New Zealand, South East Asia +61 2 9550 6600
+64 9 477 2148
APAC Website
Cal-Chip Connect 1-215-942-8900
North America Website
DigiKey 1-800-344-4539
North America, South America, APAC, EMEA Website
EBV Elektronik EMEA Website
Farlink Technology China, Hong Kong +86 13266922199
APAC Website
Farnell 1-800-936-198
+44 3447 11 11 22
EMEA Website
Future Electronics 1-800-675-1619
1-514-428-8470
North America, South America, APAC, EMEA Website
Glyn +49-6126-590-0
EMEA Website
Jetronic China, Hong Kong and Taiwan 852-27636806 
APAC Website
Laird Connectivity 1-847-839-6925
+44 1628 858941
North America, South America, APAC, EMEA Website
M2M Germany +49-6081-587386-0
EMEA Website
Martinsson +46 8 7440300
EMEA Website
McCoy South East Asia +65 6515 2988
APAC Website
Mouser 1-800-346-6873
+44 1494 427500
North America, South America, APAC, EMEA Website
RS Components +852-2421-9898
+44 3457-201201
North America, South America, APAC, EMEA Website
Ryoyo Japan +81-3-3543-7711
APAC Website
Solsta UK Only +44 (0) 1527 830800
EMEA Website
Supreme Components International India, South East Asia +65 6848-1178
APAC Website
Symmetry Electronics 1-866-506-8829
North America Website
Tekdis Australia and New Zealand +61 3 8669 1210
APAC Website
Telsys +972 3 7657666
EMEA Website
WPG +44 1628 958460
EMEA Website