FSRK-USB-2 not recognized as "new device" supporting DataModeControl V2

[Chris Tan]

In freespace_deviceTable.c, add the device as follows:

const struct FreespaceDeviceInfo freespace_newDeviceAPITable[] = {
 { "Smart USB RF Transceiver v2 (MKCV)", 0x1d5a, 0xc0b3, 2 },
 { "FSRK-USB-2", 0x1d5a, 0xc080, 2 }
};

[Merrill Roller (merrill-roller)]

Yep, good call. This affects the libfreespace-examples and any other file using the isNewDevice() message. The DataModeControlV2 message definitely works with the USB-2, but this issue makes it a pain to make backwards compatible software. Thanks for filing the bug.

[Chris Tan (chris-tan-y)]

Hi Merrill,

Once I fixed this, most of the examples worked fine with the FSRK-USB-2,
with the exception of communication_example. It kept throwing an error:
<timeout> Try moving the Loop/FRCM to wake it up.

Moving the USB-2 did nothing - but maybe USB-2 just doesn't report
battery level... No worries though, I'm not using that command anyway.

Thanks,
Chris

On 7/10/2012 5:03 PM, Merrill Roller wrote:
> Yep, good call. This affects the libfreespace-examples and any other
> file using the isNewDevice() message. The DataModeControlV2 message
> definitely works with the USB-2, but this issue makes it a pain to make
> backwards compatible software. Thanks for filing the bug.
>
> ** Changed in: libfreespace
> Assignee: (unassigned) => Merrill Roller (merrill-roller)
>
> ** Changed in: libfreespace
> Importance: Undecided => High
>
> ** Changed in: libfreespace
> Status: New => Confirmed
>