Table of Contents:

• 1.  Introduction
  • 1.1 ​ What is LTC2-NB/NS NB-IoT Temperature Transmitter
  • ​1.2  Features
  • 1.3  Specification
  • 1.4 ​ Applications
  • 1.5  Sleep mode and working mode
  • 1.6  Button & LEDs
  • 1.7  BLE connection
  • 1.8  Pin Definitions , Switch & SIM Direction
    • 1.8.1 Jumper JP2
    • 1.8.2 BOOT MODE / SW1
    • 1.8.3 Reset Button
    • 1.8.4 SIM Card Direction
  • 1.9  Mechanical
    • 1.9.1 for NB version
    • 1.9.2 for NS version
  • 1.10  Probe Variant
• 2.  Use LTC2-NB/NS to communicate with IoT Server
  • 2.1  Send data to IoT server via NB-IoT network
  • 2.2 ​Payload Types
    • 2.2.1 General Json Format(Type=5)
    • 2.2.2 HEX format Payload(Type=0)
    • 2.2.3 ThingsBoard Payload(Type=3)
    • 2.2.4 ThingSpeak Payload(Type=1)
• 3. Configure LTC2-NB/NS
  • 3.1 Configure Methods
  • ​​​3.2  Serial Access Password
  • 3.3 AT Commands Set
  • 3.4 Test Uplink and Change Update Interval
  • 3.5 Set the receiving time
  • 3.6 Reset
  • 3.7 Trigger an uplink by external interrupt
  • 3.8 Set the QoS level
  • 3.9 Clock logging
  • 3.10 Set the TLS mode
  • 3.11 Set the search network time
  • 3.12  Set alarm mode
  • 3.13  Alarm check time
  • 3.14  Set Alarm Threshold
  • 3.15 Factory data reset
  • 3.16 Set CoAP option
  • 3.17 Example Query saved historical records
  • 3.18 Uplink log query
  • 3.19 Print last few data entries
  • 3.20 Print data entries base on page
  • 3.21 Clear Flash Record
  • 3.22 Set the downlink debugging mode
  • 3.23 Domain name resolution settings
• 4. Battery & Power Consumption
• 5. Firmware update
• 6.  FAQ
  • 6.1 How can I access t BC660K-GL AT Commands?
• 7.  Order Info
• 8. ​ Packing Info
• 9.  ​Support

1.  Introduction

1.1 ​ What is LTC2-NB/NS NB-IoT Temperature Transmitter

The Dragino LTC2-NB/NS Industrial NB-IoT Temperature Transmitter is designed to monitor temperature for different environment. It supports to read PT100 probe and convert the value to temperature and then upload to IoT server via NB-IoT network*.

LTC2-NB/NS has two internal 24-bit ADC interfaces.

LTC2-NB/NS supports BLE configure and wireless OTA update which make user easy to use.

LTC2-NB/NS supports different uplink methods include TCP, MQTT, UDP, MQTTs or CoAP for different application requirement. and Support Uplinks to various IoT Servers.

LTC2-NB/NS is powered by 8500mAh Li-SOCI2 battery or solar powered + Li-ion battery, It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period and uplink method. Please check related Power Analyze report).

*make sure you have NB-IoT coverage locally.

​1.2  Features

• NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD
• Ultra-low power consumption
• max: 2 x monitor temperature channels
• Support 3 -wire PT-100
• Temperature alarm
• Multiply Sampling and one uplink
• Uplink via MQTT, MQTTs, TCP, UDP or CoAP
• Support Bluetooth v5.1 remote configure and update firmware
• Uplink on periodically
• Downlink to change configure
• 8500mAh Battery for long term use  (LTC2-NB)
• Solar panel + 3000mAh Li-ion battery (LTC2-NS)

1.3  Specification

Common DC Characteristics:

• Supply Voltage: Built-in Battery , 2.5v ~ 3.6v
• Operating Temperature: -40 ~ 85°C

Temperature Sensor:

