Do you know if Apple's keyboards use same usb coding as in this pdf:
http://www.mindrunway.ru/IgorPlHex/USBKeyScan.pdf
If not, then could someone post proper coding table for apple's usb keyboards?
Thanks
I would assume that Apple's keyboards work with non-Apple computers, so they should implement the standardized USB Human Interface Device (HID) specification. The key codes for that specification are found in the HID Usage Tables, table 12:
http://www.usb.org/developers/hidpage/Hut1_12v2.pdf
Related
I'm looking for Microntroller (something like ARM Cortex M4) that will have Bluetooth and CAN support. ST has a lot of Bluetooth or CAN chips, but none has both together...
We would like to avoid two chip design...
Thanks.
I did some brief research:
NXP KW39. This would be an M0+.
Renesas RA4W1 is a M4.
Silicon Labs have lots of Bluetooth products but I didn't find one with a CAN controller - I didn't look that carefully though.
ESP32 has both Bluetooth and CAN (they call it "Two-Wire Automotive Interface").
Here is a link to the datasheet: https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf
I am trying to do USB keyboard interfacing with arduino UNO. I would like to take input in the form of ascii values. How can i do it?
Thank you for answering my question. But i figured it out that we could use a female USB connector and connect the data pins with the pwm pins and further use the PS2Keyboard.h library to read input.
The newer 32u4-based Arduino boards (such as Leonardo) support a native Mouse and/or Keyboard integration. For the Arduino Uno you will need extra libraries/firmware to realize a HID keyboard. You can find several approaches and libraries on the web (e.g. Arduino HID Project 2.2, Turning an Arduino into a USB keyboard and so on. Search "Arduino Uno as HID keyboard").
I'm using my iPhone to scan in a complex 2D barcode. Problem is, the iPhone camera doesn't do so well at very close distances (less than 3 inches).
I was wondering if there were a way I could affix a Bluetooth low energy "sticker" to a piece of paper. The idea being instead of using the camera to scan a 2D barcode, I could just put my iPhone near the paper and "scan" it.
I'm extremely new to Bluetooth tech, so it's quite possible that what I'm asking for is completely ridiculous. Please forgive me, if that is the case.
Unlike NFC, Bluetooth Low-Energy devices need a power source, so it's imposible to just "print" them. They need a BLE chip and a battery to operate. So while you could use BLE same way you use NFC (proximity-based actions), you won't be able to do it with just a sticker.
Register at bluetooth sig for manufactorer id. Then put manufacturer id in advertisement package 0xff with id (16 bit) followed by the data. You must be sure your length is correct or iOS can't decode it.
For NFC, your scanner must be pretty close to the tag. But BLE devices work within several tens of meters without any problem. This is like an active RFID chip.
Of course, you need a power source for it. But if you print this BLE tag to a piece of expensive equipment, the cost of the tag and the battery is not a problem. You can use a button cell battery to power the BLE tag up. Let is broadcast/advertise some info once a second. Of course, you have to add some security mechanism if you want to be away from any replay attacks.
I have an RFID reader which is ISO 14443A compliant. It is capable of reading Mifare 1k (s50), Mifare 4k (s70), and Mifare Mini (s20) cards. I want to know if the same RFID reader can read the cards which are ISO 15693 compliant. I am new with RFID and I dont know anything about the ISO standards.
Compliancy to ISO14443 does not imply compliancy to ISO15693. However, some reader chips can do both. If you can tell the model name of your reader, or the reader chip inside, it may be possible to tell whether it supports ISO15693.
Check with your reader manufacturer to see if it supports both protocols. Many do; but, you should double check to be sure.
Even if it does support both, it will likely NOT be able to do so simultaneously. Likely, you will have to toggle between the two protocols in order work with both types of RFID tags.
ISO14443 A/B and ISO15693 standard operate on the same frequency 13.56 MHz, and both have about the same read range when reading tags 5 - 20 cm, but from then on the similarities end.
They have different ways to access RFID tags and perform inventory, data read/write and different memory organization.
Because of the similarities some manufacturers provide readers that can handle both types of tags, but the procedure is different due to the different standards (so a software designed to read ISO14443 will not read ISO15693 and vice-versa).
As previous answers you will need to check with your manufacturer to be sure, but if you need a recommendation of reader with which I have worked you can try the IDTronic Desktop EVO HF or IDTronic Desktop EVO LEGIC. From my knowledge it's under 100 $.
Datasheet here:
Desktop EVO Reader Datasheet
the RFID reader ISO 14443A can not read the cards which are ISO 15693.
they are totally two different kind standard.
for rfid reader, i think you could first learn from this rfid news here http://syncotek.com/news/
Not exactly a programming question, but close. I'll try my luck anyway.
The keyboard wedge
barcode scanner inserts the
translation device between the reader
and the keyboard. Data sent through a
wedge appears as if it was typed into
the computer, while the keyboard
itself remains fully functional.
Because a computer using a keyboard
wedge can't tell the difference
between data that is entered by a
scanning device, or data that is
entered by keyboard typing, a wedge
can be used to easily add barcode
reading capability to an existing
computer without modifying software
applications.
I'd like to know if all USB interface barcode scanners automatically translate digital signals from a barcode reader into keyboard strokes for a applications just like wedge or is USB different from wedge?
Many thanks
There are all sorts of API to access barcode scanners -- by no means do they all work by making believe they're "the keyboard"!-) For example, here you can find a reasonable summary of possibilities (the classic rs232 approach, the "wedge" one, and USB-interface ones) albeit for a single firm producing them. Depending on what programming you're willing and able to do, your best choice might be any of these approaches, or others yet.