Ursalink Software & Firmware Release Note

 

UrsalinkVPN, Ursalink DeviceHub, Toolbox, and more

Version 1.19

What’s new:

  1. CO2 and TVOC area on e-ink screen displays alert icon for AM102, and alert threshold is configurable.
  2. ToolBox for Android and iOS can read and display uptime from device.
  3. Spread factor is open to set when ADR is not enabled.

Optimized:

  1. ACK confirm counter is open to set between 4 to 32 (default) in network RE-join mechanism.
  2. Frequency usage to join LoRa network for CN470 devices when the user doesn’t set certain channel mask. UC11-N1 will use channel 8~15 for the first 16 times trials, channel 80~87 for the second 16 trials, and then go through all channels 0~95.
  3. For CO2 reading less than 600, each dot in column histogram stands for 50 ppm, otherwise each dot stands for 25 ppm for more critical situation and easier visual judgement.

Removed:

  1. Lock time and continue time for threshold of temperature and humidity.

Bugs fixed:

  1. Modification in channel index might fail.
  2. Reboot caused by stack overflow.

Version 1.17

  • Device with this version automatically shuts down when the power reaches 0% and requires battery level above 30% to restart.

Added:

  1. Three new screen display modes. You can switch by pressing then releasing the reset button, or ToolBox v6.15. Different mode displays different content.

Optimized:

  1. Enable automatical calibration of CO2 reading every 180 hours. The calibration is carried out by the sensor itself and independent from manual calibration by ToolBox.

Fixed:

  1. Light sensor reading was 0 under sunlight.
  2. DevEUI might be over-written during NFC configuration.
  3. CO2 sensor reading might be wrong and rebooting didn’t help unless battery reached 0% or was changed. This bug was caused by collecting CO2 during TVOC initialization, CO2 collection should wait until TVOC initialization is completed.
  4. Restart because of interrupt PIR collection.

Version 1.14

Added:

  1. DevStatusReq mac-command specified by LoRaWAN® protocol to request battery level.
  2. Configurable LoRaWAN version.

Optimized:

  1. Refresh e-ink screen on the hour and the half-hour.
  2. Synchronize timestamp every 5 days from Network Server.

Fixed:

  1. If the sensor was rebooted frequently it might report 0% battery.
  2. Time slowed down due to watchdog rebooting.
  3. Occasional black screen

Version 1.12

Added:

  1. AM100 Series is compatible with ASR LORA module now.

Optimized:

  1. Joining network uses DR_2 now.

Fixed:

  1. Abnormal NFC reading and writing, exceptional screen display might occur when battery voltage was low (<2V).
  2. NFC couldn’t read the correct on/off state when the program is writing flash

Version 1.11

Added:
  1. Temperature display on e-ink screen supports Fahrenheit.

Version 1.10

Initial version for AM10x.

Version 1.15

Added:

  1. DevStatusReq mac-command specified by LoRaWAN® protocol to request battery level.
  2. Configurable LoRaWAN version.

Version 1.14

Fixed:
  1. When device was connected via USB cable, NFC didn’t function.
  2. Exceptional reboot.
  3. NFC couldn’t read the correct on/off state when the program is writing flash.

Version 1.12

Initial version for EM500 series

Version 2.0.19

  • It’s NOT recommended to parallel install UrsalinkVPN and DeviceHub

Added:

  1. Remote upgrade and batch configuration for UR75-EDGE.

Fixed:

  1. Devices can’t connect due to characters in device sn.

Version 2.0.17

  • It’s NOT recommended to parallel install UrsalinkVPN and DeviceHub

Optimized:

    1. Alarm report

Version 2.0.15

Optimized:

  1. Users need only 1 command to complete the download of the installation package and firmware
  2. Clear logs regularly each day (logs that were written 2 weeks ago)
  3. Clear database regularly (clean statistics and GPS data)
  4. UR32 supports upgrade and provision in bulk

UR3x SDK Version 2.1.4

Python version: 2.7

UR5x SDK Version 2.1.5

Python version: 2.7

Matching firmware version for this SDK: 5x.2.0.54 and above.

Optimized:

  1. Supports to customize email content when DI meets the preset condition or duration.

UR7x SDK Version 2.1.5

Python version: 2.7

Matching firmware version for this SDK: x.2.0.54 and above.

Optimized:

  1. Supports customizing email content when DI meets the preset condition or duration.

UG85/87v2 SDK Version 1.1.12

Python version: 2.7

Initial version for UG8x.

Version 6.21

What’s New:

  1. Support NFC read-write configuration of EM500-SWL-L050.
  2. Simplified Chinese mode.

Optimized:

  1. Timezone calculation for UC11/UC3x “Commands”.

Bugs Fixed:

  1. “-” couldn’t be saved in APN for UC3x.
  2. When AM10x was turned off, older version displayed “on” as status.
  3. LinkWAN version devices should not upgrade to standard version or vice versa.
  4. Wrong prompt note on “Status” after device was connected.
  5. Failure in reading saved configuration on “Command” for UC11.
  6. Some typo.
  7. Inactive setting available to change on certain models.
  8. Failure in reading saved configuration on “LoRaWAN Settings>Channels”.

Version 6.18

