選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。

keywords.txt 2.3KB

USBSerial_BigBuffer - T4.x (multi devices) This delta originated to do the work similar to what was done for the MIDI code base and support two versions of the object. All of the code was renamed to a new base class USBSerialBase which has everything, except the main buffer. Two sub-classes were made that the only difference is the size of the buffer to hold all of the USB RX and TX information. This started off to try to support an FT2232H device which transers 512 bytes at a time instead of what most of our devices were transfering which is 64 bytes. While doing this, I found that we have a similar issue with the T4.x boards which now transfer 512 bytes as well and our Serial object would not handle it. So there are two sublasses: ``` USBSerial - for those up to 64 byte transfers USBSerial_BigBuffer - for up to 512 bytes ``` Note: by default the biguffer version will only handle those devices > 64 bytes, but you can pass in an optional parameter of the minimum size, so doing something like: ``` USBSerial_BigBuffer userial(myusb, 1); ``` Will handle all up to 512. Also the FTDI2232H supports two USB to Serial objects, and our code was setup that in most cases including when we put in VID:PID pair in our table, the code would claim would claim the object at device level so only one USB Serial adapter. So changed table to support saying for this VID:PID claim at interface level. It now works, but not sure for the device I have as it is a USB to Serial and JTAG and not sure how to test 2nd one. But while doing this created a test sketch for Multiple Host USB Serial objects and the two are claimed by this. I also created a new version of the Teensy USBToSerial example sketch that if you configure USB type to Dual Serial or Triple Serial will output SerialUSB1 to Serial2 and SerialUSB2 to Serial3, which works, and then tried T4 configured for Dual plugged into T4.1 with above sketch and could talk to both USB Serial adapters. The Claim code was rearranged a lot, so hopefully did not break anything. But tested with T4 as mentioned, both Single and Dual Serial T3.2 with Single Serial, plus: Serial, Joystick, Keyboard... FTDI - USB to Serial adapter (Sparkfun) CP2104 - Adafruit PL2303 - some clones ... So hopefully most things are still working
4年前
USBSerial_BigBuffer - T4.x (multi devices) This delta originated to do the work similar to what was done for the MIDI code base and support two versions of the object. All of the code was renamed to a new base class USBSerialBase which has everything, except the main buffer. Two sub-classes were made that the only difference is the size of the buffer to hold all of the USB RX and TX information. This started off to try to support an FT2232H device which transers 512 bytes at a time instead of what most of our devices were transfering which is 64 bytes. While doing this, I found that we have a similar issue with the T4.x boards which now transfer 512 bytes as well and our Serial object would not handle it. So there are two sublasses: ``` USBSerial - for those up to 64 byte transfers USBSerial_BigBuffer - for up to 512 bytes ``` Note: by default the biguffer version will only handle those devices > 64 bytes, but you can pass in an optional parameter of the minimum size, so doing something like: ``` USBSerial_BigBuffer userial(myusb, 1); ``` Will handle all up to 512. Also the FTDI2232H supports two USB to Serial objects, and our code was setup that in most cases including when we put in VID:PID pair in our table, the code would claim would claim the object at device level so only one USB Serial adapter. So changed table to support saying for this VID:PID claim at interface level. It now works, but not sure for the device I have as it is a USB to Serial and JTAG and not sure how to test 2nd one. But while doing this created a test sketch for Multiple Host USB Serial objects and the two are claimed by this. I also created a new version of the Teensy USBToSerial example sketch that if you configure USB type to Dual Serial or Triple Serial will output SerialUSB1 to Serial2 and SerialUSB2 to Serial3, which works, and then tried T4 configured for Dual plugged into T4.1 with above sketch and could talk to both USB Serial adapters. The Claim code was rearranged a lot, so hopefully did not break anything. But tested with T4 as mentioned, both Single and Dual Serial T3.2 with Single Serial, plus: Serial, Joystick, Keyboard... FTDI - USB to Serial adapter (Sparkfun) CP2104 - Adafruit PL2303 - some clones ... So hopefully most things are still working
4年前
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113
  1. # Objects
  2. USBHost KEYWORD1
  3. USBHub KEYWORD1
  4. USBHIDParser KEYWORD1
  5. KeyboardController KEYWORD1
  6. MouseController KEYWORD1
  7. DigitizerController KEYWORD1
  8. MIDIDevice KEYWORD1
  9. MIDIDevice_BigBuffer KEYWORD1
  10. USBSerial KEYWORD1
  11. USBSerial_BigBuffer KEYWORD1
  12. USBSerialEmu KEYWORD1
  13. USBSerialBase KEYWORD1
  14. AntPlus KEYWORD1
  15. JoystickController KEYWORD1
  16. RawHIDController KEYWORD1
  17. BluetoothController KEYWORD1
  18. # Common Functions
  19. Task KEYWORD2
  20. idVendor KEYWORD2
  21. idProduct KEYWORD2
  22. manufacturer KEYWORD2
  23. product KEYWORD2
  24. serialNumber KEYWORD2
  25. # KeyboardController
  26. getKey KEYWORD2
  27. getModifiers KEYWORD2
  28. getOemKey KEYWORD2
  29. attachPress KEYWORD2
  30. attachRelease KEYWORD2
  31. attachExtrasPress KEYWORD2
  32. attachExtrasRelease KEYWORD2
  33. LEDS KEYWORD2
  34. updateLEDS KEYWORD2
  35. numLock KEYWORD2
  36. capsLock KEYWORD2
  37. scrollLock KEYWORD2
  38. forceBootProtocol KEYWORD2
  39. # MIDIDevice
  40. getType KEYWORD2
  41. getChannel KEYWORD2
  42. getData1 KEYWORD2
  43. getData2 KEYWORD2
  44. setHandleNoteOff KEYWORD2
  45. setHandleNoteOn KEYWORD2
  46. setHandleVelocityChange KEYWORD2
  47. setHandleControlChange KEYWORD2
  48. setHandleProgramChange KEYWORD2
  49. setHandleAfterTouch KEYWORD2
  50. setHandlePitchChange KEYWORD2
  51. setHandleSysEx KEYWORD2
  52. setHandleRealTimeSystem KEYWORD2
  53. setHandleTimeCodeQuarterFrame KEYWORD2
  54. sendNoteOff KEYWORD2
  55. sendNoteOn KEYWORD2
  56. sendPolyPressure KEYWORD2
  57. sendControlChange KEYWORD2
  58. sendProgramChange KEYWORD2
  59. sendAfterTouch KEYWORD2
  60. sendPitchBend KEYWORD2
  61. sendSysEx KEYWORD2
  62. sendRealTime KEYWORD2
  63. sendTimeCodeQuarterFrame KEYWORD2
  64. sendTimeCodeQuarterFrame KEYWORD2
  65. SYSEX_MAX_LEN LITERAL1 KEYWORD2
  66. # AntPlus
  67. onStatusChange KEYWORD2
  68. onDeviceID KEYWORD2
  69. onHeartRateMonitor KEYWORD2
  70. onSpeedCadence KEYWORD2
  71. onSpeed KEYWORD2
  72. onCadence KEYWORD2
  73. setWheelCircumference KEYWORD2
  74. # MouseController
  75. mouseDataClear KEYWORD2
  76. getButtons KEYWORD2
  77. getMouseX KEYWORD2
  78. getMouseY KEYWORD2
  79. getWheel KEYWORD2
  80. getWheelH KEYWORD2
  81. # JoystickController
  82. joystickDataClear KEYWORD2
  83. getAxis KEYWORD2
  84. axisMask KEYWORD2
  85. axisChangedMask KEYWORD2
  86. axisChangeNotifyMask KEYWORD2
  87. userAxisMask KEYWORD2
  88. setRumbleOn KEYWORD2
  89. setLEDs KEYWORD2
  90. joystickType KEYWORD2
  91. PS3 LITERAL1
  92. PS3_MOTION LITERAL1
  93. PS4 LITERAL1
  94. XBOXONE LITERAL1
  95. XBOX360 LITERAL1
  96. SWITCH LITERAL1
  97. # USBSerial
  98. USBHOST_SERIAL_7E1 LITERAL1
  99. USBHOST_SERIAL_7O1 LITERAL1
  100. USBHOST_SERIAL_8N1 LITERAL1
  101. USBHOST_SERIAL_8N2 LITERAL1
  102. USBHOST_SERIAL_8E1 LITERAL1
  103. USBHOST_SERIAL_8O1 LITERAL1
  104. # RAWHid
  105. usage KEYWORD2
  106. attachReceive KEYWORD2
  107. sendPacket KEYWORD2