|
19306
|
SmasherGS by @parkerrupe | Stardance
|
parkerrupe
|
0
|
71.63
|
0
|
[]
|
[{"post_id": 78628, "ts": "202 [{"post_id": 78628, "ts": "2026-08-31T00:40:37Z", "hours": 1.1333, "text": "I worked on preparing for shipping this project. I made most of the BOM, took some renders, did some Github Repo formatting. I am so ready to be done with this project but I am worried about budget as my PCB is rather expensive with tariffs/shipping. Maybe I reach out to PCBway for a sponsorship or something. Ugh, I don’t know. Anyways, peep the cool render."}, {"post_id": 78627, "ts": "2026-08-14T00:00:00Z", "hours": 3.0, "text": "Final CAD touches. Wow. That went quick. This is the final cad entry though. First things first, I had to split the casing into two sections that would fit on my printer. These sections would be joined with M3 bolts and heat set inserts. This is a simple overlapping butt joint with 4 screws per side. Nothing complex, was just a few sketch and extrudes. Next was building up interior structure, which you can see part of in that screenshot. I basically just needed mounting for the screen and board. This is what I came up with. I also added the port cuouts on the side while I was at it. This one interior strucutre has mounting holes for both the screen and the lattepanda carrier PCB. Here is the other side. Unfortunately, this will need supports to print, as I couldn’t think of a way to avoid them, which hurts me. But it is what it is, I will make do. Here is the interior with the components. Looks good! Lastly, I added 4 antennas. That’s right, 4. One is on the inside in this corner! The square one internally is a GPS antenna. It is a ceramic active patch antenna. The other 3 antennas are simple “rubber ducky” antennas for Wifi+Bluetooth and LORAWAN. Short and simple. That’s it for cad! Now I just need to take renders and put the repo together with a BOM and stuff! Wait, I forgot screws. Now we good. I also added slits to the back for cooling! They will just be lasercut into the aluminum. Okay, alll done for real this time. Now we move on to renders and stuff."}, {"post_id": 78626, "ts": "2026-07-22T00:00:00Z", "hours": 4.0, "text": "CAD!! CAD CAD CAD!! I love CAD. Ok, first things first, I exported the Mu carrier board 3D model and imported it into Fusion 360. I needed to add the M.2 accessories and standoffs for the M.2 and Mu stuff. This was fairly straightforward. The standoffs are M2 x 1.5mm and I used M2 pan head phillips screws as those are typically what M.2 hardware kits include. For the M.2 accessories, we have a full size NVME drive and a half size NVME wifi/bluetooth card. These are lines up to the best of my abilities but may be a smidge off. Thankfully, they are just cosmetic, so it does not matter much at all. Anywho, next up. I started laying things out in CAD for the actual deck. I am going for a minimalist flat slab with a metallic top/bottom panel sandwiching a printed frame. So, that’s what I am laying out! You may have noticed (you probably didn’t) that the keyboard usb port/buttons/etc are now on the bottom of the PCB. This is no mistake! I realized I made a bit of an oopsie - the only way a top plate can fit with choc switches is if all that good stuff is on the bottom. Ugh. So, I flipped those components to the other side of my PCB. This required me to reroute a large portion of the matrix (half of it) and all the traces connecting the matrix to the MCU. As you can see in the photo, all the keyswitch footprints are on the bottom now. Flipped. Anywho, with that out of the way, I could now move on to developing the case. First was the top plate. This is a 1.2mm aluminum lasercut plate that I will be getting anodized Red to contrast the Black 3D printed mainframe. I started by making the keyswitch grid. This is a 17.5x18.5mm spaced 12x5 grid of 13.5x13.5mm squares. Quite a mouthfull. The choc switches snap into this plate nicely, and it serves as a structural point of rigidity. From there it gets extended, and the cyberdeck is starting to look like something! I initially went for this clean look where there was no border around the screen besides the one built into the screen - this would later change, but thats for later. I then started building up the black casing. I am targeting 40mm thickness for the printed portion. Which is fairly thick, but it kinda has to be for the lattepanda mu fan stuff to fit. This has a lip for the keyboard pcb to rest on and mounting holes for the keyboard pcb. I will later add bracing under more of the keyboard pcb but for now I am focused on the outermost shell. It then gets extended under the screen! Man, it’s looking awesome. However, it was at this point that I remembered - hey, the ports for my screen are on the outer edge! How would the cables reach the interior with the ports on the exterior…. They wouldn’t. So, it gets extended! Bam. I actually like how the red border ties it all together and think this still looks awesome! Albeit bigger, but that’s ok. At this point I also added a flat back panel to finish the sandwich. This will ultimately have screw holes and ventilation in it, but for now it can stay flat. That’s all for this entry actually! I made a lot of cad progress, but as you may have noticed this entry took a while to get posted. That’s because I went to OutPost IRL! It was a life changing event and I had so much fun. It was so awesome. Anywho. What’s next? Literally just fleshing out the casing. I need to: Add cutouts for the I/O ports Add internal structure/Skeleton Add ventilation/Fans Add Battery Split part into smaller printable sections And then submit! I am getting so close!!!"}, {"post_id": 78625, "ts": "2026-07-07T00:00:00Z", "hours": 3.5, "text": "Low speed routing, mounting holes… we are done!!! As the title of this entry suggests, this is the last entry of pcb design. I routed all the low speed traces, which was the only thing left. Besides mounting holes, which I did afterwards. I started at the top left for this and worked my way clockwise around the board. Mostly. At some point I couldn’t keep track of what needed routed so I was just following what DRC said needed routed, working my way down the list. I started doing that about halfway through. This sucked. I had to bob and weave and sneak my way around all the high speed traces, ensuring proper spacing to minimize cross talk and keep trace impedance correct. Having gnd pours or traces close to the high impedance traces changes impedance because of uhh… parasitic capacitance I think? Electromagnetic fields inducing inductance and capacitance. Something like that. Anywho, lets see it! Look at all that spaghetti. I had to route some traces on my power plane it was getting so busy! Good thing I named it power/aux signal. This is the board with gnd pours on top/bottom. The pours are offset 1mm from all traces, which should be enough to protect the high speed. Here’s the signal layer. Yes, I did route some diff pairs on this layer. They are usb 2.0 and do not care. This is my power/aux sig layer. Mostly big ol power traces and pours, but there are a few signals mixed in that I just couldn’t get to route well on other layers. And those are the GND planes! With that, we have a finished board! Well almost. It needs a bit of silkscreen. That’s better. You can also see the mounting holes in that photo! I just used EasyEDA’s Pad feature to add pads with an OD of 5.8mm and an ID of 3.2mm. Should perfectly match M3 socket head screws. So. Where do we go from here? It’s cad time. I LOVE cad time. I need to physically design the deck itself! Which means exporting the 3D models of my pcbs, modeling out the screen, modeling a case, modeling all the internals, etc. This is the fun part!! Pcbs are NOT the fun part. So… CAD soon!!"}, {"post_id": 78623, "ts": "2026-07-06T00:00:00Z", "hours": 3.0, "text": "So. I did the pcie ports. This was a doozy. So for my 3V3 setup for this board, I have a 500ma LDO. Because I don’t have much 3V3. I thought. Fun fact - M.2 SSDs draw up to 3 amps. Uh oh. 3 amps??? That’s insane! So, I initially was just adding a 6a circuit. I got that all sorted. Turns out, this needs 2oz copper. I am not doing 2oz copper. That is expensive. So I switched. Each m.2 gets its own 3V3 3A circuit. Not actually that complex! Just annoying. It was at this point that I also realized I had both M.2 on the same PCIE lines. This does not work. So, I had to delete ethernet to get another pcie set. This is fine. I was never really going to use it if we’re being honest and it lets me make the whole board much smaller to get rid of it. The board is like, 120mm wide now! In that photo you can also see the completed M.2 circuits. Each one has a power circuit tapping into the main 12v, and some passives for stuff like filtering high speed lines and a status LED - one per M.2. Here are some closeups! The circuits off to the side of each port are the power circuits. The bottom left two components are the status LEDs, and the top right two components are filtering capacitors for high speed lines. With those updates, the board is now ready to hook up all the high speed pairs to the mu! After that I get to do low speed, power routing, and be done! Woooo. I am so ready to be done with this pcb."}, {"post_id": 78624, "ts": "2026-07-06T00:00:00Z", "hours": 2.0, "text": "High speed routing!! I connected everything up to the Mu. This sucked. Things kept overlapping and it was so bleh. I started in the top right with USBC and worked down and to the left. Well. I actually started with the m.2 because they are right next to the Mu, and then went top right to bottom left. It was at this point that I felt like something might be off. Why would the pins for one HDMI port be backwards but not for the other? The answer was simple: I had the pins wrong. Oops. Once I fixed that I could line up everything real nice. But first, after a tip from a friend, I dropped the USBC lines down to the bottom layer so that everything else could be top. This made it so much cleaner looking. SO much better. I am a little worried about EMI from the buck converters but I think it might be ok? I’ll add a bunch of GND vias or something. After I had those all wired up, I did the last few small circuits. LORAWAN. GPS, with the antenna keepout. The power switch. The fans. And last, but certainly not least, the CMOS battery. And with that, all the individual circuits are complete. So what’s left? I literally just have to connect all the low speed lines up to the Mu, and I am done. This is no small task, as I have to weave around and through all the high speed lines, but it is very possible. It will get done soon."}, {"post_id": 78622, "ts": "2026-07-01T00:00:00Z", "hours": 3.0, "text": "I routed the second hdmi port and the ethernet port! HDMI was super straight forward, just a copy of the other one rotated 90 degrees. Did take me a second to remember what I did but I got it done. Next was ethernet. I had no idea what I was doing for this but here we go. I started connecting the diff pairs of the connector to my ethernet controller. This converts the ethernet junk to PCIE for my Mu to deal with. All length matched, impedance matched to 100 ohms, spaced out properly, ESD filtering, etc. All sorts of nonsense. It was at this point, when I went to wire the passives for my ethernet controller that I realized - hey, this needs 1v0. I don’t have 1v0 in my power circuit. Time to speedrun a power circuit. Ready… Set… Go!! I started by pulling up TI WeBench to get a power circuit schematic. I inputed 1v and 500ma and it outputted a couple options. I picked the first one, the cheapest. It gave me this. I used it to make: This. Identical circuit, just some pins moved on the symbol. I threw this onto the Ethernet page because my Power page is full, and because this is gonna be near the ethernet connector as I don’t trust the 1v to survive a path across the board. Just in case. After that, I synced the schematic to my pcb, and threw together the circuit on board. Stupid simple, so it’s stupid reliable. Boom. Power circuit done. With that fixed I could go back to adding all the passives and power hookups for my ethernet controller. Bam. Done. This thing has so many power hookups, it’s unreal. 4 different pins get 1v0, 3 different pins get 3v3. That’s 7 pins. Wtf. It’s ok though, I got it done. I did have to route decoupling internally for a couple pins just because they got placed next to high speed pairs for some reason (stupid placement realtek. stupid placement.). I think if I do this again I will use a TI IC for ethernet because the realtek documentation is mid and 1v0 is stupid. Give me 3v3 and 5v like a sane person. Anywho, with that done, all the ports on the board are wired. Yup. All of them. HUGE progress. But - what do I have left? m.2 slots CMOS battery fans gps lorawan final power routing (5v and 3v3) final signal routing (hook it all up to the mu) That’s it! Only 7 things on my checklist. M.2 slots are more diff pairs because of course they are, but after that it’s smooth sailing stupid logic until the final signal routing. And even then, that is partially stupid logic too (high speed = smart logic, low speed = stupid logic). I guess I’ll tackle M.2 next? TBD."}, {"post_id": 78620, "ts": "2026-06-30T00:00:00Z", "hours": 2.5, "text": "I routed 1 hdmi port and 4 usba 2.0 ports! I am making solid progress! First was hdmi. This required defining a new differential pair rule for 100 ohms instead of 90 ohms (usb spec). Easy enough. That’s the rule. Anywho. HDMI has a pretty interesting circuit on it actually. When the device goes to sleep or shuts off, it pulls all the hdmi lines to gnd with a mosfet. I always thought the way computers did sleep for hdmi was something way fancier but no. It literally just shunts the signal to gnd. Pretty neat in my opinion! That’s the big circuit with resistors on the left. All into a mosfet that triggers with sleep or shutdown. The sls_s0 operates that way - only active (low) when the device is in use. Recreating this was a bit of a hassle honestly and really made me think. But I got it figured out in the end. From right to left it goes connector, ESD diodes, resistors, and then ac filtering capacitors. AC filtering capacitors ugh. Doesn’t that sound like it should filter out AC? But actually, they work by blocking DC and only letting AC through. I think that should be named DC filtering but idk I ain’t no electrician. Rant aside, those resistors will get connected to a common line in the signal layer (layer 3) and then to a mosfet. Next was an I2C level shift. The HDMI side of the I2C lines operate on 5 volt while my device side operates on 3 volt. So, I use a little IC to handle the level shift and make sure my data stays clean. Did you know there is I2C in HDMI? I sure didn’t, but it is fascinating. Basically, the I2C lines are how your device figures things out like screen size, resolution, refresh rate, color profiles, etc. Basically, it is how the device and screen “talk” about what each is capable of and what they need from eachother. Over I2C! I’ve personally seen 30 foot hdmi cables. You’re telling me I2C lines can be 30 feet long without issue?? Wow. Fascinating stuff. Second rant aside, the next circuit was my hot plug detection and 5v power. This is the last bit. These just get lumped together because the pins are together. 5V is on the very left with the rectangle thing, that’s a diode. Everything to the right of that is hot plug detect. It basically tells my device that a screen was unplugged/plugged in while my device was on so that it knows to reconfigure everything. Pretty neat. That’s a full hdmi port! It looks like this: Next was the USB ports. One is external and the other three are internal. They are all basically carbon copies save for two of the internal ones sharing an ESD diode module just because they can and I want to cut down on components. They all get ESD filtering on the data pair, plus a fuse and decoupling capacitor on the 5V power line. That way an overcurrent blows the fuse and not my whole board. That’s it for this entry! I am on a roll today and honestly may not sleep for a while to just keep going. Or I will. I don’t know, it’s late. Next is the second HDMI port and the Ethernet port. Not sure which will come first. Probably HDMI since I know how to do it."}, {"post_id": 78621, "ts": "2026-06-30T00:00:00Z", "hours": 3.5, "text": "The second usbc port! I have decided that differential pairs are my greatest enemy. Truly, this is miserable I worked from the “bottom” up, routing traces through their passives in impedance and length matched pairs. This worked surprisingly well and I ran into minimal issues. Something cool I was able to do was go back and use open channels on existing ESD diodes rather than adding more. Specifically, that one at the top. It had one pair from the first usbc port, and now has a pair from the second port. Since they both had to be routed around the plug legs like that, they end up in the same spot. RX lines get just resistors while TX lines get capacitors and resistors. That’s what the smaller passives are on two of the lines - capacitors. Once I had those 4 lines routed, I get to route the less crucial lines. There’s still a diff pair in these ones, but since it’s usb 2.0, it is way less important where that bad boy goes. It’s lower speed. Higher speed = more fragile = more important. For these routing I had to add the other chips necessary for the port. One for protecting vbus shorts and one for connecting vbus to 5 volt, since this port needs to be a power source, not just a sink. That way it can power other devices. This is what those vbus lines look like. They will be connected to 5v ultimately, but I have yet to route 5v. Soon. With a couple more traces, I had this USBC port complete. This one is a mess. And it was super tedious as always. But after this I get to route just some nice chill usb 2.0 as a break before I route HDMI. Hdmi has waay more passives on the diff pairs for some reason. HDMI and Ethernet also mean I get to deal with writing new differential pair rules as these have different impedances from USBC. Anywho, here’s both usbc ports together. It’s really getting busy in here! Can’t wait to add more. On the logistics side of things, I got approved for super hardware builder for Outpost aswell as got my flight stipends approved. That means I am going to Open Sauce/Outpost! I need to finish this project by July 7 to truly “qualify”, though if I already have flights… I’m not worried, I’ll get it done in time."}, {"post_id": 78618, "ts": "2026-06-29T00:00:00Z", "hours": 4.0, "text": "Power circuitry! I wasn’t sure where to start and I certainly didn’t want to start with any highspeed routing. So, we are doing the power circuit first. I started with simply just… trying to get everything connected and compact. This would prove harder than I anticipated. It’s a big mess honestly. I was working without ratlines so that I can actually see what I am doing, and that means I forgot some components. So it actually just got worse for a bit. The big thick trace is 12v main power. This is up to like, 35 watts, so it needs to be super big. Hence the 3mm wide trace. We have roughly: Bottom is 5v. Top middle is 12v. Top right is battery charger. You can kinda see the ICs buried in there. Those are the focal points. The very first thing I did to make this better was move 5v. I realized there’s no reason it needs to be so smushed in there. So, it gets scooted over to the left. Much better. Zooming in on 5v… I did some rearranging to make it less wonky and added the components I had forgotten - mainly decoupling caps. I am really good at forgetting decoupling caps. Since 5v is the main power for the system besides 12v for the mu, it gets a big big decoupling cap. That’s the big thing on the left. There are actually three ICs in here. One is the 5v buck converter, one is the 5v load switch for the system, and one is the 3v3 LDO. I completely forgot 3v3 is in there! Not that it’s easy to tell. This is the current state of the power circuitry. We have from left to right: 5v and 3v3, 12v, battery charger, and charger EEPROM. Plus the battery and thermistor connectors. Here is a view of the internal power layer. I used a mix of wide traces and copper pours for this so that I can guarantee my traces are wide enough. I also used multiple vias for connections in a lot of spots to give more “wire” for the power to go over. It’s way less of a mess now than when we started, and it was annoying to get to this point. I am still not sure if I am super happy with it, but I think it is good enough for now. I still need to wire up the i2c control, but that requires the USBC PD controller be wired. And I haven’t gotten that far yet. I think that will be next? Though I may need to route some high speed traces first so I know what I am working around. Not totally sure, I’ll probably ask one of my smarter PCB friends what to do. I am gonna get this done, whether through perserverance or straight up spite."}, {"post_id": 78619, "ts": "2026-06-29T00:00:00Z", "hours": 4.5, "text": "Power circuitry and some usbc 3.2. So. High speed routing is probably what I hate most in the world right now. It’s so annoying, it’s all diff pairs, you gotta be so careful. Bleh. Impedance and length matching. Bleh. Regardless, I started routing the very first usbc port just because I have to work around it’s traces. This took an hour. This. It’s 8 trace routes. Although because of how easyeda works it’s split into like 16 different configured differential pairs. Each one needs the rules assigned to tell it spacing and width. Then I had to actually route them. TX lines are supposed to get their passives closer to the USBC port while RX lines get it closer to the device, but both kinda got it in the middle because of how the spacing works out. Oh, and they all get piped through ESD diodes. Then I had to length match them within like, 0.1mm. Blehh. After that I worked more on power circuitry. I needed to route I2C lines within the power circuitry so that the ICs could talk to eachother, as well as add more passives that I had forgotten. Mostly decoupling. I also shifted the VBUS line down so I would have room to wire 5v and 3v3 to all the ICs crammed in there. Before that they were all kinda blocked on my power plane, which defeats the point of a power plane. More on usbc. I had to change nets (pins) a bunch in my schematic to get this to work because I needed them to line up with the physical pin and component locations so I wasn’t crossing paths or anything. While doing this, I noticed something. My USBA 3.2 port was doubled up on pins, sharing with my first USBC port. That’s not right… Turns out, I had made a big oopsie. By default the lattepanda mu only exposes 2 usb3.2 paths. Exposing more would require messing up my hdmi or ethernet. And that doesn’t work. So, I actually had to delete my usba 3.2 port! That’s fine, I have two usbc and a usba still, the usba is just 2.0. But, be honest, who actually needs usba 3.2 when you have usbc? Worst case I plug in a hub. This gives me a decent bit more space and actually makes my life easier. Yay. Anywho, I think the power circuitry and first usbc port are actually done? Ish. I need to route 3v3 and 5v still within the power circuit, and I need to connect the USBC port to the Lattepanda Mu. But those will come later as there are a lot of other components those work around. I spent way too long figuring out how to do high speed traces. These usbc traces are all matched to 90 ohms, all length matched within their pairs, all spaced out, connected to ESD diodes, their passives, aaaaah. There is so much to keep track of. This is the net rule menu for the usbc traces. There are 12 more not pictured, roughly. Each one gets assigned the “usbc” rule I wrote, which just defines spacing and width. I believe spacing and width are like 0.254mm and 0.155mm? Something like that, I know the width I said is right. Spacing is less important as it’s just “make pairs close, make not pairs far”. I think. This is all just my interpretation and it could be wrong. We won’t really find out for sure until I try to use the board! Regardless, I made some serious progress and am getting excited for this to be done! I think I can use this to qualify for OutPost! Hopefully. I really want to go to open sauce again. Next I think is the second USBC port and starting the last of the power routing. Yay."}, {"post_id": 78617, "ts": "2026-06-27T00:00:00Z", "hours": 1.5, "text": "Beginning of the PCB. The big one. And planning. Okay. So. I imported all the pcb stuff and dear lord is there a lot of components. So. What’s the first step? Sort it! I sorted everything by schematic page and then within the pages by section/component. That way I know what capacitors and resistors belong to what just by glancing at my design. During this sorting, I felt that my battery stuff was looking off. There was an excess of components and some weird duplicates. Turns out, I had accidentally copied a couple things that Ti included in their reference circuit that exist only for internal Ti debug. AKA, they are useless to me. So I went and removed those. Extra programming headers mainly, with some resistors paired with em. It’s kinda goofy how big of a spot the battery connector gets but its ok. Anywho, with that out of the way, I now had a sorted design. You can see the clusters of components and whatnot. Looking at it now, I realize that one of the usbc ports should be by the power circuity (bottom right) since it is part of that. Not that you can read the words, but you can see stuff moved. Here it is with ratlines by the way. Completely unreadable. Anywho, game plan. I can’t quite figure out sizing but I can kinda let the pcb decide that. This is gonna be a bit of a thick boi but that’s alright. I think the mu will be on the back of the deck, not the front, as I can put a vent back there. And then the screen can go on the other side. I have a few requirements though: Aim for a max width of 230mm. I have a lot more space in Y than X (x is the 230mm) to expand if needed, because of the screen. External ports on the right if possible. Antennas up top if possible. Internal ports on the bottom if possible. Mu somewhere in the middle! That’s my plan for now. Obviously, I can change where things end up to fit my format better. But I think that plan should work out. I will need some usb male to female cables to make routing everything work I think. Mostly for the internal rtl-sdr. PCB Time!"}, {"post_id": 78616, "ts": "2026-06-27T00:00:00Z", "hours": 1.0, "text": "CAD Break! I decided to toss the keyboard pcb in cad so I could get a full mockup with the switches and just get a general vibe for the scale. It turned out really good! I just did it with a simple rectangular pattern, the hardest part was lining up everything initially. The keycaps are an open source design I found called MOTE. https://www.printables.com/model/864126-mote-choc-low-profile-flat-keycaps I really like the flat look. On the real thing I will probably get legended keycaps but I don’t think I will cad that. I mean maybe I could if I feel like placing a ton of decals (I don’t). Maybe I’ll get bored. I actually had to swap out the boot and reset switches 3 seperate times while I was trying to find something low profile enough to fit under the top plate. This will have a solid plate over it after all and I can’t have that hitting the buttons. The original ones were way too tall. The second revision was better but still too tall. So for the third I got the literal lowest profile I could find. These bad boys are half a millimeter tall. They should work though! Was only mildly tedious to export the 3d file, make changes, export again, make changes, export again, make changes, and export for the last time. Just typing that was annoying. But I did it for the love of the game. I really need to stop procrastinating on the mu board. But, I might do some general cad of the whole deck first. Not sure. TBD."}, {"post_id": 78615, "ts": "2026-06-26T00:00:00Z", "hours": 2.5, "text": "Keyboard! I finally decided to do some pcb design for this project and put the whole keyboard together. Did I remember to take progress screenshots? Nope. So. This is the board. I need to add some mounting still but I cannot figure out what fits without messing with cad a bit, as this pcb doesn’t have a representation of the switches. Here was my process. Organize. I started by manually laying out the whole key grid. Easyeda has tools to do this, but they cannot handle multiple components that group together (like switches and diodes). So, I did it all by hand. The keys are on a 17.5x18.5mm grid. This should put 1mm between each key. I then put all the brains on the left of the board for no reason other than I felt like it. In hindsight I maybe should have put them on the top, but I don’t think I want to redo it . Wire the grid. This was tedious as I had to go and do the traces for each diode and key, but I got it done. Wire the brains. This is for 2 layer, so I have no gnd or 3v3 planes, something I have grown very used to. Wire the grid to the brains. This took the most time as I had to keep redoing traces when I figured out I blocked something. That’s it ! A super quick ortholinear 50% keyboard with USBC for my deck. It may be detachable, hence the USBC. I haven’t decided yet but I will soon. That’s the easy part of this project done. Next is a bunch of hard routing. Ugh."}, {"post_id": 78614, "ts": "2026-06-26T00:00:00Z", "hours": 2.5, "text": "Keyboard 2 - Electric Boogaloo. So. I fiugred out that my footprint for the keyswitch sockets was wrong as it did not contain the necessary mounting holes for the switches. This meant I had to redo the keyboard. I took this opportunity to also move the brains up top. This makes the keyboard way less wide, allowing me to make the whole deck less wide. Hooray. I also took progress photos this time. I started by organizing the key grid. Because this is an ortholinear keyboard, it really is just a basic grid. Each diode got put in a little slot at the top, where there is a cutout in the key switch. This is important to avoid collisions of the keys with the diodes. Next I wired up the rows and columns. This is always the most time consuming part. Once I had the grid done, I decided to do something I don’t normally do. I adjusted the pin locations to match the physical layout, allowing me to make a MUCH better looking circuit. It went through a few iterations. Here are two of them. The second looks way better. The columns all connect to the sides while the rows attach to roughly the bottom right. This makes the whole circuit very well organized and creates “wings” of sort out of wiring for the columns. I love it. Next was the brains! I challenged myself to make this as compact as posSIble - good practice for when I have to do the Mu board. It looks pretty great! Left to right it goes USB, 3v3 LDO, MCU, and then debug switches. Here is a close up of the usb section. It is so compact! This board is 2 layer too. If I can get this compact on 2 layer, imagine what I can do with 4 or 6 (aka the mu board). I really didn’t want to redo this board but I am very glad I did. It is way narrower, at 228.5mm wide instead of 260mm, allowing me to keep this deck small. Specifically, small enough to fit structural parts on my 3D printers without splitting them up. Because it’s way cooler to not have ugly seams/splits! I am getting really excited for this project. The keyboard board is so good."}, {"post_id": 78613, "ts": "2026-06-25T00:00:00Z", "hours": 3.5, "text": "Little fixes, little annoyances. Ok so. I had to make a bunch of small fixes in prepping for pcb time and ugh. For instance, changing every instance of a + or - to _P or _N. Why? Because I decided I like that more and want it to be consistent across my whole schematic. What else… I ran DRC a few times to catch issues. Everything is wired up now. Running DRC also showed me that some components were missing footprints, so I had to resolve that. For the most part that was an easy fix. But, I found out my usba 3.0 port was completely messed up and was somehow half of a 2 port schematic, with no footprint. So I had to fully replace that component. Fun fact - majority of LCSC usba 3.0 ports have no footprint or schematic. Problematic. I found one though! Tadaaa. Oh I also realized I forgot fans and a power switch setup. Fans were easy, I just stole the circuit from the lattepanda reference design because I know that works. Fan 1 is the cooler attached to the lattepanda while fan 2 will be some sort of additional inlet or something. I haven’t decided yet but I will figure it out. It’s nice to have either way. > Power switch is simple but actually made me realize I had no way to cut power to anything but the mu, or everything. All or nothing basically. And that is not great for battery life, especially when my battery charging/monitoring circuit NEEDS to maintain power or else I could get a lipo fire (and I can’t charge my battery, and I can’t turn on stuff, etc). So, I split my 5v into two sections. 5v for the battery side and 5v for everything else. Then I put a load switch between the two and wired it to the power button. 90% of the power draw that isn’t the mu is on 5v. 3V3 draws practically nothing and it’s for the best that I maintain 3v3 power, as the Mu needs that for bios stuff. 12v is also needed to stay on as the Mu doesn’t fully lose power, it goes into a shut-down standby mode waiting to be turned back on. This protects your data and whatnot. In desktop PCs, the PSU never actually turns off unless you actively turn it off! The power button just kills everything else. Same philosophy here. Now I think I really am ready to start the pcb. I do want to maybe take a look in cad first to get an idea of what to do, but I could also just take a reserved design approach and work around the pcb. My two main design goals would thus be access to I/O and keeping it thin. Those are pretty simple if you just keep it in mind. I do need to make sure there is space for internal components and the screen and whatnot. PCB Soon!"}, {"post_id": 78612, "ts": "2026-06-24T00:00:00Z", "hours": 4.5, "text": "GPS and LORA!! These are the last two major things of the project. I am forgoing the continuity checker now because all my flight computers do continuity checking and, more importantly, I don’t feel comfortable applying current to explosive charges using anything I designed. First was GPS. I spent a while researching bias tee circuits so I could properly supply 5v to my active antenna. Bias tees are circuits that inject DC power into coaxial, aka AC, lines without disrupting the signal. Black magic in my opinion. Witchcraft. Regardless, after all my research, a friend pointed out that ublox has an integration manual that gives you the exact circuit needed. Because of course I would find that after my research. It’s actually quite simple in the end. I wired power, ground, uart for data, and the antenna line. That’s it. I just have to remember that the antenna line is impedance matched to 50 ohm, which means I need to specify board stackup and all that jazz. I already need to do some of that stuff for other high speed sensitive signals like usb 3.2, ethernet, and hdmi, so nothing new for this project. This should be fully functiona GPS for my deck because linux is cool and supports uart well. This gps module is ten bucks… sheesh. Anywho, next, and somehow the last part of the entire schematic, was LORAWAN. I was initially using an SX1262 module from SEEED Studio but unfortunately none of those feature UART, only SPI. Technically speaking, the Mu has SPI, but it is in practice only able to be used for audio. So, I had to find something with UART. I ended up finding the RAK3172-T. This is a cool module that uses a fancy MCU from ST that has lorawan integrated. Actually, it is the exact same mcu I am using for a camera controller board. That camera controller project is the reason I am putting lorawan on this deck in the first place (there are other reasons too now, but that was the main driving one). So, funnily, we come full circle. Because this is a full MCU it does need firmware updates, so I have to include an STLink header and reset/boot buttons, but thats fine. Besides that I hook up uart and power and we are good to go. That leaves us with our last schematic page completed. Kinda. I determined that, unfortunately, I cannot do this as one big PCB like I had originally intended. That’s chill, I just have to break off the keyboard, which I can do. So, the keyboard is now its own board. That means adding a usbc port to the keyboard for internal wiring. Easy peasy, in the bottom left. It’s just usb2.0, so nothing fancy. Oh, I also need to add a 3v3 regulator. Huh. I just realized that literally while typing this. Let me grab the one from my deck. Problem solved. This takes 5v from VBUS and converts it down to 3v3 for everything else. Simple fix. The cool thing about having my keyboard be a separate board is I could make the keyboard detachable. Will I do that? Not sure. It would be pretty neat though. This also meant adding another internal USBA port for the keyboard wire. While I was at it, since I have extra usb lines, I added another external USBA port aswell. I organized the schematic a little while I was at it to make things look nice. I now have 3 internal USBA, 2 external, and 2 external USBC. That’s 7 ports total, 4 of which are accessible externally. The 3 internal are reserved for an rtl-sdr, the keyboard, and powering the screen. I actually went through and organized all the unorganized sheets! It looks pretty nice now. There’s USBC Ports 1 and 2. There’s Ethernet. There’s storage and wifi. And last, but not least, power finalized. I cannot really organize hdmi much because of the way I intertwined all the stuff, but they don’t look bad. Well I can split off the ESD diodes like this: Yeah sure, why not. Both pages for hdmi are identical. That’s it. All I have left before I can start [Entry truncated]"}, {"post_id": 78611, "ts": "2026-06-23T00:00:00Z", "hours": 4.0, "text": "Today was ethernet and some little touches here and there. Connecting stuff to the lattepanda mu, changing some usba ESD diodes, planning, etc. First, ethernet. I do not understand ethernet. I tried hard to understand and use a TI IC for it and make my own circuit. I couldn’t figure it out. So, I made my own version of a circuit I found on an existing lattepanda mu carrier board - the lattepanda MOKA. https://github.com/piecol/lattepanda_MOKA It’s a pretty cool project and has good examples of some high speed routing and schematic design. This is what the MOKA has for ethernet. And this is what I have. Similar, but I made a fair amount of changes. Notably: Different ESD diodes, I like the TI ones. Different AC coupling capacitors, the MOKA used the wrong ones? I guess it wasn’t an issue but they are supposed to be 220nf, not 100nf. Straight from lattepanda/intel, so I know it’s right. DIfferent resistors to match datasheets better. Different crystal. Different pin names of course. I think that’s it? And I made everything bigger and easier to see. At their core, the circuits are similar, but I made a fair amount of changes. Call it a Reference . Oh, I also hooked up 3v3 VCC to the ethernet port. For some reason the moka just has a capacitor straight to ground?? Which is a silly mistake and probably a non issue but could affect the performance of your magnetics (if they even get power at all without that… datasheet isn’t very helpful.) So that’s ethernet! This will be super nice. I am using an IC that supports ethernet evaluation and fancy debug stuff so I should be able to use this for debugging if I wanted to. Good cyberdeck ability. Next. I changed my USBA to use the TI ESD diodes from my other pages since they are much nicer than the weird cheapo chinese one that I had before. Next again! Some little touches here and there on wiring. Look! USB has the keyboard wired in! That’s just an example of one little touch. Basically all pin mangement though. Double checking, triple checking, quadruple checking. I will never stop checking. Anywho, I also mentioned planning. I am switching to Linux. Planning on windows initially was a little silly but I wanted to be able to use fusion360. I could maybe use proxmox with windows? Depends what ram version I get of the Mu. We will see! This also means I shouldn’t need to run GPS and LORAWAN as USB devices, but rather straight to the mcu over i2c/spi/uart (haven’t decided). Technicallyyyy windows supports that but you need ring 0 level drivers which are incredibly annoying to deal with because of security shtuff. So, I just won’t deal with it! Linux to the rescue. This is probably the right choice for a lot of reasons I have yet to determine. That’s all for today. Next is gonna be finally tacking GPS and Lorawan I think? Or maybe I put it off more by doing trackball stuff. Though I may just make the trackball a USB module so that I can move it…. We will see. It’s funny, I am already past 24 hours of work on this… and I haven’t started any routing or cad. None. Zero. Yippee."}, {"post_id": 78610, "ts": "2026-06-22T00:00:00Z", "hours": 3.0, "text": "Howdy. I figured out the USB stuff! Turns out, I can just wire any two GPIO pins from the TPS25751 to the flip and enable pins of my usbc mux and then I can assign those roles through programming. Ezpz. I enabled adaptive EQ, so for the port side of the mux I don’t need to config any EQ. I think I will need to config EQ for the host side, but I cannot do that until I know my trace lengths! So it is officially a “later me problem”. Tada. Usbc port with charging. The other usbc port was pretty easy. I used a controller that integrates both power control and the mux into one IC, making my life easier. This side doesn’t have a charging circuit since as I covered previously, that is surprisingly difficult to pull off. But what it does have is a vbus power switch to hook vbus to my 5v source for downstream mode. That way it can power peripherals like mice and keyboards. My other port should be able to handle that automatically through the tps25751 so I don’t need a vbus switch. That’s the only difference besides some pin naming between the two schematics! Both have, from left to right, the port (and PD negotiator if present), the TVS diodes, and then the usbc controller/mux/redriver/they’re all the same. I chose the tps25221 for my vbus controller because it is active both low and high, while I need active low, and because TI has great datasheets. Most of the chips I was finding are only active high, so its nice that this one is both, as my usbc controller outputs active low through the ID pin. This means the pin gets pulled low when the usbc port is connected. Anywho, I can move on from usbc for now. Actually USB in its entirety since I already have my USBA 2.0 ports wired too. I am not sure if they are connected to the Mu yet, they might not be, but that is ok since I need to figure some other stuff out first before I go determining pin assigments for certain. For example… HDMI! That is what I will be tackling in my next entry. I will have two HDMI 2.1 ports, one internal for the built in screen and one external for external screens. As I have mentioned before, I could try to use ribbon for the built in screen, but I don’t want to worry about pinout issues. So I will just suffer a little. By default, the lattepanda mu exposes 2 out of the 3 max HDMI ports, which is perfectly what I need. No bios changes needed yet, to my knowledge! Ta ta for now. Surely hdmi won’t be a huge headache, right? Right?"}, {"post_id": 78609, "ts": "2026-06-22T00:00:00Z", "hours": 4.5, "text": "Howdy again! Second entry for today. I tackled HDMI and… the keyboard! First, hdmi. I have two hdmi ports. One on the inside, one the outside. I need a port, protection diodes, and some power stuff/other misc. requirements. I started with just getting everything wired up. I followed a reference design from lattepanda to figure out which pin goes where. You can see a bunch of resistors on the data lines - those are an intel requirement for hdmi. They connect to a mosfet that is controlled by the state of the PC (shutdown, sleep, etc). They help with compatibility I think? Idk, it’s just a necessity. Bottom left is the ESD diodes. They’re the same diodes from my usb shenanigans - they are advertised to work for both. Next was I2C. The HDMI side needs 5v while the lattepanda side needs 3v3. So, I use a logic converter or whatever it’s called. This just converts cleanly between two reference voltages, 3v3 and 5v. When I scrolled down further in the datasheet I saw I needed decoupling and pullup resistors. So, there’s that. Oops. Oh I also forgot to cover the bottom right. That’s hot plug detecting. Basically, it lets the intel graphics processor know when the cable has been plugged in or unplugged while the device is on. That way it can reconfigure or whatever. 5v power for this also has a diode on it so that it can NEVER EVER BACKFEED. EVER. That can destroy stuff! Anywho, I have two ports, so all of that gets duplicated for round 2. The pinout follows the same scheme as the first one despite the different naming. It’s still the same thing, just different names. You can see they follow the same order and everything. That’s actually all for hdmi for now. Routing will be a different story since they’re high speed differential pairs and thus need really fancy treatment… We will get there eventually. I hope. Next. Keyboard! I started by making my matrix. I am doing a 60 key 50% choc keyboard, mimmicking this bad boy: Called the jj50. It doesn’t use choc switches but thats ok. It will be hot swappable as I don’t like hard soldering keyswitches. Sockets are also dirt cheap. Next was mcu. It’s going to be a hardwired usb device, but it still needs an mcu to pretend to be that usb device even though its on the same pcb as the rest of the cyberdeck. I started with an rp2040. Then asked my brother if he has used one. And he said to use something else. So after a bit of browsing I chose an stm32f072cbt6 for simplicity and ease. Man, was it simple. Like, that’s it y’all. ESD diodes, reset and boot buttons, and the mcu, which just gets given power, two usb lines, and the keyboard matrix. Nothing else. It was surprisingly simple and I spent so long checking the datasheet to make sure I wasn’t doing something wildly wrong. I am not! (To my knowledge). In just a couple hours we have fully finished the HDMI and keyboard schematic. Unlike the USB I don’t have to tune EQ based off my pcb traces, so I can just finish those bad boys right now. In a days work, we have done USBC, HDMI, and keyboard. Yippee! Oh, I hit 10 pages on my schematic btw. This is a BIG project."}, {"post_id": 78608, "ts": "2026-06-16T00:00:00Z", "hours": 4.5, "text": "Alright so. I decided to tackle the usbc 3.2 ports. I want to have both ports able of charging the battery with decent speed (20v) and high data speed. First things first I had to find a new usbc port with the required rx/tx lines for high speed. From there, I wanted to do the TVS filtering. I started following this diagram from TI: This sucks. Like, really bad. It will be impossible to route, takes so much space, and the parasitics are probbaly mind boggling. So, I decided to look for chips that do multi input filtering. This way it’s nice and compact but still gives me all the tvs protection. After a LOT of digging I ended up at this. One IC specifically for handling Vbus, since that is high voltage, and then 3 of another IC for rx/tx/d+/d-. These diodes act as protection from surges, static, water shorting, etc. so my circuit doesn’t fry. That took about 2 hours. Now for what took the rest of the time. Trying to figure out multi port charging. Tl:Dr It is extremely difficult to pull off as a hobbyist. Why? I don’t know. But I will just have one charging port. I started with just trying to have two usb pd negotiators and one charging IC. However. USB PD requires that the negotiator chip talk with the charger IC for safety purposes. For some reason, nobody has bothered to implement it in a way that allows for more than one negotiator per charger. With all the Ti products for example, none of them offer i2c addressing, so they will always end up conflicting with eachother and could even pose a fire risk. All the chargers that can handle it require talking to your CPU itself. The problem with that is… that is really, really difficult to configure. It’s not available in BIOS clearly and it isn’t in software. It’s like cpu side firmware stuff that you need specialized tools to work with. This is why laptop manufacturers always partner with CPU manufacturers (and charger manufacturers) - they get those tools. At one point I found a dual port charger IC from TI and got super excited! But. It was not 2 in 1 out. It was 2 in 2 out. It solved none of my issues as you still had conflicting logic of the two power paths. Bleh. So, after all that effort, talking with friends, even making a reddit post, I decided it would just be best if I only had charging on one port and data on both. That’s fine and makes my job simpler, I just have to remember which one is charging when I go to plug the device in. Anywho, I didn’t end up getting to routing the signals to the usb 3.2 logic controller, which is what handles all the signal processing to pass onto the lattepanda and whatnot. I will do that next entry! I also want to work on HDMI next entry. That too will need TVS diode protection but I should be able to use the same chips I think! I spent so long researching and reading datasheets. I have 60 chrome tabs open right now. Bleh."}, {"post_id": 78607, "ts": "2026-06-15T00:00:00Z", "hours": 4.0, "text": "Hi. So. This project has been sponsored by LattePanda/DFRobot! I will be receiving a LattePanda Mu to base this project around. That means some things have to change! My MCU of course, my power plan a little, my format, my USB plan, etc. A lot of changes. First change - get the lattepanda in and start labeling pins! I got the symbol for this fella from an open source carrier board found here: https://oshwlab.com/yoge2013/mini-carrier-demo-for-lattepanda-mu This is a very well done mini carrier and will be good inspiration for mine. Because of how big this is and how many pins there are, it gets two sections in its schematic. One is for power and one is for literally everything else. Power is on the right, else on the left. I am not sure if I will be using all of these pins but I will sure use a lot of them, so they are getting labels just in case. Now, for what changes. First of all my power architecture changes a little as I need to boost 1s lipo voltages up to 12v for the Mu. This is simple enough and can be taken care of by a single boost converter. This circuit was figured out by Ti’s webench power supply configurator, a glorious tool that made this so easy. I inputted what I had and what I needed and it spat out a bunch of options - I picked the simplest and most efficient one. I also realized my 5v setup was a buck, not a boost, so I need to give it the 12v instead of raw system battery voltage. Easy fix. So the power path goes Battery -> Regulator/Charger -> 12v -> 5v -> 3v3 I think that should work. I don’t know if I need 1v8 yet… we are gonna find out. Anywho, I also stole the m.2 storage setup from the carrier board. “Stole”. It needs a little modification to fit my stuff but I will do that later. One of them is actually for a wifi card while the other is actually storage. The Mu does not have built in wifi like the CM5 does. Probably doesn’t fit, this thing is sooo dense. Anywho. Some more changes will need to be made. For starters, I don’t think I need the USB Hub IC’s anymore? Since the Mu has 8x USB 2.0 + 4x Usb 3.2. But I think some of them have to be multiplexed pins from pcie/sata? Basically meaning dual function pins and I can only pick one function, via bios. Since I need pcie for both storage and wifi, I might get cut short on usb ports. But that might not be an issue! I need to look into it more and do some planning. What else… The lorawan stuff probably cannot be over SPI anymore? I don’t actually know how that works with windows… Or I just give in and run linux. I dunno. Gotta think about it. Continuity checker will probably be made hardware only? Or it just becomes yet another usb device. Maybe I will want a usb hub IC just so I have more IO available. RTL-SDR is usb as always. Screen… I have two options. I can either deal with routing hdmi or try to just use the ribbon on the mu. The issue with that is there can be mismatches in pinouts on the ribbon cables - that can’t happen with hdmi. So I think I will probably just expose HDMI. One external for external screens and one internal for the main screen, I think. That’s all for this entry. I am gonna continue reading lattepanda documentation and watch some videos on carrier board design (omg… those exist!!!)."}, {"post_id": 78606, "ts": "2026-06-02T00:00:00Z", "hours": 2.0, "text": "Okay. This has been floating around my head for a while but basically I was thinking. I don’t have a laptop. I cannot afford a laptop. But I do have hackclub. What’s better than a laptop? A cyberdeck! But a general purpose one is kinda lame. Good thing I do rocketry. So here we are. A rocketry ground station cyberdeck. I will preface by saying the scope creep will be strong with this one. Initial feature list: Custom CM5 Carrier Board Based. LORAWAN enabled for controlling electronics and monitoring rocket. Both dedicated 915mhz lorawan transmitting as well as general RTL-SDR monitoring. Ethernet USBC Charging and IO Triple USBA IO XT 30 EMatch continuity checker Dual HDMI Built in touch screen Custom Keyboard Custom Track Ball Custom Scroll Wheel Some buttons! I think that is everything. Quite a lot of features - this is gonna be a long one, with a lot of pcb design. I already started the preliminary PCB design. Mainly, component selection. I will likely need to have a multi page schematic to fit everything cleanly, but that is ok. For now I have this big schematic covered in components. It has the IO ports, m.2 nvme port, usb stuff, battery charging stuff, and lorawan stuff. Oh and the CM5. I need to figure out my schematic hierarchy. Maybe: MCU/Storage/RF Everything IO/Ports Inputs (keyboard, scroll wheel, track ball)/Sensors. Maybe? I am not sure. I will workshop it. I am actually pretty excited about this despite how nightmarish it is going to be. Let’s do this thing!"}]...
|
Title: SmasherGS by @parkerrupe | Stardance
Devlo Title: SmasherGS by @parkerrupe | Stardance
Devlogs:
Okay. This has been floating around my head for a while but basically I was thinking. I don’t have a laptop. I cannot afford a laptop. But I do have hackclub. What’s better than a laptop? A cyberdeck! But a general purpose one is kinda lame. Good thing I do rocketry. So here we are. A rocketry ground station cyberdeck. I will preface by saying the scope creep will be strong with this one. Initial feature list: Custom CM5 Carrier Board Based. LORAWAN enabled for controlling electronics and monitoring rocket. Both dedicated 915mhz lorawan transmitting as well as general RTL-SDR monitoring. Ethernet USBC Charging and IO Triple USBA IO XT 30 EMatch continuity checker Dual HDMI Built in touch screen Custom Keyboard Custom Track Ball Custom Scroll Wheel Some buttons! I think that is everything. Quite a lot of features - this is gonna be a long one, with a lot of pcb design. I already started the preliminary PCB design. Mainly, component selection. I will likely need to have a multi page schematic to fit everything cleanly, but that is ok. For now I have this big schematic covered in components. It has the IO ports, m.2 nvme port, usb stuff, battery charging stuff, and lorawan stuff. Oh and the CM5. I need to figure out my schematic hierarchy. Maybe: MCU/Storage/RF Everything IO/Ports Inputs (keyboard, scroll wheel, track ball)/Sensors. Maybe? I am not sure. I will workshop it. I am actually pretty excited about this despite how nightmarish it is going to be. Let’s do this thing!
Hi. So. This project has been sponsored by LattePanda/DFRobot! I will be receiving a LattePanda Mu to base this project around. That means some things have to change! My MCU of course, my power plan a little, my format, my USB plan, etc. A lot of changes. First change - get the lattepanda in and start labeling pins! I got the symbol for this fella from an open source carrier board found here: https://oshwlab.com/yoge2013/mini-carrier-demo-for-lattepanda-mu This is a very well done mini carrier and will be good inspiration for mine. Because of how big this is and how many pins there are, it gets two sections in its schematic. One is for power and one is for literally everything else. Power is on the right, else on the left. I am not sure if I will be using all of these pins but I will sure use a lot of them, so they are getting labels just in case. Now, for what changes. First of all my power architecture changes a little as I need to boost 1s lipo voltages up to 12v for the Mu. This is simple enough and can be taken care of by a single boost converter. This circuit was figured out by Ti’s webench power supply configurator, a glorious tool that made this so easy. I inputted what I had and what I needed and it spat out a bunch of options - I picked the simplest and most efficient one. I also realized my 5v setup was a buck, not a boost, so I need to give it the 12v instead of raw system battery voltage. Easy fix. So the power path goes Battery -> Regulator/Charger -> 12v -> 5v -> 3v3 I think that should work. I don’t know if I need 1v8 yet… we are gonna find out. Anywho, I also stole the m.2 storage setup from the carrier board. “Stole”. It needs a little modification to fit my stuff but I will do that later. One of them is actually for a wifi card while the other is actually storage. The Mu does not have built in wifi like the CM5 does. Probably doesn’t fit, this thing is sooo dense. Anywho. Some more changes will need to be made. For starters, I don’t think I need the USB Hub IC’s anymore? Since the Mu has 8x USB 2.0 + 4x Usb 3.2. But I think some of them have to be multiplexed pins from pcie/sata? Basically meaning dual function pins and I can only pick one function, via bios. Since I need pcie for both storage and wifi, I might get cut short on usb ports. But that might not be an issue! I need to look into it more and do some planning. What else… The lorawan stuff probably cannot be over SPI anymore? I don’t actually know how that works with windows… Or I just give in and run linux. I dunno. Gotta think about it. Continuity checker will probably be made hardware only? Or it just becomes yet another usb device. Maybe I will want a usb hub IC just so I have more IO available. RTL-SDR is usb as always. Screen… I have two options. I can either deal with routing hdmi or try to just use the ribbon on the mu. The issue with that is there can be mismatches in pinouts on the ribbon cables - that can’t happen with hdmi. So I think I will probably just expose HDMI. One external for external screens and one internal for the main screen, I think. That’s all for this entry. I am gonna continue reading lattepanda documentation and watch some videos on carrier board design (omg… those exist!!!).
Alright so. I decided to tackle the usbc 3.2 ports. I want to have both ports able of charging the battery with decent speed (20v) and high data speed. First things first I had to find a new usbc port with the required rx/tx lines for high speed. From there, I wanted to do the TVS filtering. I started following this diagram from TI: This sucks. Like, really bad. It will be impossible to route, takes so much space, and the parasitics are probbaly mind boggling. So, I decided to look for chips that do multi input filtering. This way it’s nice and compact but still gives me all the tvs protection. After a LOT of digging I ended up at this. One IC specifically for handling Vbus, since that is high voltage, and then 3 of another IC for rx/tx/d+/d-. These diodes act as protection from surges, static, water shorting, etc. so my circuit doesn’t fry. That took about 2 hours. Now for what took the rest of the time. Trying to figure out multi port charging. Tl:Dr It is extremely difficult to pull off as a hobbyist. Why? I don’t know. But I will just have one charging port. I started with just trying to have two usb pd negotiators and one charging IC. However. USB PD requires that the negotiator chip talk with the charger IC for safety purposes. For some reason, nobody has bothered to implement it in a way that allows for more than one negotiator per charger. With all the Ti products for example, none of them offer i2c addressing, so they will always end up conflicting with eachother and could even pose a fire risk. All the chargers that can handle it require talking to your CPU itself. The problem with that is… that is really, really difficult to configure. It’s not available in BIOS clearly and it isn’t in software. It’s like cpu side firmware stuff that you need specialized tools to work with. This is why laptop manufacturers always partner with CPU manufacturers (and charger manufacturers) - they get those tools. At one point I found a dual port charger IC from TI and got super excited! But. It was not 2 in 1 out. It was 2 in 2 out. It solved none of my issues as you still had conflicting logic of the two power paths. Bleh. So, after all that effort, talking with friends, even making a reddit post, I decided it would just be best if I only had charging on one port and data on both. That’s fine and makes my job simpler, I just have to remember which one is charging when I go to plug the device in. Anywho, I didn’t end up getting to routing the signals to the usb 3.2 logic controller, which is what handles all the signal processing to pass onto the lattepanda and whatnot. I will do that next entry! I also want to work on HDMI next entry. That too will need TVS diode protection but I should be able to use the same chips I think! I spent so long researching and reading datasheets. I have 60 chrome tabs open right now. Bleh.
Howdy again! Second entry for today. I tackled HDMI and… the keyboard! First, hdmi. I have two hdmi ports. One on the inside, one the outside. I need a port, protection diodes, and some power stuff/other misc. requirements. I started with just getting everything wired up. I followed a reference design from lattepanda to figure out which pin goes where. You can see a bunch of resistors on the data lines - those are an intel requirement for hdmi. They connect to a mosfet that is controlled by the state of the PC (shutdown, sleep, etc). They help with compatibility I think? Idk, it’s just a necessity. Bottom left is the ESD diodes. They’re the same diodes from my usb shenanigans - they are advertised to work for both. Next was I2C. The HDMI side needs 5v while the lattepanda side needs 3v3. So, I use a logic converter or whatever it’s called. This just converts cleanly between two reference voltages, 3v3 and 5v. When I scrolled down further in the datasheet I saw I needed decoupling and pullup resistors. So, there’s that. Oops. Oh I also forgot to cover the bottom right. That’s hot plug detecting. Basically, it lets the intel graphics processor know when the cable has been plugged in or unplugged while the device is on. That way it can reconfigure or whatever. 5v power for this also has a diode on it so that it can NEVER EVER BACKFEED. EVER. That can destroy stuff! Anywho, I have two ports, so all of that gets duplicated for round 2. The pinout follows the same scheme as the first one despite the different naming. It’s still the same thing, just different names. You can see they follow the same order and everything. That’s actually all for hdmi for now. Routing will be a different story since they’re high speed differential pairs and thus need really fancy treatment… We will get there eventually. I hope. Next. Keyboard! I started by making my matrix. I am doing a 60 key 50% choc keyboard, mimmicking this bad boy: Called the jj50. It doesn’t use choc switches but thats ok. It will be hot swappable as I don’t like hard soldering keyswitches. Sockets are also dirt cheap. Next was mcu. It’s going to be a hardwired usb device, but it still needs an mcu to pretend to be that usb device even though its on the same pcb as the rest of the cyberdeck. I started with an rp2040. Then asked my brother if he has used one. And he said to use something else. So after a bit of browsing I chose an stm32f072cbt6 for simplicity and ease. Man, was it simple. Like, that’s it y’all. ESD diodes, reset and boot buttons, and the mcu, which just gets given power, two usb lines, and the keyboard matrix. Nothing else. It was surprisingly simple and I spent so long checking the datasheet to make sure I wasn’t doing something wildly wrong. I am not! (To my knowledge). In just a couple hours we have fully finished the HDMI and keyboard schematic. Unlike the USB I don’t have to tune EQ based off my pcb traces, so I can just finish those bad boys right now. In a days work, we have done USBC, HDMI, and keyboard. Yippee! Oh, I hit 10 pages on my schematic btw. This is a BIG project.
Howdy. I figured out the USB stuff! Turns out, I can just wire any two GPIO pins from the TPS25751 to the flip and enable pins of my usbc mux and then I can assign those roles through programming. Ezpz. I enabled adaptive EQ, so for the port side of the mux I don’t need to config any EQ. I think I will need to config EQ for the host side, but I cannot do that until I know my trace lengths! So it is officially a “later me problem”. Tada. Usbc port with charging. The other usbc port was pretty easy. I used a controller that integrates both power control and the mux into one IC, making my life easier. This side doesn’t have a charging circuit since as I covered previously, that is surprisingly difficult to pull off. But what it does have is a vbus power switch to hook vbus to my 5v source for downstream mode. That way it can power peripherals like mice and keyboards. My other port should be able to handle that automatically through the tps25751 so I don’t need a vbus switch. That’s the only difference besides some pin naming between the two schematics! Both have, from left to right, the port (and PD negotiator if present), the TVS diodes, and then the usbc controller/mux/redriver/they’re all the same. I chose the tps25221 for my vbus controller because it is active both low and high, while I need active low, and because TI has great datasheets. Most of the chips I was finding are only active high, so its nice that this one is both, as my usbc controller outputs active low through the ID pin. This means the pin gets pulled low when the usbc port is connected. Anywho, I can move on from usbc for now. Actually USB in its entirety since I already have my USBA 2.0 ports wired too. I am not sure if they are connected to the Mu yet, they might not be, but that is ok since I need to figure some other stuff out first before I go determining pin assigments for certain. For example… HDMI! That is what I will be tackling in my next entry. I will have two HDMI 2.1 ports, one internal for the built in screen and one external for external screens. As I have mentioned before, I could try to use ribbon for the built in screen, but I don’t want to worry about pinout issues. So I will just suffer a little. By default, the lattepanda mu exposes 2 out of the 3 max HDMI ports, which is perfectly what I need. No bios changes needed yet, to my knowledge! Ta ta for now. Surely hdmi won’t be a huge headache, right? Right?
Today was ethernet and some little touches here and there. Connecting stuff to the lattepanda mu, changing some usba ESD diodes, planning, etc. First, ethernet. I do not understand ethernet. I tried hard to understand and use a TI IC for it and make my own circuit. I couldn’t figure it out. So, I made my own version of a circuit I found on an existing lattepanda mu carrier board - the lattepanda MOKA. https://github.com/piecol/lattepanda_MOKA It’s a pretty cool project and has good examples of some high speed routing and schematic design. This is what the MOKA has for ethernet. And this is what I have. Similar, but I made a fair amount of changes. Notably: Different ESD diodes, I like the TI ones. Different AC coupling capacitors, the MOKA used the wrong ones? I guess it wasn’t an issue but they are supposed to be 220nf, not 100nf. Straight from lattepanda/intel, so I know it’s right. DIfferent resistors to match datasheets better. Different crystal. Different pin names of course. I think that’s it? And I made everything bigger and easier to see. At their core, the circuits are similar, but I made a fair amount of changes. Call it a Reference . Oh, I also hooked up 3v3 VCC to the ethernet port. For some reason the moka just has a capacitor straight to ground?? Which is a silly mistake and probably a non issue but could affect the performance of your magnetics (if they even get power at all without that… datasheet isn’t very helpful.) So that’s ethernet! This will be super nice. I am using an IC that supports ethernet evaluation and fancy debug stuff so I should be able to use this for debugging if I wanted to. Good cyberdeck ability. Next. I changed my USBA to use the TI ESD diodes from my other pages since they are much nicer than the weird cheapo chinese one that I had before. Next again! Some little touches here and there on wiring. Look! USB has the keyboard wired in! That’s just an example of one little touch. Basically all pin mangement though. Double checking, triple checking, quadruple checking. I will never stop checking. Anywho, I also mentioned planning. I am switching to Linux. Planning on windows initially was a little silly but I wanted to be able to use fusion360. I could maybe use proxmox with windows? Depends what ram version I get of the Mu. We will see! This also means I shouldn’t need to run GPS and LORAWAN as USB devices, but rather straight to the mcu over i2c/spi/uart (haven’t decided). Technicallyyyy windows supports that but you need ring 0 level drivers which are incredibly annoying to deal with because of security shtuff. So, I just won’t deal with it! Linux to the rescue. This is probably the right choice for a lot of reasons I have yet to determine. That’s all for today. Next is gonna be finally tacking GPS and Lorawan I think? Or maybe I put it off more by doing trackball stuff. Though I may just make the trackball a USB module so that I can move it…. We will see. It’s funny, I am already past 24 hours of work on this… and I haven’t started any routing or cad. None. Zero. Yippee.
GPS and LORA!! These are the last two major things of the project. I am forgoing the continuity checker now because all my flight computers do continuity checking and, more importantly, I don’t feel comfortable applying current to explosive charges using anything I designed. First was GPS. I spent a while researching bias tee circuits so I could properly supply 5v to my active antenna. Bias tees are circuits that inject DC power into coaxial, aka AC, lines without disrupting the signal. Black magic in my opinion. Witchcraft. Regardless, after all my research, a friend pointed out that ublox has an integration manual that gives you the exact circuit needed. Because of course I would find that after my research. It’s actually quite simple in the end. I wired power, ground, uart for data, and the antenna line. That’s it. I just have to remember that the antenna line is impedance matched to 50 ohm, which means I need to specify board stackup and all that jazz. I already need to do some of that stuff for other high speed sensitive signals like usb 3.2, ethernet, and hdmi, so nothing new for this project. This should be fully functiona GPS for my deck because linux is cool and supports uart well. This gps module is ten bucks… sheesh. Anywho, next, and somehow the last part of the entire schematic, was LORAWAN. I was initially using an SX1262 module from SEEED Studio but unfortunately none of those feature UART, only SPI. Technically speaking, the Mu has SPI, but it is in practice only able to be used for audio. So, I had to find something with UART. I ended up finding the RAK3172-T. This is a cool module that uses a fancy MCU from ST that has lorawan integrated. Actually, it is the exact same mcu I am using for a camera controller board. That camera controller project is the reason I am putting lorawan on this deck in the first place (there are other reasons too now, but that was the main driving one). So, funnily, we come full circle. Because this is a full MCU it does need firmware updates, so I have to include an STLink header and reset/boot buttons, but thats fine. Besides that I hook up uart and power and we are good to go. That leaves us with our last schematic page completed. Kinda. I determined that, unfortunately, I cannot do this as one big PCB like I had originally intended. That’s chill, I just have to break off the keyboard, which I can do. So, the keyboard is now its own board. That means adding a usbc port to the keyboard for internal wiring. Easy peasy, in the bottom left. It’s just usb2.0, so nothing fancy. Oh, I also need to add a 3v3 regulator. Huh. I just realized that literally while typing this. Let me grab the one from my deck. Problem solved. This takes 5v from VBUS and converts it down to 3v3 for everything else. Simple fix. The cool thing about having my keyboard be a separate board is I could make the keyboard detachable. Will I do that? Not sure. It would be pretty neat though. This also meant adding another internal USBA port for the keyboard wire. While I was at it, since I have extra usb lines, I added another external USBA port aswell. I organized the schematic a little while I was at it to make things look nice. I now have 3 internal USBA, 2 external, and 2 external USBC. That’s 7 ports total, 4 of which are accessible externally. The 3 internal are reserved for an rtl-sdr, the keyboard, and powering the screen. I actually went through and organized all the unorganized sheets! It looks pretty nice now. There’s USBC Ports 1 and 2. There’s Ethernet. There’s storage and wifi. And last, but not least, power finalized. I cannot really organize hdmi much because of the way I intertwined all the stuff, but they don’t look bad. Well I can split off the ESD diodes like this: Yeah sure, why not. Both pages for hdmi are identical. That’s it. All I have left before I can start [Entry truncated]
Little fixes, little annoyances. Ok so. I had to make a bunch of small fixes in prepping for pcb time and ugh. For instance, changing every instance of a + or - to _P or _N. Why? Because I decided I like that more and want it to be consistent across my whole schematic. What else… I ran DRC a few times to catch issues. Everything is wired up now. Running DRC also showed me that some components were missing footprints, so I had to resolve that. For the most part that was an easy fix. But, I found out my usba 3.0 port was completely messed up and was somehow half of a 2 port schematic, with no footprint. So I had to fully replace that component. Fun fact - majority of LCSC usba 3.0 ports have no footprint or schematic. Problematic. I found one though! Tadaaa. Oh I also realized I forgot fans and a power switch setup. Fans were easy, I just stole the circuit from the lattepanda reference design because I know that works. Fan 1 is the cooler attached to the lattepanda while fan 2 will be some sort of additional inlet or something. I haven’t decided yet but I will figure it out. It’s nice to have either way. > Power switch is simple but actually made me realize I had no way to cut power to anything but the mu, or everything. All or nothing basically. And that is not great for battery life, especially when my battery charging/monitoring circuit NEEDS to maintain power or else I could get a lipo fire (and I can’t charge my battery, and I can’t turn on stuff, etc). So, I split my 5v into two sections. 5v for the battery side and 5v for everything else. Then I put a load switch between the two and wired it to the power button. 90% of the power draw that isn’t the mu is on 5v. 3V3 draws practically nothing and it’s for the best that I maintain 3v3 power, as the Mu needs that for bios stuff. 12v is also needed to stay on as the Mu doesn’t fully lose power, it goes into a shut-down standby mode waiting to be turned back on. This protects your data and whatnot. In desktop PCs, the PSU never actually turns off unless you actively turn it off! The power button just kills everything else. Same philosophy here. Now I think I really am ready to start the pcb. I do want to maybe take a look in cad first to get an idea of what to do, but I could also just take a reserved design approach and work around the pcb. My two main design goals would thus be access to I/O and keeping it thin. Those are pretty simple if you just keep it in mind. I do need to make sure there is space for internal components and the screen and whatnot. PCB Soon!
Keyboard 2 - Electric Boogaloo. So. I fiugred out that my footprint for the keyswitch sockets was wrong as it did not contain the necessary mounting holes for the switches. This meant I had to redo the keyboard. I took this opportunity to also move the brains up top. This makes the keyboard way less wide, allowing me to make the whole deck less wide. Hooray. I also took progress photos this time. I started by organizing the key grid. Because this is an ortholinear keyboard, it really is just a basic grid. Each diode got put in a little slot at the top, where there is a cutout in the key switch. This is important to avoid collisions of the keys with the diodes. Next I wired up the rows and columns. This is always the most time consuming part. Once I had the grid done, I decided to do something I don’t normally do. I adjusted the pin locations to match the physical layout, allowing me to make a MUCH better looking circuit. It went through a few iterations. Here are two of them. The second looks way better. The columns all connect to the sides while the rows attach to roughly the bottom right. This makes the whole circuit very well organized and creates “wings” of sort out of wiring for the columns. I love it. Next was the brains! I challenged myself to make this as compact as posSIble - good practice for when I have to do the Mu board. It looks pretty great! Left to right it goes USB, 3v3 LDO, MCU, and then debug switches. Here is a close up of the usb section. It is so compact! This board is 2 layer too. If I can get this compact on 2 layer, imagine what I can do with 4 or 6 (aka the mu board). I really didn’t want to redo this board but I am very glad I did. It is way narrower, at 228.5mm wide instead of 260mm, allowing me to keep this deck small. Specifically, small enough to fit structural parts on my 3D printers without splitting them up. Because it’s way cooler to not have ugly seams/splits! I am getting really excited for this project. The keyboard board is so good.
Keyboard! I finally decided to do some pcb design for this project and put the whole keyboard together. Did I remember to take progress screenshots? Nope. So. This is the board. I need to add some mounting still but I cannot figure out what fits without messing with cad a bit, as this pcb doesn’t have a representation of the switches. Here was my process. Organize. I started by manually laying out the whole key grid. Easyeda has tools to do this, but they cannot handle multiple components that group together (like switches and diodes). So, I did it all by hand. The keys are on a 17.5x18.5mm grid. This should put 1mm between each key. I then put all the brains on the left of the board for no reason other than I felt like it. In hindsight I maybe should have put them on the top, but I don’t think I want to redo it . Wire the grid. This was tedious as I had to go and do the traces for each diode and key, but I got it done. Wire the brains. This is for 2 layer, so I have no gnd or 3v3 planes, something I have grown very used to. Wire the grid to the brains. This took the most time as I had to keep redoing traces when I figured out I blocked something. That’s it ! A super quick ortholinear 50% keyboard with USBC for my deck. It may be detachable, hence the USBC. I haven’t decided yet but I will soon. That’s the easy part of this project done. Next is a bunch of hard routing. Ugh.
CAD Break! I decided to toss the keyboard pcb in cad so I could get a full mockup with the switches and just get a general vibe for the scale. It turned out really good! I just did it with a simple rectangular pattern, the hardest part was lining up everything initially. The keycaps are an open source design I found called MOTE. https://www.printables.com/model/864126-mote-choc-low-profile-flat-keycaps I really like the flat look. On the real thing I will probably get legended keycaps but I don’t think I will cad that. I mean maybe I could if I feel like placing a ton of decals (I don’t). Maybe I’ll get bored. I actually had to swap out the boot and reset switches 3 seperate times while I was trying to find something low profile enough to fit under the top plate. This will have a solid plate over it after all and I can’t have that hitting the buttons. The original ones were way too tall. The second revision was better but still too tall. So for the third I got the literal lowest profile I could find. These bad boys are half a millimeter tall. They should work though! Was only mildly tedious to export the 3d file, make changes, export again, make changes, export again, make changes, and export for the last time. Just typing that was annoying. But I did it for the love of the game. I really need to stop procrastinating on the mu board. But, I might do some general cad of the whole deck first. Not sure. TBD.
Beginning of the PCB. The big one. And planning. Okay. So. I imported all the pcb stuff and dear lord is there a lot of components. So. What’s the first step? Sort it! I sorted everything by schematic page and then within the pages by section/component. That way I know what capacitors and resistors belong to what just by glancing at my design. During this sorting, I felt that my battery stuff was looking off. There was an excess of components and some weird duplicates. Turns out, I had accidentally copied a couple things that Ti included in their reference circuit that exist only for internal Ti debug. AKA, they are useless to me. So I went and removed those. Extra programming headers mainly, with some resistors paired with em. It’s kinda goofy how big of a spot the battery connector gets but its ok. Anywho, with that out of the way, I now had a sorted design. You can see the clusters of components and whatnot. Looking at it now, I realize that one of the usbc ports should be by the power circuity (bottom right) since it is part of that. Not that you can read the words, but you can see stuff moved. Here it is with ratlines by the way. Completely unreadable. Anywho, game plan. I can’t quite figure out sizing but I can kinda let the pcb decide that. This is gonna be a bit of a thick boi but that’s alright. I think the mu will be on the back of the deck, not the front, as I can put a vent back there. And then the screen can go on the other side. I have a few requirements though: Aim for a max width of 230mm. I have a lot more space in Y than X (x is the 230mm) to expand if needed, because of the screen. External ports on the right if possible. Antennas up top if possible. Internal ports on the bottom if possible. Mu somewhere in the middle! That’s my plan for now. Obviously, I can change where things end up to fit my format better. But I think that plan should work out. I will need some usb male to female cables to make routing everything work I think. Mostly for the internal rtl-sdr. PCB Time!
Power circuitry and some usbc 3.2. So. High speed routing is probably what I hate most in the world right now. It’s so annoying, it’s all diff pairs, you gotta be so careful. Bleh. Impedance and length matching. Bleh. Regardless, I started routing the very first usbc port just because I have to work around it’s traces. This took an hour. This. It’s 8 trace routes. Although because of how easyeda works it’s split into like 16 different configured differential pairs. Each one needs the rules assigned to tell it spacing and width. Then I had to actually route them. TX lines are supposed to get their passives closer to the USBC port while RX lines get it closer to the device, but both kinda got it in the middle because of how the spacing works out. Oh, and they all get piped through ESD diodes. Then I had to length match them within like, 0.1mm. Blehh. After that I worked more on power circuitry. I needed to route I2C lines within the power circuitry so that the ICs could talk to eachother, as well as add more passives that I had forgotten. Mostly decoupling. I also shifted the VBUS line down so I would have room to wire 5v and 3v3 to all the ICs crammed in there. Before that they were all kinda blocked on my power plane, which defeats the point of a power plane. More on usbc. I had to change nets (pins) a bunch in my schematic to get this to work because I needed them to line up with the physical pin and component locations so I wasn’t crossing paths or anything. While doing this, I noticed something. My USBA 3.2 port was doubled up on pins, sharing with my first USBC port. That’s not right… Turns out, I had made a big oopsie. By default the lattepanda mu only exposes 2 usb3.2 paths. Exposing more would require messing up my hdmi or ethernet. And that doesn’t work. So, I actually had to delete my usba 3.2 port! That’s fine, I have two usbc and a usba still, the usba is just 2.0. But, be honest, who actually needs usba 3.2 when you have usbc? Worst case I plug in a hub. This gives me a decent bit more space and actually makes my life easier. Yay. Anywho, I think the power circuitry and first usbc port are actually done? Ish. I need to route 3v3 and 5v still within the power circuit, and I need to connect the USBC port to the Lattepanda Mu. But those will come later as there are a lot of other components those work around. I spent way too long figuring out how to do high speed traces. These usbc traces are all matched to 90 ohms, all length matched within their pairs, all spaced out, connected to ESD diodes, their passives, aaaaah. There is so much to keep track of. This is the net rule menu for the usbc traces. There are 12 more not pictured, roughly. Each one gets assigned the “usbc” rule I wrote, which just defines spacing and width. I believe spacing and width are like 0.254mm and 0.155mm? Something like that, I know the width I said is right. Spacing is less important as it’s just “make pairs close, make not pairs far”. I think. This is all just my interpretation and it could be wrong. We won’t really find out for sure until I try to use the board! Regardless, I made some serious progress and am getting excited for this to be done! I think I can use this to qualify for OutPost! Hopefully. I really want to go to open sauce again. Next I think is the second USBC port and starting the last of the power routing. Yay.
Power circuitry! I wasn’t sure where to start and I certainly didn’t want to start with any highspeed routing. So, we are doing the power circuit first. I started with simply just… trying to get everything connected and compact. This would prove harder than I anticipated. It’s a big mess honestly. I was working without ratlines so that I can actually see what I am doing, and that means I forgot some components. So it actually just got worse for a bit. The big thick trace is 12v main power. This is up to like, 35 watts, so it needs to be super big. Hence the 3mm wide trace. We have roughly: Bottom is 5v. Top middle is 12v. Top right is battery charger. You can kinda see the ICs buried in there. Those are the focal points. The very first thing I did to make this better was move 5v. I realized there’s no reason it needs to be so smushed in there. So, it gets scooted over to the left. Much better. Zooming in on 5v… I did some rearranging to make it less wonky and added the components I had forgotten - mainly decoupling caps. I am really good at forgetting decoupling caps. Since 5v is the main power for the system besides 12v for the mu, it gets a big big decoupling cap. That’s the big thing on the left. There are actually three ICs in here. One is the 5v buck converter, one is the 5v load switch for the system, and one is the 3v3 LDO. I completely forgot 3v3 is in there! Not that it’s easy to tell. This is the current state of the power circuitry. We have from left to right: 5v and 3v3, 12v, battery charger, and charger EEPROM. Plus the battery and thermistor connectors. Here is a view of the internal power layer. I used a mix of wide traces and copper pours for this so that I can guarantee my traces are wide enough. I also used multiple vias for connections in a lot of spots to give more “wire” for the power to go over. It’s way less of a mess now than when we started, and it was annoying to get to this point. I am still not sure if I am super happy with it, but I think it is good enough for now. I still need to wire up the i2c control, but that requires the USBC PD controller be wired. And I haven’t gotten that far yet. I think that will be next? Though I may need to route some high speed traces first so I know what I am working around. Not totally sure, I’ll probably ask one of my smarter PCB friends what to do. I am gonna get this done, whether through perserverance or straight up spite.
The second usbc port! I have decided that differential pairs are my greatest enemy. Truly, this is miserable I worked from the “bottom” up, routing traces through their passives in impedance and length matched pairs. This worked surprisingly well and I ran into minimal issues. Something cool I was able to do was go back and use open channels on existing ESD diodes rather than adding more. Specifically, that one at the top. It had one pair from the first usbc port, and now has a pair from the second port. Since they both had to be routed around the plug legs like that, they end up in the same spot. RX lines get just resistors while TX lines get capacitors and resistors. That’s what the smaller passives are on two of the lines - capacitors. Once I had those 4 lines routed, I get to route the less crucial lines. There’s still a diff pair in these ones, but since it’s usb 2.0, it is way less important where that bad boy goes. It’s lower speed. Higher speed = more fragile = more important. For these routing I had to add the other chips necessary for the port. One for protecting vbus shorts and one for connecting vbus to 5 volt, since this port needs to be a power source, not just a sink. That way it can power other devices. This is what those vbus lines look like. They will be connected to 5v ultimately, but I have yet to route 5v. Soon. With a couple more traces, I had this USBC port complete. This one is a mess. And it was super tedious as always. But after this I get to route just some nice chill usb 2.0 as a break before I route HDMI. Hdmi has waay more passives on the diff pairs for some reason. HDMI and Ethernet also mean I get to deal with writing new differential pair rules as these have different impedances from USBC. Anywho, here’s both usbc ports together. It’s really getting busy in here! Can’t wait to add more. On the logistics side of things, I got approved for super hardware builder for Outpost aswell as got my flight stipends approved. That means I am going to Open Sauce/Outpost! I need to finish this project by July 7 to truly “qualify”, though if I already have flights… I’m not worried, I’ll get it done in time.
I routed 1 hdmi port and 4 usba 2.0 ports! I am making solid progress! First was hdmi. This required defining a new differential pair rule for 100 ohms instead of 90 ohms (usb spec). Easy enough. That’s the rule. Anywho. HDMI has a pretty interesting circuit on it actually. When the device goes to sleep or shuts off, it pulls all the hdmi lines to gnd with a mosfet. I always thought the way computers did sleep for hdmi was something way fancier but no. It literally just shunts the signal to gnd. Pretty neat in my opinion! That’s the big circuit with resistors on the left. All into a mosfet that triggers with sleep or shutdown. The sls_s0 operates that way - only active (low) when the device is in use. Recreating this was a bit of a hassle honestly and really made me think. But I got it figured out in the end. From right to left it goes connector, ESD diodes, resistors, and then ac filtering capacitors. AC filtering capacitors ugh. Doesn’t that sound like it should filter out AC? But actually, they work by blocking DC and only letting AC through. I think that should be named DC filtering but idk I ain’t no electrician. Rant aside, those resistors will get connected to a common line in the signal layer (layer 3) and then to a mosfet. Next was an I2C level shift. The HDMI side of the I2C lines operate on 5 volt while my device side operates on 3 volt. So, I use a little IC to handle the level shift and make sure my data stays clean. Did you know there is I2C in HDMI? I sure didn’t, but it is fascinating. Basically, the I2C lines are how your device figures things out like screen size, resolution, refresh rate, color profiles, etc. Basically, it is how the device and screen “talk” about what each is capable of and what they need from eachother. Over I2C! I’ve personally seen 30 foot hdmi cables. You’re telling me I2C lines can be 30 feet long without issue?? Wow. Fascinating stuff. Second rant aside, the next circuit was my hot plug detection and 5v power. This is the last bit. These just get lumped together because the pins are together. 5V is on the very left with the rectangle thing, that’s a diode. Everything to the right of that is hot plug detect. It basically tells my device that a screen was unplugged/plugged in while my device was on so that it knows to reconfigure everything. Pretty neat. That’s a full hdmi port! It looks like this: Next was the USB ports. One is external and the other three are internal. They are all basically carbon copies save for two of the internal ones sharing an ESD diode module just because they can and I want to cut down on components. They all get ESD filtering on the data pair, plus a fuse and decoupling capacitor on the 5V power line. That way an overcurrent blows the fuse and not my whole board. That’s it for this entry! I am on a roll today and honestly may not sleep for a while to just keep going. Or I will. I don’t know, it’s late. Next is the second HDMI port and the Ethernet port. Not sure which will come first. Probably HDMI since I know how to do it.
I routed the second hdmi port and the ethernet port! HDMI was super straight forward, just a copy of the other one rotated 90 degrees. Did take me a second to remember what I did but I got it done. Next was ethernet. I had no idea what I was doing for this but here we go. I started connecting the diff pairs of the connector to my ethernet controller. This converts the ethernet junk to PCIE for my Mu to deal with. All length matched, impedance matched to 100 ohms, spaced out properly, ESD filtering, etc. All sorts of nonsense. It was at this point, when I went to wire the passives for my ethernet controller that I realized - hey, this needs 1v0. I don’t have 1v0 in my power circuit. Time to speedrun a power circuit. Ready… Set… Go!! I started by pulling up TI WeBench to get a power circuit schematic. I inputed 1v and 500ma and it outputted a couple options. I picked the first one, the cheapest. It gave me this. I used it to make: This. Identical circuit, just some pins moved on the symbol. I threw this onto the Ethernet page because my Power page is full, and because this is gonna be near the ethernet connector as I don’t trust the 1v to survive a path across the board. Just in case. After that, I synced the schematic to my pcb, and threw together the circuit on board. Stupid simple, so it’s stupid reliable. Boom. Power circuit done. With that fixed I could go back to adding all the passives and power hookups for my ethernet controller. Bam. Done. This thing has so many power hookups, it’s unreal. 4 different pins get 1v0, 3 different pins get 3v3. That’s 7 pins. Wtf. It’s ok though, I got it done. I did have to route decoupling internally for a couple pins just because they got placed next to high speed pairs for some reason (stupid placement realtek. stupid placement.). I think if I do this again I will use a TI IC for ethernet because the realtek documentation is mid and 1v0 is stupid. Give me 3v3 and 5v like a sane person. Anywho, with that done, all the ports on the board are wired. Yup. All of them. HUGE progress. But - what do I have left? m.2 slots CMOS battery fans gps lorawan final power routing (5v and 3v3) final signal routing (hook it all up to the mu) That’s it! Only 7 things on my checklist. M.2 slots are more diff pairs because of course they are, but after that it’s smooth sailing stupid logic until the final signal routing. And even then, that is partially stupid logic too (high speed = smart logic, low speed = stupid logic). I guess I’ll tackle M.2 next? TBD.
High speed routing!! I connected everything up to the Mu. This sucked. Things kept overlapping and it was so bleh. I started in the top right with USBC and worked down and to the left. Well. I actually started with the m.2 because they are right next to the Mu, and then went top right to bottom left. It was at this point that I felt like something might be off. Why would the pins for one HDMI port be backwards but not for the other? The answer was simple: I had the pins wrong. Oops. Once I fixed that I could line up everything real nice. But first, after a tip from a friend, I dropped the USBC lines down to the bottom layer so that everything else could be top. This made it so much cleaner looking. SO much better. I am a little worried about EMI from the buck converters but I think it might be ok? I’ll add a bunch of GND vias or something. After I had those all wired up, I did the last few small circuits. LORAWAN. GPS, with the antenna keepout. The power switch. The fans. And last, but certainly not least, the CMOS battery. And with that, all the individual circuits are complete. So what’s left? I literally just have to connect all the low speed lines up to the Mu, and I am done. This is no small task, as I have to weave around and through all the high speed lines, but it is very possible. It will get done soon.
So. I did the pcie ports. This was a doozy. So for my 3V3 setup for this board, I have a 500ma LDO. Because I don’t have much 3V3. I thought. Fun fact - M.2 SSDs draw up to 3 amps. Uh oh. 3 amps??? That’s insane! So, I initially was just adding a 6a circuit. I got that all sorted. Turns out, this needs 2oz copper. I am not doing 2oz copper. That is expensive. So I switched. Each m.2 gets its own 3V3 3A circuit. Not actually that complex! Just annoying. It was at this point that I also realized I had both M.2 on the same PCIE lines. This does not work. So, I had to delete ethernet to get another pcie set. This is fine. I was never really going to use it if we’re being honest and it lets me make the whole board much smaller to get rid of it. The board is like, 120mm wide now! In that photo you can also see the completed M.2 circuits. Each one has a power circuit tapping into the main 12v, and some passives for stuff like filtering high speed lines and a status LED - one per M.2. Here are some closeups! The circuits off to the side of each port are the power circuits. The bottom left two components are the status LEDs, and the top right two components are filtering capacitors for high speed lines. With those updates, the board is now ready to hook up all the high speed pairs to the mu! After that I get to do low speed, power routing, and be done! Woooo. I am so ready to be done with this pcb.
Low speed routing, mounting holes… we are done!!! As the title of this entry suggests, this is the last entry of pcb design. I routed all the low speed traces, which was the only thing left. Besides mounting holes, which I did afterwards. I started at the top left for this and worked my way clockwise around the board. Mostly. At some point I couldn’t keep track of what needed routed so I was just following what DRC said needed routed, working my way down the list. I started doing that about halfway through. This sucked. I had to bob and weave and sneak my way around all the high speed traces, ensuring proper spacing to minimize cross talk and keep trace impedance correct. Having gnd pours or traces close to the high impedance traces changes impedance because of uhh… parasitic capacitance I think? Electromagnetic fields inducing inductance and capacitance. Something like that. Anywho, lets see it! Look at all that spaghetti. I had to route some traces on my power plane it was getting so busy! Good thing I named it power/aux signal. This is the board with gnd pours on top/bottom. The pours are offset 1mm from all traces, which should be enough to protect the high speed. Here’s the signal layer. Yes, I did route some diff pairs on this layer. They are usb 2.0 and do not care. This is my power/aux sig layer. Mostly big ol power traces and pours, but there are a few signals mixed in that I just couldn’t get to route well on other layers. And those are the GND planes! With that, we have a finished board! Well almost. It needs a bit of silkscreen. That’s better. You can also see the mounting holes in that photo! I just used EasyEDA’s Pad feature to add pads with an OD of 5.8mm and an ID of 3.2mm. Should perfectly match M3 socket head screws. So. Where do we go from here? It’s cad time. I LOVE cad time. I need to physically design the deck itself! Which means exporting the 3D models of my pcbs, modeling out the screen, modeling a case, modeling all the internals, etc. This is the fun part!! Pcbs are NOT the fun part. So… CAD soon!!
CAD!! CAD CAD CAD!! I love CAD. Ok, first things first, I exported the Mu carrier board 3D model and imported it into Fusion 360. I needed to add the M.2 accessories and standoffs for the M.2 and Mu stuff. This was fairly straightforward. The standoffs are M2 x 1.5mm and I used M2 pan head phillips screws as those are typically what M.2 hardware kits include. For the M.2 accessories, we have a full size NVME drive and a half size NVME wifi/bluetooth card. These are lines up to the best of my abilities but may be a smidge off. Thankfully, they are just cosmetic, so it does not matter much at all. Anywho, next up. I started laying things out in CAD for the actual deck. I am going for a minimalist flat slab with a metallic top/bottom panel sandwiching a printed frame. So, that’s what I am laying out! You may have noticed (you probably didn’t) that the keyboard usb port/buttons/etc are now on the bottom of the PCB. This is no mistake! I realized I made a bit of an oopsie - the only way a top plate can fit with choc switches is if all that good stuff is on the bottom. Ugh. So, I flipped those components to the other side of my PCB. This required me to reroute a large portion of the matrix (half of it) and all the traces connecting the matrix to the MCU. As you can see in the photo, all the keyswitch footprints are on the bottom now. Flipped. Anywho, with that out of the way, I could now move on to developing the case. First was the top plate. This is a 1.2mm aluminum lasercut plate that I will be getting anodized Red to contrast the Black 3D printed mainframe. I started by making the keyswitch grid. This is a 17.5x18.5mm spaced 12x5 grid of 13.5x13.5mm squares. Quite a mouthfull. The choc switches snap into this plate nicely, and it serves as a structural point of rigidity. From there it gets extended, and the cyberdeck is starting to look like something! I initially went for this clean look where there was no border around the screen besides the one built into the screen - this would later change, but thats for later. I then started building up the black casing. I am targeting 40mm thickness for the printed portion. Which is fairly thick, but it kinda has to be for the lattepanda mu fan stuff to fit. This has a lip for the keyboard pcb to rest on and mounting holes for the keyboard pcb. I will later add bracing under more of the keyboard pcb but for now I am focused on the outermost shell. It then gets extended under the screen! Man, it’s looking awesome. However, it was at this point that I remembered - hey, the ports for my screen are on the outer edge! How would the cables reach the interior with the ports on the exterior…. They wouldn’t. So, it gets extended! Bam. I actually like how the red border ties it all together and think this still looks awesome! Albeit bigger, but that’s ok. At this point I also added a flat back panel to finish the sandwich. This will ultimately have screw holes and ventilation in it, but for now it can stay flat. That’s all for this entry actually! I made a lot of cad progress, but as you may have noticed this entry took a while to get posted. That’s because I went to OutPost IRL! It was a life changing event and I had so much fun. It was so awesome. Anywho. What’s next? Literally just fleshing out the casing. I need to: Add cutouts for the I/O ports Add internal structure/Skeleton Add ventilation/Fans Add Battery Split part into smaller printable sections And then submit! I am getting so close!!!
Final CAD touches. Wow. That went quick. This is the final cad entry though. First things first, I had to split the casing into two sections that would fit on my printer. These sections would be joined with M3 bolts and heat set inserts. This is a simple overlapping butt joint with 4 screws per side. Nothing complex, was just a few sketch and extrudes. Next was building up interior structure, which you can see part of in that screenshot. I basically just needed mounting for the screen and board. This is what I came up with. I also added the port cuouts on the side while I was at it. This one interior strucutre has mounting holes for both the screen and the lattepanda carrier PCB. Here is the other side. Unfortunately, this will need supports to print, as I couldn’t think of a way to avoid them, which hurts me. But it is what it is, I will make do. Here is the interior with the components. Looks good! Lastly, I added 4 antennas. That’s right, 4. One is on the inside in this corner! The square one internally is a GPS antenna. It is a ceramic active patch antenna. The other 3 antennas are simple “rubber ducky” antennas for Wifi+Bluetooth and LORAWAN. Short and simple. That’s it for cad! Now I just need to take renders and put the repo together with a BOM and stuff! Wait, I forgot screws. Now we good. I also added slits to the back for cooling! They will just be lasercut into the aluminum. Okay, alll done for real this time. Now we move on to renders and stuff.
I worked on preparing for shipping this project. I made most of the BOM, took some renders, did some Github Repo formatting. I am so ready to be done with this project but I am worried about budget as my PCB is rather expensive with tariffs/shipping. Maybe I reach out to PCBway for a sponsorship or something. Ugh, I don’t know. Anyways, peep the cool render....
|
1793364676.9819567
|
1793969476.9819567
|
|
19331
|
Platformer Game by @Livvy | Stardance
|
Livvy
|
3
|
15.0
|
188
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-22T00:51:31Z", "hours": 10.0, "multiplier": 9.82, "payout": 121, "blessing": "neutral", "text": "I completed a game where you jump through obstacles and change gravity to move through each level. As an astronaut, you use a paint gun to change your gravity based on the corresponding color. I’m proud of this being my first big project in java and HTML and CSS, and that this was my first time using VS Code. Also the paint mechanics working was a big accomplishment. A struggle was getting the flag to work after something I added along the way caused a bug and I didn’t realize to way later. It took a while but I got it working! I hope everyone enjoys the project.", "repo": "https://github.com/oliviasophia67/Paint-Gravity-Platformer", "demo": "https://oliviasophia67.github.io/Paint-Gravity-Platformer/"}, {"ship_num": 2, "ts": "2026-07-13T20:43:26Z", "hours": 0.0, "multiplier": 17.21, "payout": 7, "blessing": "neutral", "text": "I made a Platformer Game where you are an astronaut and must navigate through caves to reach the flag. I’m very proud of the graphics and how much I’ve learned when it comes to coding in javascript, html, and css. I am also happy that this finally forced me to get better at using github to place the project into and make it easier to submit into stardance.", "repo": "https://github.com/oliviasophia67/Paint-Gravity-Platformer", "demo": "https://oliviasophia67.github.io/Paint-Gravity-Platformer/"}, {"ship_num": 3, "ts": "2026-06-29T21:09:31Z", "hours": 5.0, "multiplier": 13.29, "payout": 60, "blessing": "neutral", "text": "The project I worked on was a platformer game where you are an astronaut that paints to flip gravity by walking on it, to make its way out of a alien cave. Challenges for this project were honestly finding a way to start the project, as this was one of my first coding projects in JavaScript. Also part of what I struggled with was connecting the project to Hackatime and github to connect it to Stardance. Another thing that was difficult was adding in a level selection and menu with a tracker to keep track of the stars collected on each level. A couple things that I think went very well with this project was the graphics such as the astronauts paint gun, and the background along with the flag. I’m also happy about how the paint turned out with flipping gravity and its graphics.", "repo": "https://github.com/oliviasophia67/Paint-Gravity-Platformer", "demo": "https://oliviasophia67.github.io/Paint-Gravity-Platformer/"}]...
|
[{"post_id": 72014, "ts": "202 [{"post_id": 72014, "ts": "2026-09-22T00:36:16Z", "hours": 4.8328, "text": "Final Devlog Number 9!!! :) So this is the final devlog for the game, all bugs are fixed and the game is finished (for now) I may still work on some things in my spare time but since school started up it been hard to find the time to work on it. It is completed with levels, star completion, ghost racing, achievements, and smooth gameplay. I hope that all of you enjoy the project. I enjoyed working on this a lot. Thanks for all the support I got in the process!"}, {"post_id": 33175, "ts": "2026-07-22T20:49:21Z", "hours": 1.8244, "text": "Devlog 8 - Fixed All Issues! So like I described in my last devlog, I had a major issue that was continuing to pop up, and no matter what I did it was still there. Pretty much the issue was that the whole game froze when touching the flag, and it was caused because I forgot to define one of my variables correctly. The problem was that once I finally fixed this, I had to fix the issues I cause in the process of fixing this, such as the timer no longer working. Besides this I spent some time starting to make an achievements page, to show progress throughout the game."}, {"post_id": 32673, "ts": "2026-07-21T23:51:49Z", "hours": 2.5392, "text": "Bad News :( Devlog 7……. So I have spent the last day none stop working on a bug that I accidently made I think when adding in the timer, but honestly nothing I’ve tried has worked yet. I tried so many different ideas and asked anyone who knows coding but nothing has worked. pretty much the issue is that the astronaut freezes when touching the flag and nothing in the game works. I tried adding in a try …… catch function around the code where it shows what happens when you touch the flag and exactly what error happened, but for this nothing showed up, and in any debugger I try it sees nothing wrong with the code. I’ll add in a screenshot of what it looks like when it freezes, (ignore some parts at the top, I know they overlap) If anyone has an idea of what’s wrong I could really use it. Thanks y’all!"}, {"post_id": 31969, "ts": "2026-07-20T19:56:53Z", "hours": 1.0725, "text": "Paint Gravity Game Devlog! progress I made was I fixed the trajectory lines to show where the paint will end up going, along with this I worked on the tracking for the stars that you collect each level. Now there is a counter along with the total amount of possible stars, to show the progress made in the game. next i’m gonna make the grpahics on the menu and start menu much better."}, {"post_id": 27903, "ts": "2026-07-13T20:34:52Z", "hours": 0.3642, "text": "Another Devlog! I already have shipped this project once, and probably will again soon, but for now heres an update on what I worked on. Not much time was physically spent in the project, but in learning more about coding in java (which is what this project was for me), which for today took me more like an hour than what was logged. Specifically I learned more about the way to make the gun follow the mouse, and working on some of the graphics, such as the background behind the cave walls move. I also tried to think of more ideas, maybe a trajectory dots to show where the paint will go, I would like some advice or commets of what to add."}, {"post_id": 18660, "ts": "2026-06-29T20:59:57Z", "hours": 0.3661, "text": "This is now officially the last devlog I shall post for this project. First off I made most of the additions I said I would, specifically added in the waterfalls to remove paint, and worked on graphics, especially the background. Now I shall ship the project for rating, as well I added in a demo url to the info so people can now officially try it! I will start working on a new project soon, hopefully a longer and harder one."}, {"post_id": 14105, "ts": "2026-06-23T02:36:31Z", "hours": 0.5003, "text": "One of the last devlogs (hopefully) for this project. this will be a fairly short log, just describing the updates I’ve made to my game. Firstly, the changes I made was I added in a main menu with a title page and a way to go to level selection, to access levels as you unlock them. I also fixed some graphics such as the paint gun and the tutorial on the first and second levels to play the game. I made the paint even better as now it drips onto the ceiling, instead of the paint being the same anywhere it is. In this project I have been using HTML and JavaScript in VS code, so here’s an overview of what the code is composed of and what I used to program the game. Major types of functions that will be needed for coding this type of game is a draw function, which as it describes, draws the map, the game loop function and the load level function. Each of these or general loading for the game, along with functions that derive from variables. Making sure variables were defined correctly was also a main part of it. Only other thing I would like is some smaller details to add into the game. Some I was thinking of is maybe instead of just spikes have mini spikes fly across the amp in a timely order, maybe add a waterfall to some levels that when paint is shot through it it washes away, maybe a star rating system or stars to collect in the level, along with possibly making the background more fun and engaging. I would love some other ideas too!"}, {"post_id": 12936, "ts": "2026-06-21T05:28:28Z", "hours": 2.4497, "text": "This is another devlog I’ve posted for this project and I’m almost finished. I definitely fixed the graphics for the game, turning the white box into an astronaut, turning green half circles to plants, and made the theme of a alien cave (or tried to). Here’s the list of what I worked on recently: Obviously I mainly worked on graphics including the change to a pixel art theme, creating the flag and aura around it, made the paint drip to make it look more like paint gravity, and added a tutorial to learn the game along with controls at the top. Another main thing was the death mechanisms. I made spikes into the the levels that increase in difficulty as the levels continue, along with adding a reset button. At first the levels were also slightly simple as there was no limit to the ammo, which I now added to keep the levels hard, and make the game into a puzzle. There is a couple more things I need to add before posting this project for rating which is just to make the astronaut hold a paint gun (which I somehow forgot) and to add a menu for the levels of the game."}, {"post_id": 12300, "ts": "2026-06-20T02:06:08Z", "hours": 1.2378, "text": "First Devlog! So I just recently started working on this new platformer game in VS Code, and here’s what I’ve coded so far. Main thing I began were the basics. I set up the controls for the player, and added an ending goal to bring the player to the next level. I also added in platforms to jump on, and the animation for a paint gun that the player will shoot to win levels. Next I will be adding, gravity mechanics to the paint to change the gravity, making the spikes kill the player and force them to restart the level, and lastly work on the scene and art of the game."}]...
|
Title: Platformer Game by @Livvy | Stardance
Devl Title: Platformer Game by @Livvy | Stardance
Devlogs:
First Devlog! So I just recently started working on this new platformer game in VS Code, and here’s what I’ve coded so far. Main thing I began were the basics. I set up the controls for the player, and added an ending goal to bring the player to the next level. I also added in platforms to jump on, and the animation for a paint gun that the player will shoot to win levels. Next I will be adding, gravity mechanics to the paint to change the gravity, making the spikes kill the player and force them to restart the level, and lastly work on the scene and art of the game.
This is another devlog I’ve posted for this project and I’m almost finished. I definitely fixed the graphics for the game, turning the white box into an astronaut, turning green half circles to plants, and made the theme of a alien cave (or tried to). Here’s the list of what I worked on recently: Obviously I mainly worked on graphics including the change to a pixel art theme, creating the flag and aura around it, made the paint drip to make it look more like paint gravity, and added a tutorial to learn the game along with controls at the top. Another main thing was the death mechanisms. I made spikes into the the levels that increase in difficulty as the levels continue, along with adding a reset button. At first the levels were also slightly simple as there was no limit to the ammo, which I now added to keep the levels hard, and make the game into a puzzle. There is a couple more things I need to add before posting this project for rating which is just to make the astronaut hold a paint gun (which I somehow forgot) and to add a menu for the levels of the game.
One of the last devlogs (hopefully) for this project. this will be a fairly short log, just describing the updates I’ve made to my game. Firstly, the changes I made was I added in a main menu with a title page and a way to go to level selection, to access levels as you unlock them. I also fixed some graphics such as the paint gun and the tutorial on the first and second levels to play the game. I made the paint even better as now it drips onto the ceiling, instead of the paint being the same anywhere it is. In this project I have been using HTML and JavaScript in VS code, so here’s an overview of what the code is composed of and what I used to program the game. Major types of functions that will be needed for coding this type of game is a draw function, which as it describes, draws the map, the game loop function and the load level function. Each of these or general loading for the game, along with functions that derive from variables. Making sure variables were defined correctly was also a main part of it. Only other thing I would like is some smaller details to add into the game. Some I was thinking of is maybe instead of just spikes have mini spikes fly across the amp in a timely order, maybe add a waterfall to some levels that when paint is shot through it it washes away, maybe a star rating system or stars to collect in the level, along with possibly making the background more fun and engaging. I would love some other ideas too!
This is now officially the last devlog I shall post for this project. First off I made most of the additions I said I would, specifically added in the waterfalls to remove paint, and worked on graphics, especially the background. Now I shall ship the project for rating, as well I added in a demo url to the info so people can now officially try it! I will start working on a new project soon, hopefully a longer and harder one.
Another Devlog! I already have shipped this project once, and probably will again soon, but for now heres an update on what I worked on. Not much time was physically spent in the project, but in learning more about coding in java (which is what this project was for me), which for today took me more like an hour than what was logged. Specifically I learned more about the way to make the gun follow the mouse, and working on some of the graphics, such as the background behind the cave walls move. I also tried to think of more ideas, maybe a trajectory dots to show where the paint will go, I would like some advice or commets of what to add.
Paint Gravity Game Devlog! progress I made was I fixed the trajectory lines to show where the paint will end up going, along with this I worked on the tracking for the stars that you collect each level. Now there is a counter along with the total amount of possible stars, to show the progress made in the game. next i’m gonna make the grpahics on the menu and start menu much better.
Bad News :( Devlog 7……. So I have spent the last day none stop working on a bug that I accidently made I think when adding in the timer, but honestly nothing I’ve tried has worked yet. I tried so many different ideas and asked anyone who knows coding but nothing has worked. pretty much the issue is that the astronaut freezes when touching the flag and nothing in the game works. I tried adding in a try …… catch function around the code where it shows what happens when you touch the flag and exactly what error happened, but for this nothing showed up, and in any debugger I try it sees nothing wrong with the code. I’ll add in a screenshot of what it looks like when it freezes, (ignore some parts at the top, I know they overlap) If anyone has an idea of what’s wrong I could really use it. Thanks y’all!
Devlog 8 - Fixed All Issues! So like I described in my last devlog, I had a major issue that was continuing to pop up, and no matter what I did it was still there. Pretty much the issue was that the whole game froze when touching the flag, and it was caused because I forgot to define one of my variables correctly. The problem was that once I finally fixed this, I had to fix the issues I cause in the process of fixing this, such as the timer no longer working. Besides this I spent some time starting to make an achievements page, to show progress throughout the game.
Final Devlog Number 9!!! :) So this is the final devlog for the game, all bugs are fixed and the game is finished (for now) I may still work on some things in my spare time but since school started up it been hard to find the time to work on it. It is completed with levels, star completion, ghost racing, achievements, and smooth gameplay. I hope that all of you enjoy the project. I enjoyed working on this a lot. Thanks for all the support I got in the process!
Ships:
The project I worked on was a platformer game where you are an astronaut that paints to flip gravity by walking on it, to make its way out of a alien cave. Challenges for this project were honestly finding a way to start the project, as this was one of my first coding projects in JavaScript. Also part of what I struggled with was connecting the project to Hackatime and github to connect it to Stardance. Another thing that was difficult was adding in a level selection and menu with a tracker to keep track of the stars collected on each level. A couple things that I think went very well with this project was the graphics such as the astronauts paint gun, and the background along with the flag. I’m also happy about how the paint turned out with flipping gravity and its graphics.
I made a Platformer Game where you are an astronaut and must navigate through caves to reach the flag. I’m very proud of the graphics and how much I’ve learned when it comes to coding in javascript, html, and css. I am also happy that this finally forced me to get better at using github to place the project into and make it easier to submit into stardance.
I completed a game where you jump through obstacles and change gravity to move through each level. As an astronaut, you use a paint gun to change your gravity based on the corresponding color. I’m proud of this being my first big project in java and HTML and CSS, and that this was my first time using VS Code. Also the paint mechanics working was a big accomplishment. A struggle was getting the flag to work after something I added along the way caused a bug and I didn’t realize to way later. It took a while but I got it working! I hope everyone enjoys the project....
|
1793883068.5670195
|
1793969468.5670195
|