Force feedback bitmap command sends extra bytes

RMP 210, 220, 440LE, 440SE, 440 Omni
Post Reply
twlbean
Posts: 5
Joined: Thu Apr 19, 2012 12:53 pm

Force feedback bitmap command sends extra bytes

Post by twlbean »

I am using the USB interface, and sending the force feedback bitmap command. The problem I am seeing is that the response is 76 bytes. Per the documentation, I expect to get 74 bytes - (18 bits * 4 bytes) + CRC.

If I simply skip the first 2 bytes (0x41, 0x00) of the response, things appear to work.

Per the documentation of the force feedback bitmap command:

Code: Select all

UFDB1 - 0x00000000
UFDB2 - 0xFC000000
UFDB3 - 0x00000FFF
Any ideas what might be happening?

phussey
Posts: 79
Joined: Fri Apr 20, 2012 8:12 am

Re: Force feedback bitmap command sends extra bytes

Post by phussey »

Although the CRC is only 16-bits, the CCU ships all values using 32-bit values including the CRC.

The additional 2 bytes are null bytes in the CRC value (16-bit value shipped as a 32).
PATRICK HUSSEY
Principal Engineer

STANLEY INNOVATION, INC
www.stanleyinnovation.com

twlbean
Posts: 5
Joined: Thu Apr 19, 2012 12:53 pm

Re: Force feedback bitmap command sends extra bytes

Post by twlbean »

RMP Wizard wrote:Although the CRC is only 16-bits, the CCU ships all values using 32-bit values including the CRC.

The additional 2 bytes are null bytes in the CRC value (16-bit value shipped as a 32).
Thanks - that solved my problem. I also discovered that the 2 null bytes in the CRC value must also be included in the buffer passed to the CRC checksum routine otherwise the checksum will fail.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests