OSTC2 Companion 1.2 error readbyte timeout

[Ramamara]

Dear OSTC2 Experts,

we got 2 new OSTC2 with bluetooth only interface.
We can't get any useful data exchange established.

Since there I can't find an ODTC2 bluetooth companion 32bit version I have to use fallback option on OS X Companion V1.2

1. Bluetooth detects OSTC with correct serial number
2. Companion set to OSTC
3. Going deep in OSTC menu to switch on Bluetooth mode:
message:Starting...Done

4. Companion: Next:
message: Connected OSTC2 #10017,fw 1.78 HW OSTC

5. OSTC2:
message: Service mode eneabled

6. Companion function:Update firmware
- select file v1.81

7. Companion:
message: erase firmware

8. Companion:
message: Error: readByte timeout

9. OSTC2 stays endless in "service mode enabled" until bluetooth on PC is switched off.

I tried same steps for name change.....>error: read byte timeout

10. Companion function: Reconnect crashes companion
not even Quit is possible, cant't end program

11. OSTC2 can't stop service mode

need to force quit, need to switch off bluetooth, need to wait until OSTC2 is coming back

tried also outdate 32bit companion on windows with OSTC3 settings...no success.


grrrrr spent already more time on bluetooth for the firmware update than diving!

Bluetooth on PC works ok:(no problems with speakers, keyboards, phones etc.)
Bluetooth on OSTC2 can obviously establish pairing and connect

Any ideas?

[Ramamara]

Same bluetooth trouble under SUBSURFACE software:


BT connection established
Log download selected for: dev/tty/OSTC10017-SPP
OSTC2 receives command and switches to: Service mode enabled

Error: Dive data import error

reconnect obviously not possible.
OSTC2 stays in: Service code enabled under bluetooth for many, many, many minutes until its finally decides to come back to user menu

All also tried under OS X but the bluetooth stuff seems to be not so easy

[heinrichsweikamp]

Hi,

Try a smaller distance between the OSTC and the Mac. Maybe it's only related to an intermittent connection.

regards,
Matthias

[Ramamara]

Hi,


with shortest distance 40mm no improvements.

1.As before Bluetooth connection established without problems
The dive computer OSTC2 device switches to: Service mode enabled

2. Companion 1.2: OSTC2 message: PORT tty.OSTC100117SPP: not an OSTC2
But for sure I have only 2 OSTC2!

Bluetooth to all other devices then Heinrichsweikamp Dive computer work fine.

But with the oSTC dive computer I only get problems.
Each trial it is possible to establish communication but obviously either the OSTC2 firmware or the companion software or both are not working ok.

[heinrichsweikamp]

Hi,

To find out where the problem is, have you tried any other software (e.g. Subsurface) yet?

Regards,
Matthias

[Ramamara]

Hi,


all OSTS tools do not work:
OSTC COMPANION 1.2 on OS: failed
OSTC COMPANION 1.2 on WIN10: failed
OSTC COMPANION on WIN8.1 32: failed
OSTC Config on WIN8.1 failed
OSTC DUMP on WIN8.1 failed
OSTC PROFILE on WIN8.1: failed
OSTC recommended SUBSURFACE on WIN8.1: failed
OSTC recommended SUBSURFACE on WIN10: failed
OSTC recommended SUBSURFACE on OS X: failed

Third party app DIVINGLOG 5 and DIVING LOG 6 on WIN8.1 32bit: OK(tu)
all good, no problem at all with downloading all dive records even in demo mode.
Excellent support by programmer!!

[Ramamara]

Suggest that OSTC team work together with the expert from DIVINGLOG team to allow configuration and upload of new firmware via DIVINGLOG software.

DIVINGLOG 5.0 and 6.0 was very easy and fast to use.
Not one bluetooth trouble.
No software crashes

[glance]

There are a lot of confusions with the new ostc called "OSTC 2". It uses the same protocol as the OSTC 3, CR and Sport, and _NOT_ the same protocol as the older OSTC, mk2, 2N or 2C.

When you use the current released version of subsurface, the "OSTC 2" didn't exist, so you need to choose "OSTC 3".

[Ramamara]

initially I was very confused about all the OSTC 2 naming.

But finally I was told that all the Bluetooth models can be used in same software configuration.

That's why I use the OSTC3 setting in the WIN32 Companion, SUBSURFACE etc.

Very confusing is that the OSX OSTC Companion software sometimes establishes the connection, switches the OSTC2 to SERVICE MODE and than complains that the OSTC2 is not an OSTC2 although it can read the serial number and firmware rev.

With DIVING LOG (even on small travel computer with WIN32) we don't have all this problems. DIVING LOG simply works with OSTC2 settings!

Hopefully the DIVING LOG team will bring new version with firmware and CF update functions soon.

[heinrichsweikamp]

Ramamara Wrote:
-------------------------------------------------------
> all OSTS tools do not work:

Some of these tools have a "log errors" function. Can you please post the error log?

Regards,
Matthias

[TnT]

Under the hood, subsurface and divinglog are both using the libdivecomputer library to communicate with the OSTC. So there shouldn't be any difference. If one applications works, the other should work too. Especially when running both on the same system (e.g. same bluetooth chip, same drivers, etc)!

The list of supported devices is also obtained from libdivecomputer. The old OSTC's are labelled "OSTC", "OSTC Mk2", "OSTC 2N" and "OSTC 2C". These are all using USB connection. The new version with bluetooth is labelled "OSTC 2". If you don't have this option, that means the application is using an older version of the libdivecomputer library. In that case, just use "OSTC 3". It's only another name. There is no functional difference.

[HäschTäg]

Hallo Zusammen

Habe das gleiche Problem:

Ich verbinde über einen externen Bluetooth Dongel.
Der PC (Win7 64 bit) erkennt den TC perfekt mit Seriennummer.
Wähle im Companion 1.2 den OSTC 3 und folgendes passiert:
Open Port COM1
Getting Model
Getting identy
PortCOM1: readByte time out

Selbst SUBSURFACE kann nicht mit dem TC verbunden werden.


Hat bereits einer die Lösung?

Grüsse Alain

[Ramamara]

Hallo Alain,

leider gibt es bisher keine Lösung.
Bitte sende die PC, Buetoothmodul Spezifikationen die Du einsetzt an den Hersteller.

Mir hat der Hersteller angeboten, dass ich die Geräte bei denen updaten kann.
Ist zwar ziemlich unpassend für einen opensource beworbenen TC, aber zumindest geth es dann vorwärts.

Den Download der Tauchgänge bekommen wir hier mit DIVINGLOG 5 und 6 problemlos hin. (sogar problemlos auf WIN32 Reisenotebook)

Die SUBSURFACE Geschicht funktioniert bei uns auch nicht.

[HäschTäg]

Soll das dann heissen:
Ich kann meinen Tc überhaupt nicht mit dem PC über Bluetooth verbinden?
Als erstes wollte ich eigentlich den Text auf der Startseite ändern und eine kleine personalifizierung mit Namen oder so erstellen.

Habt Ihr ein paar free ware Tauchlogbücher als alternative da subsurface nicht klappt?

Grüsse Alain

[Markus G]

Hallo Alain,

hört sich ähnlich an wie das Problem das ich hatte.

Hast du schon meinen Thread "Firmware Update OSTC2 Fehler=> WIN7 GELÖST" gelesen?

Eventuell hilft es dir weiter, ich hatte auch die verschiedensten Fehlermeldungen bevor ich es geschafft habe meinen OSTC2 mit dem PC zu verbinden.

Mit freundlichen Grüßen

Markus