What’s New:

  1. Support NFC read&write configuration of EM500-CO2/EM500-LGT/EM500-SWL (gauge pressure)/EM500-PP/EM500-SMT-MEC20.
  2. Add timeout limitation in reading attributes. The “Read Channel failed” will not pop up in this version and later.
  3. Power output time on “General>AI” is limited to 0-5000 ms.
  4. Reporting interval on “General>Basic” is limited to 60-65535 sec.

Bug Fixed:

  1. “Application Mode” interface might not display or function normally when USB disconnected from UC1152 and connected to UC3x without restart.
  2. Registers quantity could changed when register type was Coil/Discrete/Input Register(INT16)/Holding Register(16), while the RS485 master can only read 1.
  3. The height of RS232 parameter blocks might be too small to display clearly when ToolBox was running on certain models of Windows computer.
  4. Data polling interval might fail to program into UC1152.
  5. Alignment might be wrong on “General” page of UC1152.
  6. Some typos.
  7. Channel index might fail to write into LoRa devices.
  8. If any threshold on “Device Settings>Basic” was left blank for infinity, it might be read as 0.

Removed:

  1. Data polling interval input block on “General>AI” of UC11-N1 will not appear when the firmware version is higher than 2.07 (included).

Version 6.13

Added:

  1. Configurable LoRaWAN version.

Version 6.12

Fixed:

  1. “Power On/Off” button didn’t take effect.
  2. “Status” page remained blank.

Version 6.10

Added:

  1. Supports NFC configuration

Version 5.21

Added:

  1. ADR switch on “LoRaWAN>Basic”.

Fixed:

  1. Blank “General” after clicking “Save the Commands as a File”.
  2. Remove calibration-related options when the device is not UC11-T1.
  3. MQTT user credential tick problem

Version 5.20

Added:

  1. Channel Mask of connected gateway on Status page for UC11-T1
  2. Temperature display in Fahrenheit on Status page for UC11-T1
  3. Calibration permit for UC11-T1
  4. RS232 option on Serial page for UC11-N1
  5. Serial Baud rate 1200, 2400 for UC11-N1
  6. Counter mode in GPIO2 for UC11-N1
  7. Alterable App Port and RS232 Port
  8. Channel Mask, Counter, Uplink Count, Downlink Count Display on Status page

Fixed:

  1. Time display error on Status page for UC3xxx

Version 5.16

Added:

  1. Support English punctuations in APN

Fixed:

  1. Negtive number display problem in SNR

Version 5.12

Added:

  1. input_32, input_int32_AB, hold_int32_CD, input_float datatype for Modbus of UC11-N1/UC1152/UC3x52/UC3552
  2. Add “-DC” for DC version of UC11-N1

Optimized:

  1. Support NB node device
  2. Optimize regular report timing/poll serial ports timing/AI collection timing
  3. Work on 32-bit computer

Version 5.6

Altered:

  1. AI signal collection type was changed to: 0-10V

Version 5.2

  • ToolBox_Sensor was merged with ToolBox_IO

Added:

  1. ABP activation

Optimized:

  • Packet confirmation mechanism, to reduce unnecessary retransmissions and power consumption.
  • Details are as follows:
  • When the device sends a timed report packet (requires ACK) to the NS, if the ACK of the other party is not received, the packet is retransmitted at most three times.
  • When the device sends an attribute packet (requires ACK) to the NS, if the ACK of the other party is not received, the packet will be retransmitted.
  • When the device sends an alarm packet (requires ACK) to the NS, if the ACK of the other party is not received, the packet is retransmitted up to three times.

Fixed:

  1. Some bugs

Version 4.28

Added:

  1. Check log via USB
  2. Modbus RS485 LoRaWAN function of UC1152
  3. “Acquire” button on interface of UC1152 to help users to acquire the newest channel data when configuring RS485 function

Optimized:

  1. Data package reporting format and decreased package size and package loss rate

Version 4.24

Optimized:

  1. Network access rate (SF=12, 11, 10)
  2. Processing mechanism when the network fails to reduce power consumption

Fixed:

  1. KR920 can’t receive data
  2. LoRa sends timeout when ChannelsNbRep is greater than 1
  3. Entering the low power probability and causing the system to restart

Version 1.2

Added:

  1. Configurable LoRaWAN version.

Version 1.1.10

Added:

  1. Supports temperature display in Fahrenheit.
  2. Pressure value displayed on “Status” and “Calibration Settings” calculates to nearest tenth.

Fixed:

  1. Changing temperature unit caused temperature value conversion on “Status” page, but the unit display on “Status” remains the former one.

Version 1.1.9

The initial version

UC11xx Version 2.0.16

Optimized:

  1. First 3 bytes of DevEUI are fixed as “24E124”, last 5 bytes are fixed as SN without the first and the last digit.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Ursalink gateways first. If it fails for 32 times (about 6 min), change to use LoRaWAN standard specification.

UC11xx Version 2.0.15

Fixed:

  1. Time error caused by RTC cycle
  2. 8 byte limit in Modbus transparent transmittion

UC11xx Version 2.0.13

Added:

  1. Input Registers (INT32) /Input Registers (Float) /Input Register (INT 32 with upper 16 bits) /Input Register (INT 32 with lower 16 bits) /Holding Register (INT 32 with upper 16 bits) /Holding Register (INT 32 with lower 16 bits)
  2. Frequency plan is changeable in between
    1. For 868 module: EU868, IN868, RU864
    2. For 915 module: US915, AU915, KR920, AS923

Altered:

  1. Channel mask restores to default after ACK fails