• Range: -40 to + 80°C
• Accuracy: ±0.2 @ 0-90 °C
• Resolution: 0.1°C
• Long Term Shift: <0.03 °C/yr

NB-IoT Spec:

NB-IoT Module: BC660K-GL

Support Bands:

• B1 @H-FDD: 2100MHz
• B2 @H-FDD: 1900MHz
• B3 @H-FDD: 1800MHz
• B4 @H-FDD: 2100MHz
• B5 @H-FDD: 860MHz
• B8 @H-FDD: 900MHz
• B12 @H-FDD: 720MHz
• B13 @H-FDD: 740MHz
• B17 @H-FDD: 730MHz
• B18 @H-FDD: 870MHz
• B19 @H-FDD: 870MHz
• B20 @H-FDD: 790MHz
• B25 @H-FDD: 1900MHz
• B28 @H-FDD: 750MHz
• B66 @H-FDD: 2000MHz
• B70 @H-FDD: 2000MHz
• B85 @H-FDD: 700MHz

Battery:

• Li/SOCI2 un-chargeable battery
• Capacity: 8500mAh
• Self Discharge: <1% / Year @ 25°C
• Max continuously current: 130mA
• Max boost current: 2A, 1 second

Power Consumption

• STOP Mode: 10uA @ 3.3v
• Max transmit power: 350mA@3.3v

1.4 ​ Applications

• Logistics and Supply Chain Management
• Food management
• Cold chains solution
• Industrial Monitoring and Control

1.5  Sleep mode and working mode

Deep Sleep Mode: Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life.

Working Mode: In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.

1.6  Button & LEDs

1.7  BLE connection

LTC2-NB/NS support BLE remote configure and firmware update.

BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:

• Press button to send an uplink
• Press button to active device.
• Device Power on or reset.

If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.

1.8  Pin Definitions , Switch & SIM Direction

1.8.1 Jumper JP2

Power on Device when put this jumper.

Power off device when take out this jumper

1.8.2 BOOT MODE / SW1

1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.

2) Flash: work mode, device starts to work and send out console output for further debug

1.8.3 Reset Button

Press to reboot the device.

1.8.4 SIM Card Direction

See this link. How to insert SIM Card.

1.9  Mechanical

1.9.1 for NB version

1.9.2 for NS version

1.10  Probe Variant

LTC2-NB/NS provide default probe version. See below for the variant:

2.  Use LTC2-NB/NS to communicate with IoT Server

2.1  Send data to IoT server via NB-IoT network

There are two version: -GE and -1T version of LTC2-NB/NS.

GE Version: This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set LTC2-NB/NS send data to IoT server.

• Install NB-IoT SIM card and configure APN. See instruction of Attach Network.

• Set up sensor to point to IoT Server. See instruction of Configure to Connect Different Servers.  

Below shows result of different server as a glance.

Servers	Dash Board	Comments
Node-Red
DataCake
Tago.IO
General UDP	Raw Payload. Need Developer to design Dash Board
General MQTT	Raw Payload. Need Developer to design Dash Board
ThingSpeak
ThingsBoard

1T Version: This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate LTC2-NB/NS and user will be able to see data in ThingsEye. See here for ThingsEye Config Instruction.

2.2 ​Payload Types

To meet different server requirement, LTC2-NB/NS supports different payload type.

Includes:

• General JSON format payload. (Type=5)

• HEX format Payload. (Type=0)

• ThingSpeak Format. (Type=1)

• ThingsBoard Format. (Type=3)

User can specify the payload type when choose the connection protocol. Example:

AT+PRO=1,0            // Use COAP Connection & hex Payload

AT+PRO=1,5            // Use COAP Connection & Json Payload

AT+PRO=2,0            // Use UDP Connection & hex Payload

AT+PRO=2,5            // Use UDP Connection & Json Payload

AT+PRO=3,0            // Use MQTT Connection & hex Payload

AT+PRO=3,5            // Use MQTT Connection & Json Payload

AT+PRO=4,0            // Use TCP Connection & hex Payload

