Plans for the dashboard

Need2Revolt

First of all, i want to say that i really like the dashboard design, it manages to marry "simple and intuitive" with "rich of information".
What i would like to know is how are we supposed to talk to it? i'm guessing the current state is just a mockup and is not ready yet to actually receive information from the satellites, but at some point it will be ready.
When that happens, i'm guessing there will be a specific communication format that our satellite needs to honour in order to be understandable by the dashboard. Is that so? or will you offer something like the decoders from the TTN dashboard and we'll be free to make our own format?

Need2Revolt

Additionally, i've found out that the TTN console automatically assigns a device address when registering a device and it cannot be changed.
This means that i can set the network session key and the app session key coming from the dashboard, but not the device address on the device in the TTN console. This resulted in the TTN console not picking up packets from my satellite.
If i change the satellite code to run the TTN device address, then i can see the packets on the TTN console, but i guess they will not be picked up by the Ambasat console.

How do you envision we approach this problem?

kamprath

Need2Revolt As I understand it, your satellite can either brodcast to your own TTN app, or the AmbaSat console, but not both. This is because the device address is an attribute of the TTN application.

John_Betong

@Need2Revolt

Thanks for your comments and questions. That's great that you like the Dashboard design. You are correct, it is work in development but it does already support 5 of the 8 sensor types, with GPS, UV and Carbon being added shortly. So that your AmbaSat can 'talk' to the Dashboard, your code should follow the payload format as detailed on gitHub. Specifically, please take a look at the Sensor 03 example which demonstrates the data payload format. We have developed the decoders on the TTN side to handle these structures. You are of coursr free to create your own structures and use your own TTN account or, as you write, you are free to create your own format.

fredricraab

John_Betong

John,

Actually where are the payload formats defined and specifically for the UV sensor? I've looked in both release/source/examples and prototype/Source/src but can not find them. Also, is the UV sensor now supported by the dashboard? If not, do you have an estimated date? Thanks,

John_Betong

@fredricraab,
The payload formats are defined in main.h. eg.

struct
{
uint8_t sensorType;
uint8_t humidity; // humidity percent
float temperature; // temperature in degrees C
uint16_t voltage; // in millivolts
uint16_t pressure; // hPa
uint16_t gas; // kOhms
float altitude; // meters
} packetData;

For the moment, we suggest adapting the above to meet your UV structure. Once we've completed and tested the revised UV code, it'll be posted to GitHub and yours can be replaced with the TTN-compatible structure.