moparisthebest
/
USBHost_t36
mirror of https://github.com/gdsports/USBHost_t36
1
0
Fork 0
Code Issues Releases Wiki Activity
USBHost_t36/keywords.txt

108 lines
2.2 KiB
Plaintext
Raw Permalink Normal View History

Update keywords
2017-10-21 14:40:59 -04:00
# Objects
Convert to Arduino library format
2017-03-07 10:40:06 -05:00
USBHost KEYWORD1
USBHub KEYWORD1
Update keywords
2017-10-21 14:40:59 -04:00
USBHIDParser KEYWORD1
Convert to Arduino library format
2017-03-07 10:40:06 -05:00
KeyboardController KEYWORD1
Add Mouse driver from wwatson https://forum.pjrc.com/threads/45740-USB-Host-Mouse-Driver
2017-08-24 16:41:39 -04:00
MouseController KEYWORD1
Convert to Arduino library format
2017-03-07 10:40:06 -05:00
MIDIDevice KEYWORD1
Update keywords
2017-10-21 14:40:59 -04:00
USBSerial KEYWORD1
AntPlus KEYWORD1
JoystickController KEYWORD1
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.
2017-11-14 11:42:28 -05:00
RawHIDController KEYWORD1
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.
2018-01-20 19:38:42 -05:00
BluetoothController KEYWORD1
Update keywords
2017-10-21 14:40:59 -04:00
# Common Functions
Convert to Arduino library format
2017-03-07 10:40:06 -05:00
Task KEYWORD2
Update keywords
2017-10-21 14:40:59 -04:00
idVendor KEYWORD2
idProduct KEYWORD2
manufacturer KEYWORD2
product KEYWORD2
serialNumber KEYWORD2
# KeyboardController
Convert to Arduino library format
2017-03-07 10:40:06 -05:00
getKey KEYWORD2
getModifiers KEYWORD2
getOemKey KEYWORD2
attachPress KEYWORD2
attachRelease KEYWORD2
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
2017-11-20 12:19:25 -05:00
attachExtrasPress KEYWORD2
attachExtrasRelease KEYWORD2
Update keywords
2017-10-21 14:40:59 -04:00
LEDS KEYWORD2
updateLEDS KEYWORD2
numLock KEYWORD2
capsLock KEYWORD2
Update Keywords
2017-11-04 23:35:52 -04:00
scrollLock KEYWORD2
Update keywords
2017-10-21 14:40:59 -04:00
# MIDIDevice
getType KEYWORD2
getChannel KEYWORD2
getData1 KEYWORD2
getData2 KEYWORD2
setHandleNoteOff KEYWORD2
setHandleNoteOn KEYWORD2
setHandleVelocityChange KEYWORD2
setHandleControlChange KEYWORD2
setHandleProgramChange KEYWORD2
setHandleAfterTouch KEYWORD2
setHandlePitchChange KEYWORD2
setHandleSysEx KEYWORD2
setHandleRealTimeSystem KEYWORD2
setHandleTimeCodeQuarterFrame KEYWORD2
sendNoteOff KEYWORD2
sendNoteOn KEYWORD2
sendPolyPressure KEYWORD2
sendControlChange KEYWORD2
sendProgramChange KEYWORD2
sendAfterTouch KEYWORD2
sendPitchBend KEYWORD2
sendSysEx KEYWORD2
sendRealTime KEYWORD2
sendTimeCodeQuarterFrame KEYWORD2
sendTimeCodeQuarterFrame KEYWORD2
SYSEX_MAX_LEN LITERAL1 KEYWORD2
# AntPlus
onStatusChange KEYWORD2
onDeviceID KEYWORD2
onHeartRateMonitor KEYWORD2
onSpeedCadence KEYWORD2
onSpeed KEYWORD2
onCadence KEYWORD2
setWheelCircumference KEYWORD2
# MouseController
mouseDataClear KEYWORD2
Add Mouse driver from wwatson https://forum.pjrc.com/threads/45740-USB-Host-Mouse-Driver
2017-08-24 16:41:39 -04:00
getButtons KEYWORD2
getMouseX KEYWORD2
getMouseY KEYWORD2
Update keywords
2017-10-21 14:40:59 -04:00
getWheel KEYWORD2
getWheelH KEYWORD2
# JoystickController
joystickDataClear KEYWORD2
getAxis KEYWORD2
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
2017-11-20 12:19:25 -05:00
axisMask KEYWORD2
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.
2018-01-11 10:09:22 -05:00
axisChangedMask KEYWORD2
axisChangeNotifyMask KEYWORD2
userAxisMask KEYWORD2
setRumbleOn KEYWORD2
setLEDs KEYWORD2
joystickType KEYWORD2
PS3 LITERAL1
PS4 LITERAL1
XBOXONE LITERAL1
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.
2018-01-20 19:38:42 -05:00
XBOX360 LITERAL1
Add support for Xbox 360 USB controller
2018-11-03 21:58:33 -04:00
XBOX360USB LITERAL1
Update keywords
2017-10-21 14:40:59 -04:00
Update Keywords
2017-11-04 23:35:52 -04:00
# USBSerial
USBHOST_SERIAL_7E1 LITERAL1
USBHOST_SERIAL_7O1 LITERAL1
USBHOST_SERIAL_8N1 LITERAL1
USBHOST_SERIAL_8N2 LITERAL1
USBHOST_SERIAL_8E1 LITERAL1
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.
2017-11-05 13:53:54 -05:00
USBHOST_SERIAL_8O1 LITERAL1
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.
2017-11-14 11:42:28 -05:00
# RAWHid
usage KEYWORD2
attachReceive KEYWORD2
sendPacket KEYWORD2