Currently hacking the FTDI driver for OSX so it recognises it and I can start talking to it. Then I'm going to measure VFO drift overnight ![ThumbsUp :-+](https://www.eevblog.com/forum/Smileys/default/icon_smile_thumbsup.gif)
Pretty please, drop a note here or in a PM when you're done and you can save me from having to do exactly the same.
I've given up for the night. The kernel is refusing to accept the unsigned FTDI driver even though I've jumped through the relevant hoops and followed the FTDI customisation. It just wont kextload it. I tried adding the vendor id and product id to the Apple shipped FTDI driver one but I can't edit the Plist.info to add it even as root. Fun will resume tomorrow ![Smiley :)](https://www.eevblog.com/forum/Smileys/default/smiley.gif)
Mine will be with me tomorrow so I may pitch in on the effort if I can get away from my FPGA fiddling for my current project and from necessary pre-christmas tidying. I've done it before but I'm buggered if I can remember how, or where any notes I made at the time have got to.
Basically FTDI allow the purchaser of large volumes of FTDI ICs to customise the vendor and device ID of the FTDI controller. TTi have done this. Ergo for every damn vendor and product you have to add a hint to the driver so the kernel knows that driver belongs to the vid/pid pair.
You don't have to be a large volume purchaser, the reprogramming is (or at least was) documented and doesn't require any programming hardware, just access to the chip over USB. All as far as I can remember, again, something that I've done before, once, too long ago for it to come to the surface of my mind fast enough..