Fixed:

  1. Fix frame count error related bug

UC11xx Version 2.0.7

Added:

  1. ABP method

Optimized:

  1. Allow Modbus Slave ID more than 16
  2. DO performance

Version 2.15

Optimized:

  1. Stability in querying Modbus slaves.

Bug fixed:

  1. Pulse counter increased even though connection was idle.

Version 2.11

What’s new:

  1. Obtain battery level using LoRaWAN MAC command.

Optimized:

  1. Modbus stability with unstable external power source.
  2. Program stability with exceptional power loss when upgrading.
  3. Frequency usage to join LoRa network for CN470 devices when the user doesn’t set certain channel mask. UC11-N1 will use channel 8~15 for the first 16 times trials, channel 80~87 for the second 16 trials, and then go through all channel 0~95.

Bugs fixed:

  1. Modbus queries might fail.
  2. Deleting Modbus channel might not take effect or require user to save again.
  3. Program would restart when USB disconnected.
  4. Device might go to reboot if many Modbus channels were in use and device needed to transmit a data volume that was too large.
  5. When “Power Output Time Before Collect” was enabled, power outsourcing time might exceed and continue when user manually click “fetch”.
  6. When writing in flash, device essencial parameters might be erased if power supply was cut out. This could lead to model reading failure on ToolBox.

Version 2.07

  • Resetting is required if UC11-N1 upgrade from 1.44 and lower.
  • ToolBox v6.12 and more supports on/off switch while UC11-N1 is in shutdown mode.

Added:

  • LoRaWAN duty cycle function.
  • USB switch function code, users can use the switch button on the ToolBox status page to switch on and off.
  • Newly added setting items to provide equipment to restore power supply status.

Optimized:

  • Modify the lora configuration from the original restart device to modify the lora configuration to only restart the lora module; when the modification mode (ABP/OTAA), frequency band is saved, the device will only be restarted when it is saved.
  • USB detection process.
  • Power consumption optimization, modification of power calculation method.
  • All collection cycles of N1 are changed to be consistent with the reporting cycle, and ToolBox removes the collection cycle configuration items.

Fixed:

  • Unable to send data because of LoRa reload under RU864 ABP mode.
  • Unable to enter low power consumption after 1 hour without access to the network.
  • Fixed the problem of abnormal ToolBox working under Windows 7.

Version 1.44

  • Resetting may be required if UC11-N1 upgrade from 1.37 and lower.
Optimized:
  1. Switch mechanism and sleep program.

Version 1.40

  • Resetting may be required after upgrade

Added:

  1. Supports restoring to the state before shutdown (configurable in Toolbox v6.8). Default mode is off for unchargeable model; default mode is on and will restore to the state before shutdown for DC model.

Optimized:

  1. Shorter device turn-off time from 6 seconds to 2 seconds when attaching a magnet to the device. If the device beeps for 2 seconds, it is powered on. If the device beeps for 6 seconds, it is powered off. Magnet can be moved away during beeping.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Ursalink gateways first. If it fails for 32 times (about 6 min), use LoRaWAN standard specification instead.

Fixed:

  1. Problem in joining network when devices are connected by USB.
  2. Battery calculation didn’t include join requests.

Version 1.36

  • Resetting may be required after upgrade

Optimized:

  1. First 3 bytes of DevEUI are fixed as “24E124”, last 5 bytes are fixed as SN without the first and the last digit.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Ursalink gateways first. If it fails for 32 times (about 6 min), use LoRaWAN standard specification instead.

Version 1.31

  • Resetting may be required after upgrade

Added:

  1. Support RS232 in Serial
  2. Support Baud rate 1200, 2400
  3. Counter mode in GPIO2 port for DC version
  4. Alterable App Port and RS232 Port
  5. Channel Mask, Counter, Uplink Count, Downlink Count Display on Status page

Optimized:

  1. When a channel didn’t read data, Cloud displays “-” rather than the latest data reported from UC11-N1.
  2. Possible error in Modbus RTU function code and CRC

Removed:

  1. Low power consumption mode for DC version

Version 1.27

  • Need reset after upgrade to this version

Added:

  1. Support to switch frequency in between
    • Alterable channels for 868: EU868/IN868/RU864
    • Alterable channels for 915: US915/AU915/KR915/AS923
  2. Data type input_int32/input_float for modbus readable data
  3. Display GPIO status in regular uplink packet

Optimized:

  1. Support bootloader upgrade
  2. Optimize power-effective working mode
  3. Optimize DO control

Fixed:

  1. Fix repeated uplink when controlling GPIO from cloud

Version 1.23

Optimized:

  1. Battery performance

Fixed:

  1. No-beep problem (need to burn this version to take effect)

Version 2.05

Added:

  1. Duty Cycle in LoRaWAN configuration.
  2. Switching on/off (sleep mode) in ToolBox v6.12 and later; supports viewing and editing settings in sleep mode.

Optimized:

  1. Micro USB detection.
  2. Collecting interval is 20 seconds now.
  3. Power consumption.

Fixed:

  1. When device had dual power source via battery and USB, removing USB or battery might cause problems.
  2. If temperature threshold was left blank, action of reading would return 9999.

Version 1.34

Optimized:

  1. Power consumption when device transmits LoRa signal.

Version 1.30

