Establishing an ANT connection with the Shimano Di2 groupset

On my Edge 830, I am trying to connect to the Shimano Di2 groupset. Since the complete interface hasn't been officially published, I am using the channel configuration found here and the code I am using to connect to the ANT device is the following:

deviceConfig = new Ant.DeviceConfig({
	:networkKey64Bit => [0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX, 0xXX],
	:deviceNumber => 0,
	:deviceType => 1,
	:transmissionType => 5,
	:messagePeriod => 8198,
	:radioFrequency => 57,
	:searchTimeoutLowPriority => 10,
	:searchThreshold => 0
});

GenericChannel.initialize(method(:onMessage), new Ant.ChannelAssignment(Ant.CHANNEL_TYPE_RX_ONLY, Ant.NETWORK_PRIVATE));
GenericChannel.setDeviceConfig(deviceConfig)

While I am able to open the channel and establish a connection when using the Connect IQ simulator, running the same code on the device results in an error about the ANT private network key.

Error: System Error
Details: 'No network key given, the ANT Private network requires a valid network key'
Time: 2021-03-14T13:21:10Z
Part-Number: 006-B3122-00
Firmware-Version: '7.10'
Language-Code: deu
ConnectIQ-Version: 3.2.5
Filename: Ant
Appname: Generic ANT
Stack:
...

Does anyone have any experience with establishing a connection with the Shimano Di2 groupset and possibly suggestions for how to resolve the issue with the private network key?

Top Replies

Jan Čapek over 4 years ago in reply to gmoelter +1

Hi, I posted it as bug report here:
forums.garmin.com/.../ciq-apps-on-edge-devices-can-t-communicate-via-ant-private-channel
I hope you don't mind I used your code samples. Please do vote for it here.…

All Replies

0 jim_m_58 over 4 years ago

This is a standard sensor on that device. Why not just use it that way? You won't be able to use it as a standard sensor and then do your own ANT interface for it.

0 gmoelter over 4 years ago in reply to jim_m_58

Unfortunately, the provided API functions cannot be used to communicate with the Shimano Di2 groupset, as mentioned in the API documentation here. Regardless, I have tried to use the API functions as below:

Di2State = new AntPlus.Shifting(new AntPlus.ShiftingListener());

[...]

if (Di2State != null) {
    var shiftState = Di2State.getShiftingStatus();
    var frontGearIndex = shiftState.frontDerailleur.gearIndex
    var rearGearIndex = shiftState.rearDerailleur.gearIndex
}

However, this does not yield sensible results, with both gear indices being invalid (Toybox::AntPlus::FRONT_GEAR_INVALID & Toybox::AntPlus::REAR_GEAR_INVALID).

As mentioned above, the generic ANT channel yields the right information, however, only when used with the Connect IQ Simulator and not when used with the Edge 830.

0 jim_m_58 over 4 years ago in reply to gmoelter

The 830 can not have the sensors paired in the FW if you want to do your own ANT.

0 gmoelter over 4 years ago in reply to jim_m_58

Unfortunately, this does not seem to be the problem. The Di2 sensor is not paired so it should not interfere when opening the generic ANT channel.

0 gmoelter over 4 years ago

Perhaps this blog will be read by Garmin experts who can answer the question, why the Edge 830 does not accept the private network key.

0 Jan Čapek over 4 years ago in reply to gmoelter

Hi,
1) did you write bug report to https://forums.garmin.com/developer/connect-iq/i/bug-reports ? I can't find it there.
2) I don't think it is ok to publicly share private ant keys...

0 gmoelter over 4 years ago in reply to Jan Čapek

Hi Jan

1) No, i didn't.

2) Sorry! 3 month ago, i found the key here https://github.com/kwakeham/DiHack/wik and i thought it wasn’t a secret...

0 Jan Čapek over 4 years ago in reply to gmoelter

Hi, I posted it as bug report here:
forums.garmin.com/.../ciq-apps-on-edge-devices-can-t-communicate-via-ant-private-channel
I hope you don't mind I used your code samples. Please do vote for it here.

According to my experience:
not reported bug - 0% probability of fix
bug reported via discussion forum - 0% probability of fix
bug reported via bug report section
- 5% probability of fixing the bug in short-term
- 45% probability of fix in long-term - >6 months or years
- 20% probability that already fixed bug in HW FW will be soon commited back - especially true for EDGE devices

But at least we will have some change now. ;)

0 gmoelter over 4 years ago in reply to Jan Čapek

Thanks.