Why the limitation to 2 custom data fields?

Why is there still a limit of two custom data fields? I am sure most modern Garmin watches can handle more.

It would be so much easier to just create single fields for dedicated purposes, rather create the one big field that covers everything people might want.

Top Replies

jim_m_58 over 3 years ago in reply to Former Member +1

The Epix and fr735 handle more than 2 as do Edge Devices. For the 735, the cost is lack of access to widgets.

It's all about the memory available to CIQ, where the oldest devices have a limit of 16k per…

All Replies

0 Former Member over 3 years ago

solved

0 jim_m_58 over 3 years ago in reply to Former Member

The Epix and fr735 handle more than 2 as do Edge Devices. For the 735, the cost is lack of access to widgets.

It's all about the memory available to CIQ, where the oldest devices have a limit of 16k per DF, while the newest ones allow for much larger/more complex DFs.

0 mike over 3 years ago in reply to jim_m_58

So I guess it is much more a marketing decision to maintain a gap between device classes than a technical thing.

0 jim_m_58 over 3 years ago in reply to mike

No, it's all about the memory allowed for CIQ in a native activity. Otherwise there would be more possible on high end forerunner and fenix devices.