CubeCell Configurator

Thanks.
Once again, forgive my ignorance on this subject, but does enabling AT commands result in higher power consumption, as I believe somebody mentioned? I would guess not, as the AT wakeup will be an interrupt…

I will use a little more battery cause the serial interface must be powered to here for the wakeup.
But there arw only this two ways to save the keys:

  1. In the source code
  2. At commands

OK. Thanks.
I still have the serial port enabled anyway, as I hadn’t thought about it consuming extra power.
So I’m seeing 37uA with or without the AT commands enabled.

am using the LoraWan_Multisensor version wasnver = “2.1.1”; and cubecell configurator : 6.4 its joining to the network server successfully, but data is not being send or junk data is send. I have 2 sensors attached BME680 and VL53L1X. Only change which i made in the LoraWan_Multisensor is

#define TCS9548 1 // TCS9548A I2C 8 port Switch
#define maxpnr 2 // TCS9548A last I2C Port
The below as done as my VL53L1X address was 0x29 (sparkfun)
case 41: //0x29 – VL53L1X
{
Serial.println(“Found VL53L1X”);
LR_VL53L1X_e[pnr] = true;
break;
}

Below is the log from cubecell configurator

24.02.20 22:29:35: AT+LORAWAN=1
24.02.20 22:29:35: AT+OTAA=1
24.02.20 22:29:35: AT+DevEui=2232330000888804
24.02.20 22:29:35: AT+AppEui=70B3D57ED0027EF2
24.02.20 22:29:35: AT+AppKey=FA540C83C6F8AAC0E00A8BC389245492
24.02.20 22:29:36: AT+DevAddr=007E6AE1
24.02.20 22:29:36: AT+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67
24.02.20 22:29:36: AT+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85
24.02.20 22:29:36: AT+DutyCycle=180000
24.02.20 22:29:36: AT+IsTxConfirmed=1
24.02.20 22:29:37:
24.02.20 22:29:37: AT+RESET=1
24.02.20 22:29:37: VL53L1X: 24.02.20 22:29:37: +OK

24.02.20 22:29:37: +LORAWAN=1

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +OTAA=1

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +DevEui=2232330000888804(For OTAA Mode)

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +AppEui=70B3D57ED0027EF2(For OTAA Mode)

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +AppKey=FA540C83C6F8AAC0E00A8BC389245492(For OTAA Mode)

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +DevAddr=007E6AE1(For ABP Mode)

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +DutyCycle=180000

24.02.20 22:29:37: +OK

24.02.20 22:29:37: +IsTxConfirmed=1

24.02.20 22:29:37: +OK

24.02.20 22:29:37: Copyright @ 2019 Heltec Automation.All rights reserved.

24.02.20 22:29:37: Copyright @ 2019 WASN.eu

24.02.20 22:29:37: FW-version: 2.1.1

24.02.20 22:29:37:

24.02.20 22:29:38: Sensor Port Scanning…

24.02.20 22:29:38: Sensor Port 0

24.02.20 22:29:38: Found BME680

24.02.20 22:29:38: Sensor Port 1

24.02.20 22:29:38: Found VL53L1X

24.02.20 22:29:38: Sensor Port 2

24.02.20 22:29:38: No Sensors found

24.02.20 22:29:38:

24.02.20 22:29:38: AT Rev 0.6

24.02.20 22:29:38:

24.02.20 22:29:38: +LORAWAN=1

24.02.20 22:29:38:

24.02.20 22:29:38: +KeepNet=0

24.02.20 22:29:38: +OTAA=1

24.02.20 22:29:38: +Class=A

24.02.20 22:29:38: +ADR=1

24.02.20 22:29:38: +IsTxConfirmed=1

24.02.20 22:29:38: +AppPort=2

24.02.20 22:29:38: +DutyCycle=180000

24.02.20 22:29:38: +ConfirmedNbTrials=8

24.02.20 22:29:38: +DevEui=2232330000888804(For OTAA Mode)

24.02.20 22:29:38: +AppEui=70B3D57ED0027EF2(For OTAA Mode)

24.02.20 22:29:38: +AppKey=FA540C83C6F8AAC0E00A8BC389245492(For OTAA Mode)

24.02.20 22:29:38: +NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)

24.02.20 22:29:38: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)

24.02.20 22:29:38: +DevAddr=007E6AE1(For ABP Mode)

24.02.20 22:29:38:

24.02.20 22:29:38:

24.02.20 22:29:38: LoRaWAN EU868 Class A start!

24.02.20 22:29:38:

24.02.20 22:29:44: joining…joined

24.02.20 22:29:44: Sensor Port 0

24.02.20 22:29:46: BME680: T = 0.00C, RH = 0.00 %, Pressure = 0.00 hPA, GAS = 129468.60mOhm, IAQ = 75.00

24.02.20 22:29:46: Sensor Port 1

please give the new 2.1.2 version a try.

the VL sensor will be found on address 0x52 and 0x29

@wasn

Tried 2.1.2 , seems like data is not sending. Below is the Debug :

5.02.20 07:22:19: +OK

25.02.20 07:22:19: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)

25.02.20 07:22:19: +OK

25.02.20 07:22:19: +DutyCycle=360000

25.02.20 07:22:19: +OK

25.02.20 07:22:19: +IsTxConfirmed=1

25.02.20 07:22:19: +OK

25.02.20 07:22:19: Copyright @ 2019 Heltec Automation.All rights reserved.

25.02.20 07:22:19: Copyright @ 2019 WASN.eu

25.02.20 07:22:19: FW-version: 2.1.2

25.02.20 07:22:19:

25.02.20 07:22:19: Sensor Port Scanning…

25.02.20 07:22:19: Sensor Port 0

25.02.20 07:22:19: Found BME680

25.02.20 07:22:19: Sensor Port 1

25.02.20 07:22:19: Found VL53L1X at 0x29

25.02.20 07:22:20: Sensor Port 2

25.02.20 07:22:20: No Sensors found

25.02.20 07:22:20:

25.02.20 07:22:20: AT Rev 0.6

25.02.20 07:22:20:

25.02.20 07:22:20: +LORAWAN=1

25.02.20 07:22:20:

25.02.20 07:22:20: +KeepNet=0

25.02.20 07:22:20: +OTAA=1

25.02.20 07:22:20: +Class=A

25.02.20 07:22:20: +ADR=1

25.02.20 07:22:20: +IsTxConfirmed=1

25.02.20 07:22:20: +AppPort=2

25.02.20 07:22:20: +DutyCycle=360000

25.02.20 07:22:20: +ConfirmedNbTrials=8

25.02.20 07:22:20: +DevEui=2232330000888804(For OTAA Mode)

25.02.20 07:22:20: +AppEui=70B3D57ED0027EF2(For OTAA Mode)

25.02.20 07:22:20: +AppKey=FA540C83C6F8AAC0E00A8BC389245492(For OTAA Mode)

25.02.20 07:22:20: +NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)

25.02.20 07:22:20: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)

25.02.20 07:22:20: +DevAddr=007E6AE1(For ABP Mode)

25.02.20 07:22:20:

25.02.20 07:22:20:

25.02.20 07:22:20: LoRaWAN EU868 Class A start!

25.02.20 07:22:20:

25.02.20 07:22:25: joining…joined

25.02.20 07:22:26: Sensor Port Sensor Port 0

tested it here with a bme680 an vl51 sensor with no problems.
please try with connecting only one sensor at a time.

ok thank you. Tested still having the same issue.

This is my current settings.
#define TCS9548 1 // TCS9548A I2C 8 port Switch
#define minpnr 0 // TCS9548A first I2C Port
#define maxpnr 7 // TCS9548A last I2C Port

#define ModularNode 0

Do i need to make any other changes ?

all things you can edit without having an impact on the code are above these lines:

/*
NO USER CHANGES NEEDED UNDER THIS LINE
*/

setting

#define TCS9548 1

is right

try setting

#define One_Wire 0

sometimes the OneWire library can make strange things

please post your logs in “preformatted text” it is much easier to read

Thanks.

Tried #define One_wire 0
Tried using attaching only one sensor. Still stuck at the line Sensor Port Sensor Port 0

25.02.20 20:54:00: AT+LORAWAN=1
25.02.20 20:54:00: AT+OTAA=1
25.02.20 20:54:00: AT+DevEui=2232330000888804
25.02.20 20:54:00: AT+AppEui=70B3D57ED0027EF2
25.02.20 20:54:01: AT+AppKey=FA540C83C6F8AAC0E00A8BC389245492
25.02.20 20:54:01: AT+DevAddr=007E6AE1
25.02.20 20:54:01: AT+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67
25.02.20 20:54:01: AT+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85
25.02.20 20:54:02: AT+DutyCycle=180000
25.02.20 20:54:02: AT+IsTxConfirmed=0
25.02.20 20:54:02: 
25.02.20 20:54:02: AT+RESET=1
25.02.20 20:54:02: 25.02.20 20:54:02: +OK

