scottbez1 / smartknob Goto Github PK

There are many projects that try to mechanically present an interface for users to input XYZ movement and Yaw Pitch Roll for interaction with models in 3D space. The use of BLDC motors in addition to or in place of potentiometers, rotary encoders, and similar electro-mechanical sensors could greatly improve the user experience ans simplify the mechanical design. Rather than having to find a mechanical device that was designed for the way the user intuitively wants to give input, the user could purchase a device that fits a much larger market and customize it through software to deliver the experience that allows each user to stay in flow and not be distracted by the hardware interface.

Note: This is constitutes Prior Art. The feature described is currently in development and offered freely to the public domain and may not be used in patents.

Next to the left/right mounting holes where there is room, add pins and matching PCB holes for help aligning the base PCB with the back plate when mounting it.

I used TMC6300 and 3215 motor, looks like there's no torque when base PCB is powered.

Not a major issue as you've said you've got several others on the way for testing, but the link to the motor you used is now out of stock: AliExpress

This a an amazing work both in enginering and designing. I really apperiate it.
But there is one thing I couldn't understand. MountBase is covering the MT6701 sensor. Both are stationary. And I didn't see any magnet using in the CAD file. I could not figure out what magnet feild the MT6701 is sensing. Maybe there is a donut shaped magnet attached to the rotor? Could you please explain it a littele bit? Maybe in your next video. Thanks in advance.

Sorry, this is not an issue at all. I just wanted to say excellent work! This is a very creative project. You basically made a force feedback steering wheel. I'm a developer at iRacing.com, if your ever curious about making it work with DirectInput let me know. And if you ever get it to a commercial state I would love to add it into our video game, our members would be ecstatic to have something like this to make brake bias adjustments.

Hi there,

as you've mentioned multiple times in the readme, working with strain gauges isn't trivial, so it's easy to screw up when mounting them to the PCB. You can practice mounting them somewhere else beforehand of course, but that means ordering more units than you'd actually need.

I'm currently working on a project where I also need to detect pressure being applied to something, and I've found that Force-Sensitive Resistors (FSRs) are quite easy to work with and offer a straight-forward implementation when it comes to measuring force.
Here's an example of what I'm talking about
They usually are a bit more expensive, but as I mentioned, working with them is probably easier than using strain gauges.

Maybe give them a try? :)

Hi,

First thanks a lot for this amazing piece of DIY. Great to get a hands on feeling of haptic feedback.
I am having a little trouble flashing the firmware and getting it to work. First, on the master branch only the view env compiles (which I believe is normal looking at the dependencies). After flashing the view build I get stuck in the following bootloop :

`ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 271414342, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Sprite created!
millilux: 1764.00
Guru Meditation Error: Core 1 panic'ed (Unhandled debug exception)
Debug exception reason: Stack canary watchpoint triggered (Motor)
Core 1 register dump:
PC : 0x400dfa22 PS : 0x00060836 A0 : 0x800e51e5 A1 : 0x3ffb8220
A2 : 0x00000000 A3 : 0x3ffb8414 A4 : 0x00000000 A5 : 0x00000000
A6 : 0x3ffb8600 A7 : 0x00000008 A8 : 0x3ffb8530 A9 : 0x3ffb8210
A10 : 0x3ffb8230 A11 : 0x3ff9c510 A12 : 0x000000ff A13 : 0x0000ff00
A14 : 0x00ff0000 A15 : 0xff000000 SAR : 0x00000020 EXCCAUSE: 0x00000001
EXCVADDR: 0x00000000 LBEG : 0x400014fd LEND : 0x4000150d LCOUNT : 0xffffffff

ELF file SHA256: 0000000000000000

Backtrace: 0x400dfa22:0x3ffb8220 0x400e51e2:0x3ffb8530 0x400e521a:0x3ffb85c0 0x400da45a:0x3ffb8600 0x400d3cfb:0x3ffb86a0 0x400d5218:0x3ffb86d0 0x400d3152:0x3ffb8700 0x400d2cdd:0x3ffb8850 0x400883f2:0x3ffb8870

Rebooting...
`

Should I assume bad soldering on the TMC6300 ? Is there something else I am missing ?

Thanks a lot

I think adding support for ethernet with poe can help in cases where latency is important, it also makes power distribution easier.

It may not be convenient in all cases, therefore I propose to create two versions, the normal one and the one with ethernet and poe support.

