At 09:28 AM 7/22/2008, Neal Campbell wrote: >Sorry to have mis-represented this. I guess we just need to write >routines that can use these functions to talk to our products! > >Neal > >On Tue, Jul 22, 2008 at 12:26 PM, Eric Wachsmann <[EMAIL PROTECTED]> wrote: > > There are tested functions defined to talk to the FlexWire > interface. These > > functions do indeed talk through the firewire midi port (same as all other > > control messages). See ...Source\Console\FWC\fwc.cs for the details. > > > >
Well... adding functionality to PowerSDR is non-trivial. The process is straightforward, but decidedly non-trivial: One has to scrounge up Visual Studio 2003, then figure out how and where to add the functions you'd want (User interface wise). After that, it's pretty easy to figure out how to call Eric's control functions. (this is assuming you have a piece of gear that is I2C controlled, and you know how to command it already. here's the functions: I2C_WriteValue(ushort addr, byte val) I2C_Write2Value(ushort addr, byte v1, byte v2) I2C_ReadValue(ushort addr, out uint val) If you want to do it with MIDI messages, it's a bit more complex.. (because they're sent back and forth as SysEx messages).. Something along the lines of F0, 00, 00, 41, 2byte msg id, 2 byte protocol id (unused), 4byte opcode, 4 byte data, 4 byte data, F7 I think you need to turn the short ints into hex (I can't remember if MIDI allows high bit set in the middle of a SysEx.. probably not) opcode is found in a big ENUM, and might be 1019, 1020, 1021, for the three functions above. Jim _______________________________________________ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