Optimized:

  1. Success rate in joining network.
  2. Shorter device turn-off time from 6 seconds to 2 seconds when attaching a magnet to the device. If the device beeps for 2 seconds, it is powered on. If the device beeps for 6 seconds, it is powered off. Magnet can be moved away during beeping.
  3. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Ursalink gateways first. If it fails for 32 times (about 6 min), use LoRaWAN standard specification instead.

Fixed:

  1. Battery calculation didn’t include join requests.
  2. Problem in joining network when devices are connected by USB.

Version 1.27

Optimized:

  1. Turn off the 0% battery detection

Fixed:

  1. Repair possible restart at low temperature

Version 1.25

Optimized:

  1. First 3 bytes of DevEUI are fixed as “24E124”, last 5 bytes are fixed as SN without the first and the last digit.
  2. For devices using CN470/AU915/US915, when devices join network, use frequencies as defined in Ursalink gateways first. If it fails for 32 times (about 6 min), change to use LoRaWAN standard specification.
  3. Uplink 1 “0% battery” packet as soon as battery voltage is detected as less than 2.4V, then uplink an additional “0% battery” packet along with regular report.

Version 1.23

  • This version is only compatible with Toolbox 5.20 and above, you must reset the device after upgraded to this version.

Added:

  1. Calibration permit
  2. Channel Mask of connected gateway on Status page
  3. Temperature display in Fahrenheit on Status page
  4. Low battery detection. Report battery level as 0 when battery voltage is lower than 2.2V.

Version 1.20

  • This version is only compatible with Toolbox 5.12 and above, you must reset the device after upgraded to this version.

Added:

  1. Frequency plan is alterable in between
    1. For 868 module: EU868, IN868, RU864
    2. For 915 module: US915, AU915, KR920, AS923

Fixed:

  1. Some minor bugs

Version 1.19

Fixed:

  1. Failing to boot after a drastic shock
  2. Probable failing to jump from bootloader to application

Version 3.11

NOTE:

  • UC3x22/UC3x14 with firmware version 2.xx CANNOT upgrade to this version
  • Upgraded UC3x52 CANNOT be downgraded to version 2.xx

Added:

  1. Configurable APN for model UC35xx

Optimized:

  1. Prolong the time to 10 min when device waits for base station.
  2. Supports up to 128-bit-long APN.
  3. Time acquiry mechanism.
  4. UC35xx default “Keep Alive Interval” is changed to 300 sec when under Aliyun mode.

Fixed:

  1. Failure to upgrade by OTA when device is under Ursalink Cloud mode.
  2. Wrong device name when device is under MQTT mode.

Version 3.09

NOTE:

  • UC3x22/UC3x14 with firmware version 2.xx CANNOT upgrade to this version
  • Upgraded UC3x52 CANNOT downgrade to version 2.xx

Added:

  1. Configurable APN for model UC35xx

Optimized:

  1. Keep Alive Interval set as 120 seconds for default

Fixed:

  1. Failure in configuration when failing to connect to Aliyun

Version 3.08

NOTE:

  • UC3x22/UC3x14 with firmware version 2.xx CANNOT upgrade to this version
  • Upgraded UC3x52 CANNOT downgrade to version 2.xx

Added:

  1. NB module for model UC35xx
  2. Aliyun mode for model UC35xx
  3. Support Ursalink Cloud China

Version 2.20

  • You must use this version or above with Toolbox 5.12 or above

Added:

  1. Add Input Register (int32)/Input Register (float)/Input Register (int32 with upper 16 bits)/Input Register (int32 with lower 16 bits)/Holding Register (int32 with upper 16 bits)/Holding Register (int32 with lower 16 bits)

Altered:

  1. Time in commands is Greenwich time, local time in status is device local time
  2. Manual reboot after Keep Alive Interval was altered in Ursalink Cloud mode is not necessary

Optimized:

  1. Support AWS China cloud
  2. Optimize performance in joining network

Fixed:

  1. Fix local time disappearance in status in Toolbox after device joined network
  2. Fix continual reboot after Keep Alive Interval was altered in AWS mode

Version 2.19

Fixed:

  1. Downlink problem

UG85/87v2 Version 80.0.0.78

What’s new:

  1. Devices with freqencies CN470, US915 and AU915 come with default channel mask.

Optimized:

  1. The default tx power in NS is adjusted to maximum (CN470: 20dB; AU915: 27dB, EU868: 16dB, IN865: 27dB, KR920: 23dB, RU865: 16dB, US915: 27dB, AS923: 16dB).
  2. In Channel Mask setting the high bits of 0 will not be hidden after saving.
  3. For default spreading factors SF10, SF11, and SF12, gateway uses window 1 to downlink messages (take effect after reset).

Bugs fixed:

  1. When NS received data packets from two nodes at the same time, MQTT client would not report the first data packet, but sent two second packets.
  2. If a back up file of NS with registered end-devices is imported into a new gateway, the new gateway automatically becomes failover for the registered ones.
  3. Idle application saved an extra copy of related data packets for another application with MQTT enabled, which caused repeated data transmission.
  4. Too many file handles during DeviceHub connection.

UG85/87v2 Version 80.0.0.75

What’s new:

  1. Support WS86.

Optimized:

  1. “lastseen” value reported by Gateway to Ursalink Cloud will be more realistic  with second as minimal unit.

UG85/87v2 Version 80.0.0.74

