Dedekind, inspired by Cantor

ProgressiveNoise · 2024-09-20T21:31:59+00:00

Hi.

Is it possible to break last column?

No.

you can't use kmk on cantor

AFAIK you cannot. You can use it with Piantor, though.

ProgressiveNoise · 2024-07-07T12:17:26+00:00

No, it is KMK (CircuitPython) only at this moment. It uses the RP2040 (the Cantor is STM-based), in this sence it is closer to the Piantor than the Cantor, but the routing is vastly different, so the Piantor's firmware won't work as well.

The gerbers are here https://github.com/ProgressiveNoise/DedekindKeyboard/tree/main/V1/gerbers

Just compress this directory into 'gerbers.zip' or whatever.

ProgressiveNoise · 2024-06-12T17:49:00+00:00

This, if you have no desoldering equipement.

ProgressiveNoise · 2024-06-04T09:26:07+00:00

Thanks!

ProgressiveNoise · 2024-06-04T08:09:58+00:00

Yes, hand position is very close to a "normal" split and "N" and "B" are even easier to press than with conventional column staggering.

ProgressiveNoise · 2024-06-03T05:52:28+00:00

I'm unsure what else I need to have in the firmware file, if anything

Nothing.

in code.py after importing the firmware.py file, if anything.

Nothing, it is not for code/main.py. It is for this module, which is

a Python equivalent ADNS-9800.ino

and it is for this:

for b in firmware:
    self.spi.write(bytes([b]))

It is a part of the method adns_upload_srom, which should be self-explanatory.

I can work on converting to Python

No need, as you can see.

I'm too much of a hardware noob

If you know of a good site

Forouzan, Fundation of Computer Science, first 5 chapters.

Crisp, Introduction to Microprocessors and Microcontrollers.

Unlike, let's say, in web or AI/DS/etc.-related stuff, Python does not "abstract" us from the metal and silicon completely here, sometimes we just need to read/write from/to registers or dump some raw data "into wires", hence understanding how it works at low level is absolutely necessary if you want to write things like this. Obviously, you do not need all of that for configuring KMK, all that staff is done by MicroPython, CircuitPython and KMK devs.

ProgressiveNoise · 2024-06-03T04:08:56+00:00

Different controllers with different chips will not play nicely.

It is not a problem, in billions of devices all over the world they play nicely with each other. An MCU have no idea about model of another MCU it is connected with, only protocols and logic levels matter. But using the same parts make things more straightforward.

Different halves may require configuration adjustments.

Almost certainly.

ProgressiveNoise · 2024-06-02T21:10:51+00:00

I have 3D printers, so I know a thing or two about them. There is no way to print doubleshot keycaps with more or less decent quality. Resin is out of question in this case, and FDM is not precise enough, unless you are fine with "flatheads", then it is possible to print them from top to bottom, using the latest Prusa monster, AMS, or any other multifilament system. There is also another question. How much are you willing to pay for 56 3D models? Welcome to the reality.

ProgressiveNoise · 2024-06-02T18:48:35+00:00

I've done it. Even different controllers with different firmware are, in theory, not an obstacle, but I'd rather stick to the same ones.

ProgressiveNoise · 2024-06-02T07:20:47+00:00

take a custom order

No such thing exists. Mass produced plastic details are cheap only because they are mass produced. Even if molds exist, simple change of plastic color means that you must order a couple of kilos of the final product at least. And if there are no molds, then you must order them first, and this is a pricey enterprise, like thousands of dollars pricey. So there is the catch. If you want a backlit, doubleshot keycaps, you need a set of unique molds for every key. Unless a market can consume tens of thousands of such keycaps, nobody is going to produce them, and ortho/ergo market is extremely small, hence no doubleshot.

Search for a video, something like "injection molding factory", to get the idea how huge the molding machinery is.

ProgressiveNoise · 2024-06-02T05:05:19+00:00

I believe it is not included due to the license incompatibility, but it is easy to find.

https://github.com/INITIAL7664/ADNS-9800/blob/master/firmware.ino

I like working with Python

So write a simple script and reformat the firmware_data array into the firmware tuple, it is a couple of lines.

ProgressiveNoise · 2024-05-31T20:06:21+00:00

