What is actual & total cost of sending data?

Hi, Hologram,

I’m trying to understand the actual cost of data sent. With my Dash now up and running, I’ve been testing it for a couple of days at a time, and a couple of questions have presented themselves.

  1. I’ve noticed that when I send 5 bytes of data (literally sending a 5-byte ping: “Ping!”), the dashboard logs it as 8 bytes. I assume there may be some overhead involved with that, maybe a stop bit or two, or field descriptor, etc. Either way, it would just be good to know what the calculation is behind that. Same thing happens when I send a 65 byte string, it’s logged as 88.

  2. How does my transmitted (useful part of the data) translate to what is actually logged, for total data that I get charged for? As with the other question above, it seems there’s some overhead that is necessarily involved on a per-message basis – completely understandable, I would just like to know what that overhead is, how it’s broken down, etc., so I can come up with a good estimate for volume field deployment costs, and what I’m likely to see in data charges based both on message length and frequency of transmission.

  3. Are any data charges incurred, say over a 24 hour period, if the board is alive but not transmitting anything?

I know you’re working on bringing better resolution, timing, etc. to the dashboard re. usage, but understanding what goes into the calculation is the key I’m trying to understand at this point.

Thanks as always!

Hi Michael,

Thanks for testing on the Hologram Dash! Here are responses to your questions below:
1+2: Headers for TCP/IP messages range start at 20 bytes and our own protocol is about 30 bytes but as you’ve seen the overhead amounts can vary based on size if the messages are split up into multiple packets. Definitely understand how it’d be helpful to forecast for your field deployment and how this makes it more difficult. For now, best way would likely be to send out your expected messages and track like you’re doing. We’re working on additional documentation and examples that compare the lower data usage from our protocol vs. the usual headers attached to an HTTP POST.
3: As long as the board isn’t transmitting any keep alive to the cloud, there shouldn’t be any additional data charges on your end. Let us know if you’re seeing otherwise though.

If you need further details than that, happy to chat further to learn more about your messages, what you’re trying to build so we can get a better picture for you on data usage.


@tonym63 @Reuben