I added another day of Bible reading and started 2 Corinthians! I also added a little bit of CSS to have enough time to post this because my sticky streak isn’t updating.
I added another day of Bible reading and started 2 Corinthians! I also added a little bit of CSS to have enough time to post this because my sticky streak isn’t updating.
Since this website is made to have something to work on daily for the Sticky Streak challenge, I will be working on this project for 3 weeks, with 20 posts by the end (hopefully!)
I have not written any CSS yet, I plan on doing that if I can’t find enough to write about for 5 minutes, but so far that hasn’t been an issue.
The reason the first firmware didn’t work is because the D# pins didn’t map directly to GP# pins, so it was listening for phantom pins that weren’t even on the microcontroller. Then the laptop had numlock on by default with no way to turn it off because it doesn’t have a numberpad or numlock key, so it wasn’t doing what was expected.
After changing the pins correctly, the firmware wouldn’t compile and threw a bunch of errors, so I tested adding layers to the standard firmware QMK autogenerates.
Once that got compiled, I tried to flash it to the board and I couldn’t get it into bootloader mode.
I then tried a different laptop and it worked just fine.¯_(ツ)_/¯
I’m mostly done assembling, flashed my firmware to the macropad, and it does nothing. I plan on flashing the standard QMK firmware it creates and checking if that does anything to make sure that the assembly was done correctly.
I brought Ace of Sharks to a tournament and it held up way better than last time.
I tied four other robots for 5th place and had a great time talking with and learning from other builders :)
I added new wheel guards to Ace of Sharks (don’t mind the bright red, it’s just a test with random filament) and tested a bunch of wheel combos.
The wheel guard print worked the first time (!), and seems ready. In the Duramic PLA+ filament, Ace of Sharks should be underweight and ready for a possible tournament next week!
I tried rubber cement coated wheels to try to improve traction, and it worked really well. I also added rubber bands wrapped around the rubber cement, and that improves traction as well. That is probably what I will do in the tournament, and we will see how it works in a fight. Rubber cement does pick up dust, but a damp cloth will wipe it off and not significantly reduce stickiness. (I forgot to lapse the testing and chassis swap during the Stardance huddle, oops… )
Well, I forgot to devlog, so here’s an update of all that I have changed.
I will continue to update these pages and I only have a draft of each of these, so hopefully I will remember to devlog more frequently :)
Quite a few of the reviews I got on the last ship said that I should add more of a UI, so now I started trying to do that. So far, I have tried Tkinter to create a GUI (Same as in my other project Bible Clock), but it is harder than I expected. I have dropdown menus working so far and am (sometimes) able to get the unit into the code, but the number input fields are not doing what it seems like they should.
I looked at creating a website, but I don’t know JavaScript and I will need that to create a dropdown menu and do the math.
Maybe I will end up learning JavaScript instead of learning Tkinter :)
So far, I have:
I also decided I want to improve wheel traction (the grippiness of the wheel) to hopefully get more pushing power. I don’t have time to get funding, design, and iterate a cast polyurethane wheel for this tournament, so I decided I will get rubber cement and experiment with gluing rubber bands, electrical tape (sticky side out), and latex balloons to the foam wheels and see what works best.
I brought Ace of Sharks 3.1 to a tournament and it went pretty well! I defiantly found some bugs that need fixed (like the whole weapon assembly falling off) but I was still able to lift other robots and the concept worked great.
There was no four wheel drive for this iteration, but that will come soon as well as wheel guards and a stronger attachment point for the lifter assembly.
I am ready to ship, with the tournament highlight video as the demo video for Ace of Sharks.
Stay tuned to Ace of Sharks as I will continue to improve Ace of Sharks 3.2 to prepare for another tournament before Stardance is over!
Edit for shipwrights because I can’t edit the ship post: I hope bonuses will retroactively apply as well as payout increases. I have a logo I make into stickers to give out a tournaments (a new one for v3 and I have three other Ace of Sharks logos I wish I could show you but I can’t add more pictures to a devlog), I edited a highlight video myself (that’s the demo video) and I designed the poster myself. I worked really hard on making this project do well in voting, so I am disappointed at the fixed 5 stardust an hour payout rate. The fixed payout makes sense with the way Stardance is formatted; it’s just disappointing because of how hard I worked on this project, trying to get 15-20 stardust an hour.
I learned more commands in tkinter for adding background color, text padding (though I can’t get the text centered vertically) and window size.
I also added some more randomness to the verses with the books with a certain match being only if the random book does not have one.
If anyone knows how to center the text vertically, I would appreciate a suggestion.
Before, the clock started whenever you started the program and changed time one minute (plus web scraping time) later. Now, the clock will change within 2 seconds of the real clock (no web scraping time included)!
This was harder than I expected because time.sleep will freeze the GUI.
There is a weird bug where some of the time, it just pops up a blank screen (no text at all). But that only happens some of the time, so I’m not sure what is causing that. Any suggestions would be appreciated!