Issue with shared lib in setup.py when using Pi4 running ubuntu 22.04

[tsdamas]

I am trying to use the setup.py, but I am having issues with the -lalgosec. I have added the BOSCH PiFour library from an previous issue that I found here, but still having issues with the setup.py. Any thoughts? Thanks!

[mcalisterkm]

The setup.py is expecting a specific version of BSEC.
Which version of BSEC are you using?
Also I see you are using PI hardware but Ubuntu OS rather than Raspbian, and the Ubuntu is possibly 64 bit?
The setup.py is pointing to a 32bit BSEC binary.

The good news is that BSEC 2.5 has a 64 bit binary for the PI5/Pi4, and there have been linux binaries in earlier releases (2.4) that may work for you.

Keith

[hub187]

I am having the same issue on a RPI 4. Any pointers or help would be much appreciated!!

Uname: Linux raspberrypi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux (CPU is an ARM Cortex-A72)

trying to install with bsec with both bsec 2.5.n and the specific older version some people recommended (2.0.6.1). In both cases the install fails. Also tried with pip (install "without" bsec using ./bin/pip3 install bme68x on a venv. This also failed).

Trace from the original "sudo python3 setup.py install" gave me the same "-lalgosec" output as per below:

aarch64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2 build/temp.linux-aarch64-cpython-311/BME68x-Sensor-API/bme68x.o build/temp.linux-aarch64-cpython-311/bme68xmodule.o build/temp.linux-aarch64-cpython-311/internal_functions.o -L/usr/local/lib -LBSEC_2.0.6.1_Generic_Release_04302021/algo/normal_version/bin/RaspberryPi/PiThree_ArmV6 -L/usr/lib/aarch64-linux-gnu -lpthread -lm -lrt -lalgobsec -o build/lib.linux-aarch64-cpython-311/bme68x.cpython-311-aarch64-linux-gnu.so
/usr/bin/ld: skipping incompatible BSEC_2.0.6.1_Generic_Release_04302021/algo/normal_version/bin/RaspberryPi/PiThree_ArmV6/libalgobsec.a when searching for -lalgobsec
/usr/bin/ld: cannot find -lalgobsec: No such file or directory
collect2: error: ld returned 1 exit status
error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1

[mcalisterkm]

There is a 64 bit binary for BSEC2.4 posted on the BOSCHSensortec community site - I am sure I have linked to it before, yes see issue 21. I have that working after fixing the references in setup with my 2.4 clone of this code. I have not tried BSEC 2.5 as it is a complete trash and start again release, and the new AI Studio does not load on my mac. It is going to be next month before I am able to look at this. BSEC 2.4 and earlier only contain 32bit binary's in the RPI release, so they are no use to you.

Previously in discussions with BoschSensortec they released some non-relocatable 64bit binary's that could not work with this Python integration. That is a possibility again with BSEC 2.5 please have a look.

Here is the BSEC 2.4: [64 bit binary](https://community.bosch-sensortec.com/t5/MEMS-sensors-forum/BSEC-2-4-0-0-errors-when-installing-BME68x-library-for-Python/td-p/78296/page/2
Do have a read of issue 21.

Regards
Keith

[hub187]

Hello Keith!
Thanks a lot for your reply :).
I tried with the 2.4 version but to no avail (also with replacing the algo files the community member shared in the thread).
I installed a 32 bits of Raspbian and used the old 2.6.0.1 and it worked (had to install python full & dev but otherwise it went well).

Now I need to figure out how to use the sensor! ;) It is not as straight forward as a DHT! :D

[mcalisterkm]

You will need to burn it in for 24 hours, and save the state.
Then load that state in your next script, which speeds up the time to stability/quality on the sensor.

I have some code you could use here
These and other config files have a BSEC version specific header and therefore need to be re-created with each of the annual BoschSensortec releases.

[mcalisterkm]

With the 2.4 BSEC did you try my release of BME68x for version 2.4: https://github.com/mcalisterkm/bme68x-python-library-bsec2.4.0.0 There were code changes needed for 2.4 support, contributed by the community. Unfortunately PI3g are no longer updating the original code. Regards Keith McAlister ***@***.***

…

On 16 May 2024, at 21:28, hub187 ***@***.***> wrote: Hello Keith! Thanks a lot for your reply :). I tried with the 2.4 version but to no avail (also with replacing the algo files the community member shared in the thread). I installed a 32 bits of Raspbian and used the old 2.6.0.1 and it worked (had to install python full & dev but otherwise it went well). Now I need to figure out how to use the sensor! ;) It is not as straight forward as a DHT! :D — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB2Y6G52QFUZ4PIF3ZQNJXLZCUJILAVCNFSM6AAAAABF3UONCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWGEZDENRQHA>. You are receiving this because you commented.

[hub187]

Hello Keith!

Thanks for the reply. :)

The old bsec 2.0.6.1 runs fine on a 32 bits OS (for people landing on this thread!! ;D).

---

Doh I did not try this one (I already installed the 32 bits OS and was happily coding by then). I bookmarked your project because it might come very handy later on!!