I purchased components from online shop, when soldering it's quite tricky to get the right direction for LEDs, need your PCB boards for reference. Appreciated for your efforts.

Would it be possible to include a simple pick & place file in addition to the bom?
I'm not that experienced with smd soldering and would like to order the pcbs already assembled at factory, at least for the general stuff like resistors and capacitors.

--- Miniterm on COM6 115200,8,N,1 ---
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 271414342, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Sprite created!
millilux: 26236.80
millilux: 26949.60
Press Y to run calibration
Ymillilux: 26942.40
millilux: 27057.60
millilux: 26697.60
millilux: 27021.60

Sensor measures positive for positive motor rotation: YES, Direction=CW
Guru Meditation Error: Core 1 panic'ed (Unhandled debug exception)
Debug exception reason: Stack canary watchpoint triggered (Motor)
Core 1 register dump:
PC : 0x400dfaf1 PS : 0x00060c36 A0 : 0x800e5255 A1 : 0x3ffb8280
A2 : 0x00000000 A3 : 0x00000011 A4 : 0x00000001 A5 : 0x3f404396
A6 : 0x3ffb8660 A7 : 0x00000008 A8 : 0x3f404385 A9 : 0x3ffb8474
A10 : 0x3ffb8290 A11 : 0x3ff9c510 A12 : 0x000000ff A13 : 0x0000ff00
A14 : 0x00ff0000 A15 : 0xff000000 SAR : 0x0000001d EXCCAUSE: 0x00000001
EXCVADDR: 0x00000000 LBEG : 0x400014fd LEND : 0x4000150d LCOUNT : 0xffffffff

ELF file SHA256: 0000000000000000

Backtrace: 0x400dfaf1:0x3ffb8280 0x400e5252:0x3ffb8590 0x400e528a:0x3ffb8620 0x400da4ca:0x3ffb8660 0x400d3280:0x3ffb8700 0x400d2ced:0x3ffb8850 0x400883f2:0x3ffb8870
#0 0x400dfaf1:0x3ffb8280 in _svfprintf_r at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdio/../../../.././newlib/libc/stdio/vfprintf.c:929
#1 0x400e5252:0x3ffb8590 in _vsnprintf_r at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdio/../../../.././newlib/libc/stdio/vsnprintf.c:72
#2 0x400e528a:0x3ffb8620 in vsnprintf at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib

It's a little tricky to ensure the LCD is perfectly centered relative to the screen PCB (and therefore the rest of the mechanics and knob window) when permanently mounting it with VHB, so it might be nice to have a small 3d-printable jig to help with alignment.

It would hold the screen PCB (with alignment pin to ensure correct rotation) and have walls that align the LCD. Might be tricky since the LCD will be rotating down via its ribbon cable rather than simply translating straight down, but could be nice to get better overall alignment considering how permanent VHB is.

(If anyone tackles this, note that the existing LCD model in the F360 file is only a rough depiction based on a handful of dimensions from the datasheet. It would probably be best to put the LCD on a flatbed scanner to ensure dimensional accuracy)

Quick question only sort of related to your project - how did you solder the strain gauges? I bought some of a similar kind a while ago for a different project but I couldn't figure out how to reliably connect to the pads on the gauge without destroying it.

Latest Fusion 360 Model: https://a360.co/3BzkU0n

I think this project is really cool. I was hoping you could share detailed specs of the motor so we can find a suitable replacement that can potentially just drop right in.

Thanks,
Maxwell

It's not working on my side, before fixed strain gauges on PCB, I just want to validate strain gauges is originally working with HX711.

There's current on 6 pads for strain gauges, but no response(the screen keeps showing Unbounded No detents which is the mode by defaut) when I touched 4 strain gauges when powered.

See the pciture depicted below, the screen moved when I assembled, there's not slot to fix the screen.

Much like some logitech scroll wheels implementing a long running scroll with the motor kicked off by initial user interaction would feel lovely on this project. Seeing it decelerate on the display too would feel soo nice.

@scottbez1 Hi Scott, I soldered all most components on base PCB, when connected PCB board with PC, it looks good from PlatformIO monitor from VSCode, but TMC6300 is so hot, do you know which component is short or some other reasons?

The current detent configuration is pretty flexible (number of detents, size of detents, strength, etc), but isn't the only kind of haptic feedback you might want to provide.

