MCP2200的HID出现参数不正确

但是，您是否将第一字节设置为“设备ID”？（通常为1或2）



以下为原文

But did you set the 1st Byte to the "Report ID" as your device expects? (usually 1 or 2)

是的，我做到了。我尝试发送17字节报告＝{0x80+ 16字节0x00 }。（在MC2200 HID接口命令描述中没有ID＝1或2的报告）



以下为原文


Yes, I did. I tried to sent 17 bytes report = {0x80 + 16 bytes of 0x00} for example.
(There are no reports with ID=1 or 2 in MCP2200 HID Interface Command Description)

如文档（http://WW1.Microchip .com／下载/ En/DeViceOC/93066 A.pdf）中所描述的：“从/MC2200生成读/写数据的16字节长HID报告”



以下为原文



As described in document ( http://ww1.microchip.com/downloads/en/DeviceDoc/93066A.pdf):
"16 bytes long HID reports generated to read/write

data from/to MCP2200"

然后你需要发送17字节。如果你得到“参数错误”，那么字节的数量与HID描述符（+1）的输出报告大小不匹配，或者发送的第一个字节不是有效的报告ID（或者如果只有一个报告ID）为零。引用的DOC没有说明它是什么样的报告。我假设SeaRealEng/Outlook报表，虽然这些特征报告的可能性很小，在这种情况下，您应该使用HIDStaseTuffE（）和HIDGETFraseUp（）。



以下为原文




Then you need to send 17 bytes. If you get "parameter error" then either the number of bytes doesn't match the output report size from the HID descriptor (+1), or the first byte of what you send is not the valid report id (or zero if there's only one report Id).

The doc you quoted doesn't say what kind of report it is. I would assume that these are input/output reports, although there's a small chance that these are feature reports, in which case you should use HIDSetFeature() and HIDGetFeature().

顺便说一下，在第一个代码中，你在“WDATA”中准备数据，然后将“DAT”传递给WreWr.Fo（）。



以下为原文

BTW: In your first code snipped you prepare data in "wdata", but then pass "dat" to WriteFile().

我用很少的组合发送了17个字节，但仍然没有找到正确的字节。不幸的是，我现在无法访问芯片。我将在星期一尝试使用HyStValk和HiDigFoice。谢谢你的帮助，祝你周末愉快！



以下为原文



I sent 17 bytes in few combinations, still not found right one.



Unfortunatelly I have no access to chip right now. I will try to use HIDSetFeature and HIDGetFeature on Monday.
Thanks for your help and have a nice weekends!

嗯，根据THISTHP://WW.Microchip .com／下载/ En/DeViceOC/93066 A。PDF没有“报告ID”。谁知道…



以下为原文

Well, according to this
http://ww1.microchip.com/downloads/en/DeviceDoc/93066A.pdf
there's no "report ID" byte.
who knows...