|
15951
|
Airbus FCU Macropad by @samraat-756 | Stardance
|
samraat-756
|
0
|
1.12
|
0
|
[]
|
[{"post_id": 21310, "ts": "202 [{"post_id": 21310, "ts": "2026-07-03T05:20:42Z", "hours": 1.1175, "text": "Devlog: Building a Custom Airbus-FCU Macropad Total Build Time : 18 Hours, 45 Minutes Project Overview : This project was a multi-day journey to design, route, and program a custom Airbus-FCU macropad from scratch. Powered by a Raspberry Pi Pico, the board features 4 EC11 rotary encoders (with push-button functionality) and 6 Cherry MX switches. While heavily inspired by the A320 FCU for use in Microsoft Flight Simulator 2020 (via the Fly-By-Wire A32NX API), it’s also mapped to serve as a daily-driver productivity pad featuring media controls, zoom, and copy/paste functionality. Hardware & PCB Design (KiCad) : I originally planned to use an Epal Arduino Mega 2560 Pro Mini clone, but after falling down a rabbit hole trying to create a custom, dimensionally accurate footprint, I pivoted to the RP Pico. The Routing Grind : I spent hours meticulously mapping the tracks to ensure zero intersections while matching the physical layout of the real FCU (minus the displays due to size constraints). The “Oops” Moment : Right as I was moving to the firmware stage, I realized I completely forgot to wire the “B” pin for one of the encoders (EC8_B) to the microcontroller. I had to jump back into KiCad, route the missing pin, and re-lay the tracks to accommodate the fix. Enclosure & CAD (Fusion 360) : Autodesk Fusion 360 (an absolutely goated CAD program) was used to design the enclosure. I aimed for a minimalist aesthetic with clean, rounded edges. Fitment : A significant chunk of time went into troubleshooting physical tolerances—ensuring the top plate cutouts, the PCB, and the input hardware all sandwiched together perfectly. I also designed a custom window cutout in the case to keep the RP Pico visible. Engravings : I wanted neat text engravings to label each input. My initial font choice had overlapping geometry that broke the extrude tool, so I compensated by swapping to a simpler, cleaner font that rendered perfectly. Software & Firmware : I researched both MobiFlight and QMK MSYS to handle the brains of the board. MobiFlight’s recently updated UI introduced a bit of a learning curve since they moved away from a traditional text editor to a mouse-driven GUI. Ultimately, I used VS Code alongside QMK to write the firmware. The Code : I wrote out the keyboard.json and carefully matched the keymap.c file to handle my dual-purpose setup (Mute/Vol, Brightness, Zoom, Horizontal Nav, Next/Prev Track, and Copy/Paste). Compiler Woes : On the final day, I hit the dreaded QMK compiler errors when trying to generate the final .uf2 file. The culprit turned out to be an outdated keycode naming scheme I was using for the horizontal scrolling. Once I tracked down the correct syntax, the firmware compiled smoothly. Final Thoughts : Between re-routing traces, fixing geometry errors in CAD, and debugging C code, this build was a massive test of patience and problem-solving. The final result is a highly functional, dual-purpose sim and productivity tool packed into a sleek custom case!"}]...
|
Title: Airbus FCU Macropad by @samraat-756 | Stard Title: Airbus FCU Macropad by @samraat-756 | Stardance
Devlogs:
Devlog: Building a Custom Airbus-FCU Macropad Total Build Time : 18 Hours, 45 Minutes Project Overview : This project was a multi-day journey to design, route, and program a custom Airbus-FCU macropad from scratch. Powered by a Raspberry Pi Pico, the board features 4 EC11 rotary encoders (with push-button functionality) and 6 Cherry MX switches. While heavily inspired by the A320 FCU for use in Microsoft Flight Simulator 2020 (via the Fly-By-Wire A32NX API), it’s also mapped to serve as a daily-driver productivity pad featuring media controls, zoom, and copy/paste functionality. Hardware & PCB Design (KiCad) : I originally planned to use an Epal Arduino Mega 2560 Pro Mini clone, but after falling down a rabbit hole trying to create a custom, dimensionally accurate footprint, I pivoted to the RP Pico. The Routing Grind : I spent hours meticulously mapping the tracks to ensure zero intersections while matching the physical layout of the real FCU (minus the displays due to size constraints). The “Oops” Moment : Right as I was moving to the firmware stage, I realized I completely forgot to wire the “B” pin for one of the encoders (EC8_B) to the microcontroller. I had to jump back into KiCad, route the missing pin, and re-lay the tracks to accommodate the fix. Enclosure & CAD (Fusion 360) : Autodesk Fusion 360 (an absolutely goated CAD program) was used to design the enclosure. I aimed for a minimalist aesthetic with clean, rounded edges. Fitment : A significant chunk of time went into troubleshooting physical tolerances—ensuring the top plate cutouts, the PCB, and the input hardware all sandwiched together perfectly. I also designed a custom window cutout in the case to keep the RP Pico visible. Engravings : I wanted neat text engravings to label each input. My initial font choice had overlapping geometry that broke the extrude tool, so I compensated by swapping to a simpler, cleaner font that rendered perfectly. Software & Firmware : I researched both MobiFlight and QMK MSYS to handle the brains of the board. MobiFlight’s recently updated UI introduced a bit of a learning curve since they moved away from a traditional text editor to a mouse-driven GUI. Ultimately, I used VS Code alongside QMK to write the firmware. The Code : I wrote out the keyboard.json and carefully matched the keymap.c file to handle my dual-purpose setup (Mute/Vol, Brightness, Zoom, Horizontal Nav, Next/Prev Track, and Copy/Paste). Compiler Woes : On the final day, I hit the dreaded QMK compiler errors when trying to generate the final .uf2 file. The culprit turned out to be an outdated keycode naming scheme I was using for the horizontal scrolling. Once I tracked down the correct syntax, the firmware compiled smoothly. Final Thoughts : Between re-routing traces, fixing geometry errors in CAD, and debugging C code, this build was a massive test of patience and problem-solving. The final result is a highly functional, dual-purpose sim and productivity tool packed into a sleek custom case!...
|
1793551792.962615
|
1794156592.962615
|
|
15952
|
Chakraolio by @Chakradhar | Stardance
|
Chakradhar
|
0
|
3.47
|
0
|
[]
|
[{"post_id": 18295, "ts": "202 [{"post_id": 18295, "ts": "2026-06-29T12:16:46Z", "hours": 3.4683, "text": "Just finished designing the hero section of my page now trying to fix up main page and finished designing how the burger menu should look like."}]...
|
Title: Chakraolio by @Chakradhar | Stardance
Devl Title: Chakraolio by @Chakradhar | Stardance
Devlogs:
Just finished designing the hero section of my page now trying to fix up main page and finished designing how the burger menu should look like....
|
1793504868.2415829
|
1794109668.2415829
|
|
15953
|
Untitled by @Hippo | Stardance
|
Hippo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Hippo | Stardance
|
1793534062.2071986
|
1794138862.2071986
|
|
15954
|
My very own WebOS by @Harsh-UpPad | Stardance
|
Harsh-UpPad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Harsh-UpPad | Stardan Title: My very own WebOS by @Harsh-UpPad | Stardance...
|
1793198898.9349358
|
1793803698.9349358
|
|
15955
|
My very own WebOS by @shravanv | Stardance
|
shravanv
|
1
|
7.2
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-18T17:44:41Z", "hours": 6.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made my very own WebOS, with multiple apps and features. I added a calculator, a mock browser, and a camera. This is my first coding project that I have ever attempted and I am really proud of it.", "repo": "https://github.com/Shravan50/Star-dance-", "demo": "https://star-dance-ruby.vercel.app"}]...
|
[{"post_id": 18682, "ts": "202 [{"post_id": 18682, "ts": "2026-06-29T21:24:39Z", "hours": 1.2019, "text": "I just made the OS look better!!! I created a new drawing pad feature and made the OS look more futuristic and go along with the theme."}, {"post_id": 11399, "ts": "2026-06-18T17:42:53Z", "hours": 0.4367, "text": "This is my last devlog on this project and I will be moving onto my next step in learning coding. My journey will be tough but I will get there. In my last devlog, I fixed a lot of bugs that there were."}, {"post_id": 10826, "ts": "2026-06-17T19:27:06Z", "hours": 2.1256, "text": "I finally got more apps and fixed the camera on my WebOS. I’m learning more about HTML and Java integrations, especially through the .innerText command in Java. New features I added was a working calculator, it actually didn’t take that long because of the forums online guiding me through it. I also added a mock browser which doesn’t work, but its supposed to be like that because this OS is on a browser. I also fixed the Camera being non-centered as well as added the camera being automatically turned off. I added a new notes app which was really simple. These 2 hours were mostly centered around me learning and experimenting and encountering bugs that I wanted fix by myself. Added a name feature on the homescreen as well which personalizes the OS a little. That’s it for now, but I hope to learn much more in the coming days."}, {"post_id": 10297, "ts": "2026-06-16T22:51:45Z", "hours": 3.6428, "text": "I am working on a WebOS as this is my first time coding anything, I used HTML and Java to create this personalized in-browser experience. I made a camera app and some other quality of life improvements in the code. ~3 hours 30 mins were spent on mostly me learning the IDE and then figuring out debugging. Features: Working Camera: It isn’t centered yet, but it works. Time tracker: Has a clock"}]...
|
Title: My very own WebOS by @shravanv | Stardance
Title: My very own WebOS by @shravanv | Stardance
Devlogs:
I am working on a WebOS as this is my first time coding anything, I used HTML and Java to create this personalized in-browser experience. I made a camera app and some other quality of life improvements in the code. ~3 hours 30 mins were spent on mostly me learning the IDE and then figuring out debugging. Features: Working Camera: It isn’t centered yet, but it works. Time tracker: Has a clock
I finally got more apps and fixed the camera on my WebOS. I’m learning more about HTML and Java integrations, especially through the .innerText command in Java. New features I added was a working calculator, it actually didn’t take that long because of the forums online guiding me through it. I also added a mock browser which doesn’t work, but its supposed to be like that because this OS is on a browser. I also fixed the Camera being non-centered as well as added the camera being automatically turned off. I added a new notes app which was really simple. These 2 hours were mostly centered around me learning and experimenting and encountering bugs that I wanted fix by myself. Added a name feature on the homescreen as well which personalizes the OS a little. That’s it for now, but I hope to learn much more in the coming days.
This is my last devlog on this project and I will be moving onto my next step in learning coding. My journey will be tough but I will get there. In my last devlog, I fixed a lot of bugs that there were.
I just made the OS look better!!! I created a new drawing pad feature and made the OS look more futuristic and go along with the theme.
Ships:
I made my very own WebOS, with multiple apps and features. I added a calculator, a mock browser, and a camera. This is my first coding project that I have ever attempted and I am really proud of it....
|
1793663323.11792
|
1793749723.11792
|
|
15956
|
NostPad by @jaiagilan | Stardance
|
jaiagilan
|
0
|
1.15
|
0
|
[]
|
[{"post_id": 9056, "ts": "2026 [{"post_id": 9056, "ts": "2026-06-15T03:40:55Z", "hours": 1.1533, "text": "Finished the pcb!"}]...
|
Title: NostPad by @jaiagilan | Stardance
Devlogs: Title: NostPad by @jaiagilan | Stardance
Devlogs:
Finished the pcb!...
|
1793350341.157608
|
1793955141.157608
|
|
15957
|
MLSEP by @jb | Stardance
|
jb
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: MLSEP by @jb | Stardance
|
1793156196.736147
|
1793760996.736147
|
|
15958
|
My awesome macropad! by @brenna_pham | Stardance
|
brenna_pham
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @brenna_pham | Star Title: My awesome macropad! by @brenna_pham | Stardance...
|
1793372021.8309062
|
1793976821.8309062
|
|
15959
|
Arduino Trvia Helper by @jamespabbathi | Stardance
|
jamespabbathi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Arduino Trvia Helper by @jamespabbathi | St Title: Arduino Trvia Helper by @jamespabbathi | Stardance...
|
1793242465.0809107
|
1793847265.0809107
|
|
15960
|
My awesome macropad! by @jamespabbathi | Stardance
|
jamespabbathi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @jamespabbathi | St Title: My awesome macropad! by @jamespabbathi | Stardance...
|
1793174001.3064277
|
1793778801.3064277
|
|
15961
|
My awesome macropad! by @LittleAhsoka | Stardance
|
LittleAhsoka
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @LittleAhsoka | Sta Title: My awesome macropad! by @LittleAhsoka | Stardance...
|
1793562708.537193
|
1794167508.537193
|
|
15962
|
My very own WebOS by @junyic1 | Stardance
|
junyic1
|
0
|
0.53
|
0
|
[]
|
[{"post_id": 6816, "ts": "2026 [{"post_id": 6816, "ts": "2026-06-11T13:14:01Z", "hours": 0.5325, "text": "Trying out different text and css options, also trying to fix launch errors"}]...
|
Title: My very own WebOS by @junyic1 | Stardance
Title: My very own WebOS by @junyic1 | Stardance
Devlogs:
Trying out different text and css options, also trying to fix launch errors...
|
1793238638.3365397
|
1793843438.3365397
|
|
15963
|
My very own WebOS by @willw1034 | Stardance
|
willw1034
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @willw1034 | Stardance
|
1793242569.5394554
|
1793847369.5394554
|
|
15964
|
My very own WebOS by @Sophie_H | Stardance
|
Sophie_H
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Sophie_H | Stardance
|
1793267311.8449829
|
1793872111.8449829
|
|
15965
|
My first slack bot! by @yohonf | Stardance
|
yohonf
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @yohonf | Stardance
|
1793325174.623363
|
1793929974.623363
|
|
15966
|
My first slack bot! by @starfish08second | Stardan My first slack bot! by @starfish08second | Stardance...
|
starfish08second
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @starfish08second | Title: My first slack bot! by @starfish08second | Stardance...
|
1793425714.7482207
|
1794030514.7482207
|
|
15967
|
Niche Nightmare by @General_Delta | Stardance
|
General_Delta
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Niche Nightmare by @General_Delta | Stardan Title: Niche Nightmare by @General_Delta | Stardance...
|
1793162934.6289494
|
1793767734.6289494
|
|
15968
|
My very own WebOS by @lauren_shaddock | Stardance
|
lauren_shaddock
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @lauren_shaddock | Sta Title: My very own WebOS by @lauren_shaddock | Stardance...
|
1793346501.9305375
|
1793951301.9305375
|
|
15969
|
Tesseract by @crkalapat | Stardance
|
crkalapat
|
0
|
8.92
|
0
|
[]
|
[{"post_id": 18057, "ts": "202 [{"post_id": 18057, "ts": "2026-06-29T01:14:47Z", "hours": 1.7333, "text": "After a (very tragic) discovery that basically nobody online sells 2x9 or 2x10 JST connectors, I updated my schematic to use 2 1x10 or 1x9 JST XH connectors for the connections to the OLED display and RPI Zero 2W. I found footprints for all my symbols, finished the schematic, and started the PCB layout process. Turns out that JST sockets are pretty big (relatively speaking). I did some layout work, and now I have a rough sense of where everything will go (see pic below), but I still need to finalize all the positions in CAD so everything is precise and lines up. Although I wanted to keep the PCB as small as I could, something tells me that I might have to make it bigger to allow for more room and spacing for components."}, {"post_id": 16698, "ts": "2026-06-27T04:16:19Z", "hours": 1.6858, "text": "Decided to take a break from the CAD to focus on designing a PCB that will serve as a middle man between the Pi and the other electronics. I finished most of the schematic (still need to add LEDs), and had to do a fair share of datasheet reading in order to figure out what to wire to what. Right now the schematic has a speaker IC, two microphones, a display connector, a giant connector to the Raspberry Pi (which I plan to separate at the endpoint into individual wires), 4 push buttons, and lots of decoupling capacitors. I haven’t decided fully on footprints for some symbols (like the connectors), but I’m leaning right now towards JST connectors so that the inside of the cube is not a messy wire spaghetti. * Fingers crossed * this schematic doesn’t lead to me making a broken PCB."}, {"post_id": 15730, "ts": "2026-06-25T16:27:21Z", "hours": 1.6725, "text": "Moved the Raspberry Pi Zero 2W from being mounted on the ceiling to being mounted with standoffs above the speaker. In the process, I also modified the speaker mount that I made last time to use threaded inserts so the case could be 3D printed easier. After this, I wanted the cube to look better, so I added some cutouts on the sides for LEDs, buttons, and for the microphone. Finally, I ended this session by rounding all the corners ever so slightly with a 1mm fillet, so it won’t be as sharp to touch."}, {"post_id": 15147, "ts": "2026-06-24T16:37:38Z", "hours": 1.8372, "text": "I realized that I needed space to have rubber feet (so that the downward firing speaker’s audio isn’t muffled), so I had to redesign the speaker grill to be smaller. I added in some rubber feet once that was done and there was room. In the process, I also decided to use the rubber feet’s screws as a way to screw the display cover and the rest of the enclosure. Finally, I went on Mouser and found a pretty good fitting speaker for the case, and I mounted it inside the cube with some M3 screws and nuts."}, {"post_id": 14566, "ts": "2026-06-23T18:50:02Z", "hours": 1.9933, "text": "Started on the cube enclosure, and made a speaker grill for the bottom (since I want a downward firing speaker). I also made a slot for the square 1.9” OLED display that I plan to use, and tried to come up with a way to attach the display to the front with threaded inserts, but I didn’t end up figuring out a solution yet. I did however add holes for threaded inserts to hold down a Raspberry Pi Zero 2W, which will handle communication with cloud APIs. I had some trouble getting Lookout configured properly with my Stardance project (which is why this devlog is late), so I also journaled all my progress in the GitHub repo I created, just to be safe."}]...
|
Title: Tesseract by @crkalapat | Stardance
Devlog Title: Tesseract by @crkalapat | Stardance
Devlogs:
Started on the cube enclosure, and made a speaker grill for the bottom (since I want a downward firing speaker). I also made a slot for the square 1.9” OLED display that I plan to use, and tried to come up with a way to attach the display to the front with threaded inserts, but I didn’t end up figuring out a solution yet. I did however add holes for threaded inserts to hold down a Raspberry Pi Zero 2W, which will handle communication with cloud APIs. I had some trouble getting Lookout configured properly with my Stardance project (which is why this devlog is late), so I also journaled all my progress in the GitHub repo I created, just to be safe.
I realized that I needed space to have rubber feet (so that the downward firing speaker’s audio isn’t muffled), so I had to redesign the speaker grill to be smaller. I added in some rubber feet once that was done and there was room. In the process, I also decided to use the rubber feet’s screws as a way to screw the display cover and the rest of the enclosure. Finally, I went on Mouser and found a pretty good fitting speaker for the case, and I mounted it inside the cube with some M3 screws and nuts.
Moved the Raspberry Pi Zero 2W from being mounted on the ceiling to being mounted with standoffs above the speaker. In the process, I also modified the speaker mount that I made last time to use threaded inserts so the case could be 3D printed easier. After this, I wanted the cube to look better, so I added some cutouts on the sides for LEDs, buttons, and for the microphone. Finally, I ended this session by rounding all the corners ever so slightly with a 1mm fillet, so it won’t be as sharp to touch.
Decided to take a break from the CAD to focus on designing a PCB that will serve as a middle man between the Pi and the other electronics. I finished most of the schematic (still need to add LEDs), and had to do a fair share of datasheet reading in order to figure out what to wire to what. Right now the schematic has a speaker IC, two microphones, a display connector, a giant connector to the Raspberry Pi (which I plan to separate at the endpoint into individual wires), 4 push buttons, and lots of decoupling capacitors. I haven’t decided fully on footprints for some symbols (like the connectors), but I’m leaning right now towards JST connectors so that the inside of the cube is not a messy wire spaghetti. * Fingers crossed * this schematic doesn’t lead to me making a broken PCB.
After a (very tragic) discovery that basically nobody online sells 2x9 or 2x10 JST connectors, I updated my schematic to use 2 1x10 or 1x9 JST XH connectors for the connections to the OLED display and RPI Zero 2W. I found footprints for all my symbols, finished the schematic, and started the PCB layout process. Turns out that JST sockets are pretty big (relatively speaking). I did some layout work, and now I have a rough sense of where everything will go (see pic below), but I still need to finalize all the positions in CAD so everything is precise and lines up. Although I wanted to keep the PCB as small as I could, something tells me that I might have to make it bigger to allow for more room and spacing for components....
|
1793152569.6062403
|
1793757369.6062403
|
|
15970
|
My very own WebOS by @Jad_Alami | Stardance
|
Jad_Alami
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Jad_Alami | Stardance
|
1793504845.637716
|
1794109645.637716
|
|
15971
|
My very own WebOS by @piyushkancharapu | Stardance
|
piyushkancharapu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @piyushkancharapu | St Title: My very own WebOS by @piyushkancharapu | Stardance...
|
1793426079.9477317
|
1794030879.9477317
|
|
15972
|
Frictionless by @Jad_Al_Alami | Stardance
|
Jad_Al_Alami
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @Jad_Al_Alami | Stardance
|
1793256469.968655
|
1793861269.968655
|
|
15973
|
My very own WebOS by @Caluryth | Stardance
|
Caluryth
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Caluryth | Stardance
|
1793328509.283396
|
1793933309.283396
|
|
15974
|
My very own WebOS by @sophiasouza | Stardance
|
sophiasouza
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @sophiasouza | Stardan Title: My very own WebOS by @sophiasouza | Stardance...
|
1793519741.2260015
|
1794124541.2260015
|
|
15975
|
My very own WebOS by @xanderr | Stardance
|
xanderr
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @xanderr | Stardance
|
1793339584.2820437
|
1793944384.2820437
|
|
15976
|
My awesome macropad! by @Kimathman | Stardance
|
Kimathman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Kimathman | Starda Title: My awesome macropad! by @Kimathman | Stardance...
|
1793472812.6265306
|
1794077612.6265306
|
|
15977
|
My very own WebOS by @vedantvk | Stardance
|
vedantvk
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @vedantvk | Stardance
|
1793361419.7916973
|
1793966219.7916973
|
|
15978
|
My first slack bot! by @squiddy | Stardance
|
squiddy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @squiddy | Stardance
|
1793188520.1444972
|
1793793320.1444972
|
|
15979
|
My awesome macropad! by @aayan_patel0204 | Stardan My awesome macropad! by @aayan_patel0204 | Stardance...
|
aayan_patel0204
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @aayan_patel0204 | Title: My awesome macropad! by @aayan_patel0204 | Stardance...
|
1793552235.4214406
|
1794157035.4214406
|
|
15980
|
My very own WebOS by @aaravg772 | Stardance
|
aaravg772
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @aaravg772 | Stardance
|
1793231681.1873338
|
1793836481.1873338
|
|
15981
|
Frictionless by @amit_ | Stardance
|
amit_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @amit_ | Stardance
|
1793274463.8621027
|
1793879263.8621027
|
|
15982
|
My awesome macropad! by @stevesandoval9187 | Stard My awesome macropad! by @stevesandoval9187 | Stardance...
|
stevesandoval9187
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @stevesandoval9187 Title: My awesome macropad! by @stevesandoval9187 | Stardance...
|
1793242115.7342844
|
1793846915.7342844
|
|
15983
|
My very own WebOS by @Kimathman | Stardance
|
Kimathman
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Kimathman | Stardance
|
1793396898.223381
|
1794001698.223381
|
|
15984
|
C-level OS by @sarvesh | Stardance
|
sarvesh
|
0
|
0.86
|
0
|
[]
|
[{"post_id": 6625, "ts": "2026 [{"post_id": 6625, "ts": "2026-06-11T03:30:57Z", "hours": 0.8572, "text": "Coded a basic custom C kernal that maps text to VGA hardware memory and a startup file. I also managed to make a watch.sh script that automatically build the .bin file and push it inside a browser emulator using v86."}]...
|
Title: C-level OS by @sarvesh | Stardance
Devlogs Title: C-level OS by @sarvesh | Stardance
Devlogs:
Coded a basic custom C kernal that maps text to VGA hardware memory and a startup file. I also managed to make a watch.sh script that automatically build the .bin file and push it inside a browser emulator using v86....
|
1793490785.6550293
|
1794095585.6550293
|
|
15985
|
Orcapad by @Right_Bright | Stardance
|
Right_Bright
|
1
|
22.16
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-01T01:14:45Z", "hours": 19.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "This is Orcapad (I realized I should’ve probably done the initial ship a while ago)! Orcapad is built for Onshape, made by an Onshape fan. It features: An OLED with a dynamic LVGL-based GUI for keyboard layer info, and active RGB mode/color (when on the RGB keyboard layer) 8 keys for custom macros on each layer to streamline workflow 5 RGB LEDs forming a dynamically updating LED status bar 9 more RGB LEDs for vibes & looks! Orca theming because orcas are awesome This is the first project I’ve actually started & finished, from scratch, with so many first-times, and I loved* every part of it! *ignoring all the hours I spent withering in front of my computer because of silly mistakes TT", "repo": "https://github.com/Right-Bright/Orcapad", "demo": ""}]...
|
[{"post_id": 52749, "ts": "202 [{"post_id": 52749, "ts": "2026-08-23T02:36:56Z", "hours": 3.1617, "text": "Just wanted to say I didn’t mean to put the project back into the review queue… The parts are on the way and I’ll work on an actual demo when I get the parts"}, {"post_id": 36731, "ts": "2026-07-28T23:55:11Z", "hours": 10.9558, "text": "Updates QMK/Firmware It’s pretty much done (other than Raw HID)!! It compiles and passes all QMK Lint checks (which verifies compliance with licenses & QMK standards) LVGL Quick story time: Once upon a time I discovered LVGL through the QMK docs. QMK sent me to V8.2 of the LVGL docs. I said nu-uh and started using the newest version of LVGL. Fun twist: QMK uses V8.2 of LVGL :). Conclusion: I spent at least 4ish hours converting the code because some of the features I was using aren’t in LVGL V8.2 TT. Integration The actual integration was relatively easy, I basically just update certain variables regularly in QMK Compiling The only majorly annoying issue I dealt with while compiling was that LVGL re-defines PRINTF_SUPPORT_LONG_LONG after QMK without checking if it is already defined, so I had to play around with un-defining it in the right spot to fix the warning. There were of course also a plethora of other issues that I ironed out (such as compiling the custom font and images properly) :) ! Next Up! Raw HID"}, {"post_id": 29920, "ts": "2026-07-17T03:00:58Z", "hours": 10.8914, "text": "Updates LVGL GUI The GUI is pretty much all done! The changes are: the home screen now has two animated orcas spinning in circles! (I really really love this feature!) An RGB screen with: an rgb mode indicator/an rgb color indicator 3 live information labels with saturation, value (brightness), and hue/animation speed resized & repositioned layer & volume indicators from the home screen The rgb screen will switch between showing the current mode & animation speed, and color & hue. This allows me to use the space more effectively to show useful information. It took me a little bit of time to get the animation source images compiled properly, and I used Inkscape to make sure the original image downscaled and rotated while staying recognizable (and made a few adjustments in paint). Next QMK integration! I also want to properly set up my coding workspace to have autocomplete and all that for QMK."}, {"post_id": 27000, "ts": "2026-07-12T04:08:33Z", "hours": 16.9633, "text": "Updates LVGL Simulator It took me at least 2 days to get the lvgl simulator working TT. I settled on Visual Studio (also tried Codeblocks and VSCode) because it worked for demos, but it took me forever to get my own code running. TLDR I turned of a setting and it broke it… I just needed to add: lv_delay_ms(lv_timer_handler()); lv_refr_now(NULL); It worked immediately :) Lets just say it was a very bittersweet moment GUI Progress I have the home screen pretty much done, and I’m starting to feel very comfortable coding in LVGL! So far I have: infinite scroll list to show active layer (still need to apply style for the active one) -Has circular scrolling, which took quite some trial and error. I was doing a very roundabout way with manual calculations to get nice animated snapping. But I learned about flags and now the active layer’s button is flagged, which made everything much easier! volume slider (still deciding on it as I would need to mess with Raw HID for it) FYI: The buttons in the GIF are just to test out & showcase how I plan to integrate the layer indicator in QMK Next create RGB info screen actually integrate into QMK"}, {"post_id": 15938, "ts": "2026-06-25T21:52:43Z", "hours": 7.6339, "text": "I have quite a few QMK firmware developments! First off, I am quite amateur at programming, and I’ve never touched C before. So, there have been a lot of new things to learn, which is really good because I’ve been meaning to get more familiar with programming and different languages. Also, I finally decided that I was going to create the Orcapad to streamline my Onshape workflow by populating it with shortcuts. Ok, so currently I have: 4 keyboard layers (three for shortcuts, one for the lEDs) RGB light layers so that I can easily change the LED bar to indicate what layer is on 2 custom keycodes (one to cycle through layers, one to cycle through static RBG colors) An encoder map to simplify customizing it Hopefully all that is set and I don’t have to fix anything :) :) :) :) To be added I still need to add support for the OLED screen, and on that note, I decided to dive into LVGL so I could create a more sophisticated user experience (over standard quantum painter and the basic functionality), and (again) to really help me get more familiar with C. Finishing thoughts :) So far my experience has surprisingly not been too painful, just very time consuming, but for all I know none of what I’ve written so far works TT. Very excited about how its turning out so far though!"}, {"post_id": 10724, "ts": "2026-06-17T16:21:48Z", "hours": 5.8586, "text": "Since my last devlog, I realized that I connected part of the keyboard matrix to the 3.3v output pin, so I had to update the PCB once again (and remove one of the keys since I didn’t have enough pins…again). The PCB is finally completely finished!! I also have a good chunk of the CAD for the case done :). For the case I have 3 printed layers, the bottom that holds the PCB, a middle diffusion layer for the LEDs (just a very thin layer of white PLA that I hope will look nice), and the top layer to make sure everything can be assembled easily. Up next: add finishing touches to the case, add mounting hardware/interface, introduce myself to QMK for the firmware."}, {"post_id": 8498, "ts": "2026-06-14T03:57:16Z", "hours": 5.815, "text": "Long overdue devlog, but tldr: I finished the schematic for the PCB and just about finished the layout and tracing of the board! I essentially worked on the PCB over two days, so the first day I was getting oriented with general PCB design (this is my first PCB), KiCad, keyboard matrixes, etc… For some reason it took me some time to get used to footprints/symbols/and libraries and how to assign them properly, but I got around to it! I also realized I had to get rid of one of my planned rotary encoders because I didn’t have enough pins for it. Then on the second day, I organized the PCB and completed the tracing. Halfway through I decided to add LEDs to the top of every key switch for aesthetics, and to add some more complexity for me. Overall I enjoyed designing it a lot more than I expected to, which was a pleasant surprise. Next up: touch up the PCB (ground fill, rounded corners, silkscreen decor…), and start on the CAD for the case."}]...
|
Title: Orcapad by @Right_Bright | Stardance
Devlo Title: Orcapad by @Right_Bright | Stardance
Devlogs:
Long overdue devlog, but tldr: I finished the schematic for the PCB and just about finished the layout and tracing of the board! I essentially worked on the PCB over two days, so the first day I was getting oriented with general PCB design (this is my first PCB), KiCad, keyboard matrixes, etc… For some reason it took me some time to get used to footprints/symbols/and libraries and how to assign them properly, but I got around to it! I also realized I had to get rid of one of my planned rotary encoders because I didn’t have enough pins for it. Then on the second day, I organized the PCB and completed the tracing. Halfway through I decided to add LEDs to the top of every key switch for aesthetics, and to add some more complexity for me. Overall I enjoyed designing it a lot more than I expected to, which was a pleasant surprise. Next up: touch up the PCB (ground fill, rounded corners, silkscreen decor…), and start on the CAD for the case.
Since my last devlog, I realized that I connected part of the keyboard matrix to the 3.3v output pin, so I had to update the PCB once again (and remove one of the keys since I didn’t have enough pins…again). The PCB is finally completely finished!! I also have a good chunk of the CAD for the case done :). For the case I have 3 printed layers, the bottom that holds the PCB, a middle diffusion layer for the LEDs (just a very thin layer of white PLA that I hope will look nice), and the top layer to make sure everything can be assembled easily. Up next: add finishing touches to the case, add mounting hardware/interface, introduce myself to QMK for the firmware.
I have quite a few QMK firmware developments! First off, I am quite amateur at programming, and I’ve never touched C before. So, there have been a lot of new things to learn, which is really good because I’ve been meaning to get more familiar with programming and different languages. Also, I finally decided that I was going to create the Orcapad to streamline my Onshape workflow by populating it with shortcuts. Ok, so currently I have: 4 keyboard layers (three for shortcuts, one for the lEDs) RGB light layers so that I can easily change the LED bar to indicate what layer is on 2 custom keycodes (one to cycle through layers, one to cycle through static RBG colors) An encoder map to simplify customizing it Hopefully all that is set and I don’t have to fix anything :) :) :) :) To be added I still need to add support for the OLED screen, and on that note, I decided to dive into LVGL so I could create a more sophisticated user experience (over standard quantum painter and the basic functionality), and (again) to really help me get more familiar with C. Finishing thoughts :) So far my experience has surprisingly not been too painful, just very time consuming, but for all I know none of what I’ve written so far works TT. Very excited about how its turning out so far though!
Updates LVGL Simulator It took me at least 2 days to get the lvgl simulator working TT. I settled on Visual Studio (also tried Codeblocks and VSCode) because it worked for demos, but it took me forever to get my own code running. TLDR I turned of a setting and it broke it… I just needed to add: lv_delay_ms(lv_timer_handler()); lv_refr_now(NULL); It worked immediately :) Lets just say it was a very bittersweet moment GUI Progress I have the home screen pretty much done, and I’m starting to feel very comfortable coding in LVGL! So far I have: infinite scroll list to show active layer (still need to apply style for the active one) -Has circular scrolling, which took quite some trial and error. I was doing a very roundabout way with manual calculations to get nice animated snapping. But I learned about flags and now the active layer’s button is flagged, which made everything much easier! volume slider (still deciding on it as I would need to mess with Raw HID for it) FYI: The buttons in the GIF are just to test out & showcase how I plan to integrate the layer indicator in QMK Next create RGB info screen actually integrate into QMK
Updates LVGL GUI The GUI is pretty much all done! The changes are: the home screen now has two animated orcas spinning in circles! (I really really love this feature!) An RGB screen with: an rgb mode indicator/an rgb color indicator 3 live information labels with saturation, value (brightness), and hue/animation speed resized & repositioned layer & volume indicators from the home screen The rgb screen will switch between showing the current mode & animation speed, and color & hue. This allows me to use the space more effectively to show useful information. It took me a little bit of time to get the animation source images compiled properly, and I used Inkscape to make sure the original image downscaled and rotated while staying recognizable (and made a few adjustments in paint). Next QMK integration! I also want to properly set up my coding workspace to have autocomplete and all that for QMK.
Updates QMK/Firmware It’s pretty much done (other than Raw HID)!! It compiles and passes all QMK Lint checks (which verifies compliance with licenses & QMK standards) LVGL Quick story time: Once upon a time I discovered LVGL through the QMK docs. QMK sent me to V8.2 of the LVGL docs. I said nu-uh and started using the newest version of LVGL. Fun twist: QMK uses V8.2 of LVGL :). Conclusion: I spent at least 4ish hours converting the code because some of the features I was using aren’t in LVGL V8.2 TT. Integration The actual integration was relatively easy, I basically just update certain variables regularly in QMK Compiling The only majorly annoying issue I dealt with while compiling was that LVGL re-defines PRINTF_SUPPORT_LONG_LONG after QMK without checking if it is already defined, so I had to play around with un-defining it in the right spot to fix the warning. There were of course also a plethora of other issues that I ironed out (such as compiling the custom font and images properly) :) ! Next Up! Raw HID
Just wanted to say I didn’t mean to put the project back into the review queue… The parts are on the way and I’ll work on an actual demo when I get the parts
Ships:
This is Orcapad (I realized I should’ve probably done the initial ship a while ago)! Orcapad is built for Onshape, made by an Onshape fan. It features: An OLED with a dynamic LVGL-based GUI for keyboard layer info, and active RGB mode/color (when on the RGB keyboard layer) 8 keys for custom macros on each layer to streamline workflow 5 RGB LEDs forming a dynamically updating LED status bar 9 more RGB LEDs for vibes & looks! Orca theming because orcas are awesome This is the first project I’ve actually started & finished, from scratch, with so many first-times, and I loved* every part of it! *ignoring all the hours I spent withering in front of my computer because of silly mistakes TT...
|
1793720844.4788055
|
1793807244.4788055
|
|
15986
|
Frictionless by @parijaatdhruv | Stardance
|
parijaatdhruv
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @parijaatdhruv | Stardance
|
1793177465.982542
|
1793782265.982542
|
|
15987
|
My awesome macropad! by @thad | Stardance
|
thad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @thad | Stardance
|
1793408020.4553213
|
1794012820.4553213
|
|
15988
|
Untitled project by @Rhys | Stardance
|
Rhys
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Rhys | Stardance
|
1793296333.63964
|
1793901133.63964
|
|
15989
|
Cognitive Care Assistant by @CORBIN | Stardance
|
CORBIN
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Cognitive Care Assistant by @CORBIN | Stard Title: Cognitive Care Assistant by @CORBIN | Stardance...
|
1793231510.7182467
|
1793836310.7182467
|
|
15990
|
My awesome macropad! by @Vickie | Stardance
|
Vickie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Vickie | Stardance
|
1793562896.7059534
|
1794167696.7059534
|
|
15991
|
My very own WebOS by @Sudsy | Stardance
|
Sudsy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Sudsy | Stardance
|
1793407659.9318256
|
1794012459.9318256
|
|
15992
|
My first slack bot! by @Aadineer | Stardance
|
Aadineer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Aadineer | Stardanc Title: My first slack bot! by @Aadineer | Stardance...
|
1792925430.9000106
|
1793789430.9000106
|
|
15993
|
Frictionless by @nalinasraden857 | Stardance
|
nalinasraden857
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @nalinasraden857 | Stardanc Title: Frictionless by @nalinasraden857 | Stardance...
|
1793159402.516368
|
1793764202.516368
|
|
15994
|
My first slack bot! by @ilya1 | Stardance
|
ilya1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @ilya1 | Stardance
|
1793198980.5713832
|
1793803780.5713832
|
|
15995
|
AI Roblox Clothing Gen by @Saqib | Stardance
|
Saqib
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AI Roblox Clothing Gen by @Saqib | Stardanc Title: AI Roblox Clothing Gen by @Saqib | Stardance...
|
1793231650.9155672
|
1793836450.9155672
|
|
15996
|
My very own WebOS by @Synxed | Stardance
|
Synxed
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Synxed | Stardance
|
1793465374.6875825
|
1794070174.6875825
|
|
15997
|
My awesome macropad! by @radherpatel | Stardance
|
radherpatel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @radherpatel | Star Title: My awesome macropad! by @radherpatel | Stardance...
|
1793508902.9688025
|
1794113702.9688025
|
|
15998
|
Parrallax by @Caluryth | Stardance
|
Caluryth
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Parrallax by @Caluryth | Stardance
|
1793472718.508932
|
1794077518.508932
|
|
15999
|
My awesome macropad! by @achu | Stardance
|
achu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @achu | Stardance
|
1793270932.6148129
|
1793875732.6148129
|
|
16000
|
My very own WebOS by @TheAstrophysicistHaidy | Sta My very own WebOS by @TheAstrophysicistHaidy | Stardance...
|
TheAstrophysicistHaidy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @TheAstrophysicistHaid Title: My very own WebOS by @TheAstrophysicistHaidy | Stardance...
|
1793534101.0518515
|
1794138901.0518515
|