TOTEM VS Serializer

Wired Totem from keeb.supply needs a reset every time I start my Win10 pc, otherwise it works as usual. it says "USB device not recognized". Tested on multiple pcs and cables. Asked on their discord but they haven't heard this problem before. Nuked and reflashed with the given files multiple times, checked again the soldering but didn't help. If it works perfectly fine after reset or connecting to an already running pc, what might be wrong? Is there a watchdog feature that sends a reset signal the moment it gets power? My repo.

You just need a new keyboard 🙃

I built a TOTEM[1] (same creator) and it looks stunning. Was a breeze to get manufactured (both PCB and resin printer case from jlcpcb, in my case) and assemble too!

The build guide is very informative and quirky, it has everything from tips in how to solder smd diodes to "use a sharpie to paint the PCB sides black so it looks nicer", way better than some expensive kits I've bought in the last few years!

1. https://github.com/GEIGEIGEIST/TOTEM

There are some pads on the underside of the XIAO controller that we need to connect to. The footprint that I am using here has plated through-holes with edge cuts with enough space to allow you to use a soldering iron from the bottom to solder the plated through-holes to the pads. This approach was borrowed from Totem so it should work but I am worried about manufacturing issues due to the DRC failures there.

Here you can find the PCB and case files and of course a buildguide. Here is a Hackster post covering my process. I hope it's ok to mention, that you can also buy complete kits on keeb.supply by now.

Thanks! The KiCad files are open source, you can figure out how to add a number row, I believe in you! build guide

design your own case – take a look at the bottom of GEIST’s TOTEM

add an extra pinky key – popularized by Jian and seen in Totem

as u/Tulip2MF mentions, GEIST did the TOTEM for SEEED XIAO challenge and showed it off with a clear case and keycaps

Making a class "final" is always a bad decision IMO. You would never know how will other people use your library. For example, we used JMSSerializerBundle and wanted to extend DateHandler to make it not to throw exceptions if a date string is invalid. But the class is final. So we had to just copy-paste it :(

Or this popular alternative: https://jmsyst.com/libs/serializer

JMS Serializer: This library allows you to (de-)serialize data of any complexity. Currently, it supports XML and JSON.

Only took a very brief look, but it looks nice. I like that the DTO class isn't required to extend anything, and that it seems to be for real DTOs used for actual transfer of data between systems - not 'local dtos'. It feels like this might be more comparable to something like schmittjoh/serializer rather than spatie/data-transfer-object.

When it's time to create the PDF, convert the object structure to an XML using an already existing serializer (like JMS or symfony serializer) or do this by hand.

One frequently used serializer is JMS Serializer which allows you to convert JSON or XML to objects (or the other way around if needed). You can then use the objects in your application.