deskthority

Indeed. Let me add a few requests for Soarer 2.0:


NeXT protocol support
ADB protocol support
SUN protocol support
See the pattern?
We need active open source development for this
It's not multiple projects
It's one product!


Man, having one multi-port, intelligently programmable ...

Well, until I've done my own scope traces to refute myself (and that with a non-clicky switch - that 1/5th second thing looks suspect), I choose to believe it is possible. :)

It would be nice to know the key switch circuit those scope traces above were observed on.

Also, a cycle of a 200 MHz clock ...

There are enough pins today to have each switch wired directly to an individual pin. And then you choose a microcontroller that has notification on pin change (or write that in FPGA), and aside from NKRO that would trivially give you things like a 200 MHz (or whatever clock speed you are running ...

And then you could change one of the two pieces to use electromagnets, computer-controlled – turning the switch into a Voice Coil Actuator, which would give you force feed back, so your users can fiddle with the flavour per-switch, (macro) layers could switch keys between flavours on the fly ...

If I recall correctly, Wyszecki & Stiles has some info on visibility and readability – granted it is not the newest source, but if you can find it in your local library, it is worth a read.

This is what I put together for my elderly father to improve contrast and navigation over his previous, run ...

oh sorry, I thought the microcontroller part of the circuit has a well working fixed schematic already, so that you could write that in skidl once, and then just generate the key matrix programmatically and connect the matrix row and column signals to free pins on the microcontroller. so that ...

Don't forget SKiDL: https://xess.com/skidl/docs/_site/index.html

I like those narrow keys on the top, remind me of the first computer I used: https://www.hpmuseum.org/hp9830.htm

And the case is neat too.

numist wrote: 02 Jun 2019, 06:28 if memory serves the capacitance should drop with the square of the distance between the plates

not with the square of the distance, just inversely proportional to it

PMed

I would like to try another approach for the measurement (keypress detection), as well as the programmability.

Looking for a relatively cheap(ish) board for prototyping a capacitive controller.

Does not have to look nice at all, just have a reasonable number of keys (say >30%) in place so that I have something to test with.

Keyboards where the capacitive matrix is separate from the controller electronics ...

I could use some cheap 100% keyboard cases for prototyping ISO (105 key) PCBs/controllers.

The larger (the more empty space around the keys for the controller) the better.

They do not have to look nice, as they will be hacked up anyway.

Fun with numbers:

The sensor apparently used in the Lachnit has 0.8 mm between the two light beams (not much, right?). Modern microcontrollers routinely have a 200 MHz clock. Let's put these two into perspective.

Let's conservatively assume that the metal hammer in the Lachnit keyboard does not ...

since it's a dual optical sensor wouldn't be more like:

r r XX__XX__XXXXXXXXXXXX____XX <-- r = reciever

that with a timer could give you the time difference between 2 transitions and with that velocity of sorts ??

tran2 - tran1 / time = velocity ??

Oh yes, that is true. In essence you would ...

then from there what I get is that the easier route is to send a very polite a loving email to pianoteq support asking if they have some documentation about what midi commands they accept and start designing from there, if we know what info to send its easier to see what sensors are more adequate ...

Really good point Mu, midi is very constrained and at the end of the day you only send noteON(velocity) and that velocity only have 128 points of resolution if I remember correctly

Don't limit our possibilities by this kind of thinking. These representational limits were true decades ago, but I ...

Mu, what tricks are possible with 3 sensors that are not possible with 2? Whole new world to me, interesting what's there

My theories:

with 3 points, you can afford to make the release point (note off) to be at a different point of key travel, than where the (imagined) hammer starts to ...

Where capsense could really shine is in a mechanical, weighted piano with hammers (like my Roland or indeed a real piano)

... which is indeed the case above (real piano mechanism) ...

and feeding its output to a software sound engine unlimited by midi’s 1980s constraints.

... which is where ...

Here however the concept is to sense the position of the hammers continuously. And that allows for some quite nice things (like negative latency).

An extra idea would be to also sense the position of the dampers, as that would be another currently missing piece of information that is available on a ...

What will this do/how will this be used?

SolidWorks can do curvature continuous fillets since 2015-2017ish - simply choose that option when creating the fillet.

(I'll leave the flamewar on actual contributions of Apple on the topic of curvature continuous curves - let's just say the original ...

show some photos so that we can have an idea what the thing looks like.

if you just need some basic shapes and measurements, you are often better off with calipers, rulers and tape measures.

to design a case takes some kind of engineering sense and planning and precision anyway, and studying the ...

I just saw there are videos. My further recommendations:

- measure velocity at the original position: the hammer
- ditch the rail (unless it is part of the original mechanism)
- mount a strip of (IR) transparent plastic or glass above the hammers where the strings would be hit; thick enough to get ...

just a few brief ideas:

- you could go acoustic and put a tiny microphone capsule to be hit by the hammer; potentially behind some individual damping or blocking to prevent capsule damage; and measure hammer speed indirectly from the loudness of the sound/vibration it generates - just like it ...

I was thinking about the easiest ways of converting the model m to operate with NKRO.

It seems there are three general possibilities:

Two more options:

have a replacement 1×N "matrix" custom membrane designed and printed
or you could try using the resistance inherent in the conductive film ...

DMA wrote: I fought damn EMI like 2 days ago, I know what I'm talking about.

Don't despair, Soarer's efforts were directed towards the much less noise-prone resistive keys, not capacitive like you do. Or am I mistaken?

Are you also experiencing EMI while not scanning?

Any ideas how to fix this?

Most files from digital cameras have a flag in them telling which main (90 degree) orientation the camera was in when the photo was taken. The photo is still stored in the file in the original orientation the sensor saw it. Smart image viewers take the orientation flag ...

<off>
If it really is 1KRO, how do you type e.g. the symbol # on it? Press Shift, release Shift, press 3/#, release 3/#?
</off>

Pick up a Win98 era ThinkPad with USB but without WiFi for about €30?

SpacemanToby wrote: I'll have to bring my work laptop home for testing.

Maybe it is some kind of electromagnetic interference where your work laptop is. Maybe take it outside, away from such possible sources.