I'm not shure if the current configurable serial interface is capable to do bit-mangling and I'm quite confident that it lacks support for checksumming. But this may come in the future,
Thanks actually that looks pretty good, and is really close to the register then data format that I normally use on my microcontroller comms. Only with a channel number and parity, really could just have a block number and send 4 or 8 channels at once then parity. With just parity it may get the occasional false positive to start, but once some controls are moved and it falls through to the correct spot it should stay locked on since always getting right parity. Not much need for NEMA for a direct controller so 8 bit values shouldn't be a problem either.
With blocks of channels it would also be easy to prioritize the refresh rate, send the first block most of the time for the main controls and only send the buttons and switches a few times a second.
Should work fairly well.
I may have to even look at the PC side myself shortly. I've got the hardware mostly done, but am leaning away from having the yoke use the system mouse. Still want to use an optical mouse for yoke control pickup, just want it on a seperate controller so it doesn't interfere with the system mouse and normal button pushing and view selection. Then edit the system mouse so it never goes into the control mode and things should be pretty nice.
Alan
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
