Objective Development Forums

Re: HID & Force Feedback

2012-12-11T19:45:30+02:00

for an example of the descriptor see Post #: 35 at this link http://www.microchip.com/forums/tm.aspx ... 25&mpage=2

Yes its big, yes I tried to chop it down, no it does no budge. You will need the latest version of v-usb as a patch had to be made to allow > 254 descriptor lengths.

Statistics: Posted by ulao — Tue Dec 11, 2012 7:45 pm

Re: HID & Force Feedback

2012-12-11T09:01:48+02:00

Hi,
Is someone can share the final descriptor or at least tell me if someone is interesting to reactive this project ?

Thanks

Statistics: Posted by FFB.BOY.30 — Tue Dec 11, 2012 9:01 am

Re: HID & Force Feedback

2010-06-10T15:06:27+02:00

Not at the moment (inthe middle of making a write up) , but would be more than willing to help you. Give me a shout on that other board as there is no PM here.

Statistics: Posted by ulao — Thu Jun 10, 2010 3:06 pm

Re: HID & Force Feedback

2010-06-09T19:31:47+02:00

Sorry, was abroad for some days and hadn't access to any internet Are you willing to post a full excerpt of everything belonging to the FB part? (descriptor & receive/send/setup functions)

Statistics: Posted by Guest — Wed Jun 09, 2010 7:31 pm

Re: HID & Force Feedback

2010-05-27T23:02:42+02:00

Ok learned bit here..

On start up we get c,4 stop all effects.

Once I run an effect I see that come in. For example I create a constant force and I see 1,1 see report below..

Code:

 0x09,0xAB,    //    Usage Undefined
   0xA1,0x02,    //    Collection Datalink
      0x85,0x01,    //    Report ID 1
      0x09,0x25,    //    Usage Effect Type
      0xA1,0x02,    //    Collection Datalink
      0x09,0x26,    //    Usage ET Constant Force
      0x09,0x27,    //    Usage ET Ramp
      0x09,0x30,    //    Usage ET Square
      0x09,0x31,    //    Usage ET Sine
      0x09,0x32,    //    Usage ET Triangle
      0x09,0x33,    //    Usage ET Sawtooth Up
      0x09,0x34,    //    Usage ET Sawtooth Down
      0x09,0x40,    //    Usage ET Spring
      0x09,0x41,    //    Usage ET Damper
      0x09,0x42,    //    Usage ET Inertia
      0x09,0x43,    //    Usage ET Friction
      0x09,0x28,    //    Usage ET Custom Force Data
      0x25,0x0C,    //    Logical Maximum Ch (12d)
      0x15,0x01,    //    Logical Minimum 1
      0x35,0x01,    //    Physical Minimum 1
      0x45,0x0C,    //    Physical Maximum Ch (12d)
      0x75,0x08,    //    Report Size 8
      0x95,0x01,    //    Report Count 1
      0xB1,0x00,    //    Feature
   0xC0     ,    // End Collection

FYI here is report C, as you can see 1 is stop all effects.

Code:

   0x09,0x96,    //    Usage DC Disable Actuators
   0xA1,0x02,    //    Collection Datalink
      0x85,0x0C,    //    Report ID Ch (12d)
      0x09,0x97,    //    Usage DC Stop All Effects
      0x09,0x98,    //    Usage DC Device Reset
      0x09,0x99,    //    Usage DC Device Pause
      0x09,0x9A,    //    Usage DC Device Continue
      0x09,0x9B,    //    Usage PID Device State
      0x09,0x9C,    //    Usage DS Actuators Enabled
      0x15,0x01,    //    Logical Minimum 1
      0x25,0x06,    //    Logical Maximum 6
      0x75,0x08,    //    Report Size 8
      0x95,0x01,    //    Report Count 1
      0x91,0x00,    //    Output
   0xC0     ,    //    End Collection

For reference here is the info on the report communication. ( around page 35 )
http://www.usb.org/developers/devclass_docs/pid1_01.pdf

see page 42

once the device receives this Set Report request and validates that it is capable of performing the
requested operation, the device allocates the memory for the requested effect. The size of the
allocated memory is decided by device

If I send this 02 01 02 FF FF, I get the output device is full and I should
If I send this 02 01 03 FF FF, I get the output error and I should
If I send this 02 01 01 FF FF, Fedit freezes..?

My guess is the memory ff,ff. I have no idea what I should put in there..

FYI:
02 is the report
01 is the effect index you get from the set 1,1 I talked about above.
01/02/03/ is the response error or success code.
the next two are allocated memory and I think its where I'm failing.

Quick update the reason for the freeze was my endpoint 3 was 64, I made it an 8, SHE IS ALIVE!!! I friggen did it, rumble works tested and working in project 64 as well

:: As it seems the person of interested has dropped off the topic here, so I'm done reporting status unless otherwise asked.

Statistics: Posted by ulao — Thu May 27, 2010 11:02 pm

Re: HID & Force Feedback

2010-05-25T19:51:42+02:00

