Wednesday, May 15, 2013

I have no comm port so I must scream

Six weeks ago I embarked on what should have been a fairly mundane task of getting NMEA data from a GPS and some older Simrad gear imported into a laptop running Nobletec's Odyssey Time Zero navigation software. This wasn't my first time at the NMEA data rodeo, and the results were pretty typical. Using the existing Prolific serial to USB converter I could only have one talker, and one listener, not that I didn't try to get a second talker to work. Alas, but not unsurprisingly one talker only for you, and some of the older NMEA version data was getting lost in translation. To help with these issues a Actisense NDC-4 was purchased.

The little box arrives, and I install it. It's a pretty straight forward job. The NDC control panel software loads up from the CD, The comm, and USB port drives get installed. I find the comm port (6), and set it for 36,400 baud. Open the control center, and click on port 6, and also 36,400, and it all works as advertised.

I connect the GPS, and data flows to the Nobeltec system. Excellent methinks. I create various configurations to learn how to do them, and whoa, it's almost five. The lure of happy hour tugs at me. Everything gets shut down, and I'll come back in the morning to wrap this install up. That was six long weeks ago, and until yesterday I couldn't get it to work for love or money.

A fresh new day sees me on the boat. I fire up the computer, and add a second talker to the Actisense box. I open the control panel, and it's there, but now insidiously ghosted. Something must have gotten changed. Control Panel/Device Manager/Ports, and there it is on comm 6 labeled as Actisense, just like yesterday. I check the speed, and port configuration. That's all fine. I look at the USB port. That's fine also, and it says in both cases "The device is working properly." No it isn't you piece of claptrap PC junk. It ain't working properly at all. Back to the control panel and check the speed, and port. Both are correct, but the little box won't connect to the comm port. The PC knows it's there, if I unplug it from the computer, it disappears from the port list. Plug it in and it reappears. It's just mocking me.

An email goes off to Actisense in my usual windy fashion describing what I have done and how I wired the little box. A response comes soonest suggesting I shouldn't have really connected 12 volt power to the little box, ground looping may occur causing my connection problem.

The first aha moment occurs. It seems the manual in the box, is not the full user manual. I download the full manual which discusses powering the box in greater detail, and ship's power is promptly remove from the box. But this doesn't solve the problem. More emails, uninstalling, and re-installing occurs. Crap, I take the disk, and the little box home and install it on my computer. It works perfectly on my computer. More emails, and then the question appears can you verify the drivers you are using are version

Back to the boat I go for the umpteenth time and check. Yes it is. So what do I now know? It doesn't work on the boat's laptop, but it does work on my computer at home, and now my little net book also. It has to be a problem with the laptop unit, although I don't know what. The owner gives the laptop to an IT guru, and it gets scrubbed clean, updated, and all of that promotional stuff you get on a new computer is removed. Meanwhile I'm yachting on the Salton Sea. I get back and try the computer again, nope, same thing. The little box is there, but it isn't. It acts like it can't connect, because it is already connected.

I'm running out of options here. There is one more thing to try. The IT guru did not have the little box when she cleaned up the computer, so I arrange to meet her with the computer, and little box in hand. I plug it in, and show her how to set up the ports, and how it's used. I also show her that everything seems to configured correctly. She takes off fingers flying, and then gets a little frustrated, and confused. Then the really big aha moment occurs. On a whim she rolls back the driver for just the USB port back one generation to, and the little box works. It was an orgasmic moment, in a geeky sort of way, and I now know what happened.

When I took the little box back home, I plugged it into my computer, and it no longer worked. Mr Gates had been my undoing. When I first installed the little box, the CD was the source for the drivers, and the USB driver was version Both my computer, and the boat's laptop had an automatic Windows 7 update, which noticed the out of date USB driver, and did us the favor of updating it to a current version. This was not currently compatible with the Actisense NDC-4. Subtle it was. See it you could, but work it would not. PC's just drive me nuts. Six freaking weeks. The really smart IT guru set up the laptop to never allow an update for all time to come, and I'm fine with that.

The Actisense products are great, and their tech support people stuck by me in spite of my mildly acerbic emails at times. I understand they are working on this quirky little automatic update wart.


  1. It's not really the PC (the metal) that's the problem here, it's the business models around software, which deliver much of their value not to the customer but to others, in the form of secrecy. The expediently bankable value of most software lies in secrecy, which is fundamentally in conflict with a customer's objective of being fully informed to make a combination of hardware and software function correctly.

    As somebody once said, dealing with the secrecy we've become accustomed to in commercial software is like maintaining a car with its hood permanently welded shut at the factory.

    The basic problem here is that at a certain point you are simply not allowed to know how the OS and software actually works as opposed to how it appears to function. Given that OS and associated product business models depend on tightly maintained secrecy, customer interaction with most software is restricted to ritual incantations.

    Windows 7 and the plethora of vendor software here gave you "bad magic"; the spells you were provided with didn't work. Software isn't magic; magic doesn't exist and we shouldn't be forced to pretend it does. But for some reason we're continuing to buy into the "magic" software model, making even the best of us appear like superstitious primitives ignorantly dealing with a force of nature.

    Short of having complete access to internals you're never really going to know what's controlling your access to Happy Hour. Hopefully this is just a phase and more of us will remember our scientific abilities at some point, starting with rejecting alchemists with their secret writing and attempts to show us how they're going to turn their lead into our gold (or that is to say, substitute our gold for their lead).

  2. I think this could be a problem with the FTDI chip, FTDI decided to pull the plug on support for older FTDI chips in their software.

    The problem was that cheap immitation FTDI cables were sold, using the FTDI drivers. In the new drivers ALL older FTDI chips (real and fake ones) are blocked.

    Actisense uses this chip I guess.

    I have the same problem with a GPS puck, the BU-353, you have to go back to the older driver.

  3. Erik's remark (which sounds highly plausible) nicely illustrates my extensive bloviation, in far fewer words.

    "Sorry, your magic spell is deactivated. Try using a decompiler to figure out how to make your kit work again, but bear in mind it's illegal to do so."


Note: Only a member of this blog may post a comment.