forum.heinrichsweikamp.com

All of a sudden my iMac decided I don't have a valid serial port anymore. Meaning I can't download my dives and I can't use OSTC planner.

I've downloaded and installed the FTDIUSB serial and installed it. It still won't work.

I'm running OSX 10.8.5.

Any ideas guys ?

Maybe you can find some help here in the Documentation:
http://www.ftdichip.com/Support/Documen ... AC_OSX.pdf

As far as i remeber there's a section about checking if the drivers are installed properly...

Thanks Tinoo,

I did everything on the page, even upgrading to Maverick (10.9) but it still doesn't work.

I'm at a loss so any help would be appreciated.

BTW. I tried changing cables and I tried every USB port I have

Jean-François Wrote:
-------------------------------------------------------
> BTW. I tried changing cables and I tried every USB
> port I have

Is the OSTC charging when connected by USB? The battery
symbol has to change the color - if not the connection
is not propper...

Yeap, the cables are working fine, the unit is charging.

I just don't get it and it pisses me off...

firmware 2.90 ?

Any corrosion on the contacts?

Regards,
Matthias

Firmware 2.90 and no corrosion on the contacts.

I was able to upgrade to 2.90 with OSTC Planner without problems and and I can charge the battery too.

I downloaded my dives the day prior to my trip to St Cyr and when I came back I wasn't able to do it. In the meantime no one used my computer....

I know that does not help much but almost every unit where people tried "all ports" and "dozens of different cables" on a "few different PCs" worked just fine here and in the end it was (only) a driver issue after some kind of system update.

The firmware itself has no influence on the connectivity. The USB port is enumerated in hardware. Even OSTC with totally corrupted firmware enumerate with an virtual COM port.

regards,
Matthias

OSTC Planner and 2.90 don't work fine together
OSTC Planner can read CF but doesn't write to OSTC

I'm sure it's a driver issue. But I can't seem to be able to install them.

I thought maybe some people encountered the same issue and could help me.

Thanks anyway guys.

Are you using a different USB cable then before?
Some cables charge fine but the head is to big to be seated all the way and to provide proper contact for data-pins.
Make sure to use the same cable which had a good data-connection before.
Some people solved this issue by cuting the head of the cable a little slimmer to enable it to be properly seated all the way.

What kind of Software are you using for Logbook? I had some problems with JDivelog in the past, but now with Subsurface everything works fine...

I'm using Mac Dive and I never had any issues with it. I'll keep investigating.

Have you tried another Mac or a PC?

swissdiving Wrote:
-------------------------------------------------------
> Have you tried another Mac or a PC?


As dumb as it sounds, I didn't think about that solution. I'll try on my wife's iMac.

Cheers

Mate thats what the forum is here for...
...brainstorming

I've solved my problem. Posting my solution so other can benefit from it.

I thought my iMac was a 64bit architecture (I still think it is...) but the 64bit drivers wouldn't work. I tried it on my wife's computer and still no joy. So I've decided to install the 32bit drivers and... it worked. Go figure.

I still don't know why it was broken in the first place but it works now.

Thanks everyone for your input.

Jean-François Wrote:
-------------------------------------------------------
> I've solved my problem. Posting my solution so
> other can benefit from it.

I'm glad that you figured it out!

> I thought my iMac was a 64bit architecture (I
> still think it is...) but the 64bit drivers
> wouldn't work. I tried it on my wife's computer
> and still no joy. So I've decided to install the
> 32bit drivers and... it worked. Go figure.

Interessting indeed! Because all the links for
the different architectures x86 (32-bit), x64 (64-bit)
and PPC point to the same file...

I found this in the Documentation of the FDTI-Driver:
OS X 10.9 (Mavericks)
7.1 Using VCP or D2XX with OS X 10.9
Th e VCP driver is provided as part of the
kernel in OS X 10.9, therefore no driver
installation is re quired to create a virtual
COM port in Mavericks.

Maybe the manual installation caused some confusion on
your system...

I've read that paragraph too but it's not true. I still needed to install the drivers.

It seems that some devices still require the drivers and others don't. A mistery to me.

Hi,

Thanks for posting the solution, this will definitely help others.

regards,
Matthias

I have hit the same problem.

I have a Macbook Air Intel i7 and an OSTC 2N

Installed the drivers, installed the software and no matter what i do the OSTC Planner cannot see the COM port, the settings remain blank (no value in the drop down list) and just keeps asking me if I have installed the drivers.

There is only one set of drivers that I can use, I have been through all of the FDTI documentation etc and I am still no closer to sorting.

Very frustrated!

If anyone can help I would be very, very grateful.

JC

Hi,

Just as almost any Windows we tested MAC OS will download the drivers automatically (If connected to the internet) upon first connection with the OSTC. Maybe this feature is disabled on your MAC?

Regards,
Matthias