the driver should be installed via windows update.
if not you can find it here:
https://www.silabs.com/documents/public/software/CP210x_Universal_Windows_Driver.zip
CubeCell Configurator
@sronan, the Silicon Labs CP210x driver once correctly or successfully installed would appear in the Device Manager dialog box (window) as “Silicon Labs CP210x USB to UART Bridge” under Ports (COM & LPT) - if you connect any device using any of the CP210x chips. When you remove the device, that entry for the driver vanishes from below the Port(COM & LPT) listing. So as you are reporting, you have successfully installed the driver
Using the version 2.6 of the Configurator by @rsmedia, I am getting an error about format and operation hanging at joining and never connecting to TTN please see the debug output that follows
For the capsule board I had to reflash more than 9 times before success and at times just could not repeat the results!
@rsmedia, could you please confirm what the error means in the debug screen, and why one needs to flash that many times on a capsule. TIA GB.
Downloadind Firmware …
Downloading Firmware done
Flashing Firmware …
Initialising bootloader.
Silicon ID 0x256a11b5, revision 0.
Verifying rows.
Array 0: first row 34, last row 511.
Starting upload.
Uploading ( 10 / 100 )
Uploading ( 20 / 100 )
Uploading ( 30 / 100 )
Uploading ( 40 / 100 )
Uploading ( 50 / 100 )
Uploading ( 60 / 100 )
Uploading ( 70 / 100 )
Uploading ( 80 / 100 )
Uploading ( 90 / 100 )
Uploading ( 100 / 100 )
Checksum verifies OK.
Rebooting.
Total upload time 23.13s
Flashing Firmware done
CleanUp Starting
CleanUp done
Copyright @ 2019 Heltec Automation.All rights reserved.
+ERROR: error input format
+OK
+DutyCycle=900000
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !
I2C device found at address 0x3E !
I2C device found at address 0x3F !
I2C device found at address 0x40 !
Found HDC1080
I2C device found at address 0x41 !
I2C device found at address 0x42 !
I2C device found at address 0x43 !
I2C device found at address 0x44 !
I2C device found at address 0x45 !
I2C device found at address 0x46 !
I2C device found at address 0x47 !
I2C device found at address 0x48 !
I2C device found at address 0x49 !
I2C device found at address 0x4A !
I2C device found at address 0x4B !
I2C device found at address 0x4C !
I2C device found at address 0x4D !
I2C device found at address 0x4E !
I2C device found at address 0x4F !
I2C device found at address 0x50 !
I2C device found at address 0x51 !
I2C device found at address 0x52 !
I2C device found at address 0x53 !
I2C device found at address 0x54 !
I2C device found at address 0x55 !AT Rev 0.5
+LORAWAN=1
+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=0000000000000000(For OTAA Mode)
+AppEui=0000000000000000(For OTAA Mode)
+AppKey=00000000000000000000000000000000(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)LoRaWan Class A start!
joining…
AT+DevEui=00A5151A240545EA
AT+AppEui=70B3D57ED0027527
AT+AppKey=99D22FAAD556D60FC3D552C74E5AA886
AT+DutyCycle=900000AT+RESET=1
+ERROR: error input format
+OK
+DevEui=00A5151A240545EA(For OTAA Mode)
+OK
+AppEui=70B3D57ED0027527(For OTAA Mode)
+OK
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+OK
+DutyCycle=900000
+OK
Copyright @ 2019 Heltec Automation.All rights reserved.
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !
I2C device found at address 0x3E !
I2C device found at address 0x3F !
I2C device found at address 0x40 !
Found HDC1080
I2C device found at address 0x41 !
I2C device found at address 0x42 !AT Rev 0.5
+LORAWAN=1
+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=00A5151A240545EA(For OTAA Mode)
+AppEui=70B3D57ED0027527(For OTAA Mode)
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)LoRaWan Class A start!
joining…
@rsmedia, I just noticed an updated Configurator software. I will go back and test using the latest version and report back
@rsmedia, I just installed the v2.7 Configurator. There appears to be errors but the device at least successfully connected to TTN. @rsmedia, could you please check the debug output and confirm what these errors are? TIA
Downloadind Firmware …
Downloading Firmware done
Flashing Firmware …
Initialising bootloader.
Silicon ID 0x256a11b5, revision 0.
Verifying rows.
Array 0: first row 34, last row 511.
Starting upload.
Uploading ( 10 / 100 )
Uploading ( 20 / 100 )
Uploading ( 30 / 100 )
Uploading ( 40 / 100 )
Uploading ( 50 / 100 )
Uploading ( 60 / 100 )
Uploading ( 70 / 100 )
Uploading ( 80 / 100 )
Uploading ( 90 / 100 )
Uploading ( 100 / 100 )
Checksum verifies OK.
Rebooting.
Total upload time 23.05s
Flashing Firmware done
CleanUp Starting
CleanUp done
Copyright @ 2019 Heltec Automation.All rights reserved.
+ERROR: error input format
+OK
+DutyCycle=900000
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !
I2C device found at address 0x3E !
I2C device found at address 0x3F !
I2C device found at address 0x40 !
Found HDC1080
I2C device found at address 0x41 !
I2C device found at address 0x42 !
I2C device found at address 0x43 !
I2C device found at address 0x44 !
I2C device found at address 0x45 !
I2C device found at address 0x46 !
I2C device found at address 0x47 !
I2C device found at address 0x48 !
I2C device found at address 0x49 !
I2C device found at address 0x4A !
I2C device found at address 0x4B !
I2C device found at address 0x4C !
I2C device found at address 0x4D !
I2C device found at address 0x4E !
I2C device found at address 0x4F !AT Rev 0.5
+LORAWAN=1
+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=0000000000000000(For OTAA Mode)
+AppEui=0000000000000000(For OTAA Mode)
+AppKey=00000000000000000000000000000000(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)LoRaWan Class A start!
+ERROR: error input format
joining…
+OK
+DevEui=0000000000000000(For OTAA Mode)
+OK
+AppEui=0000000000000000(For OTAA Mode)
+OK
+AppKey=00000000000000000000000000000000(For OTAA Mode)
+OK
+DutyCycle=900000
AT+DevEui=00A5151A240545EA
AT+AppEui=70B3D57ED0027527
AT+AppKey=99D22FAAD556D60FC3D552C74E5AA886
AT+DutyCycle=900000AT+RESET=1
+ERROR: error input format
+OK
+DevEui=00A5151A240545EA(For OTAA Mode)
+OK
+AppEui=70B3D57ED0027527(For OTAA Mode)
+OK
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+OK
+DutyCycle=900000
+OK
Copyright @ 2019 Heltec Automation.All rights reserved.
Scanning…
I2C device found at address 0x01 !
I2C device found at address 0x02 !
I2C device found at address 0x03 !
I2C device found at address 0x04 !
I2C device found at address 0x05 !
I2C device found at address 0x06 !
I2C device found at address 0x07 !
I2C device found at address 0x08 !
I2C device found at address 0x09 !
I2C device found at address 0x0A !
I2C device found at address 0x0B !
I2C device found at address 0x0C !
I2C device found at address 0x0D !
I2C device found at address 0x0E !
I2C device found at address 0x0F !
I2C device found at address 0x10 !
I2C device found at address 0x11 !
I2C device found at address 0x12 !
I2C device found at address 0x13 !
I2C device found at address 0x14 !
I2C device found at address 0x15 !
I2C device found at address 0x16 !
I2C device found at address 0x17 !
I2C device found at address 0x18 !
I2C device found at address 0x19 !
I2C device found at address 0x1A !
I2C device found at address 0x1B !
I2C device found at address 0x1C !
I2C device found at address 0x1D !
I2C device found at address 0x1E !
I2C device found at address 0x1F !
I2C device found at address 0x20 !
I2C device found at address 0x21 !
I2C device found at address 0x22 !
I2C device found at address 0x23 !
found BH1750
I2C device found at address 0x24 !
I2C device found at address 0x25 !
I2C device found at address 0x26 !
I2C device found at address 0x27 !
I2C device found at address 0x28 !
I2C device found at address 0x29 !
I2C device found at address 0x2A !
I2C device found at address 0x2B !
I2C device found at address 0x2C !
I2C device found at address 0x2D !
I2C device found at address 0x2E !
I2C device found at address 0x2F !
I2C device found at address 0x30 !
I2C device found at address 0x31 !
I2C device found at address 0x32 !
I2C device found at address 0x33 !
I2C device found at address 0x34 !
I2C device found at address 0x35 !
I2C device found at address 0x36 !
I2C device found at address 0x37 !
I2C device found at address 0x38 !
I2C device found at address 0x39 !
I2C device found at address 0x3A !
I2C device found at address 0x3B !
I2C device found at address 0x3C !
I2C device found at address 0x3D !AT Rev 0.5
+LORAWAN=1
+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=1
+AppPort=2
+DutyCycle=900000
+ConfirmedNbTrials=8
+DevEui=00A5151A240545EA(For OTAA Mode)
+AppEui=70B3D57ED0027527(For OTAA Mode)
+AppKey=99D22FAAD556D60FC3D552C74E5AA886(For OTAA Mode)
+NwkSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+AppSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)LoRaWan Class A start!
joining…
joined
[BH1750] ERROR: received NACK on transmit of data
[BH1750] Device is not configured!
[BH1750] Device is not configured!
BH1750: Light = -2.00lx
BatteryVoltage: 4148, AppDataSize: 5
6 FF EC 10 34
confirmed uplink sending …
receive data: rssi = -64, snr = 12, datarate = 13
When you are seeing
LoRaWan Class A start!
joining…
have you been able to check TTN application data and gateway traffic data?
On several recent attempts, while seeing “joining” in the Configurator and (occasionally “join failed”), I’ve at the same time seen at TTN a 15 minutes long series of periodic join accepts that seem not truly successful with the dev. address changing on each occasion. Then after 15 minutes I’ve seen payload starting to be successfully delivered… And at that point the Configurator starts to show additional activity.
Coincidentally or not (I suspect not), I have a 15 minute duty cycle set via the Configurator
@sronan, re your question about the data shown on TTN when the debug screen still says “joining”, I have the same observation like you. Yes it appears despite the joining status as per the debug screen, the device during that interval is trying to send data to TTN.
As you rightly observed, the payload once an “interval”, the 15 minute duty cycle selected during configuration, gets through to TTN.
We need to confirm this behaviour and let @rsmedia know, so that we could amend the guide to advise that the user checks the data tab of the device on TTN
1 Like
@rsmedia, I got a question for you.
Please see the debug screen log below.
Is it possible to add time stamps to the activities indicated?
The reason I am asking is I notice that data is being uploaded to the TTN device - the capsule in this case. However on checking the device data on TNN, the data does not seem to be getting there.
(BTW the gateway is just located in the room only less than 20 feet from where the sensor is
join failed
join failed
joined
BH1750: Light = 3.33lx
BatteryVoltage: 4080, AppDataSize: 5
6 0 21 F F0
confirmed uplink sending …
BH1750: Light = 4.58lx
BatteryVoltage: 4102, AppDataSize: 5
6 0 2D 10 6
confirmed uplink sending …
BH1750: Light = 3.75lx
BatteryVoltage: 4106, AppDataSize: 5
6 0 25 10 A
confirmed uplink sending …
BH1750: Light = 4.17lx
BatteryVoltage: 4100, AppDataSize: 5
6 0 29 10 4
confirmed uplink sending …
BH1750: Light = 4.17lx
BatteryVoltage: 4122, AppDataSize: 5
6 0 29 10 1A
confirmed uplink sending …
BH1750: Light = 2.92lx
BatteryVoltage: 4102, AppDataSize: 5
6 0 1D 10 6
confirmed uplink sending …
BH1750: Light = 3.33lx
BatteryVoltage: 4100, AppDataSize: 5
6 0 21 10 4
confirmed uplink sending …
BH1750: Light = 3.33lx
BatteryVoltage: 4100, AppDataSize: 5
6 0 21 10 4
confirmed uplink sending …
BH1750: Light = 1.25lx
BatteryVoltage: 4108, AppDataSize: 5
6 0 C 10 C
confirmed uplink sending …
This log entry:
+ERROR: error input format
Means an error in the communication between cubecell and configurator. Sometimes the configurator sends two commands to fast after each other. This is on my agenda.
The log entries:
I2C device found at address …
Counting up indicates a faulty i2c bus.
There should only be such a message with the addresses of the i2c devices connected.
Sometimes a shortage one line or a i2c device holding a i2c line on low level.
Adding timestamps in the configurator is a good idea.
Will implement it today
Thanks.
The other question from the debug log above
BH1750: Light = 1.25lx
BatteryVoltage: 4108, AppDataSize: 5
6 0 C 10 C
Could you explain the info and format used
BH1750----reading of light intensity
Battery Voltage---- 4.108v ( I am assuming that the data is in millivolts)
AppDataSize----5 ??? what is this entry
6 0 C 10 C------??? what is this entry
TIA
The reading from the sensors are always printed with the sensor type in front:
so this
- BH1750: Light = 1.25lx
means: - reading from the BH1750 sensor: Datatype = Value
The battery voltage is given in millivolt.
AppDataSize is the length of the send payload. in your example 5
the AppDataSize is build out of:
- 1byte: Sensortype (6 stands for BH1750)
- 2bytes: sensorvalue
- 2byte: battery voltage
the AppData is shown in the last row:
- 6 0 C 10 C
means: - 6: Sensortype 6 (BH1750)
- 0 C: sensor value
- 10 C: battery voltage
My suspicion that the 15 minute delays in successfully sending the first payload was perhaps related to the 15-minute duty cycle I had set now seems incorrect.
I tried a 7-minute duty cycle and that did not speed the time to first payload. And then tried a 25 minute duty cycle and the first payload was sent successfully within the first couple of minutes…
Another more recent attempt with a 15 minute duty cycle has taken more than an hour without successfully delivering a payload… with this most recent sequence showing payload “not provided” and port 0 listed.
In a perhaps similar situation I see Arjanvanb on the TTN forum stating “Your node is using port 0 for the uplink. That is not allowed for uplinks.” But I’m not able to comprehend the full discussion…
@rsmedia, thanks for explaining the format of data being generated.
Secondly, is there any reason why port 0 is being used for the uplink?
reference @arjanvanb from the The Things Network???
After I restarted my capsule, it shows that when an uplink used port 0, there was no reading/data. 3 seconds later data was uploaded using port2 with valid data.
I guess the question then becomes what selects the uplink port, is it random or as coded
Perhaps my current problem getting payloads may result from too many separate reflashes/rewrites/restarts today that have made me exceed the 24-hour maximum for downlinks? Is there risk of that?
" Finally, on The Things Network’s public community network, we have a Fair Access Policy that limits the uplink airtime to 30 seconds per day (24 hours) per node and the downlink messages to 10 messages per day (24 hours) per node ." https://www.thethingsnetwork.org/docs/lorawan/duty-cycle.html#maximum-duty-cycle
When looking at the most recent downlink message via the TTN gateway traffic, I see a “set empty payload” message as per below… Could that be due to a violation of the fair use policy… too many restarts?
port 2 is hardcoded
cant say where the port 0 is comming from
I wonder if this discussion is at all relevant:
It references a sensor where “the firmware for these devices uses confirmed uplink for every transmission,”
Does the capsule “use confirmed uplink for every transmission”. ?
I was still wondering whether TTN may send empty payload using port 0 when there is a violation of its fair use policy due to too many downlink messages for a device using its free network…
But here, just a few weeks ago, I see someone say: “The fair access policy is currently not enforced.”
Meanwhile I have unplugged my capsule thinking I will try it again tomorrow…
i cant reproduce this failure with sending on port 0, but i can only test in the EU868 band.
by the way i have uploaded a new configurator.
this is new in version 3.0:
- better error handling
- window can now be resized vertically for having a bigger debug output field
- some minnor bug fixes
Searching for port 0 on the TTN forums, here are a couple of items of potential relevance:
But can’t say I properly understand them…
I look forward to trying Configurator version 3.0 tomorrow. Thanks @rsmedia…
@rsmedia
Today I got the dev board and cubecell. Now am trying configurator version 3.2
I have connected cube cell to the debug board. I have connected CCS8118 sensor to the debug board as below (not sure if this is correct way or not )
But the configurator was not able to detect any sensor…
Any advice ?
@BDM
The sensor is connected right.
which frequency band do you use?
Which firmware have you used?
The version of the configurator is not important.
For each flash the newest firmware is downloaded.