Optimized:

  1. Default frequencies for CN470 model used to be 80~87 or 80~95 and now are 8~15 (8-channel model) or 0~15 (16-channel model).
  2. Default keep-alive interval for CN470 model is 10 seconds now.

Fixed:

  1. Exit route 0.0.0.0 might be lost after failover configuration on “Network>Link Failover>WAN Failover”.
  2. Invalid SSH connection might be set up to DeviceHub when SSH was not enabled.
  3. System would be constantly rebooting after a sudden power cut when installing postgressql.
  4. MQTT client might stop publishing messages after a while.
  5. End-devices might fail to join network when keep-alive interval on “Packet Forwarder>Advanced>Intervals Setting” was 3600 seconds.
  6. Localhost as a destination on “Packet Forwarder” might fail to start when switched on from ChirpStack.
  7. chirpstack-gateway-bridge was not saved in back-up file.

Removed:

  1. Network Mode on “Packet Forwarder>Advanced>Network Setting”.

UG85/87v2 Version 80.0.0.69

Added:

  1. LinkWAN option in multi-destination (CN470 only).

Optimized:

  1. Enable NAT by default.
  2. eMMC stability.
  3. Prolong timeout for custom payload codec.

Fixed:

  1. Illegal downlink topic when gateway connected to Azure via MQTT.
  2. admin account might fail to log in via SSH.
  3. GUI of some new devices only displayed pages related to Packet Forwarder and Maintenance, other pages remained blank and the device kept rebooting.

UG85/87v2 Version 80.0.0.66

Optimized:

  1. Loriot connection.

UG85/87v2 Version 80.0.0.65

Optimized:

  1. eMMC performance

UG85/87v2 Version 80.0.0.64

Added:

  1. Add devices in batch
  2. Display MQTT connection status.
  3. Support to use “$deveui” on uplink/ack/error/notification topics. E.g. : “/ursalink/uplink/$deveui” means to publish to “/ursalink/uplink/xxxxxxxxxxxx” according to the DevEUI in packet.
  4. Support to use “$deveui” on downlink topics. E.g. : “/ursalink/uplink/$deveui” means to publish to “/ursalink/uplink/xxxxxxxxxxxx” according to the DevEUI in packet.

Optimized:

  1. LoRaWAN uplink payload format.
  2. Pyuser user security issues.
  3. Shorten firmware upload time.

Fixed:

  1. System constantly reboots due to enabled IPSec.
  2. Cellular LED indicators switched.
  3. MQTT connection thread stuck resulting in failing to respond JnAcc.

UG85/87v2 Version 80.0.0.62

Added:

  1. Main interface set as cellular0 automatically in “Network>Link Failover>WAN Failover”.

Optimized:

  1. “Help” sidebar explanation.
  2. Default WAN static IP: 192.168.23.150, gateway: 192.168.23.1.

Fixed:

  1. Reconnect timeout extends to 6 sec when subscribing AWS MQTT service.

Removed:

  1. “LAN”, “PORT”, “VLAN Truck” tabs on “Network>Interface”.
  2. “4G First”, “3G First” options under “Network>Interface>Cellular”.

UG85/87v2 Version 80.0.3000.59.1

NOTE:

  • If you are using AU915 before upgrade, please change “Supported frequency” in “Packet Forwarder>Radios” to US915/AS923, “Save” and “Apply”, then change it back to AU915, “Save” and “Apply”.
  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

Altered:

  1. Upgrade Python 2.7 to Python 3.7 bundle and environment.

UG85/87v2 Version 80.0.0.59

NOTE:

  • If you are using AU915 before upgrade, please change “Supported frequency” in “Packet Forwarder>Radios” to US915/AS923, “Save” and “Apply”, then change it back to AU915, “Save” and “Apply”.

Added:

  1. Devices with GPS module will display GPS information on “Status>Overview”.
  2. “Basic Station” option as Packet Forwarder type.

Optimized:

  1. Cellular network problem with EG25 module.
  2. Optional Semtech server addresses. Reference
  3. Allow blank as password in MQTT user credentials

Fixed:

  1. AU915 connection problem with TTN.
  2. DeviceHub connection problem after reboot.
  3. False connection to Ursalink Cloud after constant switch.
  4. If Ursalink, Semtech, Chirpstack are all disabled on “Packet Forwarder>General”, buttons on “Packet Forwarder>Traffic” are enabled regardless of status of embedded network server; if TTN/Loriot/Chirpstack/Base Station is enabled, buttons are disabled.

Removed:

  1. “2G First”, “2G Only” options on “Network>Interface>Cellular”.

UG85/87v2 Version 80.0.0.53

NOTE:

  • Due to massive change on web GUI, please refresh the web page after upgrade.

Added:

  1. Support multi-destination (Ursalink, Semtech, TTN, Loriot, ChirpStack) for LoRa packets.
    • No other destination could be chosen when TTN, Loriot or Chirpstack is enabled.
  2. Support 16 channels under Ursalink/TTN/Semtech mode.
  3. Support frequency synchronization from localhost or NS (NOT applicable to ChirpStack).
  4. Support TLS validation without certificates.
  5. Increase length limit in MQTT user credentials.

Optimized:

  1. Logical relationships warning notes at different destinations on Packet Forwarder page.
  2. Frequency-Sync stays disabled when no destination is enabled.
  3. Ursalink Cloud on Network Server page.
  4. When LoRa radio on Packet Forwarder>Radios>Radio Channel Setting is changed, Channel Plan Setting on Network Server page changes automatically.
  5. When Ethernet port is set as WAN, disable DHCP.

