Search results

Dewey, Thanks for the info. The V-USB example code that I am working from uses a Report Size of 128. Since I originally wrote the code for the Teensy I only need 64 anyway. At this point I am assuming that I need this CRC checking on the hardware firmware side. The V-USB guys indicate that...

Paul, I wish I could use the Teensy as I already have it working without this issue. My problem is the price point. I was hoping to make the whole thing for under $10. So far my design, testing and development seem to be headed in that direction. Not factoring in hand assembly, I'm...

I am leaning toward the fact that the V-USB library has a setting to enable CRC checking (see below). In any event it requires the use of an external 18mhz crystal for the clock. My plan is to order some of those crystals next week and see how I make out. I'm assuming that the CRC check maybe...

I have a hid-data example, from V-USB working fine, using a ATTiny85. When using the included command line testing tool, written is C, called hidtool, I can send and then receive the sent data from this command line test. But being a command line program it's pretty basic and does not really...

Doing it from the tablet, now that would be some feat. Way beyond anything I could figure out, good luck.

Just found this discussion which may help. http://forum.pjrc.com/threads/846-Newbie-Question-about-the-quot-Teensy-Loader-quot

Couldn't you just create the hex file that gets loaded on the teensy, send the hex file to your remote locations and then run the teensy loader? I'm quite the novice at this stuff so maybe I'm missing something. Note that I have never done this myself.

I have a project prototype running on a Teensy 2 board using Arduino. I am setting the Teensy to be a USB Raw HID and am only using 2 outputs as PWM's. Anyway I want to work toward a possible production product and want to use a ATTiny85. My question is: will I only need the code that I...

Yeah, I figured out that the instance I want is the second one. At this point I am just wondering why it shows up twice when I list the devices in my code. It is not the only device that shows up twice so it must be "normal" or have something to do with the library I am using to list the HID...

OK found it. I needed to add my info to the /Contents/Resources/Java/Hardware/Teensy/cores/usb_rawhid/usb_private.h file.

Ok so I found the zip file for the HID_RAW.zip stuff. usb_rawhid.* Where would I put this code, and/or how would I get changes made to these files, loaded up to the Teensy as part of the loading a sketch process?

[SOLVED/Answered] see third post Is there a way to set the serial number returned or the product_string? It would be nice to brand the final product to make it unique.

Here is a better view of the HID data that is displayed. The difference between the two is the usage_page and the usage. 6 HIDDeviceInfo [path=USB_16c0_0486_0x7fa02c25d4c0, vendor_id=5824, product_id=1158, serial_number=, release_number=258, manufacturer_string=, product_string=Teensyduino...

Was wondering why I get two instances of the Teensy as a HID in my Java code. Here is a short snip of the java code, I'm using the hidapi-1.1.jar. { HIDManager manager = HIDManager.getInstance(); HIDDeviceInfo[] devs = manager.listDevices()...

OK, finally got it to work. I was able to find a file called libhidapi-jni-64.jnlib from http://code.google.com/p/javadrone/source/browse/lib/mac/?r=5daf4b0f68840d53d4c4d5e0600a9855e045a75e I needed to change the name, just drop the "-64" put it into my java library path...

I am trying to write a small app that will interface with the Teensy board. I am working in Java using Eclipse. Anyway I have spent the last few days trying to figure out how to configure my environment with the appropriate "native library". I have downloaded the hidapi-0.7.0.zip...