Bike PowerBike Power and Bike Crank Torque Frequency can both be received by the yellowcog Pilot devices. They are more complex than device types such as speed and cadence and can produce quite a lot of information (normally at 4 or 8Hz). The maximum number of output streams of data that a specific power device can provide (it depends on the sensor, not the Pilot) may include some or all of the following:

  • Power, 16 bits, Watts
  • Speed, 16 bits, meters/h
  • Distance, 32 bits, cm
  • Cadence, 8 bits, rpm
  • Average Power, 16 bits, Watts
  • Pedal Power, 8 bits, %
  • Accumulated Power, 16 bits, 0.01kW
  • Output Variation, 16 bits
  • Left Torque, 8 bits, %
  • Right Torque, 8 bits, %
  • Left Smoothness, 8 bits, %
  • Right Smoothness, 8 bits, %
  • Accumulated Torque, 16 bits, 1/32Nm

There are many Bike Power Products on the marker and our Bike Power Sensor help gives information on configuring them.

Wheel Properties

Some calculations require the wheel (or equivalent) circumference so cadence can be converted.

prop wheel

Wheel circumference: This is needed to calculate distance and speed

Data Precision: this is now deprecated.

ANT Properties

 prop ant

Most of the properties in this section should be left at their defaults if you are using a consumer sensor. If you are providing connectivity to your own custom device then the properties will need to be altered.

Available options are:

  • Serial Number – set this to the serial number of the target peripheral or to zero for wildcard.

The remaining options should only be changed for custom sensors, standard sensors will cease to function if these options are changed; they are:

  • MoS Type – Master or Slave type.
  • Device Type – the number must match the peripherals device type.
  • Network – Controls the Frequency Offset.
  • Trans Type – this is specific to the way pairing is achieved.
  • Period – the period between data exchanged in ticks of 1/32768 of a second. I.e. a period of 8102 means data is exchanged 4.04 times per second. Altering this from the sensors default will cause sporadic data transfer.
  • Frequency Offset – defined by the network and is the offset from the base GHz frequency. Altering this will not alter the sensor frequency and will stop communications.

Wireless Device Properties

Wireless Properties

All wireless devices share some common properties.

  • Group – see the page on Groups.
  • Enable Late Binding – see Late Binding.
  • Bind in group – see Late Binding.
  • Serial – the serial number of the peripheral. It is not always necessary to have this set correctly but it assists in identification and pairing.
  • Emit Unit Number as – in order to identify a device in subsequent output data it is useful to have the module transmit a stream called Unit Number. The number can be one of:
    • Configured Serial Number – if this device is connected then this module will output whatever serial number you have entered into the config. If you have used a wildcard (serial number set to zero) then this option is not useful.
    • Unit Number – this is an arbitrary configured value for this module. This is useful if the proper serial number is not wanted in the output data e.g. you would like your devices called “1, 2, 3…” not their true serials which may be opaque e.g. “43252, 243352… etc”
    • Remote Serial Number – most devices will transmit their true serial number back, either via the transport protocol or in a separate message. As such, this option can be used with a configured serial number of zero but when the device connects the actual identity of the remote device is available. Note for ANT, this is the 16-bit serial number, for Bluetooth (+LE) this is the low 16-bits of the MAC address.

Basic Properties

Basic Properties

All modules have this panel. Options are:

  • Type – is determined when first adding the module and governs which module properties can be configured.
  • Name – used to identify the module in the module list but may also play a part on the embedded device, for example it may be required for it to appear in the outputted data.
  • Enable on Pilot – if this is set then this config item will be included and enabled when transferred to the Pilot. If not, then it will still be editable on the PC but will not be used by the Pilot.
  • Default Filter – see Streams, Advanced Concepts.
  • User Number – This can be used to identify this module elsewhere in the system. For example, by outputting this number whenever the device is connected. In general, it can be left as zero.