Author Topic: Starting on Force Feed Back using PID  (Read 14285 times)

gbr

  • Member
  • ***
  • Posts: 23
Starting on Force Feed Back using PID
« on: November 02, 2010, 05:02:47 am »
Long time away
Having started on Force Feed BacK now,I set up the PID longish part of it(total lenght over 0x500 bytes)
Chip Microchip 18F2550

After correctly reaching and reading the HIDreportDescriptor my   HHDsoftware USB tool gives me a message of aborting and disconecting without reporting any error status just a blank page lenght before the disconnection messages

If I remove the PID part (and the report ID 1 from tje joystick) the program works properly
my program has been checked and rechecked for possible fault ...
I must have missed something ....

Any clues ?
Or other chaps suffering through PID(Physical Interface Device).it's got a whole Pdf for itself

Jan Axelson

  • Administrator
  • Frequent Contributor
  • *****
  • Posts: 3033
    • Lakeview Research
Re: Starting on Force Feed Back using PID
« Reply #1 on: November 02, 2010, 11:38:31 am »
There is discussion about this on the Microchip forum, but it looks like you've been there.

Jan

gbr

  • Member
  • ***
  • Posts: 23
Re: Starting on Force Feed Back using PID
« Reply #2 on: November 02, 2010, 01:23:10 pm »
Thanks Jan ,I have studied and taken all I could from there...
I have sent a log file of the plug in process to the designers of the program ,I may get some luck there.
It seems to interest them that the error status is missing.
I usually get an error number when something is wrong.
I'll let you know of the outcome.
Would you find anything else please let me know.

Jan Axelson

  • Administrator
  • Frequent Contributor
  • *****
  • Posts: 3033
    • Lakeview Research
Re: Starting on Force Feed Back using PID
« Reply #3 on: November 02, 2010, 05:57:30 pm »
Hope you get it sorted out.

Jan

gbr

  • Member
  • ***
  • Posts: 23
Re: Starting on Force Feed Back using PID
« Reply #4 on: November 03, 2010, 06:47:00 am »
I did find some errors in the descriptor
That sorted out the problem
Busy now with the real nittygritty

Best regards
gb