CubeCell Configurator

@rsmedia

  1. I have used 868 frequency. I have flashed by going to flash --> Flash Firmware.

image

This is the full log

28.12.19 23:19:28: +OK
28.12.19 23:19:28: Copyright @ 2019 Heltec Automation.All rights reserved.
28.12.19 23:19:28: Sensor Port Scanning…
28.12.19 23:19:28: No Sensors found
28.12.19 23:19:28:
28.12.19 23:19:28: AT Rev 0.5
28.12.19 23:19:28:
28.12.19 23:19:28: +LORAWAN=1
28.12.19 23:19:28:
28.12.19 23:19:28: +KeepNet=0
28.12.19 23:19:28: +OTAA=1
28.12.19 23:19:28: +Class=A
28.12.19 23:19:28: +ADR=1
28.12.19 23:19:28: +IsTxConfirmed=0
28.12.19 23:19:28: +AppPort=2
28.12.19 23:19:28: +DutyCycle=900000
28.12.19 23:19:28: +ConfirmedNbTrials=8
28.12.19 23:19:28: +DevEui=2232330000888802(For OTAA Mode)
28.12.19 23:19:28: +AppEui=70B3D57ED0027EF2(For OTAA Mode)
28.12.19 23:19:28: +AppKey=87AB76E8E51A7477F75B41E989E2BB1F(For OTAA Mode)
28.12.19 23:19:28: +NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
28.12.19 23:19:29: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
28.12.19 23:19:29: +DevAddr=007E6AE1(For ABP Mode)
28.12.19 23:19:29:
28.12.19 23:19:29: +LED=1
28.12.19 23:19:29:
28.12.19 23:19:29: LoRaWan Class A start!
28.12.19 23:19:29: joining…
28.12.19 23:19:34: joined
28.12.19 23:19:35: Scan for OneWire Sensors …
28.12.19 23:19:35: No OneWire Sensors found.
28.12.19 23:19:35: BatteryVoltage: 4158
28.12.19 23:19:35: confirmed uplink sending …
28.12.19 23:19:35: unconfirmed uplink sending …

I tried with only HDC1080 SENSOR Below is the log

28.12.19 23:26:36: Downloadind Firmware …
28.12.19 23:26:37: Downloading Firmware done
28.12.19 23:26:37: Flashing Firmware …
28.12.19 23:26:40: Initialising bootloader.
28.12.19 23:26:40: Silicon ID 0x256a11b5, revision 0.
28.12.19 23:26:40: Verifying rows.
28.12.19 23:26:40: Array 0: first row 34, last row 511.
28.12.19 23:26:40: Starting upload.
28.12.19 23:26:40: Uploading ( 10 / 100 )
28.12.19 23:26:42: Uploading ( 20 / 100 )
28.12.19 23:26:44: Uploading ( 30 / 100 )
28.12.19 23:26:46: Uploading ( 40 / 100 )
28.12.19 23:26:48: Uploading ( 50 / 100 )
28.12.19 23:26:51: Uploading ( 60 / 100 )
28.12.19 23:26:53: Uploading ( 70 / 100 )
28.12.19 23:26:55: Uploading ( 80 / 100 )
28.12.19 23:26:57: Uploading ( 90 / 100 )
28.12.19 23:27:00: Uploading ( 100 / 100 )
28.12.19 23:27:00: Checksum verifies OK.
28.12.19 23:27:00: Rebooting.
28.12.19 23:27:00: Total upload time 22.53s
28.12.19 23:27:00: Flashing Firmware done
28.12.19 23:27:00: CleanUp Starting
28.12.19 23:27:00: CleanUp done
28.12.19 23:27:16: Copyright @ 2019 Heltec Automation.All rights reserved.
28.12.19 23:27:16: 28.12.19 23:27:16: +OK
28.12.19 23:27:16: +DutyCycle=0
28.12.19 23:27:16: +OK
28.12.19 23:27:16: +IsTxConfirmed=0
28.12.19 23:27:17: Sensor Port Scanning…
28.12.19 23:27:17: Found HDC1080
28.12.19 23:27:17: Found ADS1015
28.12.19 23:27:17: Found VL53L1X
28.12.19 23:27:18: Found CCS811
28.12.19 23:27:18: Found MPU9250
and it get stuck over there…