I actually run into a problem where the get_bsec_data() and get_digital_nose_data() methods give me completely pants results vs. a DHT22 which I use as "source of truth". Will create another thread for this as to not mix topics.

[mcalisterkm]

I saw your code fragment and it looks odd. 1) get_digital_nose_data() is used to sniff up to 4 classes of smell/gas, it returns a percentage for each registered class. 2) It looks like you are swapping sample rates in flight which the sensor will not like. With a burned in sensor it takes at least 5 min to stabilise and the data includes accuracy info. It can take a while to learn how to use this complex sensor, see the .md file and the bosch sensortec pdf docs. Regards Keith

…

On 21 May 2024, at 21:04, hub187 ***@***.***> wrote: DHT22

[hub187]

Hello Keith,

I tried the specific library you recommended and I still got a algo link issue. It is no biggy for me because I have a 32 bit raspbian with bsec2.0.6.1 and this works.

Steps:

1. Was on an arm 64 rpi5, clone your repo above, also used the specific 2.4.0 bsec library from january,
2. wget the bsec into the library next to the readme
3. this created the folder "BSEC2.4.0.0_Generic_Release_23012023"
4. ran sudo python3 setup.py install
5. script finished on the error below

internal_functions.c:377:13: warning: variable ‘iaq_accuracy’ set but not used [-Wunused-but-set-variable] 377 | uint8_t iaq_accuracy = 0; | ^~~~~~~~~~~~ internal_functions.c:376:11: warning: variable ‘iaq’ set but not used [-Wunused-but-set-variable] 376 | float iaq = 0.0f; | ^~~ internal_functions.c:375:13: warning: variable ‘timestamp’ set but not used [-Wunused-but-set-variable] 375 | int64_t timestamp = 0; | ^~~~~~~~~ aarch64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2 build/temp.linux-aarch64-cpython-311/BME68x-Sensor-API/bme68x.o build/temp.linux-aarch64-cpython-311/bme68xmodule.o build/temp.linux-aarch64-cpython-311/internal_functions.o -L/usr/local/lib -LBSEC2.4.0.0_Generic_Release_23012023/algo/normal_version/bin/RaspberryPi/PiThree_ArmV6 -L/usr/lib/aarch64-linux-gnu -lpthread -lm -lrt -lalgobsec -o build/lib.linux-aarch64-cpython-311/bme68x.cpython-311-aarch64-linux-gnu.so /usr/bin/ld: skipping incompatible BSEC2.4.0.0_Generic_Release_23012023/algo/normal_version/bin/RaspberryPi/PiThree_ArmV6/libalgobsec.a when searching for -lalgobsec /usr/bin/ld: cannot find -lalgobsec: No such file or directory collect2: error: ld returned 1 exit status error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1

my folder looks like this:

/bme68x-python-library-bsec2.4.0.0/bme68x-python-library-bsec2.4.0.0-jan2023 $ ls bme68xConstants.py bme68xmodule.c BSEC2.4.0.0_Generic_Release_23012023 bsecConstants.py Documentation.md internal_functions.c LICENSE setup.py bme68x.egg-info BME68x-Sensor-API bsec2-4-0-0_generic_release_23012023.zip build examples internal_functions.h README.md tools

[mcalisterkm]

I have created a repo with the 64 bit BSEC library from BoschSensortec, here: https://github.com/mcalisterkm/bme68x-python-library-bsec2.4.0.0-64bit It includes the 64bit lib so no need to copy the BSEC software. I have not found any issues that are not present in the 32bit version. Regards Keith

[hub187]

Thanks Keith!

Just to summarise (it works just fine :):

• The library shared above works on rpi5 64 bits OS!
• The bsec library it is already included in the package above and it should NOT be manually installed (installing bsec 2.4 manually failed for me as per the error mentioned in the previous comment). This was actually mentioned in the readme... doh!

Note: the bsec method does not return comp_gas anymore in the 2.4 library. Was it dropped entirely? Or is it just not available yet because this is an alpha release?

[mcalisterkm]

At BSEC 2.2.0 Boschsensortec removed a virtual sensor perviously annotated for "internal use", which reduced the number of virtual sensors from 14 to 13. This was documented in the BSEC 2.2 release note and the integration guide, however the BSEC library still had all 14 virtual sensors. Community member FlipTheDog did most of the work to remove the deprecated sensor, and 2.3 and 2.4 bme68x are 13 virtual sensor python wrappers for BSEC. It would not surprise me if that virtual sensor was still present in BSEC 2.5 but is now undocumented.

Each BSEC release from BoschSensortec has a release note and an integration guide. The Integration Guide has a section 1.2.4 Supported Virtual Sensor Output Signals, that defines the virtual sensors.

Regards
Keith

[hub187]

Super interesting! Thanks for the detailed answer Keith. I started with Humidity and Temperature and gradually discovering a world of (interesting) complexity! :)

PS: issue is closed from my perspective (not sure if you prefer keeping issues opened or not). the library can run well on both 32 bits and 64 bits OSes on rpi.

[mcalisterkm]

I think tsdamas would need to close. (I can't close it)
It would be interesting to know if it works for a Pi4 running ubuntu 22.04? - I think it should.