image-20240705094013-3.png

Table of Contents:

1.  Introduction

1.1  What is the PB01 LoRaWAN Push Button?

The PB01 LoRaWAN Push Button is a wireless LoRaWAN device equipped with a single push button. When the user presses the button, the PB01 sends an uplink to the LoRaWAN Network Server using the long-range LoRaWAN wireless protocol. Additionally, the PB01 measures environment temperature & humidity and periodically uplinks this data to the LoRaWAN Network Server.

The PB01 is powered by 2 x AAA batteries, allowing it to operate for several years.* Users can easily replace the batteries once they are drained.

The PB01 also features a built-in speaker that can produce different sounds when the button is pressed or when a reply (downlink) is received from the Network Server. The speaker can be disabled if the user prefers.

The PB01 is fully compatible with the LoRaWAN v1.0.3 protocol, and works seamlessly with standard LoRaWAN gateways.

* Battery life depends on the frequency of data transmission. Please refer to the battery analyzer for details.

1.2  Features

  • Wall-mountable
  • LoRaWAN v1.0.3 protocol, Class A mode
  • 1 x push button (available in different colors)
  • Built-in temperature and humidity sensor
  • Built-in speaker
  • Frequency bands: CN470, EU433, KR920, US915, EU868, AS923, AU915
  • AT commands for parameter changes
  • Remote parameter configuration via LoRaWAN downlink
  • Firmware upgradable via programming port
  • Supports 2 x AAA LR03 batteries
  • IP rating: IP52

1.3  Specification

Built-in Temperature Sensor:

  • Resolution: 0.01 °C
  • Accuracy Tolerance: Typ ±0.2 °C
  • Long-Term Drift: < 0.03 °C/year
  • Operating Range: -10 ~ 50 °C or -40 ~ 60 °C (depends on battery type; see FAQ)

Built-in Humidity Sensor:

  • Resolution: 0.01 %RH
  • Accuracy Tolerance: Typ ±1.8 %RH
  • Long-Term Drift: < 0.2 %RH/year
  • Operating Range: 0 ~ 99.0 %RH (no dew)

1.4  Power Consumption

PB01 : Idle: 5 uA, Transmit: max 110 mA

1.5  Storage & Operation Temperature

-10 ~ 50 °C  or -40 ~ 60 °C (depends on battery type; see FAQ)

1.6  Applications

  • Smart buildings & home automation
  • Logistics & supply chain management
  • Smart metering
  • Smart agriculture
  • Smart cities
  • Smart factories

2.  Operation Mode

2.1  How It Works?

Each PB01 is shipped with registration information that can be used to register and activate the device with a LoRaWAN Network Server using Over-The-Air Activation (OTAA), which is the most secure method for activating an end device on a LoRaWAN Network Server. It also supports Activation-By-Personalization (ABP), but this method is not recommended as it is less secure.

After registration, if the PB01 is within the LoRaWAN network's coverage area, it can join the network and start transmitting sensor data to the LoRaWAN Network Server. The default uplink interval is 20 minutes.

2.2  How to turn on PB01?

 1.  Open the enclosure from the bottom.

image-20220621093835-1.png

 2.  Insert 2 x AAA LR03 batteries to turn on the device.

image-20220621093835-2.png

 3. After activating with a LoRaWAN network, you can re-join/restart the device by long pressing the ACT button as shown in the image below.

image-20220621093835-3.png  

You can check the LED Status to determine the working state of the PB01.

2.3  Example to join LoRaWAN network

This section shows an example for how to join the TheThingsNetwork LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure.

Assume the LPS8v2 is already set to connect to TTN V3 network . We need to add the PB01 device in TTN V3 portal.  

image-20240705094824-4.png

Step 1:  Create a device in TTN V3 with the OTAA keys from PB01.

Each PB01 is shipped with a sticker with the default DEV EUI as below:

image-20230426083617-1.png

2.3.1 Add PB01 to The Things Stack

PB01 currently supports only manual registartion with The Things Stack.

