Opened 4 years ago

Last modified 4 years ago

#310 new defect

Fail to connect to "7988-899:ERGORACE II"

Reported by: Stanislav <Bilbob@…> Owned by: anonymous
Priority: normal Milestone: 0.9
Component: Bike Interface Version: 0.8
Severity: minor Keywords:
Cc: Blocked By:

Description (last modified by stefan)

I cannot connect to "7988-899:ERGORACE II"

WARNING: RXTX Version mismatch

Jar version = RXTX-2.2pre1
native lib Version = RXTX-2.2pre2

Connection to ergometer failed at state "retrieveId"

It is the same for RXTX or Socat

WIN XP 32 bit

Change History (5)

comment:1 Changed 4 years ago by anonymous

7988-899:ERGORACE II

comment:2 Changed 4 years ago by stefan

  • Description modified (diff)

comment:3 follow-up: Changed 4 years ago by stefan

  • Milestone set to 0.9
  • Priority changed from high to normal
  • Summary changed from Connection Fail to Fail to connect to "7988-899:ERGORACE II"

I updated the device name in the ticket description.

I suppose that "7988-899:ERGORACE II" has a new communication protocol. Otherwise "retrieveId" should work. I will put it on the list of unsupported devices. Thanks for your report.

comment:4 in reply to: ↑ 3 Changed 4 years ago by anonymous

Is there any chance to support it in short time?
I am willing to donate some money if it works. It has everything I need and I do not want to buy original time limited software.

comment:5 Changed 4 years ago by stefan

The problem is that Kettler does not provide any API or protocol description for their ergometers. That makes it complicated, because one has to reverse engineer their communication protocol. I did this once for the AX1 by iterating through all possible two letter commands via brute force and listening to answers of the ergometer. And I was lucky that more Kettler ergometers used exactly the same protocol.

In the case of 7988-899:ERGORACE II I cannot reverse engineer the protocol since I don't have such a device. So I'm sorry. If the 7988-899:ERGORACE II uses another protocol (which seems to be the case) we have to wait for a developer who owns this ergometer and who is willing to determine and implement the protocol. That's the only chance.

Note: See TracTickets for help on using tickets.