This looks like that the sensor is not connected right or is faulty.
It pulls the data line of the i2c bus low

i have just uploaded a new firmware for the capsule and EU868 band.
you dont have to download a new configurator, just flash the capsule again.

@rsmedia

Thanks for your update. I have a feature request. In the flash firmware page, you can have a checkbox saying “Preserve existing configuration”. if this checkbox is selected you can restore DevEui, AppEui , AppKey Duty cycle and TX confirmed after flashing. This will make the configurator much easier to use :slight_smile: And thanks from the heart for bringing up this easy to use application.

Just tried with three different sensors on the capsule with EU 868 Band. Below is the result.
while using the sensor HDC1080

29.12.19 21:56:02: Copyright @ 2019 Heltec Automation.All rights reserved.
29.12.19 21:56:02: Copyright @ 2019 WASN.eu
29.12.19 21:56:02: FW-version: 2.0.2
29.12.19 21:56:02:
29.12.19 21:56:02: Sensor Port Scanning…
29.12.19 21:56:03: Found HDC1080
29.12.19 21:56:03: Found ADS1015
29.12.19 21:56:03: Found VL53L1X
29.12.19 21:56:04: Found CCS811
29.12.19 21:56:04: Found MPU9250

After that its getting stuck

Test result when using ccs8018

29.12.19 21:57:59: +OK
29.12.19 21:57:59: Copyright @ 2019 Heltec Automation.All rights reserved.
29.12.19 21:57:59: Copyright @ 2019 WASN.eu
29.12.19 21:57:59: FW-version: 2.0.2
29.12.19 21:57:59:
29.12.19 21:57:59: Sensor Port Scanning…
29.12.19 21:57:59: No Sensors found
29.12.19 21:57:59:
29.12.19 21:57:59: AT Rev 0.5

while using the sensor bh1750 : sensor was correctly detected.

29.12.19 22:00:58: Copyright @ 2019 Heltec Automation.All rights reserved.
29.12.19 22:00:58: Copyright @ 2019 WASN.eu
29.12.19 22:00:58: FW-version: 2.0.2
29.12.19 22:00:58:
29.12.19 22:00:58: Sensor Port Scanning…
29.12.19 22:00:58: found BH1750
29.12.19 22:00:58:
29.12.19 22:00:58: AT Rev 0.5

@BDM

your HDC1080 sensor seems to be brooken.
your CCS8018 could not be found because it is not known
the only CCS sensor known is CCS811

@rsmedia Thanks for your feedback.

Used Configurator with development board and bme280 sensor. works fine.

@BDM
i have a new configurator online and updated the readme.
now you can preserve the configuration when flashing new firmware.

that makes testing much better.

There will be a new firmware at the end of the week which will handle the hang on IIC scan

with uploading the new firmwares you need to download the new configurator.
all versions prior to 3.4 will not work anymore for flashing.

uploaded a new configurator.
you can now check the online version of the firmware and download all firmwares.

i had problems in areas without cellular network to flash a new firmware, but now i can download all firmware at home and flash in the field without cellular coverage.

Thanks, really appreciated. Will try out soon…

@rsmedia Tried the new version of configurator

I have flashed with the new firmware. After successfull flashing, coming to config tab and tried to write…Its getting stuck over there … below is the screen shot

Let the cubecell plugged in and hit the reset button of the cubecell.
What does the debug field say?

@rsmedia

