- exposed strain SCK and DO
- use 12 bit PWM (instead of 16 bit) for screen brightness on s3
- added option to use uart serial for s3
- bump nanopb/Nanopb @ 0.4.7
- fixed SPI bus alias and DMA channel for s3
---------
Co-authored-by: Scott Bezek <scottbez1@gmail.com>
- reworked smartknobjs into separate smartknobjs-node and
smartknobjs-webserial packages
- configured CI to build and deploy webserial example to
https://scottbez1.github.io/smartknob/
Seems to be causing weird behavior/performance with the motor control loop, particularly noticeable with fine detents. Reverting for now until I have a chance to investigate further.
This reverts commit 1d73af17cc.
- New Configuration class for managing persistent configuration
- New proto messages for serialized configuration, with flexibility for
expansion
- Load persistent configuration at startup, if available, use for
default motor calibration
- Save motor calibration to persistent configuration file
- Breaking proto updates
- added position nonce to config, and added ability to specify a
sub_position via config as well => more flexibility to control position
via config
- added version as first field of serial protocol messages, so future
breaking proto updates can easily be detected and ignored
- Fixed up web-based demo of a mock video editor/timeline jog/playback
controller
- Fixed config/state flow so that mode changes correctly maintain
playback position
- Demo: https://www.youtube.com/watch?v=J9192DfZplk
I would suggest using `drawNumber` instead of drawString to align each
digit of the number to the same width and erase the jittering effect
when the current position is changed.
- New PlatformIO env (`nanofoc`) for the NanoFOC hardware
- Huge thanks to @lgc00 for the initial NanoFOC configuration and prototyping!
- Uses `HWCDC` rather than `UartStream` as the serial `Stream` interface (ESP32-S3 specific change)
- Support for MAQ430 magnetic encoder sensor
- Motor-specific PID tuning constants moved to separate header files
---------
Co-authored-by: lgc00 <lgcasd1+1@gmail.com>
Breaking change to protobuf messages to support new detent configurations - adds more flexibility compared to existing config parameters (e.g. min/max position rather than just number of positions).
New magnetic detent mode allows for config to specify up to 5 nearest detent positions (with smooth scrolling in between them); the intent is a higher-level controller (e.g. connected demo app, see below) to dynamically update that list as the position changes, in order to support an unlimited number of magnetic detents.
---
React demo app implements a mock video editor timeline, with the ability to interact with it via the SmartKnob connected over USB serial. (Currently uses a node backend to stream config/state to the frontend via websockets, but it would probably be possible to do everything on the frontend with webserial in the future?).
The 3 demo input modes are:
- Scroll: quickly smooth-scroll through the timeline, with magnetic detents at clip boundaries. Scroll speed is determined by zoom level (currently only controllable by mouse scroll wheel)
- Frames: small detents (1.5 degrees) to move frame-by-frame through video
- Speed/playback: "spring-loaded" speed control, biased to return to center (paused), with detents at powers of 2: 1x, 2x, 4x playback
Currently the frontend app has some bugs, particularly with the current playback position when switching modes and zooming, but planning to merge anyway to get the other breaking changes into master along with the initial demo framework.
Windows upper cases the vendor and product id, so the filter will fail.
So LOWERCASE ALL THE THINGS!
Co-authored-by: Crosseye Jack <dan@crosseyejack.com>
- Firmware
- Refactor all code to use a log interface rather than `Serial` directly
- Moved platformio.ini to root, so you can load the entire repo in VS Code and still use platformio
- Reduced graphic buffer bit depth to 8 bits (short on RAM :( )
- Implemented threadsafe log interface in interface_task (using a queue for posting log message)
- Created serial protocol interface and 2 implementations - plaintext (default) and protobuf (selected by sending a NULL byte)
- Protobuf protocol is roughly the same architecture as Splitflap's:
- PacketSerial (cobs) framing with NULL delimiters
- CRC32 checksums for packets
- nanopb generated code for encoding/decoding (generated firmware code is checked in, since it should change less frequently and this reduces burden to build the project from scratch)
- Software
- Typescript example host-side code:
- smartknobjs-proto
- Autogenerated types/encoding/decoding protobuf code (using protobufjs)
- smartknobjs
- Helper library for interfacing the with smartknob via serial/protobuf. Implements basic outgoing queue (with retries and ACK checking) and message callback for responding to messages from the SmartKnob
- example
- Basic demo CLI app that uses smartknobjs to connect to the smartknob, send a haptic config, and print state changes and log messages to the console
The voltage regulator that was originally used isn't available at the moment. To provide more options, a second footprint was added to the PCB for an alternative regulator that has a different pinout. Important to note that only one regulator should be used.
Also, adjusted .gitignore for Mac files and KiCad auto-generated backups.
- Updated view_base and view_screen KiCad projects to v6 files
- Updated footprints to v6 versions
- Fixed all DRC errors and most warnings
- Updated CI
- Run on Ubuntu 22.04 runner
- Updated KiBot and KiKit versions
- Use KiBot for 3d rendering now instead of custom scripts
- Switched to using KiCad text variables for replacement rather than raw text find&replace
- Misc design updates
- Exposed bottom-side thermal pad underneath TMC6300 to make it easier to possibly hand-solder
- Separated GND and GNDA nets, replaced connection with a net-tie, and updated corresponding copper fills around HX711
Removed some legacy platformio envs that are not actively being maintained. But also fixed some bugs with different build flags that caused compilation issues.
Fixes#49