ONYX-488: Crash in Tanita runner

[ymarcon]

Jira issue originally created by user @plaflamme:

See attached InstrumentBootstap.log file.

pr 21, 2009 9:48:37 AM org.obiba.onyx.jade.client.JnlpClient main

SEVERE: Unexpected error while initializing runner {}

java.lang.RuntimeException: Communication error with the Tanita BC418, exiting runner...

at org.obiba.onyx.jade.instrument.tanita.Bc418InstrumentRunner.sendReceive(Bc418InstrumentRunner.java:119)

at org.obiba.onyx.jade.instrument.tanita.Bc418InstrumentRunner.resetTanita(Bc418InstrumentRunner.java:233)

at org.obiba.onyx.jade.instrument.tanita.Bc418InstrumentRunner.initialize(Bc418InstrumentRunner.java:346)

at org.obiba.onyx.jade.client.JnlpClient.main(JnlpClient.java:47)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.sun.javaws.Launcher.executeApplication(Unknown Source)

at com.sun.javaws.Launcher.executeMainClass(Unknown Source)

at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)

at com.sun.javaws.Launcher.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Apr 21, 2009 9:48:37 AM org.obiba.onyx.jade.client.JnlpClient main

[ymarcon]

Comment created by @plaflamme:

Attached screen shots also (HW.doc)

[ymarcon]

Comment created by mboulang:

This is working fine on my machine when running the most recent version of BC's configuration.

This seems to be the result of a hardware connection problem. The Tanita 418 needs to be connected to a PC with a cable that has the correct specifications (not standard serial cable). See BC-418 documentation for those specifications.

[ymarcon]

Issue was closed with resolution "Cannot Reproduce"

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because no further activity occurs. Feel free to re-open it if it is still relevant.