CIQ error DataFields RunScribePlus & StrydPower

OnlyTwo, I'm talking with our ANT+ guys right now. I'm not sure if these datafields are using a generic channel or ANT+ Running Power. Are you using other sensors along with them? Have you checked to see if data shows up on both screens even if only one power meter is running? There are a limited number of communication channels available on the ANT/ANT+ sensor hub. It's possible that both are utilizing two channels, plus whatever else has opened a channel with your sensors and It's maxing out. I'm grasping a little admittedly, but I'll keep trying to figure it out.

-Coleman

sitting at my desk...

here we go...not much but a nice read...

sitting at my desk

runscribe has two physical sensors
stryd has one physical sensor

CIQ datafield setup
-both datafields are setup with filled in sensor ID so they only connect straight to their appropriate sensor
-runscribeplus setup to show power data in first field
-runscribeplus setup to show only the one field
-runscribeplus setup with entered runscribe sensor id's part of serialnumber for both left and right sensors
-strydpower setup with entered sensor id ANT+ id


datafield setup
-datascreen with four fields
-top field contains runscribeplus with power data
-bottom field contains stryd with power data
-left field contains speed data
-right field contains cadence data


runscribe sensors turned off in sensors menu on the watch
stryd sensors turned off in sensors menu on the watch

-open activity with one screen for runscribeplus, strydpower, speed, cadence
-runscribeplus field shows the text 'searching null...'
-strydpower field shows the text '3S POWER SEARCHING...'
--waking the stryd sensor triggers a CIQ! error on strydpower field
--while CIQ! error, shaking and moving the stryd sensor speed and cadence keep zero



runscribe sensors turned off in sensors menu on the watch
stryd sensors turned off in sensors menu on the watch

-open activity with one screen for runscribeplus, strydpower, speed, cadence
-runscribeplus field shows the text 'searching null...'
-strydpower field shows the text '3S POWER SEARCHING...'
--waking the runscribe sensors shows power data on runscribeplus field
--strydpower field shows the text '3S POWER SEARCHING...'
---while CIQ! error, shaking and moving the stryd sensor speed and cadence keep zero



runscribe sensors turned off in sensors menu on the watch
stryd footpod turned on in sensors menu on the watch

-open activity with one screen for runscribeplus, strydpower, speed, cadence
-runscribeplus field shows the text 'searching null...'
-strydpower field shows the text '3S POWER SEARCHING...'
--waking the stryd sensor triggers a CIQ! error on strydpower field
--while CIQ! error, shaking and moving the stryd sensor, speed and cadence sometimes shows data



result is that strydpower field goes into CIQ! error when stryd sensor is kicked to life
and while a second screen is setup with a runscribe data field

happy hunting

i hate this forums layout crap json error after json error ...aaaarghh

frustrating

forerunner 920XT firmware 990
same behavior

ERROR: System Error
DETAILS:
STORE_ID: 660A581E5301460C8F2F034C8B6DC90F
CALLSTACK:
@PC = 0x10000505

FR935 FW 1157 beta

test with third datafield using ANT+ ID to connect to external heart rate sensor

test subjects datafields Auxiliary Heart Rate & RunScribe Plus & Stryd Power

datafield combination ok
-Auxiliary Heart Rate and Stryd Power
--both data fields work together without any problem
--both data fields also show the same font size and type adapted to the UI screen layout

datafield combination ok
-Auxiliary Heart Rate and Runscribeplus
--both data fields work together without any problem
--data field runscribeplus has different font size and type not suitable for this UI screen layout
--data field auxiliaryheartrate has a correct font size and type adapted to the UI screen layout

datafield combination CIQ!
-Stryd Power and Runscribeplus
--data field strydpower generates a CIQ! error
--data field runscribeplus has different font size and type not suitable for this UI screen layout
--data field strydpower has a correct font size and type adapted to the UI screen layout

FR935 FW 1157 beta

test subjects RunScribe Light & Stryd Power

datafield combination ok
-Stryd Power and Runscribelight
--data field runscribelight shows power
--data field strydpower shows power
--data field runscribelight has different font size and type not suitable for this UI screen layout
--data field strydpower has a correct font size and type adapted to the UI screen layout

at last...what a mess

thank you FlowState for the quick reply

ok, that is how it works for GC

I suppose and hope this manifest can not change with app updates ?

stays the problem handling fit files with third party software !

how does an external party derive those empty developer data fields in the fit file ? without knowledge of the application manifest content

strange concept

For a CIQ app generated field, a "native field" number can be used, and 3rd party site can use that fitcontrib data in place of that native field in the .fit

jim_m_58, that is what Stryd Power datafield does with a couple of their developer field names

but for this workout there were only empty developer field names from the RunScribe Light datafield

so what you are saying is that third party can only know what kind of data it is when the developer filled in these native fields

and only Garmin knows the developer fields names from the application manifest content

stuff enough to discuss in a new thread ;)