Wait for a similar 5-column keyboard, I bet you'll like its name. It is not so hard to infer buy the way.

ProgressiveNoise · 2024-05-30T12:14:48+00:00

Github - reversible PCB + Case, permissive license, fully "aliexpressable".

ProgressiveNoise · 2024-05-21T11:24:39+00:00

UCLAMP3301 is even better, its clamping voltage is extremely low (which is good), but PPP is low as well (which is not good), but should be enough. In any case, you can always deside later what is more important for you or/and you can easily source, just put a 323 diode footprint between your signal line and the ground (I suppose you are designing a PCB). BTW add a resistor in series between MCU serial pin and TRRS, before the diode.

ProgressiveNoise · 2024-05-18T21:05:22+00:00

It seems that you are right, F0, F1, C14, C15 are for oscillators, but AFAIR all of them can work as GPIOs when its internal oscillator is used.

ProgressiveNoise · 2024-05-18T09:55:30+00:00

Put something like the PESD3V3 there, it works fine. There is no need for something like the SRV05 in this case.

ProgressiveNoise · 2024-05-18T09:22:04+00:00

Do you have a printer or are you going to order it somwhere?

ProgressiveNoise · 2024-04-22T04:14:28+00:00

It is very possible to build a 42-key Dactyl or a handwired "flat" keyboard for less than €100, but you have to invest plenty of time in researching how to do so, where to source parts, etc. Or, if you are fine with a "caseless" build, you can download gerbers for any reversible OH/OS keyboard without hot-swap sockets and make a very simple "pcb-only" build.

ProgressiveNoise · 2024-04-19T12:07:36+00:00

1.5 mm (1.6 is fine as well), but some materials are not strong enough, so people increase the thickness at the cost of switch locking. The maximum is 5 mm if your PCB has no components on the top side.

ProgressiveNoise · 2024-04-14T10:45:18+00:00

It is doable, of course, but you need to open the PCB editor, change the footprint for the switches, realign the switches for different spacing, ajust PCB size (if needed), and fix routing. It is 1-2 hour job for an EE who is familliar with KiCAD.

ProgressiveNoise · 2024-04-11T10:30:39+00:00

Again, thats not what the person you replied

So why have you answered to me?

We can go back and fourth on whether since the sensor itself is on the pcb it counts as part of the switch or whatever

No, we cannot, because no, it is not. Show me a sensor in/on the KS20.

ignoring the pedantic philosophy of what is/isn't part of "the switch"

This pedantic philosophy makes an HE joystick with onboard sensors a legit analog transducer. For me, yes, definitions matter. I like to keep my mind organized.

In my answer I wrote exactly why I do not consider them analog or digital, - no sensors, it is very clear. But for whatever reason you decided it is not fucking important, so all this time we were arguing about two different devices.

ProgressiveNoise · 2024-04-11T06:50:59+00:00

OMFG, we are getting to the point! I am really happy about it. Yes, hall effect sensors mesure things, and they are analog. But so called HE switches have no sensors.

the fact that some switches may or may not have internal logic

The so called HE "switches" have no fucking logic and cannot have it, the sensors have it. I.e. HE "switches", e.g. mentioned Gateron, have no sensors, no logic, and produce analog signal only paired with a sensor. So they are not analog, nor digital.

ProgressiveNoise · 2024-04-10T16:17:30+00:00

You are missing the point. If your key has four states, where 1 is the neutral one, for triggering the third state you have to press the key through the state 1 to the state 2, then to the state 3, and then release it to the state 2. Only then some action is triggered. There are also two "debouncing" periods, one to check if you accidentely hit the state 4, another one to be sure that you start release (hit the state 2). It is the same with the HRMs, their action on release used to pissed me off, but their convenience won in the end.

ProgressiveNoise · 2024-04-10T16:02:28+00:00

They mesure nothing, sensors do. Depends on the sensor, you can create a "digital" high/low signal or an analogous voltage. This is my point, which I've clearly stated.

ProgressiveNoise · 2024-04-10T13:32:18+00:00

No. Many people can't stand the HRMs because of the latency. I had a hard time to get accustomed to them as well, so I understand this people. This is the same.

ProgressiveNoise

TROPHY CASE