CubeCell Configurator

When I use the CubeCell Configurator, no sensor attached just the CubeCell board, when it does finally join it will hang at waiting for GPS FIX. I do not have a gps attached so it will not move past this. US915 and FW 3.0.5

26.04.20 06:48:02: Sensor Port Scanning...
26.04.20 06:48:02:     No Sensors found
26.04.20 06:48:02: 
26.04.20 06:48:02: AT Rev 0.6
26.04.20 06:48:02: 
26.04.20 06:48:02: +LORAWAN=1
26.04.20 06:48:02: 
26.04.20 06:48:03: +KeepNet=0
26.04.20 06:48:03: +OTAA=1
26.04.20 06:48:03: +Class=A
26.04.20 06:48:03: +ADR=1
26.04.20 06:48:03: +IsTxConfirmed=1
26.04.20 06:48:03: +AppPort=2
26.04.20 06:48:03: +DutyCycle=15000
26.04.20 06:48:03: +ConfirmedNbTrials=8
26.04.20 06:48:03: +DevEui=#(For OTAA Mode)
26.04.20 06:48:03: +AppEui=#(For OTAA Mode)
26.04.20 06:48:03: +AppKey=#(For OTAA Mode)
26.04.20 06:48:03: +NwkSKey=0(For ABP Mode)
26.04.20 06:48:03: +AppSKey=0(For ABP Mode)
26.04.20 06:48:03: +DevAddr=0(For ABP Mode)
26.04.20 06:48:03: 
26.04.20 06:48:03: 
26.04.20 06:48:03: LoRaWAN US915 Class A start!
26.04.20 06:48:03: 
26.04.20 06:48:16: joining...join failed, join again at 30s later
26.04.20 06:49:00: join failed, join again at 30s later
26.04.20 06:49:36: joined
26.04.20 06:49:37: Waiting for GPS FIX ...

It should timeout after 1.5sec.

I should say that it doesn’t always time out. Sometimes it will just sit there waiting for the GPS. I have to reset it to get it to try and reconnect.

i have to correct me the latest firmware has a timeout of 5 seconds.
here it is working without problems, but i will have a look to make it saver.

Firmware 3.0.9 is now online;

Had to remove support for the BMP180 sensor to get more space.
But now with many bug fixes and stability improvements.

Firmware 3.1.0 is now online.

many bug fixes and added Adafruit STEMMA Soil Sensor

new configurator 7.9 is online now.

fixed a firmware download bug

Configurator 8.0 is released.

many little bug fixes and stability improvements
fixed problem that AppEUI is not exported to database

configurator 8.1:
fixed error when comport not avail

configurator 8.2:
fixed gui bug for flashing firmware

Firmware 3.1.1 is now online

new BME680 library many bug fixes

1 Like

Hello people, im using a cubecell with an MPU9250 attached, what i find odd is (upgraded the firmware to the last one) is that im displayed the complete payload at ttn only and only when i have attached the usb adapter connected to my pc. Until that moment i have hours of no ping data. When i connect that to my pc somehow it triggers and i have new payload to TTN. Can anyone assist on this?
So i have the decoded payload of mag acc and gyro only when i connect to pc and configurator is connected

Which cubecell do you have?
Have connected the battery with right polarity?

i reflashed the configurator firmware today, i get the MPU payload after about 20 minutes activation messages in TTN and for about 20 mins of correct payloads. But after some time i get no payload at all. how this cube cell works?
31.05.20 22:09:06: No GPS connected
31.05.20 22:09:06: BatteryVoltage: 4120
31.05.20 22:09:06: Trigger: Interrupt or timer
31.05.20 22:09:16: MPU9250 sensorId: 113
31.05.20 22:09:16: accelX: -0.39, accelY: -0.50, accelZ: 0.78, accelSqrt: 1.00
31.05.20 22:09:16: gyroX: -4.21, gyroY: 55.11, gyroZ: -60.12
31.05.20 22:09:16: magX: 32.38, maxY: 127.12, magZ: -100.93, horizontal direction: 14.29Probing for GPS …

once again it gets the payload delivered only when i attach the cable and connect the com port to the configurator. I dont think is battery related as i get the 3 led flashes from time to time
{
“P0_MPU9250_aSqrt”: 1.0043842792510986,
“P0_MPU9250_aY”: 0.99658203125,
“P0_MPU9250_aZ”: -0.06298828125,
“P0_MPU9250_ax”: -0.10791015625,
“P0_MPU9250_gX”: 1.708984375,
“P0_MPU9250_gY”: -2.5634765625,
“P0_MPU9250_gZ”: 1.708984375,
“P0_MPU9250_mDirection”: 67.3509292602539,
“P0_MPU9250_mX”: 166.69140625,
“P0_MPU9250_mY”: 69.5546875,
“P0_MPU9250_mZ”: -89.33203125,
“battery”: 4184,
“trigger”: 0
}
either by trigger 0 or 1

how will i make it work without having it attached to the computer? thanks

trigger should be 1 if triggered by timer.
when trigger is 0 sending was triggered by interrupt (GPIO2 high for trigger). this should not happen if you have nothing connected to GPIO2.

i think in the capsule the mpu9250 is connected with the interrupt from the mpu to GPIO6.
so no conflicts here.

what battery do you have installed in the capsule?
are you using the official MPU9250 module?

Please open a new threat for this discussion because i think it is not related to the CubeCell Configurator.

yes its the official addon MPU9250 that came with the device. I once have trigger 1 the other time 0. Battery is also the original 3.7 80ma that measured it and has 3.7v. Fact of the matter is that even powered since yesterday i have no other packets send. So it doesnt favor the duty cycle of 2.5 mins set either by moving it to trigger. I would open a new thread next.

Have to look if i have that sensor flying around.
If yes i will test it with a capsule.
Normally i only test on the dev board

Thats the capsule in question

i know it is a dumb question but have you selected the right CubeCell Type: Capsule before flashing?