AT+PRO=4,5            // Use TCP Connection & Json Payload

2.2.1 General Json Format(Type=5)

This is the General Json Format. As below:

{"IMEI":"863663062765285","IMSI":"460086859301435","Model":"LTC2-NB","temp_alarm":"NN","channel1_temp":22.7,"channel2_temp":22.7,"battery":3.522,"signal":23,"time":"2024/12/31 05:33:12","1":[22.7,22.7,"2024/12/31 05:22:00"],"2":[22.7,22.7,"2024/12/31 05:07:00"],"3":[22.7,22.9,"2024/12/31 04:52:00"],"4":[22.9,22.9,"2024/12/31 04:37:00"],"5":[22.9,23.1,"2024/12/31 04:22:00"],"6":[23.1,23.4,"2024/12/31 04:07:00"],"7":[23.1,23.6,"2024/12/31 03:52:00"],"8":[23.0,23.2,"2024/12/31 03:37:00"]}

Example:

Notice, from above payload:

• Temp_alarm, Channel1_temp, Channel2_temp, Battery, Signal & time are the value at uplink time.

• Json entry 1 ~ 8 are the last 1 ~ 8 sampling data as specify by AT+CLOCKLOG=1,65535,15,8 Command. Each entry includes (from left to right): TChannel1_temp, Channel2_temp, Sampling time.

Temp_alarm:

This data field shows whether the packet was generated by a temperature alarm.

"L" stands for low temperature alarm, "H" stands for high temperature alarm.

Example:

• NN: No temperature alarm.
• NH: Channel 1 does not alarm, channel 2 high temperature alarm.
• NL: Channel 1 does not alarm, channel 2 low temperature alarm.
• HH: Both channel 1 and channel 2 have high temperature alarms.
• LL: Both channel 1 and channel 2 have low temperature alarms

2.2.2 HEX format Payload(Type=0)

This is the HEX Format. As below:

f863663062765285f4600868593014353d640dce1500000000e300e56773846100e300e3677382fc00e300e367737f7800e300e367737bf400e300e56773787000e500e5677374ec00e500e76773716800e700ea67736de400e700ec67736a60

Device ID(f+IMEI): f863663062765285 =863663062765285

SIM Card ID(f+IMSI): f460086859301435 =460086859301435

Version:

These bytes include the hardware and software version.

Higher byte: Specify Sensor Model: 0x3d for LTC2-NB/NS

Lower byte: Specify the software version: 0x64=100, means firmware version 1.0.0

BAT (Battery Info):

Ex1: 0x0cbc = 3260mV

Signal Strength:

NB-IoT Network signal Strength.

Ex1: 0x15 = 21

0        -113dBm or less

1        -111dBm

2...30 -109dBm... -53dBm

31      -51dBm or greater

99      Not known or not detectable

Interrupt:

This data field shows if this packet is generated by interrupt or not.

Example:

If byte[0]&0x01=0x00 : Normal uplink packet.

If byte[0]&0x01=0x01 : Interrupt Uplink Packet.

Interrupt_level:

This byte shows whether the interrupt is triggered by a high or low level.

Ex1: 0x00  Interrupt triggered by falling edge (low level)

Ex2: 0x01  Interrupt triggered by rising edge (high level)

Temp_alarm:

This data field shows whether the packet was generated by a temperature alarm.

Example:

Ex1: 0x00(H) = 0000(B)  No temperature alarm.

Ex2: 0x04(H) = 0100(B)  Channel 1 does not alarm, channel 2 alarms.

Ex3: 0x01(H) = 0001(B)  Channel 1 alarms, channel 2 does not alarm.

Ex4: 0x05(H) = 0101(B)  Channel 1 and channel 2 alarms.

channel1_temp

If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree

If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.

(FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)

If the value is -327.6, it means the channel1 PT100 probe is not connected.

If the value is -983, it means the PT100 converter is not connected.

channel2_temp

