For some reason, the Windows Client is unable to connect to the ESP, as soon as it is found and an attempt to connect is made it loses the connection to the board over BT.
this is the error created by the player:

2022-11-28 15:47:40,361 [1] ERROR BhapticsPlayer.Internal.BhapticsLiteDB: BhapticsDB DB created
2022-11-28 15:47:40,438 [1] ERROR BhapticsPlayer.Utils.Utilities: Util Get BhapticsSettingValue 1
2022-11-28 15:47:40,439 [1] ERROR BhapticsPlayer.Utils.Utilities: CurrentCulture: de-AT
2022-11-28 15:47:40,439 [1] ERROR BhapticsPlayer.Utils.Utilities: Properties.Settings.Default.language Before: en-US
2022-11-28 15:47:40,439 [1] ERROR BhapticsPlayer.Utils.Utilities: Properties.Settings.Default.language: en-US
2022-11-28 15:47:40,731 [1] WARN  BhapticsPlayer.Internal.SettingsStore: CheckDfuFailure
2022-11-28 15:47:40,840 [1] ERROR BhapticsPlayer.Utils.AudioToHapticConfig: Load default setting
2022-11-28 15:47:41,014 [1] ERROR BhapticsPlayer.Audio.Utils.AudioDeviceWatcher: AudioDeviceWatcher() default selected. Die Sequenz enthält kein übereinstimmendes Element.
2022-11-28 15:47:41,131 [1] ERROR BhapticsPlayer.WebSocket.StudioReceiver: Listening on port 15881, and providing WebSocket services:
2022-11-28 15:47:41,145 [1] ERROR BhapticsPlayer.WebSocket.StudioReceiver: Listening on port 15882, and providing WebSocket Secure services: True
2022-11-28 15:47:41,145 [1] WARN  BhapticsPlayer.Utils.Utilities: Release Id : 2009
2022-11-28 15:47:41,145 [1] WARN  BhapticsPlayer.Utils.Utilities: releaseNum : 2009
2022-11-28 15:47:41,655 [1] WARN  BhapticsPlayer.Internal.SettingsStore: CheckDfuFailure
2022-11-28 15:47:41,745 [5] ERROR BhapticsModLauncher.Config.BhapticsContentsRepository: HttpWebResponse status: OK
2022-11-28 15:47:42,448 [5] ERROR BhapticsModLauncher.Config.BhapticsContentsRepository: BhapticsContentsRepository Exists DB
2022-11-28 15:47:42,486 [5] ERROR BhapticsModLauncher.Config.BhapticsContentsRepository: BhapticsContentsRepository SaveGameContents()
2022-11-28 15:47:52,765 [6] WARN  BhapticsPlayer.Bluetooth.DeviceWatcherService: Remove Device TactosyDevice {Name=TactSuitX40, Id=70518412007866, Paired=False, Connected=Disconnected}
2022-11-28 15:48:00,282 [30] WARN  BhapticsPlayer.Bluetooth.DeviceWatcherService: Remove Device TactosyDevice {Name=TactSuitX40, Id=70518412007866, Paired=False, Connected=Disconnected}

Serial output does not produce anything bt this:

>>      onConnect()
>>      onConnect(*param)
>>      onDisconnect()

Add MAX17048 component for battery level fuel gauge

Implementation PR

