HSDPython_SDK missing in DATALOG2_3.0.0

[Old_Geezer]

So I downloaded the new datalog2 demo zip file (early 2025)

Installed the bin file into my STWINBOX using STM32programmer and verified that file was the same as target 

I believe this version is a bit more stable at connecting to the iphone app ST_BLE_Sensor 5.2.4, using BLE.

However

* I managed to easily lock the stwinbox by pressing the [START] arrow button on the app's Sensors page. the middle green LED stopped blinking and was stuck in either on or off and comms was lost.

* The python lib was not present in the zip archive. I started the hsdatalog_GUI.py in datalog 2.3 instead and it had trouble connecting over usb. After connecting, it locked up on a "loading templates" window,. Here's the debug log:

2025-03-26 13:18:39,745 - HSDatalogApp.st_hsdatalog.HSD_link.HSDLink - INFO - Trying to open communication using libhs_datalog_v2...
2025-03-26 13:18:39,748 - HSDatalogApp.st_hsdatalog.HSD_link.communication.PnPL_HSD.hsd_dll - INFO - Platform Architecture: 64bit
HSD_DLLv2: libusb_close!
HSD_DLLv2: libusb_close!
HSD_DLLv2: libusb_close!
HSD_DLLv2: libusb_close!
HSD_DLLv2: libusb_close!
HSD_DLLv2: libusb_close!
HSD_DLLv2: CONNECTED!
2025-03-26 13:18:40,202 - HSDatalogApp.st_hsdatalog.HSD_link.communication.PnPL_HSD.PnPLHSD_com_manager - INFO - Communication Engine UP (libhs_datalog_v2 DLL/so) (PnPLHSD_com_manager.py:45)
2025-03-26 13:18:40,203 - HSDatalogApp.st_hsdatalog.HSD_link.HSDLink_v2 - INFO - Vespucci PnPL Commands (HSDLink_v2.py:89)
2025-03-26 13:18:40,203 - HSDatalogApp.st_hsdatalog.HSD_link.communication.STWIN_HSD.STWINHSD_com_manager - INFO - Communication Engine DOWN (libhs_datalog_v1 DLL/so) (STWINHSD_com_manager.py:142)
2025-03-26 13:18:40,204 - HSDatalogApp.st_hsdatalog.HSD_link.HSDLink - INFO - Commmunication Opened correctly
Traceback (most recent call last):
File "c:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples\st_dtdl_gui\Widgets\ConnectionWidget.py", line 123, in clicked_COM_connect_button
self.controller.load_device_template(board_id,fw_id)
File "c:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples\st_hsdatalog\HSD_GUI\HSD_Controller.py", line 339, in load_device_template
super().load_local_device_template(dev_template_json)
File "c:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples\st_dtdl_gui\STDTDL_Controller.py", line 106, in load_local_device_template
self.components_dtdl = self.__dt_manager.get_components()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\A508196\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\st_pnpl\DTDL\device_template_manager.py", line 56, in get_components
for content in self.get_root_component().contents:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'contents'
Traceback (most recent call last):
File "c:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples\st_dtdl_gui\STDTDL_MainWindow.py", line 196, in s_device_connected
for i in reversed(range(self.widget_device_config.layout().count())):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'layout'
Traceback (most recent call last):
File "c:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples\st_dtdl_gui\Widgets\ConnectionWidget.py", line 123, in clicked_COM_connect_button
self.controller.load_device_template(board_id,fw_id)
File "c:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples\st_hsdatalog\HSD_GUI\HSD_Controller.py", line 339, in load_device_template
super().load_local_device_template(dev_template_json)
File "c:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples\st_dtdl_gui\STDTDL_Controller.py", line 106, in load_local_device_template
self.components_dtdl = self.__dt_manager.get_components()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\A508196\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\st_pnpl\DTDL\device_template_manager.py", line 56, in get_components
for content in self.get_root_component().contents:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'contents'
PS C:\ST\STM32CubeFunctionPack_DATALOG2_V2.3.0\Utilities\HSDPython_SDK\examples>

[SimonePradolini]

Hello @Old_Geezer 

From v3.0.0, HSDPython_SDK has been removed from FP-SNS-DATALOG2 and it has been released as a separate product with the new part number STDATALOG-PYSDK.

The new Python SDK has been rebranded, completely redesigned and reshaped with new features. For example, the hsdatalog_GUI has been rebranded as stdatalog_GUI distributed in stdatalog_examplesgui_applications/stdatalog/GUI folder.

The error you reported depends from the SDK version you’re using: v2.3.0-based SDK can’t work with v3.0.0 firmware. v3.0.0 firmware needs STDATALOG-PYSDK. By installing the latest STDATALOG-PYSDK, the issue will be solved.

New references are available in the function pack Quick Start Guide, Release_Notes, and README files.

Detailed explanations on the brand-new Python SDK are available on the STDATALOG-PYSDK GitHub repository. Be sure to follow the instructions available in the How to use and How to install sections.

Best regards,

Simone

[SimonePradolini]

Hello @Old_Geezer 

any news on the topic? Have you installed STDATALOG-PYSDK properly and used it with FP-SNS-DATALOG2 v3.0.0?

Best regards

Simone

[Old_Geezer]

No. All things are getting worse.

I didn't mention that the ST BLE apps are seemingly not compatible with 3.0.0, the green LED stops blinking when I press the Play button on the app.

Reverted to using 2.3, 2.2 and 2.1 and they are happy with the phone apps, however when unpacking/showing a measured dataset I get complaints from the *_plot and *_GUI python programs that a measurement description file (*.json) is bad. 

I have always had problems with installing your PC SW on this corporate PC but it got worse with this version when packets are separated. I'll be back with more info about the above issues.