Unable to connect OSTC to Mac

[Niko]

Hello,

I have just acquired an OSTC 2N and can't manage to connect to JDivelog (Mac).
I have correctly installed Jdivelog and ftdi drivers.
When going to settings, I can only see bluetooth-modem and bluetooth-pda port coms. I can't see any regular com port (it is plugged via usb). Maybe this is the problem ?
Also, when connecting my ostc nothing displays on the ostc screen (not sure it is even connected then).

Please help !
Needless to say, I am far from an IT expert

Thanks

[Bardass]

There are many, many problems with Jdivlog which is not updtodate with ostc.
Try ostc planner for Mac

[scubatinoo]

Hi Bardass

I have no problem at all (*) with JDiveLog and MacOS X (10.8.2). But i'm talking only about downloading dives - not editing CF's...

@niko:
Just make sure you have the newest version of
- JRE (Java Update!)
- JDiveLog
- FTDI drivers
- MacOS

(*) I have a problem when i plug the USB-Cable into an USB-Hub. So make sure you connect your OSTC directly to your USB-Port on your Mac!

[Niko]

Hello,

Thanks for your prompt replies.
I didn't know OSTC planner, can we also configure all OSTC CF's with it ?

@scubatinoo, I believe I have the latest versions of jdivelog / FTDI drivers and MacOS... but I don't know about JRE. Can you please tell me how to do the java update ? any link and documentation ?

Thanks
Niko

[heinrichsweikamp]

Also, give subsurface a try: http://subsurface.hohndel.org/ It's easier to install on a MAC and will test the general connectivity. If Subsurface works I'm sure we get jdivelog working, too.

regards,
Matthias

[Niko]

Hi Matthias,

I am unable to connect with subsurface.
I choose "OSTC" as dive computer, then the "device name" that is proposed is:
/dev/tty.SLAB_USBtoUART -> not sure what this is !

When trying to download dive information (following subsurface documentation), I have the following error message:
Unable to open Heinrich Weikamp OSTCN (/dev/tty.SLAB_USBtoUART)

...still desperate !

[scubatinoo]

Niko, the device name has to look something like that: /dev/tty.usbserial-A4SHCQSJ
As far as i can remember i had to change the name manually. JDiveLog will offer you the name automatically...

Did you connect your OSTC directly to your Mac (not via USB Hub)? Did you first connect, then turn on the OSTC and then open the software? Make sure that the software is closed properly when you connect - use cmd+q to close JDiveLog!

For Updates just use the Apple on the very top left --> Software update. This will check with App Store for newer versions... There are also some helpfiles on the FTDI Website. Some of them will explain how to find the device name. Maybe you're going to have a look there too.

[scubatinoo]

Maybe this Guide will help you to check if the FTDI Driver is installed properly:
http://www.ftdichip.com/Support/Documen ... AC_OSX.pdf
Have a look on page 9...

[Niko]

thanks scubatino.... will check all this tonight
softwrae update is all good
I hugged the ostc directly (not via a hub)

Maybe you can tell me something, when you plug the ostc in, does it display something on the ostc screen showing it is indeed plugged ? The battery being fully charged I don't have any sign on the ostc screen, is it normal ?

Many thks for your help
Niko

[scubatinoo]

Yes, the battery color will change when connected to usb... Turn the OSTC on and you'll see if it's charging.

[Niko]

Hi scubatinoo

Many many thanks !!!!!
Actually the problem was ti the usb cable itself, it didn't connect well to the ostc because the plastic plug around the usc connector was too large and didn't plug well in the ostc. I cut some of the plastic -> then the battery changed from green to yellow (connection was ok !).
Jdivelog works well now !

@Matthias: should should probably check this, the usb plug is to big to fit correctly with the ostc.... did you have this problem before ?

Good that it works, I was kind of desperate !
Thanks to you all
Niko

[tiefunten]

Yep, this problem with some of the usb-cables was reported before.

[scubatinoo]

It's not a common problem, but a reported one... I'm glad you figured that out! Now you can write down the device name from JDiveLog and use it with Subsurface too, if you like

[heinrichsweikamp]

Subsurface makes rapid progress currently. It's really worth a try.

Regards,
Matthias

[scubatinoo]

Did you compile your own actual version? Because 3.0 is not yet ready to come... And 2.1 i personally don't like very much...

[heinrichsweikamp]

Yes, which is very simple using Linux...

regards,
Matthias