Fixed:

  1. Default route lost when using cellular.
  2. Cannot connect to Loriot server after reboot.
  3. End-devices failed to activate after reboot.
  4. Default value of IN865 channels, failure in saving IN865 channels.
  5. Failure in scanning WLAN AP.

UG85/87v2 Version 80.0.0.49

Added:

  1. Support multi-destination (Ursalink, Semtech, TTN, Loriot, ChirpStack) for LoRa packets
    • No other destination could be chosen when Loriot or Chirpstack is enabled
  2. Support 16 channels under Ursalink/TTN/Semtech mode
  3. Support frequency synchronization from localhost or NS (NOT applicable to ChirpStack)
  4. Support TLS validation without certificates
  5. Increase length limit in MQTT user credentials

Fixed:

  1. Default route lost when using cellular

UG85/87v2 Version 80.0.3000.43.4

Note:

  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

Altered:

  • Upgraded Python 2.7 to Python 3.7 bundle and environment.

UG85/87v2 Version 80.0.3000.43.2

Note:

  • This version works exactly the same as 43.1 but is a springboard between 43.1 to 43.4 or higher Greengrass version.
  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

UG85/87v2 Version 80.0.3000.43.1

Note:

  • Resetting to factory defaults is must when upgrading from greengrass version to normal version.

Added:

  1. Greengrass related features.
  2. Python 2.7 bundle and environment.
  3. soft links are now saved in /etc/root/home (before were saved in /mnt/mmcblk0p1).
  4. When upgrading, backup system stays the same.

Altered:

  1. GRPC port from 8000 to 9000 to avoid conflict with Greengrass.
  2. Permission on system utility from read-only to read&write.

UG85/87v2 Version 80.0.0.43

Added:

  1. Allow blank or special characters in MQTT user credential

Fixed:

  1. Downlink conflict bug
  2. Cloud connection failure due to port mismatch

UG85/87v2 Version 80.0.0.39

Added:

  1. Display “-CH16” in 16-channelled gateway’s PN code

Optimized:

  1. Timezone synchronization mechanism

UG85/87v2 Version 80.0.0.38

Optimized:

  1. Support 16-ch module
  2. Optimize nodes’ network joining judgement

Fixed:

  1. Timezone problem in Packets of Network Server
  2. System time error after reboot

UG85/87v2 Version 80.0.0.35

Added:

  1. EG25-G module

UG87v1 Version 81.1.0.117

Optimized:

  1. Allow special characters in MQTT user credentials but not blank

Fixed:

  1. Downlink conflict

UG87v1 Version 81.1.0.115

Fixed:

  1. System timezone error and time display error in NS packets after upgrade when device local timezone is not UTC+8
  2. System time error due to device reboot
  3. Probable login failure due to altered password

UG87v1 Version 81.1.0.111

Added:

  1. Modbus RTU to TCP/Modbus RTU over TCP feature

UG87v1 Version 81.1.0.108

Fixed:

  1. MQTT related bug
  2. Frame count bug for device in ABP mode

UG87v1 Version 81.1.0.106

Added:

  1. Redis backup
  2. Subscription in MQTT client to downlink

Altered:

  1. Disable Frame-counter Validation as default

Fixed:

  1. SSH/Telnet access error when using WAN
  2. Multi clients bug to MQTT

3x.2.0.20

What’s new:

  1. Cellular module’s firmware on “Status>Cellular”.

Optimized:

  1. The maximum number of Wi-Fi clients is limited to 15, and the default number is 10.

Bugs fixed:

  1. When QoS download was stopped, upload might not stop.
  2. Wrong OpenVPN configuration might cause crash log and abnormal OpenVPN related process.
  3. Kernel dump problem when multiple Wi-Fi clients are connected
  4. When the OpenVPN authentication method was username + certificate, configuration file did not save with TLS authentication checked.

3x.1.0.63

Bugs fixed:

  1. SNMP MIB file loading failure.
  2. Failure in obtaining SNMP WAN port’s Gateway.
  3. DTU TCP-Server/UDP-Server mode (the select interval 10ms is incorrectly set to 10 nanoseconds) might cause CPU occupation up to 100%.
  4. Abnormal selection of the quagga caused by the vty handle not being closed normally.

Removed:

  1. Cellular Connection Setting configuration items in the SNMP MIB (because these configuration items are related to each other, and SNMP write operations can only be configured one by one).

3x.2.0.18

What’s new:

  1. Cellular speed and uptime interfaces in MIB.
  2. OpenVPN is upgraded from 2.4.0 to 2.4.9.

Bugs fixed:

  1. Reload counter was not reset after dialing succeeded, which led to a direct restart instead of reload in the next exception.
  2. If system recorded signal like “ICMP FAILED” while dialing, reload counter might not be reset and caused exception in next dialing action.
  3. Default route of cellular missed.
  4. Cellular network was normal but the signal lights were all off.
  5. CSQ99 event is prevented from triggerring the cellular module to redial now.
  6. Security issues.
  7. Expert options were not written into configuration.
  8. DI false alarm.
  9. After the OpenVPN Client was successfully connected, the status page displayed “Disconnect”.
  10. Network might not automatically recover when the AT command read and wrote abnormally under high temperature conditions.
  11. High CPU usage in DTU process caused in tcp_server and udp_server modes, the timeout setting of select was incorrectly set to 10 nanoseconds (expected to be 10 milliseconds).
  12. Hardware reset button might fail.
  13. Out-dated interfaces left in MIB.

