|
67659
|
The greatest alarm clock to ever live! by @shyamks The greatest alarm clock to ever live! by @shyamks1828 | Stardance...
|
shyamks1828
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The greatest alarm clock to ever live! by @ Title: The greatest alarm clock to ever live! by @shyamks1828 | Stardance...
|
1793732367.4722633
|
1794337167.4722633
|
|
67660
|
elepahant alarm clock by @aadhii | Stardance
|
aadhii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: elepahant alarm clock by @aadhii | Stardanc Title: elepahant alarm clock by @aadhii | Stardance...
|
1793732368.4001224
|
1794337168.4001224
|
|
67661
|
astro botany by @ibuild | Stardance
|
ibuild
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: astro botany by @ibuild | Stardance
|
1793732369.2910464
|
1794337169.2910464
|
|
67662
|
Macropad by @Pilot_572 | Stardance
|
Pilot_572
|
0
|
5.35
|
0
|
[]
|
[{"post_id": 76785, "ts": "202 [{"post_id": 76785, "ts": "2026-10-04T15:49:41Z", "hours": 3.6092, "text": "THE 3D MODEL IS DONEEE. This took… not too long actually, 2 days to finish the PCB, 3D model AND the firmware, im too good. I will submit it, let’s hope for the best!"}, {"post_id": 76650, "ts": "2026-10-04T08:11:56Z", "hours": 1.7381, "text": "Macropad! Yesterday I finished the pcb and everything, now imma go onto 3d modeling."}]...
|
Title: Macropad by @Pilot_572 | Stardance
Devlogs Title: Macropad by @Pilot_572 | Stardance
Devlogs:
Macropad! Yesterday I finished the pcb and everything, now imma go onto 3d modeling.
THE 3D MODEL IS DONEEE. This took… not too long actually, 2 days to finish the PCB, 3D model AND the firmware, im too good. I will submit it, let’s hope for the best!...
|
1793732370.163821
|
1794337170.163821
|
|
67663
|
Converter by @Midhunesh | Stardance
|
Midhunesh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Converter by @Midhunesh | Stardance
|
1793732373.7724302
|
1794596373.7724302
|
|
67664
|
Virtual brain Ai by @zndrnx | Stardance
|
zndrnx
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Virtual brain Ai by @zndrnx | Stardance
|
1793732374.6286163
|
1794337174.6286163
|
|
67665
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793760591.987214
|
1794624591.987214
|
|
67666
|
Alarm clock by @nikolopoulosmaximos3 | Stardance
|
nikolopoulosmaximos3
|
0
|
4.33
|
0
|
[]
|
[{"post_id": 76545, "ts": "202 [{"post_id": 76545, "ts": "2026-10-03T22:05:01Z", "hours": 0.3592, "text": "Finishing up the CAD, Exporting eveyrthing to one file, Creating the GitHub repository."}, {"post_id": 76421, "ts": "2026-10-03T14:12:03Z", "hours": 3.9736, "text": "First project: I just worked with KiCad to design a SImple PCB, follwed by designing a custom shell for the alarm. Next is to write the code for the ESP32 inside the alarm."}]...
|
Title: Alarm clock by @nikolopoulosmaximos3 | Star Title: Alarm clock by @nikolopoulosmaximos3 | Stardance
Devlogs:
First project: I just worked with KiCad to design a SImple PCB, follwed by designing a custom shell for the alarm. Next is to write the code for the ESP32 inside the alarm.
Finishing up the CAD, Exporting eveyrthing to one file, Creating the GitHub repository....
|
1793732375.5121832
|
1794337175.5121832
|
|
67667
|
live-stop by @pwohlfahrt | Stardance
|
pwohlfahrt
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: live-stop by @pwohlfahrt | Stardance
|
1793732376.4842594
|
1794337176.4842594
|
|
67668
|
Stress reliever neckband by @SumukhAgastipurkar | Stress reliever neckband by @SumukhAgastipurkar | Stardance...
|
SumukhAgastipurkar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Stress reliever neckband by @SumukhAgastipu Title: Stress reliever neckband by @SumukhAgastipurkar | Stardance...
|
1793732377.3739557
|
1794337177.3739557
|
|
67669
|
Weendoes OS by @Lizardy | Stardance
|
Lizardy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Weendoes OS by @Lizardy | Stardance
|
1793732378.2758694
|
1794337178.2758694
|
|
67670
|
JARVIS THE BOT by @AIBEL_BAIJU | Stardance
|
AIBEL_BAIJU
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: JARVIS THE BOT by @AIBEL_BAIJU | Stardance
|
1793732379.1679935
|
1794337179.1679935
|
|
67671
|
BLARE by @frinkluko | Stardance
|
frinkluko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: BLARE by @frinkluko | Stardance
|
1793732380.054365
|
1794337180.054365
|
|
67672
|
My very own WebOS by @matyaschudy510 | Stardance
|
matyaschudy510
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @matyaschudy510 | Star Title: My very own WebOS by @matyaschudy510 | Stardance...
|
1793732380.9539742
|
1794337180.9539742
|
|
67673
|
Special car for engineering student by @Jaiditya | Special car for engineering student by @Jaiditya | Stardance...
|
Jaiditya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Special car for engineering student by @Jai Title: Special car for engineering student by @Jaiditya | Stardance...
|
1793732382.7926056
|
1794337182.7926056
|
|
67674
|
My very own WebOS by @aaryanhm | Stardance
|
aaryanhm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @aaryanhm | Stardance
|
1793732385.8218224
|
1794337185.8218224
|
|
67675
|
A advanced Astronomy and Astrophotography rig by @ A advanced Astronomy and Astrophotography rig by @Shaik_Nissar_Hussain | Stardance...
|
Shaik_Nissar_Hussain
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: A advanced Astronomy and Astrophotography r Title: A advanced Astronomy and Astrophotography rig by @Shaik_Nissar_Hussain | Stardance...
|
1793732386.70389
|
1794337186.70389
|
|
67676
|
hackpadd by @cseprenyi | Stardance
|
cseprenyi
|
0
|
1.65
|
0
|
[]
|
[{"post_id": 76397, "ts": "202 [{"post_id": 76397, "ts": "2026-10-03T12:52:40Z", "hours": 0.3142, "text": "have a repo now"}, {"post_id": 76396, "ts": "2026-10-03T12:28:45Z", "hours": 0.8731, "text": "Made a case for it using FreeCAD. took longer than expected honestly, mostly because i haven’t used FreeCAD in a while, and never actually finished anything with it since i don’t have a 3D printer yet"}, {"post_id": 76386, "ts": "2026-10-03T11:34:28Z", "hours": 0.4581, "text": "Done with the KiCad part, now for the case!"}]...
|
Title: hackpadd by @cseprenyi | Stardance
Devlogs Title: hackpadd by @cseprenyi | Stardance
Devlogs:
Done with the KiCad part, now for the case!
Made a case for it using FreeCAD. took longer than expected honestly, mostly because i haven’t used FreeCAD in a while, and never actually finished anything with it since i don’t have a 3D printer yet
have a repo now...
|
1793732390.0439932
|
1794337190.0439932
|
|
67677
|
My awesome macropad! by @noelbode | Stardance
|
noelbode
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @noelbode | Stardan Title: My awesome macropad! by @noelbode | Stardance...
|
1793732392.4789836
|
1794337192.4789836
|
|
67678
|
Blare alarm by @DTFive | Stardance
|
DTFive
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Blare alarm by @DTFive | Stardance
|
1793458429.869453
|
1794322429.869453
|
|
67679
|
My awesome macropad! by @Sundhar | Stardance
|
Sundhar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Sundhar | Stardanc Title: My awesome macropad! by @Sundhar | Stardance...
|
1793732393.3809636
|
1794337193.3809636
|
|
67680
|
Chopsticks by @wldd | Stardance
|
wldd
|
0
|
2.56
|
0
|
[]
|
[{"post_id": 77644, "ts": "202 [{"post_id": 77644, "ts": "2026-10-07T18:42:38Z", "hours": 1.0525, "text": "done some more work on the minimax algorithm. might improve it more in the future."}, {"post_id": 77291, "ts": "2026-10-06T13:36:52Z", "hours": 1.5094, "text": "been working on the minimax algorithm. seems to be working better now, but i need to optimize it a bit more"}]...
|
Title: Chopsticks by @wldd | Stardance
Devlogs:
b Title: Chopsticks by @wldd | Stardance
Devlogs:
been working on the minimax algorithm. seems to be working better now, but i need to optimize it a bit more
done some more work on the minimax algorithm. might improve it more in the future....
|
1793732396.1285684
|
1794337196.1285684
|
|
67681
|
My first slack bot! by @mohammedaleem1323 | Starda My first slack bot! by @mohammedaleem1323 | Stardance...
|
mohammedaleem1323
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @mohammedaleem1323 | Title: My first slack bot! by @mohammedaleem1323 | Stardance...
|
1793735255.7786512
|
1794340055.7786512
|
|
67682
|
Han's website :> by @hann | Stardance
|
hann
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Han's website :> by @hann | Stardanc Title: Han's website :> by @hann | Stardance...
|
1793735256.703693
|
1794340056.703693
|
|
67683
|
game by @frinkluko | Stardance
|
frinkluko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: game by @frinkluko | Stardance
|
1793735258.098323
|
1794340058.098323
|
|
67684
|
My very own WebOS by @Arman2012 | Stardance
|
Arman2012
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Arman2012 | Stardance
|
1793735258.9485006
|
1794340058.9485006
|
|
67685
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793760592.8651168
|
1794624592.8651168
|
|
67686
|
riggermortis by @xenoaitham | Stardance
|
xenoaitham
|
0
|
18.81
|
0
|
[]
|
[{"post_id": 76925, "ts": "202 [{"post_id": 76925, "ts": "2026-10-05T03:12:20Z", "hours": 10.9147, "text": "the sculpt wires into the product flow The proportion and volume sculpting work was measured and gated, but had no real user-facing path yet. That debt got paid: a new command line tool measures a reference image’s proportions and volume ratios into one deterministic file, and both the manual tool and the interactive in-app action now call the same shared function underneath, so they can’t quietly drift apart. The real proof was ordering: sculpt once at rest pose, then animate, and the sculpt has to survive byte-identically. It does, frame-one drift came out effectively zero across seventy checks. Three real bugs earned their keep. First, two test rigs sharing one scene made solved values look wrong, the real cause was one fixture already carrying an earlier sculpt while the other’s baseline measurement accidentally captured the overlapping shape of both figures at once. Took a full debugging ladder to isolate, fixed with a clean scene per case, a lesson the project had already learned once before, now learned twice. Second, baking an animation shifts frame numbers by one internally, so comparing a frame against its own neighbor instead of itself made results look dramatically worse than they actually were. A one-line offset fix, with the reasoning written directly into the check itself this time so it can’t get silently lost again. Third, comparing raw bone positions across an animated sequence turned out to be the wrong check entirely, since a position-based re-solve is supposed to compensate for the current pose’s rotation by design, not match it exactly. Redefined what the check actually verifies, and caught a related bug along the way: an assigned animation silently overrides a rest-pose snapshot unless that animation gets explicitly muted first. Landed with fifteen new tests, the full suite green, and every number comfortably inside its bar except one, a single rig type’s re-sculpt accuracy sits just barely over target, left as the next rough edge."}, {"post_id": 76391, "ts": "2026-10-03T11:46:33Z", "hours": 7.8906, "text": "volume from silhouette The third model decision is made and the volume feature is real. The engine now carries a third pinned model, a segmentation pass, plus a working body sculpt: feed it a reference shape and the character’s hip, waist, chest, and thigh widths move to match it, skeleton provably untouched. Getting there meant benchmarking five real candidate models on real hardware, checksums, speed, and accuracy each, rejecting six other families with the evidence written down. Funniest catch: the model built specifically for segmenting people was completely blind to the test case, zero accuracy, while the general-purpose model saw it fine and ran cheaper too. The mechanism authors real shape keys per body region, so the adjustable sliders are the solved math directly, and every pose/animation path downstream sees a completely unchanged skeleton. The real fight was realizing the first passing test was a lie. A whole-frame comparison technically passed on a completely unsculpted body, since the measurement was too insensitive to tell a correctly sculpted shape from an untouched one. Fixed by scoping comparisons to the actual body regions with no model in the loop, publishing a baseline next to every result so a cheating pass can’t hide again. Smaller lessons banked too: a slider silently defaulting to zero killed half its usable range, one rig type needed its math in a different coordinate space entirely or it silently did nothing, leftover scene state poisoned later measurements, and naive bone-weight assignment broke the hip region specifically. Numbers came out solid: worst-case regional accuracy clears the bar across every test case, width delivery lands exact to four decimal places, solved values track intended targets within about 3% through the real model, and resetting a sculpt restores the original mesh almost exactly. Next: wire both sculpts into the real user-facing flow, and prove the sculpt survives animation, set once, then animate, and the widths hold."}]...
|
Title: riggermortis by @xenoaitham | Stardance
De Title: riggermortis by @xenoaitham | Stardance
Devlogs:
volume from silhouette The third model decision is made and the volume feature is real. The engine now carries a third pinned model, a segmentation pass, plus a working body sculpt: feed it a reference shape and the character’s hip, waist, chest, and thigh widths move to match it, skeleton provably untouched. Getting there meant benchmarking five real candidate models on real hardware, checksums, speed, and accuracy each, rejecting six other families with the evidence written down. Funniest catch: the model built specifically for segmenting people was completely blind to the test case, zero accuracy, while the general-purpose model saw it fine and ran cheaper too. The mechanism authors real shape keys per body region, so the adjustable sliders are the solved math directly, and every pose/animation path downstream sees a completely unchanged skeleton. The real fight was realizing the first passing test was a lie. A whole-frame comparison technically passed on a completely unsculpted body, since the measurement was too insensitive to tell a correctly sculpted shape from an untouched one. Fixed by scoping comparisons to the actual body regions with no model in the loop, publishing a baseline next to every result so a cheating pass can’t hide again. Smaller lessons banked too: a slider silently defaulting to zero killed half its usable range, one rig type needed its math in a different coordinate space entirely or it silently did nothing, leftover scene state poisoned later measurements, and naive bone-weight assignment broke the hip region specifically. Numbers came out solid: worst-case regional accuracy clears the bar across every test case, width delivery lands exact to four decimal places, solved values track intended targets within about 3% through the real model, and resetting a sculpt restores the original mesh almost exactly. Next: wire both sculpts into the real user-facing flow, and prove the sculpt survives animation, set once, then animate, and the widths hold.
the sculpt wires into the product flow The proportion and volume sculpting work was measured and gated, but had no real user-facing path yet. That debt got paid: a new command line tool measures a reference image’s proportions and volume ratios into one deterministic file, and both the manual tool and the interactive in-app action now call the same shared function underneath, so they can’t quietly drift apart. The real proof was ordering: sculpt once at rest pose, then animate, and the sculpt has to survive byte-identically. It does, frame-one drift came out effectively zero across seventy checks. Three real bugs earned their keep. First, two test rigs sharing one scene made solved values look wrong, the real cause was one fixture already carrying an earlier sculpt while the other’s baseline measurement accidentally captured the overlapping shape of both figures at once. Took a full debugging ladder to isolate, fixed with a clean scene per case, a lesson the project had already learned once before, now learned twice. Second, baking an animation shifts frame numbers by one internally, so comparing a frame against its own neighbor instead of itself made results look dramatically worse than they actually were. A one-line offset fix, with the reasoning written directly into the check itself this time so it can’t get silently lost again. Third, comparing raw bone positions across an animated sequence turned out to be the wrong check entirely, since a position-based re-solve is supposed to compensate for the current pose’s rotation by design, not match it exactly. Redefined what the check actually verifies, and caught a related bug along the way: an assigned animation silently overrides a rest-pose snapshot unless that animation gets explicitly muted first. Landed with fifteen new tests, the full suite green, and every number comfortably inside its bar except one, a single rig type’s re-sculpt accuracy sits just barely over target, left as the next rough edge....
|
1793458438.218095
|
1794322438.218095
|
|
67687
|
My own site! by @ananzeh | Stardance
|
ananzeh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @ananzeh | Stardance
|
1793735259.8413212
|
1794340059.8413212
|
|
67689
|
Frictionless by @Evanthecat | Stardance
|
Evanthecat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @Evanthecat | Stardance
|
1793735262.4210405
|
1794340062.4210405
|
|
67690
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793760594.0232425
|
1794624594.0232425
|
|
67691
|
My very own WebOS by @YAWR | Stardance
|
YAWR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @YAWR | Stardance
|
1793735263.3302104
|
1794340063.3302104
|
|
67692
|
My awesome macropad! by @Ananya303 | Stardance
|
Ananya303
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Ananya303 | Starda Title: My awesome macropad! by @Ananya303 | Stardance...
|
1793735264.2183647
|
1794340064.2183647
|
|
67693
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1793760595.7442944
|
1794624595.7442944
|
|
67694
|
My awesome macropad! by @parasitegami | Stardance
|
parasitegami
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @parasitegami | Sta Title: My awesome macropad! by @parasitegami | Stardance...
|
1793735265.0885894
|
1794340065.0885894
|
|
67695
|
ESPvision by @omarelhalaby76 | Stardance
|
omarelhalaby76
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ESPvision by @omarelhalaby76 | Stardance
|
1793735265.9749818
|
1794340065.9749818
|
|
67696
|
ESPvision by @omarelhalaby76 | Stardance
|
omarelhalaby76
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ESPvision by @omarelhalaby76 | Stardance
|
1793735266.8510861
|
1794340066.8510861
|
|
67697
|
My awesome macropad! by @UncleGreg | Stardance
|
UncleGreg
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @UncleGreg | Starda Title: My awesome macropad! by @UncleGreg | Stardance...
|
1793735267.7069945
|
1794340067.7069945
|
|
67698
|
Mini Dance-Dance-Revolution by @Evanthecat | Stard Mini Dance-Dance-Revolution by @Evanthecat | Stardance...
|
Evanthecat
|
0
|
21.54
|
0
|
[]
|
[{"post_id": 82120, "ts": "202 [{"post_id": 82120, "ts": "2026-10-24T00:18:26Z", "hours": 2.7589, "text": "Added screw holes to CAD, added better animations to firmware, and updated production files. I added holes to the HackPad case to fit the heatset inserts and modeled a simple placeholder part to act as a heatset insert in my CAD (to fix the problem of the screws being too short). I also added fillets to some edges and removed the holes on the cover plate (the plate would be held to the case by the heatset inserts). Since I wanted the OLED to be responsive to key presses, I decided to redesign the firmware to have each key fill in when pressed. To do this, I separated each sprite into individual animations and drew each animation separately on the screen by moving the origin, checking key presses to display different key animations."}, {"post_id": 80847, "ts": "2026-10-19T00:27:01Z", "hours": 4.4925, "text": "Made animation for OLED and finished firmware. After creating a simple sprite animation in Krita and writing the QMK firmware (it took me hours to realize that the pin labels were GPIO numbers and match everything), my keymap.c file somehow deleted itself, skipping past the recycling bin, so I had to code it twice. I also stayed up until 11:30pm and used the next morning to debug the various causes of compiler errors. Many of them were just typos like missing a comma or forgetting a semicolon after an enum, but I had to just test which function actually worked for layer switching because all the others gave the error “this statement is not necessary” somewhere in the QMK code. As I was working on the GitHub repository, I realized that the screws were too short to go through my entire case, so I’ll have to redesign it next time."}, {"post_id": 79455, "ts": "2026-10-14T03:06:22Z", "hours": 1.2028, "text": "Rewired part of PCB and worked on firmware. While looking at XIAO RP2040 diagrams, I realized that the SDA and SCL pins were not connected to the right spot. I swapped the connections for those pins and row 0 and row 1. I swapped out the switches in my CAD for the .STEP files in the official resources and spent some time defining the pins in the firmware."}, {"post_id": 79391, "ts": "2026-10-13T19:45:52Z", "hours": 3.3419, "text": "Realigned components on the PCB and finished most of the CAD. While trying to align the switches on the PCB to the grid, I realized that the footprints were snapping to weird increments. Eventually, I decided to use the position values in the sidebar to manually set the x and y coordinates of the switches. I also moved the XIAO RP2040 to the right and the diodes further down for more room in the CAD. After finishing the cover plate, I modeled a simple knob for the rotary encoder."}, {"post_id": 78911, "ts": "2026-10-12T00:45:25Z", "hours": 2.4681, "text": "Fixed small measurement errors, realigned the components, and worked on the cover piece. While I was working on the cover piece, I noticed a small piece sticking out, a sign of a slightly mismatched measurement. It turns out that most of my plates had small measurement errors (from slightly unconstrainted rectangles made while shortening one of the sides). While realigning my components, I learned that my PCB model had misplaced holes, which meant that I couldn’t trust it for measurements. I also lowered my rotary encoder so it wouldn’t clip into the top panel."}, {"post_id": 78501, "ts": "2026-10-11T00:19:59Z", "hours": 2.1903, "text": "Aligned keycaps/OLED and edited case to better fit components. After working on the top plate for a while, I realized that a lot of my parts were clipping (e.g. diodes and microcontroller), so I cut away parts of the plate to make things fit. I improved my method for aligning components after having the align the keycaps on the switches (I spent a long time trying to align the original keycap to the origin before just calculating the displacement to where I needed it to be). After putting on the top plate, I raised part of the bottom plate to make a cutout for the USB-A port and raised the OLED screen. I also started working on the decorative top plate that’ll go onto top of everything."}, {"post_id": 78210, "ts": "2026-10-09T23:38:37Z", "hours": 5.0825, "text": "Created PCB and started work on assembling in CAD. I had to scale down the amount of keys and remove the LEDs because there weren’t enough pins. I spent way too long searching for OLED and Rotary Encoder symbols while making the schematic before I realized that they just need the footprints paired with generic symbols from the default library. While routing the PCB, I learned that the red and blue wires are for different layers and assigned footprints to the diodes so they would show up (I forgot to do that while working on the schematic). After aligning most of the parts in Fusion, I realized that one of the switches and the rotary encoder were overlapping and that I could just export the PCB as a .step file from KiCad."}]...
|
Title: Mini Dance-Dance-Revolution by @Evanthecat Title: Mini Dance-Dance-Revolution by @Evanthecat | Stardance
Devlogs:
Created PCB and started work on assembling in CAD. I had to scale down the amount of keys and remove the LEDs because there weren’t enough pins. I spent way too long searching for OLED and Rotary Encoder symbols while making the schematic before I realized that they just need the footprints paired with generic symbols from the default library. While routing the PCB, I learned that the red and blue wires are for different layers and assigned footprints to the diodes so they would show up (I forgot to do that while working on the schematic). After aligning most of the parts in Fusion, I realized that one of the switches and the rotary encoder were overlapping and that I could just export the PCB as a .step file from KiCad.
Aligned keycaps/OLED and edited case to better fit components. After working on the top plate for a while, I realized that a lot of my parts were clipping (e.g. diodes and microcontroller), so I cut away parts of the plate to make things fit. I improved my method for aligning components after having the align the keycaps on the switches (I spent a long time trying to align the original keycap to the origin before just calculating the displacement to where I needed it to be). After putting on the top plate, I raised part of the bottom plate to make a cutout for the USB-A port and raised the OLED screen. I also started working on the decorative top plate that’ll go onto top of everything.
Fixed small measurement errors, realigned the components, and worked on the cover piece. While I was working on the cover piece, I noticed a small piece sticking out, a sign of a slightly mismatched measurement. It turns out that most of my plates had small measurement errors (from slightly unconstrainted rectangles made while shortening one of the sides). While realigning my components, I learned that my PCB model had misplaced holes, which meant that I couldn’t trust it for measurements. I also lowered my rotary encoder so it wouldn’t clip into the top panel.
Realigned components on the PCB and finished most of the CAD. While trying to align the switches on the PCB to the grid, I realized that the footprints were snapping to weird increments. Eventually, I decided to use the position values in the sidebar to manually set the x and y coordinates of the switches. I also moved the XIAO RP2040 to the right and the diodes further down for more room in the CAD. After finishing the cover plate, I modeled a simple knob for the rotary encoder.
Rewired part of PCB and worked on firmware. While looking at XIAO RP2040 diagrams, I realized that the SDA and SCL pins were not connected to the right spot. I swapped the connections for those pins and row 0 and row 1. I swapped out the switches in my CAD for the .STEP files in the official resources and spent some time defining the pins in the firmware.
Made animation for OLED and finished firmware. After creating a simple sprite animation in Krita and writing the QMK firmware (it took me hours to realize that the pin labels were GPIO numbers and match everything), my keymap.c file somehow deleted itself, skipping past the recycling bin, so I had to code it twice. I also stayed up until 11:30pm and used the next morning to debug the various causes of compiler errors. Many of them were just typos like missing a comma or forgetting a semicolon after an enum, but I had to just test which function actually worked for layer switching because all the others gave the error “this statement is not necessary” somewhere in the QMK code. As I was working on the GitHub repository, I realized that the screws were too short to go through my entire case, so I’ll have to redesign it next time.
Added screw holes to CAD, added better animations to firmware, and updated production files. I added holes to the HackPad case to fit the heatset inserts and modeled a simple placeholder part to act as a heatset insert in my CAD (to fix the problem of the screws being too short). I also added fillets to some edges and removed the holes on the cover plate (the plate would be held to the case by the heatset inserts). Since I wanted the OLED to be responsive to key presses, I decided to redesign the firmware to have each key fill in when pressed. To do this, I separated each sprite into individual animations and drew each animation separately on the screen by moving the origin, checking key presses to display different key animations....
|
1793735268.603994
|
1794340068.603994
|
|
67699
|
WarioWare Game by @lollmao98 | Stardance
|
lollmao98
|
0
|
3.62
|
0
|
[]
|
[{"post_id": 78751, "ts": "202 [{"post_id": 78751, "ts": "2026-10-11T14:22:58Z", "hours": 3.6153, "text": "step 13 so far"}]...
|
Title: WarioWare Game by @lollmao98 | Stardance
D Title: WarioWare Game by @lollmao98 | Stardance
Devlogs:
step 13 so far...
|
1793735269.8150065
|
1794340069.8150065
|
|
67700
|
skying game by @Davi89 | Stardance
|
Davi89
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: skying game by @Davi89 | Stardance
|
1793735270.7049859
|
1794340070.7049859
|
|
67701
|
My awesome macropad! by @tanilegehan | Stardance
|
tanilegehan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @tanilegehan | Star Title: My awesome macropad! by @tanilegehan | Stardance...
|
1793735271.5726643
|
1794340071.5726643
|
|
67702
|
Cli Based Portfolio by @Sami | Stardance
|
Sami
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cli Based Portfolio by @Sami | Stardance
|
1793735272.968934
|
1794340072.968934
|
|
67703
|
Robo panda by @ntpro9119 | Stardance
|
ntpro9119
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Robo panda by @ntpro9119 | Stardance
|
1793735273.8525279
|
1794340073.8525279
|
|
67704
|
playground by @seeyon | Stardance
|
seeyon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: playground by @seeyon | Stardance
|
1793735274.717441
|
1794340074.717441
|
|
67705
|
GO TO A WONDERFUL BLOG by @Jazil | Stardance
|
Jazil
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: GO TO A WONDERFUL BLOG by @Jazil | Stardanc Title: GO TO A WONDERFUL BLOG by @Jazil | Stardance...
|
1793735275.6122706
|
1794340075.6122706
|
|
67706
|
WarioWare Game by @TojiEthan | Stardance
|
TojiEthan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @TojiEthan | Stardance
|
1793735276.4916363
|
1794340076.4916363
|
|
67707
|
Gross BIling APP by @Dev_Ashwin444 | Stardance
|
Dev_Ashwin444
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Gross BIling APP by @Dev_Ashwin444 | Starda Title: Gross BIling APP by @Dev_Ashwin444 | Stardance...
|
1793735277.3976967
|
1794340077.3976967
|
|
67708
|
My first slack bot! by @Szyszka | Stardance
|
Szyszka
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Szyszka | Stardance
|
1793735278.2438014
|
1794340078.2438014
|
|
67709
|
An autonomous environment monitoring fixed-wing UA An autonomous environment monitoring fixed-wing UAV by @Kunal123star | Stardance...
|
Kunal123star
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: An autonomous environment monitoring fixed- Title: An autonomous environment monitoring fixed-wing UAV by @Kunal123star | Stardance...
|
1793735279.6124508
|
1794340079.6124508
|