Storage a fit message more than 32B in datdfield.

Greetings,

[Status]

Now, I'm working on a datafield for EGDE series device such as edge830. And I need to storage many data, which is get from my power meter sensor. However, I need at least 41B for such data per fit message.

[Question]

1. If there is a way and I can create two fit file and data is divided into two parts for each.

2. If I can use watchapp api in datafield, and in watchapp I can storage 256B for each fit message.

Glad to hear any thoughts on this issue.

Thank you.

0 FlowState over 3 years ago

5953548 said:
1. If there is a way and I can create two fit file and data is divided into two parts for each.

No.

5953548 said:
2. If I can use watchapp api in datafield, and in watchapp I can storage 256B for each fit message.

No.

Is it possible to use 8-bit or 16-bit types to save memory? I'm guessing you're already doing this given your requirement of 41 bytes.

0 FlowState over 3 years ago in reply to FlowState

Is it possible to have 2 data fields, each of which will connect to the power sensor and save different kinds of data?

(I don't know if your power sensor will accept multiple connections, though.)

Otherwise it seems like your only option is to write a device app.

0 5953548 over 3 years ago in reply to FlowState

Yes, I have restored the data to binary storage Bit by Bit. Every bit in 41 bytes is necessary.

0 5953548 over 3 years ago in reply to FlowState

Thank you firstly,

Is it possible to change the fit message name? It has 64 bytes space. But it seems don't have field delete function and I can't use createField() in compute().