CubeCell Configurator

Updated the firmware files for AU915SB2 frequency plan.

You dont need to download the Configurator again.
Just choose the AU915SB2 frequency and hit the flash button it will download the new version.

1 Like

The new Configurator is online.

you can get it here:

1 Like

Any chance you’ll be supporting the MPU-9250 9-axis attitude sensor any time soon?

Looks like Invensense has replaced that with the ICM-20948 in its lineup
https://www.invensense.com/products/motion-tracking/9-axis/icm-20948/

(I don’t know whether Heltec will keep selling the MPU-9250 or will switch over…)

Will try to implement it next week.
Will post the update here

2 Likes

i have just uploaded new firmwares including the MPU9250 sensor.
the TTN decoder is updated too.

i have no MPU9250 sensor here so could not test it.

1 Like

Wow, that’s a quick nice surprise. I reflashed my CubeCell and put the new decoder in place at TTN.
For about 10 minutes I just got data specifying the time, nothing under counter or port and then a listing of the dev addr, ap eui and dev eui
But then I started to see some messages like this, which seems like good progress:

Now a little later, looking at data from the same device via a view of the gateway’s traffic, I see something that states payload size which switches between 15 and 22 bytes
And there’s a reference to “Physical payload” one example of which is:
60F62E0226AA04000340020071031500FF0178E98257
and for that same transmission under “Event data” it includes:
“payload”: “YPYuAiaqBAADQAIAcQMVAP8BeOmCVw==”

Ah, but I now see here wise advice to ignore that “physical payload”

it look like the sensor is not detected.
can you please post the serial output of the CubeCell

1 Like

How would I (relatively inexperienced in these matters) view the serial output?

open the configurator
select com port and click connect
now you can see the serial output in the debug tab.

1 Like

Thanks. Heading out of town but will try later in week.

This below is what I see…

+OK
+DevEui=004A8D9E3AC5C604(For OTAA Mode)
+OK
+AppEui=70B3D57ED00269A4(For OTAA Mode)
+OK
+AppKey=4E8916A4BC733CE46AEB386FF6076166(For OTAA Mode)
+OK
+DutyCycle=900000
+OK
Copyright @ 2019 Heltec Automation.All rights reserved.
Scanning…
No I2C devices found

AT Rev 0.3

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=004A8D9E3AC5C604(For OTAA Mode)
+AppEui=70B3D57ED00269A4(For OTAA Mode)
+AppKey=4E8916A4BC733CE46AEB386FF6076166(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWan Class A start!
joining…
joined
BatteryVoltage: 3816, AppDataSize: 2
E E8
confirmed uplink sending …

============================
That was with the MPU-9250 sensor inserted into the USB board like this:

Sensor in the wrong way round turn 180 deg and make sure where the two solder pins are they are next to SDA. If it detects the sensor it will show IC2 address. Simon

Sivaelid was faster.
just turn it around, the four pins should be on the left side and (on your picture) on the upper side

Ah, thanks, both.
When I turn the sensor around to face the opposite way and move it so it fits in the back four headers on the left in the picture, leaving the first one in front empty, in the configurator I now see:
Scanning…
I2C device found at address 0x68 !
Found MPU9250

But it stops right there… no reference to LoRaWan Class A start! no reference to joining…
No traffic on the TTN console

Any further suggestions would be much appreciated…

Found a bug in the mpu code. I will upload new firmware today.

@sronan: new firmware uploaded.
if you have time please try again

Ah, it gets much further now… but hasn’t yet joined…

I set it to US 915 and selected Flash Firmware
I saw 10/100, 20/100 etc in the command prompt and in the configurator saw:

Downloadind Firmware …
Downloadind Firmware done
Flashing Firmware …
Flashing Firmware done
CleanUp Starting
CleanUp done

Then I selected Connect
I ensured that the DevEUI AppEUI and AppKey correspond to what I see on TTN and set the duty cycle to 0,15,0 and select write and in the configurator see:

AT+DevEui=003981B550BD22EA
AT+AppEui=70B3D57ED00269A4
AT+AppKey=B423D01003D3F1A1B932C2A7CD027990
AT+DutyCycle=900000

AT+RESET=1
+OK
+DevEui=003981B550BD22EA(For OTAA Mode)
+OK
+AppEui=70B3D57ED00269A4(For OTAA Mode)
+OK
+AppKey=B423D01003D3F1A1B932C2A7CD027990(For OTAA Mode)
+OK
+DutyCycle=900000
+OK
Copyright @ 2019 Heltec Automation.All rights reserved.
Scanning…
I2C device found at address 0x68 !
Found MPU9250

AT Rev 0.5

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=003981B550BD22EA(For OTAA Mode)
+AppEui=70B3D57ED00269A4(For OTAA Mode)
+AppKey=B423D01003D3F1A1B932C2A7CD027990(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWan Class A start!
joining…

======================

However, there it stops… I don’t see a join request when looking at the US915 gateway traffic…

hi can you flash it again?
i have found a failure in my script for compiling all the firmware for the different frequencies.
the frequency bands are not right compiled.
i have fixed that now

Sure! But now, after I reflash the firmware and then connect and enter the user data (DevEUI, etc.) and duty cycle and try to write it, it just gets this far:

AT+DevEui=003981B550BD22EA
AT+AppEui=70B3D57ED00269A4
AT+AppKey=B423D01003D3F1A1B932C2A7CD027990
AT+DutyCycle=900000

AT+RESET=1

And then stops. And if I then disconnect and connect again, the DevEUI, etc. are blank.