Hi,
I'm kind of lost here...
On a Leonardo I send the command: Keyboard.write(65); shouldn't the result be A being sent instead of Q?
According to the documentation I found onlinekeyboard.write should use the ASCII code, or not?
Serial.write(65); gives me an A in the serial monitor.
Any clues what goes wrong?
I don't know if it matters but I use the Belgian keyboard layout on my PC (AZERTY)
Thanks!
Edit: typo corrected
Try sending:
Keyboard.write('Q');
If that sends "A" then the keyboard layout is the problem.
Yes, that's the problem! But now that we have named the disease, what is the possible cure?
Even if I'd by far prefer to change my keyboard to Qwerty, that's not really an option.
I did some more research, with a Teensy it's easy, in the IDE you can choose what keyboard type you want it to emulate.
Still no solution for the leonardo though :o
ON5MF:
Yes, that's the problem! But now that we have named the disease, what is the possible cure?Even if I'd by far prefer to change my keyboard to Qwerty, that's not really an option.
Well, you need to remap the wanted keys to their scan codes. Try this site:
http://www.quadibloc.com/comp/scan.htm
Look in HID.cpp in the Arduino distribution.
Inside that is:
#define SHIFT 0x80
const uint8_t _asciimap[128] =
{
0x00, // NUL
0x00, // SOH
0x00, // STX
0x00, // ETX
0x00, // EOT
0x00, // ENQ
0x00, // ACK
0x00, // BEL
0x2a, // BS Backspace
0x2b, // TAB Tab
0x28, // LF Enter
0x00, // VT
0x00, // FF
0x00, // CR
0x00, // SO
0x00, // SI
0x00, // DEL
0x00, // DC1
0x00, // DC2
0x00, // DC3
0x00, // DC4
0x00, // NAK
0x00, // SYN
0x00, // ETB
0x00, // CAN
0x00, // EM
0x00, // SUB
0x00, // ESC
0x00, // FS
0x00, // GS
0x00, // RS
0x00, // US
0x2c, // ' '
0x1e|SHIFT, // !
0x34|SHIFT, // "
0x20|SHIFT, // #
0x21|SHIFT, // $
0x22|SHIFT, // %
0x24|SHIFT, // &
0x34, // '
0x26|SHIFT, // (
0x27|SHIFT, // )
0x25|SHIFT, // *
0x2e|SHIFT, // +
0x36, // ,
0x2d, // -
0x37, // .
0x38, // /
0x27, // 0
0x1e, // 1
0x1f, // 2
0x20, // 3
0x21, // 4
0x22, // 5
0x23, // 6
0x24, // 7
0x25, // 8
0x26, // 9
0x33|SHIFT, // :
0x33, // ;
0x36|SHIFT, // <
0x2e, // =
0x37|SHIFT, // >
0x38|SHIFT, // ?
0x1f|SHIFT, // @
0x04|SHIFT, // A
0x05|SHIFT, // B
0x06|SHIFT, // C
0x07|SHIFT, // D
0x08|SHIFT, // E
0x09|SHIFT, // F
0x0a|SHIFT, // G
0x0b|SHIFT, // H
0x0c|SHIFT, // I
0x0d|SHIFT, // J
0x0e|SHIFT, // K
0x0f|SHIFT, // L
0x10|SHIFT, // M
0x11|SHIFT, // N
0x12|SHIFT, // O
0x13|SHIFT, // P
0x14|SHIFT, // Q
0x15|SHIFT, // R
0x16|SHIFT, // S
0x17|SHIFT, // T
0x18|SHIFT, // U
0x19|SHIFT, // V
0x1a|SHIFT, // W
0x1b|SHIFT, // X
0x1c|SHIFT, // Y
0x1d|SHIFT, // Z
0x2f, // [
0x31, // bslash
0x30, // ]
0x23|SHIFT, // ^
0x2d|SHIFT, // _
0x35, // `
0x04, // a
0x05, // b
0x06, // c
0x07, // d
0x08, // e
0x09, // f
0x0a, // g
0x0b, // h
0x0c, // i
0x0d, // j
0x0e, // k
0x0f, // l
0x10, // m
0x11, // n
0x12, // o
0x13, // p
0x14, // q
0x15, // r
0x16, // s
0x17, // t
0x18, // u
0x19, // v
0x1a, // w
0x1b, // x
0x1c, // y
0x1d, // z
0x2f|SHIFT, //
0x31|SHIFT, // |
0x30|SHIFT, // }
0x35|SHIFT, // ~
0 // DEL
};Now if you rework that you should be able to remap the keys.
Thanks for the help Nick!
Google did not yet find me a complete table of the 'Azerty' vs 'Qwerty' scancodes so I guess I'll have to test those myself.
Just remember that the scan codes represent a location on the keyboard and have nothing to do with the label on the key or the interpretation of the key by the receiving device. Look at diagrams of the two keyboards and you will see what codes have to be moved and where.
Yes John,
I kind of figured that out already. Some more research to do 