I have written a new library for communicating to my SMEC via DRBII:
http://github.com/cout/drbii
http://github.com/cout/ftdic
It runs on linux and is written in ruby. I have written a simple tachometer program in opengl which I'm hoping will serve as the basis for a DIY HUD.
I have combed through the turbonator source code and have implemented the DRBII protocol to the best of my ability without being able to plug in.
Problem is, when I do plug in, before I send anything, I get a never-ending a stream of null bytes (at one point I did send a byte, and the computer just echoed it back to me over and over).
I have connected the orange (TX?) wire on the FTDI cable to the green (RX?) wire on the SCI. I have also connected the yellow (RX?) wire on the FTDI cable to the pink (TX?) wire on the SCI. Since I am using SCI, I have enabled bitbang mode in libftdi.
1. Is this behavior (constant stream of bytes) expected?
2. What baud rate should I be using? I've tried both 7812 and 976. I'm not (yet) sending the command to enter high-speed mode.
3. How do I know if my cal has the high-speed logger enabled? Not sure if this will help, but here's a pic of the IC:
It is a cal from shelgame, but at the moment that's all I know.