That old chestnut: Only this time, I _REALLY_ need to know the answer.

Ok. so I have many, many, many times tried to find out some guidance on the number and type of fit fields that an activity or device can handle.

I am aware of the following caveats:

1. It is device and software dependent

2. It depends what else is running

3. There are lots of unknowns

However...

I have code that absolutely works fine on every single device that it is installed on except for one and it crashes only on the Session.createField line. I cannot replicate this one in the simulator at all. I do not have access to (or knowledge of anybody who has ever purchased) the device in question apart from the person who has so far clocked up an identical error on three fields in a related set of fields.

- In the simulator, I have a peak memory of 27.4KB out of an allowed maximum of almost 128KB. So it is not memory.

- In the simulator, despite trying any number of different routes to start and stop activities, I cannot get it to break. So it is not a crass coding error.

- In the simulator, I have tried discarding and restarting new sessions without problems. So it is not an illegal operation overwriting an existing field.

But clearly I have hit some limit or restriction on creating FIT fields.

So, please, one more time with feeling:

I am aware of all the caveats about what you can tell me about FIT field creation and FIT field limits, but I still need to know something helpful about what factors play into FIT field limitations so that I can allow for and build around them.

0 Travis.ConnectIQ over 4 years ago in reply to 9635560

9635560 said:
Travis.ConnectIQ said:
None of the built-in data fields that are provided by Garmin don't use fit contributions.

Isn't that backwards?

Yes.. Should have said "None of the built-in data fields that are provided by Garmin use fit contributions."

0 9635560 over 4 years ago in reply to Travis.ConnectIQ

Hi,

This is now recurring and the only current, unsolved, unresolved ERA report.

Error Name: System Error
Occurrences: 1
First Occurrence: 2020-12-05
Last Occurrence: 2020-12-05
Devices:
    MontanaÂ® 7 Series: 7.10
App Versions: 0.0.38
Languages: eng
Backtrace:
    DataField_SingleDialBaseView.runOnceFieldSetup:577
    DataField_SingleDialBaseView.compute:649

The line is the same createField line that it has always been, and the Montana7xx is the only device I ever see this for. Equally, I never see a single report - it is always a single, isolated report on THREE distinct data fields for the same device at the same time.

So I am now confident that the answer lies in the answers that I have asked, unsuccessfully, so many times:

1. How many Connect IQ fields can run simultaneously on a single Montana7xx device? Can I confirm that it is more than the two allowed on other Garmin devices?

2. What is the total allocation of memory that is available for the Montana7xx devices across all ConnectIQ fields that are running on a single activity?

I am aware you are getting tired of me starting threads on this and that you think it is something I either don't need to know (despite the fact that I do) or some other reason, but if you can either answer this or give me a way to find an answer for myself short of purchasing a Montana device, I will keep quiet on it for a bit.

0 9635560 over 4 years ago in reply to 9635560

This one is literally my only ERA report at the moment. But it is happening routinely, and only for Montana7xx.

As per the above: I am pretty certain of the cause, but I cannot do anything about it without some more information form Garmin.

Travis.ConnectIQ I literally have no way to proceed without some way to confirm these fairly simple numbers that Garmin has and I do not.

1. How many CIQ data fields can a Montana 7xx run simultaneously on a single instance?

2. What is the total number of bytes of FIT contribution across the entire activity from all CIQ fields that are allowed?

3. Is there an additional upper limit to the total number of FIT contributions across the entire activity that might come into play?

How do the numbers for 2. and 3. for a Montana 7xx compare to the same numbers for FR735xt because the former appears to crash, where the latter runs safely with three CIQ instances of my fields?

0 9635560 over 4 years ago in reply to 9635560

And again...