Yes I have a FFB device with no reg settings. I can receive a FFB command, but I'm not using it right so any thing coming in triggers my motor. I had to use the descriptor from that other forum. I just added a few buttons and analogs. Not sure why my descriptor is not right.

Its by no means perfect but it does work. Going to try to clean it up a bit, but I'd sure wish I could get some V-usb help on the data coming in .

Statistics: Posted by ulao — Tue May 25, 2010 7:51 pm

Re: HID & Force Feedback

2010-05-25T10:10:45+02:00

Hadn't had the time to test anything.

What is your latest descriptor/code? Does it now get recognized as a FF device without manually installing a driver/changing reg keys?

@Rumbles only once: FF only sends the start of the effect and the duration - You'll probably have to count that time manually if you aren't already.

Statistics: Posted by Guest — Tue May 25, 2010 10:10 am

Re: HID & Force Feedback

2010-05-25T01:08:25+02:00

I will have a look and report back, I bet you I did miss that, cant wait to try it .
------------------
ok
--

I was in fact missing it but Here is what I have so far.

Code:

unsigned  usbFunctionSetup(uchar data[8])
{

   usbRequest_t    *rq = (void *)data;
    usbMsgPtr = reportBuffer;
   if((rq->bmRequestType & USBRQ_TYPE_MASK) == USBRQ_TYPE_CLASS)
   {    /* class request type */
      if(rq->bRequest == USBRQ_HID_GET_REPORT)
      {  /* wValue: ReportType (highbyte), ReportID (lowbyte) */
         /* we only have one report type, so don't look at wValue */
blinkLed(1);
         return 8;
      }
   }
   else if(rq->bRequest == USBRQ_HID_GET_IDLE)
   {blinkLed(2);
         usbMsgPtr = &idleRate;
         return 1;
    }
   
   else if(rq->bRequest == USBRQ_HID_SET_IDLE)
   
   {blinkLed(3);
         idleRate = rq->wValue.bytes[1];
    }
    
   else if (rq->bRequest == USBRQ_HID_SET_REPORT)
    
   {blinkLed(4);
         _awaitReport = 1;
         return USB_NO_MSG;
    }
    
   else
    {
    /* no vendor specific requests implemented */
    }

    return 0;
}

I get my one blink when the Fedit is ran, device is selected, and when the effect is played but I never get blinks 2,3,4.

----
ok I can make the rumble work by doing this

Code:

   if((rq->bmRequestType & USBRQ_TYPE_MASK) == USBRQ_TYPE_CLASS)
   {    /* class request type */

      if(rq->bRequest == USBRQ_HID_GET_REPORT)
      {  /* wValue: ReportType (highbyte), ReportID (lowbyte) */
         return USB_NO_MSG;
      }

but I know this is not the way to do it.Easty if you have a though let me know, have you been able to get as far as me?

Statistics: Posted by ulao — Tue May 25, 2010 1:08 am

Re: HID & Force Feedback

2010-05-24T20:09:59+02:00

and you haven't forgotten to enable the FN_WRITE define, have you?

"Reading" something is the rather easy part

some excerpts using (nearly) latest V-USB:

Code:

static uchar    idleRate;           /* in 4 ms units */
char _awaitReport;

uchar   usbFunctionSetup(uchar data[8])
{
   usbRequest_t    *rq = (void *)data;
   usbMsgPtr = reportBuffer;
   if((rq->bmRequestType & USBRQ_TYPE_MASK) == USBRQ_TYPE_CLASS){    /* class request type */
      if(rq->bRequest == USBRQ_HID_GET_REPORT){  /* wValue: ReportType (highbyte), ReportID (lowbyte) */
         /* we only have one report type, so don't look at wValue */
         curGamepad->buildReport(reportBuffer);
         return curGamepad->report_size;
      }else if(rq->bRequest == USBRQ_HID_GET_IDLE){
         usbMsgPtr = &idleRate;
         return 1;
      }else if(rq->bRequest == USBRQ_HID_SET_IDLE){
         idleRate = rq->wValue.bytes[1];
      }else if (rq->bRequest == USBRQ_HID_SET_REPORT)
      {
         _awaitReport = 1;
         return USB_NO_MSG;
      }
   }else{
   /* no vendor specific requests implemented */
   }
   return 0;
}



uchar   usbFunctionWrite(uchar *data, uchar len)
{
   if (!_awaitReport || len < 1)
      return 1;
   curGamepad->rumble(data[len-1]);
   _awaitReport = 0;
    return 1;
}

#define USB_CFG_IMPLEMENT_FN_WRITE      1
/* Set this to 1 if you want usbFunctionWrite() to be called for control-out
 * transfers. Set it to 0 if you don't need it and want to save a couple of
 * bytes.
 */

(doesn't distinguish between different report ids & types)

Statistics: Posted by Guest — Mon May 24, 2010 8:09 pm

Re: HID & Force Feedback

2010-05-24T14:26:18+02:00

Hey sounds great, I made some good progress this weekend. I'm now back to the fact the V-usb receive data seems to be the hold up.

Statistics: Posted by ulao — Mon May 24, 2010 2:26 pm