25.02.20 20:54:02: +LORAWAN=1

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +OTAA=1

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +DevEui=2232330000888804(For OTAA Mode)

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +AppEui=70B3D57ED0027EF2(For OTAA Mode)

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +AppKey=FA540C83C6F8AAC0E00A8BC389245492(For OTAA Mode)

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +DevAddr=007E6AE1(For ABP Mode)

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +DutyCycle=180000

25.02.20 20:54:02: +OK

25.02.20 20:54:02: +IsTxConfirmed=0

25.02.20 20:54:02: +OK

25.02.20 20:54:02: Copyright @ 2019 Heltec Automation.All rights reserved.

25.02.20 20:54:02: Copyright @ 2019 WASN.eu

25.02.20 20:54:02: FW-version: 2.1.2

25.02.20 20:54:02: 

25.02.20 20:54:03: Sensor Port Scanning...

25.02.20 20:54:03:  Sensor Port 0

25.02.20 20:54:03:       Found BME680

25.02.20 20:54:03:  Sensor Port 1

25.02.20 20:54:03:     No Sensors found

25.02.20 20:54:03:  Sensor Port 2

25.02.20 20:54:03:     No Sensors found

25.02.20 20:54:03: 

25.02.20 20:54:03: AT Rev 0.6

25.02.20 20:54:03: 

25.02.20 20:54:03: +LORAWAN=1

25.02.20 20:54:03: 

25.02.20 20:54:03: +KeepNet=0

25.02.20 20:54:03: +OTAA=1

25.02.20 20:54:03: +Class=A

25.02.20 20:54:03: +ADR=0

25.02.20 20:54:03: +IsTxConfirmed=0

25.02.20 20:54:03: +AppPort=2

25.02.20 20:54:03: +DutyCycle=180000

25.02.20 20:54:03: +ConfirmedNbTrials=8

25.02.20 20:54:03: +DevEui=2232330000888804(For OTAA Mode)

25.02.20 20:54:03: +AppEui=70B3D57ED0027EF2(For OTAA Mode)

25.02.20 20:54:03: +AppKey=FA540C83C6F8AAC0E00A8BC389245492(For OTAA Mode)

25.02.20 20:54:03: +NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)

25.02.20 20:54:03: +AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)

25.02.20 20:54:03: +DevAddr=007E6AE1(For ABP Mode)

25.02.20 20:54:03: 

25.02.20 20:54:03: 

25.02.20 20:54:03: LoRaWAN EU868 Class A start!

25.02.20 20:54:03: 

25.02.20 20:54:03: joining...TX on freq 868100000 Hz at DR 5

25.02.20 20:54:08: RX on freq 868100000 Hz at DR 5

25.02.20 20:54:09: joined

25.02.20 20:54:09: Sensor Port Sensor Port 0

Will have a look when i am back home
But youcan try to set tcs to 0 and modularnode to 1

Thanks. Highly appreciated. Sorry it was my mistake.

The issue was related to the the antenna connection. The antenna to the cubecell board was not properly connected and hence data was not sending.

Thanks again.

The antenna connector can shorten to the last pin of the pin header. Had that problem often

Just uploaded the new firmware 3.0.2 inkl interrupt triggered send and support for a gps through softwareserial.

just uploaded a new configurator v6.7.
many small bugfixes and the start of the new design.

the android version is now in the next state, pre beta but i hope to release an open beta next week.

@wasn Thanks for continuous improvement of the software, colors look good. if you need ways to target more audience :slight_smile: below are some functional requirements

Function : Reads the data from the Database based on the Chip Id and fill the DevEui, AppEui etc…
Challenge : Now Multiple EUis values can be saved to the Database for a single ChipId, this should be sorted out first
Implementation tip : Near to Save to DB button,add a button saying “Read from DB”

Function: Option to enter /configure multiple variables in the firmware (like dutycycle)
Implementation Tip : User enter the variable name and enter the values. You can have 2 text box like below in the configuration page.
image

Challenge : Not sure whether this is possible, Can have a max of 3 sets

@BDM
Configurator v6.8 is now online.

Changes:
small bugfixes and
there is now a button for read from database based on the ChipID

it will fill the keys from database if there is only one device with the CHipID found in the database,
all other will give a little dialogbox saying that there is no entry or more than one entry found.

allowing only unique ChipIDs in the database is not a sollution. i have 2 entries for each of my test devices (ABP and OTAA).

your second suggestion:
do you mean for sending custom AT commands?
please explain a little more.

You can now send you own AT commands with the new Configurator 7.1

Fixed changing between otaa and abo auth mode introduced in 6.8

just uploaded configurator 7.2

fix for downloading the TCA9548A firmware.
some more error handling for serial connection.

thanks @wasn… Will try the new version and will update