VL6180X API

pmak · ‎2026-02-04

Hi, I'm supporting a legacy product which uses this older sensor, VL6180X.

Where could I find the API source code for download? It seems that all links for "STSW-IMG003", "STSW-IMG011" etc. which are listed in the docs have been erased from the site. Could someone provide a working link to the latest API version, or perhaps just attach the .zip here for posterity?

Thanks in advance!

Anne BIGOT · ‎2026-02-04

Hello,
The VL6180X is nomore supported by ST, that's why SW drivers have been removed from the site.
Anne

Our community relies on fruitful exchanges and good quality content. You can thank and reward helpful and positive contributions by marking them as 'Accept as Solution'. When marking a solution, make sure it answers your original question or issue that you raised.

ST Employees that act as moderators have the right to accept the solution, judging by their expertise. This helps other community members identify useful discussions and refrain from raising the same question. If you notice any false behavior or abuse of the action, do not hesitate to 'Report Inappropriate Content'

pmak · ‎2026-02-04

Hi, thanks for replying!

I understand that the VL6180X is now obsolete, but the chips and devices using them still exist in the world in large numbers, and need to be maintained. I don't expect support in the sense of new releases or bug fixes, but surely it's possible to get the last release of the API code?

Does anyone in the community have a copy of the latest API package? Or should we file a support ticket instead?

Cheers

John_Kvam · ‎2026-02-05

In this case, GitHub is your friend. I'm sure there is some code on that site that has the API in it.

I searched VL6180 STM32 on GitHub and the first hit had the TOF driver in it.

Seems silly for ST to remove the legacy code. I guess they just didn't want to maintain it for the very few customers who still wanted to play.

Good luck

- john

If this or any post solves your issue, please mark them as "Accept as Solution". It really helps the next guy.
And if you notice anything wrong do not hesitate to "Report Inappropriate Content".
I am a recently retired ST Employee. My former username was John E KVAM.

pmak · ‎2026-02-05

Hi,

yes, I actually did just that yesterday and found a few different versions hosted in various places. It just feels a little iffy in a professional context to rely on random copies found online, but I'll do my best to verify that the files are unaltered and go with that.

I do wish ST would reconsider this policy - I understand not wanting to actively maintain the product or API, and that's fine, but leave at least the final release available somewhere.

Cheers