CubeCell Configurator

arduino-cli has some issues compiling the firmwares right.
thought i could script the build process for the different frequency bands and options
but the arduino-cli is making something really wrong.

back to compiling by hand.
a new compiled version for us915 band is online now.

Curious: what are the firmware fixes for ?
Also: I’m using a mac, will the configurator run in a VM ? Or is there another way to update the firmware ?

The last fixea are only little typos.
The conhigurator should be running in a windows vm.
If you would like to compile on your own you can use the manual here:

Excellent progress! It’s now joining and sending data successfully… Though the payload may not yet be quite what it should be?

LoRaWan Class A start!
joining…
joined
MPU9250 sensorId: 0
accelX: 0.00, accelY: 0.00, accelZ: 0.00, accelSqrt: 0.00
gyroX: 0.00, gyroY: 0.00, gyroZ: 0.00
magX: 0.00, maxY: 0.00, magZ: 0.00, horizontal direction: 0.00
BatteryVoltage: 3786, AppDataSize: 47
A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E CA
confirmed uplink sending …
MPU9250 sensorId: 0
accelX: 0.00, accelY: 0.00, accelZ: 0.00, accelSqrt: 0.00
gyroX: 0.00, gyroY: 0.00, gyroZ: 0.00
magX: 0.00, maxY: 0.00, magZ: 0.00, horizontal direction: 0.00
BatteryVoltage: 3784, AppDataSize: 47
A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E C8
confirmed uplink sending …

We are getting better :wink:
I will have a look this evening.
My mpu sensor is still on its way so i cant test.

Hipe to have a new functional version this evening

1 Like

@rsmedia, thanks.
Btw, the CubeCell Configurator works well in a VM so I’ll stick to that.

@sronan uploaded a new US915 firmware. hope the MPU is now not only detected but will deliver values.

Oh, so close…
When I disconnect and reconnect, I am almost always just seeing:
+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…

And then it stops…

Then at TTN I see some traffic… but normally no payload… the dev addr keeps changing…

But on just one occasion… I think as I disconnected at the configurator, I suddenly saw a full payload delivered including this data:
{
“aSqrt”: 0.9949142336845398,
“aY”: -0.88330078125,
“aZ”: -0.1767578125,
“ax”: 0.42236328125,
“battery”: 3802,
“gX”: 1.0986328125,
“gY”: -1.15966796875,
“gZ”: 1.5869140625,
“mDirection”: 2.9584898948669434,
“mX”: 8.28515625,
“mY”: 160.3125,
“mZ”: 61.8046875
}

See attached image of it suddenly appearing in the middle of this screenshot

I reflashed again… and rewrote the user data

I now see this in the configurator

LoRaWan Class A start!
joining…
joined
MPU9250 sensorId: 113
accelX: 0.37, accelY: -0.71, accelZ: -0.61, accelSqrt: 1.01
gyroX: -0.12, gyroY: -1.16, gyroZ: 1.22
magX: 5.92, maxY: 123.50, magZ: 114.45, horizontal direction: 2.74
BatteryVoltage: 3796, AppDataSize: 47
A 0 0 BE 3E 0 C0 34 BF 0 0 1D BF 0 0 FA BD 0 70 94 BF 0 40 9C 3F 0 60 BD 40 0 0 F7 42 0 E8 E4 42 85 C9 80 3F A4 94 2F 40 E D4
confirmed uplink sending …

Looking at gateway traffic I at first was seeing a long series of join accepts which is what each of these is:

Apparently that explained the dev addr changing each time.

But now the dev. addr. has stabilized and I am seeing some legitimate payload data…

Had a potential professional group test the cubececell capsule today using the configurator designed by @rsmedia

  1. Geographical region: US
  2. This is the output of the debug screen:

Downloadind Firmware …
Downloadind Firmware done
Flashing Firmware …
Flashing Firmware done
CleanUp Starting
CleanUp done
AT+DevEui=0053BCEFDE322854
AT+AppEui=70B3D57ED0027527
AT+AppKey=9997374D3E037024033967622987D154
AT+DutyCycle=900000