3x.2.0.10

Added:

  1. “Network>Firewall>Port Mapping” allows 64 rules now.

Fixed:

  1. Major change in ubus interfaces led to possible failure in reading product and firmware information on “Status>Overview”

3x.2.0.8

Optimized:

  1. Quicker dialing under weak signal or other occasions that switching SIM cards is needed.

Fixed:

  1. cellular0 might obtain void address.

3x.2.0.6

Added:
  1. “Link in use” block on “Status>Overview”.
  2. Cellular signal strength bars on “Status>Cellular”, no bars for 0 asu.
  3. Cellular usage monthly statistics on “Status>Cellular”.
  4. “Satellites in Use”, “Satellites in View” data display on “Status>GPS”.
  5. AT commands debugger on “Maintenance>Debugger>Cellular Debugger”. NOTE: If debugger result is cleared, it can’t be downloaded as log file.
  6. Create firewall by typing in firewall rules on “Maintenance>Debugger>Firewall Debugger”, and to modify or delete a firewall rule is not supported.
  7. Daily, weekly, monthly reboot cycle to achieve more flexible reboot schedule.
Modified:
  1. Link failover is moved from “Network>Link Failover>WAN Failover” to “Network >Interface>Link Failover” and integrated with the switch to enable or disable each interface.
  2. Order of “Network” settings on left navigation panel are “Network>Interface, DHCP, Firewall, QoS, VPN, IP Passthrough, Routing, VRRP, DDNS” now.
  3. Order of “System” settings on left navigation panel are “System>General Settings, Phone & SMS, User Management, SNMP, AAA, Device Management, Events” now.
Optimized:
  1. NTP server and client are separated.
  2. Add “Choose All” checkbox for each column on “System>Events>Events Setting”.
Fixed:
  1. PPPoE password encryption.
  2. NAT is enabled by default and cannot be disabled.

3x.1.0.61

Fixed:

  1. UR32 WAN NAT does not take effect after being disabled
  2. After the WAN port nat is enabled or disabled, the ping operation cannot take effect immediately
  3. EG25 occasionally can’t register the Internet

Optimized:

  1. Encrypt pppoe related password under admin account
  2. pyuser user security issues
  3. Shorten firmware upload time
  4. Python SDK installation prompts version mismatch problem

3x.1.0.58

Added:

  1. References counter in SLA/Track. Rules can’t be deleted when referred to.

Optimized:

  1. Reload automatically when recording qxdmlog.
  2. Request timeout time to connect to DeviceHub is extended to 10 sec.
  3. Multiple IP addresses of same subnet are allowed in bridge IP configuration
  4. Length limitation of DDNS password: 1-256.
  5. CPU 100% occupied by DeviceHub remote access.
  6. Reboot VPN clients when default route switches.

Fixed:

  1. Only 1 serial port could be read while 2 ports are using DTU-Modbus.
  2. Default port missing in static routing configuration while WAN is using PPPoE.
  3. Failed to download log file with http.
  4. False connection to DeviceHub when the device is not removed from previous account.
  5. Fail to delete phone group when it’s referred by a deleted event.
  6. Cancel email notifications or SMSs after reference is diabled

3x.1.0.48

Fixed:

  1. Default route missing
  2. The middle indicator of UR32 SIM signal LED keeps staticly on
  3. Telstra private network connection failure
  4. IPsec client cannot be pinged by server subnet
  5. Cellular connection failure problem because of SMS center redialing
  6. RS232 serial port error in first usage

Altered:

  1. Remove “4G first”, “3G first”, “2G first” options in cellular configuration page

3x.1.0.42

Fixed:

  1. Default route missing problem

3x.1.0.38&39

Added:

  1. DI edge trigger

Fixed:

  1. Even parity bug in RS232

3x.1.0.35

Fixed:

  1. TCP connection bug under FTP mode
  2. Static route missing after track recovery

Optimized:

  1. Distribute different track ID for each static route

Version 3.0.41

Fixed:

  1. Pyuser user security issues
  2. Shorten firmware upload time

Optimized:

  1. Add PN into Model, which displays on “Status>Overview”

Version 3.0.40

Fixed:

  1. Error caused by urtool -b when programming commands

Version 3.0.39

Added:

  1. References counter in SLA/Track. Rules can’t be deleted when referred to.

Optimized:

  1. Firmware upgrade can only be used within its own product series.
  2. Remove “This SDK does not match the current firmware version, please upgrade the Python SDK” after imported successfully.
  3. Remove “I/O error” after Python app with name containing special characters or numbers is imported.
  4. Remove unnecessary blank space on RS232 configuration.
  5. Stablize AppManager status.
  6. Request timeout time to connect to DeviceHub is extended to 10 sec.
  7. Multiple IP addresses of same subnet are allowed in bridge IP configuration
  8. Length limitation of DDNS password: 1-256.
  9. CPU 100% occupied by DeviceHub remote access.
  10. Reboot VPN clients when default route switches.