If payload is: 0105H:  (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree

If payload is: FF3FH :  (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.

(FF3F & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative)

If the value is -327.6, it means the channel2 PT100 probe is not connected.

If the value is -983, it means the PT100 converter is not connected.

​

TimeStamp:  

Unit TimeStamp Example: 676b5f85(H) = 1735090053(D)

Put the decimal value into this link(https://www.epochconverter.com/) to get the time.

2.2.3 ThingsBoard Payload(Type=3)

Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.

{
    "topic": "LTC2_NB",
    "payload": {
        "IMEI": "863663062765285",
        "IMSI": "460086859301435",
        "Model": "LTC2-NB",
        "temp_alarm": "NN",
        "channel1_temp": 23.3,
        "channel2_temp": 22.7,
        "battery": 3.577,
        "signal": 21,
        "time": "2024/12/26 03:54:18",
        "1": [23.1, 22.5, "2024/12/26 03:31:19"],
        "2": [23.1, 22.4, "2024/12/26 03:16:19"],
        "3": [22.9, 22.2, "2024/12/26 03:01:19"],
        "4": [22.7, 22.1, "2024/12/26 02:46:19"],
        "5": [23.0, 22.2, "2024/12/26 02:31:19"],
        "6": [22.2, 22.2, "2024/12/26 02:16:19"],
        "7": [22.1, 22.1, "2024/12/26 02:01:19"],
        "8": [21.0, 20.1, "2024/12/25 09:29:50"]
    }
}

​

3. Configure LTC2-NB/NS

3.1 Configure Methods

LTC2-NB/NS supports below configure method:

• AT Command via Bluetooth Connection (Recommended): BLE Configure Instruction.

• AT Command via UART Connection : See UART Connection.

​​​3.2  Serial Access Password

After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.

The label on the box of the node will print the initial password: AT+PIN=xxxxxx, and directly use the six-digit password to access the AT instruction window.

3.4 Test Uplink and Change Update Interval

By default, Sensor will send uplinks every 2 hours.

User can use below commands to change the uplink interval.

AT Command: AT+TDC       

Example: AT+TDC=7200   // Set Update Interval to 7200 seconds

Downlink Commands: 0x01

Format: Command Code (0x01) followed by 3 bytes.

Example:     12 hours= 43200 seconds     43200(D)=0xA8C0(H)

                    Downlink Payload: 01 00 A8 C0          // AT+TDC=43200, Set Update Interval to 12 hours.

Note: User can also push the button for more than 1 second to activate an uplink.

3.5 Set the receiving time

Feature: Extend the receiving time

AT Command: AT+RXDL

Example: AT+RXDL=1000   // Set the receiving time delay to 1000ms

Downlink Commands: 0x03

Format: Command Code (0x03) followed by 3 bytes.

Example:  Downlink Payload: 03 00 03 E8     // AT+RXDL=1000

3.6 Reset

Feature: Trig a reset of the MCU.

AT Command: ATZ

Downlink Commands: 0x04FF

3.7 Trigger an uplink by external interrupt

LTC2-NB/NS has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets.

AT command:

• AT+INTMOD         // Set the trigger interrupt mode

• AT+INTMOD=0    // Disable Interrupt

• AT+INTMOD=1    // Trigger by rising and falling edge

• AT+INTMOD=2    // Trigger by falling edge

• AT+INTMOD=3    // Trigger by rising edge

Downlink Commands: 0x06

Format: Command Code (0x06) followed by 3 bytes.

Example1:  Downlink Payload: 06 00 00 01    // AT+INTMOD=1

Example2:  Downlink Payload: 06 00 00 03    // AT+INTMOD=3

3.8 Set the QoS level

This command is used to set the QoS level of MQTT.

AT command:

• AT+MQOS=xx   // 0~2

Downlink command: 0x07

Format: Command Code (0x07) followed by 1 byte.

Ex1: Downlink payload: 0x0700   // AT+MQOS=0

Ex2: Downlink payload: 0x0701   // AT+MQOS=1

3.9 Clock logging

Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.

We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.

AT command: AT+CLOCKLOG=a,b,c,d

a: 0: Disable Clock logging.   1: Enable Clock Logging

b: Specify First sampling start second: range (0 ~ 3599, 65535)         //  Note: If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.

c: Specify the sampling interval: range (0 ~ 255 minutes)

d: How many entries should be uplink on every TDC (max 32)

Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0

Example:

AT+CLOCKLOG=1,65535,1,5

After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp).

Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.

Downlink command: 0x08

Format: Command Code (0x08) followed by 5 bytes.

• Example 1: Downlink Payload: 08 01 FFFF 0F 08              // Set SHT record time: AT+CLOCKLOG=1,65535,15,8
• Example 2: Downlink Payload: 08 01 04B0 0F 08             // Set SHT record time: AT+CLOCKLOG=1,1200,15,8

Note: When entering the downlink payload, there must be no Spaces between bytes.

3.10 Set the TLS mode

Refer to this link (MQTT Connection to send data to Tago.io)to use the TLS mode.

AT Command: AT+TLSMOD

Example 1:  AT+TLSMOD=0,0   // Disable TLS Mode.

Example 2:  AT+TLSMOD=1,0   // No authentication

                     AT+TLSMOD=1,1   // Perform server authentication

                     AT+TLSMOD=1,2   // Perform server and client authentication if requested by the remote server

Downlink command: 0x09

Format: Command Code (0x09) followed by 2 bytes.

Example1:  Downlink Payload: 09 00 00    // AT+TLSMOD=0,0

Example2:  Downlink Payload: 09 01 02    // AT+TLSMOD=1,2

3.11 Set the search network time

Feature: Get or Set the time to join the network(unit: minutes).

AT Command: AT+CSQTIME

Example: AT+CSQTIME=10   // Set the search time to 10 minutes.

Downlink command: 0x13

Format: Command Code (0x13) followed by 1 byte.

Example:  Downlink Payload: 13 0A   // AT+CSQTIME=10

3.12  Set alarm mode

Feature: Enable/Disable Alarm Mode.

AT Command: AT+WMOD

• AT+WMOD=0    // Disable the alarm mode, default.
• AT+WMOD=1    // Enable the alarm mode.

Downlink Command: 0xA5

• Downlink payload: 0xA500         // Same as AT+WMOD=0
• Downlink payload: 0xA501         //  Same as AT+WMOD=1

3.13  Alarm check time

Feature: The time interval to check sensor value for Alarm. ( Default: AT+CITEMP=5; Unit: minute )

AT Command: AT+CITEMP

Example: 

• AT+CITEMP=10     // Set collection interval in 10 min, only in alarm mode.

Downlink Command: 0xA6

Format: Command Code (0xA6) followed by 2 bytes.

Example:

• Downlink payload: 0xA6000A     // Same as AT+CITEMP=10

3.14  Set Alarm Threshold

Feature: Set Alarm Threshold. (Unit: ℃)

AT Command: AT+ARTEMP

The first parameter sets the low limit of channel 1, and the second parameter sets the high limit of channel 1.

The third parameter sets the low limit for channel 2, and the fourth parameter sets the high limit for channel 2.

Example:

• AT+ARTEMP=-200,800,-200,800    // Channel 1 & Channel 2 operating temp: -200℃~800℃，alarm when out of range.
• AT+ARTEMP=10,100,10,101           // Channel 1 operating temp: 10℃~100℃; Channel 2 operating temp: 10℃~101℃, alarm when out of range.

Downlink Command: 0xA7

Format: Command Code (0xA7) followed by 8 bytes.

Each two bytes after the function code 0xA7 is a parameter, corresponding to the four parameters of AT+ARTEMP in sequence.

Example:

• Downlink payload: 0xA7FF380320FF380320    // Same as AT+ARTEMP=-200,800,-200,800
• Downlink payload: 0xA7000A0064000A0065   // Same as AT+ARTEMP=10,100,10,101   

Note: For negative temperature -200℃: 65536-200= 65336(D) = 0XFF38(H)

3.15 Factory data reset

Two different restore factory Settings configurations.

AT command:

• AT+FDR       // Reset Parameters to Factory Default.
• AT+FDR1     // Reset parameters to factory default values except for passwords.

3.16 Set CoAP option

This command sets the connection parameters of the COAP. 

AT command:

• AT+URI1       // CoAP option name, CoAP option length, "CoAP option value"
• AT+URI2      // CoAP option name, CoAP option length,  "CoAP option value"
• AT+URI3     // CoAP option name, CoAP option length,  "CoAP option value"
• AT+URI4     // CoAP option name, CoAP option length,  "CoAP option value"

Example:

• AT+URI1=11,38,"i/faaa241f-af4a-b780-4468-c671bb574858"

3.17 Example Query saved historical records

• AT command: AT+CDP

This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes.

3.18 Uplink log query

• AT command: AT+GETLOG

This command can be used to query upstream logs of data packets.

3.19 Print last few data entries

Feature: Print the last few data entries

AT command: AT+PLDTA

Downlink Command: 

No downlink commands for feature

3.20 Print data entries base on page

Feature: Print the sector data from start page to stop page.

AT command: AT+PDTA

Downlink Command: 

No downlink commands for feature

3.21 Clear Flash Record

Feature: Clear flash storage for data log feature.

AT command: AT+CLRDTA

Downlink Command:  0x32

• Example: 0x32 00        //  Same as AT+CLRDTA

3.22 Set the downlink debugging mode

Feature: Set the conversion between the standard version and 1T version downlinks.

AT command: AT+DOWNTE

Example:

• AT+DOWNTE=0,1  // Set to standard version downlink, and enable downlink debugging.
• AT+DOWNTE=1,1  // Set to 1T version downlink, and enable downlink debugging.

Downlink Command:  

No downlink commands for feature

3.23 Domain name resolution settings

Feature: Set dynamic domain name resolution IP.

AT command: AT+BKDNS

Example:

• AT+BKDNS=1,0        // Dynamic domain name resolution is disabled.
• AT+BKDNS=2,1        // The dynamic domain name resolution function is enabled and the automatic update time is set to 1 hour.
• AT+BKDNS=2,4,3.69.98.183,1883      // The dynamic domain name resolution function is enabled and the automatic update time is set to 4 hour, and manually set the ip address, if the domain name failed to resolve, it will directly use this ip to communicate. When the next domain name resolution is successful, it will be updated to the ip address of the successful resolution.

Downlink Command:  

No downlink commands for feature

4. Battery & Power Consumption

LTC2-NB use ER26500 + SPC1520 battery pack and LTC2-NS use 3000mAh Recharable Battery with Solar Panel. See below link for detail information about the battery info and how to replace.

Battery Info & Power Consumption Analyze .

5. Firmware update

User can change device firmware to::

• Update with new features.

• Fix bugs. 

Firmware and changelog can be downloaded from : Firmware download link

Methods to Update Firmware:

• (Recommended way) OTA firmware update via BLE: Instruction.

• Update through UART TTL interface : Instruction.

6.  FAQ

6.1 How can I access t BC660K-GL AT Commands?

User can access to BC660K-GL directly and send AT Commands.

See BC660K-GL AT Command set

7.  Order Info

Notice: This part number doesn't include the Temperature sensor. Users need to purchase separately.

Part Number: LTC2-NB/NS-XX

XX:

• GE: General version ( Exclude SIM card)

• 1T: with 1NCE * 10 years 500MB SIM card and Pre-configure to ThingsEye server

Probe Options: DR-SI, DR-LT, DR-HT, DR-FSA, DR-FT

8. ​ Packing Info

Package Includes:

• LTC2-NB/NS NB-IoT Temperature Transmitter x 1

Dimension and weight:

• Device Size: cm
• Device Weight: g
• Package Size / pcs : cm
• Weight / pcs : g

9.  ​Support

• Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
• Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to support@dragino.com.