visus
/
teensy-usbhost
Bevaka 1
Stjärnmärk 0
Förgrening 0
Kod Ärenden 0 Pull-förfrågningar 0 Släpp 0 Wiki Aktiviteter
Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.
288 Incheckningar
1 Gren
Träd: ab5e043a3a
Grenar Taggar
${ item.name }
Skapa branchen ${ searchTerm }
från 'ab5e043a3a'
${ noResults }
teensy-usbhost/keywords.txt

keywords.txt 2.3KB
Rå Normal View Historik

Update keywords
7 år sedan
Convert to Arduino library format
7 år sedan
​
Update keywords
7 år sedan
Convert to Arduino library format
7 år sedan
Add Mouse driver from wwatson https://forum.pjrc.com/threads/45740-USB-Host-Mouse-Driver
7 år sedan
WIP Digitizer Thanks mostly to Mike (@mjs513) - a WIP to support some of the digitizer tablets that are not properly supported by Mouse. Like Wacom Intous...
5 år sedan
Convert to Arduino library format
7 år sedan
Add MIDIDevice_BigBuffer, for high speed MIDI devices
5 år sedan
Update keywords
7 år sedan
​
​
RAWHID Support Needed HID Parser to support Bidirectional Transfers The HidParser code was setup such that the claim for a report, the caller could say I want to claim the whole thinig and allowed callback functions for processing of in buffer and out buffer. Allow RawHID to contribute Transfer_t Since RawHID may need more resources than most, maybe it should contribute the additional structures The constructor for a RAWHID object allows you to specify the top usage that it wishes to connect to. I used this for example to be able to connect to a Teensy with the RAWHID associated with emulating the Serial object. If a HID Input class says that it wants to claim the whole interface, I reuse the buffer associated with holding the HID descriptor and use it for output buffers.
7 år sedan
XBox360 Wireless controller Support for using the Microsoft XBox 360 wireless receiver for windows to be able to communicate with XBox 360 wireless controllers. In theory this should support up to 4 controllers. So far I have only tested with one as I only have one. Added a joystick only test that should support up to 4 joystick objects.
6 år sedan
Update keywords
7 år sedan
Convert to Arduino library format
7 år sedan
Update keywords
7 år sedan
​
​
​
​
​
​
Convert to Arduino library format
7 år sedan
​
​
​
​
Add Xbox One controller support While the other Joystick objects currently supported by the USB Host code are driven by HID data, the Xbox does not contain HID data and instead works at the top level. To handle this I made the Joystick object use multiple InHeritence like: class JoystickController : public USBDriver, public USBHIDInput This allowed me to have the object work either way. This did add some complexity in that some of the methods like is the object connected (The bool operator) had to be overwritten as both of the bases classes had it. In addition needed to update the other query functions to be able to grab the data from mydevice or device depending on which type of controller was connected. Since this looked like a valid way, I then merged the Keyboard Extras code that Keyboard and made it also do a similar multiple inheritance. In this case however I restricted the HID top level report handle code to only accept it if on the same object that claimed the keyboard. The mouse test app was updated as well
7 år sedan
​
Update keywords
7 år sedan
​
​
​
Update Keywords
7 år sedan
Now only optionally force keyboard into boot protocol mode The first gigabyte fix, was to always force the keyboard into boot protocol mode, which appeared to work well for all of the keyboards I tried. Unforationally it caused issues with some wireless keyboard/mouse combo packages, including some logitech and some microsoft keyboards. This version instead, I created a list (currently only one vendor id), of vendor id:product id, that need to be forced into boot mode. Knowing that if there is one keyboard vendor with this N key rollover feature, there are probably others. So while this list can be expanded, this requires users to update library. So added a method forceBootProtocol method to keyboard class that allows the user to try it out without needing to update the library sources. The mouse test program has example of either setting it before the keyboard is initiated, as well as another way that when a connection is found it asks for the vendor id, and if it is the one of my gigabyte keyboard, it calls the function then. While doing this I found some of the query functions like idVendor on the keyboard class would not compile as the keyboard object has multiple inheritence and both base classes have this. So like the joystick objects I added these to the top level function and these functions will direct the calls to the approrpriate places.
5 år sedan
Update keywords
7 år sedan
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Add Mouse driver from wwatson https://forum.pjrc.com/threads/45740-USB-Host-Mouse-Driver
7 år sedan
​
​
Update keywords
7 år sedan
​
​
​
​
​
Add Xbox One controller support While the other Joystick objects currently supported by the USB Host code are driven by HID data, the Xbox does not contain HID data and instead works at the top level. To handle this I made the Joystick object use multiple InHeritence like: class JoystickController : public USBDriver, public USBHIDInput This allowed me to have the object work either way. This did add some complexity in that some of the methods like is the object connected (The bool operator) had to be overwritten as both of the bases classes had it. In addition needed to update the other query functions to be able to grab the data from mydevice or device depending on which type of controller was connected. Since this looked like a valid way, I then merged the Keyboard Extras code that Keyboard and made it also do a similar multiple inheritance. In this case however I restricted the HID top level report handle code to only accept it if on the same object that claimed the keyboard. The mouse test app was updated as well
7 år sedan
Joystick - USB enhance More Axis, Rumble, LEDS Added support for Joysticks, that on some of them we can not receive more of the Joysticks axis. So far mainly on PS3 and PS4. So you can now get the Gyro/accel stuff. You get feedback on the DS4 touch area, PS3 you can get the pressure values on several of the buttons. LIke the RT/LT ones. In addition added some support for Rumble. So far it appears to be working somewhat on the PS3 and PS4 controllers. On the PS4 you can also set the RGB LED light values and on the PS3 you can set the 4 LEDS on the front., which are normally used to say which controller it is.
6 år sedan
​
​
​
​
​
​
PS3 Move Motion controller Turns out they are a lot different than other PS3 controllers. When plugged into USB, it appears like these units do not send any reports. They do allow us to do pairing (which is differnt) than other PS3, as well as set the Bulb LED color, which I now have it alternating colors every few seconds and also it tries to pair it with a BT dongle When connected to Bluetooth, it now is setup to generate reports, as well as again set the bulb color and rumble. So far it maps the 3 button bytes into the buttons field and then simply copies most all of the data down into Axis, starting where the Trigger button is. JoystickBT.ino was updated, to know about this controller and as mentioned above in the USB case it tries to pair and plays with the color of bulb. In the BT case it tries to display data. I did a quick and dirty change of the Accel/Gyro like stuff which is probably totally wrong. Pressing some of the buttons will set bulb color and pressing trigger will set rumble. PS3 Motion controller - very little mapping of axis
5 år sedan
Joystick - USB enhance More Axis, Rumble, LEDS Added support for Joysticks, that on some of them we can not receive more of the Joysticks axis. So far mainly on PS3 and PS4. So you can now get the Gyro/accel stuff. You get feedback on the DS4 touch area, PS3 you can get the pressure values on several of the buttons. LIke the RT/LT ones. In addition added some support for Rumble. So far it appears to be working somewhat on the PS3 and PS4 controllers. On the PS4 you can also set the RGB LED light values and on the PS3 you can set the 4 LEDS on the front., which are normally used to say which controller it is.
6 år sedan
​
XBox360 Wireless controller Support for using the Microsoft XBox 360 wireless receiver for windows to be able to communicate with XBox 360 wireless controllers. In theory this should support up to 4 controllers. So far I have only tested with one as I only have one. Added a joystick only test that should support up to 4 joystick objects.
6 år sedan
Beginning support USB for Nintendo Switch... It shows up with name XBox360 for Windows (at least the version I have)... But at least it is starting to give some data
4 år sedan
Update Keywords
7 år sedan
​
​
​
​
​
Test fixes for different parity and like I did a quick test using the Serial test app, where I can type in lines like: #38400,7E1 And it reopens the serial port at the specified baud and format. Note the formats the test app looks for is 7E1, 7O1, 8N1, 8N2. Tested on an FTDI, PL2303 and CH341. I also tested going to Teensy 3.2 CDCACM. But as far as I know the teensy could not care less about Baud/Format. Unless of course there is a way to query the value and use it to set a Hardware Serial port to it.
7 år sedan
RAWHID Support Needed HID Parser to support Bidirectional Transfers The HidParser code was setup such that the claim for a report, the caller could say I want to claim the whole thinig and allowed callback functions for processing of in buffer and out buffer. Allow RawHID to contribute Transfer_t Since RawHID may need more resources than most, maybe it should contribute the additional structures The constructor for a RAWHID object allows you to specify the top usage that it wishes to connect to. I used this for example to be able to connect to a Teensy with the RAWHID associated with emulating the Serial object. If a HID Input class says that it wants to claim the whole interface, I reuse the buffer associated with holding the HID descriptor and use it for output buffers.
7 år sedan
​
​
​
​
 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110 
  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. AntPlus	KEYWORD1

  12. JoystickController	KEYWORD1

  13. RawHIDController	KEYWORD1

  14. BluetoothController	KEYWORD1

  15. # Common Functions

  16. Task	KEYWORD2

  17. idVendor	KEYWORD2

  18. idProduct	KEYWORD2

  19. manufacturer	KEYWORD2

  20. product	KEYWORD2

  21. serialNumber	KEYWORD2

  22. 

  23. # KeyboardController

  24. getKey	KEYWORD2

  25. getModifiers	KEYWORD2

  26. getOemKey	KEYWORD2

  27. attachPress	KEYWORD2

  28. attachRelease	KEYWORD2

  29. attachExtrasPress	KEYWORD2

  30. attachExtrasRelease	KEYWORD2

  31. LEDS	KEYWORD2

  32. updateLEDS	KEYWORD2

  33. numLock	KEYWORD2

  34. capsLock	KEYWORD2

  35. scrollLock	KEYWORD2

  36. forceBootProtocol	KEYWORD2

  37. 

  38. # MIDIDevice

  39. getType	KEYWORD2

  40. getChannel	KEYWORD2

  41. getData1	KEYWORD2

  42. getData2	KEYWORD2

  43. setHandleNoteOff	KEYWORD2

  44. setHandleNoteOn	KEYWORD2

  45. setHandleVelocityChange	KEYWORD2

  46. setHandleControlChange	KEYWORD2

  47. setHandleProgramChange	KEYWORD2

  48. setHandleAfterTouch	KEYWORD2

  49. setHandlePitchChange	KEYWORD2

  50. setHandleSysEx	KEYWORD2

  51. setHandleRealTimeSystem	KEYWORD2

  52. setHandleTimeCodeQuarterFrame	KEYWORD2

  53. sendNoteOff	KEYWORD2

  54. sendNoteOn	KEYWORD2

  55. sendPolyPressure	KEYWORD2

  56. sendControlChange	KEYWORD2

  57. sendProgramChange	KEYWORD2

  58. sendAfterTouch	KEYWORD2

  59. sendPitchBend	KEYWORD2

  60. sendSysEx	KEYWORD2

  61. sendRealTime	KEYWORD2

  62. sendTimeCodeQuarterFrame	KEYWORD2

  63. sendTimeCodeQuarterFrame	KEYWORD2

  64. SYSEX_MAX_LEN	LITERAL1	KEYWORD2

  65. 

  66. # AntPlus

  67. onStatusChange	KEYWORD2

  68. onDeviceID	KEYWORD2

  69. onHeartRateMonitor	KEYWORD2

  70. onSpeedCadence	KEYWORD2

  71. onSpeed	KEYWORD2

  72. onCadence	KEYWORD2

  73. setWheelCircumference	KEYWORD2

  74. 

  75. # MouseController

  76. mouseDataClear	KEYWORD2

  77. getButtons	KEYWORD2

  78. getMouseX	KEYWORD2

  79. getMouseY	KEYWORD2

  80. getWheel	KEYWORD2

  81. getWheelH	KEYWORD2

  82. 

  83. # JoystickController

  84. joystickDataClear	KEYWORD2

  85. getAxis	KEYWORD2

  86. axisMask	KEYWORD2

  87. axisChangedMask	KEYWORD2

  88. axisChangeNotifyMask	KEYWORD2

  89. userAxisMask	KEYWORD2

  90. setRumbleOn	KEYWORD2

  91. setLEDs	KEYWORD2

  92. joystickType	KEYWORD2

  93. PS3	LITERAL1

  94. PS3_MOTION	LITERAL1

  95. PS4	LITERAL1

  96. XBOXONE	LITERAL1

  97. XBOX360	LITERAL1

  98. SWITCH	LITERAL1

  99. # USBSerial

  100. USBHOST_SERIAL_7E1	LITERAL1

  101. USBHOST_SERIAL_7O1	LITERAL1

  102. USBHOST_SERIAL_8N1	LITERAL1

  103. USBHOST_SERIAL_8N2	LITERAL1

  104. USBHOST_SERIAL_8E1	LITERAL1

  105. USBHOST_SERIAL_8O1	LITERAL1

  106. 

  107. # RAWHid

  108. usage	KEYWORD2

  109. attachReceive	KEYWORD2

  110. sendPacket	KEYWORD2