2.3.1.1 Creating an application

Sign up for a free account with The Things Stack Sandbox if you do not have one yet. Then, create an application as shown in the screenshots below.

2.3.1.2 Adding manually

You can refer to the screenshots below to register your PB01 using The Things Stack's manual registration option.

On The Things Stack console:

  • Click Applications.
  • Click <your application>. E.g. dragino-docs
  • Click End devices.
  • Click + Register end device button.

5.png

  • Select Enter end device specifies manually option.
  • Frequency plan: Select the frequency plan that matches your device. E.g.: Europe 863-870 MHz (SF9 for RX2 - recommended).
  • LoRaWAN version: LoRaWAN Specification 1.0.3
  • Regional Parameters version: You can't change it and it will select automatically.

2.png

  • JoinEUI: Enter the AppEUI of the device (see the registration information sticker) and Click the Confirm button.
  • DevEUI: Enter the DevEUI of the device (see the registration information sticker).
  • AppKey: Enter the AppKey of the device (see the registration information sticker).
  • End device ID: Enter a name for your end device to uniquely identify it within this application.
  • Click View registered end device option.
  • Click Register end device button.

3.png

You will be navigated to the Device overview page.
 

2.3.1.3 Activate the PB01

Press ACT button to activate the PB01. It will then join The Things Stack. Once successfully connected, the device will begin uplinking sensor data to The Things Stack, which can be viewed on the Live data panel.

image-20240507143104-5.png

2.4  Uplink Payload

Uplink payloads include two types: Valid Sensor Value and other status / control command.

  • Valid Sensor Value: Use FPORT=2
  • Other control command: Use FPORT other than 2.

2.4.1  Uplink FPort=5, Device Status

The 'Device Status' uplink is sent by the PB01 as its first uplink after successfully joining a LoRaWAN network. However, you can manually retrieve the device status as an uplink by sending a command as a downlink to the device. The format of the downlink command should be in hexadecimal.

Downlink:  0x2601 

The device uplinks its status via FPort=5, and the payload format is as follows:

Size(bytes) 12112
ValueSensor ModelFirmware VersionFrequency BandSub-bandBAT

The following figure shows the decoded device status payload as displayed on The Things Stack.

image-20240507152130-12.png 

For example, if the device status uplink includes the payload,  image-20240507152254-13.png

Sensor model: 0x35 - for PB01, this value is 0x35.

Firmware version: 0x0100 - value 0x0100 means v1.0.0.

Frequency band: 01 - means EU868. The following are the possible values for other frequency bands.

*0x01: EU868

*0x02: US915

*0x03: IN865

*0x04: AU915

*0x05: KZ865

*0x06: RU864

*0x07: AS923

*0x08: AS923-1

*0x09: AS923-2

*0x0A: AS923-3

Sub band: 0xFF - value 0x00 ~ 0x08 (only for CN470, AU915, US915. Others are 0x00)

BAT: 0x 0CDE - represents the battery voltage for PB01. The values 0x0CDE means 3294 mV = 3.294 V

2.4.2  Uplink FPort=2, Real time sensor values

The PB01 sends real time sensor values after the Device Status uplink. The device will continue to send this uplink periodically. The default interval is 20 minutes, but it can be changed.

This type of uplink uses FPort=2 and, by default, is sent every 20 minutes. The default uplink interval can be changed using AT commands.

Size(bytes)

2

1

1

2

2

Value

Battery

Sound_ACK & Sound_key

Alarm

Temperature

Humidity

The following figure shows the decoded real time sensor values payload as displayed on The Things Stack.

image-20240507150155-11.png

For example, if the real time sensor values uplink includes the payload (FPort=2):   0C EA 03 01 01 11 02 A8

Battery:

Byte 1 and 2: Check the battery voltage.

  • Example 1: 0x0CEA = 3306mV
  • Example 2: 0x0D08 = 3336mV

Sound_ACK & Sound_key:

