CubeCell Configurator

Yes, yes i did, when i got it though the first time as i wasnt aware of the different versions i flashed it as an indoor nod or board. I didnt paid attention on this (i had emailed you back then) how to restore as of your firmware needs to unlock the bootloader for the next flash. But i managed to the correct flash since then for over 20 times of testing codes here and there.

Configurator 8.3:

added support for OutdoorNode

Hi, having problems connecting a heltec AB01 cubecell board to the ttn in Australia.
When programming the board in the Arduino programmer, I must set the channel mask to 0xFF00 in order to connect to the ttn AU915 frequency plan - this works fine mostly.

However, when I’m using the CubeCell configurator, it seems to default to the 0x00FF channels, therefore my device is never able to successfully join the ttn. I don’t see any option to change the channel setting through the configurator… Is there a way to select the correct channel range? Thanks

you can change it with AT commands.

just type ChMask in the field next to AT+ and the full channel mask next to the = sign
than klick on send and the configurator will send the new channel mask to your cubecell

Looks like it’s coming along great.
Any news on the android version?

I’d be happy to help test it once it’s ready.


Might be useful if the app could be registered to recognise a custom URL schema in order to set the main configuration options. Ideally on both the mobile & desktop versions.

That way end-users could commission devices without manually entering long hex strings, either by clicking a generated link, or by scanning a QR code to launch the app with pre-configured values.

Thanks for that tip. I found I had to click ‘send’ twice.
Once to wake the MCU up, and again to send the AT command, interesting.

So what’s the full string you send by AT commands to change to AU915SB2?

I haven’t used the tool yet as I have been mainly working in Arduino IDE

cheers
Paul

that is normal.
the serial on the cubecell will go to sleep as the device itself.
the first command will wake up the cubecell.

IF you us my firmware SB2 is selected for AU915 band by default.

you need to send AT+ChMask=FF0000000000000000020000

I did flash your firmware for the HTCC-AB01 and it seemed to default to ChMask= 0000000000000000000000FF, the device was never able to connect to the TTN AU915.

I then used the Configurator to change the band with the following:
“AT+ChMask= 00000000000000000000FF00” - this allows the device to connect perfectly to ttn, however it doesn’t seem the ADR functionality is working correctly (SF is not dynamically changing and downlinks from ttn server seem to be ignored).

I will try “AT+ChMask=FF0000000000000000020000” next and see if it makes a difference. Great work on the configurator program too, its a powerful little tool! :grinning:

SB2 should be “AT+ChMask= 00000002000000000000FF00”. The first four hex number
is for channelMask[5], and the last four hex number is for channelMask[0].

Supporter is right. I shuffled mab and lsb

new Configurator v9.0

  • added TX Confirmed to DB
  • added online DB integration
  • added secure password store for online DB integration

If you want to test the new online Database function drop me a message.

You can edit your nodes over a web interface.
The configurator can then use the online db, now you can have your data on all your pcs.
this will allow the android app (release in september) to use the data too.

Configurator 9.1

  • changed api read format for future expansion
  • api bug fixes

Configurator, is it support AS923 band now in database?

We have found the error message from the database tab. Pls help to fix it.

Hello, just starting with cubecell, I have followed all the thread of your configurator and I have one question, can I configure my cubecell HTCC-AB01 with your configurator? If so, should I select Board, Capsule, TCA9548A, IndoorNode, ModularNode, Mapper? . Thank you very much for your great contribution.

Hello, when I hit the update button, I get this, and no firmware updates, has it been left without support?