Fixed:

  1. Only 1 serial port could be read while 2 ports are using serial ports as RS485.
  2. Default port missing in static routing configuration while WAN is using PPPoE.
  3. When use PPPoE to access Internet with default netmask, default route was displayed as inactive and 2 bridge IP were displayed.
  4. When using PPPoE to access Internet, default interface displayed as “wan” without “pppoe” option.
  5. Failed to download log file with http.
  6. False connection to DeviceHub when the device is not removed from previous account.
  7. Fail to delete phone group when it’s referred by a deleted event.
  8. Cancel email notifications or SMSs after reference is diabled
  9. “3G-Only”, “4G-Only” cannot be taken into effect with LongSung module.
  10. When using L2TP routing, the connection cannot automatically restore after disconnect to Internet.
  11. Fail to connect to DeviceHub after hardware reboot.
  12. Possibility on failing to dial up with EC25-G.
  13. Error occurred when connecting to Azure with Python.

Version 3.0.36

Added:

  1. System reboot CLI (ROUTER# reload).
  2. NAT for IPsec server.

Fixed:

  1. Failed to upgrade.
  2. Memory leak problem caused by CLI (ROUTER(config-serial_1)#no serial debug).
  3. Register failure with Telstra.
  4. HTTPS/TELNET/SSH default ports.

Altered:

  1. Removed “4G-first”, “3G-first”, “2G-first” options on cellular page.

Version 3.0.32

Fixed:

  1. Default route missing problem

Version 3.0.31

Fixed:

  1. Some bugs

Version 3.0.28

Fixed:

  1. RS232 RTU mode Modbus even parity problem

Version 3.0.27

Fixed:

  1. Bug to redial after rebooting and SIM being inserted

Version 3.0.26

Fixed:

  1. TCP connection in FTP port mode

Version 2.0.81

Added:

  1. NAT for IPsec server.
  2. System reboot CLI (ROUTER# reload).

Fixed:

  1. Default route missing problem.
  2. Memory leak problem caused by CLI (ROUTER(config-serial_1)#no serial debug).
  3. OpenVPN client failed to generate configuration file.
  4. Register failure with Telstra.
  5. https/telnet/ssh default ports.

Altered:

  1. Removed “4G-first”, “3G-first”, “2G-first” options on cellular page.

Version 2.0.68

Added:

  1. SDK installation in SSK.

Fixed:

  1. Multi-IP bug in WAN status when choose PPPoE mode for WAN

Version 1.0.19

What’s new:

  1. 5G modules like Huawei MH500, Gemalto, etc.
  2. Display module firmware version on “Status>Cellular”.

Optimized:

  1. Maximum VLAN ID is limited at 127.
  2. vlan 1 is used by Bridge0.
  3. vlan 2 is reserved for WAN port.
  4. 11 as vlan ID is restricted and not allowed to use.
  5. Priority order of available DDNS service providers.

Bugs fixed:

  1. SNMP problem with faulty MIB file.
  2. WAN access might fail.
  3. VLAN configuration might fail.
  4. QoS might fail.
  5. DHCP Server might fail to allocate subnets when VLAN was enabled.
  6. Quectel RM500 module could not dial up when the network mode is “5G-only”.
  7. RM500 SIM card switching might fail.
  8. When “Status>Cellular” was refreshed, there might be multiple lines of “data usage statistics”.
  9. More than one udhcpc processes.
  10. DDNS program inadyn might fail.
  11. Button “Save” might not respond when the DDNS setting was saved for the second time.
  12. InACL and OutACL in the interface list become empty when the firewall deletes an ACL that was not referenced.

Removed:

  1. Service providers that no longer operate or do not provide DDNS on “Network>DDNS”.
  2. DMVPN log “config change, mtu=1500”.

Version 1.0.15

Bugs fixed:

  1. DTU TCP-Server/UDP-Server mode (the select interval 10ms is incorrectly set to 10 nanoseconds) might cause CPU occupation up to 100%.
  2. Some information in MIB interface could not be obtained.
  3. Quagga restart problem due to zebra segmentation error.
  4. Hardware reset button might fail.

Linux Version 1.0.19

NOTE: Do not install DeviceHub and UrsalinkVPN in the same system at the same time.

One-click installation command: wget https://resource.ursalink.com/software/UrsalinkVPN/ursalinkvpn_install.sh && chmod +x ursalinkvpn_install.sh && ./ursalinkvpn_install.sh

Fixed:

  1. Client program has connected but the status on web page shows “Disconnected”.
  2. Devices can’t connect due to characters in device sn.

Linux Version 1.0.17

NOTE: Do not install DeviceHub and UrsalinkVPN in the same system at the same time.

One-click installation command: wget https://resource.ursalink.com/software/UrsalinkVPN/ursalinkvpn_install.sh && chmod +x ursalinkvpn_install.sh && ./ursalinkvpn_install.sh

Time needed: 10 min

Compatible with:
UR32: 32.1.0.7 and above; UR35: 35.1.0.12 and above; supports working as VPN server and displays real-time connection failure notification.
UR5x: 5x.2.0.23 and above; supports working as VPN server and displays real-time connection failure notification.

Fixed:

  1. The component “forever” installation failure
  2. Problem of inconsistent version between node.js and ursalinkvpn; installation package comes with embedded node.js.

Removed:

  1. Subnet conflict pop-up window notification. If there’s conflict in present subnet, mark the conflict subnet as red.

Added:

  1. Watchdog on URSALINK_VPN, openvpn.

Linux Version 1.0.16

Fixed:

  1. Clients don’t connect automatically after server reboots.