| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
* this is required by VUSB which we don't support currently anyway
|
|
|
|
* In contrast to the relay breakout board I was using before,
the solenoid driver is HIGH-active, so some code had to be changed
as well.
|
|
|
|
|
|
Teensy 2.0++
|
|
* It is deactivated after a short while, so the state of the solenoid does
not correspond with the state of the key.
* The MCU now less frequently crashes, but quite possibly we will need a separate
power supply to use the solenoid.
|
|
* since we use timer 3 exclusively for the buzzer but trigger the pin
using an IRQ handler, there is no longer any need to occupy a high-resolution
pin for the buzzer.
* PD5 became a new high resolution LED
* PD0 became the new buzzer pin
* rearranged the pins used for the different LEDs so that the distribution
of high-resolution LEDs is symmetric
* Timer 0 is no longer used/modified by setting LEDs.
This avoids some workarounds as timer 0 is also used by tmk's timer module.
* The song routines could be slightly improved using the timer module.
* documented the LED and buzzer pinout in README
|
|
|
|
it could be active at the time of the function call due to the keyclick mode
|
|
* the keypress events were swallowed due to debouncing
* instead, we process the corresponding bits in the keyboard matrix
now only after debouncing.
* we now generate a short keypress event (immediately followed by a keyrelease)
not only when removing, but also when inserting the physical key.
* when removing the key, F18 (in Unimap's geometry, by default mapped to RCTRL)
is additionally pressed. This can be used to discern removing from inserting.
In the common case that you own only one physical key, you can remap F18
to the removal action and F19 (or whatever corresponds to your key) to the
insertion action.
|
|
|
|
|
|
|
|
USB port
The original documentation states that they simply read the matrix twice
in order to debounce. They did not mention any delays.
|
|
|
|
|
|
|
