# What's next with ADVi3++?

**URL:** <https://community.advfirmwares.com/t/whats-next-with-advi3/3614>\
**Category:** General\
**Created:** [September 21, 2021, 4:51pm UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614 "2021-09-21T16:51:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrivet](https://community.advfirmwares.com/user_avatar/community.advfirmwares.com/andrivet/32/993_2.png) [@andrivet](https://community.advfirmwares.com/u/andrivet)\
**Post date:** [September 21, 2021, 4:51pm UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614/1 "2021-09-21T16:51:33Z")

</div>

![ADVi3++5.1](https://community.advfirmwares.com/uploads/default/original/2X/e/e634d2aae04846625fbf6f27c8755a9adabbfd2a.png)

Now that version 5 is released and is quite stable (all known issues were fixed in 5.0.1 except one related to LCD dimming), it is now time to talk about the future.

What I have planned at a minimum for version 5.1 is to align ADVi3++ with the latest version of [Marlin Firmware (currently 2.0.9.1)](https://github.com/MarlinFirmware/Marlin). But of course, I want to integrate other features.

There is already a list of [Feature Requests on GitHub](https://github.com/andrivet/ADVi3pp/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement). If you have ideas, it is time to submit them either here (by replying to this message) or on GitHub ([submit an Enhancement](https://github.com/andrivet/ADVi3pp/issues/new)). Everybody can submit a feature request but be sure your request is not specific to your setup and **can benefit to many people**. Please also do not submit **duplicates** (check before submitting that this is a new request).

Then at the beginning of October (around the 4th), I will publish a poll and people sponsoring the project on Patreon with **$8 or more will able to vote**. I will make my best to implement the features with the most votes. I will not implement all the features in version 5.1. Instead, I will implement some in version 5.1, them others in version 5.2, etc. This way, you will not have to wait again months before seeing a new release.

Thank you all, present and past sponsors of the project. It is such an amazing journey. And thanks to you, ADVi3++ will become even better.

Sebastien

---

<div class="post-metadata">

**Author:** ![kevdechef](https://community.advfirmwares.com/letter_avatar_proxy/v4/letter/k/91b2a8/32.png) [@kevdechef](https://community.advfirmwares.com/u/kevdechef)\
**Post date:** [September 23, 2021, 11:45am UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614/2 "2021-09-23T11:45:48Z")

</div>

Can you add bltouch support for i3 plus mk2?

---

<div class="post-metadata">

**Author:** ![andrivet](https://community.advfirmwares.com/user_avatar/community.advfirmwares.com/andrivet/32/993_2.png) [@andrivet](https://community.advfirmwares.com/u/andrivet)\
**Post date:** [September 23, 2021, 1:29pm UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614/3 "2021-09-23T13:29:38Z")

</div>

Can you elaborate a little? Why since those printers already have a sensor? It is not precise/reliable enough? Or for another reason?

---

<div class="post-metadata">

**Author:** ![kevdechef](https://community.advfirmwares.com/letter_avatar_proxy/v4/letter/k/91b2a8/32.png) [@kevdechef](https://community.advfirmwares.com/u/kevdechef)\
**Post date:** [September 23, 2021, 1:50pm UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614/4 "2021-09-23T13:50:45Z")

</div>

Yes the stock sensor is not precise / reliable enough, because of the heated bed that generates an unconsistent electromagnetic field.

---

<div class="post-metadata">

**Author:** ![Sam\_Koebrich](https://community.advfirmwares.com/letter_avatar_proxy/v4/letter/s/41988e/32.png) [@Sam\_Koebrich](https://community.advfirmwares.com/u/Sam_Koebrich)\
**Post date:** [September 27, 2021, 2:47pm UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614/5 "2021-09-27T14:47:25Z")

</div>

It seems like many people have replaced the stock thermistor with an M3 screw-in one. I believe the only way to currently account for the different power curve (type 1 vs type 11) is to recompile with a custom configuration. It would be nice if this setting was available on the LCD.

---

<div class="post-metadata">

**Author:** ![andrivet](https://community.advfirmwares.com/user_avatar/community.advfirmwares.com/andrivet/32/993_2.png) [@andrivet](https://community.advfirmwares.com/u/andrivet)\
**Post date:** [September 27, 2021, 6:03pm UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614/6 "2021-09-27T18:03:38Z")

</div>

This is a duplicate of [Be able to specify the thermistors type on the LCD panel · Issue #137 · andrivet/ADVi3pp · GitHub](https://github.com/andrivet/ADVi3pp/issues/137)

---

<div class="post-metadata">

**Author:** ![andrivet](https://community.advfirmwares.com/user_avatar/community.advfirmwares.com/andrivet/32/993_2.png) [@andrivet](https://community.advfirmwares.com/u/andrivet)\
**Post date:** [September 27, 2021, 6:59pm UTC](https://community.advfirmwares.com/t/whats-next-with-advi3/3614/7 "2021-09-27T18:59:41Z")

</div>

Tracked here: [Add BLTouch support for i3 plus Mark II · Issue #262 · andrivet/ADVi3pp · GitHub](https://github.com/andrivet/ADVi3pp/issues/262)