Byte 3: Key sound and ACK sound are enabled by default.

  • Example1: 0x03

          Sound_ACK: (03>>1) & 0x01=1, OPEN.

          Sound_key:  03 & 0x01=1, OPEN.

  • Example 2: 0x01

          Sound_ACK: (01>>1) & 0x01=0, CLOSE.

          Sound_key:  01 & 0x01=1, OPEN.

Alarm:

Byte 4: Key alarm.

  • Example 1: 0x01 & 0x01=1, TRUE.
  • Example 2: 0x00 & 0x01=0, FALSE.

Temperature:

Byte 5 and 6: Temperature.

  • Example 1: 0x0111/10=27.3°C
  • Example 2: (0xFF0D-65536)/10=-24.3°C

If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3°C

(FF0D & 8000:Check whether the highest bit is 1. If the highest bit is 1, the value is negative)

Humidity:

Byte 7 and 8: Humidity

  • Humidity: 0x02A8/10=68.0%

2.4.3  Uplink FPort=3, Datalog sensor value

PB01 stores sensor values, and you can retrieve these historical values via a downlink command. The Datalog sensor values are sent via FPort=3.

image-20240510144912-1.png 

Each data entry is 11 bytes. To save airtime and battery, the maximum payload size is depending on the current Date Rate and the frequency band.  For example, in US915 band, the maximum payload for different DR is as follows:

  1. DR0: maximum payload is 11 bytes. The device will uplink one entry of data.
  2. DR1: maximum payload is 53 bytes. The device will upload 4 entries of data (total of 44 bytes)
  3. DR2: A payload includes 11 entries of data
  4. DR3: A payload includes 22 entries of data.

Note: The PB01 will save 178 sets of historical data. If the device doesn't have any data during the polling time, it will uplink 11 bytes of 0s.

See Datalog feature for more information.

  

2.4.4  Decoder in TTN V3

In the LoRaWAN protocol, the uplink payload uses HEX format to store data. You need to add a payload formatter or decoder in the LoRaWAN server to extract each field and convert them into readable values.

The following figure shows how to add the uplink payload formatter in The Things Stack. The uplink decoder for PB01 can be found here:  https://github.com/dragino/dragino-end-node-decoder

image-20240507162814-16.png

2.5 Show data on Datacake

Datacake IoT platform provides a human friendly interface to show the sensor data in charts, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:

 

Step 1:  Be sure that your device is programmed and properly connected to the LoRaWAN network.

Step 2:  Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console --> Applications --> Integrations --> Add Integrations.

1. Add Datacake:

2. Select default key as Access Key:

3. In Datacake console (https://datacake.co/) , add PB01:

 Please refer to the figure below.

image-20240510150924-2.png

Log in to DATACAKE, copy the API under the account.

image-20240510151944-3.png

image-20240510152150-4.png

image-20240510152300-5.png

image-20240510152355-6.png

image-20240510152542-8.png

image-20240510152634-9.png

image-20240510152809-10.png

image-20240510153934-14.png

image-20240510153435-12.png

Copy and paste the TTN decoder here and save.

image-20240510153624-13.png

Visual widgets please read the DATACAKE documentation.

  

2.6  Datalog Feature

To retrieve a sensor value, you can send a poll command from the network server to request the sensor to send the value within the required time period.

2.6.1  Unix Timestamp

The Unix timestamp indicates the sampling time of the uplink payload, based on the following format:

image-20220523001219-11.png

You can get this time from the link:  https://www.epochconverter.com/ :

For example, if the Unix timestamp is in HEX format as 0x60137afd, you can convert it to decimal: 1611889405, and then convert it to the time: 2021-Jan-29, Friday, 03:03:25 (GMT).

1655782409139-256.png

2.6.2  Poll sensor value

You can poll sensor values based on timestamps from the server. The start and end timestamps use the Unix timestamp format as mentioned above. The device will reply with all data logs from this time period, using the uplink interval.

For example, if the downlink command is: image-20220621113526-13.png  

0x31 : Prefix

0x5FC5F350 and 0x5FC60160 : This is equivalent to checking the stored data between 2020/12/1 07:40:00 and 2020/12/1 08:40:00.

0x05 : The uplink interval is 5 seconds, which means the PB01 will send one packet every 5 seconds. The uplink interval can be mentioned in the downlink payload with a range of 5 to 255 seconds.

2.6.3  Datalog Uplink payload

See Uplink FPort=3, Datalog sensor value

   

2.7  Buttons

  • ACT button

Long press this button, and the PB01 will reset and rejoin the network.

image-20240510161626-17.png

  • Alarm button

Press this button to immediately send an uplink, and the alarm will be set to 'TRUE'.

image-20240705095149-5.png 

2.8  LED Indicators

The PB01 has a single LED that displays different colors to indicate various stages:

  1. Hold the ACT button: The LED will light up GREEN. GREEN flashing indicates the node is restarting. A BLUE flash signals a request for network access, and a solid GREEN light for 5 seconds signifies successful network access.
  2. Normal Working State:

    • When the node restarts, hold the ACT button, and the LED will turn GREEN. GREEN flashing indicates a restart. A BLUE flash signals a request for network access, and a solid GREEN light for 5 seconds indicates successful network access.
  3. During OTAA Join:

    • For each Join Request uplink, the LED will blink GREEN once.
    • Once the join is successful, the LED will remain solid GREEN for 5 seconds.
    • After joining, for each uplink, the LED will blink either BLUE or GREEN.
  4. Alarm Button:

    • When the alarm button is pressed, the LED will flash RED until the node receives an acknowledgment (ACK) from the platform, followed by the LED staying BLUE for 5 seconds.

 

2.9  Buzzer

The PB01 produces different sounds or tones for the following events, which can be turned on or off using the AT+SOUND command.

  • Button Sound: This is the tone produced by the node after the alarm button is pressed. Users can use the AT+OPTION command to set different button sounds.
  • ACK Sound: This is the notification tone emitted when the node receives an acknowledgment (ACK).

3.  Configure PB01 via AT command or LoRaWAN downlink

You can configure PB01 via AT Commands or LoRaWAN Downlinks.

  • See FAQ to find out how to connect PB01 with a computer to configure it using AT commands.

 

There are two types of commands to configure the PB01:

  1. General Commands:
    These commands are used to configure:

    • General system settings, such as the uplink interval.
    • LoRaWAN protocol and radio-related parameters.

    These commands are the same for all Dragino devices that support the DLWS-005 LoRaWAN stack (Note**). You can find these commands on the wiki: End Device Downlink Command.

  2. Commands Specifically Designed for PB01:
    These commands are valid only for the PB01, as listed below (see Downlink Commands):

3.1  Downlink Commands

Command ExampleFunctionResponseDownlink
AT+TDC=?

Get the current TDC (uplink) time

1200000
OK

Default 1200000(ms)
AT+TDC=300000Set the TDC (uplink) timeOK

0X0100012C:
01: fixed command
00012C: 0X00012C=300(seconds)

 

ATZReset the node 0x04FF
AT+FDRRestore to factory settings 0X04FE
AT+CFM=?View the current confirmation mode status

0,7,0

OK

Default 0,7,0
AT+CFM=1,7,1

Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry

OK

05010701

05: fixed command

01:confirmed uplink

07: retry 7 times

01: fcnt count plus 1

AT+NJM=?

Check the current network connection method

1
OK

Default 1
AT+NJM=0Change the network connection method to ABP

Attention:Take effect after ATZ
OK

0X2000: ABP
0x2001: OTAA
20: fixed command 

AT+RPL=?View current RPL settings

0
OK

Default 0
AT+RPL=1set RPL=1    OK

0x2101:
21: fixed command
01: for details, check wiki

AT+ADR=?View current ADR status

1
OK

Default 0
AT+ADR=0Set the ADR state to offOK

0x2200: close
0x2201: open
22: fixed command

AT+DR=?View the current DR settingsOK 
AT+DR=1

set DR to 1
It takes effect only when ADR=0

OK

0X22000101:
00: ADR=0
01: DR=1
01: TXP=1
22: fixed command

AT+TXP=?View the current TXPOK 
AT+TXP=1

set TXP to 1
It takes effect only when ADR=0

OK

0X22000101:
00: ADR=0
01: DR=1
01: TXP=1
22: fixed command

AT+RJTDC=10Set RJTDC time intervalOK

0X26000A:
26: fixed command
000A: 0X000A=10(min)
for details, check wiki

 

____________________________

Retrieve stored data for a specified period of time

 

 

0X3161DE7C7061DE8A800A:
31: fixed command
61DE7C70:0X61DE7C70=2022/1/12 15:00:00
61DE8A80:0X61DE8A80=2022/1/12 16:00:00
0A: 0X0A=10(second)
View details 2.6.2 

AT+DDETECT=?View the current DDETECT setting status and time

1,1440,2880
OK

Default 1,1440,2880(min)
AT+DDETECT=

1,1440,2880

Set DDETECT setting status and time
(When the node does not receive the downlink packet within the set time, it will re-enter the network)

OK

0X320005A0: close
0X320105A0: open
32: fixed command
05A0: 0X05A0=1440(min)

3.2  Set Password

Feature: Set the device password with a maximum of 9 digits.

AT command

CommandAT+PWORD
Parameterspassword : maximum up to 9 digits
GetAT+PWORD=?
Response

Returns the current password

OK

SetAT+PWORD=<password>
ResponseOK
Example

AT+PWORD=999999999

Set the password 999999999

Downlink command

There is no downlink command for this feature.

3.3  Set button sound and ACK sound

Feature: Turn on/off button sound and ACK alarm.

AT command

CommandAT+SOUND
Parameters

button_sound

0 - off

1 - on

ack_sound

0 - off

1 - on

GetAT+SOUND=?
Response

Returns the current sound settings. <button_sound>,<ack_sound>

OK

Set

AT+SOUND=<button_sound>,<ack_sound>

ResponseOK
Example

AT+SOUND=0,1

This will turn off the button sound and turn on the ACK sound.

Downlink command

Prefix0xA1
Parameters

button_sound : 1 byte in hexadecimal.

00 - off

01 - on

ack_sound : 1 byte in hexadecimal.

00 - off

01 - on

Payload format<prefix><button_sound><ack_sound>
Example

A10001

Turn off the button sound and turn on ACK sound.

3.4  Set buzzer music type (0~4)

Feature: Set different alarm key response sounds.There are five different types of button music.

AT Command

CommandAT+OPTION
Parameters

<buzzer_music_type> :

0

1

2

3

GetAT+OPTION=?
Response

Return the current music type.

OK

SetAT+OPTION=<buzzer_music_type>
ResponseOK
Example

AT+OPTION=1

Set the buzzer music to type 1

Downlink command

Prefix0xA3
Parameters

<buzzer_music_type> : 1 byte in hexadecimal

0

1

2

3

Payload format<prefix><buzzer_music-type>
Example

A300

Set the buzzer music to type 0.

3.5  Set Valid Push Time

Feature: Set the holding time for pressing the alarm button to avoid accidental activation. The values range from 0 to 1000 ms.

AT Command: AT+STIME

Command ExampleFunctionResponse

AT+STIME=?

Get the button sound time

0
OK 

AT+STIME=1000

Set the button sound time to 1000msOK

Downlink Command: 0xA2

Format: Command Code (0xA2) followed by 2 bytes mode value.

  • Example: Downlink Payload: A203E8                 // Set AT+STIME=1000   

          Explain: Hold the alarm button for 10 seconds before the node will send the alarm packet.

4.  Battery

PB01 uses 2xAAA LR03 (1.5V) batteries.

4.1  Replacing batteries

If the batteries are running low (if the battery voltage drops to 2.1V), you can use any two generic AAA batteries to replace them.

Note: 

1. The PB01 doesn't have any screws; you can use a nail to open the battery cover.

image-20220621143535-5.png  

2. Make sure the direction is correct when installing the AAA batteries.

image-20220621143535-6.png

4.2  Power Consumption Analysis

Dragino's battery-powered products all operate in Low Power mode. We provide an updated battery calculator based on real device measurements. You can use this calculator to estimate battery life and calculate it for different transmission intervals.

Instructions for use:

Step 1: Download the latest version of the DRAGINO_Battery_Life_Prediction_Table.xlsx from the battery calculator.

Step 2: Open the file and select:

  • Product Model
  • Uplink Interval
  • Working Mode

The expected battery life for different scenarios will be displayed on the right.

image-20220621143643-7.png

5.  Accessories

  • AS-02 USB Type-C Converter

    The AS-02 is an optional accessory. It is a USB Type-C converter that provides access to the AT console of the PB01 when used with a USB-TTL adapter. For more details, see this link.

image-20220621141724-3.png

6.  FAQ

6.1  How to use AT Commands to configure PB01

PB01 supports the AT Command set. Users can use a USB-to-TTL adapter along with the AS-02 USB Type-C converter to connect to the PB01 and issue AT commands, as shown below.

image-20240511085914-1.png

Connection:

  • USB to TTL GND <--> Program Converter GND pin
  • USB to TTL RXD  <--> Program Converter D+ pin
  • USB to TTL TXD  <--> Program Converter A11 pin

 

On the PC, you need to set the serial tool (such as PuTTY, SecureCRT) baud rate to 9600 to access the serial console for the PB01. The AT commands are disabled by default, and you need to enter the password (default: 123456) to activate them. The timeout for entering AT commands is 5 minutes; after 5 minutes, the user will need to enter the password again.

Enter the password 123456 and type "ATZ" to reboot the PB01, as shown below:

image-20240510174509-18.png

6.2  AT Commands

  • Sending "ATZ" will reboot the device.
  • Sending "AT+FDR" will restore the device to factory settings.
  • Get the device's AT command settings by sending "AT+CFG." The following is the output after issuing the AT+CFG command.

 

Sample output:                                            

AT+DEUI=FA 23 45 55 55 55 55 51

AT+APPEUI=FF AA 23 45 42 42 41 11

AT+APPKEY=AC D7 35 81 63 3C B6 05 F5 69 44 99 C1 12 BA 95

AT+DADDR=FFFFFFFF

AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

AT+ADR=1

AT+TXP=7

AT+DR=5

AT+DCS=0

AT+PNM=1

AT+RX2FQ=869525000

AT+RX2DR=0

AT+RX1DL=5000

AT+RX2DL=6000

AT+JN1DL=5000

AT+JN2DL=6000

AT+NJM=1

AT+NWKID=00 00 00 13

AT+FCU=61

AT+FCD=11

AT+CLASS=A

AT+NJS=1

AT+RECVB=0:

AT+RECV=

AT+VER=EU868 v1.0.0

AT+CFM=0,7,0

AT+SNR=0

AT+RSSI=0

AT+TDC=1200000

AT+PORT=2

AT+PWORD=123456

AT+CHS=0

AT+RX1WTO=24

AT+RX2WTO=6

AT+DECRYPT=0

AT+RJTDC=20

AT+RPL=0

AT+TIMESTAMP=systime= 2024/5/11 01:10:58 (1715389858)

AT+LEAPSEC=18

AT+SYNCMOD=1

AT+SYNCTDC=10

AT+SLEEP=0

AT+ATDC=1

AT+UUID=003C0C53013259E0

AT+DDETECT=1,1440,2880

AT+SETMAXNBTRANS=1,0

AT+DISFCNTCHECK=0

AT+DISMACANS=0

AT+PNACKMD=0

AT+SOUND=0,0

AT+STIME=0

AT+OPTION=3

 

Example:

image-20240511091518-2.png

6.3  How to upgrade the firmware?

PB01 requires a USB-to-TTL adapter along with the AS-02 USB Type-C converter to upload a new firmware image to PB01: Upgrading the device firmware,

  • supports new features
  • fixes bugs
  • allows change the LoRaWAN frequency bands.

The PB01 is shipped with firmware preloaded. The firmware is divided into a bootloader and a work program.

If the bootloader is erased for any reason, you will need to download the firmware (which includes both the bootloader and the work program).

The latest firmware version for the PB01 can be downloaded from this link: firmware

6.3.1 Update firmware (Assume device have bootloader)

Follow the steps below only if the firmware needs to be updated and the bootloader of your device is not corrupted and is working properly.

Step 1: Connect UART as per FAQ 6.1

Step 2: Update follow Instruction for update via DraginoSensorManagerUtility.exe

6.3.2 Update firmware (Assume device doesn't have bootloader)

Follow the steps below if the firmware needs to be updated along with the bootloader. This method is required if the bootloader of your device is corrupted.

Download both the bootloader and the worker program. After updating the firmware, the device will have the bootloader installed, allowing you to use the above 6.3.1 method to update the worker program.

Step 1: Install TremoProgrammer  first.

image-20220615170542-5.png

Step 2: Hardware Connection 

Connect PC and PB01 via USB-TTL adapter .

Note: To download firmware in this way, you need to pull the boot pin(Program Converter D- pin) high to enter the burn mode. After burning, disconnect the boot pin of the node and the 3V3 pin of the USB-TTL adapter, and reset the node to exit the burning mode.

Connection:

  • USB-TTL GND <--> Program Converter GND pin
  • USB-TTL RXD  <--> Program Converter D+ pin
  • USB-TTL TXD  <--> Program Converter A11 pin
  • USB-TTL 3V3  <--> Program Converter D- pin

Step 3: Select the device port to be connected, baud rate and bin file to be downloaded.

image-20240701160913-1.png

Users need to reset the node to start downloading the program.
1. Reinstall the battery to reset the node
2. Hold down the ACT button to reset the node (see 2.7 ).

When this interface appears, it indicates that the download has been completed.

image-20240701160924-2.png

Finally, Disconnect Program Converter D- pin, reset the node again , and the node exits burning mode.

6.4  How to change the LoRa Frequency Bands/Region?

If you want to change the frequency band/region of your device, the only way is to upgrade its firmware to support the desired frequency band/region. When downloading the firmware, ensure you choose the correct image that supports the required frequency band/region.

We have named each firmware file to make it easy for you to identify its frequency band/region. For example, for the EU868 band, the file name is eu868.bin. You can follow the instructions in the section how to upgrade image to complete the process.

6.5 Why i see different working temperature for the device?

The working temperature range of device depends on the battery user choose.

  • Normal AAA Battery can support -10 ~ 50°C working range.
  • Special AAA battery can support -40 ~ 60 °C working range. For example: Energizer L92

7.  Ordering Information

7.1  PB01

Part Number: PB01-LW-XX (white button) / PB01-LR-XX(Red Button)

XX : The default frequency band

  • AS923LoRaWAN AS923 band
  • AU915LoRaWAN AU915 band
  • EU433LoRaWAN EU433 band
  • EU868: LoRaWAN EU868 band
  • KR920LoRaWAN KR920 band
  • US915LoRaWAN US915 band
  • IN865:  LoRaWAN IN865 band
  • CN470LoRaWAN CN470 band

7.  Packaging Information

Package Includes:

  • PB01 LoRaWAN Push Button x 1

8.  Support

  • Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
  • Please provide as much information as possible regarding your inquiry (e.g., product models, an accurate description of your problem, and steps to replicate it) and send an email to support@dragino.com.

9.  Reference material

10.  FCC Warning

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

(1) This device may not cause harmful interference;
(2) This device must accept any interference received, including interference that may cause undesired operation.

 

Tags:
    
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0