Hi, there, sorry for the late response, you guys may know that because of the coronavirus problem, we just back to office this week, but our factory and some cooperation factories still not back to work normally… many works have to delay
Yes, @wasn is right, as far as our test, maybe because of the net work in China main land, we also can’t get downlink messages from TTN.
I have a CubeCell dev board (HTCC-AB01) running a simple test.
It transmits a fixed 3-byte uplink message (without any further processing) and the RGB LED is enabled so the LED lights with each uplink message.
So far it has sent more than 72000 uplink messages on a single battery charge already.
A 1200mAh LiPo battery is used as power source (true capacity is probably more like 1000mAh).
The CubeCell board has sent 72000+ uplink messages already on a single battery charge (and running). Battery voltage is still 3.69V so maybe 100k messages on a single charge will be possible. (For this test battery voltage is measured manually, and not measured automatically by the node).
Update:
I lost track of the exact uplink message count and later noticed the battery was empty.
Based on my last counter check (80+k) and some extrapolation: A total of between 90k and 100k uplink messages have been sent on a single battery charge.
EByte sells ASR6501 (sample) modules as low as 2+ USD per one piece delivered (depending on frequency band).
Since ASR6501 has only 1 UART access available - this SiP has little or no use for my purpose.
I noticed (but did not see such low price).
No generic Arduino support is available for ASR650x I guess. I have only seen Arduino support for the CubeCells.
If not Arduino, what SDK/toolchain would you use for ASR650x?
Ebyte has 2-3 stores on AE. At least one of them does typically make a ‘sale’ offer at any particular moment. This is one example
No generic Arduino support is available for ASR650x I guess. I have only seen Arduino support for the CubeCells.
Since ASR6501 is a S-i-P - most of stuff is hardwired inside the package. This makes such devices very compatible between different final product manufacturers.
Even firmware binaries are likely transferable in such cases, not only SDKs.
Example of such compatibility within single SiP (valid not for ASR but for similar AcSiP S76G package) is this one - firmware binaries from RAK7200 LoRaWAN GNSS assets tracker can run on TTGO T-Motion tracker (and likely vice versa).
I tried platform.io support at the end of last year, but I did not succeed because I don’t have enough sense about this platform.
Not long ago, the founder of platform.io contacted me and gave some suggestions and support. These days I am busy with the release of the new ASR6502 series (the original plan was released last week, but there were some problems in production because of COVID-19 The impact of many components can not reach our factory on time).
The support of platform.io is already in my plan, and I will deal with it when the ASR6502 series is released.
Thank you! Many people are waiting for Platform.io support for CubeCell boards. In our case this is the main reason why our company hesitates with switching to this platform.
It would be nice to add a comparison between the different CubeCell products so one can select a board based on requirements.
HTCC-AB02S product page Overview says:
Ultra low power design, 50uA in deep sleep;
HTCC-AB02S product page Tech Specs says:
Low power design Deep Sleep 3.5uA
Apparently the 50uA in the Overview is correct and 3.5uA is uncorrected copy/paste?
Why is deep sleep current 14+ times higher than for the other CubeCell boards?