• No FFB, No Splay (#60)
• FreeRTOS task (#64)
• Bluetooth Serial Communication (#69)
• Add Splay
• Add FFB
• Put in task
• Unified firmware for TactGlove + OpenGloves compatibility

Reference Issues

Will require merging #39, thus closing #29, #31 and #36

Summary

• Add support for OpenGloves protocol (USB Serial and Bluetooth Serial)
• Add support for servo outputs (already done? the same output writers)
• Add inputs for finger tracking (using ISensor? use Battery as a reference for throttled update rate)
• Add buttons (with interrupts? or looped?)

Basic Example

There are references:

• https://github.com/LucidVR/lucidgloves
• https://github.com/JohnRThomas/OpenGloves-Firmware/

Drawbacks

Creating a proper config file for such a configuration will be hard. Possible options are:

• TactGlove + OpenGlove (Serial + flexion + splay + FFB)
• TactGlove + OpenGlove (Serial + flexion + FFB)
• TactGlove + OpenGlove (Serial + flexion + splay)
• TactGlove + OpenGlove (Serial + flexion)

Multiply that with BT Serial instead of Serial, and if someone wants to use it without Haptic Feedback, and configuration becomes quite hard

Unresolved questions

No response

What happened?

I did install the last version 0.7.0-rc1 and work perfectly in IOS and Android mobiles phone. But in quest, are detected correctly in bluetooth but into the Haptic player don't... and don't work in games.

I have a screen shot that I report the Version of the Bhaptic player and the version of Quest are 66.
Is detected by the BHaptic, can see into the list, but can't connect and use it.

Greetings.

Target Device

x16 haptic

Hardware Configuration

ESP32-WROOM-32

Firmware Version

0.7.0 RC1

What OS or environment are you seeing the problem on?

Meta Quest

bHaptics Player Version

1.2.3

Relevant log output

Quest 3 version 66.

Serial output

NO serial output

Contact Details

[email protected]

Code of Conduct

• I agree to follow this project's Code of Conduct

We really need one, I only found how I need to build it out from analyzing the files and trial and error (I guess because I use other software versions). But I get it to build the code.

What you need (for others):

1. Vistual Studio Code
2. Inside VSC the Extensions PlatformIO IDE, Espressif IDF and maybe Arduino(?), at the last not sure, I simply installed it.
3. Clone the Git Code from here to your drive and open it with PlatformIO, on their website is a tutorial how.

I get an error "src_filter is missing inside [Common] in platformio.ini" (something like that). I copied build_src_filter inserted it before and remove "build_", it worked.

But when I want to upload it, it load all files from all bHaptics product one after another up, so you need to make a backup of ini/bhaptics.ini and delete all except the one you want to build and upload.

And after this... holly cow, it works perfect in the bHaptics Feedback Test! Couldn't find an issue here. Now I can start to build my vest in the next weeks. I tested it with the Tactosi for feets, because it only has 3 rumble motors, easier to test. All 3 ports worked as they should inclusive the intensity.

Implementation PR

No response

Reference Issues

espressif/arduino-esp32#8796

Summary

Upgrade to Arduino core for the ESP32 3.0.0 after it's release

Basic Example

Migration guide: https://docs.espressif.com/projects/arduino-esp32/en/latest/migration_guides/2.x_to_3.0.html

Drawbacks

Refactoring, some libs may stay outdated, needed to be forked/reimplemented

Unresolved questions

No response

Implementation PR

No response

Reference Issues

Will require #29 first

Summary

Reorganize project to use lib directory as described herethe

Basic Example

- lib
  - Core
    - Component
    - Output
  - OutputLedc
    - OutputLedc
  - OutputPCA9685
    - OutputPCA9685
  - ...

Drawbacks

Will require to create it's own internal library for each major firmware part

Unresolved questions

1. What is our desired structure?
2. What components to extract?

https://diyi0t.com/ina219-tutorial-for-arduino-and-esp/

Here I am just writing ideas from my mind to future implement in our own protocol, when current protocol from bHaptics when it ceases to meet the needs

OpenHaptics Protocol

Coordinates encoding

Each axis (X and Y) is uint8_t between 0 and 255

(0, 0)                                 (128, 0)                                 (255, 0)









(0, 128)                               (128, 128)                               (255, 128)









(0, 255)                               (128, 255)                               (255, 255)

Intensity

Intensity is uint8_t:

0: 0%, 255: 100%

Effects layer

Effect layer is 16 possible values (4 bits - uint8_t << 4)

Body Parts IDs mapping

Every diverging part of the body is separated into Front and Back faces.
Coordinate path has 255 possible values (8 bits - uint8_t)

Implementation PR

No response

Reference Issues

Required for #50

Summary

Create a communication, that allows ForceTube SDK to connect
It is 100% possible, since ForceTube itself is originally built on ESP32

Basic Example

BluetoothSerial(“ForceTube xxxxxxxxx”)

Drawbacks

• It is one more integration in 3rd-party SDK, future usage will not allow interconnection
• Incompatible with #44, since both use BluetoothSerial
• Probably incompatible with BLE stack

Unresolved questions

No response

Using current uint16_t for coordinates is too excessive.

We can save some memory and future transmission bytes by reducing every axis (X and Y) and output intensity to uint8_t, giving us $2^{8}=256$ values for each variable

This RFC is a part of transition to #9

https://diyi0t.com/reduce-the-esp32-power-consumption/

Packages

    platformio/[email protected]+20240530
    platformio/[email protected]+20240403

Changelog

• https://gcc.gnu.org/gcc-13/changes.html

Add handlers to firmware to OTA firmware updates over BLE, to update it without any need to connect via USB

References:

• https://github.com/sparkfun/ESP32_OTA_BLE_React_WebApp_Demo/
• https://learn.sparkfun.com/tutorials/esp32-ota-updates-over-ble-from-a-react-web-application/all
• https://www.esp32.com/viewtopic.php?t=18324
• https://github.com/espressif/arduino-esp32/blob/master/libraries/Update/examples/SD_Update/SD_Update.ino

Implementation PR

No response

Reference Issues

Will require #36 first

Summary

Create Unit tests to insure, that all components of the firmware are working as expected

Basic Example

Test closest output, auto output mapper, etc.

Drawbacks

Is TDD a drawback? 😃

Unresolved questions

No response

Implementation PR

No response

Reference Issues

No response

Summary

Create a testing pipeline using Wokwi for testing

Hardware projects:

• https://wokwi.com/projects/370142477673707521
• https://wokwi.com/projects/370143558255472641

Basic Example

• https://github.com/wokwi/wokwi-ci-action
• https://github.com/wokwi/esp32-hello-wokwi-ci
• https://github.com/wokwi/platform-io-esp32-counter-ci

Drawbacks

• More complex CI pipeline

Unresolved questions

No response

Using PlatformIO and PlatformIO IDE is not as straightforward as using Arduino IDE, so an alternative is required

As proposed, WebFlash API may be used to achieve a more effortless firmware flashing experience. Using newly-created openhaptics.github.io it is possible to create a WebFlash-based page. To achieve this following steps are required:

• Create releases for firmware
• #16
• https://github.com/openhaptics/openhaptics.github.io/issues/1
• https://github.com/openhaptics/openhaptics.github.io/issues/9

Implementation PR

No response

Reference Issues

No response

Summary

Replace existing C-style casts with C++ casts across all codebase.

Basic Example

Replace (T)foo with static_cast, reinterpret_cast, const_cast and dynamic_cast

Drawbacks

Ugly code, need to understand how it works first

Unresolved questions

No response

Implementation PR

No response

Reference Issues

No response

Summary

Allow changing SerialPlotter port with #defines, to later use with Configurable firmware builder

Basic Example

Add config for serial plotter component: enable, port, baudrate

Accept HardwareSerial port as input for SerialPlotter, open port in setup() function

Drawbacks

With this implementation submitted port must be reserved for using only with SerialPlotter

Unresolved questions

No response

Implementation PR

No response

Reference Issues

No response

Summary

Add an option to change an active connected devices with a push of a button (quest/pcvr)

Basic Example

Logitech MX Master 3

Drawbacks

1. Will require a button
2. Is it really necessary?

Unresolved questions

Technical details: how does it work? Does it change MAC? Or smth else?

Implementation PR

#22

Reference Issues

Part of #17

Summary

Most basic Battery level monitor, using raw battery input to ADC pin

Basic Example

https://randomnerdtutorials.com/power-esp32-esp8266-solar-panels-battery-level-monitoring
https://theiotprojects.com/esp8266-monitor-its-own-battery-level-using-iot
https://github.com/SlimeVR/SlimeVR-Tracker-ESP/blob/main/src/batterymonitor.h
https://github.com/SlimeVR/SlimeVR-Tracker-ESP/blob/main/src/batterymonitor.cpp

Drawbacks

Will require soldering some resistors to create voltage divider, since ESP32 runs on 3.3V, but max battery output is around ~4V

Unresolved questions

No response

To increase the UX of firmware with the bHaptics player on devices, powered by an internal battery (not an external power bank), the battery level needs to be reported.

bHaptics uses 6e400008-b5a3-f393-e0a9-e50e24dcca9e Battery Level characteristic to report battery level (0 - 100) in Motor Service (6e400001-b5a3-f393-e0a9-e50e24dcca9e)

Additionally, for better UX on host devices without the need to check bHaptics software and native battery level notifications, this battery level may be reported to default 0x2A19 Battery Level characteristic in 0x180F Battery Service

Supported battery level sensors/gauges:

• MAX17048: #10 (SparkFun, AdaFruit)
• Internal ADC: #37
• INA219: #12 (Adafruit)

Details

Appear like 0 the battery level.

Implementation PR

No response

Reference Issues

Required for #65 and partially #44

Summary

Add a CD74HC4067 multiplexer sensor to firmware and allow using it as AnalogSensor
Required for OpenGloves Splay and MultiCurl

Basic Example

• JohnRThomas/OpenGloves-Firmware@main...JohnRThomas:OpenGloves-Firmware:multi-curl
• LucidVR/lucidgloves@main...proto5
• https://github.com/Droog71/CD74HC4067/blob/main/README.md
• https://github.com/esphome/esphome/blob/dev/esphome/components/cd74hc4067/cd74hc4067.h
• https://github.com/waspinator/CD74HC4067

Drawbacks

Harder to maintain easy INI configuration

Unresolved questions

No response

ArduinoBLE library uses ~1mb of memory: espressif/arduino-esp32#1075

Alternative: https://github.com/h2zero/NimBLE-Arduino

Implementation PR

No response

Reference Issues

No response

Summary

Create a config for Val's Indexer preset: https://github.com/Valsvirtuals/Indexer/wiki/wiring-and-pinout

Basic Example

Same as opengloves-proto-3 and opengloves-proto-4

Drawbacks

a lot of new configs: C, CS, CF, CSF, CC, CCS, CCF, CCSF:

• https://github.com/Valsvirtuals/Indexer/wiki/How-to-Indexer-guide

Unresolved questions

No response

Implementation PR

#49

Reference Issues

No response

Summary

Provide an option to integrate not only body-replated haptic accessories, such as gunstock for recoil effect

Basic Example

See #49

Drawbacks

Not currently supported by bHaptics' BLE, will require either option for future:

• use our own API
• emulate ProTubeVR protocol

Unresolved questions

No response

https://github.com/espressif/arduino-esp32/releases/tag/3.0.3

Implementation PR

No response

Reference Issues

No response

Summary

Create a new sensor that utilizes the atan2 function to calculate the angle from two analog inputs: cos and sin

Basic Example

auto* sin_sensor = new AnalogSensor(PIN_SIN);
auto* cos_sensor = new AnalogSensor(PIN_COS);

// (0.0F, 1.0F) => (-1.0F, 1.0F)
auto* sincos_filter = new LambdaFilter<float>([](float value) {
    return value * 2.0F - 1.0F;
});

sin_sensor->addFilter(sincos_filter);
cos_sensor->addFilter(sincos_filter);

atan2_sensor = new Atan2Sensor(sin_sensor, cos_sensor);

/// Sensor that calculates the atan2 of two sensors
template<typename Tp = float>
class Atan2Sensor : public Sensor<Tp> {
    static_assert(std::is_floating_point_v<Tp>, "Tp must be a floating point type");

  public:
    using Source = Sensor<Tp>;

    Atan2Sensor(Source* sin, Source* cos) : sin_(sin), cos_(cos){};

    void init() override
    {
        SS_SUBSENSOR_INIT(this->sin_, false, [this](float /*value*/) {
            this->recalculateState();
        });

        SS_SUBSENSOR_INIT(this->cos_, false, [this](float /*value*/) {
            this->recalculateState();
        });
    }

    inline void tick() override { this->recalculateState(); }

    void recalculateState()
    {
        const Tp sin = this->sin_->getValue();
        const Tp cos = this->cos_->getValue();

        if (sin == 0.0F && cos == 0.0F) {
            this->publishState(0.0F);
            return;
        }

        const Tp radians = std::atan2(sin, cos);

        this->publishState(radians);
    }

  private:
    Source* sin_;
    Source* cos_;
};

More examples:

1. https://github.com/LucidVR/lucidgloves/blob/proto5/firmware/lucidgloves-firmware/input.ino#L315

Drawbacks

1. The approach above requires applying a custom filter to the sensor.

Unresolved questions

No response

Implementation PR

No response

Reference Issues

No response

Summary

Develop a SlimeVR-compatible layer

Basic Example

Take a look at: https://github.com/SlimeVR/SlimeVR-Tracker-ESP

struct IMU_State {
  Vector3 gyroscope, accelerometer, magnetometer;
};

class BNO055 : public ISensor<IMU_State> {
  ...
};

Drawbacks

• A separate task for updates
• Will only work with WiFi
• Will require either recompile for each WiFi AP, or developing a provisioning module

Unresolved questions

No response