Idea is to extract a lot of the existing detent-specific code into a DetentEngine implementation of a more general (and swappable) HapticEngine interface. The HapticEngine interface would mostly just take the current mechanical angle as input and return a torque value as output.

Other implementations might be a jog/shuttle engine which might have stops placed for 1x, 2x, 10x playback rates in either direction, or an inertial smooth scroll engine (it remains to be seen if this can be implemented well with the current control system).

MJF prints of the rotor and rotor spacer fit together well, but could use a separable snap fit feature to retain the knob/rotor once it's pushed all the way down onto the spacer.

Once the screen PCB is mounted to the motor mount base, and that is mounted to the base pcb, the screen's wires prevent the PCB from being lifted, so you can't easily access the wire solder points for probing.

It would be nice to have testpoints for all the screen wires on the top side of the PCB, so you can probe each one to determine which wire is which when soldering them to the base PCB.

Building in release mode
Retrieving maximum program size .pio\build\view\firmware.elf
Checking size .pio\build\view\firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [= ] 5.4% (used 17648 bytes from 327680 bytes)
Flash: [=== ] 27.3% (used 357450 bytes from 1310720 bytes)
Configuring upload protocol...
AVAILABLE: esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...
Auto-detected: COM3
Uploading .pio\build\view\firmware.bin
esptool.py v3.1
Serial port COM3
Connecting......................................_____

A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
*** [upload] Error 2
================================================================================================================================ [FAILED] Took 28.07 seconds ================================================================================================================================
Environment Status Duration

view FAILED 00:00:28.074
=========================================================================================================================== 1 failed, 0 succeeded in 00:00:28.074 ===========================================================================================================================The terminal process "C:\Users\zinwa.platformio\penv\Scripts\platformio.exe 'run', '--target', 'upload', '--environment', 'view'" terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

Per HX711 datasheet: (R1 in datasheet is R3 on view base, R2 in datasheet is R4 on view base)
V AVDD =V BG *(R1+R2)/R2

So with R1(aka R3)=20k, this comes out to 1.25V*(20k+8.2k)/8.2k = 4.3V which is higher than VSUP (3.3V).

Changing R1(aka R3) to 10k, we get 1.25V*(10k+8.2k)/8.2k = 2.77V which fulfills 2.6-5.5V range, and is a "minimum of
100mV below VSUP voltage" as recommended by the datasheet.

This should make the analog voltage supply more resilient to noise on the 3.3V rail.

A quick suggestion: ESPHome is an exceptionally well though-out modular environment where most of the work has been done in terms of integration with many third party systems. If you would develop your I/O as an ESPHome component, you could save tons of work and concentrate on your special features supported by the hardware.

Also have a peak at OpenHASP on how LVGL is approached. It hardly relies on touch functionality, though, so may not be appropriate here.

Hello, I saw your video yesterday for the first time and was blown away. I always wanted such a thing, but DIY and not like the Nest thing. I directly made a shopping list for all parts and had no problem to find all the parts besides the BLDC Motor. And also the price for all parts with shipping to Germany is around €85, pretty good. And if the shipping cost for the PCBs weren't that high, it would be even cheaper.

Likewise, I first used the link to find the motor isn't for sale anymore. So I thought maybe find it somewhere else on the internet, but... google pictures said No. I really tried to find the thing with all the product pictures the names of the specifications, but I didn't find it. The only seller for the motor in my opinion was AliExpress. I couldn't find another platform where you could buy this exact motor.

The only motor of similar size I could spot was a bit bigger one

I could use the smaller motor, but you said on your other branch "moderate cogging - not ideal for completely smooth input". I ordered this one, but do you think it is relatively easy to remodel the design for the 34 mm Version? Or is there definitely not enough space, so I had to remodel the complete exterior covering?
Maybe you found a better motor till now.

Happy to hear from you 👍

Could use another ~0.5mm between LCD and the inside/inner-bottom face of the knob, to account for assembly imperfections, to ensure the knob doesn't scrape on the screen.

It should be ok to decrease the vertical clearance below the screen pcb correspondingly; there's more clearance here than necessary.

Currently on the master branch only the view target will compile.

Environment Status Duration

proto FAILED 00:00:04.469
view SUCCESS 00:00:43.869
handheld FAILED 00:00:07.100
handheld_tdisplay FAILED 00:00:06.988

The handheld and handheld mods seem to be a bit behind master, but do compile ok.