AT+RESET=1

Please note the following when reading @rsmedia configuration guide
Under the CubeCell Configurator for configuration, section Use CubeCell Configurator for configuration please read as follows

a. Go to TTN, and create an application if you haven’t already

b Under your application create a device for the CubeCell device you are setting up

c. copy the keys: Device EUI, Application EUI and App Key

Please note that you should copy and paste only one key at a time. On TTN you will notice that there is a Copy icon at the end of each key field. Then back in the Configurator screen just paste each value you copied from the TTN device screen

d. Once those three values are entered, click on write

e. The keys will be saved in the CubeCell device and the device will reboot
If you click on the Debug type you should see the above log entry - last line should read
AT+RESET=1

The guide does not say what is supposed to happen or what you should do next

Any pointers: the 915 MHz capsule is connected to a USB board connected to Com15 of an HP PC
TIA

As per my message here:

just yesterday (December 13) I had results similar to what you describe and subsequently a new version of the firmware was developed.

Could you try again now?

I’d add to your excellent, clear outline of procedures just a reminder to select the right frequency (e.g., US915) in the Configurator.

thank you @[Gipsyblues
just updated the guide to make the needed steps a little clearer.

Please note that the version of the configurator ist not the version of the firmware.
The configurator downloads allways the newest firmware.

Thank you guys for your prompt responses - @rsmedia and @sronan in particular.
@sronan, the configurator software I downloaded was only yesterday night, so I will assume that it is the latest .

Also you should know that I did test the Configurator software using a CubeCell dev board and the software worked perfectly! So the issue has to be with the CubeCell capsule I am using for the test

One thing I noticed, BTW I am using a Windows PC, when I used the dev board, the DOS window shows a complete count down/up of 10, 20, 30, etc. However with the capsule the DOS windows closes before the count down/up.

I intend to try the capsule setup again and hopefully report the results.

Once again @rsmedia, thanks you for your fantastic work. Just another comment: could you please fix a typo in the debug messages. the word downloading is spelt as “downloadind” it should be corrected to downloading - ending with a “g” and not a “d” . Please pardon my comment, too many years of spending time in the air force and teaching at a college make me do that:smile:

Will fix the typo later today. Thank for reporting @Gipsyblues
Will take a look why the firmware write for the capsule does not work as intended. I am right now in berlin and took only a dev board with me. All capsule are left at home.

Please keep in mind that the version of the configurator has nothing to do with the firmware version.
The newest firmware is allways downloaded before flashing.

Did you have a chance to see how the CubeCell capsule shows up in the Windows device manager?

This may perhaps be relevant

Yes, I did. The strange thing is that I have successfully tested and proven system working using 2 different dev boards. But no matter what I do I just cannot get the dos prompt screen entries to go beyond" initialising bootloader". However the Configurator debug screen claims that the capsule is flashed but definitely no uploading of any sort being done.

The next thing will be me replacing the USB cable to see if the capsule just doe not like what I am using now - which by the way works properly with the dev boards!

@rsmedia , @Sivaelid does the capsule need to have a battery installed inside in addition to the USB power for it to be debugged properly??

no battery needed inside the capsule.
The power from the USB board is ok.
Will be back at home on tuesday evening and will test it with my capsules.

the configurator does not check the output of the dos windows for flashing and will allways report flashing done.
this is on my agenda to check the output and report the result in the configurator.

there will be a update of the configurator next week.
in this update there will be many fixes and error messages if somethings goes wrong.

Thanks for the answer

As selfish as i could be at times, I would say @rsmedia, please take some, while away from all of us, to rest - at least while away from home! You have more than earned it!

the new configurator is online. it now handel some common failures.

i have found a failure in my compiling script. some firmware files were compiled with AT commands disabled.
this is now fixed and all firmware files updated.

now i will go out to have a beer or two.

good night to all of you.

1 Like

So do you have “Silicon Labs CP210x USB to UART Bridge” showing in your device manager for the capsule? That’s what I have after installing their driver.