Output from the debug when reset button is hit.
02.01.20 19:41:25: Copyright @ 2019 Heltec Automation.All rights reserved.
02.01.20 19:41:26: Copyright @ 2019 WASN.eu
02.01.20 19:41:26: FW-version: 2.0.3
02.01.20 19:41:26:
02.01.20 19:41:26: Sensor Port Scanning…
02.01.20 19:41:26: found BH1750
02.01.20 19:41:26:
02.01.20 19:41:26: AT Rev 0.5
02.01.20 19:41:26:
02.01.20 19:41:26: +LORAWAN=1
02.01.20 19:41:26:
02.01.20 19:41:26: +KeepNet=0
02.01.20 19:41:26: +OTAA=1
02.01.20 19:41:26: +Class=A
02.01.20 19:41:26: +ADR=1
02.01.20 19:41:26: +IsTxConfirmed=0
02.01.20 19:41:26: +AppPort=2
02.01.20 19:41:26: +DutyCycle=900000
02.01.20 19:41:26: +ConfirmedNbTrials=8
02.01.20 19:41:26: +DevEui=0000000000000000(For OTAA Mode)
02.01.20 19:41:26: +AppEui=0000000000000000(For OTAA Mode)
02.01.20 19:41:26: +AppKey=00000000000000000000000000000000(For OTAA Mode)
02.01.20 19:41:26: +NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
02.01.20 19:41:26: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
02.01.20 19:41:27: +DevAddr=007E6AE1(For ABP Mode)
02.01.20 19:41:27:
02.01.20 19:41:27: +LED=0
02.01.20 19:41:27:
02.01.20 19:41:27: LoRaWan Class A start!
02.01.20 19:41:27: joining…

Below is the screen shot. As write function is not working we cannot enter DevEui, App Eui and Appkey

will have a look this evening.
i have flashed and programmed 1 capsule and 2 boards with the 3.5 version.

i am just heading home, so now time right now.

@rsmedia

Just checked the version 3.7. Looks promising… Most of the bugs has been fixed. Great work.

Sensor CCS811 (cubecell, 868) is detecting correctly ( In the previous versions it was not). still the sensor in the warming up… will keep you posted.

there was a little problem with the original CCS811 and BH1750 sensor.
both uses GPIO0, but the CCS811 needs it LOW for activating the CCS811 and the BH1750 needs it HIGH (LOW on BH1750 will keep the BH1750 in reset state)

Will try to get both working but right now i have GPIO0 LOW to get the CCS811 working .

Great !!

Just a question. what is the best practise to set alert while using the various sensors. For example while using ccs811 or bme280 need to send to send a alert when the temperature is above 25 or humidity has reached a specific value. Can we do it with the configurator ? or do we need to modify the sketch file

The firmware flashed with the configurator just sends the sensor values.
You can make an alarm on the receiver site or you have to compile your own firmware.
The source of my firmware is in the official repository with the name “LoRaWan_MultiSensor”

@rsmedia ok thanks to pointing to that. While compiling the ino file in the ardunio am getting below error.

LoRaWan_MultiSensor:175:1: error: ‘SFEVL53L1X’ does not name a type

SFEVL53L1X LRSVL53L1X;

^

C:\Users\jihadaj\Documents\Arduino\water-display\LoRaWan_MultiSensor\LoRaWan_MultiSensor.ino: In function ‘void PrepareTxFrame(uint8_t)’:

LoRaWan_MultiSensor:828:12: error: ‘LRSVL53L1X’ was not declared in this scope

   if (!LRSVL53L1X.begin() == 0) { //Begin returns 0 on a good init

        ^

LoRaWan_MultiSensor:831:7: error: ‘LRSVL53L1X’ was not declared in this scope

   LRSVL53L1X.setDistanceModeShort();

   ^

Could you tell me which library are you using for the sensor VL53L1X?
Also were you able to fix the error of scanning oneWire devices in the version 2.4

Thanks

For the vl53l1x i use the bundled library.