Hi! Thanks for open sourcing this project. Looks amazing! I am looking into integrate this into my hobby IoT project. I am curious what the current consumption. My IoT project takes in power through usb 2.0, so in total 500 mA.

I had a look at your design (which is fantastic!) and I couldn't help but notice you're using the MT6701-CT for positional encoding. Let me first state: That's fine. The MT6701-CT is a fantastic chip but it has two issues:

• It's expensive (like $2/each in bulk)
• It requires a relatively expensive ($0.25/each) diametrically-magnetized disc magnets that are kind of hard for every day people to source.

For my Void Switch keyboards (https://github.com/riskable/void_switch) I came up with an analog rotary encoder design (well, several of them actually) that utilizes just two super cheap ($0.09/each) GH39FKSW (or OH49E-S) linear hall effect sensors with ultra cheap ($0.01/each) 4x2mm (or 4x1mm) magnets to perform the same exact job as a single MT6701-CT.

Here's a screenshot of what the simplest version looks like:

The little white circles represent the location of the magnets. They're alternating N/S and since the sensors are analog the resolution is configurable just like the detents/tactile feedback you've come up with for your smart knob. The rest of it should be pretty self-explanatory but I can provide intimate details if you want (including the conditional "truth table" that determines knob direction/motion).

The only downside to this method is it requires 6 magnets (or as many as you want if you desire a bigger ring; just make it an even number--my Riskeyboard 70 I'm typing on uses a ring of 12) instead of just one like with the MT6701-CT.

There's also a way you can do away with your strain gauges (though that's super clever I love it) to add a pushbutton feature by simply adding a 3rd hall effect sensor in the middle and using a mechanical setup like so:

https://gfycat.com/fabulouscostlyblackrhino

Anyway, this is totally not important. Just a way to save a couple bucks per PCB.

Would it be possible to also apply power from underneath, and not the USB-C port?

In a wall-mounted setup, having a USB plug sticking out would make it look dull. Instead, one could mount on top of a junction box within a wall, with a power supply underneath.

It's essentially impossible to align all the 30AWG wires into a service loop without overlapping, so if you actually follow the indicated silkscreen marks you'll end up with overlapping wires that are taller than the extra thin VHB tape. I found it worked better to just skip the service loops (which I don't think were usable anyway due to the tight clearances).

First of all thanks for open-sourcing this awesome design! I just noticed that the readme states the screen PCB must be 1.2mm thick ("Ordering notes: Must be 1.2mm thick (not "standard" 1.6mm) per mechanical design.") but on the silkscreen of the PCB there's a big "0.6mm thick" label. Probably just a small copy and paste mistake from the ordering notes of the base PCB, thought I'd mention it anyway.

PS: Can't wait for my PCB and parts to arrive and build one up. :-)

I didn't receive all components, no strain gauge at the moment, when I touch pins on strain gauge position, the mode is changed.

Please build project in debug configuration to get more details about an exception.
See https://docs.platformio.org/page/projectconf/build_configurations.html

--- Miniterm on COM3 115200,8,N,1 ---
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 271414342, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
use SENSOR_MT6701
MOT: Monitor enabled!
MOT: Init
MOT: Enable driver.
millilux: 165384.00
MOT: Align sensor.
MOT: Skip dir calib.
MOT: Skip offset calib.
millilux: 165470.39
MOT: No current sense.
MOT: Ready.
Press Y to run calibration
millilux: 165484.80
millilux: 165484.80
millilux: 165441.61
7.34
Got new config
millilux: 165441.61
millilux: 165441.61
millilux: 165441.61

With which integrated could I replace TMC6300-LA but which one can I find on Aliexpress? (DRV8316 is still not on Aliexpress)

To avoid LED light leakage around the LCD, it might make sense to increase the PCB's diameter. Might also be helpful to add silkscreen alignment marks on the top side to help with centering the LCD.

Need to make sure it's still narrow enough for the knob/rotor to slide past it during assembly.

On macOS, there's a kind of difference on date/convert commands.

I wonder how much power this uses and whether it would be feasible for battery-powered or low-power products. Presumably the consumption differs based on usage (artificial detents, no motor usage etc.)

Imagine a scroll wheel that had the inertial scrolling commonly seen on multi-touch trackpads. But because the motion could be physically represented by the driven motor, the software could adapt to the user. The user could have dents until they fling it. The fling could have friction that lessens if the user give additional flings upon slowing.

Note: This is constitutes Prior Art. The feature described is currently in development and offered freely to the public domain and may not be used in patents.

LOG:

Executing task in folder test: C:\Users\wlj.platformio\penv\Scripts\platformio.exe run --target upload --target monitor <

Processing view (board: esp32doit-devkit-v1; platform: [email protected]; framework: arduino)

Verbose mode can be enabled via -v, --verbose option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32doit-devkit-v1.html
PLATFORM: Espressif 32 (3.4.0) > DOIT ESP32 DEVKIT V1
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (esp-prog) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:

• framework-arduinoespressif32 3.10006.210326 (1.0.6)
• tool-esptoolpy 1.30100.210531 (3.1.0)
• tool-mkspiffs 2.230.0 (2.30)
• toolchain-xtensa32 2.50200.97 (5.2.0)
  LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
  LDF Modes: Finder ~ chain, Compatibility ~ soft
  Found 37 compatible libraries
  Scanning dependencies...
  Dependency Graph
  |-- 2.2.0
  | |-- 1.0
  | |-- 1.0.1
  |-- 1.0.3
  | |-- 1.0.1
  |-- 1.9.1
  |-- <TFT_eSPI> 2.4.25
  | |-- 1.0
  | | |-- 1.0
  | |-- 1.0
  | |-- 1.0
  |-- 3.5.0
  | |-- 1.0
  |-- 0.7.5
  |-- 1.1.1
  | |-- 1.11.3
  | | |-- 1.0.1
  | | |-- 1.0
  | |-- 1.0.1
  | |-- 1.0
  Building in release mode
  Retrieving maximum program size .pio\build\view\firmware.elf
  Checking size .pio\build\view\firmware.elf
  Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
  RAM: [= ] 5.4% (used 17648 bytes from 327680 bytes)
  Flash: [=== ] 27.3% (used 357434 bytes from 1310720 bytes)
  Configuring upload protocol...
  AVAILABLE: esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
  CURRENT: upload_protocol = esptool
  Looking for upload port...
  Auto-detected: COM6
  Uploading .pio\build\view\firmware.bin
  esptool.py v3.1
  Serial port COM6
  Connecting......
  Chip is ESP32-PICO-D4 (revision 1)
  Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
  Crystal is 40MHz
  MAC: 4c:75:25:a8:34:50
  Uploading stub...
  Running stub...
  Stub running...
  Changing baud rate to 460800
  Changed.
  Configuring flash size...
  Auto-detected Flash size: 4MB
  Flash will be erased from 0x00001000 to 0x00005fff...
  Flash will be erased from 0x00008000 to 0x00008fff...
  Flash will be erased from 0x0000e000 to 0x0000ffff...
  Flash will be erased from 0x00010000 to 0x00067fff...
  Compressed 17104 bytes to 11191...
  Writing at 0x00001000... (100 %)
  Wrote 17104 bytes (11191 compressed) at 0x00001000 in 0.5 seconds (effective 265.5 kbit/s)...
  Hash of data verified.
  Compressed 3072 bytes to 128...
  Writing at 0x00008000... (100 %)
  Wrote 3072 bytes (128 compressed) at 0x00008000 in 0.1 seconds (effective 428.9 kbit/s)...
  Hash of data verified.
  Compressed 8192 bytes to 47...
  Writing at 0x0000e000... (100 %)
  Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 664.2 kbit/s)...
  Hash of data verified.
  Compressed 357536 bytes to 190478...
  Writing at 0x00010000... (8 %)
  Writing at 0x00018fa4... (16 %)
  Writing at 0x0002ae4c... (25 %)
  Writing at 0x00031fba... (33 %)
  Writing at 0x00037609... (41 %)
  Writing at 0x0003ce26... (50 %)
  Writing at 0x00043401... (58 %)
  Writing at 0x0004bfda... (66 %)
  Writing at 0x0005193c... (75 %)
  Writing at 0x000579b5... (83 %)
  Writing at 0x0005d835... (91 %)
  Writing at 0x000635f9... (100 %)
  Wrote 357536 bytes (190478 compressed) at 0x00010000 in 4.7 seconds (effective 608.0 kbit/s)...
  Hash of data verified.

Leaving...
Hard resetting via RTS pin...
=========================================== [SUCCESS] Took 15.55 seconds ===========================================
--- Available filters and text transformations: colorize, debug, default, direct, esp32_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time
--- More details at https://bit.ly/pio-monitor-filters

Please build project in debug configuration to get more details about an exception.
See https://docs.platformio.org/page/projectconf/build_configurations.html

--- Miniterm on COM6 115200,8,N,1 ---
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x400f2040: ffff5755 ffffffff ffffffff
Core 1 register dump:
PC : 0x400f2044 PS : 0x00060230 A0 : 0x0000000d A1 : 0x3ffb8660
A2 : 0x00000021 A3 : 0x00000000 A4 : 0x0000001a A5 : 0x3ff49028
A6 : 0x0000001a A7 : 0x00000001 A8 : 0x00002a00 A9 : 0x00000a00
A10 : 0x0000000a A11 : 0x3ff000c4 A12 : 0x06ff1f78 A13 : 0x3ffb1f60
A14 : 0x3ffb8058 A15 : 0x00000001 SAR : 0x0000000e EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

ELF file SHA256: 0000000000000000

Backtrace: 0x400f2044:0x3ffb8660 0x0000000a:0x3ffb8690 0x400d5f67:0x3ffb86d0 0x400d3118:0x3ffb8700 0x400d2ced:0x3ffb8850 0x400883f2:0x3ffb8870
#0 0x400f2044:0x3ffb8660 in mcpwm_gpio_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/mcpwm.c:699
#1 0x0000000a:0x3ffb8690 in ?? ??:0
#2 0x400d5f67:0x3ffb86d0 in BLDCDriver6PWM::init() at .pio/libdeps/view/Simple [email protected]/src/drivers/BLDCDriver6PWM.cpp:61
#3 0x400d3118:0x3ffb8700 in MotorTask::run() at src/motor_task.cpp:61
#4 0x400d2ced:0x3ffb8850 in Task::taskFunction(void*) at src/task.h:46
#5 0x400883f2:0x3ffb8870 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)

Rebooting...
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x400f2040: ffff5755 ffffffff ffffffff
Core 1 register dump:
PC : 0x400f2044 PS : 0x00060230 A0 : 0x0000000d A1 : 0x3ffb8660
A2 : 0x00000021 A3 : 0x00000000 A4 : 0x0000001a A5 : 0x3ff49028
A6 : 0x0000001a A7 : 0x00000001 A8 : 0x00002a00 A9 : 0x00000a00
A10 : 0x0000000a A11 : 0x3ff000c4 A12 : 0x06ff1f78 A13 : 0x3ffb1f60
A14 : 0x3ffb8058 A15 : 0x00000001 SAR : 0x0000000e EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

ELF file SHA256: 0000000000000000

Backtrace: 0x400f2044:0x3ffb8660 0x0000000a:0x3ffb8690 0x400d5f67:0x3ffb86d0 0x400d3118:0x3ffb8700 0x400d2ced:0x3ffb8850 0x400883f2:0x3ffb8870
#0 0x400f2044:0x3ffb8660 in mcpwm_gpio_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/mcpwm.c:699
#1 0x0000000a:0x3ffb8690 in ?? ??:0
#2 0x400d5f67:0x3ffb86d0 in BLDCDriver6PWM::init() at .pio/libdeps/view/Simple [email protected]/src/drivers/BLDCDriver6PWM.cpp:61
#3 0x400d3118:0x3ffb8700 in MotorTask::run() at src/motor_task.cpp:61
#4 0x400d2ced:0x3ffb8850 in Task::taskFunction(void*) at src/task.h:46
#5 0x400883f2:0x3ffb8870 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)

Rebooting...
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x400f2040: ffff5755 ffffffff ffffffff
Core 1 register dump:
PC : 0x400f2044 PS : 0x00060230 A0 : 0x0000000d A1 : 0x3ffb8660
A2 : 0x00000021 A3 : 0x00000000 A4 : 0x0000001a A5 : 0x3ff49028
A6 : 0x0000001a A7 : 0x00000001 A8 : 0x00002a00 A9 : 0x00000a00
A10 : 0x0000000a A11 : 0x3ff000c4 A12 : 0x06ff1f78 A13 : 0x3ffb1f60
A14 : 0x3ffb8058 A15 : 0x00000001 SAR : 0x0000000e EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

ELF file SHA256: 0000000000000000

Backtrace: 0x400f2044:0x3ffb8660 0x0000000a:0x3ffb8690 0x400d5f67:0x3ffb86d0 0x400d3118:0x3ffb8700 0x400d2ced:0x3ffb8850 0x400883f2:0x3ffb8870
#0 0x400f2044:0x3ffb8660 in mcpwm_gpio_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/mcpwm.c:699
#1 0x0000000a:0x3ffb8690 in ?? ??:0
#2 0x400d5f67:0x3ffb86d0 in BLDCDriver6PWM::init() at .pio/libdeps/view/Simple [email protected]/src/drivers/BLDCDriver6PWM.cpp:61
#3 0x400d3118:0x3ffb8700 in MotorTask::run() at src/motor_task.cpp:61
#4 0x400d2ced:0x3ffb8850 in Task::taskFunction(void*) at src/task.h:46
#5 0x400883f2:0x3ffb8870 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)

Rebooting...
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x400f2040: ffff5755 ffffffff ffffffff
Core 1 register dump:
PC : 0x400f2044 PS : 0x00060230 A0 : 0x0000000d A1 : 0x3ffb8660
A2 : 0x00000021 A3 : 0x00000000 A4 : 0x0000001a A5 : 0x3ff49028
A6 : 0x0000001a A7 : 0x00000001 A8 : 0x00002a00 A9 : 0x00000a00
A10 : 0x0000000a A11 : 0x3ff000c4 A12 : 0x06ff1f78 A13 : 0x3ffb1f60
A14 : 0x3ffb8058 A15 : 0x00000001 SAR : 0x0000000e EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

ELF file SHA256: 0000000000000000

Backtrace: 0x400f2044:0x3ffb8660 0x0000000a:0x3ffb8690 0x400d5f67:0x3ffb86d0 0x400d3118:0x3ffb8700 0x400d2ced:0x3ffb8850 0x400883f2:0x3ffb8870
#0 0x400f2044:0x3ffb8660 in mcpwm_gpio_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/mcpwm.c:699
#1 0x0000000a:0x3ffb8690 in ?? ??:0
#2 0x400d5f67:0x3ffb86d0 in BLDCDriver6PWM::init() at .pio/libdeps/view/Simple [email protected]/src/drivers/BLDCDriver6PWM.cpp:61
#3 0x400d3118:0x3ffb8700 in MotorTask::run() at src/motor_task.cpp:61
#4 0x400d2ced:0x3ffb8850 in Task::taskFunction(void*) at src/task.h:46
#5 0x400883f2:0x3ffb8870 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)

Rebooting...
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x400f2040: ffff5755 ffffffff ffffffff
Core 1 register dump:
PC : 0x400f2044 PS : 0x00060230 A0 : 0x0000000d A1 : 0x3ffb8660
A2 : 0x00000021 A3 : 0x00000000 A4 : 0x0000001a A5 : 0x3ff49028
A6 : 0x0000001a A7 : 0x00000001 A8 : 0x00002a00 A9 : 0x00000a00
A10 : 0x0000000a A11 : 0x3ff000c4 A12 : 0x06ff1f78 A13 : 0x3ffb1f60
A14 : 0x3ffb8058 A15 : 0x00000001 SAR : 0x0000000e EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

ELF file SHA256: 0000000000000000

Backtrace: 0x400f2044:0x3ffb8660 0x0000000a:0x3ffb8690 0x400d5f67:0x3ffb86d0 0x400d3118:0x3ffb8700 0x400d2ced:0x3ffb8850 0x400883f2:0x3ffb8870
#0 0x400f2044:0x3ffb8660 in mcpwm_gpio_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/mcpwm.c:699
#1 0x0000000a:0x3ffb8690 in ?? ??:0
#2 0x400d5f67:0x3ffb86d0 in BLDCDriver6PWM::init() at .pio/libdeps/view/Simple [email protected]/src/drivers/BLDCDriver6PWM.cpp:61
#3 0x400d3118:0x3ffb8700 in MotorTask::run() at src/motor_task.cpp:61
#4 0x400d2ced:0x3ffb8850 in Task::taskFunction(void*) at src/task.h:46
#5 0x400883f2:0x3ffb8870 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)

Rebooting...
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0xffffffff,len:-1
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x400f2040: ffff5755 ffffffff ffffffff
Core 1 register dump:
PC : 0x400f2044 PS : 0x00060230 A0 : 0x0000000d A1 : 0x3ffb8660
A2 : 0x00000021 A3 : 0x00000000 A4 : 0x0000001a A5 : 0x3ff49028
A6 : 0x0000001a A7 : 0x00000001 A8 : 0x00002a00 A9 : 0x00000a00
A10 : 0x0000000a A11 : 0x3ff000c4 A12 : 0x06ff1f78 A13 : 0x3ffb1f60
A14 : 0x3ffb8058 A15 : 0x00000001 SAR : 0x0000000e EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

ELF file SHA256: 0000000000000000

Backtrace: 0x400f2044:0x3ffb8660 0x0000000a:0x3ffb8690 0x400d5f67:0x3ffb86d0 0x400d3118:0x3ffb8700 0x400d2ced:0x3ffb8850 0x400883f2:0x3ffb8870
#0 0x400f2044:0x3ffb8660 in mcpwm_gpio_init at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/mcpwm.c:699
#1 0x0000000a:0x3ffb8690 in ?? ??:0
#2 0x400d5f67:0x3ffb86d0 in BLDCDriver6PWM::init() at .pio/libdeps/view/Simple [email protected]/src/drivers/BLDCDriver6PWM.cpp:61
#3 0x400d3118:0x3ffb8700 in MotorTask::run() at src/motor_task.cpp:61
#4 0x400d2ced:0x3ffb8850 in Task::taskFunction(void*) at src/task.h:46
#5 0x400883f2:0x3ffb8870 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c:355 (discriminator 1)

Rebooting...
ets Jun 8 2016 00:22:57

I sent STL/STP files to 3D Printing factory, they can't read models properly.

The link is https://bezeklabs.autodesk360.com/g/shares/SH35dfcQT936092f0e4372570ef992887b79

Is there anything I did wrong with 3D models?

Thinking of integrating something like this in our input device firmware project openinput
Can think of couple applications for this like keyboards, and mouse scroll wheel, and stand alone ofcourse

That said the way it currently is wont integrate well (arduino and esp), so I will have to do something from scratch.

Yet I think it would be nice to integrate here the openinput-protocol for configurations and interactions, the protocol is under development, so feel free to suggest functions that would be useful for this so that they can be thought about and integrated

There are a number of hardcoded configuration values currently:

• electrical zero angle (motor + sensor alignment)
• motor pole count
• motor orientation
• HX711 upper and lower thresholds
• VEML7700 lux mapping to LED/backlight brightness

Might be nice to move these to a file (json?) on spiffs/littlefs, and ideally eventually add a calibration menu that can write/update that file automatically.

Is there any plan to have a version supporting wired Ethernet connetion?

ESP32 can accomodate with various Ethernet PHY chips, also combined with an 802.3af PoE supply this project could really kick ass in the home automation world. Think of this also as mounted on wall on the end of a CAT5 cable supplying both data and power...

Hello! Great project! Love the idea for model railway throttle controllers. (Plus so many more possibilities!)

I think it would be cool to sync the ring LED output to match the rotation of the knob, like a virtual indicator?

Could set a brightness or colour for general orientation point/direction, and mix the rest to blur/dim to background colour/darkness?

Cheers!
P.S. check out www.dcc-ex.com for open-source DIY model train control technology! 😎👍

Hey, just an FYI:

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "{}"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

@scottbez1 protect your IP! This project is amazing!

Currently there is not enough memory available to initialize wifi (and I assume the same is likely true of bluetooth though I haven't tested yet).

A big culprit is the full 240x240x16b framebuffer in the display task which is used to avoid flickering when rendering. Two ideas of avoiding this memory issue:

• potentially enable PSRAM (the ESP32-PICO-V3-02 has 2MB SPI PSRAM built in but not enabled by default in the current Arduino core). I did an initial test trying to enable PSRAM by using a newer arduino platform from git, but overall CPU performance ended up really bad. I didn't dig further where that performance hit was coming from, so I'm not sure if whether this approach is viable or not
• migrate the graphics to LVGL, which supposedly can work with a smaller buffer and do tiled rendering (and do smarter rendering if regions haven't changed). I haven't used LVGL before, but it looks pretty powerful, and should also simplify adding things like a menu system later

There are some other memory issues, like the default arduino loop task allocates a (fixed) moderately sized stack but is essentially completely unused and gets deleted immediately after starting other tasks, but I think those issues are smaller scale compared to the framebuffer issue.

Should swap for AP2114HA-3.3 - make sure to fix footprint to match

https://twitter.com/scottbez1/status/1499445571999846409