Hi Mitch and Tom,
Thank you for both jumping in here. I have the board set up in the lab, and I'm still getting no response from the Gluon Config program. The baud rate, parity, and connections all seem to be good. I have a separate bench supply powering the Gluon board, and the RS232 has a common ground.
In realterm, I see the text of the Gluon boot and start dumping data out just fine. Then I close the port, open it in Gluon Config and connect, and nothing (yes, I have the hide parsed messages unchecked). Nothing, no response at all. Close the port on GluonConfig and open it in RealTerm and there is the data.
I'm running XP on a Dell Laptop that has its own serial port, and it seems to work fine. I've checked it several times and can read and write to it on other serial adapters (same thing happens when I use a USB adapter).
Any ideas?
Thanks, G.
PS: Yes, I am that Prof. Elkaim. We've developed a larger, more capable autopilot board (see
http://slugsuav.soe.ucsc.edu/ ) that uses the same processor and is programmed directly from MATLAB. I'm very interested in seeing if we can move most of that code onto the Gluon as a "smaller and simpler" version of what we do.
PPS: I'm very happy to help you with the algorithms using the two-vector estimation. Really, though, you want to keep track of the whole DCM or quaternion. I've got some really good algorithms for calibrating the mags and accels, and if you have a rate table and a lot of patience, the gyros.